implementation guidelines for ansi asc x12 edi … documents... · fca us - mopar order status...

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS

MOPAR – FROM SUPPLIER

ORDER STATUS REPORT (870) TRANSACTION SET

FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 003030

FCA US - Mopar Order Status Report (from supplier)

870 Order Status Report

Functional Group ID=RS

Introduction:

This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/services on a purchase order, or purchase orders for a specific customer in their entirety or on a selection basis. The transaction set can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This transaction set may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners.

Notes:

FCA will use the Order Status Report to receive daily notification of material unavailable for shipment from a distributor.

Notes about the new format of this implementation guide:

1. The requirements contained herein have not changed, with the exception of anything that may appear in the History of Change section below.2. The term 'Base Status' refers to the requirements as defined by the ASC X12 Standards Organization.3. The terms 'User Status' and 'User Attributes' refer to FCA requirements.4. Data segment sequence tables for each hierarchical level will no longer be presented at the beginning of each transaction section. The data segment sequence tables for each hierarchical level will now be presented at the beginning. 5. Segment Syntax and Semantic notes as defined by ASC X12 will now be included where in the 'old' format they were not. 6. Element Description as defined by ASC X12 will now be included where in the 'old' format they were not. 7. Many comments that relate to a particular code value will now appear underneath the code value description, where previously the comments would appear to the right.

History of Change:

05/2009:Update of document format; transition to Chrysler LLC with removal of references to Daimler

09/24/2010:Name change from Chrysler LLC to ChryslerUpdated Address

11/10/2014:Detail - PID05 & ISR01 Updated Notes Example - Updated

07/23/2015 V/R 003030 1 FCA US


07/23/2015:Name Change To FCA US

Heading:

Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments5 010 ST Transaction Set Header M M 1

6 020 BSR Beginning Segment for Order Status Report

M M 1

030 NTE Note/Special Instruction O Not Used 100

040 REF Reference Numbers O Not Used 12

LOOP ID - N1 200

8 050 N1 Name O 1

060 N2 Additional Name Information O Not Used 2

070 N3 Address Information O Not Used 2

080 N4 Geographic Location O Not Used 1


100 PER Administrative Communications Contact

O Not Used 3

105 PWK Paperwork O Not Used 1

110 DTM Date/Time/Period O Not Used 10

LOOP ID - LM 10

120 LM Code Source Information O Not Used 1

130 LQ Industry Code M Not Used 100

Detail:

Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments

LOOP ID - HL 1000

9 010 HL Hierarchical Level M M 1

020 PRF Purchase Order Reference O Not Used 1

LOOP ID - ISR 104

030 ISR Item Status Report O Not Used 1

040 PID Product/Item Description O Not Used 6

050 QTY Quantity O Not Used 4



O Not Used 3


086 CS Contract Summary O Not Used 3 n1

LOOP ID - N1 200

090 N1 Name O Not Used 1





07/23/2015 V/R 003030 2 FCA US



O Not Used 3

LOOP ID - LM 10



LOOP ID - PO1 1000

10 150 PO1 Baseline Item Data O 1

160 SLN Subline Item Detail O Not Used 100

170 PO3 Additional Item Detail O Not Used 1

180 PID Product/Item Description O Not Used 1000

190 MEA Measurements O Not Used 40

200 PKG Marking, Packaging, Loading O Not Used 25

LOOP ID - ISR 104

13 210 ISR Item Status Report O 1

14 220 PID Product/Item Description O 6

16 230 QTY Quantity O 4


17 250 N1 Name O 1




260 TD1 Carrier Details (Quantity and Weight) O Not Used 1

270 TD5 Carrier Details (Routing Sequence/Transit Time)

O Not Used 1

280 TD3 Carrier Details (Equipment) O Not Used 1

290 TD4 Carrier Details (Special Handling, or Hazardous Materials, or Both)

O Not Used 1


310 ITA Allowance, Charge or Service O Not Used 1

LOOP ID - LM 10



LOOP ID - LX >1

340 LX Assigned Number O Not Used 1 n2

350 REF Reference Numbers O Not Used >1

360 N1 Name O Not Used 1


LOOP ID - LM 10



Summary:

Page Pos. Seg. Base User Loop Notes and No. No. ID Name Guide Status Max.Use Repeat Comments18 010 CTT Transaction Totals M M 1 n3

19 020 SE Transaction Set Trailer M M 1

07/23/2015 V/R 003030 3 FCA US


Transaction Set Notes

1. Use is limited to intra-organizational transactions.2. The LX loop conveys serial number, lot number, and inventory data.3. The 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 quantities ordered (PO102) for each PO1 segment.

07/23/2015 V/R 003030 4 FCA US


Segment: ST Transaction Set Header

Position: 010Loop:

Level: HeadingUsage: Mandatory

Max Use: 1Purpose: To indicate the start of a transaction set and to assign a control number

Syntax Notes:Semantic Notes: 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:

Data Element SummaryRef. Data Base User Des. Element Name Attributes Attributes

ST01 143 Transaction Set Identifier Code M ID 3/3 M

Code uniquely identifying a Transaction Set

870 X12.23 Order Status Report

ST02 329 Transaction Set Control Number M AN 4/9 M

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

A unique control number assigned to each transaction set within a functional group, starting with 0001 and incrementing by 1 for each subsequent transaction set.

07/23/2015 V/R 003030 5 FCA US


Segment: BSR Beginning Segment for Order Status Report

Position: 020Loop:

Level: HeadingUsage: Mandatory

Max Use: 1Purpose: To indicate the beginning of an Order Status Report.

Syntax Notes:Semantic Notes: 1 BSR03 indicates a status report document number assigned by the sender.

2 BSR04 indicates the date of this report from the sender.3 BSR07 indicates the time of this report from the sender.4 BSR08 indicates a status report document number assigned by the inquirer.5 BSR09 indicates the date this report was requested from the sender by the

inquirer.6 BSR10 indicates the time this report was requested from the sender by the

inquirer.Comments:

Notes: This segment is used to uniquely identify this report from others that are transmitted during a year.


BSR01 850 Status Report Code M ID 1/2 M

Code indicating the reason for sending the report

3 Unsolicited Report

BSR02 847 Order/Item Code M ID 1/2 M

Code identifying a group of orders and items

AO All orders - items with changed status

BSR03 127 Reference Number M AN 1/30 M

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

A unique reference number for this transaction set that is not repeated within a 12 month period.

BSR04 373 Date M DT 6/6 M

Date (YYMMDD)

The creation date of the report.

BSR05 848 Product/Date Code O ID 1/2 Not Used

BSR06 849 Location Code O ID 1/2 Not Used

BSR07 337 Time O TM 4/6 Not Used

BSR08 127 Reference Number O AN 1/30 Not

07/23/2015 V/R 003030 6 FCA US


Used

BSR09 373 Date O DT 6/6 Not Used

BSR10 337 Time O TM 4/6 Not Used

07/23/2015 V/R 003030 7 FCA US


Segment: N1 Name

Position: 050Loop: N1 Optional

Level: HeadingUsage: Optional

Max Use: 1Purpose: To identify a party by type of organization, name, and code

Syntax Notes: 1 At least one of N102 or N103 is required.2 If either N103 or N104 is present, then the other is required.

Semantic Notes:Comments: 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.

Notes: Two N1 segments are always required in the Heading level:

'SU' for the FCA assigned supplier code for the released supplier transmitting the report.

'PK' for the FCA division or functional area who is to receive the report.


N101 98 Entity Identifier Code M ID 2/2 M

Code identifying an organizational entity, a physical location, or an individual

PK Party to Receive Copy

SU Supplier/Manufacturer

N102 93 Name X AN 1/35 Not Used

N103 66 Identification Code Qualifier M ID 1/2 M

Code designating the system/method of code structure used for Identification Code (67)

91 Assigned by Seller or Seller's Agent

N104 67 Identification Code M AN 2/17 M AN 5/7

Code identifying a party or other code

If N101 = SU, use FCA assigned supplier code for the release supplier;If N101 = PK, use '03103' for FCA Mopar Parts Division;

07/23/2015 V/R 003030 8 FCA US


Segment: HL Hierarchical Level

Position: 010Loop: HL Mandatory

Level: DetailUsage: Mandatory

Max Use: 1Purpose: To identify dependencies among and the content of hierarchically related groups of

data segmentsSyntax Notes:

Semantic Notes:Comments: 1 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.

2 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.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

4 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 item-level information.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.


HL01 628 Hierarchical ID Number M AN 1/12 M

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

For first occurence, use '1'; for each subsequent occurence, increment by 1.

HL02 734 Hierarchical Parent ID Number O AN 1/12 Not Used

HL03 735 Hierarchical Level Code M ID 1/2 M

Code defining the characteristic of a level in a hierarchical structure

O Order

HL04 736 Hierarchical Child Code O ID 1/1 Not Used

07/23/2015 V/R 003030 9 FCA US


Segment: PO1 Baseline Item Data

Position: 150Loop: PO1 Optional

Level: DetailUsage: Optional

Max Use: 1Purpose: To specify basic and most frequently used line item data

Syntax Notes: 1 If PO103 is present, then PO102 is required.2 If PO105 is present, then PO104 is required.3 If PO106 is present, then PO107 is required.4 If PO108 is present, then PO109 is required.5 If PO110 is present, then PO111 is required.6 If PO112 is present, then PO113 is required.7 If PO114 is present, then PO115 is required.8 If PO116 is present, then PO117 is required.9 If PO118 is present, then PO119 is required.10 If PO120 is present, then PO121 is required.11 If PO122 is present, then PO123 is required.12 If PO124 is present, then PO125 is required.

Semantic Notes:Comments: 1 See the Data Dictionary for a complete list of ID's.

2 PO101 is the line item identification.3 PO106 through PO125 provide for ten (10) different product/service ID's per

each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.

Notes: FCA uses the PO1 to show the quantity of material ordered for a particular FCA part number as shown in the Material Release (830). For coils, the material ordered is shown in actual pounds. For cut blanks, the material ordered is shown in pieces. Some material is ordered in theoretical pounds. Consult the FCA Material Release (830) for the ordered units.

The PO1 segment may also be used to transmit the FCA Purchase Order number for the material.


PO101 350 Assigned Identification O AN 1/11 Not Used

PO102 330 Quantity Ordered X R 1/9

Quantity ordered

The quantity of material ordered (from the Material Release).

PO103 355 Unit or Basis for Measurement Code O ID 2/2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

EA Each

07/23/2015 V/R 003030 10 FCA US


PO104 212 Unit Price X R 1/14

Price per unit of product, service, commodity, etc.

PO105 639 Basis of Unit Price Code O ID 2/2 Not Used

PO106 235 Product/Service ID Qualifier X ID 2/2 Must Use

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP Buyer's Part Number

PO107 234 Product/Service ID X AN 1/30 AN 8/10

Identifying number for a product or service

FCA Part Number from the Material Release (830)

PO108 235 Product/Service ID Qualifier O ID 2/2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

PO109 234 Product/Service ID X AN 1/30 AN 8/10

Identifying number for a product or service

The Customer Order Number from the Material Release (830)

PO110 235 Product/Service ID Qualifier O ID 2/2 Not Used

PO111 234 Product/Service ID X AN 1/30 Not Used










PO121 234 Product/Service ID X AN 1/30 Not

07/23/2015 V/R 003030 11 FCA US


Used





07/23/2015 V/R 003030 12 FCA US


Segment: ISR Item Status Report

Position: 210Loop: ISR Optional


Max Use: 1Purpose: To specify detailed purchase order/item status

Syntax Notes:Semantic Notes: 1 If ISR01 specifies a date, ISR02 is required.

Comments:Notes: ISR is used to indicate that the material described in the PO1 segment is available

for shipment and provide the date it was made available.


ISR01 368 Shipment/Order Status Code M ID 2/2 M

Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction

When ISR01= BM or BP, PID05 Must Be Filled In With Two Digit Reason Code;

BM Backordered, Manufacturer, Out-of-Stock

BP Shipment Partial, Back Order to Ship on (Date)

IC Item Canceled

ISR02 373 Date O DT 6/6

Date (YYMMDD)

If ISR01 = IC, use the date the item was cancelled by the supplier;If ISR01 = BM, use the date the item was backordered;If ISR01 = BP, use the date backordered items to be shipped;

ISR03 641 Status Reason Code O ID 3/3 Not Used

07/23/2015 V/R 003030 13 FCA US


Segment: PID Product/Item Description



Max Use: 6Purpose: To describe a product or process in coded or free-form format

Syntax Notes: 1 If PID04 is present, then PID03 is required.2 At least one of PID04 or PID05 is required.3 If PID07 is present, then PID03 is required.4 If PID08 is present, then PID03 is required.

Semantic Notes: 1 Use PID03 to indicate the organization that publishes the code list being referred to.

2 PID04 should be used for industry-specific product description codes.3 PID08 describes the physical characteristics of the product identified in PID04.

A ``Y'' indicates that the specified attribute applies to this item. A ``N'' indicates it does not apply. Any other value is indeterminate.

Comments: 1 If PID01 = ``F'', then PID05 is used. If PID01 = ``S'', then PID04 is used. If PID01 = ``X'', then both PID04 and PID05 are used.

2 Use PID06 when necessary to refer to the product surface or layer being described in the segment.

3 PID07 specifies the individual code list of the agency specified in PID03.Notes: Use PID05 to describe the item status.


PID01 349 Item Description Type M ID 1/1 M

Code indicating the format of a description

F Free-form

PID02 750 Product/Process Characteristic Code O ID 2/3 Not Used

PID03 559 Agency Qualifier Code X ID 2/2 Not Used

PID04 751 Product Description Code X AN 1/12 Not Used

PID05 352 Description X AN 1/80

A free-form description to clarify the related data elements and their content

Order Status Reason

When ISR01 = BM or BP, One Of The Following Must Be Used:Please Use First Two Digits Only

01 CARRIER RELATED ISSUE02 CUSTOMS (IMPORT / EXPORT)03 MISSING DOCUMENTS

07/23/2015 V/R 003030 14 FCA US


04 WEATHER RELATED05 CORE SHORTAGE (REMAN ONLY)06 CHANGE NOTICE / SUPERSEDENCE WRONG LEVEL ORDERED07 PURCHASING / PAYMENT ISSUE08 QUALITY ISSUE09 COMPONENT OR MATERIAL SHORTAGE10 CAPACITY CONSTRAINT11 NATURAL DISASTER12 PACKAGING NOT APPROVED13 ENGINEERING PART APPROVAL NEEDED - PPAP14 SUPPLIER TOOLING ISSUE15 OTHER

PID06 752 Surface/Layer/Position Code O ID 2/2 Not Used

PID07 822 Source Subqualifier O AN 1/15 Not Used

PID08 1073 Yes/No Condition or Response Code O ID 1/1 Not Used

07/23/2015 V/R 003030 15 FCA US


Segment: QTY Quantity



Max Use: 4Purpose: To specify quantity information

Syntax Notes:Semantic Notes:

Comments:


QTY01 673 Quantity Qualifier M ID 2/2 M

Code specifying the type of quantity

BQ Backorder Quantity

ZZ Mutually Defined

QTY02 380 Quantity M R 1/15 M

Numeric value of quantity

If QTY01 = BQ, backorder quantity;If QTY01 = ZZ, cancel quantity;

QTY03 355 Unit or Basis for Measurement Code O ID 2/2 Not Used

07/23/2015 V/R 003030 16 FCA US


Segment: N1 Name



Max Use: 1Purpose: To identify a party by type of organization, name, and code

Syntax Notes: 1 At least one of N102 or N103 is required.2 If either N103 or N104 is present, then the other is required.

Semantic Notes:Comments: 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.


N101 98 Entity Identifier Code M ID 2/2 M

Code identifying an organizational entity, a physical location, or an individual

N102 93 Name X AN 1/35 Not Used

N103 66 Identification Code Qualifier X ID 1/2 Must Use

Code designating the system/method of code structure used for Identification Code (67)

91 Assigned by Seller or Seller's Agent

N104 67 Identification Code X AN 2/17 Must Use

AN 5/8

Code identifying a party or other code

If N101 = MA, use the FCA dealer code;

07/23/2015 V/R 003030 17 FCA US


Segment: CTT Transaction Totals

Position: 010Loop:

Level: SummaryUsage: Mandatory

Max Use: 1Purpose: To transmit a hash total for a specific element in the transaction set

Syntax Notes: 1 If CTT03 is present, then CTT04 is required.2 If CTT05 is present, then CTT06 is required.

Semantic Notes:Comments: 1 This segment is intended to provide hash totals to validate transaction

completeness and correctness.Notes: This segment is intended to provide hash totals to validate transaction

completeness and correctness.


CTT01 354 Number of Line Items M N0 1/6 M

Total number of line items in the transaction set

CTT02 347 Hash Total O R 1/10 Not Used

CTT03 81 Weight O R 1/10 Not Used

CTT04 355 Unit or Basis for Measurement Code X ID 2/2 Not Used

CTT05 183 Volume O R 1/8 Not Used

CTT06 355 Unit or Basis for Measurement Code X ID 2/2 Not Used

CTT07 352 Description O AN 1/80 Not Used

07/23/2015 V/R 003030 18 FCA US


Segment: SE Transaction Set Trailer

Position: 020Loop:

Level: SummaryUsage: Mandatory

Max Use: 1Purpose: To indicate the end of the transaction set and provide the count of the transmitted

segments (including the beginning (ST) and ending (SE) segments).Syntax Notes:

Semantic Notes:Comments: 1 SE is the last segment of each transaction set.


SE01 96 Number of Included Segments M N0 1/10 M

Total number of segments included in a transaction set including ST and SE segments

SE02 329 Transaction Set Control Number M AN 4/9 M

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

07/23/2015 V/R 003030 19 FCA US

FCA US – Mopar Order Status Report (from supplier)

07/23/2015 V/R 003030 20 FCA US

Example: Service & Parts Order Cancel EDI Format Interpretation ST~870~0001 Transaction Set Identifier Code = “870” (X12.23 Order Status Report) Transaction Set Control Number = 0001 BSR~3~AO~0001~931203 Status Report Code = “3” (Unsolicited Report) Order/Item Code = “AO” (All orders - items with changed status) Reference Number = 0001 Date 12/03/1993 N1~SU~~91~12345 Entity Identifier Code = “SU” (Supplier/Manufacturer) Identification Code Qualifier = “91” (Assigned by Seller or Seller's Agent) Identification Code = 12345 N1~PK~~91~03103 Entity Identifier Code = “PK” (Party to Receive Copy) Identification Code Qualifier = “91” (Assigned by Seller or Seller's Agent) Identification Code = 03103 HL~1~~O Hierarchical ID Number = 1 Hierarchical Level Code = “O” (Order) PO1~~25~EA~~~BP~P1234567~OR~OR123456 Quantity Ordered = 25 Unit or Basis for Measurement Code = “EA” (Each) Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = P1234567 Product/Service ID Qualifier = OR Product/Service ID = OR123456 ISR~IC~931130 Shipment/Order Status Code = “IC” (Item Cancelled) Date = 11/30/1993 PID~F~~~~NO LONGER AVAILABLE Item Description Type = “F” (Free-form) Description = NO LONGER AVAILABLE QTY~ZZ~20 Quantity Qualifier = “ZZ” (Mutually Defined) Quantity = 20 N1~MA~~91~05002 Entity Identifier Code = MA Identification Code Qualifier = “91” (Assigned by Seller or Seller's Agent) Identification Code = 05002 ISR~BP~940102 Shipment/Order Status Code = “BP” (Shipment Partial, Back Order to Ship on <Date>) Date = 01/02/1994


07/23/2015 V/R 003030 21 FCA US

Example: Service & Parts Order Cancel (continued) EDI Format Interpretation PID~F~~~~PARTIAL SHIP Item Description Type = “F” (Free-form) Description = PARTIAL SHIP QTY~39~5 Quantity Qualifier = 39 Quantity = 5 N1~MA~~91~05002 Entity Identifier Code = MA Identification Code Qualifier = “91” (Assigned by Seller or Seller's Agent) Identification Code = 05002 PO1~~5~EA~~~BP~P8888888~OR~OR234567 Quantity Ordered = 5 Unit or Basis for Measurement Code = “EA” (Each) Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = P8888888 Product/Service ID Qualifier = OR Product/Service ID = OR234567 ISR~IC~931203 Shipment/Order Status Code = “IC” (Item Cancelled) Date = 12/03/1993 PID~F~~~~NO LONGER AVAILABLE Item Description Type = “F” (Free-form) Description = NO LONGER AVAILABLE QTY~ZZ~5 Quantity Qualifier = “ZZ” (Mutually Defined) Quantity = 5 N1~MA~~91~05032 Entity Identifier Code = MA Identification Code Qualifier = “91” (Assigned by Seller or Seller's Agent) Identification Code = 05032 PO1~~35~EA~~~BP~P8881111~OR~OR567890 Quantity Ordered = 35 Unit or Basis for Measurement Code = “EA” (Each) Product/Service ID Qualifier = “BP” (Buyer's Part Number) Product/Service ID = P8881111 Product/Service ID Qualifier = OR Product/Service ID = OR567890 ISR~BM~940115 Shipment/Order Status Code = “BM” (Backordered, Manufacturer, Out-of-Stock) Date = 01/15/1994 PID~F~~~~12 Item Description Type = “F” (Free-form) Description = 12 QTY~BQ~35 Quantity Qualifier = “BQ” (Backorder Quantity) Quantity = 35


07/23/2015 V/R 003030 22 FCA US

Example: Service & Parts Order Cancel (continued) EDI Format Interpretation N1~MA~~91~05032 Entity Identifier Code = MA Identification Code Qualifier = “91” (Assigned by Seller or Seller's Agent) Identification Code = 05032 CTT~1 Number of Line Items = 1 SE~26~0001 Number of Included Segments = 26 Transaction Set Control Number = 0001

implementation guidelines for ansi asc x12 edi … documents... · fca us - mopar order status...

Documents