EDI 837

Health Net EDI 837 Professional and Institutional Submissions Mapping Guides Health Net requires at least one ST and one SE record per Submitter ID within a submission. This means that Health Net requires one ST and one SE for each unique occurrence of the 1000A NM109 Submitter ID field. Health Net does not want any additional ST/SE Read More →

LWC EDI Production Claim

LWC EDI Production Claim JCN Assignment LWC EDI Production Claim JCN assignments will be used for the EDI Production Process that will be applicable in the daily business in the production environment use of JCN within LWC. Data Population Format: 4 digit year (based on calendar year) followed by a unique 6 digit number using Read More →

EDI logistics training

COPARN EDIFACT Message (Container announcement message) COPARN EDIFACT Message contains an order to release, to make available, to accept or to call down containers or to announce the impending arrival of containers. COPARN EDIFACT Message Raw EDI Data: UNB+UNOC:2+MSC+BRPNGTC+160225:1048+000024609 UNH+1+COPARN:D:00B:UN:SMDG20 BGM+11+MSC160225647885+9 RFF+BN:241ISZ0779329 DTM+137:201602251040:203 TDT+20+FI608R+1++MSC:172:20+++D5CC9:103::MSC ANCHORAGE RFF+VON:1728613 LOC+9+BRPNG:139:6:PARANAGUA+BR:162:5:BRAZIL DTM+133:201603050400:203 NAD+CF+MSC NAD+MS+MSC EQD+CN++4510:102:5++2+5 RFF+BN:241ISZ0779329 RFF+SQ:1 EQN+1:2 LOC+9+BRPNG:139:6:PARANAGUA+BR:162:5:BRAZIL LOC+11+CNSHA:139:6:SHANGHAI+CN:162:5:CHINA Read More →

EDI 322 Transaction Set

EDI 322 Transaction Set: Terminal Operations and Intermodal Ramp Activity (BNSF Railway) EDI 322 Transaction Set can be used to provide all the information necessary for a railroad, terminal operation, port authority, or Intermodal ramp to communicate rail events (e.g. arrivals, departures), as well as terminal and Intermodal ramp activities (e.g., “ingates” or “outgates”), to authorized Read More →

EDI Acknowledgements

EDI Acknowledgements and Reports (AHCCCS) AHCCCS will respond to all transactions with the creation of the standard Acknowledgement response files as defined in the HIPAA Implementation Guides. EDI system will not reject the whole file but will be split to good/bad records. An acknowledgement is produced accordingly and the good documents will continue for further processing. Read More →

EDI Control Segments

  EDI Transaction Control Segments/Envelopes (AHCCCS EDI Requirements) EDI transactions transmitted during a session or as a batch are identified by an interchange header segment (ISA) and trailer segment (IEA) which forms the envelope enclosing the transmission. Each ISA marks the beginning of the transmission and provides sender and receiver identification. Only one set of ISA/IEA is Read More →

EDI logistics training

Gentex ASN Over-Pack Label Requirements Gentex ASN Over-Pack Label requirements must be followed by all suppliers on ASN with Gentex. ASN Over-pack containers must have labels with the following information in the order listed below: ASN Number (same as supplier packing slip number) with barcode including the embedded data identifier “2S”. Please note that the ASN Read More →

EDI X12 envelope

EDI X12 Structure: Interchange Control Header (ISA) EDI X12 Structure will be analyzed on the the EDI 850 example document (Purchase Order). This particular EDI file contains two purchase orders from a retailer to a supplier, sent on 11/01/2005. Now you see why EDI transactions are primarily handled by computers. But with a little practice after our webinars you’ll Read More →

H-E-B EDI ASN

H-E-B EDI ASN Required Segments by Hierarchy Level Today we focus on H-E-B EDI ASN Required Segments – primary product/shipment segments and specific requirements. Designing your ASN to meet the requirements below is critical to implementing Advance Shipping Notices with H-E-B. Tare Hierarchy Level The example below shows the basic requirements when defining Tare Level: HL*0003*0002*T Read More →

EDI 810 Invoice

EDI 810 Invoice Specifications – PVH Corp. Vendors EDI 810 Invoice types are represented by the two ones which are direct-to-store and consolidated. Direct-to-Store – PVH Corp. requires one invoice per store destination. Consolidated – PVH Corp. requires one invoice for the warehouse destination for warehouse shipments and mark-for-store shipments. BIG SEGMENT: This segment contains the invoice Read More →