Do EDI profiles support nested instance identifiers?

Document created by Nikita_nandakumar on Feb 13, 2014Last modified by Adam Arrowsmith on Mar 15, 2017
Version 2Show Document
  • View in full screen mode

Nested instance identifiers are currently not supported in profiles. There is currently an open idea for supporting nested instance identifiers: Support nested identifier instances.

 

Example Scenario

A scenario where you are trying to process an 850 from a customer who is sending multiple N3 segments in their Ship To information.

 

For example:
The following represents how the elements are mapped in the CN segment:

 

1050[type=CN]
type=CN (qualifier identifier)
code=AAFES (Default Value)
adr1 = mapped from N1 Loop (ST qualifier identifier) N301 (occurrence identifier = 1)
adr2 = mapped from N1 Loop (ST qualifier identifier) N302 (occurrence identifier = 1)
adr3 = mapped from N1 Loop (ST qualifier identifier) N301 (occurrence identifier = 2)
city = mapped from N1 Loop (ST qualifier identifier) N401
state = mapped from N1 Loop (ST qualifier identifier) N402
zip = mapped from N1 Loop (ST qualifier identifier) N403

 

The problem is with mapping them (adr1, adr2 and adr3) to one line in the destination profile. You might see the occurrence identifiers being getting switched on re-saving the map.

This is because the Nested instance identifiers are currently not supported by the platform.

 

A possible work around, would be to combine instances into a common element. You can use multiple identifiers to select a specific element i.e. [ element=qualifier, element2=qualifier, element3=qualifier ]

2 people found this helpful

Attachments

    Outcomes