Product Documentation
Abstract
EDI Standards are used in the WebSphere Data Interchange Client. A number of common standards are provided with the WebSphere Data Interchange product. These standards are provided in WDI Import format so that they can be imported into WDI using the WDI Client or WDI Server.
WDI customers using X12 standards may have implemented standards provided that use one of two different loop id assignments defined in the transaction sets. The two loop id assignments are those using the loop start segment ID or a short (4 digit) numeric value as documented by X12 and those generated by WDI processes with a long (6 digit) numeric value.
Due to an inconsistency in how Loop ID assignments have been provided within WDI import files for X12 standards since X12V5R5, two different formats are being provided to better accommodate map migration between versions.
This document will describe how customers can identify which X12 standard import file they should download.
Content
WDI customers using X12 standards may have implemented standards provided that use one of two different loop id assignments defined in the transaction sets. The two loop id assignments are those using the loop start segment ID or a short (4 digit) numeric value as documented by X12 and those generated by WDI processes with a long (6 digit) numeric value.
Due to an inconsistency in how Loop ID assignments have been provided within WDI import files for X12 standards since X12V5R5, two different formats are being provided to better accommodate map migration between versions.
Download file name examples:
x12v7r1.zip (loop start segment ID or 4 digit numeric value)
x12v7r1.lpidsix.zip (6 digit numeric value)
The recommended and most consistent use of Loop IDs for X12 standards are those using the loop start segment ID or a short (4 digit) numeric value as documented by X12.
Download file name example: x12v7r1.zip
Below is the 850 transaction using the loop start segment ID as the Loop ID:
Below is the 106 transaction using the short(4 digit) numeric value as the Loop ID:
WDI import files going back to X12V5R5 have been inconsistent whereby Loop ID assignments may instead be in a long (6 digit) numeric format. The 6 digit numeric format is generated by the WDI process that creates the import files.
Download file name example: x12v7r1.lpidsix.zip
Below is the 850 transaction using the WDI generated 6 digit numeric value as the Loop ID:
Below is the 106 transaction using the WDI generated 6 digit numeric value as the Loop ID:
Note to users who are migrating an existing map to a newer version of X12.
This discrepancy with the Loop ID assignment will cause WDI Client to report an error, as follows, when the EDI Dictionary Name for map is updated to an X12 version using a different Loop ID assignment than what was used in the original mapping:
15446 - A mapping for table "x" and position "yyy" will be deleted, since the Segment that started the Loop does not exist in the "zzz" Transaction of the "X12V7R1" EDI Standard Dictionary.
Note that it is also possible for the 15446 error to be reported as a result of X12 changes in Loop structure for a given transaction. In other words, it is not always the result of how WDI forms loop IDs. In which case, the alternative WDI import format will not resolve the issue and the loop will need to be remapped.
To check which format is currently in use, go to the EDI standard being migrated from and open the associated transaction set. If there are loop start segment IDs or a short (4 digit) numeric value as forming loop ID assignments, then use the recommended (x12v7r1.zip). If there are long (6 digit) numeric assignments, then use (x12v7r1.lpidsix.zip) for compatibility.
Was this topic helpful?
Document Information
Modified date:
19 July 2019
UID
swg27042956