Definition of BEMIS V ORD001A Import and Export File for ...edi.infor.com/Download Area/Documents/BaanERP/PDF... · BAAN ERP as well as possible special actions, which will be carried

BaanERP (Grieg SP4)Definition of BEMIS V ORD001AImport and Export File for the MessageTrading Orders

A publication of:

Baan Development B.V.P.O.Box 1433770 AC BarneveldThe Netherlands

Printed in the Netherlands

© Baan Development B.V. 1999.All rights reserved.

The information in this documentis subject to change withoutnotice. No part of this documentmay be reproduced, stored ortransmitted in any form or by anymeans, electronic or mechanical,for any purpose, without theexpress written permission ofBaan Development B.V.

Baan Development B.V.assumes no liability for anydamages incurred, directly orindirectly, from any errors,omissions or discrepanciesbetween the software and theinformation contained in thisdocument.

Document Information

Code: U7316A USGroup: User DocumentationEdition: ADate: August, 1999

i

Definition of BEMIS V ORD001A Import and Export File for the Message Trading Orders

1 General Principles 1-1Available kinds of data records 1-1Branching diagramm 1-2Key fields outgoing 1-4Key fields incoming 1-4Network directories 1-5BEMIS V Messages - Conventions 1-6What is new in comparison to BEMIS for BAAN IV 1-9

2 Data record description by kind of data record 2-1SA1 MESSAGE OVERHEAD 2-1SA2 ORDER HEADER 2-13SA3 ORDER TEXT - TEXTDATEN 2-45SA4 Order Specific Addresses 2-51First Appearance: Ship From Business Partner Address ( Address Qualifier:

SFBP ) 2-51Second Appearance: Warehouse Address ( Address Qualifier: CWAR ) 2-54First Appearance: Ship from Business partner Address ( Address Qualifier:

SFBP ) 2-57Second Appearance: Warehouse Address ( Address Qualifier: CWAR ) 2-70SA5 Order Lines 2-83SA6 Ship from Business Partner Address per Order Line 2-123First Appearance: Warehouse Address ( Address Qualifier: CWAR ) 2-123

Table of contents

Table of contents


ii


iii

This documentation describes in a detailed way the standard inhouse dataformats, which the BAAN Electronic Message Interchange System BEMIS Vrequires as interfaces to the respective EDI Sub-System.

The documentation is intended for developers of EDI Sub-Systems, which wantto realize an interface of their software to BAAN ERP. Furthermore, it supportsconsultants, who want to implement and verify such an interface within acustomer project.

Chapter 1 gives an overview over the general principles of the relevant EDImessage. For example available kinds of data records, message structure, keyfields and other conventions.

Chapter 2 describes all corresponding kinds of data records for the EDI messagein a detailed way. All data fields are listed in an overview table in connectionwith the corresponding table fields. In addition, every single field is described ina more detailed way. You will find information about the general conditions,which you need to observe for the processing in the EDI Sub-System or inBAAN ERP.

About this document

About this document


iv


1-1

This section describes the BAAN EDI inhouse format for the message typeOrders (incoming/outgoing).

Available kinds of data recordsThe use of the following kinds of data records is conditional (C) respectivelymandatory (M), when you transmit information about orders.

Id Status Name

SA1 M Overhead

SA2 M Order Header

SA3 C Order Header Text

SA4 C Order Warehouse / Invoice Addresses

SA5 M Order Line

SA6 C Order Line Warehouse Addreses

1 General Principles

General Principles


1-2

Branching diagrammThe following data record structure is used for the message type BEMIS V -Orders:

Level

0 SA1 SA2 SA3 SA4

M 1 M 1 C 1 C R

1 SA5

M R

2 SA6

C R

Legend:

Status: Frequency:

M: mandatory in message 1: once by message

C: conditional in message R: repeatable by message

General Principles


1-3

For example, for two required orders with each two lines the BEMIS V file hasthe following structure:

SA1 ... BAAN ERP Overhead

SA2 ... Order Header 1

SA3 ... Order Header 1 Text

SA4 ... Order Address Order 1

SA4. .. Order Address Order1

SA5 ... Order Lines Item 1

SA6 ... Order Line Delivery Address Item 1

SA5.... Order Line Item 2


...

SA1 ... BAAN ERP Overhead

SA2 ... Order Header 2

SA3 ... Order Header 2 Text

SA4 ... Order Address Order 2

SA4... Order Address Order 2

SA5 ... Order Lines Item 1


SA5.... Order Line Item 2


...

General Principles


1-4

Key fields outgoingThe following structure of the key fields is used to determine the related datarecords of an order:

Kind of datarecord

Key field 1 Key field 2 Key field 3 Key field 4

SA1 MessageReference

IdentificationSender





Order Number



Order Number



Order Number



Order Number OrderPosition Number

Key fields incomingThe following structure of the key fields is used to determine the related datarecords of an order message:

Kind of datarecord

Key field 1 Key field 2 Key field 3 Key field 4







Customer PurchaseOrder Number










OrderPositionNumber

General Principles


1-5

Network directoriesThe so-called network directories form the basis of the communication betweenthe EDI Sub-System and BAAN ERP. These directories are established inBAAN. The network basis directories for each network will be defined in theBAAN session SEecedi0120m000. For the network BEMISV, the basisdirectories can be indicated in the following way:

/auto3/baanerp/bemis5/order/

BAAN will additionally create the following subdirectories:

/auto3/ baanerp /bemis5/order/appl_from//auto3/ baanerp /bemis5/order/appl_to//auto3/ baanerp /bemis5/order/command//auto3/ baanerp /bemis5/order/store_recv//auto3/ baanerp /bemis5/order/store_sent//auto3/ baanerp /bemis5/order/trace/

The above mentioned directories have the following function:

1 .../appl_from/: In this directory, BAAN ERP records the outgoing messageswhich are the defined BEMIS V inhouse format files. The EDI Sub-Systemcan collect them from here.

2 .../appl_to/: The EDI Sub-System writes the incoming message into thisdirectory in the BAAN ERP inhouse format.

3 .../command/: Directory of the semaphores.

4 .../store_recv/: BAAN ERP stores in this directory processed incomingmessages, if the configuration is accordingly. During this process anadditional subdirectory by incoming message file will be created which isnamed with a date and time stamp indicating when the message was moved.

5 .../store_sent/: BAAN ERP stores in this directory processed outgoingmessages if the configuration is accordingly. During this process anadditional subdirectory by incoming message file will be created which isnamed with a date and time stamp indicating when the message was moved.

6 ../trace/: BAAN ERP creates under this directory a log of the incoming andoutgoing messages in the processing order, if the configuration isaccordingly.

General Principles


1-6

For every message type one network directory will be used for outgoing and onefor incoming messages. This means that one message file contains data forseveral business partners.

The file name of the BEMIS V inhouse format file of the order, which is beingdescribed in this documentation, is defined in the following way:

Direction File name Network directory

outgoing ord001.txt ../appl_from

incoming ord001.txt ../appl_to

BEMIS V Messages - ConventionsThe following general rules apply to a message record in a BEMIS V messagefile:

1 Every message record starts with “SAx“2 Every message record ends with “SAx_END“3 The length of a data record can vary.4 The message record must consist of all fields, even if not every field contains

a value.5 The fields in the file must be separated by a ; .6 A filled string field have to be put in “ ....“ .

In the following sections you will find the format descriptions for the individualkinds of data records of the interface file. The table contains the following data:

ORDER INHOUSE FORMAT

Pos FIELD DESCRIPTION Key ST FM

The first block of the table describes the format of a kind of data record:

General Principles


1-7

Pos. Position of the field in the data recordField description Description of the fieldKey Key field outgoing (O) / incoming (I)ST Field status mandatory (M) / conditional (C)FM Field format

an..14 alphanumerical field with a maximum of 14charactersan14 alphanumerical field with exactly 14 charactersn..10 numerical field with a maximum of 10 charactersn1 numerical field with exactly 1 character

from Application Table Fields (out) / Mapping to (in)

Table Field Action

The second block of the table describes the corresponding table field inBAAN ERP as well as possible special actions, which will be carried out duringthe processing of the messages.

Following the table overview, every field is described in a more detailed way,including information about the processing in the EDI Sub-System and inBAAN ERP.

In the past, there seemed to be some doubts about the way BAAN points out aposition within the message file. Here are some additional explanations:

As defined in BEMIS V a position within a message file is pointed out using twosemikolons.

To draw an example: p6$;p��3RVLWLRQ��p6$;B(1'p

If an position in a BEMIS V Message File is not taken by a value (this means theposition is empty), the position is pointed out as shown above. Moreover theBAAN EDI Module distinguishes between numerical and alphanumerical dataformat. If a position defined as numerical is empty the position is pointed outusing semikolons. On the other hand empty alphanumerical positions areexported in two way. The first way is to point out a position using thesemicolons. The second way BAAN exports empty alphanumerical positions isto write two inverted commands within the position. This depends whether thealphanumerical field exists in BAAN’s database or not.

General Principles


1-8

Finally we take a look at the following example:

empty numerical Position:

p6$;p��p6$;B(1'p

empty alphanumerical Position:

p6$;p��p6$;B(1'p

or

p6$;p��pp��p6$;B(1'p

General Principles


1-9

What is new in comparison to BEMIS forBAAN IV

1. The Overhead has been changed. Please look Chapter 2 for more details.

2. Furthermore the positions of the rest of the data records has beenrestructured.

3. Comming with BEMIS V we have to introduce a new date / time format.The new date format consists of at maximum 14 digits as shown here.

The new format is now: CCYYMMDDHHMMSS. The date / time information isput as an numerical field to the position within the message.

General Principles

Definition

1-10

4. Comming with BEMIS V, we introduce a new message naming andversioning:

a) Each message type is named by abbreviation and its version number.

To draw an example: ORD 001

Message Type:

ORD for ORDERSVersion: 1

of BEMIS V ORD001A Import and Export File for the Message Trading Orders

b) It is possibel to define different releases to one message, e.g. Release A,B,... a.s.o.

Example: To draw an example: ORD001 A

Release

General Principles


1-11

In case of adding new positions to message type a new version will be released.

We have the aim that the BEMIS V Message standard fits to needs of externaland internal EDI. Hence we decided to deliver two different conversion setupsfor one release. One for external EDI and one for internal EDI. The conversionsetup für internal EDI gets additionally the extension “I”. The structure is thesame. For the internal EDI a conversion is only for the business partner codesnecessary. Therefore the setup for the internal EDI has a minimum ofconversions. It is also possible to use the iternal setup for external EDI and theother way around if additionaly conversion is needed or not.

General Principles

Definition of BEMIS V ORD001A Import and Export File

1-12

To draw an example:

Example: To draw an example: ORD001 A

ORD001 AI

5. Incoming and outgoing messages

Release A forexternal EDI

Release A forinternal EDI

for the Message Trading Orders

have now the same file name.

General Principles


1-13

6. The name of the message file is now depended from the message version.

7. Alternative Items / Item Code Systems

In comparison to BAAN IV the conversion of the Item Codes (customer’s itemcode) has been changed.

BEMIS V comes with two predefined qualifiers in order to determine the internalitem code. The Item Code Id’s are used in oreder to distinguish between ageneral item conversion and a conversion which is business partner related.

Therefore two Codes for the Item System are defined.

Looking at BAAN ERP Common data we will find the used table to translate theitem codes:

a) General Code System:

General Principles


1-14

b) Business Partner specific Code System:

The exported BAAN ERP Item Code is a string with at maximum 47 digists. Atminimum the item code contains 10 digits. To draw anexample: “.........1” (nineleading blanks and at minimum one sign).


2-1

SA1 MESSAGE OVERHEAD

Status: Mandatory

Frequency: Once by order

Description: This data record contains information about thetransmitter, the message type and the time of thetransmission. The message reference identifies allrelated data records of this message.

ORDER INHOUSE FORMAT Mapping from Application

Table Fields (out)

Mapping to Application Fields

(in)

Pos FIELD

DESCRIPTION

Key ST FM Table Field Action Table Field Action

1. Kind of data record O/I M an3 SA1 SA1

2. Message reference O/I M an..14 ecedi701.bano Generation

(see below)

ecedi702.bano Generation

by EDI Sub-

System

3. Identification of the

Sender

O/I M an..17 ecedi020.neta Conversion

(see below)

ecedi702.bpid Conversion

(see below)


Reciever

M an..17 ecedi028.neta Conversion

(see below)

5. Message M an..6 ecedi001.code Conversion

(see below)

ecedi702.mess Conversion

(see below)

6. Organization M an..6 ecedi003.code Conversion

(see below)

ecedi702.orga Conversion

(see below)

7. Order type M an..35 ecedi011.koor Conversion

(see below)

ecedi702.koor Conversion

(see below)

2 Data record description by kind ofdata record

Data record description by kind of data record


2-2


Table Fields (out)


(in)

Pos FIELD

DESCRIPTION


8. Transmission reference M an..20 tdpur400.orno ecedi702.msno

9. Date / Time of

transmission

M n..14 current date /

time

ecedi702.send

10. Transmission reference

old

C an..20 empty position

(...;;...)

ecedi702.prno


technical message

creator

C an..35 “BAANERP”

12. Identifier of Test

Messages

C an1 ecedi003.test empty means

original

message;

1 means Test

message

ecedi702.test empty means

original

message;

1 means Test

message

13. Message Funktion C empty, not

supported for

outgoing

messages

leave the

position empty

this means:

...;;...

(ecedi702.mest)

14. Data record end sign M an7 SA1_END SA1_END



2-3

Detailed description: OrderKind of data record: SA1 Overhead

Description: This field identifies the kind of data record inthe message block. It contains the constant value‘SA1’.

Processing outgoing

EDI Sub-System: .

BAAN: This field will be filled with the constant value‘SA1’.

Processing incoming

EDI Sub-System: This field will be filled with the constant value‘SA1’.

BAAN: None

Position 1 Field format an3 Field status M

Field name Kind of data record (Key field out/in)



2-4

Description: This field identifies all connected data recordsof one order. The numbering, which has to beclear by order, helps to control the chronologicalorder of the orders and the completetransmission. The field consists of a fix itemwith four characters, the current date (format:YYMMDD) and a serial number with fourcharacters.

The special format will be defined in thenetwork parameters in the BAAN tableTBecedi020. When generating the messagereference with the EDI Sub-System, the createdmessage reference needs to be specific, thatmeans unique. While storing the messagereference BAAN controls whether it is specific.

Processing outgoing

EDI Sub-System:

BAAN: BAAN generates this number to identify anorder, stores it in the BAAN table fieldTFecedi701.bano and writes it into all datarecords of an order.

Processing incoming

EDI Sub-System: The EDI Sub-System generates this number toidentify an order and writes it into all datarecords of an order.

BAAN: Mapping to BAAN table field TFecedi702.bano.

Position 2 Field format an..14 Field status M

Field name Message reference (Key field out/in)



2-5

Description: This field contains the identification of thesender (e.g. the ILN Number)

Processing outgoing

EDI Sub-System: Transmission of the value from the message file.

BAAN: The identification is stored in the BAAN tableTBecedi020 ‘Our Identification’ under thecorresponding network in the BAAN table fieldTFecedi020.neta. The contents of this field ismapped to the position of the transmission file.Here you can store the general ILN-Number foryour customer.

Processing incoming

EDI Sub-System:

BAAN: The identification of the sender determines thecorresponding business partner (customer) andthe network in the table TBecedi028 ‘Relationsby network’. This identification is mapped tothe BAAN table field TFecedi702.bpid.

Position3 Field format an..17 Field status M

Field name Identification of the sender (Key field out/in)



2-6

Description: This field contains the identification of thereceiver.

Processing outgoing

EDI Sub-System:

BAAN: The identification of the receiver (e.g. the ILNof the receiver) in the used network is entered inthe table TBecedi028. The BAAN table fieldTFecedi028.neta is mapped to this position.

Processing incoming


BAAN: On the incoming side this field will be ignored.


Field name Identification of the receiver



2-7

Description: This field contains the code for theidentification of the concerned message. Thecode for the message type ‘Orders’ is ORD001.

Processing outgoing

EDI Sub-System:

BAAN: The internal message code ecedi001.code‘ORD001’ of the BAAN table TBecedi001‘Supported EDI messages’ is mapped to thisposition.

Processing incoming

EDI Sub-System: This field will be filled with the constant value‘ORD001’.

BAAN: The message code in the table TBecedi001‘Supported EDI Messages’ determines, whichinternal message in BAAN is connected to thisorder. In the BAAN table TBecedi005 ‘EDIMessages’ is determined for every messagewhich session (Dll ) is used in BAAN toprocess the order. The message code is mappedto the BAAN table field TFecedi702.mess.


Field name Message



2-8

Description: This field contains the organization (Standard),which is used for the EDI communication.

Processing outgoing

EDI Sub-System:

BAAN: The internal organisation code ecedi003.code‘BEMISV’ from the BAAN table TBecedi003‘Organizations’ is mapped to this position.

Processing incoming

EDI Sub-System: This field will be filled with the constant value‘BEMISV’.

BAAN: Mapping to BAAN table field TFecedi702.orga.

The corresponding organization must have beenentered into the BAAN table TBecedi003.


Field name Organization



2-9

Description: This field contains a code for the concernedorder type.

Processing outgoing

EDI Sub-System:

BAAN: In the BAAN table TBecedi011 there must be anentry for this order type in connection with therespective message and organization. TheBAAN table field TFecedi011.koor is mappedto this position. This field is filled with theEDIFACT order types. For example “220” fornormal orders. The inhouse order type isconverted in TBecedi433.

Processing incoming

EDI Sub-System:

BAAN: Mapping to BAAN table field TFecedi702.koor.

In the BAAN table TBecedi200 there must be anentry for this order type in connection with therespective message and organization.


Field name Order type



2-10

Description: This field contains the reference code which theEDI Sub-System applied to this transmission.

Processing outgoing

EDI Sub-System:

BAAN: The position will be filled with the purchaseorder number from BAAN table fieldTFtdpur400.orno

Processing incoming

EDI Sub-System: Transmission of the value from the transmissionfile.

BAAN: Mapping to BAAN table fieldTFecedi702.msno. This field should contain thecustomer purchase order number.

Description: This field contains on the outgoing side thecurrent date / time, on which the order messagewas created. On the incoming side, this fieldcontains the arrival date / time of the order at theEDI Sub-System (format:YYYYMMDDHHMMSS).

Processing outgoing

EDI Sub-System:

BAAN: Mapping of the current date / time to theposition.

Processing incoming

EDI Sub-System: Entry of the arrival date / time of the message atthe EDI Sub-System.

BAAN: Mapping to BAAN table field TFecedi702.send


Field name Transmission Reference

Position 9 Field format n..14 Field status M

Field name Date / Time of transmission



2-11

Description: This field contains the reference number, whichthe EDI Sub-System applied to the previoustransmission.

Processing outgoing

EDI Sub-System:

BAAN: not used

Processing incoming


BAAN: Mapping to BAAN table field TFecedi702.prno.

Description: This fields contains an identification of thetechnical message creator

Processing outgoing

EDI Sub-System:

BAAN: The position will be filled with the constantvalue ‘BAANERP’ .

Processing incoming

EDI Sub-System: The EDI Sub System put its identifierer to thisposition.

BAAN: None.

Position 10 Field format an..20 Field status C

Field name Transmission reference old


Field name Identification of the technical message creator



2-12

Description: Identification if the message is a test message oran original message.

Processing outgoing

EDI Sub-System: None.

BAAN: This field will be filled with the value of tablefield TFecedi003.test. Test messages have to beidentified with a ‘1’, original messages with anempty field.. This has to be marked in the tableTBecedi003.

Processing incoming


BAAN: Test messages are checked but nor entered in thesystem. There will be a report, if the message isokay or not.

Description: This field indicates the end of the data record. Itcontains the constant value ‘SA1_END’.

Processing outgoing

EDI Sub-System:

BAAN: This field will be filled with the constant value‘SA1_END’.

Processing incoming

EDI Sub-System: This field will be filled with the constant value‘SA1_END’.

BAAN: None


Field name Indentification of Test Messages


Field name Data record end sign



2-13

SA2 ORDER HEADERStatus : Mandatory

Frequency: Once by order number

Description: This data record contains all information of the orderheader except of address and text data and is related toSA1.

ORDER INHOUSE FORMAT Mapping from Application Table

Fields (out)

Mapping to Application

Fields (in)

Pos FIELD

DESCRIPTION


1. Kind of data record O/I M an3 SA2 SA2 2. Message reference O/I M an..14 ecedi701.bano ecedi702.bano 3. Identification of the

sender

O/I M an..17 ecedi020.neta Conversion tdsls400.ofbp Conversion

(see below)

4. Customer Order

Number

O/I M an..9

an..30

tdpur400.orno tdsls400.corn

5. Contract Number C an..9 tdpur400.prno Code und

Conversion

tdsls400.prno Code und

Conversion

6. Order Date / Time C n..14 tdpur400.odat tdsls400.odat 7. Delivery Date /

Time

C n..14 tdpur400.ddat

or

tdpur400.ddtc

EDI Expression

ORD1

tdsls400.ddat

8. Term of Delivery C an..6 tdpur400.cdec Code and

Conversion

tdsls400.cdec Code and

Conversion

9. Terms of Payment C an..6 tdpur400.cpay Code and

Conversion

tdsls400.cpay Code and

Conversion

10. Order Discount C n..6 tdpur400.odis NNN.NN tdsls400.odis NNN.NN

11. Currency C an..6 tdpur400.ccur Code and

Conversion

tdsls400.ccur Code and

Conversion

12. Purchase / Sales

Currency Rate

C n..13 tdpur400.ratp

(1)

NNNNNN.NNN

NNN

13. Purchase Rate

Factor

C n..6 tdpur400.ratf

(1)

NNNNNN

14. Late Payment

Surcharge

C n..6 tdpur400.ccrs Code and

Conversion

tdsls400.ccrs Code and

Conversion

15. Forwarding Agent C an..20 tdpur400.cfrw Code and

Conversion

tdsls040.cfrw Code and

Conversion



2-14


Fields (out)


Fields (in)

Pos FIELD

DESCRIPTION


16. Reference A C an..30 tdpur400.refa tdsls400.refa 17. Reference B C an..20 tdpur400.refb tdsls400.refb 18. Qualifier Address

Code

M an2 ZZ ZZ

19. Purchase Price List C an..3 tdpur400.cplp tdsls400.cpls

20. Region C an..3 tdpur400.creg tdsls400.creg

21. Line of Business C an..6 tdpur400.cbrn tdsls400.cbrn

22. Planned receipt date

/ time

C n..14 tdsls400.prdt

23. Description Terms

of Delivery

C an..30 tcmcs041.dsca

24. Description of the

Carrirer


25. Description Late

Payment Surcharges


26. Description Terms

Of Payment


27. Country C an..3 tdpur400.ccty tdsls400.ccty

28. Self Billed Invoice C an1 tdpur400.sbim 0 means empty

position

1 means yes

2 means no

tdsls400.sbim

29. Purchase Office C an..6 tdpur400.cofc Code and

Conversion

30. Buy From Business

Partner

C an..20 tdpur400.otbp Code and

Conversion

31. Qualifier Address /

Partner Code Buy

From

C an4 ecedi224.code “BFBP”

32. Ship From Business

Partner

C an..20 tdpur400.sfbp Code and

Conversion

tdsls400.cwar Code and

Conversion


Partner Code Ship

From

C an4 ecedi224.code “SFBP”

34. Invoice From

Business Partner

C an..20 tdpur400.ifbp Code and

Conversion



2-15


Fields (out)


Fields (in)

Pos FIELD

DESCRIPTION



Partner Code

Invoice From

C an4 ecedi224.code “IFBP”

36. Pay To Business

Partner

C an..20 tdpur400.ptbp Code and

Conversion


Partner Code pay

To

C an4 ecedi224.code “PTBP”

38. Code for the

Warehouse

C an..20 tdpur400.cwar Code and

Conversion

tdsls040.stbp Code and

Conversion


Partner Code

Warehouse

C an4 ecedi224.code “CWAR”

40. Remittance

Agreement

C an..16 tdpur400.ragr

41. Fixed Rate C an..1 tdpur400.mcfr 0 = empty

1 = fixed local

2 = fixed hard

3 = fixed local

and hard

4 = Delivery Date

5 = Document

Date

6 = expected

Cash Date

7 = Manually

Entered

42. Route Plan C an..3 tdpur400.ctrj

43. Original Order Typ C n1 tdpur400.odty 0 means empty

1 means order

2 means receipt

44. Original Order

Number

C an..9 tdpur400.odno

45. Invoice to Business

Partner

C an..20 tdsls400.itbp Code –and

Conversion

46. Pay By Business

Partner

C an..20 tdsls400.pfbp Code –and

Conversion



2-16


Fields (out)


Fields (in)

Pos FIELD

DESCRIPTION


47. Qualifier Sold To

Business Partner

M an4 “STBP” “STBP”

48. Qualifier Ship To

Business Partner

M an4 “SIBP” “SIBP”

49. Qualifier Invoice To

Business Partner

M an4 “ITBP” “ITBP”

50. Qualifier Pay By

Business Partner

M an4 “PBBP” “PBBP”

51. Warehouse Address

Code

an..9 tdpur400.cadr

52. Data record end

sign

M an7 SA2_END SA2_END

EDI-Expression:

ORD1: tdpur400.ddtc <> 0

Detailed description: OrderKind of data record: SA2 Order Header


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:





2-17

Description: This field identifies all connected data recordsof one order. The numbering of the messagereference, which has to be clear by Order, helpsto control the chronological order of the Ordersand the complete transmission.

Processing outgoing

EDI Sub-System:

BAAN: Refer to data record SA1.

Processing incoming

EDI Sub-System: Refer to data record SA1

BAAN:

Description: This field contains the identification of thesender.

Processing outgoing

EDI Sub-System:

BAAN: Refer to data record SA1

Processing outgoing

EDI Sub-System:


Refer to data record SA1




Field name Identification of the sender (Key field out)



2-18

Description: This field contains the order number.

Processing outgoing


BAAN: The purchase order number is mapped fromBAAN table field TFtdpur400.orno to thisposition.

Processing incoming


BAAN: Mapping to BAAN table field TFtdsls400.corn

Description: This field contains the Contract Number whichis defined with the business partner. AConversion is possible.

Processing outgoing

EDI Sub-System: None

BAAN: The purchase contract number is mapped fromBAAN table TBtdpur400.prno to this positionafter conversion with BAAN table TBecedi453.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.prno after conversion with BAANtable TBecedi314.

Position 4 Field format out an..9 / in an..30 Field status M

Field name Order Number (Key field in/out)


Field name Contract Number



2-19

Description: This field contains the date / time(YYYYMMDDHHMMSS) the order is enteredin the system.

Processing outgoing


BAAN: The order date / time from BAAN table fieldTFtdpur400.odat is mapped to this position.

Processing incoming

EDI Sub-System: Transmission of the value from the message fileor entry of the arrival date / time of the messageat the EDI Sub-System (only possible, if thedelivery date / time is not in the past)

BAAN: Mapping to BAAN table field TFtdsls400.odat

Description: This field contains the date / time(YYYYMMDDHHMMSS) on which thedelivery should take place.

Processing outgoing


BAAN: The purchase order delivery date / time fromBAAN table field TFtdpur400.ddat is mapped tothis position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.ddat.

Position 6 Field format n..14 Field status C

Field name Order Date / Time


Field name Delivery Date / Time



2-20

Description: This field contains a code for the Term ofDelivery. This field indicates how to frank theshipment (unfranked,...) It contains a uniquealphanumerical identification.

01 = unfranked (unfrei)

02 = free destination (frei Bestimmungsort)

03 = free to the door (frei Haus)

04 = free German border (frei deutsche Grenze)

05 = free receiving carrier (frei Empfängsspediteur)

99 = special postage (Sonderfrankatur)

Processing outgoing


BAAN: The Term of Delivery of the purchase orderfrom BAAN table field TFtdpur400.cdec ismapped to this position. If other definitions areused in BAAN, the BAAN table TBecedi430 isused for conversion.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.cdec and conversion via BAANtable TBecedi300.


Field name Term of Delivery



2-21

Description: This field contains a Code for the Terms ofPayment agreed upon with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The Terms of Delivery of the purchase orderfrom BAAN table field TFtdpur400.cpay ismapped to this position and converted using thetable TBecedi466.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.cpay and conversion via BAANtable TBecedi326.

Description: This field contains the Order Discount related tothe complete order amount.NNN.NN. Maximum is 100.00

Processing outgoing

EDI Sub-System:

BAAN: The Order Discount of the purchase order fromBAAN table field TFtdpur400.odis is mapped tothis position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.odis


Field name Terms of Payment


Field name Order Discount



2-22

Description: This field contains the Currency relevant for theorder. It contains the clear alphanumericalidentification of the currency. The currencycode will be defined according to ISO 4217,e.g.‚280‘ for German mark (DM). For detailedinformation please refer to the BEMIS VCookbook (U7315AUS).

Processing outgoing

EDI Sub-System:

BAAN: The Currency relevant for the purchase orderfrom BAAN table field TFtdpur400.ccur ismapped to this position and converted usingtable TBecedi438.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.ccur and conversion with BAANtable TBecedi324.


Field name Currency



2-23

Description: This field contains the Rate used to convert thecurrency (position11) into the home currency.

Processing outgoing

EDI Sub-System:

BAAN: The currency rate of the purchase order fromBAAN table field TFtpur400.ratp is mapped tothis position.

Processing incoming

EDI Sub-System:

BAAN: None

Description: This field contains the Rate Factor used as basisfor the conversion of the currency. Mostly used1, 10, 100 or 1000.

Processing outgoing

EDI Sub-System:

BAAN: The rate factor of the purchase order fromBAAN table field TFtdpur400.ratf is mapped tothis position.

Processing incoming

EDI Sub-System:

BAAN: None


Field name Purchase / Sales Currency Rate 1


Field name Purchase Rate Factor 1



2-24

Description: This field contains the Late Payment Surchargeagreed upon with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The Late Payment Surcharge of the purchaseorder from BAAN table field TFtdpur400.ccrs ismapped to this position. A conversion has to bedone with BAAN table TBecedi470.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.ccrs and conversion with BAANtable TBecedi330.

Description: This field contains the Code of the ForwardingAgent used for this order. The code list has to beagreed with the partner.

Processing outgoing

EDI Sub-System:

BAAN: The Code for the Forwarding Agent of thepurchase order from BAAN table fieldTFtdpur400.cfrw is mapped to this position andconverted with BAAN table TBecedi456.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.cfrw and conversion with BAANtable Tbecedi318.


Field name Late Payment Surcharge


Field name Forwarding Agent



2-25

Description: This field contains a reference. You can use thisfield to give further information to yoursupplier.

Processing outgoing

EDI Sub-System:

BAAN: The Reference A of the purchase order fromBAAN table field TFtdpur400.refa is mapped tothis position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.refa.

Description: This field contains a second reference field forfurther information defined with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The Reference B of the purchase order fromBAAN table field TFtdpur400.refb is mapped tothis position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.refb.


Field name Reference A


Field name Reference B



2-26

Description: This field contains the first Qualifier for theDelivery Address Code.

Processing outgoing

EDI Sub-System:

BAAN: The field is filled with the constant value ‘ZZ’.

Processing incoming

EDI Sub-System: This field is filled with the constant value ‘ZZ’.

BAAN:

Description: The price list code used for the order. The codehas to be agreed upon with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The code for the Purchase Price List fromBAAN table field TFtdpur400.cplp is mapped tothis position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.cplp.


Field name Qualifier Address Code


Field name Purchase/Sales Price List



2-27

Description: This field contains the Region thecustomer/supplier belongs to. The Code must bemutual defined with the customer/supplier. Aconversion is not possible.

Processing outgoing

EDI Sub-System:

BAAN: The Region code from BAAN table fieldTFtdpur400.creg is mapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.creg.

Description: This field contains the Code for the Line ofBusiness the customer/supplier belongs to. TheCode must be mutual defined with thecustomer/supplier. A conversion is not possible.

Processing outgoing

EDI Sub-System:

BAAN: The code for the line of business from BAANtable field TFtdpur400.cbrn is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.cbrn


Field name Region


Field name Line of Business



2-28

Description: This field contains the date and the timeinformation in refer to the planned date/timewhen the goods will be receipt. Please refer tothe remarks concerning the new date / timeformat for BAAN ERP above.

Processing outgoing

EDI Sub-System:

BAAN:

Processing incoming

EDI Sub-System: Transmission of the value from the message fileor the same date as filled on position 7.

BAAN: Mapping to the BAAN table fieldTFtdsls400.prdt.

Description: This field contains the description of the TermsDelivery Code in position SA2.8.

Processing outgoing

EDI Sub-System:

BAAN: The description for the code of the terms ofdelivery from BAAN table fieldTFtcmcs041.dsca is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Planned receipt date / time


Field name Description Terms of Delivery



2-29

Description: This field contains the description of the partywho carries the goods.

Processing outgoing

EDI Sub-System:

BAAN: The description of the carrier from BAAN tablefield TFtcmcs080.dsca is mapped to thisposition.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: This field contains the description of the code ofthe late payment surcharges in position SA2.14.

Processing outgoing

EDI Sub-System:

BAAN: The description of the codeof the late paymentsurcharges from BAAN table fieldTFtcmcs011.dsca is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Description of the Carrier


Field name Description Late Payment Surcharges



2-30

Description: This field contains the description of the Codefor the Terms of payment in position SA2.9.

Processing outgoing

EDI Sub-System:

BAAN: The description of the Code for the Terms ofPayment from BAAN table fieldTFtdpur400.dsca is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: This field contains the country code.

Processing outgoing

EDI Sub-System:

BAAN: The Country Code for the from BAAN tablefield TFtdpur400.ccty is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.ccty.


Field name Description Terms of Payment


Field name Country



2-31

Description: This qualifier is used to show whether self billedinvoicing is used or not.

used codes:

“0” means empty position

“1” means yes

“2” means no

Processing outgoing

EDI Sub-System:

BAAN: The Code for Self Billed Invoicing from BAANtable field TFtdpur400.sbim is mapped to thisposition.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: The code of the purchase office.

Processing outgoing

EDI Sub-System:

BAAN: The Code for Purchase Office from BAAN tablefield TFtdpur400.cofc is converted using theconversion table ecedi420 and the defaultqulifier “ZZ”and is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.

Position 28 Field format an1 Field status C

Field name Self Billed Invoice


Field name Purchase Office



2-32

Description: This position contains the code for the BusinessPartner where the customer buys its goods.

Processing outgoing

EDI Sub-System:

BAAN: The Code for the Buy From Business Partnerfrom BAAN table field Tftdpur400.otbp isconverted using the conversion table ecedi468and Address Code Id “ZZ” and is mapped to thisposition.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: This position contains the standard qualifier forthe buy from business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “BFBP” is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Buy From Business Partner


Field name Qualifier Address / Partner Code Buy From



2-33

Description: This position contains the code for the BusinessPartner who will deliver the goods.

Processing outgoing

EDI Sub-System:

BAAN: The Code for the Ship From Business Partnerfrom BAAN table field TFtdpur400.otbp isconverted using the conversion table ecedi468and Address Code Id “ZZ” and is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.cwar using the code and conversiontable ecedi355 and the Address Code Id “ZZ”..

Description: This position contains the standard qualifier forthe ship from business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “SFBP” is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Ship From Business Partner


Field name Qualifier Address / Partner Code Ship From



2-34

Description: This position contains the code for the BusinessPartner who will send the invoice to thecustomer.

Processing outgoing

EDI Sub-System:

BAAN: The Code for the Invoice From Business Partnerfrom BAAN table field Tftdpur400.ifbp isconverted using the conversion table ecedi468and the Address Code Id “ZZ” and is mapped tothis position.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: This position contains the standard qualifier forthe invoice from business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “IFBP” is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Invoice From Business Partner


Field name Qualifier Address / Partner Code Invoice From



2-35

Description: This position contains the code for the BusinessPartner who will get the money from thecustomer.

Processing outgoing

EDI Sub-System:

BAAN: The Code for the Pay To Business Partner fromBAAN table field Tftdpur400.ptbp is convertedusing the conversion table ecedi468 and theAddress Code Id “ZZ”and is mapped to thisposition.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: This position contains the standard qualifier forthe Pay To business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “PTBP” is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Pay To Business Partner


Field name Qualifier Address / Partner Code Pay To



2-36

Description: This position contains the code for thecustomer’s warehouse.

Processing outgoing

EDI Sub-System:

BAAN: The Code for the customer’s warehouse fromBAAN table field TFtdpur400.cwar is convertedusing the conversion table ecedi462 and thequalifier “ZZ”and is mapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.sfbp using the code and conversiontable ecedi328 .and the Address Code ID “ZZ”.

Description: This position contains the standard qualifier forthe ship from business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “SFBP” is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Code for the Warehouse


Field name Qualifier Address / Partner Code Warehouse



2-37

Description: A subcontracting document that containsagreements about how the payment for a projectwill take place. For example, the remittanceagreement states the part of the invoice amountthat must be paid to the subcontractor’sindustrial assurance board (IAB) and to the taxauthorities.

Processing outgoing

EDI Sub-System:

BAAN: The Remittance Agreement number fromBAAN table field TFtdpur400.ragr is mapped tothis position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Remittance Agreement



2-38

Description: The exchange rate agreed upon by contract withyour bank or business partner (in order to avoida currency loss).Used values:

0 = empty1 = fixed local2 = fixed hard3 = fixed local and hard4 = Delivery Date5 = Document Date6 = expected Cash Date7 = Manually Entered

Processing outgoing

EDI Sub-System:

BAAN: The Fixed Rate identifier from BAAN tablefield TFtdpur400.mcfr is mapped to thisposition.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Fixed Rate



2-39

Description: The code for the Rout Plan which is the code forthe line of travel from a warehouses to the ship-to or ship-from business partner’s warehouseand vice versa. Use routes to group businesspartners that are located in the same area oralong one convenient route.

Processing outgoing

EDI Sub-System:

BAAN: The Code for Route Plan from BAAN tablefield TFtdpur400.ctrj is mapped to this position.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: Qualifier to show the origin of the original OrderNumber: Used values:0 means empty1 means order2 means receiptOnly used for return orders.

Processing outgoing

EDI Sub-System:

BAAN: The qualifier for the original order type fromBAAN table field TFtdpur400.odty is mapped tothis position.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Route Plan


Field name Original Order Type



2-40

Description: This position contains the original order number.Only used for return orders.

Processing outgoing

EDI Sub-System:

BAAN: The original order number from BAAN tablefield TFtdpur400.odno is mapped to thisposition.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: This position contains the code for the receiverof the invoice.

Processing outgoing

EDI Sub-System:

BAAN: None.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.itbp using the code and conversiontable ecedi328 .and the Address Code Id “ZZ”.


Field name Original Order Number


Field name Invoice To Business Partner



2-41

Description: This position contains the code for party whichshould pay the invoice.

Processing outgoing

EDI Sub-System:

BAAN: None.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls400.pfbp using the code and conversiontable ecedi328 .and the Address Code Id “ZZ”.

Description: This position contains the standard qualifier forthe Sold To business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “PTBP” is mapped to this position.

Processing incoming

EDI Sub-System: Transmission of the constant value “PTBP” tothe message file.

BAAN: None.


Field name Pay By Business Partner


Field name Qualifier Sold To Business Partner



2-42

Description: This position contains the standard qualifier forthe Ship To business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “SIBP” is mapped to this position.

Processing incoming

EDI Sub-System: Transmission of the constant value “SIBP” tothe message file.

BAAN: None.

Description: This position contains the standard qualifier forthe Invoice To business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “ITBP” is mapped to this position.

Processing incoming

EDI Sub-System: Transmission of the constant value “ITBP” tothe message file.

BAAN: None.


Field name Qualifier Ship To Business Partner


Field name Qualifier Invoice To Business Partner



2-43

Description: This position contains the standard qualifier forthe Pay By business partner.

Processing outgoing

EDI Sub-System:

BAAN: The constant “PBBP” is mapped to this position.

Processing incoming

EDI Sub-System: Transmission of the constant value “PBBP” tothe message file.

BAAN: None.

Description: This field contains the warehouse code.

Processing outgoing

EDI Sub-System:

BAAN: The warehouse code from BAAN table fieldTFtdpur400.cwar is mapped to this positionafter conversion with BAAN table TBecedi462.

Processing incoming

EDI Sub-System:

BAAN: None


Field name Qualifier Pay By Business Partner


Field name Warehouse Address Code



2-44


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: None





2-45

SA3 ORDER TEXT - TEXTDATEN

Status : Conditional

Frequency : Once by order number

Description: This data record contains the text information of theorder header and is related to SA2.

ORDERS) INHOUSE FORMAT Mapping from Application

Table Fields


Pos FIELD

DESCRIPTION


1. Kind of data record O/I M an3 SA3 SA3

2. Message reference O/I M an..14 ecedi701.bano ecedi702.bano


sender

O/II M an..17 ecedi020.neta Conversion tdsls400.ofbp Conversion (see

below)

4. Order Number O/I M an..9

an..30

tdpur400.orno

tdsls400.corn

5. Free Header Text 1 C an..70 tdpur400.txta tdsls400.txta





10. Data record end

sign




2-46

Detailed Description: OrderKind of data record: SA3 Order text


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: None

Description: This field identifies all connected data recordsof one Order. The numbering of the messagereference, which has to be clear by Order, helpsto control the chronological order of the Ordersand the complete transmission.

Processing outgoing

EDI Sub-System:


Processing incoming

EDI Sub-System: Refer to data record SA2.








2-47


Processing outgoing



Processing incoming




Processing outgoing

EDI Sub-System:

BAAN: The order number of the purchase order fromBAAN table field TFtdpur400.orno is mappedto this position.

Processing incoming


BAAN: Mapping to BAAN table field TFtdsls400.corn.


Field name Identification of the sender (Key field out/in)

Position 4 Field format out an..9 / in an..30 Field status M




2-48

Description: This field contains a free text with a maximumof 70 characters.

Processing outgoing

EDI Sub-System:

BAAN: Mapping of BAAN table field TFtdpur400.txtato position.

Processing incoming


BAAN: Mapping to BAAN table field TFtdsls400.txta


Processing outgoing

EDI Sub-System:


Processing incoming




Field name Free text 1





2-49


Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing

EDI Sub-System:


Processing incoming









2-50


Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: None







2-51

SA4 Order Specific AddressesStatus : Conditional

Frequency : Twice at maximum by order number

Description: This data record contains the specific addresses of theorder header and is related to SA2.

First Appearance: Ship From Business Partner Address( Address Qualifier: SFBP )


Table Fields


Fields

Pos FIELD

DESCRIPTION


1. Kind of data

record

O/I M an3 SA4 SA4


3. Identification of

the sender)

O/II M an..17 ecedi020.neta Conversion tdsls400.ofbp Conversion

4. Order Number O/I M n..9

an..30

tdpur400.orno

tdsls400.corn

5. Address Qualifier

Ship From

Business Partner

Address

M an4 ”SFBP” “SFBP” Code and

Conversion

6. Ship From

Business Partner

Address Country

C an..6 tccom130.ccty ORD3 tccom130.ccty Code and

Conversion

7. Ship From

Business Partner

Address first part

of the name

C an..35 tccom130.nama

ORD3 tccom130.nama



2-52


Table Fields


Fields

Pos FIELD

DESCRIPTION


8. Ship From

Business Partner

Address second

part of the name

C an..30 tccom130.namb

ORD3 tccom130.namb

9. Ship From

Business Partner

Address third part

of the name

C an..30 tccom130.namc

ORD3

tccom130.namc

10. Ship From

Business Partner

Address 2

C an..30 tccom130.namd

ORD3 tccom130.namd

11. Ship From

Business Partner

Address City

C an..30 tccom130.name

ORD3 tccom130.name

12. ILN Code, Ship

From Business

Partner Address

C an..30 tccom130.namf

ORD3 tccom130.namf

13. Ship From

Business Partner

Address Zip Code

C an..10 tccom130.pstc

ORD3 tccom130.pstc

14. Ship From

Business Partner

Address Tax Id

C an..20 tccom130.fovn ORD3 tccom130.fovn

15.

16. TAX Code Id

Qualifier

M an3 “VAT” ORD3

17. Ship From

Business Partner

Address State /

Province

C an..2 tccom130.cste ORD3 tccom130.cste



2-53


Table Fields


Fields

Pos FIELD

DESCRIPTION


18. Ship From

Business Partner

Telephone

Number

C an..15 tccom130.telp ORD3 tccom130.telp

19. Ship From

Business Partner

Telex Number

C an..15 tccom130.telx ORD3 tccom130.telx

20. Ship From

Business Partner

Fax Number

C an..15 tccom130.tefx ORD3 tccom130.tefx

21. Ship From

Business Partner

GEO Code

C an..10 tccom130.geoc ORD3 tccom130.geoc

22. Ship From

Business Partner

House Number

C an..10 tccom130.hono ORD3 tccom130.hono

23. Ship From

Business Partner

P. O. Box Number

C an..10 tccom130.pobn ORD3 tccom130.pobn

24. Data record end

sign

M an7 SA4_END ORD3 SA4_END

Evaluation Expression.

ORD3: (strip(tdpur400.sfad) <> "" and tdpur400.sfad <> tccom121.cadr)



2-54

Second Appearance: Warehouse Address ( AddressQualifier: CWAR )


Table Fields


Fields

Pos FIELD

DESCRIPTION


1. Kind of data

record

O/I M an3 SA4 SA4



the Sender



an..30

tdpur400.orno

tdsls400.corn


Warehouse

Address

M an4 “CWAR”

6. Warehouse

Address Country

C an..6 tccom130.ccty

ORD6 tccom130.ccty

Code and

Conversion

7. Warehouse

Address first part

of the name


ORD6 tccom130.nama

8. Warehouse

Address second

part of the name


ORD6 tccom130.namb

9. Warehouse

Address third part

of the name


ORD6 tccom130.namc

10. Warehouse

Address 2


ORD6 tccom130.namd

11. Warehouse

Address City


ORD6 tccom130.name



2-55


Table Fields


Fields

Pos FIELD

DESCRIPTION


12. ILN Code,

Warehouse

Address


ORD6 tccom130.namf

13. Warehouse

Address Zip Code


ORD6 tccom130.pstc

14. Warehouse

Address Tax Id


15. empty Position C an..35 for later use ORD6 for later use

16. TAX Code Id

Qualifier

M an3 “VAT” ORD6 “VAT”

17. Warehouse

Address State /

Province Code

C an..2 tccom130.cste ORD6 tccom130.cste

18. Warehouse

Address

Telephone

Number


19. Warehouse

Address Telex

Number


20. Fax Number C an..15 tccom130.tefx ORD6 tccom130.tefx

21. Warehouse

Address GEO

Code


22. Warehouse

Address House

Number

C an..10 tccom130.hono ORD6 tccom130.hono

23. Warehouse

Address P. O. Box

Number

C an..10 tccom130.pobn ORD6 tccom130.pobn



2-56


Table Fields


Fields

Pos FIELD

DESCRIPTION


24. Data record end

sign


Evaluation Expression.

ORD6: strip(tdpur400.cadr) <> "" and tdpur400.cadr <> tcmcs003.cadr)



2-57

Detailed description: Specific Order AddressesKind of data record: SA4 Specific Order Addresses

First Appearance: Ship from Business partner Address( Address Qualifier: SFBP )


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:







2-58

Description: This field contains the identification code of thesender.

Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing



Processing incoming

EDI Sub-System:




Position 4 Field format an..9/an..30 Field status M




2-59

Description: This field contains the Qualifier which identifiesthe next data set as an ship from or an ship toaddress.

SFBP The following data is the Ship From Address

CWAR The following data is the Ship to (delivery) address

This qualifier must be entered in BAAN tableTBecedi224 regarding to the used organization.

Processing outgoing

EDI Sub-System:

BAAN: The value “SFBP” or is filled in from BAANtable field ecedi224.code.

Processing incoming

EDI Sub-System: The value “SFBP” is filled in this position.

BAAN: Mapping to BAAN table field TFtdsls042.ckorand Conversion with TBecedi224.


Field name Address Qualifier Address Ship From B.P.



2-60

Description: This field contains the Country of the Address.The following country codes are defined inBAAN table TBecedi226 according to ODDC 6

AT: AustriaBE: BelgiumCH: SwitzerlandDE: Federal Republik of GermanyDK: DenmarkES: SpainFI: FinlandFR: FranceGB: United KingdomGR: GreeceIE: IrelandIT: ItalyLU: LuxembourgNL: NetherlandsNO: NorwayPT: PortugalSE: SwedenTR: TurkeyYU: Yugoslavia

Processing outgoing

EDI Sub-System:

BAAN: The country code of the delivery address fromBAAN table field tccom130.ccty is mapped tothis position and converts with BAAN tableTBecedi440.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.ccty and conversion with BAANtable TBecedi302.


Field name Ship From B. P. Address Country



2-61

Description: This field contains the first part of the name.

Processing outgoing

EDI Sub-System:

BAAN: The First part of the Name from BAAN tablefield TFtccom130.nama is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.nama

Description: This field contains the second part of the name.

Processing outgoing

EDI Sub-System:

BAAN: The Second part of the Name from BAAN tablefield TFtccom130.namb is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.namb


Field name Ship From B. P. Address First part of Name


Field name Ship From B. P. Address Second part of Name



2-62

Description: This field contains the first part of the DeliveryAddress.

Processing outgoing

EDI Sub-System:

BAAN: The first part of the Address from BAAN tablefield TFtccom130.namc is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.namc

Description: This field contains the second part of thedelivery address.

Processing outgoing

EDI Sub-System:

BAAN: The second part of the Address from BAANtable field TFtccom130.namd is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.namd


Field name Ship From B. P. Address 3rd part of the name


Field name Ship From B. P. Address 2



2-63

Description: This field contains the name of the City.

Processing outgoing

EDI Sub-System:

BAAN: The name of the City from BAAN table fieldTFtccom130. name is mapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.name

Description: This field contains further information to theCity (province/country)

Processing outgoing

EDI Sub-System:

BAAN: The ILN-Code from BAAN table fieldTFtccom130.namf is mapped to this position.

Processing incoming


BAAN: The ILN-Code is mapped to BAAN table fieldTFtccom130.namf.


Field name Ship From B. P. Address City


Field name ILN Code / Ship From B. P. further information provinceor country



2-64

Description: This field contains the postal or zip Codereferring to the Address.

Processing outgoing

EDI Sub-System:

BAAN: The Zip Code from BAAN table fieldTFtccom130.pstc is mapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.pstc

Description: This field contains the Tax ID.

Processing outgoing

EDI Sub-System:

BAAN: The tax ID of BAAN table fieldTFtccom130.fovn is mapped to this position.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.fovn.


Field name Ship From B. P. Address Zip Code


Field name Ship From B. P. Address Tax ID



2-65

Description: empty position for later use.

Processing outgoing

EDI Sub-System:

BAAN: None.

Processing incoming

EDI Sub-System:

BAAN: None.

Description: This field contains the Tax Code ID Qualifier“VAT”.

Processing outgoing

EDI Sub-System:

BAAN: This field is filled with the constant value“VAT”.

Processing incoming

EDI Sub-System:

BAAN: None


Field name empty Position


Field name Tax ID Qualifier



2-66

Description: This field contains the code for the State /Province. The tax provider identifies the taxjurisdictions by means of GEO codes. The GEOcodes are assigned to the addresses, based on thefollowing address data:

City

State/province and

ZIP/postal code

Processing outgoing

EDI Sub-System:

BAAN: The State /Province Code from BAAN tablefield TFtccom130.cste is mapped to thisposition.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.cste.

Description: This field contains the Telephone Number.

Processing outgoing

EDI Sub-System:

BAAN: The telephone number of BAAN table fieldTFtccom130.telp is mapped to this position.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.telp.


Field name Ship From B. P. Adress State/Province Code


Field name Ship From B. P. Telephon Number



2-67

Description: This field contains the Telex Number.

Processing outgoing

EDI Sub-System:

BAAN: The telex number of BAAN table fieldTFtccom130.telx is mapped to this position.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.telx.

Description: This field contains the Faxnumber.

Processing outgoing

EDI Sub-System:

BAAN: The Faxnumber of BAAN table fieldTFtccom130.tefx is mapped to this position.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.tefx.


Field name Ship From B. P. Telex Number


Field name Ship From B. P. Fax Number



2-68

Description: This field contains the GEO-Code.

Processing outgoing

EDI Sub-System:

BAAN: The GEO-Code of BAAN table fieldTFtccom130.deoc is mapped to this position.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.geoc.

Description: This field contains the housenumber of theaddress.

Processing outgoing

EDI Sub-System:

BAAN: The housenumber of BAAN table fieldTFtccom130.hono is mapped to this position.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.hono.


Field name Ship From B. P. GEO Code


Field name Ship From B. P. Housenumber



2-69

Description: This field contains the P.O. Box Number.

Processing outgoing

EDI Sub-System:

BAAN: The P.O. Box Number of BAAN table fieldTFtccom130.pobn is mapped to this position.

Processing incoming


BAAN: Mapped to BAAN table field tccom130.pobn.


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: None


Field name Ship From B. P. P.O.Box Number





2-70

Second Appearance: Warehouse Address( Address Qualifier: CWAR )


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:







2-71


Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing



Processing incoming

EDI Sub-System:








2-72


SFBP The following data is the Ship From Address

CWAR The following data is the Ship to (delivery) address


Processing outgoing

EDI Sub-System:

BAAN: The value “CWAR” or is filled in from BAANtable field ecedi224.code.

Processing incoming

EDI Sub-System: The value “CWAR” is filled in this position.

BAAN: Mapping to BAAN table field TFtdsls042.ckorand Conversion with Tbecedi224..


Field name Address Qualifier Warehouse Specific Address



2-73



Processing outgoing

EDI Sub-System:

BAAN: The country code of the address from BAANtable field tccom130.ccty is mapped to thisposition and converts with BAAN tableTbecedi440.

Processing incoming


BAAN: Mapping to the BAAN table fieldTftccom130.ccty and conversion with BAANtable TBecedi302.


Field name Warehouse Address Country



2-74


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: Mapping to the BAAN table fieldTftccom130.nama


Processing outgoing

EDI Sub-System:


Processing incoming




Field name Address First part of Name


Field name Warehouse Address Second part of Name



2-75

Description: This field contains the first part of the Address.

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the second part of theaddress.

Processing outgoing

EDI Sub-System:

BAAN: The second part of the Address from BAANtable field TFtccom130.namd is mapped to thisposition.

Processing incoming




Field name Warehouse Address 3rd part of the name


Field name Warehouse Address 2



2-76


Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address City


Field name ILN Warehouse Code / further information province orcountry



2-77

Description: This field contains the postal or zip Codereferring to the Address.

Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address Zip Code


Field name Warehouse Address Tax ID



2-78

Description: empty position for later use.

Processing outgoing

EDI Sub-System:

BAAN: None.

Processing incoming

EDI Sub-System:

BAAN: None.


Processing outgoing

EDI Sub-System:


Processing incoming

EDI Sub-System:

BAAN: None


Field name empty Position


Field name Tax ID Qualifier



2-79

Description: This field contains the code for the State /Province. The tax provider identifies the taxjurisdictions by means of GEO codes. The GEOcodes are assigned to the addresses, based on thefollowing address data:

City

State/province and

ZIP/postal code

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the Telephone Number.

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address State/Province Code


Field name Warehouse Address Telephon Number



2-80

Description: This field contains the Telex Number.

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the Faxnumber.

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address Telex Number


Field name Warehouse Address Fax Number



2-81

Description: This field contains the GEO-Code.

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the housenumber of theaddress.

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address GEO Code


Field name Warehouse Address Housenumber



2-82

Description: This field contains the P.O. Box Number.

Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: None


Field name Warehouse Address P.O.Box Number





2-83

SA5 Order LinesStatus : Mandatory

Frequency : Multiple times per order number

Description: This data records contain the information about theordered items. It is related to SA2.


Table Fields


Pos FIELD

DESCRIPTIO

N


1. Kind of data

record

O/I M an3 SA5 SA5

2. Message

reference

O/I M an..14 ecedi701.bano ecedi702.bano


the sender



an..30

tdpur400.orno

tdsls401.corn

5. Order Position

Number

M n..5

an..16

tdpur401.pono

tdsls401.corp

6. Buyer’s Item

Code or EAN

Item Code

C an..47 tdpur401.item (for EAN

Conversion

)

tdsls401.item Conversion

7. Supplier’s Item

Code

C an..47 tdpur401.item Conversion

8. Qualifier Item

Code

M an2 SA SA or None depends on

Conversion

9. Description of

the Item

C an..30 tcibd001.dsca

10. Item’s price C n..19 tdpur401.pric tdsls401.pric



2-84


Table Fields


Pos FIELD

DESCRIPTIO

N


11. Purchase/Sales

Unit

C an..3 tdpur401.cuqp Code and

Conversion

tdsls401.cuqs Code and

Conversion

12. Ordered

Quantity

C n..15 tdpur401.oqua tdsls401.oqua

13. Planned Delivery

Date / Time

C n..14 tdpur401.ddta tdsls401.ddta

14. Purchase / Sales

Price Unit

C an..3 tdpur401.cupp Code and

Conversion

tdsls401.cups Code and

Conversion

15. Tax Code C an..10 tdpur401.cvat Code and

Conversion

16. Country Code

linked to the Tax

Code

C an..6 tdpur401.ccty Code and

Conversion

17. Length of the

Item

C n..8 tdpur401.leng tdsls401.leng

18. Width of the

Item

C n..8 tdpur401.widt tdsls401.widt

19. Height or

Thickness of the

Item

C n..8 tdpur401.thic tdsls401.thic

20. Back Order

Quantity

C n..15 tdpur401.bqua

21. Discount Code 1 C an..20 tdpur401.cdis(1) Code- and

Conversion

tdsls401.cdis(1) Code- and

Conversion

22. Order Line

Discount

Amount 1

C n..15 tdpur401.ldam(1) tdsls401.ldam(1)


Conversion


Conversion



2-85


Table Fields


Pos FIELD

DESCRIPTIO

N


24. Order Line

Discount

Amount 2



Conversion


Conversion

26. Order Line

Discount

Amount 3


27. Order Line Text

1

C an..70 tdpur401.txta(1) tdsls401.txta(1)

28. Order Line Text

2

C an..70 tdpur401.txta(2) tdsls401.txta(2)

29. Qualifier Tax

Code Id

M an3 ”VAT”

30. Order Date /

Time

C n..14 tdpur401.odat tdsls401.odat

31. Current Planned

Receipt Date /

Time

C n..14 tdsls401.prdt

32. empty position C an..35 for later use for later use

33. Order Line

Discount

Percentage 1

C n..6 tdpur401.disc(1) NNN.NN tdsls401.disc(1)

34. Order Line

Discount

Percentage 2


35. Order Line

Discount

Percentage 3




2-86


Table Fields


Pos FIELD

DESCRIPTIO

N


36. Order Line

Discount

Percentage 4


37. Order Line

Discount

Percentage 5



Conversion


Conversion


Conversion


Conversion

40. Order Line

Discount

Amount 4


41. Order Line

Discount

Amount 5


42. Discount Method

1

C an..20 tdpur401.dmth(1) Code- and

Conversion

tdsls401.dmth(1)

43. Discount Method

2


Conversion

tdsls401.dmth(2)

44. Discount Method

3


Conversion

tdsls401.dmth(3)

45. Discount Method

4


Conversion

tdsls401.dmth(4)

46. Discount Method

5


Conversion

tdsls401.dmth(5)

47. Manufacturer C an..6 tdpur401.cmnf tdsls401.cmnf



2-87


Table Fields


Pos FIELD

DESCRIPTIO

N


48. Product Class C an..6 tdpur401.cpcl tdsls401.cpcl

49. Confirmed

Delivery Date /

Time

C n..14 tdpur401.ddtb

tdpur401.ddtc Evaluation

Expression

ORD7

50. Forwarding

Agent

C an..20 tdpur401.cfrw Code and

Conversion

tdsls401.cfrw Code and

Conversion

51. Ship from

Business Partner

C an..20 tdpur401.sfbp Code and

Conversion

tdsls401.cwar Code and

Conversion

52. Qualifier

Address / Partner

Code

C an4 ecedi224.code “SFBP”

53. Warehouse Code C an..20 tdpur401.cwar Code and

Conversion

tdsls401.stbp Code and

Conversion

54. Qualifier

Address /

Warehouse Code

C an4 ecedi224.code “CWAR”

55. Ordered Amount C n..13 tdpur401.oamt

56. Qualifier C an2 “ZZ”

57. Qualifier Sold

To Business

Partner

an4 “STBP”

58. Data record end

sign


Evaluation Expression:

ORD7: tdpur401.ddtc <> 0



2-88

Detailed description: Order LinesKind of data record: SA5 Order Lines


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:







2-89


Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing


BAAN: The purchase order number is mapped fromBAAN table field TFtdpur400.orno to thisposition.

Processing incoming


BAAN: Mapping to BAAN table field TFtdsls400.corn


Field name Identification of the Sender (Key field out)

Position 4 Field format n..9 /an..30 Field status M




2-90

Description: This field contains the Order Position Number.

Processing outgoing

EDI Sub-System:

BAAN: The order line number of the lines of thepurchase order from BAAN table fieldTFtdpur401.pono is mapped to this position.

Processing incoming


BAAN: Mapping to BAAN table field TFtdsls401.corp

Description: This field contains the Buyer’s Item Code.

Processing outgoing

EDI Sub-System:

BAAN: The item code from BAAN table fieldTFtdpur401.item is mapped to this position. Ifthe buyer wants to send out the EAN Item Codea conversion is needed. This means that thebuyers item code has to convert using the codeand conversion table TBecedi444. Furthermoreplease notice, that the conversion setup has to beadapted to the demand under the use of thequalifier “SA” or “EAN”.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.item after conversion with qualifier“SA” or “EAN”. If no conversion should takeplace, the Qualifier on position 8 must beempty.

Position 5 Field format n..5/an..16 Field status M

Field name Order Position Number


Field name Buyer‘s Item Code / EAN Item Code



2-91

Description: This field contains the Supplier item Code.

Processing outgoing

EDI Sub-System:

BAAN: The supplier item code from BAAN table fieldTFtdpur401.item is mapped to this position afterconversion with qualifier “SA”.

Processing incoming


BAAN: None.

Description: This field contains the qualifier for the itemcode. The constant value ‘SA’ indicates, that thesupplier item codes are used. ‘EAN’ means thatthe EAN Code is used.

Processing outgoing

EDI Sub-System:

BAAN: This field will be filled with the constant value‘SA’ or ‘EAN’.

Processing incoming

EDI Sub-System: This field will be filled with the constant value‘SA’ or ‘EAN’, if the supplier item code or theEAN Code on position 6 is used.

BAAN: Used as qualifier for the conversion of the itemcode.


Field name Supplier‘s item code


Field name Qualifier Item Code



2-92

Description: This field contains the description of the item.

Processing outgoing

EDI Sub-System:

BAAN: The description of the item from BAAN tablefield TFtcibd001.dsca is mapped to thisposition.

Processing incoming


BAAN: None.

Description: This field contains the price of the item.

Format: NNNNNNNNNNNNNN.NNNN

Processing outgoing

EDI Sub-System:

BAAN: The price from BAAN table fieldTFtdpur401.pric is mapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.pric


Field name Description of the item


Field name Price



2-93

Description: This field contains the purchase/sales unit of theitem. The coding was carried out on the basis ofODETTE-Standard ODDC 25:

MillimeterCentimeterMeterKilometerSquare millimeterSquare centimeterSquare meterCubic millimeterCubic centimeterCubic meterLiterGramKilogramMetric tonPiece

MMTCMTMTRKMTMMKCMKMTKMMQCMQMTQDMQGRMKGMTONPCE

Processing outgoing

EDI Sub-System:

BAAN: The purchase unit from BAAN table fieldTFtdpur401.cupq is mapped to this position andconverted with BAAN table TBecedi442.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.cuqs and conversion with BAANtable TBecedi304.


Field name Purchase/Sales Unit



2-94

Description: This field contains the quantity ordered on thisorder line.

Format: NNNNNNNNNN.NNNN

Processing outgoing

EDI Sub-System:

BAAN: The ordered quantity from BAAN table fieldTFtdpur401.oqua is mapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.oqua

Description: This field contains the date / time on which thedelivery is planned or the customer wants to bedelivered.

Processing outgoing

EDI Sub-System:

BAAN: The planned delivery date / time from BAANtable field TFtdpur401.ddta is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.ddta


Field name Ordered Quantity


Field name Planned Delivery Date / Time



2-95

Description: This field contains purchase/sales unit the pricerefers to. The coding was carried out on thebasis of ODETTE-Standard ODDC 25:

MillimeterCentimeterMeterKilometerSquare millimeterSquare centimeterSquare meterCubic millimeterCubic centimeterCubic meterLiterGramKilogramMetric tonPiece

MMTCMTMTRKMTMMKCMKMTKMMQCMQMTQDMQGRMKGMTONPCE

Processing outgoing

EDI Sub-System:

BAAN: The purchase price unit from BAAN table fieldTFtdpur401.cupp is mapped to this position andconverted with BAAN table TBecedi442.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.cups and conversion with BAANtable TBecedi304 is possible.


Field name Purchase/Sales Price Unit



2-96

Description: This field contains the tax code. The conversionis done using the BAAN table TBecedi242 isfilled.

Processing outgoing

EDI Sub-System:

BAAN: The tax code from BAAN table fieldTFtdpur401.cvat is mapped to this position andconverted with BAAN table TBecedi446.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Tax Code



2-97

Description: This field contains the Country Code which islinked to the tax code according to ODDC 6.


Processing outgoing

EDI Sub-System:

BAAN: The country code from BAAN table fieldTFtdpur401ccty is mapped to this positionand converted with BAAN table TBecedi440.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Country Code linked to tax code



2-98

Description: This field contains the length of the item basedon an agreed physical unit.

Format: NNNNN.NN

Processing outgoing

EDI Sub-System:

BAAN: The length from BAAN table fieldTFtdpur401.leng is mapped to this position .

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.leng

Description: This field contains the width of the item basedon an agreed physical unit.Format: NNNNN.NN

Processing outgoing

EDI Sub-System:

BAAN: The width from BAAN table fieldTFtdpur401.widt is mapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.widt


Field name Length


Field name Width



2-99

Description: This field contains the height or thickness of theitem based on an agreed physical unit..

Format: NNNNN.NN

Processing outgoing

EDI Sub-System:

BAAN: The height from BAAN table fieldTFtdpur401.thic is mapped to this position .

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.thic

Description: The quantity yet to be delivered by the supplieris registered as back order.


Processing outgoing

EDI Sub-System:

BAAN: The back order quantity from BAAN table fieldTFtdpur401.bqua is mapped to this position .

Processing incoming


BAAN: None.


Field name Higth


Field name Back Order Quantity



2-100

Description: This field contains the Code for the firstdiscount and has to be agreed with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The code for the first discount from BAANtable field TFtdpur401.cdis is mapped to thisposition and converted using BAAN tableTBecedi474.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.cdis (1) and conversion usingBAAN table TBecedi332.

Description: This field contains the Amount of the OrderLine Discount.


Processing outgoing

EDI Sub-System:

BAAN: The amount of the first discount from BAANtable field TFtdpur401.ldam(1) is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.ldam (1)


Field name Discount Code 1


Field name Order Line Discount Amount 1



2-101

Description: This field contains the Code for the seconddiscount and has to be agreed with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The code for the first discount from BAANtable field TFtdpur401.cdis(2) is mapped to thisposition and converted using BAAN tableTBecedi474.

Processing incoming





Processing outgoing

EDI Sub-System:

BAAN: The amount of the second discount from BAANtable field TFtdpur401.ldam(2) is mapped to thisposition.

Processing incoming









2-102

Description: This field contains the Code for the thirddiscount and has to be agreed with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The code for the first discount from BAANtable field TFtdpur401.cdis(3) is mapped to thisposition and converted using BAAN tableTBecedi474.

Processing incoming





Processing outgoing

EDI Sub-System:

BAAN: The amount of the third discount from BAANtable field TFtdpur401.ldam(3) is mapped to thisposition.

Processing incoming









2-103

Description: This field contains the first part of the order linetext.

Processing outgoing

EDI Sub-System:

BAAN: The first part of the order line text from BAANtable field TFtdpur401.txta(1) is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.txta (1)

Description: This field contains the second part of the orderline text.

Processing outgoing

EDI Sub-System:

BAAN: The second part of the order line text fromBAAN table field TFtdpur401.txta(2) is mappedto this position .

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.txta (2)


Field name Order Line Text 1


Field name Order Line Text 2



2-104

Description: This field contains the Qualifier for the TaxCode ID on position 15.

This tax code must be filled in BAAN tableTBecedi240 to allow a conversion.

Processing outgoing

EDI Sub-System:

BAAN: The field is filled with the constant value“VAT”.

Processing incoming

EDI Sub-System: The field is filled with the constant value“VAT”.

BAAN: None.

Description: The order date / time of the order line is the date/ time on which the order line was entered intothe system. (YYYYMMDDHHMMSS)

Processing outgoing

EDI Sub-System:

BAAN: The order date / time of the purchase order linefrom BAAN table field TFtdpur401.odat ismapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.odat


Field name Qualifier Tax Code ID


Field name Order Date / Time



2-105

Description: This field contains the planned receipt date /time.

Format: YYYYMMDDHHMMSS.

Processing outgoing

EDI Sub-System:

BAAN:

Processing incoming

EDI Sub-System: Transmission of the value from the message file.If not used, the date / time of position 14 mustbe filled in here too

BAAN: Mapping to the BAAN table fieldTFtdsls401.prdt

Description: empty position, for future use

Processing outgoing

EDI Sub-System:

BAAN: None.

Processing incoming

EDI Sub-System:

BAAN: None.


Field name Planned Receipt Date / Time


Field name empty position



2-106

Description: This field contains the first Percentage of theOrder Line Discount.Format: NNN.NNMaximum is 100.00

Processing outgoing

EDI Sub-System:

BAAN: The percentage of the first discount from BAANtable field TFtdpur401.disc(1) is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.disc (1)

Description: This field contains the second Percentage of theOrder Line Discount.Format: NNN.NNMaximum is 100.00

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Order Line Discount Percentage 1





2-107

Description: This field contains the first Percentage of theOrder Line Discount.

Format: NNN.NN

Maximum is 100.00

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the fourth Percentage of theOrder Line Discount.Format: NNN.NNMaximum is 100.00

Processing outgoing

EDI Sub-System:

BAAN: The percentage of the fourth discount fromBAAN table field TFtdpur401.disc(4) is mappedto this position.

Processing incoming









2-108

Description: This field contains the fifth Percentage of theOrder Line Discount.Format: NNN.NNMaximum is 100.00

Processing outgoing

EDI Sub-System:

BAAN: The percentage of the fifth discount fromBAAN table field TFtdpur401.disc(5) is mappedto this position.

Processing incoming



Description: This field contains the Code for the fourthdiscount and has to be agreed with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The code for the first discount from BAANtable field TFtdpur401.cdis(4) is mapped to thisposition and converted using BAAN tableTbecedi474.

Processing incoming









2-109

Description: This field contains the Code for the fifthdiscount and has to be agreed with the relation.

Processing outgoing

EDI Sub-System:

BAAN: The code for the first discount from BAANtable field TFtdpur401.cdis(5) is mapped to thisposition and converted using BAAN tableTbecedi474.

Processing incoming





Processing outgoing

EDI Sub-System:

BAAN: The amount of the fourth discount from BAANtable field TFtdpur401.ldam(4) is mapped to thisposition.

Processing incoming









2-110



Processing outgoing

EDI Sub-System:

BAAN: The amount of the second discount from BAANtable field TFtdpur401.ldam(5) is mapped to thisposition.

Processing incoming







2-111

Description: This field contains the qualifier for the usedDiscount Method for the Order Line Discount.discount method. This means it is a code thatindicates the way in which discounts arecalculated if multiple discount levels are used.Discounts are calculated according to one of thefollowing amounts:

Gross: the discount is calculated over the grossamount.

Net: the discount is calculated over the netamount. The net amount is the gross amountminus the net amount over the previous levels.

Used Qualifiers are:

“1” means gross

“2” means net

Processing outgoing

EDI Sub-System:

BAAN: The Qualifier of the first discount method fromBAAN table field TFtdpur401.dmth(1) ismapped to this position.

Processing incoming


BAAN: Mapping to the BAAN table field TFtdsls401.dmth(1)


Field name Discount Method 1



2-112





“1” means gross

“2” means net

Processing outgoing

EDI Sub-System:

BAAN: The Qualifier of the second discount methodfrom BAAN table field TFtdpur401.dmth(2) ismapped to this position.

Processing incoming







2-113





“1” means gross

“2” means net

Processing outgoing

EDI Sub-System:


Processing incoming







2-114





“1” means gross

“2” means net

Processing outgoing

EDI Sub-System:


Processing incoming







2-115





“1” means gross

“2” means net

Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: Mapping to the BAAN table field TFtdsls401.dmth(5).





2-116

Description: A supplier of finished goods.

Processing outgoing

EDI Sub-System:

BAAN: The code for the manufacturer from BAANtable field TFtdpur401.cmnf is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.cmnf


Field name Manufacturer



2-117

Description: User-definable item grouping data fordistinguishing different groups of items within aproduct line. The product class is mainly used asa selection criterion for reporting.

Example

Product line Product class

TV Portable/Non-portable

VCR Stereo/Mono

Walkman Regular/Children’s models

Processing outgoing

EDI Sub-System:

BAAN: The code for the product class from BAAN tablefield TFtdpur401.cmnf is mapped to thisposition.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.cmnf


Field name Product Class



2-118

Description: This date is the confirmed delivery date /time ofthe purchase order.

Processing outgoing

EDI Sub-System:

BAAN: The date/time from BAAN table fieldTFtdpur401.ddtb is mapped to this position.

Processing incoming

EDI Sub-System: None

BAAN: None

Description: This field contains the Code for the forwardingagent used for this position. This code has to beagreed upon with th partner.

Processing outgoing

EDI Sub-System:

BAAN: The code of the forwarding agent from BAANtable field TFtdpur401.cfrw is mapped to thisposition. Conversion via BAAN tableTBecedi456.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.cfrw after conversion via BAANtable TBecedi318.


Field name Confirmed Delivery Date / Time


Field name Forwarding Agent



2-119

Description: This field contains the Code for the Ship FromBusiness Partner. Outgoing this code meansfrom which business partner the goods has to bedelivered. Incomming this code has to beconverted to the warehouse, from which thegoods should be shipped.

Processing outgoing

EDI Sub-System:

BAAN: The code of the ship from business partner fromBAAN table field TFtdpur401.sfbp is mapped tothis position after conversion with BAAN tableTBecedi468.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.cwar after conversion with BAANtable TBecedi355.

Description: This field contains the Qualifier for the PartnerCode stated on position 51. The code is “SFBP”

Processing outgoing

EDI Sub-System:

BAAN: The qualifier from BAAN table fieldTFecedi224.code is mapped to this position.

Processing incoming

EDI Sub-System: Transmission of the value from the message fileor fixed value “SFBP”

BAAN: Used for conversion of position 51.


Field name Ship from Bussiness Partner


Field name Qualifier Address/Partner



2-120

Description: This field contains the Code of the warehousethe goods has to be shiped to.

Processing outgoing

EDI Sub-System:

BAAN: The code of the warehouse from BAAN tablefield TFtdpur401.cwar is mapped to thisposition. Conversion via BAAN tableTBecedi462.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtdsls401.stbp after conversion via BAANtable TBecedi328.

Description: This field contains the Qualifier regarding to thewarehouse code conversion. The Qualifier is“STBP”.

Processing outgoing

EDI Sub-System:

BAAN: The qualifier from BAAN table fieldTFecedi224.code is mapped to this position.Qualifier for position 53.

Processing incoming

EDI Sub-System: Transmission of the value from the message fileor fixed value “STBP”.

BAAN: Used for conversion of Position 53.


Field name Warehouse Code


Field name Qualifier Warehouse Code



2-121

Description: This field contains the Orderd Amount of thisorder line.

Processing outgoing

EDI Sub-System:

BAAN: The Factor from BAAN table fieldTFtdpur401.oamt is mapped to this position.

Processing incoming


BAAN: None.

Description: This field contains the Qualifier “ZZ” used forConversion of addresses..

Processing outgoing

EDI Sub-System:

BAAN: The constant value “ZZ” is mapped to thisposition.

Processing incoming

EDI Sub-System: The fixed value ‘ZZ’ is entered on this position.

BAAN: Used for conversion.


Field name Orderd Amount


Field name Qualifier



2-122

Description: This field contains the Qualifier for the Sold toBusiness Partner Conversion. The Qualifier isstated as ‘STBP’.

Processing outgoing

EDI Sub-System:

BAAN:

Processing incoming

EDI Sub-System: The fixed value ‘STBP’ is mapped to thisposition.

BAAN: Used for conversion.


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: None


Field name Qualifier Sold to Business Partner





2-123

SA6 Ship from Business Partner Address perOrder Line

Status : Conditional

Frequency : Once per Order Position

Description: This data record is related to one Order Position.

First Appearance: Warehouse Address ( AddressQualifier: CWAR )


Table Fields


Fields

Pos FIELD

DESCRIPTION


1. Kind of data

record

O/I M an3 SA6 SA6



the sender



an..30

tdpur400.orno

tdsls400.corn

5. Order Position

Number

M n..5

an..16

tdpur401.pono tdsls401.copn


Warehouse

Address

M an4 “CWAR”

7. Warehouse

Address Country

C an..6 tccom130.ccty

ORD9 tccom130.ccty

Code and

Conversion



2-124


Table Fields


Fields

Pos FIELD

DESCRIPTION


8. Warehouse

Address first part

of the name


ORD9

tccom130.nam

a

9. Warehouse

Address second

part of the name


ORD9 tccom130.nam

b

10. Warehouse

Address third part

of the name


ORD9 tccom130.nam

c

11. Warehouse

Address 2


ORD9 tccom130.nam

d

12. Warehouse

Address City


ORD9 tccom130.nam

e

13. ILN Code,

Warehouse

Address


ORD9 tccom130.nam

f

14. Warehouse

Address Zip Code


ORD9 tccom130.pstc

15. Warehouse

Address Tax Id


16. TAX Code Id

Qualifier

M an3 “VAT” ORD9 “VAT”

17. Warehouse

Address State /

Province

C an2 tccom130.cste ORD9 tccom130.cste



2-125


Table Fields


Fields

Pos FIELD

DESCRIPTION


18. Warehouse

Address

Telephone

Number


19. Warehouse

Address Telex

Number


20. Warehouse

Address Fax

Number

C an..15 tccom130.tefx ORD9 tccom130.tefx

21. Warehouse

Address GEO

Code


22. Warehouse

Address House

Number

C an..10 tccom130.hono ORD9 tccom130.hon

o

23. Warehouse

Address P. O. Box

Number

C an..10 tccom130.pobn ORD9 tccom130.pob

n

24. Data record end

sign


Evaluation Expression: ORD9 (strip(tdpur401.sfad) <> "" andtdpur401.sfad <>tccom121.cadr)



2-126

Detailed description: Warehouse Address per order lineKind of data record: SA6 Warehouse Address per order line


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN:







2-127


Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing



Processing incoming

EDI Sub-System:








2-128

Description: This field contains the order position number.

Processing outgoing



Processing incoming

EDI Sub-System:



CWAR The following data is the Ship to (warehouse) address


Processing outgoing

EDI Sub-System:

BAAN: The value “CWAR” or is filled in from BAANtable field ecedi224.code.

Processing incoming

EDI Sub-System: The value “CWAR” is filled in this position.

BAAN: Mapping to BAAN table field TFtdsls042.ckorand Conversion with TBecedi224..


Field name Order Position Number (Key field in/out)


Field name Address Qualifier Warehouse Address



2-129



Processing outgoing

EDI Sub-System:

BAAN: The country code of the warehouse address fromBAAN table field TFtdpur042.ccty ortccom130.ccty is mapped to this position andconverts with BAAN table TBecedi440.

Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.ccty and conversion with BAANtable TBecedi302.


Field name Warehouse Address Country



2-130


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: Mapping to the BAAN table fieldTFtccom130.nama


Processing outgoing

EDI Sub-System:


Processing incoming




Field name WarehouseAddress First part of Name


Field name Warehouse Address Second part of Name



2-131

Description: This field contains the first part of theWarehouse Address.

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the second part of thewarehouse address.

Processing outgoing

EDI Sub-System:

BAAN: The second part of the warehouse Address fromBAAN table field TFtccom130.namd is mappedto this position.

Processing incoming




Field name Warehouse Address 3rd part of the name


Field name Warehouse Address 2



2-132


Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address City


Field name ILN Warehouse Code / further information province orcountry



2-133

Description: This field contains the postal or zip Codereferring to the Warehouse Address.

Processing outgoing

EDI Sub-System:


Processing incoming




Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address Zip Code


Field name Warehouse Address Tax ID



2-134


Processing outgoing

EDI Sub-System:


Processing incoming

EDI Sub-System:

BAAN: None

Description: This field contains the Warehouse Address State/ Province.

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Tax Code ID Qualifier


Field name Warehouse Address State/Province



2-135

Description: This field contains the Warehouse AddressTelephone Number.

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the Warehouse AddressTelex Number.

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address Telephon Number


Field name Warehouse Address Telex Number



2-136

Description: This field contains the Warehouse AddressFaxnumber.

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the Warehouse AddressGEO-Code.

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address Fax Number


Field name Warehouse Address GEO Code



2-137

Description: This field contains the Warehouse Addresshousenumber of the address.

Processing outgoing

EDI Sub-System:


Processing incoming



Description: This field contains the Warehouse Address P.O.Box Number.

Processing outgoing

EDI Sub-System:


Processing incoming




Field name Warehouse Address Housenumber


Field name Warehouse Address P.O.Box Number



2-138


Processing outgoing

EDI Sub-System:


Processing incoming


BAAN: None

