Shipment notice APIs

Shipment notices allow companies to exchange serialized data for sales shipments with upstream and downstream supply chain trade partners without giving these trade partners access to their serialization system of record. These shipment notices can be used to inform their Partners of the contents of a shipment, and the notices also allow these companies to comply with government regulations or recommendations for sharing serialized data about shipments.

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement, Transportation, Clinical Supply,; Function = Supply Chain, IT, Regulatory Affairs,

Serialized Shipment Notice (EPCIS v1.2)

The Serialized Shipment Notice message sends serialization data about a sales shipment and allows companies to communicate that information to Partners via Multienterprise Process Connect. Use the EPCIS 1.2 format if your internal systems normally use this format.

If the Owner uses TraceLink as their serialization system of record and is sending the shipment to a Partner:

  1. The Owner sends a sales shipment through Serialized Operations Manager with a Distribution Type of Sale - In Country or Sale - Export and the shipment contains product with one of the following target markets in product master data:
    • Bahrain
    • Brazil
    • Indonesia
    • Saudi Arabia
    • South Korea
    • UAE
    • Uzbekistan
  2. Multienterprise Process Connect generates a Serialized Shipment Notice and sends the Multienterprise Process Connect outbound Serialized Shipment Notice message to the receiving Partner.

If the Owner does not use TraceLink as their serialization system of record and is sending the shipment to a Partner:

  1. The Owner sends an inbound Serialized Shipment Notice message to Multienterprise Process Connect.
  2. TraceLink processes the Multienterprise Process Connect message and delivers it to the receiving Partner.

If a Partner is sending the shipment to the Multienterprise Process Connect Owner that uses TraceLink as their serialization system of record:

  1. The Partner sends an Multienterprise Process Connect Serialized Shipment Notice message to Multienterprise Process Connect.
  2. TraceLink processes the Multienterprise Process Connect message and delivers it via outbound Serialized Shipment Notice to the Owner.

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement, Transportation, Clinical Supply,; Function = Supply Chain, IT,

Advance Ship Notice (IDoc)

The Advance Ship Notice (ASN) IDoc message sends data about a purchase order the supplier is fulfilling and notifies the buyer of the pending goods delivery.

Companies can communicate using the standard IDoc format they normally use to communicate with Partners from their ERP to communicate asynchronously with the Multienterprise Process Connect app. While TraceLink supports this message format, companies must follow some TraceLink specific requirements for the message header control settings in all asynchronous IDoc message communications sent inbound to TraceLink.
  • Message Type: MPC_ADVANCE_SHIP_NOTICE (Advanced Ship Notice)
  • IDoc Format: DESADV.DELVRY07
  • Transform Names:
    • B2B_IDoc_DELVRY07_ASN_IB_V1
    • B2B_IDoc_DELVRY07_ASN_OB_V1

When sending an ASN IDoc message from your company inbound to TraceLink, TraceLink requires that the values for the following elements in the message header control settings must be present for TraceLink to correctly process the B2B message:

  • SNDLADRequired. Either the sending company's internal SAP, GLN, or other global identifier must be present. If the company's internal SAP identifier is present, do not include a prefix on the identifier (i.e. 0000009010). If using a global identifier the identifier type must be included as a prefix before the identifier separated by a colon (i.e. GLN:0023456789157).
  • RVCLADRequired. The internal SAP, GLN, or other global identifier of the receiving company. If the company's internal SAP identifier is sent, do not include a prefix on the identifier (i.e. 0000009010). If using a global identifier the identifier type must be included as a prefix before the identifier separated by a colon (i.e. GLN:0023456789157). The party that is the ultimate intended recipient of the message must be provided for RVCLAD. Do not identify TraceLink as the recipient for RVCLAD.
  • RVCPRNRequired. This element must indicate TraceLink as the receiving system. Additionally, the outbound partner profile for TraceLink must be configured as a logical system type in the senders SAP.

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement, Transportation, Clinical Supply,; Function = Supply Chain, IT,

Advance Ship Notice (X12)

The Advance Ship Notice (ASN) X12 message sends data about a purchase order the supplier is fulfilling and notifies the buyer of the pending goods delivery.

Contact your TraceLink Services representative for more information about integrating with this message.

  • Message Type: MPC_ADVANCE_SHIP_NOTICE (Advanced Ship Notice)
  • X12 Format: 856
  • Transform Names:
    • B2B_EDI_X12_856_AdvanceShipNotice_IB_V1
    • B2B_EDI_X12_856_AdvanceShipNotice_OB_V1

Tag end

Type = API Reference,; Topic = Multienterprise Information Network Tower,;Persona = TraceLink Administrator, User, Orchestration Architect,; Orchestration = Manufacturing, Logistics, Procurement, Transportation, Clinical Supply,; Function = Supply Chain, IT,

Advance Ship Notice (EDIFACT)

The Advance Ship Notice (ASN) EDIFACT message sends data about a purchase order the supplier is fulfilling and notifies the buyer of the pending goods delivery.

Contact your TraceLink Services representative for more information about integrating with this message.

  • Message Type: MPC_ADVANCE_SHIP_NOTICE (Advanced Ship Notice)
  • EDIFACT Format: ORDERS
  • Transform Names:
    • B2B_EDI_EDIFACT_DESADV_AdvanceShipNotice_IB_V1

    • B2B_EDI_EDIFACT_DESADV_AdvanceShipNotice_OB_V1

Tag end