SARS Mapping Guidelines: Interchange Header Segment Elements (Continued) Application Reference (0026) element may be used only if the interchange contains one message type. A reference to the specific systems’ application that will process all the messages in the interchange can be made here. Processing Priority Code (0029) Code denoting the processing priority for the interchange as assigned by … Read More →
Shipping Container Identification Numbers Container identification numbers are transmitted in MAN segments within the appropriate packaging level (Shipment, Unit Load, Tare or Pack). The recommended ID is the human-readable interpretation of the UCC/EAN-128 Serial Shipping Container Code (SSCC-18). When MAN01 contains code AA, MAN02 will contain the eighteen-character UCC/EAN-128 Serial Shipping Container Code which does not include the two-digit application … Read More →
Hierarchical structure examples: Pick and Pack Following is an example of Pick and Pack EDI 856 transaction hierarchical structure. Each box in the diagram represents a detail loop (one HL segment followed by data segments) in a Ship Notice/Manifest transaction set. In this example, the shipment contains 2 orders. The first order has 3 cartons. The first carton contains … Read More →
Mapping Guidelines For the HL Segment EDI 856 Advance Shipping Notice The HL segment marks the beginning of a detail loop. A clear understanding of how the HL segment works is a critical factor in the successful generation and receipt of the Ship Notice/Manifest transaction. There are three data elements in the HL segment which are defined … Read More →