EDIFACT inbound trade links
Trade links can be added, changed, or deleted. In addition, existing Trade Links can have their individual Documents added, changed, or deleted.
To add a new EDIFACT Inbound trade link, use the tags EDFIBTradeLink, EDFIBAPLink, and EDFInboundGroups. To change an existing EDIFACT Inbound Trade Link, use the tags EDFIBTradeLinkChange, EDFIBAPLinkChange, and EDFInboundGroupsAddChangeDelete. To delete an entire EDIFACT Inbound Trade Link, use EDFIBTLDelete.
There are two types of EDIFACT Inbound Trade Links: Known and Unknown. Unlike X12, there is no special Unknown Record type for EDIFACT Inbound Trade Links. Define unknown Trading Partners by setting the FromIchgID to UNKNOWN and leaving FromIchgIdCdQual and FromRoutingAddress blank (or not specified) in the XML data.
- Applications are specified in the EDFInboundGroups record when adding a new Trade Link; otherwise use the EDFInboundGroupsAddChangeDelete tag. An Application is the unique combination of Message Version, Message Release, Controlling Agency, the optional Association Assign Code, and a Functional ID/Message Type. Adding Applications to an existing Trade Link is supported in the "change" tags. See:
Trading/Application Partners must previously exist in the database for the Trade Link to be added. Unlike X12, Application Partners may or may not be specified on a Trade Link, depending on the setting of MandatoryUNG. Application Partners, if required, are specified within the EDFIBAPLink and EDFIBAPLinkChange tags, and must belong to the Trading Partner specified in the EDFIBTradeLink/EDFIBTradeLinkChange tags. Application Partners can only be specified if the MandatoryUNG field in EDFIBTradeLink is set to O (optional) or M (mandatory).
Applications (Documents) are nested within the Trade Link record when there is no UNG level; otherwise Applications are nested within the Application Partner record (EDFIBAPLink/EDFIBApLinkChange). The same Application cannot appear more than once within a Trade Link.