The CTA segment names a contact person or department associated with the preceding NAD party. The qualifier indicates the role: OC=order contact, IC=information contact, PD=purchasing contact. The contact name appears in element 2 sub-element 2. Followed by COM segments for phone and email.
CTAHover any part of the segment to see what it is. Open What your system receives to see the JSON or XML CleanEDI delivers.
CTA+OC+:Jane Smith'Order contact: Jane Smith.
| 1 | Contact function | OCOrder contact |
| 2.2 | Contact: Name | Jane Smith |
{
"contacts": [
{
"role": "orderContact",
"name": "Jane Smith"
}
]
}Example shape. In production the field names and structure follow your own API contract.
Elements are separated by + and their parts by :. Positions match the explainer, so 2.3 is the third part of the second element.
| Position | Element | Parts |
|---|---|---|
| 1 | Contact function | 1.1 Code |
| 2 | Contact | 2.1 ID, 2.2 Name |
| Code | Meaning |
|---|---|
IC | Information contact |
OC | Order contact |
PD | Purchasing contact |
DL | Delivery contact |
AD | Accounts contact |
Common EANCOM and UN/EDIFACT values. Your trading partner's implementation guide is the final word on which codes they send.
Have a real message with CTA in it? The explainer breaks down every segment and runs in your browser.
Explain my message