EDIFACT Application Partners (Tag: EDFAppPartners)
As with X12 Trading Partners, there can be zero or more Application Partners associated with an EDIFACT Trading Partner. Unlike X12, Application Partners are not required to create a Trade Link. Use this tag, when nested within a Trading Partner, to add Application Partners at the same time. If any Trading Partners are rejected, all associated Application Partners are rejected as well. EDIFACT Application Partners can have Contacts added . The tag and field descriptions are described in the following table:
| Field Label | FieldName/Tag | Req'd | Max. Len. | Validation | Notes |
|---|---|---|---|---|---|
| N/A | IchgIdCdQual | Yes | 4 | IchgIdCdQual of Trading Partner. May be 4 spaces | 1 |
| N/A | IchgID | Yes | 35 | IchgID of Trading Partner | 1 |
| N/A | RoutingAddress | No | 14 | Routing Address of Trading Partner | 1 |
| Application Partner Name | ApplicationName | Yes | 35 | Unique within the Trading Partner | 2 |
| UNG Application ID | UNG_AppID | Yes | 35 | Unique within the Trading Partner | |
| Application Partner ID Code Qualifier | IDCdQual | No | 4 Default: 4 spaces (None) |
fk to EDFIdCdQual | |
| Password | Password | No | 14 | External only | |
| Alias | AliasName | No | 20 | Unique if present | 3 |
| User Defined 1 | UserDefined1 | No | 20 | ||
| User Defined 2 | UserDefined2 | No | 20 |
Notes:
- The IDs of the owner of this Application Partner; equal to the previously specified Trading Partner. Used to confirm that the XML is properly formed (Application Partners nested within the parent Trading Partner).
- Do not use the name "UNKNOWN, or "ALL", or any variation of the case of these two words. For example, do not use "Unknown", or "All".
- Alias Names are unique across all EDIFACT Application Partners, if present.