Topic231 - Interface to SAP - Technical Guide

TRA/X Reference Guide - SAP Technical Guide

TRAXi3 Reference Guide

Topic231 - Interface to SAP - Technical Guide

TRAXi3 Reference Guide

Topic231 - Interface to SAP - Technical Guide

( Precision Software Limited

Precision software products are copyrighted and all rights are reserved by Precision Software Limited.

This document is copyrighted and all rights are reserved. No part of this document may be reproduced, transmitted, adapted, translated or electronically stored without the prior written consent of Precision Software Limited.

TRAXi3 ( i3ship (, i3trade ( i3Comply ( and XM4 ( and are registered trademarks of Precision Software Limited.

Progress ( is a registered trademark of Progress Software Corporation.

Precision Software Limited shall not be liable for errors contained herein or for incidental or consequential damage or loss in connection with the use of this document. Whilst every effort is made to eliminate errors, Precision Software Ltd. cannot be held liable for erroneous information contained herein.

Document Control

Issue Control

Issue

Date

Changes Made

1.0

01 July 05Updated for V61.1

11 July 05Updated Cross Reference

Change Summary

Nr.DescriptionDateBy whom

1Formatting change 23/05/05Mark McMonagle

2TRAXi3 update14/07/05Mark McMonagle

Contents

3Document Control

3Issue Control

3Cross Reference

3Change Summary

6Overview

6SAP & TRAXi3

6SAP Version 4 and Version 3 support

6Discussion

8Documents

9SAP TRAXi3 Interface

9Overview

9IDOC Technology

9Interface Programs

10Running Interface Programs

10Interface Programs Set-up

12Processing an IDOC file

12Reading the IDOC file

12Mapping SAP data to TRAXi3

12Interface Operation

13Idocs Mapping into TRAXi3

14R3 System Parameter Set-up

14Interface

16Master Data Creation

16Order Master Table

161. XMCURR0 - Currency, Short-path - CU

162. XMPTRM0 - Payment Terms, Short-path - PT

163. XMNREF0 - Partner, Short-path - NR

16a) Shipping Officers

16b) Consignees

16c) Customers

164. XTZSTP0 - Transaction Type, Short-path - ZS

165. XMTTYP0 Tax Groups, Short-path TT

166. XMTXRT0 Tax Rates, Short-path TX

177. XMCHRG0 Charge / Revenue, Short-path CH

178. XMCTRY0 Country, Short-path CT

179. XMDLNG0 Language, Short-path DL

1710. XMPBAS0 Postal Code, Short-path PB

1711. XMDELV0 Delivery Terms, Short-path DE

1712. XTZBTX0 Text id Codes, Short-path ZBTX

1713. XMPROD0 Product, Short-path PR

1714. XMNPRD0 Partner Product, Short-path NRNP

1715. XMCMOD0 Commodity, Short-path CM

18Delivery Master Table

181. XMNREF0 Partner, Short-path NR

18a) Consignees

18b) Customers



184. XTZBTX0 Text id Codes, ,Short-path ZBTX


186. XTROUT0 Route, Short-path RT

187. XMTRAN0 Transport Mode, Short-path TR

198. XMCITY0 Place, Short-path PL



20Invoice Master Table


20a) Banks

20b) Consignees

20c) Customers

202. XMDLNG0 Lanuage, Short-path DL



205. XMTTYP0 Tax Groups, Short-path TT

206. XMTXRT0 Tax Rates, Short-path TX


218. XMPTRM0 Payment Terms, Short-path PT

219. XTZBTX0 Text id Codes, Short-path ZBTX



2112. XMCMOD0 - Commodity Short-path CM

22Appendix 1 - IDOC definitions processed by TRAXi3 interface

22Idoc segment structure and field names for the Order Idoc, orders02

32Idoc segment structure and field names for the Delivery Idoc, desadv

39Idoc segment structure and field names for the Export Invoice Idoc, expinv

48Idoc segment structure and field names for the UK Invoice Idoc, invoic

57Appendix 2 - Interface field mapping

57Mapping of Idoc fields to TRAXi3 Database fields for the Orders Idoc, orders02

75Mapping of Idoc fields to TRAXi3 Database fields for the Delivery Idoc, desadv

88Mapping of Idoc fields to TRAXi3 Database fields for the Export Invoice Idoc, expinv

107Mapping of Idoc fields to TRAXi3 Database fields for the UK Invoice Idoc, invoic

124Suggestions for Improved Documentation

Overview

SAP & TRAXi3SAP Version 4 and Version 3 support

The TRAXi3 SAP interface is available for both the SAP Version 3 and Version 4-based IDOC structure; the IDOCs outlined in this document refer to SAP Version 3. While this documentation has not been updated to reflect the new IDOC internal structure, the related TRAX interface programs have been changed accordingly.

Discussion

The information required in TRAXi3 is interfaced from SAP by the use of IDOCS.

The IDOCS are produced by SAP at three stages during the order-sales cycle.

1. The Order Stage

2. The Delivery Stage

3. The Invoices Stage

At the Order stage the initial pricing information is interfaced, based on an Order created in SAP. All further Changes to the Order should produce further Idocs so that the changes can be interfaced into TRAXi3. All of this information can be accessed in TRAXi3 by option, SH ORD.

At the Delivery Stage, a Delivery Idoc will be sent which will contain the Shipping Data, based on the Delivery Created in SAP. This Delivery can be made up of 1 or more Orders.

Most Deliveries in SAP are automatically created, where data may be manually entered in either TRAXi3 or SAP until the Delivery is Goods-Issued, after which the Delivery is closed. The usual procedure is to transmit an Idoc when the Delivery is created if manual input is required in TRAXi3 and another when the delivery is Goods-Issued.

At the Invoice stage, either an Export Invoice IDOC or a domestic Invoice IDOC is produced, based on the country of destination. There is a difference in the IDOC definition between the Export Invoice IDOC and the domestic Invoice IDOC. This Idoc should be produced when the Billing Due list is run in SAP. Only one Invoice Idoc should be transmitted to TRAXi3. The relationship between the Delivery and Invoice is one delivery, one Invoice. The Idoc will contain the final pricing information from SAP, so that any customer Invoice printed from TRAXi3 will contain the same information as in the SAP financials.

The IDOCS produced by SAP are then processed by interface programs used by TRAXi3 and the data is loaded into the TRAXi3 Database.

The IDOCS produced by SAP are placed in a directory by the SAP system. Then using an FTP or an NFS connection between this directory and a specified directory on the TRAXi3 NT server, the IDOCS get transferred from one machine to the other.

Once on the TRAXi3 NT server, the IDOCS go through a three-stage process. The stages are as follows.

1. Scan

2. Process

3. Archive

In the Scan stage, the Idocs are held for processing.

In the Process Stage, the Idocs are processed and the data interfaced into the TRAXi3.

The Archive stage is where processed Idocs are held.

Figure 1 IDOC interface overviewDocuments

The Documents that are required to print can be printed in three stages, as follows:

1. Orders Stage Documents

2. Delivery Stage Documents

3. Invoices Stage Documents

As with the Idoc processing, this is a three-stage process which reflects the relationship between the data sent in the Idoc and the information appearing on the Document.

All pre-printed stationery for a Laser Printer has to be manually printed, if there is no dictated tray. The macros for documents are created with the Tray field ticked to ManInpPaper, i.e. Manual feed, so the pre-printed paper will have to be feed to the Printer when required.

SAP TRAXi3 Interface

Overview

This section describes the interface between TRAXi3 and SAP. The interface was developed by making use of the IDOC technology, supplied by SAP. In simple terms, the SAP system can output data to text files in predefined formats dependent on certain events. This information can then be processed by TRAXi3 and updated into the database for use within the TRAXi3 system. Once the IDOC system is set up within SAP, the interface between SAP and TRAXi3 occurs automatically, and is seamless to the user.

IDOC Technology

SAP incorporates a concept known has IDOC which allows SAP and non-SAP applications to communicate. This feature was introduced to standardise and simplify interfaces between SAP systems and external systems. It is similar to EDI in that structures are defined which specify the data and the format of the data to be transferred.

These structures are known as IDOC types; SAP is supplied with a number of standard IDOC types but users can develop their own, if they require. The TRAXi3 interface makes use of the standard types. IDOC types consist of segments with each segment containing additional segments or data field definitions.

The SAP system can be set up in such a way that when a particular event happens (e.g. an invoice is created), an IDOC file is created with the details of the transaction. The format of the IDOC text file created is dependent on the IDOC structure associated with the event. Once a transaction is processed within SAP, the data is available within TRAXi3 for further processing.

Interface Programs

Four Programs were developed to handle the interfacing of data from SAP to TRAXi3 for each of the three stages. There are two programs for the invoice stage, as there are two possible Idoc structures this stage.

1. The Order Stage.

The interface Program for this stage is orders.p.

2. The Delivery Stage.

The interface Program for this stage is desadv.p.

3. The Invoice Stage.

As two different Idoc formats can be sent across at this stage, two different programs were developed.

- The interface Program for Export Invoice: expinv.p.

- The interface Program for Domestic Invoices: invoic.p.

Running Interface Programs

In the running of the Idoc interface processing, the following Programs handle the three stage processing of the Idocs.

The Program, IDOCSCAN.r, handles the stage from Scan to Process. This program creates a background task, deciding what is the Idoc type; for example, an Order Idoc or a Delivery Idoc, and then assigns the correct program to handle it. The Program assigned is one of those described in section 2.3 and the Idoc is moved on to the Process stage.

The Program, IDOCPROC.r, handles the stage from Process to Archive. This program processes the background tasks created in the previous stages, using the assigned program.

The Idoc is then moved on the Archive stage where it is stored after processing.

Interface Programs Set-up

The following procedures should be followed for setting up the programs, IDOCSCAN.r, IDOCPROC.r, on the TRAXi3 NT server, so that they can interface data across while running in the background.

Create a shortcut to each of the Programs with the following properties:

- Shortcut to IDOCSCAN.r

- Target field in Properties:

V:\83A\bin\prowin32.exe -pf N:\trax.XX\traxtest.pf -ininame

N:\trax.XX\traxbtch.ini

The traxtest.pf file would contain the following:

-db XTTRAXMU

-N TCP

-S xttraxntXXdev

-H cslnt4

-p N:\trax.XX\APP\IDOCSCAN.r

-inp 20000

-tok 1600

-t

-T N:\trax.XX\temp

-d dmy

-nb 200

-yy 1990

-n 60

-s 63

-param 001,PRT01,Print

The Important values in traxbtch.ini are

DLC=v:\83a

PROBUILD=v:\83a\probuild

PROPATH=n:\trax.XX\app,c:\trax\bitmaps,v:\trax.XX\__\_std\bitmaps,v:\trax.XX\_\nt\app,v:\trax.XX\__\nt\app,v:\trax.XX\__\_std\help

Shortcut to IDOCPROC.r

Target field in Properties :

V:\83A\bin\prowin32.exe -pf N:\trax.XX\traxtest.pf -ininame

N:\trax.XX\traxbtch.ini

The traxtest.pf file would contain the following:

-db XTTRAXMU

-N TCP

-S xttraxntXXdev

-H cslnt4

-p N:\trax.XX\APP\ IDOCPROC.r

-inp 20000

-tok 1600

-t

-T N:\trax.XX\temp

-d dmy

-nb 200

-yy 1990

-n 60

-s 63

-param 001,PRT01,Print

The Important values in traxbtch.ini are

DLC=v:\83a

PROBUILD=v:\83a\probuild

PROPATH=n:\trax.XX\app,c:\trax\bitmaps,v:\trax.XX\__\_std\bitmaps,v:\trax.XX\_\nt\app,v:\trax.XX\__\nt\app,v:\trax.XX\__\_std\help

The programs can then be started by double-clicking the Icons.

Once the programs have been started, any Orders, Delivery, or Invoice Idocs sent from SAP will be automatically processed and the data placed into the TRAX Database.

To assign the directories that the interface requires, the following should be done:

1. Go to the system values screen, (short-path: Y2)

2. Select the category, R3, and go to the sub-options (F11) for this category

3. Enter the required values for the following Key values

IDOC SCAN PATH

E.g. C:\trax.XX\idoc\Scan

IDOC PROCESSING PATH

E.g. C:\trax.XX\idoc\Process

IDOC ARCHIVE PATH

E.g. C:\trax.XX\idoc\Archive

Processing an IDOC file

This section contains details on the methods used to process IDOC files within TRAXi3. The interface is divided into two distinct parts within TRAXi3: The first part physically reads the data from the IDOC text file; the second part maps the SAP data to the TRAXi3 table structures.

Reading the IDOC file

Each IDOC type within SAP produces a different file structure depending on the segments used within the IDOC definition. SAP supplies programs which allow users to report on the structure of IDOC types. One such report is the IDOC Type Overview. This report provides details of each segment, each field in each segment and a description of each field.

Precision software has developed an interpreter which takes this report and generates PROGRESS 4GL programs which can be used to read data from the IDOC file into standard PROGRESS structures. The data is then available to be used within other PROGRESS programs. This automated method of program generation allows Precision to very quickly develop programs which can read any IDOC structure within SAP. Once the data is available in TRAXi3, it is then a matter of mapping this data to the TRAXi3 database structures.

Mapping SAP data to TRAXi3This part of the interface is programmed manually. This is where the business logic is applied to provide mappings from the SAP data to the TRAXi3 data. See below for details of the mapping.

Interface Operation

The operation of the interface between SAP and TRAXi3 must be seamless to the user. Precision provides mechanisms for automating the interface based on the system configuration of TRAXi3 and SAP. Each method ultimately creates a request for the TRAXi3 Background Task Management System (see Server Background Processing document for more information) to complete.

When the IDOC message is generated within SAP, the SAP system runs a script based on the Port Definition. Currently TRAXi3 can work in two ways. (i) The first way is used when the TRAXi3 database and SAP application server are running on the same NT host. A Progress process runs in the background, which waits for filenames to be passed to a named directory. When the process receives an IDOC filename, it creates a task to be processed by the TRAXi3 background manager. Each time the TRAXi3 background process monitors the named directory, it will check this directory for entries and will process any files it finds.

(ii) The second method is used when the TRAXi3 database and the SAP application server are on different machines. The script file is used to FTP the IDOC file into a directory, which is accessible by TRAX from an NT Server. TRAXi3 will initiate a program which checks this directory for new entries; each time a new entry is made, a background task will be created which will be processed by the TRAXi3 Background Task Management System. If both systems are running on different machines but have access to common directories (network drives, NFS mounted file systems, and so on) there does not have to be a script associated with the SAP port definition. As the IDOC files are created, TRAXi3 will automatically create tasks using the same method as above; that is, polling the directory for new entries.

The task generated above has a program associated with it. For each IDOC type to be processed through TRAXi3, a program will be generated which will be capable of reading the IDOC format and populating standard PROGRESS structures with the data. These programs will have the same name as the IDOC types. The program associated with the task is determined by reading the control segment of the IDOC file to find the IDOC type which is being processed - and then using that as the program name. This program, in turn, calls the data-mapping program, which populates TRAXi3 tables with the IDOC information. If the rulebooks (see TRAXi3 Online Documentation CD-ROM) are in use within TRAXi3, the rule processing will be executed to generate default data. This information can then be processed within TRAXi3 in the same way as data which was manually entered. Each IDOC file processed by TRAXi3 is sent to an archive directory.

The system users need not know anything about the interface. As far as they are concerned, the data is entered in SAP and is then available for processing within TRAXi3. The processing which happens behind the scenes need not concern them. The IDOC processing within SAP can be run immediately or in batch mode depending on the requirements of each individual customer.

Idocs Mapping into TRAXi3This section details the mapping of the SAP IDOC structures to the TRAXi3 structures. Some fields in the IDOC structure may have no corresponding fields within TRAXi3, in which case the TRAXi3 fields column will be left blank. Where more than one field is mentioned in the TRAXi3 fields column, this is due to fact that some of the information will be used to populate both the transaction table field and the master record, to which that field is also associated. For example, the partner number may be mapped to a shipment partner field but may also be mapped to the partner number on the partner record.

The Idocs mapped at the various stages are as follows.

Order Stage Orders02

Delivery Stage Desadv

Invoice Stage Expinv, for export Invoices. Invoic, for Domestic Invoices

R3 System Parameter Set-up

Interface

The system parameters can be set by going to system values (short-path: Y2) in the category R3.

PARTNER REMOVE LEADING ZEROS: If this parameter is set to Yes, all partner IDs interfaced over from SAP will have any leading zeros removedSHIPMENT REMOVE LEADING ZEROS: If this parameter is set to Yes, all delivery or invoice numbers interfaced over from SAP will have any leading zeros removed.PRODUCT REMOVE LEADING ZEROS: If this parameter is set to Yes, all product IDs interfaced over from SAP will have any leading zeros removed.

INVOICE REMOVE LEADING ZEROS: If this parameter is set to Yes, all product IDs interfaced over from SAP will have any leading zeros removed.

DELIVERY REMOVE LEADING ZEROS: If this parameter is set to Yes, all product IDs interfaced over from SAP will have any leading zeros removed.

COPY TEXT IDS: This value can be used to set up a list of Test IDs, to be copied over from a delivery to its invoice document. IDOC Archive Location: This value is used to store the location that the Idoc is moved to, once it is finished processing.DEFAULT CONSIGNOR: This value is used to store a default consignor to a shipment if the interface hasnt picked one up from an Idoc.DELETE EXISTING SHIPMENTS: This value is used to store a default consignor to a shipment, if the interface hasnt picked one up from an Idoc.CREATE BATCH DETAILS: If this parameter is set to Yes, Lot records will be created for each item line, if batch information is present on the Idoc.IDOC PROCESSING PATH: This value is used to store the location that the Idoc is moved to, once it is ready for processing.IDOC ARCHIVE PATH: This value is used to store the location that the Idoc is moved to, once it is finished processing.QUEUE NAME: This value is used to store the name of the background queue that the interface is running on.NUMERIC FORMAT: This value is used to store the numeric format that is to be used when processing the Idoc i.e. "American" OR "European".

DEFAULT CLIENT: This value is used to store the Client to be used in the Transaction tables when the interface is running.INTERFACE TYPE: This value is used to store the description of the Interface.

POLLING PERIOD: This value is used to control how often the interface runs, e.g. 60 seconds.MAXIMUM MESSAGE SIZE: This value is used to set the number of messages that appear in the interface display window.

SECONDS FOR CLEAR MESSAGE: This value is used to set the time before the messages that appear in the interface display window are cleared.

IDOC ERROR LOG: This value is used to store the location of the file that contains details of invalid deleted Idocs.RESENT PARAMETER FILE: This value is used to store the location of the parameter file that is used in conjunction with idoc_r.exe to re-send invalid Idocs. IDOC RESENT LOG:

IDOC TEST PATH: This value is used to store the location of the Idocs before being tested to see if they are valid Idocs. It is also the location of where the Idocs are produced from SAP.

IDOC SCAN PATH: This value is used to store the location of where the Idocs are held after being tested if they are valid Idocs.

INTERFACE DESCRIPTION: This value is used to store the description of the Interface.

This system parameter, can be set by going to system values (short-path: Y2) in the category Documents.CORRESPONDENT-DOCUMENTS: This value is used to store a list of Documents that are to be printed

in the sales office of the person who raised the order.

Master Data CreationOrder Master Table

Listed below are the master data tables that are created by the order stage of the interface.

1. XMCURR0 - Currency, Short-path - CU

The main fields updates on this table are xmcurr0.cucode which is assigned the segment field e2edk01.curcy; and the xmcurr0.cudesc field which is assigned the segment field e2edk01.curcy. Therefore, the Currency Description needs to be manually changed.

2. XMPTRM0 - Payment Terms, Short-path - PT

The main fields updates on this table are xmptrm0.ptcode which is assigned the segment field e2edk01.zterm, and the xmptrm0.ptdesc field which is assigned the segment field, e2edk18.zterm_txt. 3. XMNREF0 - Partner, Short-path - NR

There are a number of different partners created which have different address books assigned, including the following:

a) Shipping Officers

Shipping Officers are created with the address book 03; the main fields updates on this table are xmnref0.nrnref which is assigned the segment field e2edk02.belnr, and the xmnref0.nrname field which is assigned the segment field e2edk02.belnr.b) Consignees

The Consignees are created with address book 0; the main fields updates on this table are xmnref0.nrnref which is assigned the segment field e2edka1.partn, and the field, xmnref0.nrname, assigned the segment field e2edka1.name1. c) Customers

The Customers are created with address book 01; the main fields updates on this table are xmnref0.nrnref which is assigned the segment field e2edka1.partn, and the xmnref0.nrname field which is assigned the segment field e2edka1.name1. 4. XTZSTP0 - Transaction Type, Short-path - ZS

The field updated on this table is xtzstp0.zstype, which is assigned the segment field, ie2edk14.orgid.5. XMTTYP0 Tax Groups, Short-path TT

The field updated on this table is xmttyp0.ttvatc, which is assigned the segment field, e2edk04.mwskz.6. XMTXRT0 Tax Rates, Short-path TX

The main fields updates on this table are xmtxrt0.txtaxc which are assigned the segment field e2edk04.mwskz, and the field xmtxrt0.txrate which is assigned the segment field, e2edk04.msatz. 7. XMCHRG0 Charge / Revenue, Short-path CH

The main fields updates on this table are xmchrg0.chcstc which are assigned the segment field, e2edk05.kschl, and the field xmchrg0.chdesc which is assigned the segment field, e2edk05.kotxt. 8. XMCTRY0 Country, Short-path CT

The main fields updates on this table are xmctry0.ctccde which are assigned the segment field, e2edka1.land1, and the field, xmctry0.ctlnam, which is assigned the segment field, e2edka1.land1. Therefore, the Country Description needs to be manually changed.


The main fields updates on this table are xmdlng0.dllang, which are assigned the segment field, e2edka1.spras, and the xmdlng0.dldesc field assigned the segment field, e2edka1.spras.


The main fields updates on this table are xmpbas0.pbpbas which are assigned the segment field, e2edka1.pfach, and the xmpbas0.pblnam field, which is assigned the segment field, e2edka1.pfach.


The main fields updates on this table are xmdelv0.dedstr which are assigned the segment field, e2edk17.lkond, and the xmdelv0.dedesc field which is assigned the segment field, e2edk17.lktext. 12. XTZBTX0 Text id Codes, Short-path ZBTX

The field updated on this table is xtzbtx0.zbtxid which is assigned the segment field, e2edkt1.tdid.13. XMPROD0 Product, Short-path PR

The main fields updates on this table are xmprod0.prprod which are assigned the segment field, e2edp19.idtnr, and the xmprod0.prdsc1 field, which is assigned the segment field, e2edp19.ktext.


This option is a sub-option off the Partners, NR, and is called Products. Its purpose is to allow for customer specific descriptions of products. The main fields updates on this table are xmnprd0.npprod which is assigned the segment field, e2edp19.idtnr, the xmnprd0.npcprd field which is assigned the segment field, e2edp19.idtnr, and the xmnprd0.npdsc1 field which is assigned the segment field, e2edp19.ktext.

15. XMCMOD0 Commodity, Short-path CM

The main fields updates on this table are xmcmod0.cmcmod which is assigned the segment field, e2edp19.idtnr, and the xmcmod0.cmcds1 field which is assigned the segment field, e2edp19.ktext.

Delivery Master Table

Listed below are the master data tables that are created by the order stage of the interface.



a) Consignees

The Consignees are created with the address book 01; the main fields updates on this table are xmnref0.nrnref which is assigned the segment field, e2edka1.partn, and the xmnref0.nrname field which is assigned the segment field, e2edka1.name1. b) Customers

The Customers are created with the address book 01; the main fields updates on this table are xmnref0.nrnref which is assigned the segment field, e2edka1.partn, and the xmnref0.nrname field which is assigned the segment field, e2edka1.name1. 2. XMDLNG0 Language, Short-path DL

The main fields updates on this table are xmdlng0.dllang which is assigned the segment, fielde2edka1.spras, and the field, xmdlng0.dldesc, which is assigned the segment field, e2edka1.spras.


The main fields updates on this table are xmpbas0.pbpbas, which is assigned the segment field, e2edka1.pfach, and the field, xmpbas0.pblnam, which is assigned the segment field, e2edka1.pfach.

4. XTZBTX0 Text id Codes, ,Short-path ZBTX

The field updated on this table is xtzbtx0.zbtxid which is assigned the segment field, e2edkt1.tdid.5. XMDELV0 Delivery Terms, Short-path DE

The main fields updates on this table are xmdelv0.dedstr which is assigned the segment field, e2edk08.inco1, and the field, xmdelv0.dedesc, which is assigned the segment field, e2edk08.inco2. 6. XTROUT0 Route, Short-path RT

The main fields updates on this table are xtrout0.rtrout, which is assigned the segment field, e2edk08.route, and the xtrout0.rtdes1 field which is assigned the segment field, e2edk08.route_bez.

7. XMTRAN0 Transport Mode, Short-path TR

The field updated on this table is xmtran0.trmode, which is assigned the segment field, e2edk08.expvz.8. XMCITY0 Place, Short-path PL

The field updated on this table is xmcity0.cicity, which is assigned the segment field, e2edk08.zlflh.9. XMPROD0 Product, Short-path PR

The main fields updates on this table are xmprod0.prprod, which is assigned the segment field, e2edp09.matnr, and the xmprod0.prdsc1 field assigned the segment field, e2edp09.arktx.


This option is a sub-option off the Partners, NR, and is called Products. Its purpose is to allow for customer specific descriptions of products. The main fields updates on this table are xmnprd0.npprod, which is assigned the segment field, e2edp09.matnr; the field, xmnprd0.npcprd, is assigned the segment field, e2edp09.kdmat, and the xmnprd0.npdsc1 field is assigned the segment field e2edp09.txtz1.

Invoice Master Table

Listed below are the master data tables that are created by the Invoice stage of the interface.



a) Banks

Banks are created with the address book 03; the main fields updates on this table are xmnref0.nrnref assigned the segment field e2edk02.belnr and the field xmnref0.nrname assigned the segment field e2edk02.belnr. b) Consignees

The Consignees are created with address book 01, and he main fields updates on this table are xmnref0.nrnref assigned the segment field e2edka1.partn and the field xmnref0.nrname assigned the segment field e2edka1.name1. c) Customers

The Customers are created with address book 01, and he main fields updates on this table are xmnref0.nrnref assigned the segment field e2edka1.partn and the field xmnref0.nrname assigned the segment field e2edka1.name1. 2. XMDLNG0 Lanuage, Short-path DL

The main fields updates on this table are xmdlng0.dllang, which is assigned the segment field, e2edka1.spras, and the xmdlng0.dldesc field which is assigned the segment field, e2edka1.spras.


The main fields updates on this table are xmpbas0.pbpbas, which is assigned the segment field, e2edka1.pfach, and the xmpbas0.pblnam field which is assigned the segment field, e2edka1.pfach.


The main fields updates on this table are xmchrg0.chcstc, which is assigned the segment field, e2edk05.kschl, and the field, xmchrg0.chdesc, which is assigned the segment field, e2edk05.kotxt. 5. XMTTYP0 Tax Groups, Short-path TT

The field updated on this table is xmttyp0.ttvatc, which is assigned the segment field, e2edk04.mwskz.6. XMTXRT0 Tax Rates, Short-path TX

The main fields updates on this table are xmtxrt0.txtaxc, which is assigned the segment field, e2edk04.mwskz, and the xmtxrt0.txrate field which is assigned the segment field, e2edk04.msatz. 7. XMDELV0 Delivery Terms, Short-path DE

The main fields updates on this table are xmdelv0.dedstr, which is assigned the segment field, e2edk17.lkond, and the xmdelv0.dedesc field which is assigned the segment field, e2edk17.lktext. 8. XMPTRM0 Payment Terms, Short-path PT

The main fields updates on this table are xmptrm0.ptcode, which is assigned the segment field, e2edk01.zterm, and the xmptrm0.ptdesc field which is assigned the segment field, e2edk18.zterm_txt. 9. XTZBTX0 Text id Codes, Short-path ZBTX

The field updated on this table is xtzbtx0.zbtxid, which is assigned the segment field, e2edkt1.tdid.10. XMPROD0 Product, Short-path PR

This is a sub-option off the Partners, NR, and is called Products. Its purpose is to allow customer specific descriptions of products. The main fields updates on this table are xmnprd0.npprod, which is assigned the segment field, e2edp19.idtnr, the xmnprd0.npcprd field which is assigned the segment field, e2edp19.idtnr, and the xmnprd0.npdsc1 field, which is assigned the segment field, e2edp19.ktext.


This is a sub-option off the Partners, NR, and is called Products. Its purpose is to allow customer specific descriptions of products. The main fields updates on this table are xmnprd0.npprod, which is assigned the segment field, e2edp19.idtnr, the xmnprd0.npcprd field which is assigned the segment field, e2edp19.idtnr, and the field, xmnprd0.npdsc1, which is assigned the segment field, e2edp19.ktext.

12. XMCMOD0 - Commodity Short-path CM

The main fields updates on this table are xmcmod0.cmcmod, which is assigned the segment field, e2edp28.stawn, and the field, xmcmod0.cmcds1, which is assigned the segment field, e2edp28.stxt1.

Appendix 1 - IDOC definitions processed by TRAXi3 interface

Idoc segment structure and field names for the Order Idoc, orders02

19.05.1999 Documentation of IDoc Types (Overview) 1

---------------------------------------------------------------------------------------------------------------------------

Output IDoc type: ORDERS02 Purchasing/Sales

E1EDK01 M 1 1 IDoc: Document header general data

E1EDK14 C 1 12 IDoc: Doc.header organizational data

E1EDK03 C 1 10 IDoc: Document header date segment

E1EDK04 C 1 10 IDoc: Document header taxes

E1EDK05 C 1 16 IDoc: Document header conditions

E1EDKA1 C P 1 8 IDoc: Doc.header partner information

E1EDKA3 C 1 99 IDoc: DocHeader Partner information Add.data

E1EDK02 C 1 10 IDoc: Document header reference data

E1EDK17 C 1 4 IDoc: Doc.header terms of delivery

E1EDK18 C 1 3 IDoc: Doc.header terms of payment

E1EDKT1 C P 1 99 IDoc: Doc.header text ID

E1EDKT2 C 1 9999999999 IDoc: Doc.header texts

E1EDP01 C P 1 999999 IDoc: Doc.item general data

E1EDP02 C 1 10 IDoc: Doc.item reference data

E1CUREF C 1 1 CU: reference order item / instance in configuration

E1EDP03 C 1 10 IDoc: Doc.item date segment

E1EDP04 C 1 10 IDoc: Doc.item taxes

E1EDP05 C 1 16 IDoc: Doc.item conditions

E1EDP20 C 1 9999 IDoc: Schedule lines

E1EDPA1 C P 1 8 IDoc: Doc.item partner information

E1EDPA3 C 1 99 IDoc: Doc.item Partner information Add.data

E1EDP19 C 1 5 IDoc: Doc.item object identification

E1EDP17 C 1 5 IDoc: Doc.item terms of delivery

E1EDP18 C 1 3 IDoc: Doc.item terms of payment

E1EDPT1 C P 1 9999999999 IDoc: Doc.item text ID

E1EDPT2 C 1 9999999999 IDoc: Doc.item texts

E1EDC01 C P 1 9999999 SS: general service specifications data

E1EDC02 C 1 10 SS item: reference data

E1EDC03 C 1 10 SS item: date segment

E1EDC04 C 1 10 SS item: taxes

E1EDC05 C 1 16 SS item: conditions

E1EDCA1 C 1 8 SS items: partner information

E1EDC19 C 1 5 SS items: object identification

E1EDC17 C 1 5 SS items: terms of delivery

E1EDC18 C 1 3 SS items: terms of payment

E1EDCT1 C P 1 9999999999 SS items: text identification

E1EDCT2 C 1 9999999999 SS items: texts

E1CUCFG C P 1 99999 CU: configuration data

E1CUINS C 1 99999 CU: instance data

E1CUPRT C 1 99999 CU: partof data

E1CUVAL C 1 99999 CU: characteristic valuation

E1EDS01 C 1 5 IDoc: Summary segment general


---------------------------------------------------------------------------------------------------------------------------

Output IDoc type: ORDERS02 Purchasing/Sales


ACTION 3 Action code for the whole EDI message

KZABS 1 Indicator for order acknowledgment requirement

CURCY 3 Currency

HWAER 3 EDI local currency

WKURS 12 Exchange rate

ZTERM 17 Terms of payment key

KUNDEUINR 20 VAT registration number

EIGENUINR 20 VAT registration number

BSART 4 Document type

BELNR 35 IDOC document number

NTGEW 18 Net weight

BRGEW 18 Net weight

GEWEI 3 Weight unit

FKART_RL 4 Invoice list type

ABLAD 25 Unloading point

BSTZD 4 Purchase order number supplement

VSART 2 Shipping type

VSART_BEZ 20 Description of the shipping type

RECIPNT_NO 10 Number of recipient (for control via the ALE model)

KZAZU 1 Order combination indicator

AUTLF 1 Complete delivery defined for each sales order?

AUGRU 3 Order reason (reason for the business transaction)

AUGRU_BEZ 40 Description

ABRVW 3 Delivery schedule usage ID

ABRVW_BEZ 20 Description

FKTYP 1 Billing category

E1EDK14 C 1 12 IDoc: Doc.header organizational data

QUALF 3 IDOC qualifer organization

ORGID 35 IDOC organization


IDDAT 3 Qualifier for IDOC date segment

DATUM 8 IDOC: Date

UZEIT 6 IDOC: Time


MWSKZ 7 VAT indicator

MSATZ 17 VAT rate

MWSBT 18 Value added tax amount

TXJCD 15 Jurisdiction for tax calculation - tax jurisdiction code


ALCKZ 3 Surcharge or discount indicator

KSCHL 4 Condition type (coded)

KOTXT 80 Condition text

BETRG 18 Fixed surcharge/discount on total gross

KPERC 8 Condition percentage rate

KRATE 15 Condition record per unit

UPRBS 9 Price unit

MEAUN 3 Unit of measurement

KOBTR 18 IDoc condition end amount


MSATZ 17 Condition type (coded)

E1EDKA1 C P 1 8 IDoc: Doc.header partner information

PARVW 3 Partner function (e.g. sold-to party, ship-to party, ...)

PARTN 17 Partner number

LIFNR 17 Vendor number at customer location

NAME1 35 Name 1

NAME2 35 Name 2

NAME3 35 Name 3

NAME4 35 Name 4

STRAS 35 Street and house number 1

STRS2 35 Street and house number 2

PFACH 35 PO box

ORT01 35 City

COUNC 9 County code

PSTLZ 9 Postal code

PSTL2 9 Postal code of PO box

LAND1 3 Country key


PERNR 30 Contact person's personnel number

PARNR 30 Contact person's number (not personnel number)

TELF1 25 1st telephone number of contact person

TELF2 25 2nd telephone number of contact person

TELBX 25 Telebox number

TELFX 25 Fax number

TELTX 25 Teletex number

TELX1 25 Telex number

SPRAS 1 Language key

ANRED 15 Title

ORT02 35 District

HAUSN 6 House number

STOCK 6 Floor

REGIO 3 Region

PARGE 1 Partner's sex

ISOAL 2 Country ISO code

ISONU 2 Country ISO code

FCODE 20 Company key (France)

IHREZ 30 Your reference (Partner)

BNAME 35 IDoc user name

PAORG 30 IDOC organization code

ORGTX 35 IDoc organization code text

PAGRU 30 IDoc group code

KNREF 30 Customer description of partner (plant, storage location)

ILNNR 70 Character field, length 70

E1EDKA3 C 1 99 IDoc: DocHeader Partner information Add.data

QUALP 3 IDOC Partner identification (e.g.Dun&Bradstreet number)

STDPN 70 Character field, length 70


QUALF 3 IDOC qualifier reference document


POSNR 6 Item number

DATUM 8 IDOC: Date

UZEIT 6 IDOC: Time


QUALF 3 IDOC qualifier: Terms of delivery

LKOND 3 IDOC delivery condition code

LKTEXT 70 IDOC delivery condition text


QUALF 3 IDOC qualifier: Terms of payment

TAGE 8 IDOC Number of days

PRZNT 8 IDOC percentage for terms of payment

ZTERM_TXT 70 Line of text


TDID 4 Text ID

TSSPRAS 3 Language key

E1EDKT2 C 1 9999999999 IDoc: Doc.header texts

TDLINE 70 Line of text

E1EDP01 C P 1 999999 IDoc: Doc.item general data

POSEX 6 Item number

ACTION 3 Action code for the item

PSTYP 1 Item category


MENGE 15 Quantity

MENEE 3 Unit of measure

BMNG2 15 Quantity in price unit

PMENE 3 Price unit of measure

ABFTZ 7 Agreed cumulative quantity

VPREI 15 Price (net)

PEINH 9 Price unit

NETWR 18 Item value (net)

ANETW 18 Absolute net value of item

SKFBP 18 Amount qualifying for cash discount

NTGEW 18 Net weight

GEWEI 3 Weight unit

EINKZ 1 Flag: More than one schedule line for the item

CURCY 3 Currency

PREIS 18 Gross price

MATKL 9 IDOC material class

UEPOS 6 Higher-level item in BOM structures

GRKOR 3 Delivery group (items delivered together)

EVERS 7 Shipping instructions

BPUMN 6 Denominator for conv. of order price unit into order unit

BPUMZ 6 Numerator for conversion of order price unit into order unit

ABGRU 2 Reason for rejection of quotations and sales orders

ABGRT 40 Description

ANTLF 1 Maximum number of partial deliveries allowed per item

FIXMG 1 Delivery date and quantity fixed

KZAZU 1 Order combination indicator

E1EDP02 C 1 10 IDoc: Doc.item reference data

QUALF 3 IDOC qualifier reference document


ZEILE 6 Item number

DATUM 8 IDOC: Date

UZEIT 6 IDOC: Time

E1CUREF C 1 1 CU: reference order item / instance in configuration

POSEX 6 Character field of length 6

CONFIG_ID 6 Character field of length 6

INST_ID 8 Character field, 8 characters long

E1EDP03 C 1 10 IDoc: Doc.item date segment


DATUM 8 Date

UZEIT 6 Time

E1EDP04 C 1 10 IDoc: Doc.item taxes


MSATZ 17 VAT rate



E1EDP05 C 1 16 IDoc: Doc.item conditions







UPRBS 9 Price unit



MENGE 15 Price scale quantity (SPEC2000)

PREIS 15 Price by unit of measure (SPEC2000)



E1EDP20 C 1 9999 IDoc: Schedule lines

WMENG 15 Scheduled quantity

AMENG 15 Previous scheduled quantity

EDATU 8 IDOC: Date

EZEIT 6 IDOC: Time

EDATU_OLD 8 IDOC: Date

EZEIT_OLD 6 IDOC: Time

E1EDPA1 C P 1 8 IDoc: Doc.item partner information




NAME1 35 Name 1

NAME2 35 Name 2

NAME3 35 Name 3

NAME4 35 Name 4



PFACH 35 PO box

ORT01 35 City

COUNC 9 County code

PSTLZ 9 Postal code


LAND1 3 Country key







TELFX 25 Fax number




ANRED 15 Title

ORT02 35 District


STOCK 6 Floor

REGIO 3 Region












E1EDPA3 C 1 99 IDoc: Doc.item Partner information Add.data

QUALP 3 IDOC Partner identification (e.g.Dun&Bradstreet number)

STDPN 70 Character field, length 70

E1EDP19 C 1 5 IDoc: Doc.item object identification

QUALF 3 IDOC object identification such as material no.,customer

IDTNR 35 IDOC material ID

KTEXT 70 IDOC short text

E1EDP17 C 1 5 IDoc: Doc.item terms of delivery




LPRIO 2 Delivery priority

E1EDP18 C 1 3 IDoc: Doc.item terms of payment





TDID 4 Text ID


E1EDPT2 C 1 9999999999 IDoc: Doc.item texts


E1EDC01 C P 1 9999999 SS: general service specifications data

SGTYP 3 IDoc service specifications segment type

ZLTYP 3 IDoc service specifications line category

LVALT 3 IDoc service specifications alternatives

ALTNO 2 IDoc alternative number for service specifications

ALREF 5 IDoc allocation number for service specifications

ZLART 3 IDoc service specifications line type

POSEX 10 Line number within service package

RANG 2 Hierarchy level of group

EXGRP 8 Outline level


MATKL 9 IDOC material class

MENGE 15 Quantity

MENEE 3 Unit of measure

BMNG2 15 Quantity in price unit

PMENE 3 Price unit of measure

BPUMN 6 Denominator for conv. of order price unit into order unit

BPUMZ 6 Numerator for conversion of order price unit into order unit

VPREI 15 Price (net)

PEINH 9 Price unit

NETWR 18 Item value (net)

ANETW 18 Absolute net value of item

SKFBP 18 Amount qualifying for cash discount

CURCY 3 Currency

PREIS 18 Gross price

ACTION 3 Action code for the item


UEBTO 4 Overfulfillment tolerance

UEBTK 1 Indicator: unlimited overfulfillment allowed

LBNUM 3 Description of service type

AUSGB 4 Edition of service type

FRPOS 6 Lower limit

TOPOS 6 Upper limit

KTXT1 40 Short text

KTXT2 40 Short text

PERNR 8 Personnel number

LGART 4 Wage type

STELL 8 Job

ZWERT 18 Total value of sum segment

E1EDC02 C 1 10 SS item: reference data

QUALF 3 IDoc qualifier reference document for service specifications


XLINE 10 Line number within service package

DATUM 8 IDOC: Date

UZEIT 6 IDOC: Time

E1EDC03 C 1 10 SS item: date segment


DATUM 8 Date

UZEIT 6 Time

E1EDC04 C 1 10 SS item: taxes


MSATZ 17 VAT rate



E1EDC05 C 1 16 SS item: conditions







UPRBS 9 Price unit



MENGE 15 Price scale quantity (SPEC2000)

PREIS 15 Price by unit of measure (SPEC2000)



E1EDCA1 C 1 8 SS items: partner information




NAME1 35 Name 1

NAME2 35 Name 2

NAME3 35 Name 3

NAME4 35 Name 4



PFACH 35 PO box

ORT01 35 City

COUNC 9 County code

PSTLZ 9 Postal code


LAND1 3 Country key







TELFX 25 Fax number




ANRED 15 Title

ORT02 35 District


STOCK 6 Floor

REGIO 3 Region










E1EDC19 C 1 5 SS items: object identification

QUALF 3 IDoc object identification for service specfns object

IDTNR 35 IDOC material ID

KTEXT 70 IDOC short text

E1EDC17 C 1 5 SS items: terms of delivery




E1EDC18 C 1 3 SS items: terms of payment




E1EDCT1 C P 1 9999999999 SS items: text identification

TDID 4 Text ID


E1EDCT2 C 1 9999999999 SS items: texts


E1CUCFG C P 1 99999 CU: configuration data

POSEX 6 Character field of length 6

CONFIG_ID 6 Character field of length 6

ROOT_ID 8 Character field, 8 characters long

E1CUINS C 1 99999 CU: instance data


OBJ_TYPE 10 Character field length = 10

CLASS_TYPE 3 3-Byte field

OBJ_KEY 50 Comment

OBJ_TXT 70 Character field, length 70

QUANTITY 15 Char 15

E1CUPRT C 1 99999 CU: partof data

PARENT_ID 8 Character field, 8 characters long


PART_OF_NO 4 Nothing

OBJ_TYPE 10 Character field length = 10

CLASS_TYPE 3 3-Byte field

OBJ_KEY 50 Comment

E1CUVAL C 1 99999 CU: characteristic valuation


CHARC 40 Character field of length 40

CHARC_TXT 70 Character field, length 70

VALUE 40 Character field of length 40

VALUE_TXT 70 Character field, length 70


SUMID 3 Qualifier for totals segment for shipping notification

SUMME 18 Total value of sum segment

SUNIT 3 Total value unit for totals segment in the shipping notif.

WAERQ 3 Currency

Idoc segment structure and field names for the Delivery Idoc, desadv19.05.1999 Documentation of IDoc Types (Overview) 1

---------------------------------------------------------------------------------------------------------------------------

Output IDoc type: DESADV DESADV + batch characteristics

E1EDK07 M P 1 1 IDoc: Document header shipping notification (transport)

E1EDKA1 M 1 9999 IDoc: Doc.header partner information

E1EDK03 M 1 9999 IDoc: Document header date segment


E1EDKT2 M 1 9999 IDoc: Doc.header texts

E1EDK08 M P 1 99999 IDoc: Document header shipping notification (delivery)





E1EDKT4 M 1 9999 IDoc: Document header text

E1EDP06 C 1 99999 IDoc: Package identification total

E1EDP07 M P 1 99999 IDoc: Purchase order data shipping notification

E1EDP08 C 1 99999 IDoc: Package data individual

E1EDP09 M P 1 99999 IDoc: Item data shipping notification

Z1EXP2 C 1 9999 Summary for batches

Z1EXP1 C 1 9999 Batch Characteristics


E1EDPT2 M 1 9999 IDoc: Doc.item texts

E1EDS02 C 1 99999 IDoc: Summary segment


---------------------------------------------------------------------------------------------------------------------------

Output IDoc type: DESADV DESADV + batch characteristics

E1EDK07 M P 1 1 IDoc: Document header shipping notification (transport)

ACTION 3 Delivery ID

BOLNR 35 Bill of lading

VBELN 35 Delivery

TRAID 20 Shipment ID

TRATY 4 Transportation category

INCO1 3 Incoterms part 1


ROUTE 35 Route

ROUTE_BEZ 35 Description of route

VSBED 3 Shipping conditions

VSTEL 25 Shipping point

VSTEL_BEZ 35 Description of shipping point

VKORG 20 Sales organization

VKGRP 20 Sales group

VTWEG 20 Distribution channel

EXPKZ 3 Export indicator

BEROT 25 Picked items location

LSTEL 25 Loading point

EXPVZ 3 Mode of transport (when goods cross border)

EXPVZ_BEZ 60 Description of mode of transport

ZOLLA 17 Office of exit

ZOLLB 17 Office of destination

ZOLL1 17 Customs office 1






KZGBE 30 Indicator for means of transport crossing the border

KZABE 30 Indicator for the means of transport at departure

STGBE 17 Origin of means of transport for crossing the border

STABE 17 Country of origin of the means of transport at departure

GRWCU 3 Currency of statistical values

ZONE1 10 Regional zone

EDLKZ 2 External agent ID

SPDLA 2 Country key for forwarding agent (Alphanumeric ISO)

SPDLN 2 ISO numeric country key for forwarding agent

ZLFLH 20 Port/airport of destination

WAERK 5 Document currency

FRAKO 18 Freight costs in the delivery

STABA 2 Country in which means of transport is registered(ISO alpha)

DOCC1 3 Pro forma invoice code (Volvo 380)

DOCC2 3 Code for EUR certificate or invoice declaration

DOCN1 20 Document number for personal identification

DOCD1 8 Date of pro forma invoice (Volvo)

DOCD2 8 Date of EUR certificate or invoice declaration

RECIPNT_NO 10 Number of recipient (for control via the ALE model)





NAME1 35 Name 1

NAME2 35 Name 2

NAME3 35 Name 3

NAME4 35 Name 4



PFACH 35 PO box

ORT01 35 City

COUNC 9 County code

PSTLZ 9 Postal code


LAND1 3 Country key







TELFX 25 Fax number




ANRED 15 Title

ORT02 35 District


STOCK 6 Floor

REGIO 3 Region














DATUM 8 IDOC: Date

UZEIT 6 IDOC: Time


TDID 4 Text ID


E1EDKT2 M 1 9999 IDoc: Doc.header texts


E1EDK08 M P 1 99999 IDoc: Document header shipping notification (delivery)

ACTION 3 Delivery ID

VBELN 35 Delivery

TRAID 20 Shipment ID

TRATY 4 Transportation category



ROUTE 35 Route

ROUTE_BEZ 35 Description of route

VSBED 3 Shipping conditions


VSTEL_BEZ 35 Description of shipping point

VKORG 20 Sales organization

VKGRP 20 Sales group

VTWEG 20 Distribution channel

EXPKZ 3 Export indicator

BEROT 25 Picked items location


EXPVZ 3 Mode of transport (when goods cross border)

EXPVZ_BEZ 60 Description of mode of transport

ZOLLA 17 Office of exit

ZOLLB 17 Office of destination







KZGBE 30 Indicator for means of transport crossing the border

KZABE 30 Indicator for the means of transport at departure

STGBE 17 Origin of means of transport for crossing the border

STABE 17 Country of origin of the means of transport at departure

GRWCU 3 Currency of statistical values

ZONE1 10 Regional zone

EDLKZ 2 External agent ID

SPDLA 2 Country key for forwarding agent (Alphanumeric ISO)

SPDLN 2 ISO numeric country key for forwarding agent

ZLFLH 20 Port/airport of destination

WAERK 5 Document currency

FRAKO 18 Freight costs in the delivery

STABA 2 Country in which means of transport is registered(ISO alpha)

DOCC1 3 Pro forma invoice code (Volvo 380)

DOCC2 3 Code for EUR certificate or invoice declaration

DOCN1 20 Document number for personal identification

DOCD1 8 Date of pro forma invoice (Volvo)

DOCD2 8 Date of EUR certificate or invoice declaration

VSART 2 Shipping type

VSART_BEZ 20 Description of the shipping type





WAERQ 3 Currency





NAME1 35 Name 1

NAME2 35 Name 2

NAME3 35 Name 3

NAME4 35 Name 4



PFACH 35 PO box

ORT01 35 City

COUNC 9 County code

PSTLZ 9 Postal code


LAND1 3 Country key







TELFX 25 Fax number




ANRED 15 Title

ORT02 35 District


STOCK 6 Floor

REGIO 3 Region









DATUM 35 IDOC date

UHRZE 6 Time for IDOC date segment


TDID 4 Text ID


E1EDKT4 M 1 9999 IDoc: Document header text


E1EDP06 C 1 99999 IDoc: Package identification total

PCKAR 35 Packing type

PCKNR 35 Customer number of shipping unit

ANZPA 15 Total number of shipping units in the shipment

TPKEY 3 Means of transport indicator

ARKTX 40 Short text for sales order item

E1EDP07 M P 1 99999 IDoc: Purchase order data shipping notification

HLNUM 12 Hierarchy number

PARENT 12 Hierarchical parent ID

BSTNK 35 Customer purchase order number

BSTDK 35 Purchase order date

BSTZT 35 Ordering time

POSEX 6 Purchase order item number

VBELN 35 Delivery

VGBEL 35 Number of preceding document

VGPOS 6 Preceding document item number

VGTYP 3 SD document category

LABNK 17 Customer number for forecast / JIT dlv. sched.

ZEICH 70 Reference of orderer

BSTZD 70 Account assignment

ABRKZ 1 ID for direct release order

ABRDT 8 Release order date from customer

KTEXT 40 Search term for product proposal

E1EDP08 C 1 99999 IDoc: Package data individual



LEVEL 12 Pack/subpack level ID

EXIDV 45 External shipping unit ID

VENUM 10 Shipping unit number

VEMEH 3 Unit of measure of delivery item quantity in ship.elem.item

PCKAR 35 Packing type

PCKNR 35 Customer number of shipping unit

ANZAR 15 Number of products per shipping unit

VBELN 35 Delivery

POSNR 30 Delivery item

BTGEW 18 Total weight

NTGEW 18 Net weight

TARAG 18 Tare weight of shipping unit

GEWEI 3 Weight unit

BTVOL 18 Total volume of shipping unit

NTVOL 18 Loading volume of shipping unit

TAVOL 18 Tare volume of shipping unit

VOLEH 3 Volume unit

LAENG 18 Length

BREIT 18 Width

HOEHE 18 Height

MEABM 3 Unit for length/width/height

MEINS 3 Base unit of measure



PKNRS 1 Shipment number key for VDA/Odette

E1EDP09 M P 1 99999 IDoc: Item data shipping notification



VBELN 35 Delivery

POSNR 30 Delivery item

ABRVW 3 Delivery schedule usage ID

MATNR 35 Material number of vendor

WERKS 25 Plant

LGORT 25 Storage location

CHARG 35 Batch number

KDMAT 35 Material number of customer

LFIMG 15 Actual quantity delivered (in sales units)

VRKME 3 Unit of measure

BTGEW 18 Total weight

NTGEW 18 Net weight

GEWEI 3 Weight unit

VOLUM 18 Volume

VOLEH 3 Volume unit

ARKTX 80 Short text by sender on item

EANNR 35 European Article Number (EAN)

STAWN 35 Commodity code

EXART 2 Business transaction type

EXART_BEZ 30 Description

HERKL 25 Country of origin of material

HERKR 25 Region of origin

GRWRT 18 Statistical value


TXTZ1 70 Customer product text line 1

TXTZ2 70 Customer product text 2

ZOLLG 1 Customs ID

MWSAT 5 Tax on sales (VAT) record

BERLI 1 Berlin status

TSTKY 2 Status key for parts

DOKPF 1 Indicator: Documentation required for inspection results

DESRE 1 Design revision number

ECHNO 1 Engineering change number

ECHDT 8 Engineering change date

VBRST 14 Customer point of consumption

ZEIKD 35 Customer drawing number

TARIF 10 Rate

AMERK 8 License characteristic

AMERT 17 Text for license characteristic

IMPLN 10 Import license number

EXPLN 10 Export license number

CHBEZ 60 Chemical description

KLAS1 3 Hazard class

IMOCE 6 English IMDG code (page number)

IMCNR 4 IMDG classification number

UNNUM 4 UN number

AESKD 17 Customer change status

PREFE 1 Preference indicator in export/import

LABNK 17 Customer number for forecast / JIT dlv. sched.

ABRDT 8 SA release date

Z1EXP2 C 1 9999 Summary for batches



Z1EXP1 C 1 9999 Batch Characteristics

ATNAM 30 Characteristic name

AUSP1 30 Characteristic value

SMBEZ 30 Characteristic description


TDID 4 Text ID


E1EDPT2 M 1 9999 IDoc: Doc.item texts


E1EDS02 C 1 99999 IDoc: Summary segment




Idoc segment structure and field names for the Export Invoice Idoc, expinv19.05.1999 Documentation of IDoc Types (Overview) 1

---------------------------------------------------------------------------------------------------------------------------Output IDoc type: EXPINV Export Invoice plus variant configuration for TRAX use.


E1EDKA1 C 1 10 IDoc: Doc.header partner information







E1EDK23 C 1 10 IDoc: Doc. header currency segment

E1EDK28 C 1 10 IDoc: Doc.header bank data

E1EDK26 C 1 20 IDoc: Doc.header amount segment

E1EDK29 M 1 1 IDoc: Document header export

E1EDK30 C 1 999 IDoc: Document header package data total


E1EDKT2 C