TENNESSEE GAS PIPELINE COMPANY
|
|
- Drusilla Knight
- 7 years ago
- Views:
Transcription
1 TGP Nomination Related Implementation Guide TENNESSEE GAS PIPELINE COMPANY Nominations Related Standards EDI Implementation Guide Supplement Version 1.4 Effective May May, 2001
2 TGP Nomination Related Implementation Guide Tennessee Gas Pipeline EDI Implementation Guide Supplement For those customers using EDI, this supplement describes how to map the GISB data sets when exchanging information in an X12 electronic format. The supplement is designed to be used in conjunction with the business sections from the GISB Nominations Related Standards Manual. The Tennessee supplement provides Tennessee business practices relevant to EDI that are in addition to the GISB standards, and the X12 mapping layout for Tennessee. The Tennessee X12 mapping layout is based on the GISB standard, version 1.4, but is customized specifically for the way business is conducted on the Tennessee pipelines. This supplement is designed specifically for business on the Tennessee pipelines. As such, the Data Element Cross Reference to ASC X12 and X12 Mapping sections contain data elements, usages and conditions specific to Tennessee. For the GISB data element definitions, usages and conditions, please consult the GISB Nominations Related Standards Manual, version 1.4. There are multiple parties that may be involved in a transaction, in both the business data in the transaction and the enveloping/communication data surrounding the business related information. 1. Business Related Party - The parties within the transaction (in the N1 and similar segments) represent the entities involved in the business transaction, and are the same regardless of whether the business transaction is conducted via EDI, the on-line EBB, or some other means. These entities would be the Service Requester, Service Requester Agent, Transportation Service Provider, etc. These may or may not be the same party as the EDI Trading Partner. 2. ISA Party and HTTP Party - The parties in the envelope of the transaction, both in the ISA envelope and HTTP envelope, are specified in the EDI Trading Partner Agreement. TGP expects that at least one of these locations will contain the party that signed the EDI Trading Partner Agreement, typically the HTTP. This is the information that is communicated into and out of TGP s back-office system and is used when validating the EDI Trading Partner that is sending/receiving the transaction. There is more information about Party Roles and the ISA segment in the Related Standards section of the GISB Implementation Guides. Information about the EDM fields can be found in GISB s EDM Related Standards Manual. Any questions about information contained in this supplement should be directed to your Tennessee Gas Pipeline Customer Service Representative. 2 May, 2001
3 TGP Nomination Related Implementation Guide Nominations Related Standards Table of Contents NOMINATION Data Element Cross Reference to ASC X ASC X12 Mapping...7 NOMINATION QUICK RESPONSE Data Element Cross Reference to ASC X ASC X12 Mapping...26 REQUEST FOR CONFIRMATION Data Element Cross Reference to ASC X ASC X12 Mapping...44 CONFIRMATION RESPONSE Data Element Cross Reference to ASC X ASC X12 Mapping...61 SCHEDULED QUANTITY Data Element Cross Reference to ASC X ASC X12 Mapping...81 SCHEDULED QUANTITY FOR OPERATOR Data Element Cross Reference to ASC X ASC X12 Mapping CONFIRMATION RESPONSE QUICK RESPONSE Data Element Cross Reference to ASC X ASC X12 Mapping May, 2001
4 TGP Nomination NOMINATION TGP Specific Implementation Notes for the Nomination: TGP uses Model Types of Pathed and Non-Pathed. TGP requires the use of Beginning Time and Ending Time There are at least two distinct types of natural gas transactions that may require a nomination. A transportation service nomination involves the movement of gas between locations for an entity under a transportation contract. A title tracking nomination involves a change in gas ownership from one contract or entity to another, at a specified physical or logical location. Confirmation nominations data elements are covered in the Request for Confirmation and Confirmation Response sections. Tennessee Gas Pipeline will no longer confirm at the contract level. Therefore, nominations will now point upstream and/or downstream to a DUNS Identifier Code ("up/dn ID"). At non-interconnect locations, the Upstream Identifier Code (and/or Downstream Identifier Code) must be populated and will be validated to ensure the party represents a valid operator or up/down party at the location. At interconnect locations, the Up/Down DUNS must be populated, but will not be validated. (The intention is that the DUNS will represent the shipper on the interconnecting pipeline.) Requiring the DUNS field to be populated should facilitate the confirmation process with interconnecting pipelines. DUNS number is considered a 9-digit alpha/numeric data element. If the customer does not populate rank, the system will default to 500. If the PI DRN does not exist, TGP will accept the proprietary location code (with proper qualifier). TNMST14A (003040) 4 May, 2001
5 TGP Nomination Selected Code Values Used by TGP: Transaction Type: Code Value Description Code Value TGP Comments Authorized Contract Overrun 02 Used with Pathed Model Type Current Business (default) 01 Used with Pathed Model Type Extended Receipt/Delivery Service 14 Imbalance Payback from Transportation Service Provider Imbalance Payback to Transportation Service Provider Loan 28 Used with Pathed Model Type Loan Payback 29 Used with Pathed Model Type Park 26 Used with Pathed Model Type Park Withdrawal 27 Used with Pathed Model Type TNMST14A (003040) 5 May, 2001
6 TGP Nomination DATA ELEMENT CROSS REFERENCE TO ASC X12 P - Pathed Model, N - Non-Pathed Model Usage Codes: M - Mandatory, C - Conditional, SO - Sender s Option, BC - Business Conditional, MA - Mutually Agreeable, nu - not used Heading: Segment Usage P N Segment Name/GISB Data Element Name ST M M Transaction Set Header BEG M M Beginning Segment DTM M M Time Stamp N1 N1 M M M M Transportation Service Provider Service Requester Detail: Segment Usage P N Segment Name/GISB Data Element Name PO1 M M M M DTM DTM Sub-detail: M M M M M M M M SLN M M M M SI M M M M SO SO SO SO SO SO N1 N1 N1 N1 M C M C M C M C Service Requester Contract Model Type Beginning Date Beginning Time Ending Date Ending Time Nominator's Tracking ID Quantity Quantity Type Indicator Transaction Type Receipt Rank (Priority) Delivery Rank (Priority) Package ID Delivery Location/Delivery Location Proprietary Code Receipt Location/Receipt Location Proprietary Code Downstream Identifier Code Upstream Identifier Code Summary: Segment Usage P N Segment Name/GISB Data Element Name CTT M M Transaction Totals SE M M Transaction Set Trailer TNMST14A (003040) 6 May, 2001
7 TGP Nomination ASC X12 MAPPING Below are the values TGP expects to send/receive in the ISA and GS segments for this transaction. This does not imply that each separate transaction must have an ISA/IEA and GS/GE pair surrounding it. Please consult the GISB Implementation Manual Related Standards Section for the usage of the ISA/IEA and GS/GE segments in conjunction with business transactions. Items in brackets are for instruction and not meant to be read as literal text to be included in the element. ISA Segment Ref. Des. Value or Choice of Values X12 Name and TGP Notes X12 Attributes ISA01 00 Authorization Information Qualifier M ID 2/2 ISA02 [blank] Authorization Information M AN 10/10 For TGP, there is no meaningful information in this element. ISA03 00 Security Information Qualifier M ID 2/2 ISA04 [blank] Security Information M AN 10/10 For TGP, there is no meaningful information in this element. ISA05 Interchange ID Qualifier M ID 2/2 This is determined by the sending trading partner and stated in the EDI Trading Partner Agreement. ISA06 Interchange Sender ID M AN 15/15 This is determined by the sending trading partner and stated in the EDI Trading Partner Agreement. ISA07 01 Interchange ID Qualifier M ID 2/2 Duns (Dun & Bradstreet) ISA Interchange Receiver ID M AN 15/15 For TGP, this is the pipeline Duns number. ISA09 [date] Interchange Date M DT 6/6 ISA10 [time] Interchange Time M TM 4/4 ISA11 U Interchange Control Standards Identifier M ID 1/1 ISA Interchange Control Version Number M ID 5/5 ISA13 Interchange Control Number M N0 9/9 This is assigned by the sender s translator and repeated in the corresponding IEA02. ISA Acknowledgment Requested 0 - No Acknowledgment Requested 1 - Interchange Acknowledgment Requested M ID 1/1 ISA15 ISA16 T P Test Indicator T - Test Data P - Production Data Subelement Separator This is determined by the sending trading partner. M ID 1/1 M AN 1/1 TNMST14A (003040) 7 May, 2001
8 TGP Nomination GS Segment Ref. Des. Value or Choice of Values X12 Name and TGP Notes X12 Attributes GS01 PO Functional Identifier Code M ID 2/2 GS02 Application Sender s Code M AN 2/15 This is determined by the sending trading partner and stated in the EDI Trading Partner Agreement. GS T01 Application Receiver s Code M AN 2/15 GS04 [date] Date M DT 6/6 GS05 [time] Time M TM 4/8 GS06 Group Control Number M N0 1/9 This is assigned by the sender s translator and repeated in the corresponding GE02. GS07 X Responsible Agency Code M ID 1/2 GS Version/Release/Industry Identifier Code M AN 1/12 TNMST14A (003040) 8 May, 2001
9 TGP Nomination 850 Purchase Order Functional Group ID=PO Notes: This document contains the Nomination X12 format for Tennessee Gas Pipeline. This document is based on the GISB Nomination (1.4.1), version 1.4. Heading: Pos. Seg. Req. Loop Notes and Must Use No. ID Name Des. Max.Use Repeat Comments 010 ST Transaction Set Header M 1 Must Use 020 BEG Beginning Segment for Purchase Order M 1 Must Use 150 DTM Date/Time/Period O 10 LOOP ID - N1 200 Must Use 310 N1 Name O 1 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - PO Must Use 010 PO1 Baseline Item Data M 1 Must Use 210 DTM Date/Time/Period O 10 Must Use 215 DTM Date/Time/Period O 10 LOOP ID - SLN 1000 Must Use 470 SLN Subline Item Detail O 1 Must Use 480 SI Service Characteristic Identification O 5 LOOP ID - N1 10 Must Use 530 N1 Name O 1 LOOP ID - N1 10 Must Use 680 N1 Name O 1 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 CTT Transaction Totals M 1 Must Use 030 SE Transaction Set Trailer M 1 TNMST14A (003040) 9 May, 2001
10 TGP Nomination Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Must Use ST Transaction Set Identifier Code M ID 3/3 850 X12.1 Purchase Order Must Use ST Transaction Set Control Number M AN 4/9 TNMST14A (003040) 10 May, 2001
11 TGP Nomination Segment: BEG Beginning Segment for Purchase Order Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Must Use BEG Transaction Set Purpose Code M ID 2/2 00 Original Must Use BEG02 92 Purchase Order Type Code M ID 2/2 G1 Nomination-Shipper to Transporter Must Use BEG Purchase Order Number M AN 1/22 The nomination number assigned by the nomination originator. Must Use BEG Purchase Order Date M DT 6/6 The nomination issue date. TNMST14A (003040) 11 May, 2001
12 TGP Nomination Segment: DTM Date/Time/Period Position: 150 Loop: Level: Heading Usage: Optional (Must Use) Max Use: 10 Notes: For GISB, this segment is mandatory. Must Use DTM Date/Time Qualifier M ID 3/3 102 Issue 582 Report Period Must Use DTM Date Time Period Format Qualifier X ID 2/3 DT Date and Time Expressed in Format CCYYMMDDHHMM Must Use DTM Date Time Period X AN 1/35 Time Stamp TNMST14A (003040) 12 May, 2001
13 TGP Nomination Segment: N1 Name Position: 310 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory and should occur once for each value in the N101 element. Must Use N Entity Identifier Code M ID 2/2 78 Service Requester SJ Service Provider Must Use N Identification Code Qualifier X ID 1/2 1 D-U-N-S Number, Dun & Bradstreet Must Use N Identification Code X AN 2/17 Service Requester, Transportation Service Provider TNMST14A (003040) 13 May, 2001
14 TGP Nomination Segment: PO1 Baseline Item Data Position: 010 Loop: PO1 Mandatory Level: Detail Usage: Mandatory Max Use: 1 Must Use PO Assigned Identification M AN 1/11 Must Use PO Product/Service ID Qualifier M ID 2/2 CR Contract Number Must Use PO Product/Service ID X AN 1/30 Service Requester Contract For TGP, this is the contract number for the nomination. Must Use PO Product/Service ID Qualifier O ID 2/2 MN Model Number Must Use PO Product/Service ID O AN 1/30 Model Type N P Non-Pathed Model For TGP, SA and FS nominations are nonpathed. Pathed Model For TGP, Transportation nominations are pathed. TNMST14A (003040) 14 May, 2001
15 TGP Nomination Segment: DTM Date/Time/Period Position: 210 Loop: PO1 Mandatory Level: Detail Usage: Optional (Must Use) Max Use: 10 Notes: For GISB, this segment is mandatory. Must Use DTM Date/Time Qualifier M ID 3/3 007 Effective Must Use DTM Date Time Period Format Qualifier X ID 2/3 D8 Date Expressed in Format CCYYMMDD When used with Beginning Date, this code designates the "gas day" on which the transaction is to be initiated. DT Date and Time Expressed in Format CCYYMMDDHHMM When used with Beginning Date and Beginning Time, this code designates the instance in time when the transaction is to be initiated. Must Use DTM Date Time Period X AN 1/35 Beginning Date, Beginning Time TNMST14A (003040) 15 May, 2001
16 TGP Nomination Segment: DTM Date/Time/Period Position: 215 Loop: PO1 Mandatory Level: Detail Usage: Optional (Must Use) Max Use: 10 Notes: For GISB, this segment is mandatory. Must Use DTM Date/Time Qualifier M ID 3/3 197 End Must Use DTM Date Time Period Format Qualifier X ID 2/3 D8 Date Expressed in Format CCYYMMDD When used with Ending Date, this code designates the "gas day" on which the transaction is to finish. For example, a transaction through the last day of August 1998 would be stated as DT Date and Time Expressed in Format CCYYMMDDHHMM When used with Ending Date and Ending Time, this code designates the instance in time when the transaction is to finish. For example, a transaction through the last day of August 1998 would be stated as Must Use DTM Date Time Period X AN 1/35 Ending Date, Ending Time TNMST14A (003040) 16 May, 2001
17 TGP Nomination Segment: SLN Subline Item Detail Position: 470 Loop: SLN Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory. Must Use SLN Assigned Identification M AN 1/11 This identifier may be assigned by the translator. Must Use SLN Assigned Identification O AN 1/11 Nominator's Tracking ID Must Use SLN Configuration Code M ID 1/1 I Included Must Use SLN Quantity M R 1/15 Quantity For TGP, this is either the Receipt Quantity or Delivery Quantity, depending on the Quantity Type Indicator. Must Use SLN Unit or Basis for Measurement Code M ID 2/2 BZ Million BTU's TNMST14A (003040) 17 May, 2001
18 TGP Nomination Segment: SI Servi ce Characteristic Identification Position: 480 Loop: SLN Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 5 Notes: For GISB, this segment is mandatory. Note: Each data element may occur in one of the 1000/234 pairs per the usage in the data dictionary. The data elements may occur in any order. Must Use SI Agency Qualifier Code M ID 2/2 AP American Petroleum Institute Must Use SI Service Characteristics Qualifier M ID 2/2 QT Quantity Type Indicator Must Use SI Product/Service ID M AN 1/30 Quantity Type Indicator D Delivery R Receipt Must Use SI Service Characteristics Qualifier X ID 2/2 TT Transaction Type Must Use SI Product/Service ID X AN 1/30 Transaction Type 01 Current Business (default) 02 Authorized Contract Overrun 03 Imbalance Payback from Transportation Service Provider 04 Imbalance Payback to Transportation Service Provider 14 Extended Receipt/Delivery Service 26 Park 27 Park Withdrawal 28 Loan 29 Loan Payback SI Service Characteristics Qualifier X ID 2/2 PG Package ID SI Product/Service ID X AN 1/30 Package ID For GISB, this element is sender's option. SI Service Characteristics Qualifier X ID 2/2 R2 Receipt Rank (Priority) SI Product/Service ID X AN 1/30 Receipt Rank (Priority) For GISB, this element is sender's option. For TGP, if the Receipt Rank is not sent, a default of 500 will be used. 001 is cut last, 500 is cut first. SI Service Characteristics Qualifier X ID 2/2 R3 Delivery Rank ( Priority) SI Product/Service ID X AN 1/30 Delivery Rank (Priority) For GISB, this element is sender's option. TNMST14A (003040) 18 May, 2001
19 TGP Nomination For TGP, if the Delivery Rank is not sent, a default of 500 will be used. 001 is cut last, 500 is cut first. TNMST14A (003040) 19 May, 2001
20 TGP Nomination Segment: N1 Name Position: 530 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory. Must Use N Entity Identifier Code M ID 2/2 M2 Receipt Meter Location Receipt Location MQ Metering Location Delivery Location Must Use N Identification Code Qualifier X ID 1/2 29 Grid Location and Facility Code ZY Temporary Identification Number Transportation Service Provider's proprietary code When a Transportation Service Provider's proprietary code is employed pursuant to this standard, the parties agree that nominations, confirmations, scheduled quantities, and capacity release documents employing such code should be for one gas day at a time, and used only until there is a verified common code for the point associated with the proprietary location code. This would include daily nominations over a weekend. Within two months following the availability of the location the parties should employ the common code and no longer employ the proprietary code for identifying such location in the datasets related to the identified standards. Must Use N Identification Code X AN 2/17 Receipt Location, Delivery Location TNMST14A (003040) 20 May, 2001
21 TGP Nomination Segment: N1 Name Position: 680 Loop: N1 Optional (Must Use) Leve l: Detail Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory. Must Use N Entity Identifier Code M ID 2/2 DW Downstream Party Downstream Identifier Code US Upstream Party Upstream Identifier Code Must Use N Identification Code Qualifier X ID 1/2 1 D-U-N-S Number, Dun & Bradstreet Must Use N Identification Code X AN 2/17 Upstream Identifier Code, Downstream Identifier Code For TGP, at pipeline interconnects, the Upstream Identifier Code (and/or Downstream Identifier Code) must be populated and represents the shipper on the pipeline upstream (or downstream) of the interconnect. At non-interconnects, the Upstream/Downstream Identifier Code must be populated and will be validated to ensure the party represents a valid operator/producer at the meter. TNMST14A (003040) 21 May, 2001
22 TGP Nomination Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Must Use CTT Number of Line Items M N0 1/6 The number of PO1 segments. TNMST14A (003040) 22 May, 2001
23 TGP Nomination Segment: SE Transaction Set Trailer Position: 030 Loop: Level: Summary Usage: Mandatory Max Use: 1 Must Use SE01 96 Number of Included Segments M N0 1/10 Must Use SE Transaction Set Control Number M AN 4/9 TNMST14A (003040) 23 May, 2001
24 TGP Nomination Quick Response NOMINATION QUICK RESPONSE TGP Specific Implementation Notes for the Nomination Quick Response: If there are any errors or warnings generated for the Nomination, both the GISB error/warning Validation Code and a TGP specific Validation Message will be sent in the Nomination Quick Response. Please see the "Errors and Warnings (Heading)," "Errors and Warnings (Detail)," and "Errors and Warnings (Sub-detail)" tables in the GISB Nomination Quick Response Transaction Set Tables section of the GISB Nominations Related Standards Implementation Guide for the GISB description of the Validation Codes. TNMQR14A (003040) 24 May, 2001
25 TGP Nomination Quick Response DATA ELEMENT CROSS REFERENCE TO ASC X12 Usage Codes: M - Mandatory, C - Conditional, SO - Sender's Option, BC - Business Conditional, MA - Mutually Agreeable, nu - not used Heading: Segment Usage Segment Name/GISB Data Element Name ST M Transaction Set Header BAK M Transaction Status Code PID N1 N1 C SO M M Validation Code Validation Message Transportation Service Provider Service Requester Detail: Summary: Segment Usage Segment Name/GISB Data Element Name PO1 C Service Requester Contract PID DTM DTM Sub-detail: C SO C C C C Validation Code Validation Message Beginning Date Beginning Time Ending Date Ending Time SLN C Nominator's Tracking ID PID C SO Validation Code Validation Message Segment Usage Segment Name/GISB Data Element Name CTT M Transaction Totals SE M Transaction Set Trailer TNMQR14A (003040) 25 May, 2001
26 TGP Nomination Quick Response ASC X12 MAPPING Below are the values TGP expects to send/receive in the ISA and GS segments for this transaction. This does not imply that each separate transaction must have an ISA/IEA and GS/GE pair surrounding it. Please consult the GISB Implementation Manual Related Standards Section for the usage of the ISA/IEA and GS/GE segments in conjunction with business transactions. Items in brackets are for instruction and not meant to be read as literal text to be included in the element. ISA Segment Ref. Des. Value or Choice of Values X12 Name and TGP Notes X12 Attributes ISA01 00 Authorization Information Qualifier M ID 2/2 ISA02 [blank] Authorization Information M AN 10/10 For TGP, there is no meaningful information in this element. ISA03 00 Security Information Qualifier M ID 2/2 ISA04 [blank] Security Information M AN 10/10 For TGP, there is no meaningful information in this element. ISA05 01 Interchange ID Qualifier M ID 2/2 Duns (Dun & Bradstreet) ISA Interchange Sender ID M AN 15/15 For TGP, this is the pipeline Duns number. ISA07 Interchange ID Qualifier M ID 2/2 This is determined by the receiving trading partner and stated in the EDI Trading Partner Agreement. ISA08 Interchange Receiver ID M AN 15/15 This is determined by the receiving trading partner and stated in the EDI Trading Partner Agreement. ISA09 [date] Interchange Date M DT 6/6 ISA10 [time] Interchange Time M TM 4/4 ISA11 U Interchange Control Standards Identifier M ID 1/1 ISA Interchange Control Version Number M ID 5/5 ISA13 Interchange Control Number M N0 9/9 This is assigned by the sender s translator and repeated in the corresponding IEA02. ISA Acknowledgment Requested 0 - No Acknowledgment Requested 1 - Interchange Acknowledgment Requested M ID 1/1 ISA15 T P Test Indicator T - Test Data P - Production Data M ID 1/1 ISA16 > Subelement Separator M AN 1/1 TNMQR14A (003040) 26 May, 2001
27 TGP Nomination Quick Response GS Segment Ref. Des. Value or Choice of Values X12 Name and TGP Notes X12 Attributes GS01 PR Functional Identifier Code M ID 2/2 GS Application Sender s Code M AN 2/15 GS03 Application Receiver s Code M AN 2/15 This is determined by the receiving trading partner and stated in the EDI Trading Partner Agreement. GS04 [date] Date M DT 6/6 GS05 [time] Time M TM 4/8 GS06 Group Control Number M N0 1/9 This is assigned by the sender s translator and repeated in the corresponding GE02. GS07 X Responsible Agency Code M ID 1/2 GS Version/Release/Industry Identifier Code M AN 1/12 TNMQR14A (003040) 27 May, 2001
28 TGP Nomination Quick Response 855 Purchase Order Acknowledgment Functional Group ID=PR Notes: This document contains the Nomination Quick Response X12 format for Tennessee Gas Pipeline. This document is based on the GISB Nomination Quick Response (1.4.2), version 1.4. Heading: Pos. Seg. Req. Loop Notes and Must Use No. ID Name Des. Max.Use Repeat Comments 010 ST Transaction Set Header M 1 Must Use 020 BAK Beginning Segment for Purchase Order M 1 Acknowledgment 190 PID Product/Item Description O 200 LOOP ID - N1 200 Must Use 300 N1 Name O 1 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - PO PO1 Baseline Item Data O 1 LOOP ID - PID PID Product/Item Description O DTM Date/Time/Period O DTM Date/Time/Period O 10 LOOP ID - SLN SLN Subline Item Detail O PID Product/Item Description O 1000 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 CTT Transaction Totals M 1 Must Use 030 SE Transaction Set Trailer M 1 TNMQR14A (003040) 28 May, 2001
29 TGP Nomination Quick Response Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Must Use ST Transaction Set Identifier Code M ID 3/3 855 X12.9 Purchase Order Acknowledgment Must Use ST Transaction Set Control Number M AN 4/9 TNMQR14A (003040) 29 May, 2001
30 TGP Nomination Quick Response Segment: BAK Beginning Segment for Purchase Order Acknowledgment Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Must Use BAK Transaction Set Purpose Code M ID 2/2 27 Verify Must Use BAK Acknowledgment Type M ID 2/2 Transaction Status Code AE Acknowledge - With Exception Detail Only Error(s) or warning(s) occurred in the transaction. Transaction has been acknowledged. Error(s) and warning(s) follow. AT Accepted The entire transaction and all nominations were accepted. RD Reject with Detail The entire transaction was rejected due to header level errors. Must Use BAK Purchase Order Number M AN 1/22 The nomination number assigned by the nomination originator in the BEG03. Must Use BAK Purchase Order Date M DT 6/6 The nomination issue date. TNMQR14A (003040) 30 May, 2001
31 TGP Nomination Quick Response Segment: PID Product/Item Description Position: 190 Loop: Level: Heading Usage: Optional Max Use: 200 Notes: For GISB, this segment is mandatory when BAK02 = 'RD' or when BAK02 = 'AE' and warning(s) exist at the header level. Must Use PID Item Description Type M ID 1/1 X Semi -structured (Code and Text) Must Use PID Agency Qualifier Code X ID 2/2 AP American Petroleum Institute Must Use PID Product Description Code X AN 1/12 Validation Code Refer to "Errors and Warnings (Heading)" table for usage and values. This table is located in the Nomination Quick Response section of the GISB Nominations Related Standards Implementation Guide. PID Description X AN 1/80 Validation Message For GISB, this element is sender's option. However, if sending an error or warning code that has been approved by GISB, but not yet published, the Validation Message should be sent for further clarification. TNMQR14A (003040) 31 May, 2001
32 TGP Nomination Quick Response Segment: N1 Name Position: 300 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory and should occur once for each value indicated in the N101 element. Must Use N Entity Identifier Code M ID 2/2 78 Service Requester SJ Service Provider Must Use N Identification Code Qualifier X ID 1/2 1 D-U-N-S Number, Dun & Bradstreet Must Use N Identification Code X AN 2/17 Service Requester, Transportation Service Provider TNMQR14A (003040) 32 May, 2001
33 TGP Nomination Quick Response Segment: PO1 Baseline Item Data Position: 010 Loop: PO1 Optional Level: Detail Usage: Optional Max Use: 1 Notes: For GISB, this segment is mandatory when BAK02 = 'AE' and the error(s) or warning(s) exist at the detail or sub-detail level. Must Use PO Assigned Identification O AN 1/11 PO Product/Service ID Qualifier O ID 2/2 CR Contract Number PO Product/Service ID X AN 1/30 Service Requester Contract Mandatory when the error(s) or warning(s) exist at the detail level. TNMQR14A (003040) 33 May, 2001
34 TGP Nomination Quick Response Segment: PID Product/Item Description Position: 050 Loop: PID Optional Level: Detail Usage: Optional Max Use: 1 Notes: For GISB, this segment is mandatory when BAK02 = 'AE' and the error(s) or warning(s) exist at the detail level. Must Use PID Item Description Type M ID 1/1 X Semi -structured (Code and Text) Must Use PID Agency Qualifier Code X ID 2/2 AP American Petroleum Institute Must Use PID Product Description Code X AN 1/12 Validation Code Refer to "Errors and Warnings (Detail)" table for usage and values. This table is located in the Nomination Quick Response section of the GISB Nominations Related Standards Implementation Guide. PID Description X AN 1/80 Validation Message For GISB this element is sender's option. However, if sending an error or warning code that has been approved by GISB, but not yet published, the Validation Message should be sent for further clarification. TNMQR14A (003040) 34 May, 2001
35 TGP Nomination Quick Response Segment: DTM Date/Time/Period Position: 200 Loop: PO1 Optional Level: Detail Usage: Optional Max Use: 10 Notes: For GISB, this segment is mandatory when BAK02 = 'AE' and the error(s) or warning(s) exist at the detail level. Must Use DTM Date/Time Qualifier M ID 3/3 007 Effective Must Use DTM Date Time Period Format Qualifier X ID 2/3 D8 Date Expressed in Format CCYYMMDD When used with Beginning Date, this code designates the "gas day" on which the transaction is to be initiated. DT Date and Time Expressed in Format CCYYMMDDHHMM When used with Beginning Date and Beginning Time, this code designates the instance in time when the transaction is to be initiated. Must Use DTM Date Time Period X AN 1/35 Beginning Date, Beginning Time TNMQR14A (003040) 35 May, 2001
36 TGP Nomination Quick Response Segment: DTM Date/Time/Period Position: 205 Loop: PO1 Optional Level: Detail Usage: Optional Max Use: 10 Notes: For GISB, this segment is mandatory when BAK02 = 'AE' and the error(s) or warning(s) exist at the detail level. Must Use DTM Date/Time Qualifier M ID 3/3 197 End Must Use DTM Date Time Period Format Qualifier X ID 2/3 D8 Date Expressed in Format CCYYMMDD When used with Ending Date, this code designates the "gas day" on which the transaction is to finish. For example, a transaction through the last day of August 1998 would be stated as DT Date and Time Expressed in Format CCYYMMDDHHMM When used with Ending Date and Ending Time, this code designates the instance in time when the transaction is to finish. For example, a transaction through the last day of August 1998 would be stated as Must Use DTM Date Time Period X AN 1/35 Ending Date, Ending Time TNMQR14A (003040) 36 May, 2001
37 TGP Nomination Quick Response Segment: SLN Subline Item Detail Position: 490 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 1 Notes: For GISB, this segment is mandatory when BAK02 = 'AE' and the error(s) or warning(s) exist at the sub-detail level. Must Use SLN Assigned Identification M AN 1/11 Must Use SLN Assigned Identification O AN 1/11 Nominator's Tracking ID Must Use SLN Configuration Code M ID 1/1 I Included Must Use SLN Quantity M R 1/15 For GISB, send zero. Must Use SLN Unit or Basis for Measurement Code M ID 2/2 BZ Million BTU's TNMQR14A (003040) 37 May, 2001
38 TGP Nomination Quick Response Segment: PID Product/Item Description Position: 510 Loop: SLN Optional Level: Detail Usage: Optional Max Use: 1000 Notes: For GISB, this segment is mandatory when BAK02 = 'AE' and the error(s) or warning(s) exist at the sub-detail level. Must Use PID Item Description Type M ID 1/1 S Structured (From Industry Code List) Must Use PID Agency Qualifier Code X ID 2/2 AP American Petroleum Institute Must Use PID Product Description Code X AN 1/12 Validation Code Refer to "Errors and Warnings (Sub-detail)" table for usage and values. This table is located in the Nomination Quick Response section of the GISB Nominations Related Standards Implementation Guide. PID Description X AN 1/80 Validation Message For GISB this element is sender's option. However, if sending an error or warning code that has been approved by GISB, but not yet published, the Validation Message should be sent for further clarification. TNMQR14A (003040) 38 May, 2001
39 TGP Nomination Quick Response Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Must Use CTT Number of Line Items M N0 1/6 The number of PO1 segments. TNMQR14A (003040) 39 May, 2001
40 TGP Nomination Quick Response Segment: SE Transaction Set Trailer Position: 030 Loop: Level: Summary Usage: Mandatory Max Use: 1 Must Use SE01 96 Number of Included Segments M N0 1/10 Must Use SE Transaction Set Control Number M AN 4/9 TNMQR14A (003040) 40 May, 2001
41 TGP Request for Confirmation REQUEST FOR CONFIRMATION TGP Specific Implementation Notes for the Request for Confirmation: The Contractual Flow Indicator identifies the logical direction of flow at a point from the originator s perspective. It may be different from physical flow of gas. Assuming the normal flow of gas, producers and receipt operators will use an R. Delivery operators and end users will use a D. Note that backoffs and backhauls would be opposite. TGP will send Request for Confirmations and expect to receive Confirmation Responses. When an entity does not have a valid common code (the D-U-N-S Number), TGP s proprietary entity identifier code (alphanumeric) will be sent within these datasets until there is a valid common code for the entity associated with the applicable party s proprietary code. TGP will no longer confirm at a contract level. Request for Confirmation quantities will "roll up" to the DUNS number level by location. Confirmation Level (new data element for TGP) - This data element differentiates between the roles of the confirming parties on a TSP that supports multi-level confirmations. When a Request for Confirmation is sent, the confirming party will know for which role (operator, producer, etc) they are being asked to confirm. All confirmations stored in the system will be for the level indicated. Confirmation Level is mapped in the Header N106 element with the following code values: T1 - Operator (OPR) - every physical location will have an OPR Z1 - Upstream or Downstream Party (UDP) - every non-interconnect physical location will have a UDP Note: The Confirmation Level data element was submitted to GISB on request R99037 and is being implemented by TGP per GISB standard Operator Confirmations: * At interconnect locations: there will never be a UDP confirmation. The Upstream Identifier Code or Downstream Identifier Code represents the shipper on the interconnecting pipe, and must be populated (based on Contractual Flow Indicator). The UP/Down DUNS data element will not be validated. Service Requester must be populated and represents the shipper on TGP. * At non-interconnect locations: Upstream Identifier Code or Downstream Identifier Code will always be required (based on Contractual Flow Indicator). The UP/Down DUNS represents the party that is supplying gas to, or receiving gas from the service to requester. The Service Requester data element is not populated. Upstream/Downstream Party Confirmations: * At interconnect locations: Upstream/Downstream (UDP) confirmations are not a valid type of confirmation (see above). * At non-interconnect locations: The Upstream Identifier Code or Downstream Identifier Code is populated based on the Contractual Flow Indicator (CF). TRQCF14A (003040) 41 May, 2001
42 TGP Request for Confirmation * If the CF indicator is "R", then the Upstream Identifier Code is populated and identifies the party who is supplying the quantities to the Service Requester. Service Requester is populated and represents the shipper on TGP and is validated as a valid shipper at that location. * If the CF indicator is "D", then the Downstream Identifier Code is populated and identifies the party who is receiving the quantities from the Service Requester. Service Requester is populated and represents the shipper on TGP and is validated as a valid shipper at that location. TRQCF14A (003040) 42 May, 2001
43 TGP Request for Confirmation DATA ELEMENT CROSS REFERENCE TO ASC X12 Usage Codes: M - Mandatory, C - Conditional, SO - Sender s Option, BC - Business Conditional, MA - Mutually Agreeable, nu - not used Heading: Detail: Segment Usage Segment Name/GISB Data Element Name ST M Transaction Set Header BEG M Transaction Identifier N1 N1 M SO M Confirming Party Confirmation Level Confirmation Requester Segment Usage Segment Name/GISB Data Element Name PO1 M Baseline Item Data segment DTM M M M M Beginning Date Beginning Time Ending Date Ending Time N1 M Location/Location Proprietary Code Sub-detail: SLN SI N1 N1 N1 Summary: M M M MA MA C C MA Confirmation Tracking Identifier Quantity Contractual Flow Indicator Receipt Rank (Priority) Delivery Rank (Priority) Downstream Identifier Code Upstream Identifier Code Service Requester Segment Usage Segment Name/GISB Data Element Name CTT M Transaction Totals SE M Transaction Set Trailer TRQCF14A (003040) 43 May, 2001
44 TGP Request for Confirmation ASC X12 MAPPING Below are the values TGP expects to send/receive in the ISA and GS segments for this transaction. This does not imply that each separate transaction must have an ISA/IEA and GS/GE pair surrounding it. Please consult the GISB Implementation Manual Related Standards Section for the usage of the ISA/IEA and GS/GE segments in conjunction with business transactions. Items in brackets are for instruction and not meant to be read as literal text to be included in the element. ISA Segment Ref. Des. Value or Choice of Values X12 Name and TGP Notes X12 Attributes ISA01 00 Authorization Information Qualifier M ID 2/2 ISA02 [blank] Authorization Information M AN 10/10 For TGP, there is no meaningful information in this element. ISA03 00 Security Information Qualifier M ID 2/2 ISA04 [blank] Security Information M AN 10/10 For TGP, there is no meaningful information in this element. ISA05 01 Interchange ID Qualifier M ID 2/2 Duns (Dun & Bradstreet) ISA Interchange Sender ID M AN 15/15 For TGP, this is the pipeline Duns number. ISA07 Interchange ID Qualifier M ID 2/2 This is determined by the receiving trading partner and stated in the EDI Trading Partner Agreement. ISA08 Interchange Receiver ID M AN 15/15 This is determined by the receiving trading partner and stated in the EDI Trading Partner Agreement. ISA09 [date] Interchange Date M DT 6/6 ISA10 [time] Interchange Time M TM 4/4 ISA11 U Interchange Control Standards Identifier M ID 1/1 ISA Interchange Control Version Number M ID 5/5 ISA13 Interchange Control Number M N0 9/9 This is assigned by the sender s translator and repeated in the corresponding IEA02. ISA Acknowledgment Requested 0 - No Acknowledgment Requested 1 - Interchange Acknowledgment Requested M ID 1/1 ISA15 T P Test Indicator T - Test Data P - Production Data M ID 1/1 ISA16 > Subelement Separator M AN 1/1 TRQCF14A (003040) 44 May, 2001
45 TGP Request for Confirmation GS Segment Ref. Des. Value or Choice of Values X12 Name and TGP Notes X12 Attributes GS01 PO Functional Identifier Code M ID 2/2 GS Application Sender s Code M AN 2/15 GS03 Application Receiver s Code M AN 2/15 This is determined by the receiving trading partner and stated in the EDI Trading Partner Agreement. GS04 [date] Date M DT 6/6 GS05 [time] Time M TM 4/8 GS06 Group Control Number M N0 1/9 This is assigned by the sender s translator and repeated in the corresponding GE02. GS07 X Responsible Agency Code M ID 1/2 GS Version/Release/Industry Identifier Code M AN 1/12 TRQCF14A (003040) 45 May, 2001
46 TGP Request for Confirmation 850 Purchase Order Functional Group ID=PO Notes: This document contains the Request for Confirmation X12 format for Tennessee Gas Pipeline. This document is based on the GISB Request for Confirmation (1.4.3), version 1.4. Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 ST Transaction Set Header M 1 Must Use 020 BEG Beginning Segment for Purchase Order M 1 LOOP ID - N1 200 Must Use 310 N1 Name O 1 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - PO Must Use 010 PO1 Baseline Item Data M 1 Must Use 210 DTM Date/Time/Period O 10 LOOP ID - N1 200 Must Use 350 N1 Name O 1 LOOP ID - SLN 1000 Must Use 470 SLN Subline Item Detail O 1 Must Use 480 SI Service Characteristic Identification O 5 LOOP ID - N1 10 Must Use 530 N1 Name O 1 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 CTT Transaction Totals M 1 Must Use 030 SE Transaction Set Trailer M 1 TRQCF14A (003040) 46 May, 2001
47 TGP Request for Confirmation Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Must Use ST Transaction Set Identifier Code M ID 3/3 850 X12.1 Purchase Order Must Use ST Transaction Set Control Number M AN 4/9 TRQCF14A (003040) 47 May, 2001
48 TGP Request for Confirmation Segment: BEG Beginning Segment for Purchase Order Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Must Use BEG Transaction Set Purpose Code M ID 2/2 00 Original Must Use BEG02 92 Purchase Order Type Code M ID 2/2 G2 Request for Confirmation Must Use BEG Purchase Order Number M AN 1/22 Transaction Identifier Must Use BEG Purchase Order Date M DT 6/6 The confirmation request issue date. TRQCF14A (003040) 48 May, 2001
49 TGP Request for Confirmation Segment: N1 Name Position: 310 Loop: N1 Optional (Must Use) Level: Heading Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory and should occur once for each value indicated in the N101 below. Must Use N Entity Identifier Code M ID 2/2 40 Receiver Confirming Party 41 Submitter Confirmation Requester Must Use N Identification Code Qualifier X ID 1/2 1 D-U-N-S Number, Dun & Bradstreet Must Use N Identification Code X AN 2/17 Confirming Party, Confirmation Requester N Entity Identifier Code O ID 2/2 Confirmation Level For TGP, this element is sender's option and is only applicable when used with the Confirming Party (N101 = '40'). T1 Operator of the Transfer Point Operator Z1 Party to Receive Status Upstream or Downstream Party TRQCF14A (003040) 49 May, 2001
50 TGP Request for Confirmation Segment: PO1 Baseline Item Data Position: 010 Loop: PO1 Mandatory Level: Detail Usage: Mandatory Max Use: 1 Must Use PO Assigned Identification O AN 1/11 This identifier may be assigned by the translator. TRQCF14A (003040) 50 May, 2001
51 TGP Request for Confirmation Segment: DTM Date/Time/Period Position: 210 Loop: PO1 Mandatory Level: Detail Usage: Optional (Must Use) Max Use: 10 Notes: For GISB, this segment is mandatory. Must Use DTM Date/Time Qualifier M ID 3/3 007 Effective Must Use DTM Date Time Period Format Qualifier X ID 2/3 RD8 Range of Dates Expressed in Format CCYYMMDD- CCYYMMDD This code designates the range of "gas days" in which the transaction will occur. For example, the entire month of April 1996 would be stated as RDT Range of Date and Time, Expressed in Format CCYYMMDDHHMM-CCYYMMDDHHMM This code designates the instance in time when the transaction is to be initiated through the instance in time when the transaction is to finish. For example, the entire month of April 1996 would be stated as Must Use DTM Date Time Period X AN 1/35 Beginning Date, Beginning Time, Ending Date, Ending Time TRQCF14A (003040) 51 May, 2001
52 TGP Request for Confirmation Segment: N1 Name Position: 350 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory. Must Use N Entity Identifier Code M ID 2/2 MQ Metering Location Location Must Use N Identification Code Qualifier X ID 1/2 29 Grid Location and Facility Code ZY Temporary Identification Number Transportation Service Provider's Proprietary Code When a Transportation Service Provider's proprietary location code is employed pursuant to this standard, the parties agree that nominations, confirmations, scheduled quantities, and capacity release documents employing such code should be for one gas day at a time, and used only until there is a verified common code for the point associated with the proprietary location code. This would include daily nominations over a weekend. Within two months following the availability of the location the parties should employ the common code and no longer employ the proprietary code for identifyi ng such location in the datasets related to the identified standards. Must Use N Identification Code X AN 2/17 Location TRQCF14A (003040) 52 May, 2001
53 TGP Request for Confirmation Segment: SLN Subline Item Detail Position: 470 Loop: SLN Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory. Must Use SLN Assigned Identification M AN 1/11 This identifier may be assigned by the translator. Must Use SLN Assigned Identification O AN 1/11 Confirmation Tracking Identifier Must Use SLN Configuration Code M ID 1/1 I Included Must Use SLN Quantity M R 1/15 Quantity Must Use SLN Unit or Basis for Measurement Code M ID 2/2 BZ Million BTU's TRQCF14A (003040) 53 May, 2001
54 TGP Request for Confirmation Segment: SI Service Characteristic Identification Position: 480 Loop: SLN Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 5 Notes: For GISB, this segment is mandatory. Note: Each data element may occur in one of the 1000/234 pairs per the specified usage. The data elements may occur in any order. Must Use SI Agency Qualifier Code M ID 2/2 AP American Petroleum Institute Must Use SI Service Characteristics Qualifier M ID 2/2 CF Contractual Flow Indicator Must Use SI Product/Service ID M AN 1/30 Contractual Flow Indicator For TGP, The Contractual Flow Indicator indicates whether the flow is to or from TGP. D Delivery R Receipt SI Service Characteristics Qualifier X ID 2/2 R3 Delivery Rank SI Product/Service ID X AN 1/30 Delivery Rank For GISB, this element is mutually agreed. For TGP, for the Delivery Rank, 011 is cut last and 500 is cut first. SI Service Characteristics Qualifier X ID 2/2 R2 Receipt Rank SI Product/Service ID X AN 1/30 Receipt Rank For GISB, this element is mutually agreed. For TGP, for the Receipt Rank, 001 is cut last and 500 is cut first. TRQCF14A (003040) 54 May, 2001
55 TGP Request for Confirmation Segment: N1 Name Position: 530 Loop: N1 Optional (Must Use) Level: Detail Usage: Optional (Must Use) Max Use: 1 Notes: For GISB, this segment is mandatory. Must Use N Entity Identifier Code M ID 2/2 78 Service Requester DW Downstream Party US Upstream Party Must Use N Identification Code Qualifier X ID 1/2 1 D-U-N-S Number, Dun & Bradstreet ZZ Mutually Defined Transportation Service Provider's Proprietary Code For TGP, when an entity does not have a valid common code (the D-U-N-S Number), TGP's entity proprietary code (business party code) will be sent within these datasets until there is a valid common code for the entity associated with the applicable party's proprietary code. Must Use N Identification Code X AN 2/17 Downstream Identifier Code, Upstream Identifier Code, Service Requester For GISB, Service Requester is mutually agreeable. For TGP, at pipeline interconnects, the Upstream Identifier Code (or Downstream Identifier Code) represents the shipper on the pipeline upstream (or downstream) of the interconnect. At noninterconnects, the Upstream Identifier Code (or Downstream Identifier Code) will be validated and must have confirming rights at the meter location. TRQCF14A (003040) 55 May, 2001
56 TGP Request for Confirmation Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Must Use CTT Number of Line Items M N0 1/6 The number of PO1 segments. TRQCF14A (003040) 56 May, 2001
57 TGP Request for Confirmation Segment: SE Transaction Set Trailer Position: 030 Loop: Level: Summary Usage: Mandatory Max Use: 1 Must Use SE01 96 Number of Included Segments M N0 1/10 Must Use SE Transaction Set Control Number M AN 4/9 TRQCF14A (003040) 57 May, 2001
58 TGP Confirmation Response CONFIRMATION RESPONSE TGP Specific Implementation Notes for the Confirmation Response: The Contractual Flow Indicator identifies the logical direction of flow at a point from the originator s perspective. It may be different from physical flow of gas. Assuming the normal flow of gas, producers and receipt operators will use an R. Delivery operators and end users will use a D. Note that backoffs and backhauls would be opposite. TGP will send Request for Confirmations and expect to receive Confirmation Responses. The following basic rules apply when transmitting an unsolicited Confirmation Response: Operator Confirmations: * At interconnect locations: there will never be a UDP confirmation. The Upstream Identifier Code or Downstream Identifier Code represents the shipper on the interconnecting pipe, and must be populated (based on Contractual Flow Indicator). The UP/Down DUNS data element will not be validated. Service Requester must be populated and represents the shipper on TGP. * At non-interconnect locations: Upstream Identifier Code or Downstream Identifier Code will always be required (based on Contractual Flow Indicator). The UP/Down DUNS represents the party that is supplying gas to, or receiving gas from the service to requester. The Service Requester data element is not populated. Upstream/Downstream Party Confirmations: * At interconnect locations: Upstream/Downstream (UDP) confirmations are not a valid type of confirmation (see above). * At non-interconnect locations: The Upstream Identifier Code or Downstream Identifier Code is populated based on the Contractual Flow Indicator (CF). * If the CF indicator is "R", then the Upstream Identifier Code is populated and identifies the party who is supplying the quantities to the Service Requester. Service Requester is populated and represents the shipper on TGP and is validated as a valid shipper at that location. * If the CF indicator is "D", then the Downstream Identifier Code is populated and identifies the party who is receiving the quantities from the Service Requester. Service Requester is populated and represents the shipper on TGP and is validated as a valid shipper at that location. Unsolicited Confirmation Responses must contain the Confirmation Level data element mapped in the Header N106 element with the following code values: T1 - Operator (OPR) - every physical location will have an OPR Z1 - Upstream or Downstream Party (UDP) - every non-interconnect physical location will have a UDP Note: The Confirmation Level data element was submitted to GISB on request R99037 and is being implemented by TGP per GISB standard Reduction Reason Codes (SO) sent in the Confirmation Response may be overlaid by TGP during the scheduling process. TRRFC14A (003040) 58 May, 2001
Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID IT1 200000 0100 IT1 Baseline Item Data M 1 0600 PID Product / Item Description M 1 1000
810 Invoice Introduction: Functional Group ID=IN This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data
More information810 Invoice ANSI ASC X12 Version 4010
810 Invoice ANSI ASC X12 Version 4010 ERICO International 31700 Solon Rd. Solon, OH 44139 7/15/2009 Purchase Order Acknowledgment Invoice-810-855 ii 7/15/2009 Purchase Order Acknowledgment Invoice-810-855
More informationANSI X12 version 4010 830 Planning Schedule with Release Capability
ANSI X12 version 4010 830 Planning Schedule with Release Capability VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 04/07/00 Trading Partner: All 830 All Partners 4010 Inbound.rtf 1 830 Planning
More informationPortland General Electric Implementation Standard
Portland General Electric Implementation Standard for Electronic Data Interchange TRANSACTION SET 810 Ver/Rel 004010 Invoice Inbound from Vendor 8104010I 1 August 18, 2004 810 Invoice Functional Group
More informationANSI X12 version 4010 856 Advance Ship Notice
ANSI X12 version 4010 856 Advance Ship Notice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 05/01/07 Trading Partner: All 856 All Partners 4010 Outbound.rtf 1 856 Ship Notice/Manifest Functional
More informationANSI X12 version 4010 864 Text Message
ANSI X12 version 4010 864 Text Message VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/22/00 Trading Partner: All Partners 864 All Partners 4010 Inbound.rtf 1 Superior Essex 864 Text Message
More information850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft
850 Purchase Order X12/V4030/850: 850 Purchase Order Version: 1.0 Draft Author: Supplier Automation Trading Partner: Ross Stores, Inc. Notes: This is the standard guide prepared by JPMC/Xign for Merchandise
More informationBORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE
BORGWARNER IMPLEMENTATION GUIDELINE FOR V4010 830 PLANNING SCHEDULE 1 Implementation Guideline 830 3-Jun-15 830 BorgWarner Material Release v004010 Functional Group ID=PS Introduction: This Standard contains
More informationElectronic Data Interchange
Electronic Data Interchange Transaction Set: 850 Supplier Purchase Order ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply
More information3/31/08 ALTRA INDUSTRIAL MOTION Invoice - 810. Inbound 810 X12 4010. Page 1 Created by Ralph Lenoir
Inbound 810 X12 4010 Page 1 DOCUMENT OVERVIEW This document contains the requirements for the standard EDI 810 document in ANSI version 4010 as d by ALTRA INDUSTRIAL MOTION. It describes the layout, syntax,
More information2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY
2.8 861 Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY INFORMATION TMM REQUIRES FROM TRADING PARTNER SCOPE THIS INFORMATION INCLUDES START-UP INFORMATION SPECIFIC TO TRADING PARTNER. APPROACH
More informationEDI GUIDELINES INVOICE 810 VERSION 4010
EDI GUIDELINES INVOICE 810 VERSION 4010 Rev. 7/23/2013 GLOSSARY OF TERS Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each preceded by an element separator,
More information810 Invoice Revised 01/26/15
Functional Group ID=IN Introduction: This Standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context of an Electronic Data Interchange
More information824 Application Advice
824 Application Advice X12/V4040/824: 824 Application Advice Version: 2.1 Final Author: Insight Direct USA, Inc. Modified: 10/12/2006 824 Application Advice Functional Group=AG This Draft Standard for
More informationImplementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)
Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound (v2002) ICS Interchange Control Structures Functional Group ID= Introduction: The purpose of this standard is to
More informationANSI X12 version 4010 820 Remittance Advice
ANSI X12 version 4010 820 Remittance Advice VERSION: 1.0 FINAL Author: Superior Essex Publication Date: 08/18/00 Trading Partner: All Notes: Remittance Advice 820's are transmitted with payment to the
More information810 Invoice. Version: 2.3 Final. X12/V4010/810 : 810 Invoice. Advance Auto Parts. Publication: 3/17/2014 Trading Partner: Notes:
810 Invoice X12/V4010/810 : 810 Invoice Version: 2.3 Final Author: Advance Auto Parts Company: Advance Auto Parts Publication: 3/17/2014 Trading Partner: Notes: Table of Contents 810 Invoice... 1 ISA
More informationVERSION: ANSI X-12 004010
855 Purchase Order Acknowledgment VERSION: ANSI X-12 004010 Author: Family Dollar Stores FDS 855 layout ( VMI Order s) 1 For internal only 855 Purchase Order Acknowledgment Functional Group=PR This Draft
More information846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007
846 Inbound Inventory Advice WITH VENDOR DIRECT (TO CONSUMER) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 08/27/2007 The following is an outline of what is expected when receiving VICS
More information84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010. August 21, 2007
84 LUMBER ELECTRONIC DATA INTERCHANGE VENDOR IMPLEMENTATION PROGRAM INFORMATION PACKAGE 810 INVOICES VERSION 4010 August 21, 2007 1 of 16 84 LUMBER EDI PROFILE 1. 84 LUMBER PERSONNEL Linda Smitley, EDI
More informationACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.
ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X12 4010 *NOTES: PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS. EXISTING DOCUMENT - SEE HIGHLIGHTED FIELDS FOR NEW ADDITIONS PLEASE REVIEW
More informationImplementation Guidelines: ANSI X12 Transaction Set 850 Purchase Order (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier
Implementation Guidelines: ANSI X12 Transaction Set 850 (Suppliers) DOCUMENT NUMBER: ICS 004010 850 S Supplier ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg
More informationInvoice. Transaction Set (810) (Outbound from TI)
Invoice Transaction Set (810) (Outbound from TI) ANSI X12 Version Format: 3020 Date: October 1996 Copyright 1996 Texas Instruments Inc. All Rights Reserved The information and/or drawings set forth in
More informationElectronic Data Interchange
Electronic Data Interchange Transaction Set: 856 Supplier Advance Ship Notice ANSI X12 Version 4010 This specification covers the requirements for Grainger and our Business Units. Grainger Industrial Supply
More information810 Invoice ANSI X.12 Version 5010
810 Invoice SI X.12 Version 5010 *** HEADE AEA *** SEG SEGMENT EQ MAX LOOP NAME DES USE EPEAT ISA Interchange Control Header M 1 GS Functional Group Header M 1 ST Transaction Set Header M 1 BIG Beginning
More informationElectronic Data Interchange (EDI) Standards 810 Invoice Version 4010
Electronic Data Interchange (EDI) Standards 810 Invoice Version 4010 Approved: 07/26/2010 Authors: Dave Danko HCR ManorCare is a leading provider of short and long term medical and rehabilitation care.
More informationX12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O)
X12 Implementation Guidelines For Outbound Receiving Advice v002001 (861O) 861 Receiving Advice/Acceptance Certificate Introduction: Functional Group ID=RC This Draft Standard for Trial Use contains the
More informationEDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message
EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft Standard for Trial Use contains the format
More informationADOBE ANSI X12 810 4010. Version: 1.0
ADOBE ANSI X12 810 4010 Version: 1.0 Author: Adobe Systems Modified: 06/15/2009 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes the data contents of
More informationThe EDI 810 specification is separated into logically distinct groups, which are composed of particular segment types.
EDI 810 File Format Direct Commerce (DCI) supports the EDI 810 format for uploaded invoice transactions. This document describes our implementation of the EDI 810 format for invoicing Carolinas Healthcare
More informationANSI X12 4010 867 - Product Transfer and Resale Report
ANSI X12 4010 867 - Product Transfer and Resale Report Version: R8674010v1 Draft Modified: 10/27/2004 Notes: 10/26/2004 - In an effort to validate that 100% of a partners reporting locations have been
More information860 Purchase Order Change Request Buyer Initiated
860 Purchase Order Change Request Buyer Initiated Set Number - 860 Set Name Purchase Order Change Request Buyer Initiated Functional Group - PC This Draft Standard for Trail Use contains the format and
More informationUnified Grocers 820 EFT Specifications Remittance Advice Document Structure
Unified Grocers 820 EFT Specifications Remittance Advice Document Structure LEVEL SEGMENT NAME Req Max Use Envelope Header ISA Interchange Header M 1 GS Group Header M 1 ST Transaction Set Header M 1 Loop
More informationEDI GUIDELINES PURCHASE ORDER 850 VERSION 4010
EDI GUIDELINES PURCHASE RDER 850 VERSIN 4010 Rev. 7/23/2013 GLSSARY F TERS BLACKHAWK NETWRK s 850 GUIDELINES Seg. Use: Reference : Number: : Consists of a segment identifier, one or more data element each
More informationBLUE CROSS AND BLUE SHIELD OF LOUISIANA DENTAL CLAIMS COMPANION GUIDE
BLUE CROSS AND BLUE SHIELD OF LOUISIANA CLAIMS Table of Contents I. Introduction... 3 II. General Specifications... 4 III. Enveloping Specifications... 5 IV. Loop and Data Element Specifications... 7 V.
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 814 Advance Notice of Intent to Drop Request and Response Ver/Rel 004010 814 Advance Notice
More informationImplementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS 004010 824 S
Implementation Guidelines: ANSI X12 Transaction Set 824 DOCUMENT NUMBER: ICS 004010 824 S ESSAR Steel Algoma Inc. Information Systems and Business Process Improvement Author: Greg Masters Effective Date:
More informationSupply Chain Merchandise Logistics E-Commerce Purchase Order
Supply Chain Merchandise Logistics E-Commerce Purchase Order E-Commerce Purchase Order Page 1 of 53 Contents Introduction 3 E-Commerce ordering How Myer Orders merchandise 4 Purchase order format 4 Basic
More informationX12 Implementation. Guidelines. For. Transfer Version 3030. (996o)
X12 Implementation Guidelines For Outbound ss File Transfer Version 3030 (996o) 996_3030 (003030) 1 April 29, 2003 996 File Transfer Functional Group ID=FT Introduction: This Draft Standard for Trial Use
More informationEDI IMPLEMENTATION GUIDE. 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel)
EDI IMPLEMENTATION GUIDE 856 ANSI X12 V4010 Ship Notice/Manifest Regular (Non Steel) Revision Date: November 7, 2013 Regular (Non Steel) Rev 6 X12 004010 pg. 1 856 Ship Notice/Manifest Introduction: Functional
More informationHIPAA EDI Companion Guide for 835 Electronic Remittance Advice
HIPAA EDI Companion Guide for 835 Electronic Remittance Advice ASC X12 Standards for Electronic Data Interchange Technical Report Type 3 (TR3) Version 005010X221A1 Companion Guide Version: 2.0 Disclosure
More informationEDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X.12-4010 Draft
EDI 210 Invoice Motor Freight 210 Invoice with Stop Offs Version: 1.0 ANSI X.12-4010 Draft Motor Freight Invoice 210 EDI Transaction. ANSI X.12 Standards Version 4010 1 Table of Contents 210 Motor Carrier
More informationANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message
ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message Revised 01/04/11 214 Transportation Carrier Shipment Status Message Functional Group=QM This Draft
More information999 Implementation Acknowledgment. Version: 1.0 Draft
999 Implementation Acknowledgment Version: 1.0 Draft Company: Network Health Publication: 9/11/2012 Table of Contents 999 Implementation Acknowledgment... 1 ISA Interchange Control Header... 2 GS Functional
More informationBill of Lading Number REF02 127 Reference Identification M AN 1/30 MustUse
Updated 05/08/06 810 Invoice Version 005010 X12 Functional Group=IN BIG Beginning Segment for Invoice Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 4 BIG01 373 Date Description: Invoice Date
More informationNote: The following information is required on all Merchandise Invoices:
810 NORDSTROM CANADA Invoice Functional Group=IN Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the
More information276/277 HIPAA Transaction Companion Guide HIPAA/V005010X212 VERSION: 1.0 DATE: 02/05/2014
276/277 HIPAA Transaction Companion Guide HIPAA/V005010X212 VERSION: 1.0 DATE: 02/05/2014 www.aetnaseniorproducts.com 1 Disclosure Statement This material contains confidential, proprietary information.
More information214 Transportation Carrier Shipment Status Message - LTL
214 Transportation Carrier Shipment Status Message - LTL Lowe's 214 - LTL Shipment Status Message Version: 4010 Author: Lowe's Companies, Inc Modified: 2/27/2013 Notes: This 214 Implementation Guide should
More informationGeisinger Health Plan
Geisinger Health Plan Companion Guide for the 820 Payroll Deducted and Other Group Premium Payment for Insurance Products Refers to the Implementation Guides Based on X12 version 004010A1 Version Number:
More informationCVS/Caremark. Implementation Guide. 810 RX DC Invoice. Version X12-4010
CVS/Caremark Implementation Guide 810 RX DC Invoice Version X12-4010 810 Mapping Specifications v4010 i Table of Contents 810 Invoice... 1 ST Transaction Set Header... 2 BIG Beginning Segment for Invoice...
More information867 Product Transfer and Resale Report Ver/Rel 003060. Electronic Data I nterchange. Utility Industry Group Implementation Guideline.
Utility Industry Group Implementation Guideline for Electronic Data I nterchange TRANSACTION SET 867 Product Transfer and Resale Report Ver/Rel 003060 Acid Rain Allowance Transfer Reporting to the U.S.
More informationUltramar Ltd IMPLEMENTATION GUIDE
IMPLEMENTATION GUIDE for electronic data interchange November 2002 TABLE OF CONTENTS INTRODUCTION... 1 KEY CONTACTS... 1 EDI STANDARDS... 1 DOCUMENT PROCESSING FREQUENCY... 1 RESPONSIBILITY FOR COMMUNICATION
More information820 Payroll Deducted and Other Group Premium Payment for Insurance Products
Companion Document 820 820 Payroll Deducted and Other Group Premium Payment for Insurance Products This companion document is for informational purposes only to describe certain aspects and expectations
More informationElectronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy
Electronic Data Interchange- Inbound Payments EDI 820/EFT Specifications for Duke Energy To: Electronic Data Interchange (EDI) Partners: The following pages contain layout specifications for EDI/EFT transmissions
More informationKANSAS CITY SOUTHERN EDI On-Boarding Guide
KANSAS CITY SOUTHERN EDI On-Boarding Guide EDI Standards and Requirements v1.0 2015 by Kansas City Southern 1 Table of Contents 1.0 INTRODUCTION... 3 1.1 INTRODUCTION... 3 1.2 PURPOSE OF THE DOCUMENT...
More information944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice
944 Warehouse Stock Transfer Receipt Advice X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice Author: Tim Wright Company: Created: 09/04/2012 Current: 09/04/2012 Table of Contents 944 Warehouse
More information997 Functional Acknowledgment
997 Functional Acknowledgment Version: 1.0 Draft Author: Margie Stewart Publication: 06/10/2013 Notes: Table of Contents 997 Functional Acknowledgment.......................................................................................
More informationCustomer EDI Guidelines United States 810 Invoice
Customer EDI Guidelines United States 810 Invoice Author: CSC Consulting EMD 810_USA.doc 1 For internal only 810 Invoice Functional Group=IN This Draft Standard for Trial Use contains the format and establishes
More information835 Claim Payment/Advice
Companion Document 835 835 Claim Payment/Advice Basic Instructions This section provides information to help you prepare for the ANSI ASC X12 Claim Payment/Advice (835) transaction. The remaining sections
More information997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.
This document defines Safeway Inc. s guidelines of EDI Transaction Set 824, Application Advice, VICS Version 004010. It does not vary from the X12/UCS/VICS standards. Only segments and elements that are
More informationDoD Transportation Electronic Data Interchange (EDI) Convention
Department of Defense DoD Transportation Electronic Data Interchange (EDI) Convention ASC X12 Transaction Set 824 Application Advice Invoice Acknowledgment (004010) INITIAL DRAFT August 2003 20030829 TTC
More information837I Health Care Claims Institutional
837 I Health Care Claim Institutional For Independence Administrators - 1 Disclaimer This Independence Administrators (hereinafter referred to as IA ) Companion Guide to EDI Transactions (the Companion
More informationHIPAA X 12 Transaction Standards
HIPAA X 12 Transaction Standards Companion Guide 837 Professional/ Institutional Health Care Claim Version 5010 Trading Partner Companion Guide Information and Considerations 837P/837I June 11, 2012 Centene
More informationElectronic Document Interchange Standards Version 5050
Yazaki North America, Inc. Electronic Document Interchange Standards Version 5050 Dear Supplier. Enclosed you will find current versions of our EDI Document Guidelines for our Suppliers that are shipping
More informationVirginia Implementation Standard
Virginia Implementation Standard For Electronic Data Interchange TRANSACTION SET 867 Product Transfer and Resale Report Historical Usage Ver/Rel 004010 VA 867 Historical Usage (4010) 1 867hu-stan2-3.doc
More informationRANDOM HOUSE. EDI Implementation Guide. 850 Purchase Order X12 Version 4010
RANDOM HOUSE EDI Implementation Guide X12 Version 4010 Effective: 6-26-2006 Notes: The Random House EDI Implementation Guide for the 850 transaction documents only the segments and elements used by the
More informationPurpose of the 270/271 Health Care Eligibility Benefit Inquiry and Response
Oklahoma Medicaid Management Information System Interface Specifications 270/271 Health Care Eligibility Benefit Inquiry and Response HIPAA Guidelines for Electronic Transactions - Companion Document The
More informationTransaction Set 824 - Application Advice
TS 824 for TS 264 in X12 Version 003040 IMPLEMENTATION GUIDE Transaction Set 824 - Application Advice Transaction set (TS) 824 can be used to provide the ability to report the results of an application
More information837 I Health Care Claim Institutional
837 I Health Care Claim Institutional Revision Number Date Summary of Changes 6.0 5/27/04 Verbiage changes throughout the companion guide 7.0 06/29/04 Updated to include the appropriate AmeriHealth qualifier
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS APPLICATION ADVICE (824) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 002040CHRY FCA
More informationEDI Specifications. 856 - Advance Ship Notice (Supplier v4010)
(Supplier v400) December 200 856 Ship Notice/anifest- Functional Group=SH VER. 400 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer
More information810 - Invoice. Set Number - 810 Set Name - Invoice Functional Group - IN
810 - Invoice Set Number - 810 Set Name - Invoice Functional Group - IN This standard contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More informationHIPAA - ASC X12N Outbound EDI 835 Electronic Remittance Advice Transaction
HIPAA - ASC X12N Outbound EDI 835 Electronic Remittance Advice Transaction HIPAA Transaction Companion Guide Refers to the X12N Implementation Guide ANSI Version 4010 X091A1 Version 1.0 Date: November13,
More information837 Professional Health Care Claim
Companion Document 837P 837 Professional Health Care Claim Basic Instructions This section provides information to help you prepare for the ANSI ASC X12N 837 Health Care transaction for professional claims.
More informationEDI GUIDELINES. Motor Carrier Load Tender 204 VERSION 004010
EDI GUIDELINES otor Carrier Load Tender 204 VERSION 004010 ASC X12 Version 4010 1 April 5, 2007 204 otor Carrier Load Tender Functional Group ID=S Introduction: This Draft Standard for Trial Use contains
More informationMazda North American Operations EDI Supplier Documentation October 20, 2015
EDI Supplier Documentation October 20, 2015 March 2006 Revision History Merged separate files into this one document Sept 13, 2007 Revised 856 BSN, Element 02, on page 101 Aug 18, 2008 Revised sample 830
More informationDart Container Corporation. EDI 810 Outbound Invoice Version 4010
Dart Container Corporation EDI 810 Outbound Invoice Version 4010 HEADER SECTION ST - Transaction Set Header 01 Transaction Set Identifier N0 1/10 810 02 Transaction Set Control Number AN 4/9 Unique Sequence
More informationEDI Specifications. 810 - Invoice (Supplier v4010)
(Supplier v400) December 200 80 Purchase rder - Functional Group=IN VER. 400 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer Invoice
More informationVDP Program Vendor Guidelines
AutoZone Merchandising Systems Vendor Reference VDP Program Vendor Guidelines (EDI X12 version 004010) Revised by Dept. 8309 EDI group February 2007 Portions of this document contain hyperlinks that are
More informationEaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010
Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010 Revision date: 12/15/2003 Author: Kathy Grubar Copyright 2003 Eaton Corporation. All rights reserved.
More informationElectronic Transaction Manual for Arkansas Blue Cross and Blue Shield FEDERAL EMPLOYEE PROGRAM (FEP) Dental Claims
Electronic Transaction Manual for Arkansas Blue Cross and Blue Shield FEDERAL EMPLOYEE PROGRAM (FEP) Dental Claims HIPAA Transaction Companion Document Guide Refers to the X12N Implementation Guide: 005010X224A2:
More information810 Invoice. Introduction: Heading: Functional Group ID=IN
810 Invoice Functional Group ID=IN Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Invoice Transaction Set (810) for use within the context
More informationHow To Use Ansi X12N For A Business
Chapter 4 Process Flow The Enterprise EDI Gateway (Gateway) is a critical component to the process of exchanging electronic transactions with trading partners. Its programs expedite the movement of transactions
More informationBIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010
BIG LOTS STORES INC. IMPLEMENTATION SPECIFICATIONS ASC X12 INVOICE TRANSACTION SET 810 VERSION 5010 Last revised 3/2/2015 9:47:55 AM - 1 - Summary of Changes 2012 Changes Return merchandise must be on
More informationNow, suppliers can also select EDI as a method for receiving Change and Cancel Orders.
850 Purchase Order Functional Group ID=PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within
More informationToyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira
Toyota Boshoku America EDI Implementation Manual Version 1 for: TBA o TBIN o TBMS o TBCA - Woodstock o TBCA - Elmira Forward The widespread implementation of EDI (Electronic Data Interchange) throughout
More informationDetail SE Transaction Set Trailer Summary GE Functional Group Trailer Summary IEA Interchange Control Trailer Summary. ISA Interchange Control Header
820 Payment Order / Remittance Advice Segment ID Description Location ISA Interchange Control Header Heading GS Functional Group Header Heading ST Transaction Set Header Heading 1 BPR Beginning Segment
More informationCVS/Caremark. Implementation Guide. 852 Product Activity Data Warehouse Movement. Version X12-4010
CVS/Caremark Implementation Guide 852 Product Activity Data Warehouse Movement Version X12-4010 852 Mapping Specifications v4010 i Table of Contents 852 Product Activity Data... 1 ST Transaction Set Header...
More informationIntroduction. Companion Guide to X12 Transactions version 5010
Introduction Companion Guide to X12 Transactions version 5010 Introduction: Table of Contents Table of Contents: Introduction Overview... 1 Purpose... 1 Content... 1 Document Structure... 1 Term Usage...
More information837 Health Care Claim: Institutional Companion Guide. HIPAA version 5010
837 Health Care Claim: Institutional Companion Guide HIPAA version 5010 Version 1.6.3 Status: Published October 28, 2015 Blue Cross & Blue Shield of Rhode Island is an independent licensee of the Blue
More informationFlorida Blue Health Plan
FLORIDA BLUE HEALTH PLAN COMPANION GUIDE Florida Blue Health Plan ANSI 270/271- Health Care Eligibility and Benefit Inquiry and Response Standard Companion Guide Refers to the Technical Report Type Three
More informationIMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET
IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET FCA US INFORMATION & COMMUNICATION TECHNOLOGY MANAGEMENT ANSI ASC X12 VERSION/RELEASE 003020 996 File Transfer
More informationState of Tennessee Department of Revenue
State of Tennessee Department of Revenue PET 350 - Distributor Monthly Fuel Tax Return PET 368 - Blenders Return PET 372 - Petroleum Products Terminal Return PET 373 - Petroleum Products Transporter Return
More informationAdministrative Services of Kansas
Administrative Services of Kansas ANSI X12N 837D V4010A1 Health Care Claim Companion Guide - Dental, INC BlueCross BlueShield of Western New York BlueShield of Northeastern New York Last Updated March
More information856 Advanced Shipping Notices (ASN)
NEXTEER Supplier Information Packet 856 Advanced Shipping Notices (ASN) Revised March, 2010 s GENERAL INFORMATION This packet is to provide information to Nexteer and SteeeringMex Direct Suppliers who
More informationACH Implementation Guide for Electronic Funds Transfer: Industry
ACH Implementation Guide for Electronic Funds Transfer: Industry NIPR Version 1.3 October 2012 NIPR NATIONAL INSURANCE PRODUCER REGISTRY For more information, please contact: NIPR Marketing Department
More informationBlue Cross and Blue Shield of Illinois (BCBSIL)
Blue Cross and Blue Shield of Illinois (BCBSIL) HIPAA Transaction Standard Companion Guide 270/271 Health Care Eligibility Benefit Inquiry and Response Version 1.0 BCBSIL December 2012 A Division of Health
More information837P Health Care Claim Professional
837P Health Care Claim Professional Revision summary Revision Number Date Summary of Changes 6.0 5/27/04 Verbiage changes throughout the companion guide 7.0 06/29/04 Updated to include the appropriate
More informationCombined Insurance Company of America
Combined Insurance Company of America Companion Guide Combined Insurance Company of America HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on X12 version 004010 Companion
More information835 Health Care Payment/ Remittance Advice Companion Guide
835 Health Care Payment/ Remittance Advice Companion Guide Version 1.6 April 23, 2007 Page 1 Version 1.6 April 23, 2007 TABLE OF CONTENTS VERSION CHANGE LOG 3 INTRODUCTION 4 PURPOSE 4 SPECIAL CONSIDERATIONS
More information