TEXAS INSTRUMENTS. Acknowledge / Rejection Advice Message CONTRL. Based on EDIFICE Issue 1 (Based on EDIFACT Version 92.1)



Similar documents
EDIFACT Standards Overview Tutorial Learn About Key E-commerce Trends and Technologies at Your Own Pace

S.2.2 CHARACTER SETS AND SERVICE STRING ADVICE: THE UNA SEGMENT

R.2 STRUCTURE OF AN EDIFACT TRANSMISSION

PURCHASE ORDER RESPONSE

EDIFACT Standards Overview Tutorial

EDIFACT MESSAGE IMPLEMENTATION GUIDELINES RECEP:0:2:FH:

997 Functional Acknowledgment

Invoice. Transaction Set (810) (Outbound from TI)

EDI Compliance Report

Adobe - EDIFACT D97.A ORDERS

SECTION VI - EDIFACT message formatting

COPRAR EDIFACT User Guide Page 2

EDIFACT DESADV D.97A for suppliers (Benteler Europe)

Issue 1.1, February agreed-upon by EDI Working Group of ECR Poland

ORDERS 92.1 EDI GUIDELINE. for. Message Type ORDERS, ORDCHG Version 1 Release 921. ORDERS, ORDCHG Version /2011 Page 1

Media Saturn EDI Application Documentation

Grundfos EDIFACT D.96.A

Revision : 1 Date :

DELJIT D97A / CALDEL

Hella EDIFACT INVRPT

Bulk EDIFACT ASN MESSAGE FORMAT

Appendix report 1: Syntax and structure of EDIFACT and XML messages Regulation F1:

INVOIC Invoice message

PARTY INFORMATION MESSAGE. PARTIN Version 1.0. agreed-upon by EDI Working Group of ECR Poland

Eaton Corporation Electronic Data Interchange (EDI) Standards Application Advice (824) Version 4010

EANCOM 2002 PART III

B/L-EDIFACT. EDI-Scenarios (Confirmation Messages For The Transmission Of B/L Data) Version 2.0e

DES150: Electronic Data Interchange (EDI) Specification

Purchase Orders Message ORDERS (EDIFACT D97A)

EDIFACT TIS. Version 6.0 January EDCS EDIFACT Technical Interface Specification Version 6.0 Title Page HM REVENUE & CUSTOMS

ZF Group North American Operations. EDI Implementation Guide

Implementation Guidelines For ANSI X12 Interchange Control Structures Inbound & outbound. (v2002)

X12 Implementation. Guidelines. For. Transfer Version (996o)

EDI Agreement EDI AGREEMENT. Article 1: Object and scope. Article 2: Definitions

IMPLEMENTATION GUIDELINES FOR ANSI ASC X12 EDI CONVENTIONS FILE TRANSFER (996) TRANSACTION SET

THE INVOIC MESSAGE EANCOM97/EDIFACT D.96A

SCTS-AIS Swedish Customs Technical Specifications for Automated Import System ICS phase 1 Appendix C Codelists Version 1.0.

INTRODUCTION TO EDIFACT. presented by EIDX

INVENTORY REPORT MESSAGE INVRPT. Version 1.2. agreed-upon by EDI Working Group of ECR Poland

Payment on Receipt EDIFACT INVOIC D97.A

Global EDI Clearing Center (GECC)

ORDERS Purchase Order Message

PRICE/SALES CATALOGUE MESSAGE PRICAT. Version 1.0. agreed-upon by EDI Working Group of ECR Poland

EDI 214 ANSI X12 Version 4010 Transportation Carrier Shipment Status Message

EPIC. EDI Core Standards VM

BORGWARNER IMPLEMENTATION GUIDELINE FOR V PLANNING SCHEDULE

EDI F GROUP A/S INVOICE. Fona. Document: EDIFACT UserGuide GB-INVOIC_IBM-draft1 Date: 5/ Version: V1.0.0A Page 0 of 43. ecommerce ServiceCenter

How To Use Ansi X12N For A Business

824 Application Advice

Combined Insurance Company of America

CUSRES Customs Response Message

ANSI X12 version Text Message

Electronic Data Interchange (EDI)

IBM Gentran:Server for Microsoft Windows. HIPAA and NCPDP Compliance Guide

999 Implementation Acknowledgment. Version: 1.0 Draft

EDI GUIDELINES. Motor Carrier Load Tender 204 VERSION

Aleph Requirements for EDI -Outgoing and Incoming Messages

Receiving Advice/Acceptance Certificate - SERVICE PARTS ONLY

X12 Implementation Guidelines For Outbound Receiving Advice v (861O)

EDI GUIDELINES INVOICE 810 VERSION 4010

EANCOM D.96A Version: 007 Print: EAN ORDERS D.96A DE

944 Warehouse Stock Transfer Receipt Advice. X12/V4030/944: 944 Warehouse Stock Transfer Receipt Advice

EDIFACT DELFOR D99B Guideline

Economic and Social Council

Learning Series: SAP NetWeaver Process Orchestration, business to business add-on EDI Separator Adapter

ACE HARDWARE 810 INVOICE (FOR CREDIT MEMO ONLY) ANSI X PLEASE DO NOT TRANSMIT WAREHOUSE OR REBATE CREDIT MEMOS.

997 MUST be sent to Safeway to confirm receipt of 824 transmission. This is unrelated to EDI syntax errors as reported on 997.

ANSI X12 version Planning Schedule with Release Capability

Data Exchange and Protocol Process Flows for Electric Deregulation in The State of New Jersey

DoD Transportation Electronic Data Interchange (EDI) Convention

The information in this document will be common for all X12N implementation guides.

FREQUENTLY ASKED QUESTIONS

ANSI ASC X.12 Standard Version 4010 Transaction Set 214 Transportation Carrier Shipment Status Message

810 Invoice ANSI ASC X12 Version 4010

ANSI X12 version Remittance Advice

Technical Interface Specification for IRL-NCTS. Transit

An Introduction to Unicorn

Portland General Electric Implementation Standard

850 Purchase Order. X12/V4030/850: 850 Purchase Order. Version: 1.0 Draft

THE DELIVERY FORECAST MESSAGE DELFOR EDIFACT D.96A

Electronic Data Interchange

ADOBE - EDIFACT D97A INVOIC

214 Transportation Carrier Shipment Status Message

E A N C O M - MESSAGE

Transaction Set Application Advice

This document has been provided as a courtesy to anyone who wants to learn more about EDI and how it applies to their TrueCommerce solution.

ANSI X12 version Advance Ship Notice

867 Product Transfer and Resale Report Ver/Rel Electronic Data I nterchange. Utility Industry Group Implementation Guideline.

Issue 1.9, April agreed-upon by EDI Working Group of ECR Poland

Implementation Guidelines: ANSI X12 Transaction Set 824 Application Advice DOCUMENT NUMBER: ICS S

ELECTRONIC DATA INTERCHANGE AGREEMENT

EDI 210 Invoice. Motor Freight 210 Invoice with Stop Offs. Version: 1.0 ANSI X Draft

Arkansas Blue Cross Blue Shield EDI Report User Guide. May 15, 2013

Implementation Guideline

276/277 HIPAA Transaction Companion Guide HIPAA/V005010X212 VERSION: 1.0 DATE: 02/05/2014

DEPARTMENT OF HEALTH & MENTAL HYGIENE MEDICAL CARE PROGRAM

DELFOR. Forecast/Calloff outbound UNH M 1 UNS M 1 UNB BGM M 1 UNS M 1 UNT UNZ M 1 M 1 M 1 SG18 R 9999 SG1 SG2 R 5 D 4 RFF NAD DTM LIN M 1 R 1 M 1 M 1

Contents 1. Introduction 2. Segment description 4. Summary of segments used 13. Summary of segments not used 13. Comparison VDA 4906 => ODETTE 13

Transcription:

TEXAS INSTRUMENTS Acknowledge / Rejection Advice Message CONTRL Based on EDIFICE Issue 1 (Based on EDIFACT Version 92.1) Date : January 1997 TI Version 1.0 This document can be found on the World Wide Web from http://www.ti.com/sc/docs/scedi/sctecpak.htm Texas Instruments Incorporated 1 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

Copyright 1997 Texas Instruments Inc. All Rights Reserved The information and/or drawings set forth in this document and all rights in and to inventions disclosed herein and patents which might be granted there on disclosing and employing the materials, methods, techniques, or apparatus described herein are exclusive property of Texas Instruments, Inc. Texas Instruments Incorporated 2 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

Table of Contents TITLE PAGE TABLE OF CONTENTS 3 INTRODUCTION 4 HOW TO USE THIS DOCUMENTATION 5 PURPOSE OF THIS MESSAGE 6 MESSAGE DIAGRAM 7 UNB INTERCHANGE HEADER 8 UNH MESSAGE HEADER 9 UNT MESSAGE TRAILER 10 UNZ INTERCHANGE TRAILER 12 EXAMPLE 13 Texas Instruments Incorporated 3 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

Introduction This guide was developed by members of the Texas Instruments EDI message development Group. It is based on the guide developed by members of the Electronics Industry through the associations representing Europe (EDIFICE), Japan (EIAJ) and the USA (EIDX). It represents and is specific to the usage as specified by Texas Instruments. Texas Instruments Incorporated 4 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

How To Use This Documentation This document was created to aid in your implementation of the CONTRL message. This documentation contains those segments and elements that will be sent for the CONTRL message created by Texas Instruments. A complete description of the segments are outlined in the UN/EDIFACT Standards Manual. If you require/need to be sent additional segments not listed in this documentation, an agreement must be reached with Texas Instruments Incorporated. This document defines the TI preferred structure and content of the EDIFICE endorsed CONTRL message. Segment/Data Element Usage (M) Mandatory = EDIFACT dictates that the Data Element or Segment must be present. (R) Required = EDIFICE members agree that the data concerned must be sent. (D) Depending = The data concerned must be sent if a particular defined condition or set of conditions exists. The associated conditions must be explained at the appropriate level of detail. (A) Advised = Indicates that the RECEIVER of the message would prefer the data concerned to be sent, but does not require its transmission. (O) Optional = Indicates that the transmission of the data concerned is at the need or discretion of the SENDER, i.e. it is not required by the receiver in order to perform its business function. EDIFICE requires that the use of O must be agreed between trading partners. (X) Not Used = The Data Element or Segment will not be used by EDIFICE members. The EDIFICE usage status and number of occurrences for segments or segment groups will be represented analogue to the representation of data elements. e.g.: R3 The segment or group is required 3 times (fixed number) R..3 The segment or group is required up to 3 times (maximum number) Data Element Representation (a) Alpha (an) Alpha Numeric (n) Numeric Enveloping The UNB/UNZ Interchange envelope and the UNH/UNT message envelope are shown in this document in the message diagram. Details on these segments are found separately in the SERSEG document. Texas Instruments Incorporated 5 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

Purpose of this Message The Acknowledgement/Rejection Advice is a message from the recipient of an Interchange back to its sender containing an acknowledgement of receipt or a rejection of the Interchange. Texas Instruments agrees with the EDIFICE recommendation that the Acknowledgement/Rejection Advice (CONTRL) message should NOT be used. However, there may be exceptional cases where a business partner (or government authority) requests in his outgoing message to receive the CONTRL message in return. The use of the CONTRL message should be agreed upon by special agreement. The request to receive a CONTRL message in return may be indicated in the UNB segment. The CONTRL message must be sent in a separate Interchange and consequently be within the service segments UNB and UNZ. Texas Instruments Incorporated 6 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

References UNSM ACKNOWLEDGEMENT/REJECTION ADVICE MESSAGE STATUS 1, SEP. 1989 EDIFACT SEGMENT DIRECTORY 90.1 EDIFACT CODE SET 90.1 EDIFICE SERVICE SEGMENTS ISO 9735 EDIFACT SYNTAX RULES Texas Instruments Incorporated 7 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

Acknowledgement / Rejection Advice (CONTRL) SEG NAME REQ DES MAX USE LOOP REPEAT UNH Message header M 1 UCI Interchange response R 1 UNT Message Trailer M 1 Texas Instruments Incorporated 8 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

UNH - Message Header Function: To head, identify and specify a message. Usage: M1 Remarks: Refer to EDIFICE Utilisation of the EDIFACT Service Segments, Issue 2. Field # Ref. Rep. Field Usage TI Utilisation UNH01 0062 an..14 MESSAGE REFERENCE M See Note 1 NUMBER UNH02 S009 MESSAGE IDENTIFIER M 0065 an..6 Message type identifier M 0052 an..3 Message type version number M 1 0054 an..3 Message type release number M 0 0051 an..2 Controlling agency M UN 0057 an..6 Association assigned code O ED2 UNH03 0068 an..35 COMMON ACCESS X REFERENCE UNH04 S010 STATUS OF THE TRANSFER O 0070 n..2 Sequence message transfer M number 0073 a..1 First/last sequence message transfer indication O UNH Notes 1. DE 0062 MESSAGE REFERENCE NUMBER Transmission message count from 1 Texas Instruments Incorporated 9 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

UCI - Interchange Response Function: To identify the Interchange which is being responded to and to indicate the action taking place i.e. acknowledgement or rejection. Usage: M1 Remarks: Field # Ref. Rep. Field Usage TI Utilisation UCI03 0020 an..14 INTERCHANGE CONTROL REF M See Note 1 UCI01 S002 INTERCHANGE SENDER M See Note 1 0004 an..35 Sender identification M 0007 an..4 Partner ID code qualifier R 0008 an..14 Address reverse rout D See Note 2 UCI02 S003 INTERCHANGE RECIPIENT M See Note 1 0010 an..35 Recipient identification M 0007 an..4 Partner ID code qualifier R 0014 an..14 Routing Address D See Note 2 UCI04 0083 an..14 ACTION CODE M See Note 3 UCI05 0085 an..2 ERROR CODE M See Note 4 Texas Instruments Incorporated 10 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

UCI - Interchange Response UCI Notes 1. The Interchange Sender and Interchange Recipient Identification is copied from the corresponding elements of the UNB of the Interchange being acknowledged, as is the Interchange Control Reference. 2. DE 0008 and DE 0014 are 'Depending' because they are copied directly from the Interchange being acknowledged, where they may or may not have been used. 3. DE 0083 ACTION CODE 4 negative acknowledgement (rejection) 5 positive acknowledgement Until codes are published by EDIFACT codes '4' and '5' are to be used. 4. DE 0085 ERROR CODE Note: This Data Element is currently not supported at Texas Instruments. 1 UNA not supported 10 Data element attribute error 11 Password invalid 2 Syntax not supported 3 Message version/release not supported 4 Service segment missing/invalid 5 Trailer check in error 6 Data segment missing/invalid 7 Addressee in error 8 Too many data elements in segment 9 Mandatory data element missing These codes are requested. Until codes are published by EDIFACT, the above codes are to be used. Texas Instruments Incorporated 11 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

UNT - Message Trailer Function: To end and check the completeness of a message. Usage: M1 Remarks: Refer to EDIFICE Utilisation of the EDIFACT Service Segments, Issue 2. Field # Ref. Rep. Field Usage TI Utilisation UNT01 0074 n..6 NUMBER OF SEGMENTS M IN A MESSAGE UNT02 0062 an..14 MESSAGE REFERENCE NUMBER M Texas Instruments Incorporated 12 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0

Example This example shows that Company ABC rejects the Interchange 000000027 received from Company XYZ. UNH+00000000100001+CONTRL:1' UCI+000000027+COMPANY ABC:US01+COMPANY XYZ:US01+4' UNT+3+00000000100001' Texas Instruments Incorporated 13 of 13 Acknowledgement/Rejection Advice Message (CONTRL) v. 1.0