Description: Limited to code that may be executed before and after EDI data is mapped. The EDI filters enable you to translate values in an EDI message for a particular field, such as translating a port code from a value not recognized by a terminal to a value that you recognize. However, to perform more complex validations on the extracted data, such as translating port codes only for a particular trading partner, you can add the EDI_EXTRACT_INTERCEPTOR extension type to the Extension form (on page 1). You can amend the extracted EDI data from N4 either before or after it is mapped. This groovy hook is similar to the EDI_POST_INTERCEPTOR but for outbound EDI messages. To amend the extracted data from N4, you need to override either the beforeEdiMap or afterEdiMap method in your groovy and then add this groovy to the applicable outbound EDI session.
If you override the beforeEdiMap.api in groovy, N4 extracts data per the EDI XML standard. In this case, to override the data, follow the EDI XML schema definition, such as the activity.xsd or stowplan.xsd. Also, you can add filters and pass necessary conditions by overriding the beforeEdiExtract API. In addition, you can add filters and pass the updated predicate by overriding the beforeEdiExtract API. In this case, saved filters in the EDI session are passed to the groovy.
If you override the afterEdiMap.api in groovy, N4 extracts per the EDI standard. In this case, to override the data, follow the EDI standard.
If you override the afterEdiLoad.api you can introduce custom code after the EDI load process. The afterEdiLoad() call back method will be called immediately after loading the EDI file into the system. The BatchGkey is primary key of the batch of the associated groovy.
Abstract Base Class: AbstractEdiExtractInterceptor
Method: beforeEdiMap(Map inParams),afterEdiMap(Map inParams)and beforeEdiExtract(Map inParams), afterEdiLoad(Serializable inEdiBatchGkey);
Interface: EEdiExtractInterceptor
Module: EDI
Version Added: 2.2
Requires Code Extension Name or Name Pattern: No
Code Extension Name or Name Pattern: N/A
Where to specify code extensions of this type: In the EDI Session form