Examples

The following examples show how the XML data would look during an add operation:

Example 1 - Mandatory

Example 1: If MandatoryUNG is M (Mandatory), the XML would look like:

<EDFIBTradeLink>
   ...header data
   <EDFIBAPLink>
   ...specify application partners here
      <EDFInboundGroups>
      ...application data
      </EDFInboundGroups>
   </EDFIBAPLink>
</EDFIBTradeLink>

Example 2 - None

Example 2: If MandatoryUNG is N (None), the XML would look like:

<EDFIBTradeLink>

...header data

<EDFInboundGroups>

...application data

</EDFInboundGroups>

</EDFIBTradeLink>

Example 3 - Optional

Example 3: MandatoryUNG is O (Optional), and only one of the Applications is associated with an Application Partner (UNG). The XML would look like:

<EDFIBTradeLink>

...header data

<EDFIBAPLink>

...specify application partners here

<EDFInboundGroups>

...application data associated with the Application Partner

</EDFInboundGroups>

</EDFIBAPLink>

<EDFInboundGroups>

...application data not associated with any Application Partner

</EDFInboundGroups>

</EDFIBTradeLink>

The following table, field, and tag descriptions are for EDIFACT inbound trade links:

• "EDIFACT Inbound Trade Links (Tag: EDFIBTradeLink)"
• "EDIFACT Inbound Application Partner Trade Links (Tag: EDFIBAPLink)"
• "EDIFACT Inbound Applications Trade Links (Tag: EDFInboundGroups"
• "EDIFACT Inbound Trade Link Change (Tag: EDFIBTradeLinkChange)"
• "EDIFACT Inbound Application Partner Trade Links Change (Tag: EDFIBAPLinkChange)"
• EDIFACT Inbound Applications Trade Links Add, Change, Delete (Tag: EDFInboundGroupsAddChangeDelete)
• "EDIFACT Inbound Trade Links Delete (Tag: EDFIBTLDelete)"