EDI 210 - Carrier Invoice - BluJay Solutions Ltd.
Carrier Invoice EDI–210 Format X12 Version 004010 Inbound Revised: Revision: July 28, 2021 2.0
DISCLAIMER This document is the property of BluJay Solutions and the information contained herein is confidential. This document, either in whole or in part, must not be reproduced or disclosed to others or used for purposes other than that for which it has been supplied without BluJay Solutions’ prior written permission, or, if any part hereof is furnished by virtue of a contract with a third party, as expressly authorized under that contract. BluJay Solutions Page 2
EXECUTIVE SUMMARY The Freight Invoice is used to electronically communicate shipment cost information to the Shipper. The Freight Invoice includes information about the load such as reference numbers, actual pickup and delivery times, locations, line-haul rate and charge, accessorial rates and charges, etc. Freight Invoice EDI documents in BluJay Solutions Transportation Management, formerly Lean Logistics, use the ANSI X12 – 210 (Motor Carrier Load Freight Details and Invoice) specification version 004010. This specification is included as well as examples of its use. Three types of Freight Invoice messages are supported by BluJay Solutions Transportation Management: Original – First Invoice for a particular Load. Adjustment - An Invoice that contains only new charges, not included on the original Invoice (Balance Due Billing). Rebilling - A complete replacement Invoice for a particular Load (Correction). BluJay Solutions Transportation Management will send X12 997 Functional Acknowledgments for this EDI transaction as directed by the ISA14 Acknowledgment Requested value. Special Characters Delimiters BluJay Solutions Transportation Management uses the asterisk (*) for the element terminator, the tilde ( ) for the segment terminator, and the vertical bar ( ) for the sub-element separator. Please do not use any other delimiters. BluJay Solutions Page 3
210 Motor Carrier Freight Details and Invoice Functional Group ID IM Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Motor Carrier Freight Details and Invoice Transaction Set (210) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide detail information for charges for services rendered by a motor carrier. It is used both as a motor carrier invoice to request payment or as details pertaining to motor freight shipment(s) charges. Heading: M Pos. No. 005 Seg. ID ISA Name Interchange Control Header Req. Des. M M 008 GS Functional Group Header M 1 M 010 ST Transaction Set Header M 1 M 020 B3 Beginning Segment for Carrier's Invoice M 1 040 C3 Currency O 1 060 N9 Reference Identification O 300 Max.Use 1 LOOP ID - 0100 Loop Repeat Notes and Comments 10 110 N1 Name O 1 130 N3 Address Information O 2 140 N4 Geographic Location O 1 Pos. No. Seg. ID 010 S5 Stop-off Details O 1 030 G62 Date/Time O 10 Detail: Name LOOP ID - 0300 Req. Des. Max.Use LOOP ID - 0310 Notes and Comments n1 2 050 N1 Name O 1 070 N3 Address Information O 2 080 N4 Geographic Location O 1 LOOP ID - 0400 9999 120 LX Assigned Number O 1 170 L0 Line Item - Quantity and Weight O 10 180 L1 Rate and Charges O 10 200 L7 Tariff Reference O 10 210 K1 Remarks O 10 BluJay Solutions Loop Repeat 999 Page 4
LOOP ID - 0430 220 SPO Shipment Purchase Order Detail 999999 O 1 LOOP ID - 0460 999999 240 N1 Name O 1 260 N3 Address Information O 2 270 N4 Geographic Location O 1 LOOP ID - 0465 350 n2 999999 SPO Shipment Purchase Order Detail O 1 Pos. No. 010 Seg. ID L3 Name Total Weight and Charges Req. Des. O M 020 SE Transaction Set Trailer M 1 M 030 GE Functional Group Trailer M 1 M 040 IEA Interchange Control Trailer M 1 Summary: Max.Use 1 Loop Repeat Notes and Comments Transaction Set Notes 1. 2. Loops 0300, 0305, 0310 and 0320 shall only be used to identify all stop-off locations and associated data for loading and unloading of freight with the exception of the original stop-off location (shipper) for truckload carriers. The original stop-off location (shipper) shall be transmitted in loop 0100. Loops 0460 and 0463 shall be used to identify all small package carrier details related to the consignee (delivery location) and the related shipment. The shipper shall be identified in loop 0100. BluJay Solutions Page 5
Segment: Position: Loop: Level: Usage: Max Use: Purpose: ISA Interchange Control Header 005 Heading Mandatory 1 To start and identify an interchange of zero or more functional groups and interchange-related control segments Syntax Notes: Semantic Notes: Comments: M Ref. Des. ISA01 M ISA02 M ISA03 M ISA04 M ISA05 M ISA06 BluJay Solutions Data Element Summary Data Element Name Attributes I01 Authorization Information Qualifier M ID 2/2 Code to identify the type of information in the Authorization Information 00 No Authorization Information Present (No Meaningful Information in I02) I02 Authorization Information M AN 10/10 Not used by the BluJay Transportation Management System I03 Security Information Qualifier M ID 2/2 Code to identify the type of information in the Security Information 00 No Security Information Present (No Meaningful Information in I04) I04 Security Information M AN 10/10 Not used by the BluJay Transportation Management System I05 Interchange ID Qualifier M ID 2/2 Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified 02 SCAC (Standard Carrier Alpha Code) ZZ Mutually Defined I06 Interchange Sender ID M AN 15/15 Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element Carrier’s SCAC Code – SCAC in BluJay Transport Management Page 6
M ISA07 I05 M ISA08 I07 M ISA09 I08 M ISA10 I09 M ISA11 I10 M ISA12 I11 M ISA13 I12 M ISA14 I13 M ISA15 I14 M ISA16 I15 BluJay Solutions Interchange ID Qualifier M ID 2/2 Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified 01 Duns (Dun & Bradstreet) ZZ Mutually Defined Interchange Receiver ID M AN 15/15 Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them This is either the BluJay Shared Organization Id (124215133) or the unique Shipper’s Organization Id (usually, the Shipper’s DUNS Number). Interchange Date M DT 6/6 Date of the interchange Interchange Time M TM 4/4 Time of the interchange Interchange Control Standards Identifier M ID 1/1 Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer U U.S. EDI Community of ASC X12, TDCC, and UCS Interchange Control Version Number M ID 5/5 This version number covers the interchange control segments 00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender Acknowledgment Requested M ID 1/1 Code sent by the sender to request an interchange acknowledgment (TA1) 0 No Acknowledgment Requested 1 Interchange Acknowledgment Requested Usage Indicator M ID 1/1 Code to indicate whether data enclosed by this interchange envelope is test, production or information P Production Data Component Element Separator M AN 1/1 BluJay TMS prefers the Greater Than symbol ( ) Page 7
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: M Ref. Des. GS01 M GS02 M GS03 M GS04 M GS05 BluJay Solutions GS Functional Group Header 008 Heading Mandatory 1 To indicate the beginning of a functional group and to provide control information 1 2 3 1 GS04 is the group date. GS05 is the group time. The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of similar transaction sets enclosed by a functional group header and a functional group trailer. Data Element Summary Data Element Name Attributes 479 Functional Identifier Code M ID 2/2 Code identifying a group of application related transaction sets IM Motor Carrier Freight Details and Invoice (210, 980) 142 Application Sender's Code M AN 2/15 Code identifying party sending transmission; codes agreed to by trading partners Carrier’s SCAC 124 Application Receiver's Code M AN 2/15 Code identifying party receiving transmission; codes agreed to by trading partners This is either the BluJay Shared Organization id (124215133) or the unique Shipper’s Organization Id (usually, Shipper’s DUNS Number). 373 Date M DT 8/8 Date expressed as CCYYMMDD 337 Time M TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (0059), S integer seconds (00-59) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9) and DD hundredths (00-99) Page 8
M GS06 28 M GS07 455 M GS08 480 BluJay Solutions Group Control Number M N0 1/9 Assigned number originated and maintained by the sender Responsible Agency Code M ID 1/2 Code used in conjunction with Data Element 480 to identify the issuer of the standard X Accredited Standards Committee X12 Version / Release / Industry Identifier Code M AN 1/12 Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used. 004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997 Page 9
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: ST Transaction Set Header 010 Heading Mandatory 1 To indicate the start of a transaction set and to assign a control number 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: M Ref. Des. ST01 M ST02 BluJay Solutions Data Element Summary Data Element Name Attributes 143 Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 210 Motor Carrier Freight Details and Invoice 329 Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Page 10
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: B3 Beginning Segment for Carrier's Invoice 020 Heading Mandatory 1 To transmit basic data relating to the carrier's invoice 1 If either B309 or B310 is present, then the other is required. 1 B306 is the billing date. 2 On collect freight bills the data in B309 will be the actual delivery date. For the shipments invoiced prior to delivery, the B309 will be the estimated date of delivery. 3 If B314 is used, B304 will indicate the party or parties responsible for payment of the transportation terms identified in B314. Comments: Not Used Ref. Des. B301 M B302 Must Use B303 Data Element Summary Data Element Name Attributes 147 Shipment Qualifier O ID 1/1 Refer to 004010 Data Element Dictionary for acceptable code values. 76 Invoice Number M AN 1/22 Identifying number assigned by issuer Carrier's Reference Number (PRO/Invoice) 145 Shipment Identification Number O AN 1/30 Identification number assigned to the shipment by the shipper that uniquely identifies the shipment from origin to ultimate destination and is not subject to modification; (Does not contain blanks or special characters) BluJay Load Id (assigned by the BluJay TMS application) M B304 146 Not Used B305 188 M B306 373 M B307 193 BluJay Solutions This MUST be the same as the Shipment Identification found in the X12 204 Load Tender, element B204. Shipment Method of Payment M ID 2/2 Code identifying payment terms for transportation charges CC Collect PP Prepaid (by Seller) Weight Unit Code O ID 1/1 Refer to 004010 Data Element Dictionary for acceptable code values. Date M DT 8/8 Date expressed as CCYYMMDD May be required by your Shipper per BluJay TMS Invoice Validation Profile settings. Net Amount Due M N2 1/12 Total charges to be paid by the receiver of this transaction set expressed in the standard monetary denomination for the currency specified Page 11
B308 202 Not Used Not Used B309 B310 32 374 M B311 140 Not Used B312 373 Not Used B313 375 Not Used B314 335 BluJay Solutions Correction Indicator O ID 2/2 Code used to indicate that the transaction set contains information which corrects previous information BD Balance Due Billing Adjustment - An Invoice that contains only new charges, not included on the original Invoice. CO Correction Rebilling - A complete replacement Invoice for a particular Load. Delivery Date X DT 8/8 Date/Time Qualifier X ID 3/3 Refer to 004010 Data Element Dictionary for acceptable code values. Standard Carrier Alpha Code M ID 2/4 Standard Carrier Alpha Code This will be the BluJay TMS Application assigned Carrier SCAC This MUST be the same SCAC that was received in the X12 204 Load Tender element B202. Date O DT 8/8 Tariff Service Code O ID 2/2 Refer to 004010 Data Element Dictionary for acceptable code values. Transportation Terms Code O ID 3/3 Refer to 004010 Data Element Dictionary for acceptable code values. Page 12
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: M Ref. Des. C301 Not Used Not Used Not Used C302 C303 C304 BluJay Solutions C3 Currency (Mandatory for BluJay Transportation Management) 040 Heading Optional 1 To specify the currency being used in the transaction set 1 2 3 1 C301 is the billing currency. C303 is the payment currency. C304 is the rated currency. Currency is implied by the code for the country in whose currency the monetary amounts are specified. This segment is mandatory for BluJay Transportation Management and should always be sent. Data Element Summary Data Element Name Attributes 100 Currency Code M ID 3/3 Code (Standard ISO) for country in whose currency the charges are specified Any valid code may be placed in this element. CAD Canadian Dollars USD United States Dollars MXN Mexican Pesos EUR Euro Dollars 280 Exchange Rate O R 4/10 100 Currency Code O ID 3/3 100 Currency Code O ID 3/3 Page 13
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: N9 Reference Identification 060 Heading Optional 300 To transmit identifying information as specified by the Reference Identification Qualifier 1 At least one of N902 or N903 is required. 2 If N906 is present, then N905 is required. 3 If either C04003 or C04004 is present, then the other is required. 4 If either C04005 or C04006 is present, then the other is required. 1 N906 reflects the time zone which the time reflects. 2 N907 contains data relating to the value cited in N902. It is recommended that at least one associated N9 “MB” and N9 “PO” reference be included. Note that the N9 “MB” and N9 “PO” references may be required by your Shipper per BluJay TMS Invoice Validation Profile “MBOL#” and “PO#” settings. M Ref. Des. N901 N902 Not Used Not Used Not Used Not Used N903 N904 N905 N906 BluJay Solutions Data Element Summary Data Element Name Attributes 128 Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Any supported reference qualifier may be sent. MB Master Bill of Lading May be required for Invoice Validation PO Purchase Order Number May be required for Invoice Validation SI Shipper's Identifying Number for Shipment (SID) 127 Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 369 Free-form Description X AN 1/45 373 Date O DT 8/8 337 Time X TM 4/8 623 Time Code O ID 2/2 Refer to 004010 Data Element Dictionary for acceptable code values. Page 14
Not Used N907 C040 Not Used C04001 128 Not Used C04002 127 Not Used C04003 128 Not Used C04004 127 Not Used C04005 128 Not Used C04006 127 BluJay Solutions Reference Identifier O To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification Refer to 004010 Data Element Dictionary for acceptable code values. Reference Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification Refer to 004010 Data Element Dictionary for acceptable code values. Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification Refer to 004010 Data Element Dictionary for acceptable code values. Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Page 15
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: M Ref. Des. N101 N102 N103 N104 Not Used N105 Not Used N106 BluJay Solutions N1 Name 110 0100 Optional (Mandatory for BluJay Transportation Management) Heading Optional 1 To identify a party by type of organization, name, and code 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. The N1 “SH” segment is used to identify the BluJay Transportation Management’s Shipper Organization Id. Usually, it is their DUNS Number. Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual SH Shipper 93 Name X AN 1/60 Free-form name 66 Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 9 D-U-N-S 4, D-U-N-S Number with Four Character Suffix 67 Identification Code X AN 2/80 Code identifying a party or other code Used for Shipper Organization Id. 706 Entity Relationship Code O ID 2/2 Refer to 004010 Data Element Dictionary for acceptable code values. 98 Entity Identifier Code O ID 2/3 Refer to 004010 Data Element Dictionary for acceptable code values. Page 16
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: M Ref. Des. N301 N302 BluJay Solutions N3 Address Information 130 0100 Optional Heading Optional 2 To specify the location of the named party Data Element Summary Data Element Name 166 Address Information Address information 166 Address Information Address information Attributes M AN 1/55 O AN 1/55 Page 17
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: N4 Geographic Location 140 0100 Optional Heading Optional 1 To specify the geographic place of the named party 1 If N406 is present, then N405 is required. 1 2 Ref. Des. N401 N402 N403 N404 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. N402 is required only if city name (N401) is in the U.S. or Canada. Data Element Summary Data Element Name Attributes 19 City Name O AN 2/30 Free-form text for city name 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) 26 Country Code O ID 2/3 Code identifying the country Country Codes for North America: US United States of America (USA) CA Canada (CAN) MX Mexico (MEX) Not Used N405 309 Not Used N406 310 BluJay Solutions The country codes will need to follow the ISO-3166 2/3 character country code abbreviations standards. (https://www.iso.org/iso-3166-country-codes.html) Location Qualifier X ID 1/2 Refer to 004010 Data Element Dictionary for acceptable code values. Location Identifier O AN 1/30 Page 18
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: S5 Stop-off Details 010 0300 Optional Detail Optional 1 To specify stop-off detail reference numbers and stop reason 1 If either S503 or S504 is present, then the other is required. 2 If either S505 or S506 is present, then the other is required. 3 If either S507 or S508 is present, then the other is required. 1 S509 is the stop reason description. The S5 Stop-off Detail Loop is used to specify the Actual Dates at a Stop Location. It is recommended that the S5 Stop-off Detail Loops be included. Note that the N1 ”SF” (Ship From) / N1 “ST” (Ship To) Loops and their associated G62 Segment may be required by your Shipper per BluJay TMS Invoice Validation Profile “Location Data”, “Ship Date”, or “Delivery Date” settings. M Ref. Des. S501 M S502 Not Used Not Used S503 S504 Not Used Not Used S505 S506 Not Used Not Used S507 S508 Not Used Not Used Not Used S509 S510 S511 BluJay Solutions Data Element Summary Data Element Name Attributes 165 Stop Sequence Number M N0 1/3 Identifying number for the specific stop and the sequence in which the stop is to be performed 163 Stop Reason Code M ID 2/2 Code specifying the reason for the stop LD Load UL Unload 81 Weight X R 1/10 188 Weight Unit Code X ID 1/1 Refer to 004010 Data Element Dictionary for acceptable code values. 382 Number of Units Shipped X R 1/10 355 Unit or Basis for Measurement Code X ID 2/2 Refer to 004010 Data Element Dictionary for acceptable code values. 183 Volume X R 1/8 184 Volume Unit Qualifier X ID 1/1 Refer to 004010 Data Element Dictionary for acceptable code values. 352 Description O AN 1/80 154 Standard Point Location Code O ID 6/9 190 Accomplish Code O ID 1/1 Refer to 004010 Data Element Dictionary for acceptable code values. Page 19
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: Ref. Des. G6201 G6202 G6203 G6204 G6205 BluJay Solutions G62 Date/Time 030 0300 Optional Detail Optional 10 To specify pertinent dates and times 1 At least one of G6201 or G6203 is required. 2 If either G6201 or G6202 is present, then the other is required. 3 If either G6203 or G6204 is present, then the other is required. May be required by your Shipper per BluJay TMS Invoice Validation Profile “Ship Date” and/or “Delivery Date” settings. Data Element Summary Data Element Name Attributes 432 Date Qualifier X ID 2/2 Code specifying type of date 35 Delivered on This Date 86 Actual Pickup Date 373 Date X DT 8/8 Date expressed as CCYYMMDD 176 Time Qualifier X ID 1/2 Code specifying the reported time 8 Actual Pickup Time 9 Actual Delivery Time 337 Time X TM 4/8 Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (0059), S integer seconds (00-59) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9) and DD hundredths (00-99) 623 Time Code O ID 2/2 Code identifying the time. In accordance with International Standards Organization standard 8601, time can be specified by a or - and an indication in hours in relation to Universal Time Coordinate (UTC) time; since is a restricted character, and - are substituted by P and M in the codes that follow Any valid code may be placed in this element CD Central Daylight Time CT Central Time ED Eastern Daylight Time ET Eastern Time MD Mountain Daylight Time MT Mountain Time PD Pacific Daylight Time PT Pacific Time Page 20
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: M Ref. Des. N101 N1 Name 050 0310 Optional Detail Optional 1 To identify a party by type of organization, name, and code 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 2 N105 and N106 further define the type of entity in N101. May be required by your Shipper per BluJay TMS Invoice Validation Profile “Location Data” settings. Data Element Summary Data Element Name Attributes 98 Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual SF Ship From Required for Actual Pickup Status ST Used to determine which Stop Location to apply the G62 Date/Time information. See X12 204 Load Tender N1 “SF” Loop information. Ship To Required for Actual Delivery Status Used to determine which Stop Location to apply the G62 Date/Time information. See X12 204 Load Tender N1 “ST” Loop information. N102 93 N103 66 N104 67 BluJay Solutions Name X AN 1/60 Free-form name Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) ZZ Mutually Defined Identification Code X AN 2/80 Code identifying a party or other code Used for Shipper Location Reference Number Page 21
Not Used N105 706 Not Used N106 98 BluJay Solutions Entity Relationship Code O ID 2/2 Refer to 004010 Data Element Dictionary for acceptable code values. Entity Identifier Code O ID 2/3 Refer to 004010 Data Element Dictionary for acceptable code values. Page 22
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: M Ref. Des. N301 N302 BluJay Solutions N3 Address Information 070 0310 Optional Detail Optional 2 To specify the location of the named party This segment is required for the N1 ”SF” (Ship From) / N1 “ST” (Ship To) Loops Data Element Summary Data Element Name 166 Address Information Address information 166 Address Information Address information Attributes M AN 1/55 O AN 1/55 Page 23
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: N4 Geographic Location 080 0310 Optional Detail Optional 1 To specify the geographic place of the named party 1 If N406 is present, then N405 is required. 1 2 Ref. Des. N401 N402 N403 N404 A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. N402 is required only if city name (N401) is in the U.S. or Canada. Data Element Summary Data Element Name Attributes 19 City Name O AN 2/30 Free-form text for city name 156 State or Province Code O ID 2/2 Code (Standard State/Province) as defined by appropriate government agency 116 Postal Code O ID 3/15 Code defining international postal zone code excluding punctuation and blanks (zip code for United States) 26 Country Code O ID 2/3 Code identifying the country Country Codes for North America: US United States of America (USA) CA Canada (CAN) MX Mexico (MEX) Not Used N405 309 Not Used N406 310 BluJay Solutions The country codes will need to follow the ISO-3166 2/3 character country code abbreviations standards. (https://www.iso.org/iso-3166-country-codes.html) Location Qualifier X ID 1/2 Refer to 004010 Data Element Dictionary for acceptable code values. Location Identifier O AN 1/30 Page 24
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: M Ref. Des. LX01 BluJay Solutions LX Assigned Number 120 0400 Optional Detail Optional 1 To reference a line number in a transaction set Data Element Summary Data Element Name 554 Assigned Number Number assigned for differentiation within a transaction set Attributes M N0 1/6 Page 25
Segment: Position: Loop: Level: Usage: Max Use: Purpose: Syntax Notes: Semantic Notes: Comments: Notes: L0 Line Item - Quantity and Weight 170 0400 Optional Detail Optional 10 To specify quantity, weight, volume, and type of service for a line item including applicable "quantity/rate-as" data 1 If either L002 or L003 is present, then the other is required. 2 If either L004 or L005 is present, then the other is required. 3 If either L006 or L007 is present, then the other is required. 4 If either L008 or L009 is present, then the other is required. 5 If L011 is present, then L004 is required. 6 If either L013 or L015 is present, then the other is required. 1 L008 is the number of handling units of the line item tendered to the carrier. 2 L013 can only be used if the code in L009 is PLT, SKD, or SLP. 3 L015 designates whether the carrier will be required to verify the number of units contained on a pallet, slip sheet or skid. Code "Y" indicates that the carrier will be required to verify. Code "N" indicates that the carrier will not be required to verify. 1 L013 is used to convey the total number of boxes, cartons, or pieces contained on a pallet, skid, or slip sheet for the line item. This segment is used to indicate the Invoice Line Detail Rated Quantity, Lading Quantity and Weight Information. It is recommended to include an L0 segment. The L0 segment is required whenever the L103 Freight Rate UM is Per Mile (PM) or Per Hundred Weight (CW). Note that only one L0 segment should be included per LX Loop. Not Used Ref. Des. L001 L
U U.S. EDI Community of ASC X12, TDCC, and UCS M ISA12 I11 Interchange Control Version Number M ID 5/5 This version number covers the interchange control segments 00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997 M ISA13 I12 Interchange Control Number M N0 9/9
4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 –Advance Ship Notice EDI 810 - Invoice EDI 860 –PO Change Request EDI 846 - Inventory Advice/Update EDI 865 –PO Change Seller
collection of EDI data is received in a batch. The batch of EDI data includes a plurality of EDI documents and each of the plurality of EDI documents has at least one EDI transaction corresponding to a transaction type. The EDI transactions included in the EDI documents are identified by decoding the received EDI data according to EDI standards.
4010 EDI documents (note EDIFACT transaction sets will be required by Amazon EU divisions): EDI 753 - Request for Routing Instructions EDI 855 - PO Acknowledgement EDI 754 - Routing Instructions EDI 856 – Advance Ship Notice EDI 810 - Invoice EDI 860 – PO Change Request
1. What is EDI? 2. What is the 'Omni-hannel' 3. Omni-Channel EDI solutions 4. Where does EDI fit into the marketplace? 5. Third Party Logistics (3PL) EDI 6. Online Retailers and CommerceHub EDI 7. eCommerce Platform EDI 8. B2BGateway EDI and QuickBooks Online 9. Pricing 10. Customer Service 11. B2BGateway Fact Sheet & Trading Partners 12 .
MAPPING Involves transforming an EDI document into another format (such as XML, a flat file, a delimited file, etc.) TRANSLATION The process of accepting in bound EDI data, or preparing an outbound file for transmission COMMUNICATIONS Refers to the transmission of the EDI transaction Accepted. The EDI message conforms to all agreed upon EDI .
TrueCommerce EDI Buyer's Guide As supply chains become more complex, EDI offers the technology . and provides all the components required for EDI, such as mapping, translation, and connectivity to trading partners. . h EDI 940 - Warehouse Shipping Order h EDI 945 - Warehouse Shipping Advice h EDI 997 - Functional Acknowledgement
EDI Notepad EDI Notepad is the ultimate EDI editor, providing all those clever features you've always wanted when working with EDI transactions. These features include several viewing modes, syntax validation for all EDI standards and versions, edit tools to edit or build EDI documents,
AngularJS, and honestly, I cannot imagine writing this same application using another kind of technology in this short period of time. I was so excited about it that I wrote an article on using AngularJS with Spring MVC and Hibernate for a magazine called Java Magazine. After that, I created an AngularJS training program that already has more than 200 developers who enrolled last year. This .
