ECGrid Simplify
Canonical Request for Routing Instructions 753 Format Specification
Version: 1.0 Date: June 2026 Owner: ECGrid Product
1. Purpose
This document defines the canonical Request for Routing Instructions format used by ECGrid Simplify. It is the single source of truth for document structure, field definitions, data types, required fields, and serialisation rules across XML and JSON.
Both XML and JSON representations convey the same logical Request for Routing Instructions message. The 753 transaction set is a shipper's request to a carrier for routing information, specifying order details, ship-from/ship-to parties, and requested pickup dates.
Direction Note: The Canonical Request for Routing Instructions flows outbound from ECGrid to the carrier or logistics provider. ECGrid receives the shipper's order data and translates it into X12 753 EDI, which maps to this canonical format for delivery to the carrier's system.
2. Scope
In scope:
- Request for Routing Instructions document structure (envelope, header, party blocks, and line items).
- Field-level definitions, data types, required fields, and EDI source mapping.
- Canonical XML and JSON representations.
- Party identification (ShipFrom, ShipTo, BillTo at header and OrderShipFrom, OrderShipTo at line level).
Out of scope:
- Transport (HTTPS, AS2, SFTP). Covered in ECGrid Simplify API docs.
- Functional acknowledgments and application responses.
- X12 753 EDI mapping rules. See Map_ANSI X12 753 004010 To Simplify XML Request for Routing Instructions 753 - Global.csv.
- Routing Instructions response (754). Covered in ECGrid_Simplify_754_Spec.docx.
3. Document Structure
A canonical Request for Routing Instructions payload contains a RequestForRoutingInstructionsMessage root element with exactly one RequestForRoutingInstructions child. The child holds all header fields from the BGN and PER segments, three header-level party blocks (ShipFrom, ShipTo, BillTo), and one or more LineItem entries from the LX loop. Each LineItem may also contain line-level party blocks (OrderShipFrom, OrderShipTo).
XML vs JSON Naming: Both XML and JSON use PascalCase field names throughout. The JSON root key is "RequestForRoutingInstructionsMessage" — matching the XML root element exactly.
Top-level shape:
RequestForRoutingInstructionsMessage
└── RequestForRoutingInstructions (required, exactly one)
├── TradingPartnerId / Sender / Receiver … (envelope fields, ISA/GS)
├── TransactionSetPurposeCode / ReferenceNumber … (header, BGN)
├── ContactName / ContactPhone … (contact, PER)
├── ShipFrom (party block, N1/SF)
├── ShipTo (party block, N1/ST)
├── BillTo (party block, N1/BT)
└── LineItem (1..n, one per LX loop)
├── LineItemNumber / AgencyQualifier / ServiceCode …
├── PurchaseOrderNumber / OrderQuantity … (OID inside LoopOID)
├── OrderShipFrom (line party, LoopN1/SF)
└── OrderShipTo (line party, LoopN1/ST)
3.1 Comparison with the Canonical Routing Instructions (754)
Aspect | Canonical Request for Routing Instr. (753) | Canonical Routing Instructions (754) |
Root element | <RequestForRoutingInstructionsMessage> / <RequestForRoutingInstructions> | <RoutingInstructionsMessage> / <RoutingInstructions> |
Transaction | 753 | 754 |
GS-01 code | RF | GF |
Direction | Outbound — shipper requests routing from carrier | Inbound — carrier responds with confirmed routing |
JSON root key | "RequestForRoutingInstructionsMessage" | "RoutingInstructionsMessage" |
Header segment | BGN: purpose, reference, RequestDate, RequestTime, timezone, action | BGN: same fields; RoutingDate instead of RequestDate |
Carrier field | None (carrier not yet assigned) | BLR: StandardCarrierAlphaCode + PickupDate (confirmed) |
Service info segment | USI: AgencyQualifier, ServiceCode, ServiceAmount | Not present in standard 754 mapping |
Quantity segment | Not present in standard 753 mapping | QTY in LoopQTY: QuantityQualifier (38=Confirmed) + Quantity |
Order detail segment | OID inside LoopOID (nested in LoopLX) | OID directly in LoopLX (not nested) |
Header party types | ShipFrom, ShipTo, BillTo | ShipFrom, ShipTo |
Line party types | OrderShipFrom, OrderShipTo (LoopLX/LoopN1) | OrderShipFrom, OrderShipTo (LoopLX/LoopN1) |
4. Envelope Fields
Sourced from ISA (interchange) and GS (functional group) segments.
ISA fixed-width: ISA-06 (Sender) and ISA-08 (Receiver) are 15-character fixed-width fields padded with trailing spaces. ECGrid always trims before populating TradingPartnerId, Sender, and Receiver.
XML Element | JSON Property | Req | Description |
TradingPartnerId | TradingPartnerId | Yes | ISA-06 — ECGrid trading partner identifier. 15-char fixed-width; always trimmed. |
Sender | Sender | Yes | ISA-06 — Interchange sender identifier value. Trimmed. |
SenderQualifier | SenderQualifier | Yes | ISA-05 — Qualifies the sender identifier type (e.g. 01=DUNS, ZZ=Mutually Defined). |
Receiver | Receiver | Yes | ISA-08 — Interchange receiver identifier value. Trimmed. |
ReceiverQualifier | ReceiverQualifier | Yes | ISA-07 — Qualifies the receiver identifier type. |
InterchangeDate | InterchangeDate | Yes | ISA-09 — Interchange date. YYMMDD format. |
InterchangeControlNumber | InterchangeControlNumber | Yes | ISA-13 — Interchange control number. |
TestProductionIndicator | TestProductionIndicator | Yes | ISA-15 — T=Test, P=Production. |
GroupFunctionCode | GroupFunctionCode | Yes | GS-01 — Functional identifier code (RF=Request for Routing Instructions). |
5. Header Fields
Sourced from BGN (request header) and PER (contact information) segments.
Contact phone/email extraction: PER-03 is the qualifier: TE=Telephone, EM=Email. If PER-03=TE then ContactPhone=PER-04; if PER-05=TE then ContactPhone=PER-06. Same pattern applies for ContactEmail with qualifier EM.
XML Element | JSON Property | Req | Description |
TransactionSetPurposeCode | TransactionSetPurposeCode | Yes | BGN-01 — Transaction set purpose code. 00=Original, 05=Replace, 01=Cancellation. |
ReferenceNumber | ReferenceNumber | Yes | BGN-02 — Unique reference number assigned by the shipper for this routing request. |
RequestDate | RequestDate | Yes | BGN-03 — Date the routing request was created. YYYYMMDD format. |
RequestTime | RequestTime | No | BGN-04 — Time the routing request was created. HHMM format. |
TimeZoneCode | TimeZoneCode | No | BGN-05 — Time zone designator code (e.g. ET=Eastern, CT=Central). |
ActionCode | ActionCode | No | BGN-06 — Action code qualifier. |
ContactFunctionCode | ContactFunctionCode | No | PER-01 — Contact function code (e.g. CN=General Contact). |
ContactName | ContactName | No | PER-02 — Contact person or department name. |
ContactPhone | ContactPhone | No | PER-04 (PER-03=TE) — Contact phone number. Extracted when PER-03 qualifier is TE. |
ContactEmail | ContactEmail | No | PER-04 (PER-03=EM) — Contact email address. Extracted when PER-03 qualifier is EM. |
6. Party Address Blocks (N1 Loop)
Header-level party blocks are extracted from the N1 loop appearing before the LX loop. N1-01 qualifier routes data: SF=ShipFrom, ST=ShipTo, BT=BillTo. Absent loops are silently skipped; all fields output as empty string.
N1 Loop Qualifier Routing: SF=ShipFrom (origin/pickup), ST=ShipTo (destination/delivery), BT=BillTo (billing party). Absent loops are silently skipped.
6.1 ShipFrom (N1-01 = SF)
XML Element | JSON Property | Req | Description |
PartyIdentification | PartyIdentification | No | N1-04 — Party identifier value (e.g. account number, location code). |
PartyIdentificationType | PartyIdentificationType | No | N1-03 — Code qualifying the identifier type (e.g. 91=Assigned by Seller). |
Name | Name | Yes | N1-02 — Party legal or trading name. |
AdditionalName | AdditionalName | No | N2-01 — Additional name line. |
StreetAddress1 | StreetAddress1 | No | N3-01 — Primary street address line. |
StreetAddress2 | StreetAddress2 | No | N3-02 — Secondary address line (suite, unit, etc.). |
City | City | No | N4-01 — City name. |
StateCode | StateCode | No | N4-02 — Two-letter state or province code. |
PostalCode | PostalCode | No | N4-03 — Postal / ZIP code. |
CountryCode | CountryCode | No | N4-04 — ISO 3166-1 alpha-2 country code (e.g. US). |
6.2 ShipTo (N1-01 = ST)
XML Element | JSON Property | Req | Description |
PartyIdentification | PartyIdentification | No | N1-04 — Party identifier value (e.g. account number, location code). |
PartyIdentificationType | PartyIdentificationType | No | N1-03 — Code qualifying the identifier type (e.g. 91=Assigned by Seller). |
Name | Name | Yes | N1-02 — Party legal or trading name. |
AdditionalName | AdditionalName | No | N2-01 — Additional name line. |
StreetAddress1 | StreetAddress1 | No | N3-01 — Primary street address line. |
StreetAddress2 | StreetAddress2 | No | N3-02 — Secondary address line (suite, unit, etc.). |
City | City | No | N4-01 — City name. |
StateCode | StateCode | No | N4-02 — Two-letter state or province code. |
PostalCode | PostalCode | No | N4-03 — Postal / ZIP code. |
CountryCode | CountryCode | No | N4-04 — ISO 3166-1 alpha-2 country code (e.g. US). |
6.3 BillTo (N1-01 = BT)
XML Element | JSON Property | Req | Description |
PartyIdentification | PartyIdentification | No | N1-04 — Party identifier value (e.g. account number, location code). |
PartyIdentificationType | PartyIdentificationType | No | N1-03 — Code qualifying the identifier type (e.g. 91=Assigned by Seller). |
Name | Name | Yes | N1-02 — Party legal or trading name. |
AdditionalName | AdditionalName | No | N2-01 — Additional name line. |
StreetAddress1 | StreetAddress1 | No | N3-01 — Primary street address line. |
StreetAddress2 | StreetAddress2 | No | N3-02 — Secondary address line (suite, unit, etc.). |
City | City | No | N4-01 — City name. |
StateCode | StateCode | No | N4-02 — Two-letter state or province code. |
PostalCode | PostalCode | No | N4-03 — Postal / ZIP code. |
CountryCode | CountryCode | No | N4-04 — ISO 3166-1 alpha-2 country code (e.g. US). |
7. Line Item Fields (LoopLX)
The LineItem element repeats for each LX loop. Within each loop: LX (line number), LoopN1 (line-level parties), L11 (reference), G62 (date/time), USI (service info), and LoopOID containing OID (order details) and CMC (commodity).
Segment order in LoopLX: Within LoopLX the order is: LX → LoopN1 (N1/N3/N4) → L11 → G62 → USI → LoopOID (OID + CMC). L11, G62, and USI appear after LoopN1 closes.
OID position: In the 753 structure OID is nested inside LoopOID (inside LoopLX). This differs from the 754 structure where OID is a direct child of LoopLX.
CMC segment: CMC (Commodity) is optional and appears inside LoopOID after OID. CMC-01=CommodityCodeQualifier, CMC-02=CommodityCode, CMC-03=CommodityCodeQualifier2.
XML Element | JSON Property | Req | Description |
LineItemNumber | LineItemNumber | Yes | LX-01 — Line item sequence number. |
ReferenceIdentification | ReferenceIdentification | No | L11-01 — Reference identification value (e.g. PO number, BOL number). |
ReferenceQualifier | ReferenceQualifier | No | L11-02 — Qualifier for the reference identification (e.g. PO=Purchase Order). |
FreeFormDescription | FreeFormDescription | No | L11-03 — Free-form description associated with the reference. |
DateQualifier | DateQualifier | No | G62-01 — Date qualifier code (e.g. 11=Ship Date, 10=Pickup Date). |
Date | Date | No | G62-02 — Date value associated with DateQualifier. YYYYMMDD format. |
TimeCode | TimeCode | No | G62-03 — Time zone code for the date/time. |
Time | Time | No | G62-04 — Time value associated with the date. HHMM format. |
AgencyQualifier | AgencyQualifier | No | USI-01 — Agency qualifier code identifying the service standard. |
ServiceCode | ServiceCode | No | USI-02 — Service or carrier code per the agency qualifier. |
ServiceAmount | ServiceAmount | No | USI-03 — Monetary amount associated with the service. |
PurchaseOrderNumber | PurchaseOrderNumber | No | OID-02 — Purchase order number. |
ReleaseNumber | ReleaseNumber | No | OID-03 — Release number against the purchase order. |
UnitOrBasisForMeasurementCode | UnitOrBasisForMeasurementCode | No | OID-04 — Unit of measure for the ordered quantity (e.g. EA, CAS, PLT). |
OrderQuantity | OrderQuantity | No | OID-05 — Quantity ordered on this line. |
WeightQualifier | WeightQualifier | No | OID-06 — Weight qualifier code (e.g. L=Net, G=Gross). |
Weight | Weight | No | OID-07 — Shipment weight value. |
VolumeUnitQualifier | VolumeUnitQualifier | No | OID-08 — Volume unit qualifier code. |
Volume | Volume | No | OID-09 — Volume measurement value. |
OrderSizingFactor | OrderSizingFactor | No | OID-10 — Order sizing factor. |
PriceBracketIdentifier | PriceBracketIdentifier | No | OID-11 — Price bracket identifier. |
CommodityCodeQualifier | CommodityCodeQualifier | No | CMC-01 — Commodity code qualifier (CMC segment inside LoopOID). |
CommodityCode | CommodityCode | No | CMC-02 — Commodity code value. |
CommodityCodeQualifier2 | CommodityCodeQualifier2 | No | CMC-03 — Secondary commodity code qualifier. |
7.1 Line-Level Party Blocks (LoopLX / LoopN1)
Each LineItem may contain line-level party blocks from the N1 loop inside LoopLX. These use the same 10-field structure as header parties.
OrderShipFrom
Ship-from party at the line level. Extracted from LoopLX/LoopN1 (N1-01=SF).
XML Element | JSON Property | Req | Description |
PartyIdentification | PartyIdentification | No | N1-04 — Party identifier value (e.g. account number, location code). |
PartyIdentificationType | PartyIdentificationType | No | N1-03 — Code qualifying the identifier type (e.g. 91=Assigned by Seller). |
Name | Name | Yes | N1-02 — Party legal or trading name. |
AdditionalName | AdditionalName | No | N2-01 — Additional name line. |
StreetAddress1 | StreetAddress1 | No | N3-01 — Primary street address line. |
StreetAddress2 | StreetAddress2 | No | N3-02 — Secondary address line (suite, unit, etc.). |
City | City | No | N4-01 — City name. |
StateCode | StateCode | No | N4-02 — Two-letter state or province code. |
PostalCode | PostalCode | No | N4-03 — Postal / ZIP code. |
CountryCode | CountryCode | No | N4-04 — ISO 3166-1 alpha-2 country code (e.g. US). |
OrderShipTo
Ship-to party at the line level. Extracted from LoopLX/LoopN1 (N1-01=ST).
XML Element | JSON Property | Req | Description |
PartyIdentification | PartyIdentification | No | N1-04 — Party identifier value (e.g. account number, location code). |
PartyIdentificationType | PartyIdentificationType | No | N1-03 — Code qualifying the identifier type (e.g. 91=Assigned by Seller). |
Name | Name | Yes | N1-02 — Party legal or trading name. |
AdditionalName | AdditionalName | No | N2-01 — Additional name line. |
StreetAddress1 | StreetAddress1 | No | N3-01 — Primary street address line. |
StreetAddress2 | StreetAddress2 | No | N3-02 — Secondary address line (suite, unit, etc.). |
City | City | No | N4-01 — City name. |
StateCode | StateCode | No | N4-02 — Two-letter state or province code. |
PostalCode | PostalCode | No | N4-03 — Postal / ZIP code. |
CountryCode | CountryCode | No | N4-04 — ISO 3166-1 alpha-2 country code (e.g. US). |
8. Naming Conventions
Both XML and JSON use PascalCase field names throughout (e.g. RequestDate, PurchaseOrderNumber, LineItem). XML and JSON field names are identical.
The JSON root key is "RequestForRoutingInstructionsMessage" — matching the XML root element exactly.
Empty optional values: XML: <FieldName></FieldName>. JSON: "FieldName": "". Every field is always present in the output even when absent from the EDI.
All values are strings: All canonical values are typed as string — including numeric-looking fields such as OrderQuantity, Weight, Volume, and LineItemNumber.
9. Validation Rules
Rule | Detail |
Required fields | TradingPartnerId, SenderQualifier, Sender, ReceiverQualifier, Receiver, GroupFunctionCode, TransactionSetPurposeCode, ReferenceNumber, RequestDate, and LineItemNumber (per LineItem) are always populated from the EDI. |
Missing fields | Every field in the canonical structure is always present — no fields are omitted even when absent from the EDI. |
ISA trimming | ISA-06 and ISA-08 are 15-character fixed-width; always trim trailing spaces. |
Contact extraction | ContactPhone and ContactEmail are extracted by scanning PER-03 and PER-05 for qualifiers TE (telephone) and EM (email) respectively. |
OID path | OID is nested inside LoopOID (inside LoopLX). Source path: LoopLX/LoopOID/OID/OID02. This differs from 754 where OID is a direct child of LoopLX. |
L11 position | L11, G62, and USI appear after LoopN1 closes within LoopLX. They are direct children of LoopLX, not inside LoopN1. |
Party qualifier | Header parties: SF=ShipFrom, ST=ShipTo, BT=BillTo. Line parties (LoopLX/LoopN1): SF=OrderShipFrom, ST=OrderShipTo. |
Weight fields | OID-06=WeightQualifier (qualifier code, e.g. L=Net), OID-07=Weight (value). OID-08=VolumeUnitQualifier, OID-09=Volume. |
G62 date qualifiers | 11=Ship Date, 10=Pickup Date. Additional qualifiers pass through in DateQualifier. |
Multiple transactions | Multiple ST…SE blocks produce separate RequestForRoutingInstructions elements (XML) or array entries (JSON). |
10. XML Example
Canonical 753 Request for Routing Instructions in XML format. Empty tags represent optional fields not present in the source EDI.
<?xml version="1.0" encoding="UTF-8"?>
<RequestForRoutingInstructionsMessage>
<RequestForRoutingInstructions>
<TradingPartnerId>112084681</TradingPartnerId>
<Sender>112084681</Sender>
<SenderQualifier>01</SenderQualifier>
<Receiver>609195581</Receiver>
<ReceiverQualifier>01</ReceiverQualifier>
<InterchangeDate>260609</InterchangeDate>
<InterchangeControlNumber>000000753</InterchangeControlNumber>
<TestProductionIndicator>P</TestProductionIndicator>
<GroupFunctionCode>RF</GroupFunctionCode>
<TransactionSetPurposeCode>00</TransactionSetPurposeCode>
<ReferenceNumber>REQ-2026-060901</ReferenceNumber>
<RequestDate>20260609</RequestDate>
<RequestTime>1511</RequestTime>
<TimeZoneCode></TimeZoneCode>
<ActionCode></ActionCode>
<ContactFunctionCode>CN</ContactFunctionCode>
<ContactName>John Smith</ContactName>
<ContactPhone>5551234567</ContactPhone>
<ContactEmail>john@acme.com</ContactEmail>
<ShipFrom>
<PartyIdentification>ACME-PLANT-05</PartyIdentification>
<PartyIdentificationType>91</PartyIdentificationType>
<Name>ACME Manufacturing Corp</Name>
<AdditionalName></AdditionalName>
<StreetAddress1>1000 Industrial Pkwy</StreetAddress1>
<StreetAddress2></StreetAddress2>
<City>Columbus</City>
<StateCode>OH</StateCode>
<PostalCode>43204</PostalCode>
<CountryCode>US</CountryCode>
</ShipFrom>
<ShipTo>
<PartyIdentification></PartyIdentification>
<PartyIdentificationType></PartyIdentificationType>
<Name></Name>
<AdditionalName></AdditionalName>
<StreetAddress1></StreetAddress1>
<StreetAddress2></StreetAddress2>
<City></City>
<StateCode></StateCode>
<PostalCode></PostalCode>
<CountryCode></CountryCode>
</ShipTo>
<BillTo>
<PartyIdentification></PartyIdentification>
<PartyIdentificationType></PartyIdentificationType>
<Name></Name>
<AdditionalName></AdditionalName>
<StreetAddress1></StreetAddress1>
<StreetAddress2></StreetAddress2>
<City></City>
<StateCode></StateCode>
<PostalCode></PostalCode>
<CountryCode></CountryCode>
</BillTo>
<LineItem>
<LineItemNumber>1</LineItemNumber>
<ReferenceIdentification>REF-001</ReferenceIdentification>
<ReferenceQualifier>PO</ReferenceQualifier>
<FreeFormDescription></FreeFormDescription>
<DateQualifier>11</DateQualifier>
<Date>20260615</Date>
<TimeCode></TimeCode>
<Time></Time>
<AgencyQualifier>01</AgencyQualifier>
<ServiceCode>BX</ServiceCode>
<ServiceAmount></ServiceAmount>
<PurchaseOrderNumber>PO-2026-0001</PurchaseOrderNumber>
<ReleaseNumber></ReleaseNumber>
<UnitOrBasisForMeasurementCode>CAS</UnitOrBasisForMeasurementCode>
<OrderQuantity>100</OrderQuantity>
<WeightQualifier>L</WeightQualifier>
<Weight>100</Weight>
<VolumeUnitQualifier>C</VolumeUnitQualifier>
<Volume>100</Volume>
<OrderSizingFactor></OrderSizingFactor>
<PriceBracketIdentifier></PriceBracketIdentifier>
<CommodityCodeQualifier></CommodityCodeQualifier>
<CommodityCode></CommodityCode>
<CommodityCodeQualifier2></CommodityCodeQualifier2>
<OrderShipFrom>
<PartyIdentification></PartyIdentification>
<PartyIdentificationType></PartyIdentificationType>
<Name></Name>
<AdditionalName></AdditionalName>
<StreetAddress1></StreetAddress1>
<StreetAddress2></StreetAddress2>
<City></City>
<StateCode></StateCode>
<PostalCode></PostalCode>
<CountryCode></CountryCode>
</OrderShipFrom>
<OrderShipTo>
<PartyIdentification>ACME-PLANT-05</PartyIdentification>
<PartyIdentificationType>91</PartyIdentificationType>
<Name>ACME Manufacturing Corp</Name>
<AdditionalName></AdditionalName>
<StreetAddress1>1000 Industrial Pkwy</StreetAddress1>
<StreetAddress2></StreetAddress2>
<City>Columbus</City>
<StateCode>OH</StateCode>
<PostalCode>43204</PostalCode>
<CountryCode>US</CountryCode>
</OrderShipTo>
</LineItem>
</RequestForRoutingInstructions>
</RequestForRoutingInstructionsMessage>
11. JSON Example
The same canonical 753 Request for Routing Instructions in JSON format. Empty string ("") represents optional fields not present in the source EDI.
{
"RequestForRoutingInstructionsMessage": {
"RequestForRoutingInstructions": {
"TradingPartnerId": "112084681",
"Sender": "112084681",
"SenderQualifier": "01",
"Receiver": "609195581",
"ReceiverQualifier": "01",
"InterchangeDate": "260609",
"InterchangeControlNumber": "000000753",
"TestProductionIndicator": "P",
"GroupFunctionCode": "RF",
"TransactionSetPurposeCode": "00",
"ReferenceNumber": "REQ-2026-060901",
"RequestDate": "20260609",
"RequestTime": "1511",
"TimeZoneCode": "",
"ActionCode": "",
"ContactFunctionCode": "CN",
"ContactName": "John Smith",
"ContactPhone": "5551234567",
"ContactEmail": "john@acme.com",
"ShipFrom": {
"PartyIdentification": "ACME-PLANT-05",
"PartyIdentificationType": "91",
"Name": "ACME Manufacturing Corp",
"AdditionalName": "",
"StreetAddress1": "1000 Industrial Pkwy",
"StreetAddress2": "",
"City": "Columbus",
"StateCode": "OH",
"PostalCode": "43204",
"CountryCode": "US"
},
"ShipTo": {
"PartyIdentification": "",
"PartyIdentificationType": "",
"Name": "",
"AdditionalName": "",
"StreetAddress1": "",
"StreetAddress2": "",
"City": "",
"StateCode": "",
"PostalCode": "",
"CountryCode": ""
},
"BillTo": {
"PartyIdentification": "",
"PartyIdentificationType": "",
"Name": "",
"AdditionalName": "",
"StreetAddress1": "",
"StreetAddress2": "",
"City": "",
"StateCode": "",
"PostalCode": "",
"CountryCode": ""
},
"LineItem": [
{
"LineItemNumber": "1",
"ReferenceIdentification": "REF-001",
"ReferenceQualifier": "PO",
"FreeFormDescription": "",
"DateQualifier": "11",
"Date": "20260615",
"TimeCode": "",
"Time": "",
"AgencyQualifier": "01",
"ServiceCode": "BX",
"ServiceAmount": "",
"PurchaseOrderNumber": "PO-2026-0001",
"ReleaseNumber": "",
"UnitOrBasisForMeasurementCode": "CAS",
"OrderQuantity": "100",
"WeightQualifier": "L",
"Weight": "100",
"VolumeUnitQualifier": "C",
"Volume": "100",
"OrderSizingFactor": "",
"PriceBracketIdentifier": "",
"CommodityCodeQualifier": "",
"CommodityCode": "",
"CommodityCodeQualifier2": "",
"OrderShipFrom": {
"PartyIdentification": "",
"PartyIdentificationType": "",
"Name": "",
"AdditionalName": "",
"StreetAddress1": "",
"StreetAddress2": "",
"City": "",
"StateCode": "",
"PostalCode": "",
"CountryCode": ""
},
"OrderShipTo": {
"PartyIdentification": "ACME-PLANT-05",
"PartyIdentificationType": "91",
"Name": "ACME Manufacturing Corp",
"AdditionalName": "",
"StreetAddress1": "1000 Industrial Pkwy",
"StreetAddress2": "",
"City": "Columbus",
"StateCode": "OH",
"PostalCode": "43204",
"CountryCode": "US"
}
}
]
}
}
}
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article