Best Practice | Step to perform | When to apply or when not to apply | Image Link |
Filtering ISA, GS, ST, SE, GE and IEA Segments | Under the Mapping ISA,GS,ST,SE,GE and IEA segment should applied Filter Option | It has to applied in Outbound Transaction for X12 EDI TRXImage1.png | |
Filtering UNB, UNH, UNT, UNZ Segments | Under the Mapping UNB, UNH, UNT, UNZ segment should applied Filter Option | It has to applied in Outbound Transaction for EDIFACT TRX | NA |
Filter Empty Element |
4. Check Filter Empty Elements | Whenever the File contains Empty elements or clients requirement that they donot want to print the empty elements.Image2.png | |
Filter Unmapped Element |
| Clients requirement that they donot want to print the Umapped Elements for the File.Image2.png | |
Do not use Filter Empty Element/Filter Unmapped Element for inbound transaction |
| When the Filter Unmapped Elements and Filter Empty Element if checked ,transaction fails | NA |
Use absolute Path in mapping rule if for each applied on root level |
| When the 'For Each' loop is applied at the root level, verify that relative paths used in mapping expressions correctly process dynamic values | NA |
Usage of Reference Maps | Create a Reference Map so that with the help of that we can create other Maps Easily. |
| NA |
Reuse the Same Map | This is particularly useful for ensuring consistency, reducing redundancy, and simplifying maintenance efforts. |
| NA |
Check if the mapping is specified under the project. | 1.Under the Mapping go to the update mapping details | It has to applied in Outbound Transaction for EDI TRX | NA |
Acknowledgement Configuration
Best Practice | Step to perform | When to apply or when not to apply | Image Link |
Define Control Number Globally or Manually for ISA and GS segment. | 1.Under Settings > Solution Properties > Edi solution Parameters we can define the type | 1.We can define the Type for control number, Globally it can be Timestamp or Sequentially. | |
Generate ACK file with the Help of Schema |
| Generate an Acknowledgement file corresponding to the EDI file during Schema testing. This testing process will produce a Source file, Target file, and ACK file, which can be utilized for testing purposes. | |
Generate Acknowledgement must be set as Yes - With error detail. | In the EDI configuration, Generate Acknowledgement must be set as Yes - With error detail. | It will be useful to find out the error if ACK files fails | |
ACK file Configuration |
| Suppose if we are Generating the ACK file from Schema or client has shared us the sample ACK file | |
Status for the Received Acknowledgement |
| Always check the Status for the Received Acknowledgement , It should be Updated as “ACCEPTED” | |
Same :Association Assigned Code for ACK and EDI file | Association Assigned Code; | Associated set code should be similar in both in the inbound source file and EDIFACT Inbound transaction. | |
Same version Code for ACK and EDI file | UNH+408021748+CONTRL:version:UN:281' | Version should be match in the inbound source file and EDIFACT Inbound transaction | |
Same Transaction Set Code for ACK and EDI file | UCM+408021748+Transaction Set Code:D:97A:UN:281' | Transaction Set Code should be match in the inbound source file and EDIFACT Inbound transaction |