EDI 856 Ship Notice /Manifest Transaction Notes For Family Dollar Vendors

EDI 856 Ship NoticeEDI 856 Ship Notice /Manifest transaction set  is used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The EDI 856 Ship Notice /Manifest transaction transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of EDI 856 Ship Notice /Manifest transaction can be any organization having an interest in the contents of a shipment or information about the contents of a shipment. Some particular mapping notes for EDI 856 Ship Notice /Manifest transaction are given below.

Functional Group SH

  • Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
  • The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

HL Segment

  • The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data. The HL segment defines a top-down/left-right ordered structure.
  • HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be “1” for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
  • HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
  • HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or itemlevel information.
  • HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

TD1 Segment

  • If TD101 is present, then TD102 is required.
  • If TD103 is present, then TD104 is required.
  • If TD106 is present, then TD107 is required.
  • If either TD107 or TD108 is present, then the other is required.
  • If either TD109 or TD110 is present, then the other is required.

Find more mapping notes for other segments in our next posts.

Learn about other Family Dollar transactions mapping notes now

 

Leave a Reply

Your email address will not be published.

Post Navigation