Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

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 TRX

Image1 (3)-20240730-102549.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

  1. Under the Mapping go to the Folder option

  2. On left hand corner, can find the folder Icon

  3. Then go the preferences

4. Check Filter Empty Elements

Whenever the File contains Empty elements or clients requirement that they donot want to print the empty elements.

Image2 (2)-20240730-102638.png

Filter Unmapped Element

  1. Under the Mapping go to the Folder option

  2. On left hand corner, can find the folder Icon

  3. Then go the preferences

  4. Check Filter Unmapped Elements

Clients requirement that they donot want to print the Umapped Elements for the File.

Image2 (3)-20240730-102716.png

Do not use Filter Empty Element/Filter Unmapped Element for inbound transaction

  1. Under the Mapping go to the Folder option

  2. On left hand corner, can find the folder Icon

  3. Then go the preferences

  4. Uncheck Filter Unmapped Elements and Filter Empty Element if checked

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

  1. Go to mapping expression

  2. Check for the mapping rule

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.

  1. It suggested to use Reference map so that that reference Map can be used Further for developing Other Maps.

  2. Usage of Reference Maps: Streamline the design process of EDI maps by seamlessly integrating Reference Maps, facilitating a more efficient and straightforward approach to map creation.

NA

Reuse the Same Map

This is particularly useful for ensuring consistency, reducing redundancy, and simplifying maintenance efforts.

  1. It is suggested that we can reuse the Same Map if the validations and the Layouts are same for different partners , In simple term we can say that we can re utilize the same Map again and again if needed.

  2. Design EDI maps that can be reused across multiple trading partners and transactions to minimize redundancy and streamline maintenance.

NA

Check if the mapping is specified under the project.

1.Under the Mapping go to the update mapping details
2.Check the project

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
2.Under UNB and ISA envelope You can define the control Number manually

1.We can define the Type for control number, Globally it can be Timestamp or Sequentially.
2.We can define through Envelope also by Manually Putting up a random number for Control.

Image3 (2)-20240730-102805.png

Generate ACK file with the Help of Schema

  1. Go to the edi Schema

  2. Test the EDi file through Schemna

  3. After testing the file , we will get source,Traget and ACK file

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.

Image4 (1)-20240730-102903.png

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

Image5 (1)-20240730-102956.png

ACK file Configuration

  1. For X12 - Replace AK1 02 with the Control Number ISA13 or GS06 located in the actual EDI file. Subsequently, we can employ the resulting ACK file to test the ACK transaction.

  2. For EDIFACT - In ACK file UCI01 field must match with our input file UNB05 field (control number)


In ACK file UCM01 field must match with our input file UNH01 field.

Suppose if we are Generating the ACK file from Schema or client has shared us the sample ACK file

Image6 (1)-20240730-103043.png

Status for the Received Acknowledgement

  1. Go to the Dashboard

  2. EDI X12 Interchanges.

  3. Check the status Column

Always check the Status for the Received Acknowledgement , It should be Updated as “ACCEPTED”

Image7 (1)-20240730-103204.png

Same :Association Assigned Code for ACK and EDI file

Association Assigned Code;
UNH+408021748+CONTRL:D:97A:UN:Association Assigned Code

Associated set code should be similar in both in the inbound source file and EDIFACT Inbound transaction.
The Association Assigned Code should match that is defined in the EDIFACT inbound transaction with the source file located at UNH02 of 5th position.

Image8 (1)-20240730-103329.png

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
The version should match that is defined in the EDIFACT inbound transaction with the inbound transaction source file located at UNH02 of 2nd+3rd position.

Image9-20240730-103413.png

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
The Transaction Set Code should match that is defined in the EDIFACT inbound transaction with the inbound transaction source file located at UNH02 of 1st position.

Image10-20240730-103445.png

  • No labels