BaanERP

BaanERP
EDI User Guide
A publication of:
Baan Development B.V.
P.O.Box 143
3770 AC Barneveld
The Netherlands
Printed in the Netherlands
Baan Development B.V. 1998.
All rights reserved.
The information in this document
is subject to change without
notice. No part of this document
may be reproduced, stored or
transmitted in any form or by any
means, electronic or mechanical,
for any purpose, without the
express written permission of
assumes no liability for any
damages incurred, directly or
indirectly, from any errors,
omissions or discrepancies
between the software and the
information contained in this
document.
Document Information
Code:
Group:
Edition:
Date:
U7100B US
User Documentation
B
June 1998
Table of contents
1 Introduction
Overview
1-1
1-2
2 General setup for EDI

Parameters
EDI default data
Networks
Business partner data by network
Code and conversion tables
2-1
2-3
2-6
2-8
2-14
2-17
3 Setting up your company

Purchasing company
Code conversions
EDI messages supported by business partner
Additional parameters
Sales company
Code conversions
3-1
3-1
3-1
3-5
3-16
3-17
3-17
3-22
3-35
4 Running EDI
Processing files
EDI interchange controller
Controller setup
Using the interchange controller
External EDI network communication
4-1
4-1
4-2
4-2
4-6
4-8
5 Incoming message data

Processing interactive messages
Reprocessing messages with errors
5-1
5-1
5-1
6 EDI procedure
General procedures: purchasing company
General procedures: selling company
General message processing requirements
The purchasing company
Enter and print purchase order
Sending the purchase order (850/ORDERS)
Receiving the order acknowledgment (855/ORDRSP)
6-1
6-1
6-4
6-6
6-8
6-8
6-10
6-10
EDI User Guide
i
Table of contents
Changing the purchase order (860/ORDCHG)

6-11
Sending the purchase order change (860/ORDCHG)
6-13
Receiving the purchase order change acknowledgment (865)
6-13
Generating and Sending the Purchase Schedule Release (830/DELFOR,
862/DELFOR, 866/DELJIT)
6-14
Receiving the Shipment Notice (856/DESADV)
6-16
Sending the error notification
6-17
Sending the Receipt Discrepancy Notification (861/RECADV)
6-18
Receiving the sales invoice (810/INVOIC)
6-19
The selling company
6-21
Receiving the customer order (850/ORDERS)
6-21
Printing and sending the order acknowledgment (855/ORDRSP)
6-22
Receiving the sales order change (860/ORDCHG)
6-24
Printing and sending the order change acknowledgment (865)
6-25
Receiving the Customer Schedule Release (830/DELFOR, 862/DELFOR,
866/DELJIT)
6-28
Sending the Shipment Notice (856/DESADV)
6-30
Receiving the Error Notification (824/APERAK)
6-32
Receiving the Receipt Discrepancy Notification (861/RECADV)
6-34
Sending the sales invoice (810/INVOIC)
6-35
Receiving the Remittance Advice (820/REMADV)
6-35
The sales or purchasing company
6-36
Receiving Functional Acknowledgments (997) / Outgoing Message Status
Updates (STATUS)
6-36
7 Internal (multisite) EDI
Introduction
General setup
Company data
Business Partner data
Parameters
Default EDI data
Networks
Purchasing company setup
Sales company setup
Setup summary
Running EDI
Multisite network communication
EDI procedure (standard plus GLO)
EDI User Guide

ii
7-1
7-1
7-3
7-3
7-4
7-7
7-7
7-7
7-9
7-9
7-10
7-12
7-14
7-14
7-14
7-16
Table of contents
8 Appendix A: Conversion setups

Overview
General notes
Conversion setup: 810S, Invoices (Single file)
Record Relationships
Field Definition - In direction
Field Definition - Out direction
Conversion setup: 820S, Remittance Advice
Conversion setup: 824S, Error Notification
Field Definition In direction
Conversion setup: 830S, Planning Release
Record relationships
Conversion setup: 830S, X12 Planning Release
Conversion setup: 850S, Sales Order
Field Definition Out direction
Conversion setup: 855S, Purchase Order Acknowledgment
Conversion setup: 856, Shipment Notice
Conversion setup: 860S, Purchase Order Change
Conversion setup: 861S, Receipt Discrepancy Notification
Conversion setup: 861S, Receipt Discrepancy Notification
8-1
8-1
8-7
8-9
8-9
8-9
8-14
8-30
8-30
8-30
8-33
8-34
8-34
8-34
8-38
8-38
8-42
8-42
8-42
8-53
8-53
8-65
8-65
8-66
8-77
8-95
8-95
8-95
8-105
8-122
8-122
8-122
8-133
8-146
8-146
8-147
8-159
8-177
8-177
8-177
8-183
8-183
EDI User Guide

iii
Table of contents
Conversion setup: 862S, Shipping Release

Conversion setup: 865S, Purchase Order Change Acknowledgment
Conversion setup: 866S Sequenced Shipping Release
Conversion setup: 977 Message Status
EDI expressions
9 Appendix B: Glossary
EDI User Guide

iv
8-197
8-197
8-197
8-207
8-207
8-220
8-220
8-220
8-229
8-247
8-247
8-247
8-255
8-269
8-269
8-269
8-272
9-1
About this document
This document explains the issues involved with the implementation of

Electronic Data Interchange (EDI). This document is designed for members of an
EDI implementation team and end-users.
This guide covers the following topics:
n
n
n
n
n
n
Preliminary setup steps

Setting up a purchasing company
Setting up a selling company
Running EDI
Review of the standard EDI procedure
Using internal (multisite) EDI
Also included are detailed lists of the EDI conversion setups and a glossary.
EDI User Guide

v
Introduction
EDI User Guide

vi
Introduction
In todays business environment, companies face increasing order volumes and

higher demands on the speed of communication. The electronic transfer of data
(referred to as EDI, for Electronic Data Interchange) has become an important
part of day-to-day business. EDI can process standard messages between two
trading partners, usually through an external translator. The translator is typically
another company that provides translation services and, possibly, other network
services.
Company A
BAAN
environment
Company B
Trading relationship
ASCII
files
ASCII
files
BAAN
environment
EDI translator
provider
Figure 1 Electronic data interchange (EDI)
The Baan EDI module can generate and read ASCII files with a flexible format.
When you use Baan EDI to exchange documents, these ASCII files are
translated, or reformatted, using standard EDI message formats, such as ANSI
X12, UN/EDIFACT, ODETTE, and VDA by a third-party translator, to provide
a format supported by your trading relation.
EDI User Guide

1-1
Introduction
The data files are typically transferred between external trading partners over
commercial (a value added network) or noncommercial (for example, Internet)
networks. Third-party translation and communication software handles the
translation of the ASCII files that are created or received by Baan EDI. This
third-party software may additionally provide encryption for transferring data
over unsecured networks. Baan EDI software does not provide this translation
and communication functionality. This environment is referred to as external
EDI throughout this document.
The transfer of internal EDI messages is similar to the external EDI situation
except for the translation and communication requirements. Internal EDI is also
referred to as multicompany or multisite. In multisite EDI implementations, the
ASCII files are usually transferred over an internal company network (LAN or
WAN) which means that encryption is not required. Also, because all companies
(or sites) in the multisite structure use the same format for the ASCII files,
translation to a different external EDI standard generally is not required.
Overview
This guide will help you understand the steps involved in implementing and
using the Baan EDI solution. This application provides several tools to help you
with this, including:
n
n
n
n
n
n
EDI User Guide

1-2
Default conversion setups for the supported transaction sets

Mechanisms for identifying the business partners and supported messages
Conversion tables to help with specific conversion information
Code tables for code identification purposes
Message generation management
Message audit and correction management
Introduction
Baan provides default data that you can import into Baan EDI. The default data
includes the following:
n
The X12 and EDI organizations which represent the ANSI X12 and
UN/EDIFACT Standards, by which you can group other EDI elements
Supported messages that follow the ANSI X12 and UN/EDIFACT Standards
naming conventions, grouped by organization (EDI messages and the
supported messages defined in EDI Master Data)
Supported Conversion setups for each supported message that define the
ASCII file layouts and supported fields for each message
Default values from select EDI codes (for example, order types, item code
IDs, address/partner code IDs, address/partner types and shipment status
codes) that you can use in code conversions
Outgoing messages by session, which link all supported outgoing messages

to the session that prepares the EDI message for generation
EDI User Guide

1-3
Introduction
Supported messages
The BaanERP release supports the following messages. The table includes the
transaction set, or message, codes to which these messages correspond for the
indicated EDI standards.
EDI standard/message
description
X12
EDIFACT
Direction
Invoice
810
INVOIC
in/out
Remittance Advice
820
REMADV
in only
Error Notification
824
APERAK
in/out
Purchase Schedules
830
DELFOR
in/out
Purchase Order
850
ORDERS
in/out
Purchase Order
Acknowledgment
855
ORDRSP
in/out
Advance Ship Notice
856
DESADV
in/out
Purchase Schedules
862
DELFOR
in/out
Purchase Schedules
866
DELJIT
in/out
Receipt Discrepancy
Notification
861
RECADV
in/out
Purchase Order Change
860
ORDCHG
in/out

Acknowledgement
865
ORDRSP
in/out
Functional
Acknowledgment
997
in only
Each message has a code that relates to a particular standard. For example,
ORDERS is the code used for the UN/EDIFACT purchase order and 850 is the
code used for the ANSI X12 purchase order. Each standard has its own
identification method for defining the name of the message.
The Baan EDI default data maintains this naming convention. You can easily
identify the Baan message with the EDI standard name for X12 and EDIFACT.
You can also customize the message names.
The message data provided in the Baan EDI default data conversion setups
include the ASCII file layouts that you can map to your EDI standard. To
maintain simplicity, the examples will use ANSI X12 terminology throughout
this document when referring to the messages.
The next few chapters cover the actual setup of EDI data, and the usage of EDI
from a procedural point of view.
EDI User Guide

1-4
Introduction
The setup of data is structured as follows:
General data setup of EDI company
Setup of purchasing company: setup specific to defining your trading partner

as the seller, you as the buyer
Setup of selling company: setup specific to defining your trading partner as

the buyer, you as the seller
The appendix reviews the currently supported EDI conversion setups provided in
the default data.
EDI User Guide

1-5
Introduction
EDI User Guide

1-6
General setup for EDI
EDI-specific data setup includes the following steps (in order of execution):
1
2
3
4
5
6
7
8
Maintain EDI parameters

Export default EDI data
Import EDI data
Maintain networks
Maintain business partner data by network
Maintain code tables
Maintain conversion tables
Maintain EDI messages by business partner
EDI User Guide

2-1
Figure 2 shows the relationships between the setup steps and the databases
involved.
Demo Company
Database
defaults.edi
Export
Default EDI
Data
EDI
Parameters
Import EDI
Data
Networks
Your Company
Database
EDI
Messages
by
Business
Partner
Business
Partner
Data
by Network
Code Tables
Figure 2 EDI setup
EDI User Guide

2-2
Conversion
Tables
Parameters
The next two forms show how to set your EDI parameters.
Figure 3 EDI Parameters (ecedi0100s000) session, defaults
EDI User Guide

2-3
Explanation of parameters
Parameter
Explanation
EDI Implemented
A check box that indicates if EDI is implemented in this

company.
Standard Path
Select the directory in which all EDI-related data is

located. The actual messages for your company are
stored in a series of subdirectories, which will be
defined at a later stage. The directory defined here is
the directory in which the import utility will search for the
Defaults.edi file as explained in the pervious section
and to which the export utility will write files.
Our Identification
The communication address that is used by your

trading business partner to identify you. For internal
EDI, using the company number, as an address is a
good choice. For external EDI, the
translation/communication software uses the
communication address to identify you as the sender of
the message
Reference Number
The reference number that is used for outgoing

messages and is created when an EDI message is
generated. This number uniquely identifies the
message. Because the actual data belonging to the
message is distributed over multiple ASCII levels, this
number is also used to identify which parts of the
message belong together. The number is built up of
three concatenated parts:
1
A string of characters defined in the Fixed Part field
The system date in one of several formats (Date

Format field)
An incrementing number
Fixed Part
The fixed part of the reference number.
Date Format
The date format of the reference number.
First Free Number
The next available sequence number.
Action on New Date
Because the date is included in the reference number,

the number will be unique on a new date, even if the
incrementing number is repeated with 0 or 1 each new
day. Alternatively, you can keep incrementing the
number. In that case, that number tells you how many
messages have been generated so far.
Store All Received and Check boxes that indicate if a copy of every received or
Sent Messages
sent message is kept. See the Networks section in
Chapter 2 for directory structure information.
EDI User Guide

2-4
Explanation of parameters
Parameter
Explanation
Suppress Blank Text

Lines
If this check box is selected, empty text lines in text

blocks are suppressed in outgoing messages, limiting
the text content to significant information.
Suppress Blank Text

Fields
If this check box is selected, blank text lines received in

incoming messages are suppressed when creating text
on internal documents limiting the message content to
significant information.
Make Use of Tracefile
A check box that indicates if a Trace file is used. See

the Networks section in Chapter 2 for directory structure
information.
Name of Tracefile
The name of the trace file.
Figure 4 EDI Parameters (ecedi0100s000) session, Series/Other
EDI User Guide

2-5
Explanation of fields
Field
Explanation
Number Series for

Address Codes
The order series that is used for address codes that

are automatically generated by EDI when specific
address information is received on incoming EDI
messages.
Sales Schedule Series
The user-defined series that will be used when

generating incoming sales schedules for incoming
EDI schedule-related messages.
Interchange Message
The name of the dummy message used in various

organizations to describe the layout of the
interchange header and the joint message overhead.
Interchange Conversion
Setup
The name of the conversion setup in which the

interchange header layout is described.
Message Overhead
Conversion Setup
The name of the conversion setup that contains the

layout of the joint message overhead. The default
conversion setups assume that this is blank.
Once you begin transmitting messages, do not change the standard path
identification or the way you create the reference number.
EDI default data

Although much of the setup data in the EDI module is user-definable, Baan
provides all the necessary EDI data as default data in demo company 812. To
avoid entering or changing this data in each of your companies, you can export
the setup data to an ASCII file and import them into other companies.
You can export the setup data from this company using the Export EDI Data
(ecedi6221m000) session. This session creates a file called Defaults.edi in the
EDI directory that is specified in the Standard Path field in the EDI parameters of
company 812. Before you run the Export EDI Data (ecedi6221m000) session,
you must create an EDI directory in $BSE and make sure that the full path of this
directory is specified in the Standard Path field of the EDI parameters of
company 812.
In principle, you only need to export the EDI data once. However, you can make
changes to the default data (organizations, networks, code or conversion tables,
or conversion setups) in any company and use the export/import sessions to
transfer that data to other companies. Once exported, the Defaults.edi file
contains the default EDI setup data for import into your normal Baan company
database, as explained in the following sections.
EDI User Guide

2-6
You should export the data for organization X12 if you want the correct default
data for external and internal EDI.
Figure 5 Export EDI Data (ecedi6221m000) session
You can import the exported default data into the EDI modules of the individual
companies.
NOTE
Contact a Baan Support Center to find out if your default data is up to date.
Once you have exported the Defaults.edi file from the Demo Company 812 you
can import the data back into other companies.
You must assign a default text group to the user who executes the import before
running the Import EDI Data (ecedi6220m000) session because the import will
read a number of evaluation expressions, which are stored as text blocks. You
can complete this task in the User Data (ttams1100s000) session.
EDI User Guide

2-7
To import the Defaults.edi file into your new company, run the Import EDI Data
(ecedi6220m000) session shown in Figure 6.
Figure 6 Import EDI Data (ecedi6220m000) session
Networks
Networks are used to specify the directory that Baan EDI uses to store and
retrieve messages (ASCII files). Because data for multisite business partners
does not need to be translated into actual EDI messages, internal EDI data must
be separated from external EDI data.
In most cases, you will need two networks.
EDI User Guide

2-8
One network represents the directory for internal (multisite) EDI.
The other network represents the directory where you will exchange files
with the translation/communication software that handles the transmission of
messages to external trading partners.
Figure 7 shows how to define a network for external trade business partners.
Figure 7 Networks (ecedi0520m000) session
Figure 8 Networks (ecedi0120s000) session, References
EDI User Guide

2-9
Field
Explanation
Network
Your name for the network.
Description
Free form description of the network that is being

defined.
Path
The directory where all EDI data related to this network

will be stored. This is usually is a subdirectory of the EDI
directory defined in the EDI parameters.
If you have more than one Baan company that will be
used for external EDI, you should create unique
directories for each company. An easy way to
accommodate this is to create a subdirectory under your
EDI path for each company and assign that directory to
each companys network.
For example, if companies 420 and 422 are both used
for external trade, company 422 can have the path:
/Home/Edi/422 assigned to its network; company 420
can have the path: /Home/Edi/420.
Our Identification
Your network address for this particular network. This

may be the unique code you use to represent yourself to
your EDI trading partners (internal and external).
General Reference
If this check box is selected, unique message numbers

are created for messages sent through this network
based on EDI parameter settings.
If this check box is not selected, you can create different
settings for each network.
EDI User Guide

2-10
Fixed Part
Identifies the fixed part of the reference number created

in this network if the General Reference field is No.
Date Format
Identifies the date format of the reference number

created in this network if the General Reference field is
No.
First Free Number
The next available sequence number if the General

Reference field is No.
Action on New Date
If the General Reference field is No:

-
Start with 0: the first outgoing message has

sequence number 0.
Start with 1: first outgoing message has sequence

number 1.
Last Number +1: the first outgoing message has

number of the last message to have been sent plus
1 as the sequence number.
Field
Explanation
Multicompany
For external EDI, this field is No; for multisite (internal)

EDI, this field is Yes
Automatic Read in
This field pertains only to internal EDI. It is used to allow
Generated Messages automatic processing of data without requiring user
intervention to start the process.
Figure 9 shows how to define a file for your external business partners.
Figure 9 Networks (ecedi0120s000) session, File definition
EDI User Guide

2-11
NOTE
EDI User Guide

2-12
Field
Explanation
Record Separator
Each line (record) in the ASCII file ends with an LF

(Linefeed) and CR (Carriage Return) character, or only
the LF (use this when the CR is automatically added
by the system).
Field Type
If this field is Delimited, a special separator sign

separates the fields in the ASCII files. If this field is
Fixed Length, each field has a specific, absolute start
position and length.
Separator Sign
The character that is used to delimit fields in the ASCII

files if the Field Type field is Delimited.
Replacement Sign
If the separator sign is used in a field content, this

character will replace it (otherwise it would be
interpreted as a separator).
Sign Around Strings
This character will be used to enclose fields that

contain alphanumeric characters. This field is optional.
Replacement Sign
If the sign around strings is used in a string field, this

character will replace it (otherwise it would be
interpreted at the end of the string). This field is
optional.
When creating any of the special signs, do not use any common punctuation
characters. This could cause problems when a message is translated. For
example, never use a comma as a separator or the sign around a string because
this character is used in the Address field.
Field
Explanation
Allow Leading Zeros
When using the Fixed Length field type, the unused

positions for numbers can be filled with leading zeros
instead of spaces.
Suppress Standard
Communication
A check box that indicates whether you want to

suppress the standard communication procedure with
the external EDI network.
If the box is blank, the standard procedure of the
external EDI communication software is used (referred
to as semaphore logic). See the External EDI network
communicationsection in Chapter 4.
If the box is checked, the standard communication
procedure is not executed.
Generate Outgoing
Messages before
Connection
If the box is checked, the Direct Network

Communication (ecedi7205m000) session will first
generate all pending outgoing messages (equivalent
to running Generate EDI Messages (ecedi7201m000)
session) before reading incoming messages.
EDI User Guide

2-13
When you save the network definition the system creates the following
subdirectories for external EDI under the path specified for the network:
Subdirectory
Description
appl_from
This is where all EDI messages generated by Baan EDI are

stored. This is the directory from which your
translation/communication software will retrieve files for
exporting.
appl_to
This is where all EDI messages to be received into the Baan

application are stored. This is the directory to which the
translation/communication software will write files that must be
processed and imported by Baan EDI.
appl_text
If a message contains any text fields, this directory contains

temporary files that are used to build up the text blocks.
appl_trace
This directory contains the created log (trace) files.
command
This directory is used by the system for semaphores. The

semaphore, or flagging, mechanism is used to communicate
with third-party translation/communication software to ensure
that the third-party software and Baan EDI are not attempting to
access files at the same time. This semaphore mechanism
uses the creation and deletion of empty files in this command
subdirectory to indicate when certain processes are active, or
can be activated. See External EDI network communication in
Chapter 4, for a more detailed explanation of semaphores.
store_send
This is where sent messages are archived based on EDI

parameter settings.
store_recv
This is where received messages are archived based on EDI

parameter settings.

Because you will communicate with your trading business partner over a
specified network(s), you must define the network address of the trading business
partner for the specified network(s). This address is the technical address that is
used in the envelope information (message overhead) of any EDI message sent to
or received from that business partner.
For messages exported from the Baan application for external EDI, the
translation/communication software can use this network address to determine
where to route the message. For messages imported into the Baan application, the
network address identifies the sender of the received message. For example, in
the default data provided for the conversion setups (the default message file
layouts/mappings), the network address, in conjunction with the network code,
determines the business partner on incoming messages.
EDI User Guide
2-14
In any case, this network address identifies a business partner by network. You
may choose to have the network address match the business partner code or you
can use this field to specify the actual technical address of your business partner.
Your choice depends on the functionality of your translation/communication
software.
Figure 10 Business Partner EDI Data by Network (ecedi0528m000) session
Figure 11 Business Partner EDI Data by Network (ecedi0128s000) session
EDI User Guide

2-15
Field
Explanation
Business Partner
The name of a valid business partner.
Network
The network used when communicating with this

business partner. Because it is possible to communicate
with a business partner through more than one network,
you can define network address information for multiple
networks per business partner.
Network Address
The network address used in the message envelope. In

EDI it identifies a business partner/network
correspondence.
For incoming messages, the network address derives
the business partner who sent the message.
For outgoing messages in external EDI, you can include
the network address in the exported ASCII file to
uniquely identify the business partner and network to the
translation/communication software. This allows the
translation/communication software to determine where
to route a message exported from Baan EDI.
New Batch Number
Messages can either be grouped By Message (a unique

message reference for each message) or By Recipient
(a unique message reference for a grouping of
messages).
The default conversion setups provided by Baan EDI
require that you set this field to By Message so that a
unique message reference is assigned for each
message/relation combination.
Incrementing
Reference Numbers
This check box applies to incoming messages.

If this check box is selected, the application checks if the
received message has a higher reference number than
previously received messages (and is therefore newer).
If not, a warning is displayed and the message is
rejected.
If this check box is left blank, a received message is
rejected if the reference number has already been
received; however, if the reference number of the new
message is lower than the previously received numbers,
and that lower number has not received before, the
message is rejected.
EDI User Guide

2-16

Code tables contain the definitions of the different codes that may be present in
generated or received EDI messages. Some of the code tables (for example, those
found under the Codes and Conversions menu) are used with conversion tables to
provide a cross-reference between values internal to the Baan application (Code
in Application) and external values defined by your trading partner or by an EDI
standard (Code in Message). The Text Codes menu contains other code tables.
You can use these to enter descriptions corresponding to selected codes that you
can use in a message instead of the code itself for outgoing messages, or in text
fields for incoming messages.
NOTE
One mandatory code is the order type code. For incoming messages, the defined
order type codes represent valid order type codes that Baan EDI can receive and
process by Baan EDI. For all incoming messages, the application validates the
order type value passed in the message overhead against the data defined in this
session (note that a blank value is valid as long as it is defined here). This serves
as another mechanism for controlling which type of documents you wish to
receive. For outgoing messages, the codes defined are used to maintain the
conversion of order types (out) for messages pertaining to a single order (order,
order change, acknowledgment, and invoice messages). Figure 13 in Chapter 3,
Setting up your company, provides an example.
Figure 12 Order Types (ecedi2100m000) session
EDI User Guide

2-17
Field
Explanation
Organization
The organization in which the order type is valid.
EDI Message
Supported EDI Messages.
Description
The description of the selected code.
Code in Message
A standard code used in a specific EDI message

that represents the external value of the order or
document type.
Description
The description of the selected code.
Some sample data is included in the Defaults.edi file that you imported. Chapters
3, Setting up your company, and 4, Running EDI, explain how these codes are
used by Baan EDI. These two chapters discuss the additional setup steps to
establish you as the buyer or the seller in the trading partner relationship.
EDI User Guide

2-18
Setting up your company
Each company that you create is a purchasing company, a sales company, or

both. A purchasing company procures materials or services from other
companies (both internal and external). A sales company sells goods or services
to other companies (internal or external).
Depending on how a particular company is used, you need to set up the
purchasing profile, the sales profile, or both.
Purchasing company
Your company is defined as a purchasing entity. This means that purchasing
activities are pursued within this company. The purchasing activities may be
classified as internal only (multisite), external only, or both.
This section describes the specific setup requirements for EDI documents
exchanged with the supplying business partners (buy-from, ship-from, invoicefrom, pay-to) from whom your company procures goods and services.
Code conversions
Conversion tables allow you to define the relationship between codes in an EDI
message and the codes used in the Baan application.
For example, unit of measure codes are usually unique to a company. However,
you may need to conform to a specific unit of measure convention based on your
trading relationship. If you must translate your internal pcs unit of measure code
to a standard unit each, you will use the conversion code table for units to handle
the automatic conversion of this data.
Remember that conversion tables only need to be filled when a particular code
must be converted from an internal value maintained within the Baan application
to one that is used externally. If both parties use the same codes for unit codes or
warehouses, for example, the conversion of the codes is not necessary.
EDI User Guide

3-1
NOTE
The conversion table for order types (out) must be filled for outgoing EDI
messages pertaining to a single order . This includes order and order change
messages for purchasing companies, and order acknowledgment and invoice
messages for selling companies. The outgoing conversion of order types not only
specifies the correct conversion of codes, but also determines which order types
can be sent through EDI. For example, purchase orders of the type PN3 can only
be sent through EDI when the code PN3 is present in the conversion table
(although it may be converted to a blank code).
When you create the conversion table for order types (out), be sure to list all
valid order types you wish to send through EDI, along with the corresponding
code in the message as specified in the code tables.
Figure 13 Order Purchase Types (Out) (ecedi4133m000) session
EDI User Guide

3-2
Field
Explanation
EDI Message
A valid EDI message code in the selected organization.
Code in
Application
Order type on the Baan order.
Code in Message This field represents the external value. The code in
application will be converted to the code in message value,
which resides in the exported message when the purchase
order is exported through Baan EDI. You must define the
code in message first as an order type in the code tables.
You can use the code in message to represent the order
types used by the EDI standard you are using (for example,
the ANSI X12 purchase order type code).
Note: This corresponds to the Order Type value specified in
EDI Messages Supported by Business Partner
(ecedi4132m000) session.
NOTE
There is no conversion table for incoming order types. The cross-reference

(conversion) of the external order type received to a valid internal order type is
handled in the EDI Messages Supported by Business Partner (ecedi4132m000)
session.
EDI User Guide

3-3
In addition to defining the outgoing conversion of order types for the

850/ORDERS message, you also must define the outgoing information for the
860/ORDCHG, purchase order change, message as shown in Figure 14. Enter the
valid order types for which you will allow purchase order changes to be
processed.
Figure 14 Conversion of Purchase Order Types (Out) (ecedi4133m000) session
Additional code conversions that you may want to consider as the purchasing
company include the following:
EDI User Guide

3-4
Conversion of Schedule Type (Out) (ecedi4113m000): Used in the outgoing

schedule release message (for example, 830/DELFOR) to indicate if the
schedule is delivery-based or shipment-based.
Conversion of Schedule Quantity Type (Out) (ecedi4115m000): Used to

indicate if the schedule release quantities are actual or cumulative values.
Conversion of Shipment Status Codes (in) (ecedi3146m000): Used in the

incoming Shipment Notice (856/DESADV) message to indicate the type of
Shipment Notice received. The shipment status code included in the
Shipment Status message is checked against the codes defined in this session
when a Shipment Notice message is received. A code conversion for the
original value is required to receive a Shipment Notice message.
Application Errors (ecedi2191m000): Code used in the Error Notification

message (824/APERAK) to indicate the type of error that occurred when
processing an incoming Shipment Notice message (856/DESADV).
Conversion of Receipt Discrepancy Codes (out) (ecedi4147m000): Used in

the outgoing Receipt Discrepancy to indicate the type of discrepancy found in
the quantity of goods received and the quantity of goods indicated on the
received Shipment Notice.
See the procedures for specific messages in The purchasing company section, in
Chapter 6, for more information on the above additional conversions.
Under the Code and Conversions menu, code conversions are organized by
organization, allowing you to organize these code conversions by EDI standard.
Under the Conversions by Business Partner menu, code conversions are
organized by business partner, allowing you to define different sets of
conversions for each business partner. Here you may define the conversions
using the business partner with whom you will be exchanging the EDI messages,
or you may define the conversions by the parent of the business partner with
whom you will be exchanging EDI messages. When processing the EDI
message, Baan EDI will first check if the code conversion exists for the business
partner with whom the EDI message is traded; if that does not exist, Baan EDI
will then check to see if the conversion has been defined for the parent business
partner. This feature saves you having to define the code conversions multiple
times (for each business partner) if all associated business partners linked to the
same parent business partner use the same codes.

In this example, you are the customer and you want to send various purchasing
documents such as purchase orders, purchase changes and purchase schedule
releases (planning release, shipping release, sequenced shipping release) to your
supplier.
After completing the general setup steps, determine what individual EDI
messages you want to exchange with your supplier(s). Not every business partner
will necessarily support each implemented message type. Use the EDI Messages
Supported by Business Partner (ecedi0111s000) session to identify the valid
messages you can transmit to or receive from a specific business partner. You
can also define additional information that could vary by business partner.
For example, there can be slight differences in the structure (field mapping or
conversion setup) of a message between business partners; and you may want to
use different conversion setups (file layouts) for different order types.
EDI User Guide

3-5
Figure 15 EDI Messages Supported by Business Partner (ecedi0511m000)
Figure 16 EDI Messages Supported by Business Partner (ecedi0111s000)
EDI User Guide

3-6
Explanation of Fields
Field
Explanation
Business Partner
Enter the business partner code for defining this EDI

message. This is the business partner with whom you will
exchange the indicated EDI message.
The business partners must have the following roles based on
the type of document being exchanged:
Order /Out
: Buy-From Business Partner
Order Change /Out
Planning Release /Out
Shipping Release / Out
Sequenced Ship. Release/Out
Order Acknowledgment /In
Change Acknowledgment /In
Shipment Notice /In
: Ship-From Business Partner
Error Notification /Out
Receipt Discrepancy /Out
Invoice /In
: Invoice-From Business Partner
Organization
The organization identifier for the set of messages you are

using.
EDI Message
Direction
Choice of In or Out.
Order Type
Standard external order type (if specified, must be a valid

code defined in the Order Type Code table).
Note: For outgoing messages that pertain to single order, the
order type field here must be defined in the Conversion of
Order Types Out. Messages that pertain to single order
include orders, order changes, acknowledgments, and
invoices.
For outgoing messages that do not pertain to a single order,
the order type field must be blank, since there is no order type
conversion.
Network
This specifies the directory where the ASCII files containing

the message data are read or written. Messages can be
exchanged over different networks, based on the business
partner, configuration, direction, message type, and order type
combination.
EDI User Guide

3-7
Conversion Setup This indicates which conversion setup to use. The conversion
setup defines the layout of the ASCII file containing the
message data. It contains information on the mapping of data
elements between the Baan application tables and the ASCII
files. Although predefined conversion setups are available and
may be imported from the Defaults.edi file, you can create your
own custom conversion setups.
Person
Responsible
The person responsible for this business partner/message

type/order type combination. This is for information and
reporting purposes only.
Number Group
Displayed on reports for information, and used to validate the

series entered for incoming orders, schedule releases and
shipment notices.
Note: The number group entered here for incoming orders,
schedule releases and shipment notices must be consistent
with the number group specified for these documents in their
respective parameter sessions (Sales Order Parameters,
Sales Contract Parameters and Inventory Handling
Parameters, respectively).
Print
For outgoing messages, mark this check box to create a hard

copy of the document at the time the messages is prepared for
EDI.
For incoming messages, set this field to Yes to create a
remarks report that a message of this type has been received.
Processing Type
Identifies whether the incoming message is processed

automatically or interactively. If this field is:
Automatic the message is read and processed during direct
network communication.
Interactive the message is read and stored in Saved
Message to be Received without any validation during direct
network communication. Then, these messages can be
modified, approved, and processed. See Chapter 5 for
additional information.
Block
Upon receipt of a purchase order through EDI, the resulting

sales order can optionally be blocked for further processing
Check Duplicate
Order Number
Check this box if you want to check for duplicate order

numbers on incoming documents.
If this box is checked and a customer purchase order is
received which is already referenced on another Baan sales
order, the message will be rejected. For incoming change
orders, the combination of the customer order number and
change order sequence number is checked for uniqueness.
For incoming purchase schedule releases, the customer
release number combined with the revision number is checked
for uniqueness.
EDI User Guide

3-8
Automatically
Prepare Error
Notification
Check this box if you want an error notification automatically

prepared.
If this box is checked and an incoming message cannot be
processed due to errors, an outgoing error notification
message (for example, ANSI X12 824) is prepared for EDI
generation. This is particularly useful in supply chain
environments for incoming shipment notices processed with
errors.
Figure 17 EDI Messages Supported by Business Partners (ecedi0111s000), Series/Conversions
Field
Explanation
SLS Order Type
This field determines what sales order type is assigned to

the order when an incoming purchase order is received.
This field is only used for incoming orders.
Note: When selecting an order type, you should use an
order type in which the Print Acknowledgments session
(tdsls4401m000) as an activity, and ensure that this activity
may be re-executed at subsequent steps, if you wish to
exchange order acknowledgments through EDI for
received EDI orders.
EDI User Guide

3-9
Series
This field determines what first free number series is

assigned to documents generated from incoming
messages. The number series is used for the sales order
when an incoming purchase order is received, the sales
release (planning release, shipping release or sequenced
shipping release) when a purchase release is received,
and the Shipment Notice (ASN) when a shipment notice
(ASN) is received.
This field is only used for incoming messages.
When you define the series with the First Free Numbers
(tcmcs0150m000) session, you may wish to set the
Blocked for Input field to Yes to prevent this series from
being used for non-EDI documents.
Item Code System
This is the item code system used to convert item codes in

outgoing messages. The item code may be converted to its
alternative item, based on this item code system and the
data defined in the Items by Item Code System
(tcibd0504m000) session.
If no value is specified here for the Item Code System, the
default value of the Qualifier 1 field for the item code in the
conversion setups will be used to derive the item code
system used to convert the item. In this case, the default
value for the qualifier is checked against the Item Code
IDs (ecedi2132m000) to derive the item code system.
Character
Conversion
For outgoing messages you can define how to convert

certain characters (for example, all characters to upper
case). Multiple conversions of characters can be defined;
each stored with a different identifier (character conversion
code).
The information in this section focused on the message 850/ORDERS, Purchase

Order (direction out). Other supported messages used for a Purchasing company
that may be defined include:
n
n
n
n
n
n
n
n
n
n
EDI User Guide

3-10
Order Acknowledgment (855/ORDRSP), direction in

Purchase Order Change (860/ORDCHG), direction out
Order Change Acknowledgment (865/ORDRSP), direction in
Shipment Notice (856/DESADV), direction in
Error Notification (824/APERAK), direction out
Receipt Discrepancy Notification (861/RECADV), direction out
Planning Release (830/DELFOR), direction out
Shipping Release (862/DELFOR), direction out
Sequenced Shipping Release (866/DELJIT), direction out
Invoice (810/INVOIC), direction in
Figures 18 through 28 show examples of the EDI Messages Supported by

Business Partners (ecedi0111s000) session for each of these messages.
Figure 18 855/ORDRSP, X12 Order Acknowledgment, direction in
Figure 19 860/ORDCHG, X12 Purchase Order Changes, direction out
EDI User Guide

3-11
Figure 20 865, X12 Order Change Acknowledgment, direction in
Figure 21 830, X12 Planning Release, direction out
EDI User Guide

3-12
Figure 22 862, X12 Shipping Release, direction out
Figure 23 Sequenced Shipping Release, direction out
EDI User Guide

3-13
Figure 24 856 X12 Shipment Notice, direction in
Figure 25 856, Shipment Notice, direction in
EDI User Guide

3-14
Figure 26 824, X12 Error Notification, direction out
Figure 27 861, X12 Receipt Discrepancy Notification, direction out
EDI User Guide

3-15
Figure 28 810, X12 Purchase Invoice, direction in
Additional parameters that exist in products other than EDI are available to
determine how the EDI data within these products may be processed. These
include the following:
n
Prompt for Change Codes (within Purchase Control): This field is

maintained in the Purchase Order Parameters (tdpur0100s400) governs
whether or not change codes (change type code, change reason codes and
acknowledgement codes) may be maintained on a purchase order. It is
required that this be enabled if you wish to process the EDI Order Change
(860/ORDCHG) message.
Release EDI Message Directly: This field maintained in the Item/Supplier

Information session (tdipu0510m000) indicates whether outgoing schedule
releases should be automatically prepared for EDI when schedules are
generated, or whether they should be manually prepared using the Generate
Schedule Releases (tdpur3208m000) session.
See The purchasing company section in Chapter 6 for additional information
about these parameter settings.
EDI User Guide

3-16
Sales company
If your company is defined as a selling entity, selling activities are pursued
within this company. The selling activities may be classified as internal only
(multisite), external only, or both.
This section describes the specific setup requirements for EDI documents
exchanged with the business partners ( sold-to, ship-to, invoice-to, pay-by) that
represent customers in your company.
Code conversions
Code Conversions allow you to define the relationship between codes in an EDI
message and the codes used in the Baan application. For example, unit of
measure codes are usually unique to a company. However, you may need to
conform to a specific unit of measure convention based on your trading
relationship. If you must translate your internal pcs unit of measure code to a
standard unit each, use the conversion code table for units to handle the
automatic conversion for you.
You only need to fill conversion tables when you need to convert a particular
code from an internal value maintained within the Baan application to a code that
is used externally. If both parties use the same codes for unit codes and
warehouses, for example, you do not need to convert the codes.
The conversion of order types is required for all outgoing messages pertaining to
a single order; this includes orders, order changes, order acknowledgments and
invoices. In the previous section for the purchasing company, you ensured that
all purchase order types (for example, PN1 and PN2) were converted to a
corresponding code in the EDI message that enables these purchase order types
to be sent through EDI. As the selling company, you will define how to exchange
documents with a buyer and how to handle outgoing conversions of order types
for order acknowledgments, and invoices. These are the current outgoing
messages supported by Baan EDI for which conversion of order types (out) must
be defined with the Conversion of Sales Order Types (Out) (ecedi4132m000)
session.
EDI User Guide

3-17
Figure 29 Conversion of Sales Order Types (out) (ecedi4132m000) session

NOTE
The Conversion Table for Order Types (Out) must be filled for outgoing EDI
messages pertaining to a single order because it specifies the correct conversion
of codes and determines which Baan sales order types can be sent through EDI
for order acknowledgments and invoices.
When you create the conversion table for order types (out), be sure to list all
valid order types you wish to send through EDI along with the corresponding
code in the message as specified in the code tables.
EDI User Guide

3-18
Figure 30 Conversion of Sales Order Types for 865 (ecedi4132m000)
EDI User Guide

3-19
Figure 31 Conversion of Sales Order Types for 810/INVOIC (ecedi4132m000)

NOTE
There is no conversion table for incoming order types. The cross-reference

(conversion) of the external order type received to a valid internal order type is
handled in the EDI Messages Supported by Business Partner (ecedi0111s000)
session. When a customer purchase order is received as a sales order, the
specified sales order type code in the EDI Messages Supported by Business
Partner (ecedi0111m000) session determines the sales order type assigned to the
order. Theoretically, this could be any of the existing sales order types.
Additional code conversions that you may want to consider as the selling
company include the following:
EDI User Guide

3-20
Conversion of Schedule Type (in) (ecedi3151m000): Used in the incoming

schedule release message (for example, 830/DELFOR) to indicate if the
schedule is delivery-based or shipment-based.
Conversion of Schedule Quantity Type (in) (ecedi3152m000): Used in the

incoming schedule release message (for example, 830/DELFOR) to indicate
if the schedule release quantities included in the message are actual or
cumulative values.
Conversion of Shipment Status Codes (out) (ecedi4180m000): Used in the

outgoing Shipment Notice (856/DESADV) message to indicate the type of
Shipment Notice sent (original or cancelling). A code conversion for the
original value should be defined.
See the procedures for specific messages in
EDI User Guide

3-21
The selling company section, in Chapter 6, for more information on the above
additional conversions.
Under the Code and Conversions menu, code conversions are organized by
organization, allowing you to organize these code conversions by EDI standard.
Under the Conversions by Business Partner menu, code conversions are
organized by business partner, allowing you to define different sets of
conversions for each business partner. Here you may define the conversions
using the business partner with whom you will be exchanging the EDI messages,
or you may define the conversions by the parent of the business partner with
whom you will be exchanging EDI messages. When processing the EDI
message, Baan EDI will first check if the code conversion exists for the business
partner with whom the EDI message is traded; if that does not exist, Baan EDI
will then check to see if the conversion has been defined for the parent business
partner. This feature saves you having to define the conversions multiple times
(for each business partner) if all associated business partners linked to the same
parent business partner use the same codes.

After completing the general setup steps, your next step in the setup of your
company is to determine what individual EDI messages you will exchange with
your customer. Not every business partner will necessarily support each
implemented message type. Use the EDI Messages Supported by Business
Partners (ecedi0511m000) session to identify the valid messages you can
transmit to or receive from a specific business partner. You can also define
additional information that could vary by business partner. For example, there
can be slight differences in the structure (field mapping or conversion setup) of a
message between business partners; and you might want to use different
conversion setups (file layouts) for different order types.
EDI User Guide

3-22
Figure 32 EDI Messages Supported by Business Partners (ecedi0511m000)
Figure 33 EDI Messages Supported by Business Partners (ecedi0111s000), Message/Business

Partner
EDI User Guide

3-23
Field
Explanation
Business Partner
Enter the business partner code for defining this EDI

message. This is the business partner with whom you will
exchange the indicated EDI message.
The business partners must have the following roles based
on the type of document being exchanged:
Order /In
: Sold-To Business Partner
Order Change /In
Planning Release /In
Shipping Release / In
Sequenced Ship. Release/In
Order Acknowledgment /Out
Change Acknowledgment/Out
Shipment Notice /Out
: Ship-To Business Partner
Error Notification /In:
Receipt Discrepancy /In
Invoice /Out
: Invoice-To Business Partner
Remittance Advice /In
: Pay-By Business Partner
Organization
The organization identifier for the set of messages you are

using.
EDI Message
Direction
Choice of In or Out.
Order Type
Standard external order type (must be a valid code defined

in the Order Type Code table).
Note: For outgoing messages that pertain to single order,
the order type field here must be defined in the Conversion
of Order Types Out. Messages that pertain to single order
include orders, order changes, acknowledgments, and
invoices.
For outgoing messages that do not pertain to a single order,
the order type field must be blank, since there is no order
type conversion.
Network
EDI User Guide

3-24
This specifies the directory where the ASCII files containing

the message data are read or written. Messages can be
exchanged over different networks, based on the business
partner, organization, direction, message type, and order
type combination.
Field
Explanation
Conversion Setup
The conversion setup defines the layout of the ASCII file

containing the message data. It contains information on the
mapping of data elements between the Baan application
tables and the ASCII files. Although predefined conversion
setups are available and may be imported from the
Defaults.edi file, it is possible to create your own custom
conversion setups.
Person
Responsible
The person responsible for this business partner/message

type/order type combination. This is for information and
reporting purposes only.
Number Group
Displayed on reports for information, and used to validate

the series entered for incoming orders, schedule releases
and shipment notices.
Note: The number group entered here for incoming orders,
schedule releases and shipment notices must be consistent
with the number group specified for these documents in
their respective parameter sessions (Sales Order
Parameters, Sales Contract Parameters and Inventory
Handling Parameters, respectively).
Print
For outgoing messages, check this box to indicate that you

want to create a hard copy of the document at the time the
outgoing message is prepared for EDI.
For incoming messages, check this box to create a remarks
report that a message of this type has been received.
Incoming
Message
Processing Type
Identifies whether the incoming message is processed

automatically or interactively. If this field is:
Automatic - the message is read and processed during
direct network communication.
Interactive - the message is read and stored in Saved
Message to be Received without any validation during direct
network communication. Then, these messages can be
modified, approved, and processed. See Chapter 5.
Block
Upon receipt of a purchase order through EDI, the resulting

sales order can optionally be blocked for further processing.
EDI User Guide

3-25
Field
Explanation
Check Duplicate
Order Number
Check this box if you want to check for duplicate order

numbers on incoming documents.
If this box is checked and a customer purchase order is
received which is already referenced on another Baan sales
order, the message will be rejected. For incoming change
orders, the combination of the customer order number and
change order sequence number is checked for uniqueness.
For incoming purchase schedule releases, the customer
release number combined with the revision number is
checked for uniqueness.
Automatically
Prepare Error
Notification
Check this box if you want an error notification automatically

prepared.
If this box is checked and an incoming message cannot be
processed due to errors, an outgoing error notification
message (for example, ANSI X12 824) is prepared for EDI
generation. This is particularly useful in supply chain
environments for incoming shipment notices processed with
errors.
Figure 34 EDI Messages Supported by Business Partners (ecedi0111s000), Series/Conversions
EDI User Guide

3-26
Field
Explanation
SLS Order Type
This field determines what sales order type is

assigned to the order when an incoming purchase
order is received.
This field is only used for incoming orders.
Note: When selecting an order type, you should use
an order type in which the Print Acknowledgments
session (tdsls4401m000) as an activity, and ensure
that this activity may be re-executed at subsequent
steps, if you wish to exchange order
acknowledgments through EDI for received EDI
orders.
Series
This field determines what first free number series is

assigned to documents generated from incoming
messages. The number series is used for the sales
order when an incoming purchase order is received,
the sales release (planning release, shipping release
or sequenced shipping release) when a purchase
release is received, and the Shipment Notice (ASN)
when a shipment notice (ASN) is received.
This field is only used for incoming messages.
When you define the series with the First Free
Numbers (tcmcs0150m000) session, set the Blocked
for Input field to Yes to prevent this series from being
used for non-EDI sales orders.
Item Code System
This is the item code system used to convert item

codes in outgoing messages. The item code may be
converted to its alternative item, based on this item
code system and the data defined in the Items by Item
Code System (tcibd0504m000) session.
If no value is specified here for the Item Code System,
the default value of the Qualifier 1 field for the item
code in the conversion setups will be used to derive
the item code system used to convert the item. In this
case, the default value for the qualifier is checked
against the Item Code IDs (ecedi2132m000) to derive
the item code system.
Character Conversion
For outgoing messages you can define how to convert

certain characters (for example, all characters to
upper case). Multiple conversions of characters can
be defined; each stored with a different identifier
(character conversion code).
EDI User Guide

3-27
The information in this section focused on the message 850/ORDERS, Order

(direction in). Other conversion setups used for a selling company that may be
defined include:
n
n
n
n
n
n
n
n
n
n
n
n
Purchase Order Change (860/ORDCHG), direction in

Order Acknowledgment (855/ORDSP), direction out
Order Change (860/ORDCHG), direction in
Order Change Acknowledgment (865,ORDCHG). direction out
Shipment Notice (856/DESADV) direction out
Error Notification (824,APERAK) direction in
Receipt Discrepancy Notification (861/RECADV), direction in
Planning Release (830/DELFOR), direction in
Shipping Release (862/DELFOR), direction in
Sequenced Shipping Release (866/DELJIT), direction in
Invoice (810/INVOIC), direction out
Remittance Advice (820/REMADV), direction in
Figure 35 855/ORDRSP, X12 Order Acknowledgment (ecedi0111s000), direction out
EDI User Guide

3-28
Figure 36 860/ORDCHG, X12 Purchase Order Changes, direction in, Message/Business
Figure 37 860, X12 Purchase Order Changes, direction in
EDI User Guide

3-29
Figure 38 865, X12 Purchase Order Change Acknowledgment, direction out
Figure 39 830, X12 Panning Release, direction in
EDI User Guide

3-30
Figure 40 862, X12 Shipping Release, direction in
Figure 41 866, Sequenced Shipping Release, direction in
EDI User Guide

3-31
Figure 42 856/DESADV, X12 Shipping Notices, direction out
Figure 43 824, X12 Error Notification, direction in
EDI User Guide

3-32
Figure 44 861, X12 Receipt Discrepancy Notification, direction in
Figure 45 810/INVOIC, X12 Sales Invoice, direction out
EDI User Guide

3-33
Figure 46 820/REMADV, X12 Remittance Advice, direction in
EDI User Guide

3-34
Additional parameters that exist in products other than EDI are available to
determine how the EDI data within these products may be processed. These
include the following:
n
Automatically Prepare ASN: This field is maintained within the Inventory

Handling Parameters (whinh0100s000) and indicates whether the outgoing
Shipment Notice message (856/DESADV) should be automatically prepared
for EDI when the shipment gets confirmed, or whether it should be manually
prepared using the Confirm ASN (whinh4532m000) session.
Prompt for Change Codes (within Sales Control): This field is maintained
in the Sales Order Parameters (tdsls0100s400) governs whether or not change
codes (change type code, change reason codes and acknowledgement codes)
may be maintained on a sales order. It is required that this be enabled if you
wish to process the EDI Order Change (860/ORDCHG) message.
Modifying EDI Orders Allowed: This field is maintained in the Sales Order
Parameters (tdsls0100s400) governs whether or not sales order created
customer orders received through EDI may be updated manually using the
sales order sessions (tdsls4500m000/tdsls4501m000).
Use Number Group for Addresses: This field maintained in the COM
Parameters session (tccom0000m000) indicates whether or your company
uses address codes, and whether addresses may be created on-the-fly. This
must be enabled if you wish to process specific address information on
incoming orders and schedule releases. If not, the default address defined for
the business partners will always be used.
EDI Change Order Response: This field maintained in the Sold-To

Business Partner session (tdsls4110s000) indicates if your business partner is
to received order acknowledgements (855/ORDRSP) or order change
acknowledgements (865) in response to sales order changes after the original
order acknowledgement has been sent.
See the selling company section in Chapter 6 for additional information about
these parameter settings.
EDI User Guide

3-35
EDI User Guide

3-36
Running EDI
Now that you have completed the basic setup of Baan EDI, you want to get Baan
EDI up and running. This section describes how to receive and generate the
ASCII files exchanged with your communication/translation software using the
sessions found on the Communication menu in the EDI module. Chapter 5,
Incoming message data, describes message handling and error processing.
Chapter 6, EDI procedure, explains the procedural steps required to exchange
specific messages.
Processing files
You can use the Direct Network Communication (ecedi7205m000) session to
receive incoming EDI messages (to read the ASCII files received from your
trading partner through your translation/communication software or directly from
another internal Baan company).
Figure 47 Direct Network Communication (ecedi7205m000) session
You can use the Generate EDI Messages (ecedi7201m000) session to generate
outgoing EDI messages. This session creates the ASCII files for all documents
that have been prepared for EDI. These ASCII files are read by your
translation/communication software and transmitted to your trading partner(s).
(Chapter 6 provides a full explanation of the steps required to prepare
documents).
EDI User Guide

4-1
Running EDI
Figure 48 Generate EDI Messages (ecedi7201s000) session
Alternatively, you can use the Direct Network Communication (ecedi7205m000)

session to both receive and generate EDI messages. Selecting the Generate
Outgoing Messages before Connection check box at the network (see Figure 8)
will result in the Direct Network Communication (ecedi7205m000) session
generating all outgoing messages (equivalent to running the Generate EDI
Messages (ecedi7201m000) session) prior to reading incoming messages.
Although you can run these sessions to manually initiate the receipt or generation
of EDI messages, you can also automate the process by using the EDI
Interchange controller to initiate direct network communication via a schedule
that you define.
EDI interchange controller

The Job Management module in BaanERP Tools handles the automation of EDI
processing by creating a job that runs the Direct Network Communication
(ecedi7205m000) session at a regular interval. However, this means that you
must start several of these jobs when EDI messages for different networks must
be generated at different intervals. So the status of the individual jobs cannot be
displayed in one single screen which leads to the loss of job manageability.
To provide a more flexible way of determining intervals and provide a better
overview of the communication status of the individual networks, the EDI
module offers an Interchange controller. The rest of this section describes how to
setup and use this controller.
Controller setup
The first step is to determine which networks should have automated
communication and at what time interval.
EDI User Guide

4-2
Running EDI
Figure 50 shows how to record these connect frequencies (communication

intervals). You can define as many frequencies as required. Each column
represents a different frequency.
In this example, a single frequency is recorded for the External Trade Network.
The active frequency runs on each workday of the year 1998 (5 days a week)
through the end of December. The Direct Network Communication
(ecedi7205m000) session is started multiple times each day beginning at 6:00
A.M. A new session is launched every 30 minutes (time interval) until 5:30 P.M.
(17:30).
Figure 49 Connect Frequencies by Network (ecedi0522m000) session
Figure 50, Connect Frequencies by Network (ecedi0122s000) session
EDI User Guide

4-3
Running EDI
You can generate a list of individual connect times (the moments that
communication must be activated) per network that is based on the frequencies.
Instead of having to maintain the next connect time with the Connect Times by
Network (ecedi0125s000) session, Baan can calculate the connect times for you
by using the data defined in the Connect Frequencies by Network
(ecedi0122s000) session.
The individual connect times are generated with the Generate Connect Times by
Network (ecedi0225m000) session.
Figure 51 Generate Connect Times by Network (ecedi0225m000) session
EDI User Guide

4-4
Running EDI
The Connect Times by Network (ecedi0125m000) session can display or modify

the result. Notice that the specified frequency indeed results in connect times
each 30 minutes beginning at 6:00 A.M.
Figure 52 Generate Connect Times by Network (ecedi0125m000) session
EDI User Guide

4-5
Running EDI
Using the interchange controller

Based on the generated or manually entered connect times, the interchange
controller will start the Direct Network Communication (ecedi7205m000)
session for the appropriate network at regular intervals. Baan EDI activates the
interchange controller as a background process. After making the desired
selections, click Continue and let the session run in the background.
Figure 53 EDI Interchange Controller (ecedi7210m000) session
You can activate the interchange controller for all networks, or exclude
individual networks. To deactivate the controller, press cancel button in the
processing popup.
Figure 54 Processing Popup Window
EDI User Guide

4-6
Running EDI
With the active controller running in the background, the interchange monitor
can check the communication status of the individual networks. Unlike Job
Management in BaanERP Tools, Baan EDI displays the pending jobs (connect
times) of all networks in a single screen. The interchange monitor will only show
the pending jobs for the current day. After a job is finished, Baan EDI removes it
from the list.
Figure 55 EDI Interchange Monitor (ecedi7505m000) session
When Baan EDI reaches a connect time for one of the networks, it starts the
Direct Network Communication (ecedi7205m000) session for that network. The
interchange monitor will show the following:
n
Which networks are active when the monitor is started (the Communication
Status will be Active).
What activity the network is currently performing (displayed under the

Activity Status).
EDI User Guide

4-7
Running EDI
External EDI network communication

Whenever the interchange controller initiates the Direct Network
Communication (ecedi7205m000) session, it uses semaphores to indicate to the
external translation/communication software that it is currently processing
messages. The semaphore mechanism uses empty files in the command directory
of the network to indicate that a certain process is active or is ready for
activation. This mechanism ensures that Baan EDI and the
communication/translation software do not try to simultaneously access the same
files in the same directory. Figure 56 shows the use of semaphores during a
direct network communication if you are not suppressing standard
communication for the network.
EDI Translator
BAAN EDI
BAAN Application
"knows" that EDI
Translator is active
Comm.yes
Create
Comm.yes file
Generate outgoing
message
Perform conversions
and process messages
(in and out)
Initiate
communication:
create Command.fil file
Command.fil
Read
incoming
messages
Terminate front end

processor: create
Command.end file
Delete
Command.fil file
Command.end
Stop execution
Figure 56 Semaphores
When the translation/communication software (translator) becomes active, it

creates a file called Comm.yes in the command directory. This lets Baan EDI
know that a translator is active (but not necessarily processing).
EDI User Guide

4-8
Running EDI
The shaded area in Figure 56 represents the Direct Network Communication

process each time it is initiated.
If the external EDI network is set up to generate EDI messages in addition to
importing messages during direct network communication (the Generate
outgoing Messages Before Connection check box at the network is checked):
n
Baan EDI will generate outgoing messages first, then create a file called
Command.fil in the command directory when it has completed generating the
outgoing messages.
If the process is not generating outgoing messages (the Generate outgoing

Messages Before Connection check box at the network is not checked):
n
It will create the Command.fil file upon activation of direct network

communication.
The Command.fil file lets the translation/communication software know that

Baan EDI is finished processing and that the translation/communication software
is free to begin processing.
The translation/communication software performs the following tasks:
n
n
n
Reads any messages created by Baan EDI

Generates any messages received from external trading partners.
Once it has completed processing, it deletes the Command.fil file from the
command directory.
The lack of the Command.fil file lets Baan EDI know that the
translation/communication software has completed its processing, and that Baan
EDI is free to begin reading incoming messages.
Finally, you may run the Terminate Front-End EDI Processor (ecedi0249m000)
session within the EDI module, to terminate communication to your
translation/communication software. This session creates a file called
Command.end in the command directory. You can use this file to terminate the
translation/communication software.
To use this semaphore mechanism provided by Baan EDI, your
translation/communication software must create/delete/check these semaphore
files as indicated.
EDI User Guide

4-9
Running EDI
To avoid unnecessary allocation of CPU resources during the create/delete/check

process before semaphores have been removed, you must activate the
interchange controller within Baan EDI and the scheduling mechanism within the
translation/communication software at sequenced, staggered intervals, such as
the following:
Baan application
company
Connect times
EDI User Guide

4-10
Translation/communication
software
06:00
08:00
12:00
14:00
18:00
20:00
Incoming message data
Processing interactive messages

Baan EDI can process inbound messages interactively or automatically (see the
EDI messages supported by business partner section in Chapter 3).
If you set up messages as interactive, when you run the Direct Network
Communication (ecedi7205m000) session the message will be stored directly in
the Saved Messages to Be Received (ecedi750) table, without validation. This
allows you to preview incoming messages before they are validated and before
they update the Baan application. Use the Messages to be Received
(ecedi7150m000) session to view, modify, approve, and process these messages.
Reprocessing messages with errors

When processing incoming messages, Baan sometimes finds validation errors
that prevent the message from being updated in the Baan application. In this
case, it stores the entire message in the Saved Messages to be Received table.
Use the Messages to be Received (ecedi7150m000) session to view and correct
data errors, approve, and reprocess the message.
EDI User Guide

5-1
The session flow for incoming messages processed with errors or processed
interactively is shown in Figure 57.
Direct Network
Communication
(ecedi7205m000)
Received
Batch Reference
(ecedi7560m000)
or
Print Saved
Messages to be
Received
(ecedi7450m000)
Saved
Messages to be
Received
(ecedi7150m000)
Received
Message Errors
(ecedi7551m000)
Print Received
Message Errors
ecedi7551m000)
Saved
Message Data to be
Received
(ecedi7151s000)
Approve Saved
Messages to be
Received
(ecedi7250m000)
Process Saved
Messages to be
Received
(ecedi7252m000)
Figure 57 Message processing session flow
EDI User Guide

5-2
Delete Saved
Messages to be
Received
(ecedi7251m000)
For each processing occurrence, a unique batch number is assigned for each
network. The following session records all processed (successful or
unsuccessful) incoming messages.
Figure 58 Received Batch Reference (ecedi7560m000) session
EDI User Guide

5-3
Use the following session to view and/or correct data for reprocessing. You can
view interactive data or validation data.
Figure 59 Saved Messages to be Received (ecedi7150m000) session
After selecting a record, use the following form to correct the message data in the
selected record. The number of forms used depends on the number of fields in
the record.
EDI User Guide

5-4
Figure 60 shows the first error/warning message. If additional error/warning

messages exist for this record, the More Messages check box will be checked;
you can zoom from this form to view all corresponding error/warning messages
using the Display Errors button.
Figure 60 Saved Message Data to be Received (ecedi7151s000) session
After approving the messages with the Approve Saved Messages to be Received
(ecedi7250m000) session, use the following session to reprocess them.
Figure 61 Process Saved Messages to be Received (ecedi7252m000) session
EDI User Guide

5-5
EDI User Guide

5-6
EDI procedure
After approving the messages with the Approve Saved Messages to be Received
(ecedi7250m000) session, use the following session to reprocess them.
This section explains the procedural steps that should be completed for a full
order cycle, using all supported EDI messages. Note that this example assumes
manually initiating direct network communication to both receive and generate
messages, instead of using the interchange controller to automate this step.
General procedures: purchasing company

If you are the purchasing company exchanging documents with your supplier, the
following diagram and list summarizes the procedural steps that you may be
completed for a full purchasing cycle.
Regenerate
Schedule
Release
Prepare Schedule
Release
(830/862/866/out)
Enter
Purchase
Order
Prepare PO
Change (860 out)
Supplier
Prepare Purchase
Order (850 out)
Print
Purchase
Order
Maintain
Receipts
Baan Company
Database
Via translator/
communication
software
Run Direct
Network
Communication
Prepare Error
Notification
(824/out)
Receive PO
Acknowledgment (855 in)
Prepare
Receipt
Discrepancy
Receive Shipment
Notice (ASN) (856 in)
Receive Invoice
(810 in)
Receive PO Chg
Acknowledgment (865 in)
Figure 62 Purchasing EDI procedure
EDI User Guide

6-1
EDI procedure
Purchase requirements may be communicated to your supplier via purchase

orders or purchase schedule releases.
Using Orders:
n
Create and print a purchase order. Printing the purchase order will prepare the
EDI message (850/ORDERS out) for transmission. After printing the
purchase order, use the Messages to be Generated (ecedi7100m000) session
to verify that the message was prepared.
Run the Direct Network Communication (ecedi7205m000) session to send

the purchase order (850/ORDERS out) to your supplier.
Optionally, maintain the purchase order and print changed lines. Printing the
purchase order (for new and changed lines) will prepare the EDI message
(860/ORDCHG out) for transmission. Run the Direct Network
Communication (ecedi7205m000) session to send a Purchase Order Change
to your supplier.
Run direct network communication to receive either a Purchase Order

Acknowledgement (855/ORDRSP in) or a Purchase Order Change
Acknowledgement (865/ORDRSP in). This will generate a report if there are
any differences between the acknowledgement and the order; the purchase
order may also be optionally updated, depending on the conversion setups
that you choose (see Appendix A for more information).
Using Schedule Releases:
EDI User Guide

6-2
Generate (Purchase) Schedule Releases. If the Generate EDI Releases

Directly check box is checked in the Item/Supplier Information
(tdipu0110s000) session, generating the schedule release using the
Regenerate Schedules (tdpur3207m000) will prepare the EDI message
(830/DGELFOR, 862/DELFOR, 866/DELJIT) for transmission. If the
Generate EDI Releases Directly check box is not checked, running Generate
Schedule Releases (tdpur3208m000) will prepare the EDI messages for
transmission, if elected. (Note that the 862/DELFOR and 866/DELJIT
messages follow an 830/DELFOR message).

the purchase schedule release (830/DELFOR, 862/DELFOR, 866/DELJIT
out) to your supplier.
EDI procedure
Using either Orders or Schedule Releases:

n
Run the Direct Network Communication to receive the Shipment Notice

(ASN) (856/DESADV in). This will create a Shipment Notice in the Baan
application.
If there is an error in the received shipment notice, the erroneous data and
corresponding errors will be stored in Saved Messages to be Received and
Saved Error Messages respectively, in EDI, as is the case with all erroneous
messages received. If the Automatically Prepare Error Notifications check
box is checked in EDI Messages Supported by Business Partner, an outgoing
Error Notification (824/APERAK out) message is prepared. Alternatively,
Print Received Message Errors (ecedi7451m000) can prepare outbound Error
Notifications (824/APERAK) for erroneous messages received.
The error notification may be prepared for any erroneous message, but is of
particular use for the erroneous shipment notice in supply chain
environments. Erroneous shipment notices received store additional error
information within the Baan EDI, based on the data defined in the
Application Errors (ecedi2191m000) session.
NOTE:

the Error Notification (824/APERAK out) to your supplier if applicable.
Upon receiving the goods, use the Receipts (whinh3520m000) session to

enter the receipt data. If you select a shipment notice against which to receive
the goods, any discrepancies between the received quantity and the shipment
notice quantity will be stored, and a Receipt Discrepancy Notification
(861/RECADV) will be prepared for EDI.

the Receipt Discrepancy Notification (861/RECADV out) to your supplier
Run the Direct Network Communication (ecedi7205m000) to receive the

Invoice (810/INVOIC in). This will create a purchase invoice in your Baan
company.
EDI User Guide

6-3
EDI procedure
General procedures: selling company

If you are the selling company, the following diagram (Figure 63) and list
summarizes the procedural steps that you must complete for a full sales cycle.
Receive Purchase
Order (850 in)
Receive PO
Change(860/In)
Customer
Receive Planning
Release (830/In)
Via translator/
communication
software
Receive Shipping
Release (862/In)
Receive
Receipt
Discrepancy
(861/in)
Receive Sequenced
Shipping
Release (866/In)
Run Direct
Run Direct
Network
Network
Communication
Communication
Receive
Error
Notification
(824/in)
Baan Company
Database
Prepare Order
Acknowledgment (855 or 865 out)
Prepare Shipment ( ASN)

(856 out)
Prepare Invoice
(810 out)
Print Order
Acknowledgment
Confirm ASN
for Lines on
Confirmed
Shipment
Compose/Print/Post
Invoice for
Delivered Lines
Figure 63 Selling EDI procedure
Customer purchase requirements may be communicated via purchase orders or

purchase schedule releases.
Using Orders:
EDI User Guide

6-4
Run the Direct Network Communication (ecedi7205m000) session to receive

the customer purchase order (850/ORDERS in). This will create a sales order
in your Baan company.
Evaluate the sales order and print the order acknowledgement. This will
prepare the outgoing Order Acknowledgement (855/ORDRSP out) for
transmission.
EDI procedure
Run direct network communication to send the order acknowledgement

(855/ORDRSP out) to your customer.
Run direct network communication to receive a Purchase Order Change

(860/ORDCHG in)
Optionally, if any information is subsequently changed on the sales order

which was created from the customer purchase order, print the order
acknowledgement (for changed and new lines) to prepare the order
acknowledgement or order change acknowledgement. Run the Direct
Network Communication to send either the Order Change Acknowledgement
(865/ORDRSP out) or the Order Acknowledgement (855/ORDRSP out) for
those changed or new lines you want to convey to your customer.
Using Schedule Releases:

n
Run the Direct Network Communication (ecedi7205m000) session to receive

the customer schedule release (830/DELFOR, 862/DELFOR, or 866/DELJIT
in). This will create a sales release (planning release, shipping release or
sequenced shipping release, respectively) and corresponding sales schedule(s)
in your Baan company. If the sales release and schedules already exist, the
updates may be reflected as new revisions to the existing release and
schedule(s).
Using either Orders or Schedule Releases:

n
Confirm a Shipment against the order and/or schedule release. If the Generate
ASNs Automatically check box in the Warehousing parameters is checked,
the Shipment Notice (856/DESADV out) is prepared for transmission once
the shipment is confirmed. If the Generate ASNs Automatically check box in
the Warehousing parameters is not checked, run the Confirm ASN session to
prepare the message for transmission.
Run the Direct Network Communication to send the Shipment Notice (ASN)
(856/DESADV out) to your customer.
Run the Direct Network Communication session to receive any Error

Notifications (824/APERAK), indicating that a previously transmitted
Shipment Notice (856/DESADV) included erroneous information. Because
the Error Notification refers to a previously generated Shipment Notice
(856/DESADV), the EDI Status field on the shipment is Disapproved, and a
(cancelling) Shipment Notice (856/DESADV) is prepared. Run the Direct
Network Communication to send the (cancelling) Shipment Notice
(856/DESADV) to your customer. The EDI Status on the shipment is
changed to Modify.
EDI User Guide

6-5
EDI procedure
If the EDI Status on the shipment is Modify, you may modify the date/time,
quantity or weight, and any EDI data included on the shipment notice to
correct the erroneous shipment notice data. Run the Confirm ASN
(whinh4532m000) session to prepare the corrected Shipment Notice
(856/DESADV out) for EDI transmission; the EDI Status on the shipment is
Confirmed. Run the Direct Network Communication to send the corrected
Shipment Notice (856/DESADV out) to your customer.
Run the Direct Network Communication to receive any Receipt Discrepancy

Notifications (861/RECADV in), indicating that the customer found a
discrepancy between the quantity of goods received and the quantity
indicated on the Shipment Notice. The discrepancies are reported, and the
shipments text fields and EDI Information fields may be updated.
Run the Compose/Print/Post Invoices (cisli2200m000) session. This will

prepare the Invoice (810/INVOIC out) for transmission.
Run Direct Network Communication to send the Invoice (810/INVOIC out)

to your customer (invoice-to business partner).
Run the Direct Network Communication to receive the Remittance Advice

from your customer (pay-by business partner).
General message processing requirements

For all outgoing messages:
For messages to be prepared, the following conditions must be met:
EDI User Guide

6-6
The business partner is linked to a network
The EDI Messages Supported by Business Partner (ecedi011) table is filled

for the combination: business partner, message, converted order type (if it
applies), and direction for the organization. The record in this table must
specify the same network as the one linked to the business partner and must
specify a conversion setup.
EDI procedure
For all incoming messages:

The following conditions must be met (as explained in the setup sections of this
document):
n
The network address specified in the incoming file is valid for the network
and is linked to a valid business partner.
The order type specified in the file is present in the Order Types table (note
that blank order types must be specified for the case when no order type value
is passed).
The EDI Messages Supported by Business Partner (ecedi011) table is filled

for the combination: business partner, message, specified order type and the
direction, for the specified organization.
The ASCII files must reside in the Appl_to subdirectory in the directory
specified for the Network in the EDI Messages Supported by Business
Partner (ecedi011) table for this message type and business partner.
The record in EDI Messages Supported by Business Partner (ecedi011) table

must specify a conversion setup.
The ASCII file Command.fil must be removed from the command directory
if you are not suppressing standard communication and if the business partner
is an external EDI trading partner.
All incoming messages generate a Remarks in Copied Message report. This

report indicates the type of document received, the internal document number
generated or updated, the line number(s) created or updated, and any remarks
pertaining to the document.
The next sections walk you through an example in which each step is explained
in more detail, first for the purchasing company, then for the selling company.
EDI User Guide

6-7
EDI procedure
The purchasing company

This section demonstrates the steps required to exchange EDI documents with
your supplier. In this example you are the purchasing company.
Purchase requirements may be communicated to your supplier via purchase
orders or purchase schedule releases. Examples of both document types are
included in this section.
Enter and print purchase order

Figure 64 shows the Print Purchase Order (tdpur4401m000) session. This session
prepares the outgoing Purchase Order EDI message (850/ORDERS out). When
you run this session the system verifies that the order or orders are prepared for
EDI transmission and are stored in the Messages to be Generated (ecedi700)
table.
Figure 64 Print Purchase Orders (tdpur4401m000) session
All of the conditions previously listed in the General message processing

requirements section must be met before a message can be prepared for EDI.
However, if any of the conditions are not met, the hard copy of the purchase
order will still be printed. This hard copy can also be printed when the previous
conditions are met if the Print check box in the EDI Messages Supported by
Business Partner (ecedi0111m000) session is checked. If a hard copy of the
purchase order is printed for an order which has also been prepared for EDI, the
words EDI Copy will appear on the upper left-hand corner of the printed
purchase order document.
EDI User Guide

6-8
EDI procedure
NOTE
The order type of the purchase order must be defined in the Conversion of
Purchase Order Types Out (ecedi4133m000) session in order for the order to be
prepared for EDI; and, the Code in Message for the order type conversion must
match the order type specified in the EDI Messages Supported by Business
Partner (ecedi0111s000) session for this message and business partner.
NOTE
The purchase order type used on the order should include the Print Purchase
Order session (tdpur4401m000) as an activity, and also allow this activity to be
re-executed at subsequent steps.
You can verify that the outgoing message was prepared for EDI, using the
Messages to be Generated (ecedi7100m000) session. If you do not want the
message to be generated the next time the Direct Network Communication
session is run, you can delete the message from this session.
Figure 65 Messages to be Generated (ecedi7100m000) session
EDI User Guide

6-9
EDI procedure
Sending the purchase order (850/ORDERS)

Once the document is prepared for EDI by purchasing, the EDI module can
generate the outgoing EDI order message.
If you are not using the interchange controller to automate the process, you can
manually generate the outgoing message using one of the following sessions:
n
Generate EDI Messages (ecedi7201m000) session

Constructs the outgoing messages that are eligible for transmission (present
in Messages to be Generated, ecedi700, table) and within the specified
selection range. For external EDI business partners, Baan EDI puts the
outgoing messages in the Appl_from directory in the directory defined for the
network specified for the Message by Business Partner. For additional
information, see the Processing files section in Chapter 4.
Direct Network Communication (ecedi7205m000) session

Generates any outgoing messages (if the network is set up to do so) and then
reads in any incoming messages. For additional information, see the
Processing files section in Chapter 4.
Both sessions display the reference number, message and order number of the
order that is currently processed. Notice that the reference number is constructed
as defined in the Networks (ecedi0520m000) session.
Both sessions also generate a report to show which messages have been
generated. This is the Remarks in Generated Messages (ecedi7601m000) report.
Receiving the order acknowledgment (855/ORDRSP)

Your supplier can send order acknowledgments after receiving your purchase
order. You may receive order acknowledgments as 855/ORDRSP incoming
transactions. Once the order acknowledgment is received, the ASCII files are
translated from their standard format into the file format defined by your
conversion setups, if external EDI. The resulting ASCII file is placed in the
appropriate appl_to directory by the translation/communication software. You
must run the Direct Network Communication (ecedi7205m000) session to
receive the order acknowledgment.
You can set up the incoming order acknowledgment message to:
EDI User Guide

6-10
Update the purchase order with any values specified on the acknowledgement
that do not agree with the purchase order, and report the differences found.
Report the differences only
EDI procedure
This is defined within the conversion setups, on a field by field basis. In

BaanERP, there are two separate conversion setups for the incoming order
acknowledgment (855/ORDRSP): for example, 855.C is for comparison while
855.U is for update. See Appendix A for more detailed information about the
conversion setups. When the Direct Network Communication receives the order
acknowledgment, you will receive the Differences between Purchase Order and
Order Acknowledgment report which show the differences between the purchase
order and the order acknowledgment.
Changing the purchase order (860/ORDCHG)

You have the option of transmitting a Purchase Order Change transaction to your
supplier to reflect any changes you have made to your purchase order.
To use this function, you must use change type codes in Purchase Control. In
order to apply change codes to purchase orders, the Prompt for Change Codes
check box in the Purchase Order Parameters (tdpur0100s400) session must be
checked. Change type codes and change reason codes can then be assigned to a
purchase order when changes are made to the order. Change Type Codes must be
present on all lines that you wish to include on an EDI change order
(860/ORDCHG) message; they are used to indicate the type of change last made
to the order or order line.
The change type codes provide you with some flexibility because you can select
the types of changes you transmit to your supplier.
NOTE
There is no way to directly transmit the cancellation or deletion of an individual

purchase order line. To do this, you must change the order line quantity to zero,
or assign a change type code representing a deleted or canceled line, and process
the line as a change. When the order acknowledgment is received back from your
supplier, you can delete this line.
Before you print purchases orders to prepare the outgoing messages, you can run
the Print Purchase Orders to be Printed (tdpur7403m000) session, which shows
the purchase order lines that will be included and prepared for EDI the next time
you run the Print Purchase Order (tdpur4401m000) session. Use this report to
ensure that change type codes have been assigned to all appropriate lines.
EDI User Guide

6-11
EDI procedure
When you run the Print Purchase Order (tdpur4401m000) session for EDI
purchase order changes, it is recommended that you set the Order Line Types to
Print field to New and Changed Lines, to include only changed and new lines
that have been changed or added since the orders last generation. Alternatively,
you can set the Order Line Types to Print field to Only Changed Lines, to include
changed lines only, or Exclude Printed Lines, to include only new lines added
since the orders last generation. Any of these three setting results in this session
preparing the outgoing Purchase Order Change EDI message for only those new
and changed order lines that were assigned a change type code. This ensures that
only those new or changed lines, and their corresponding change type codes, are
included in the message.
When you run this session the system verifies that the order or orders are
prepared for EDI and are stored in the Messages to be Generated (ecedi700 and
ecedi708) table.
Figure 66 Print Purchase Orders (tdpur4401m000) session
Messages to be Generated (ecedi7100m000). If you do want the message to be
generated the next time the Direct Network Communication session is run, you
can delete the message from this session.
EDI User Guide

6-12
EDI procedure
Sending the purchase order change (860/ORDCHG)

Once the document is prepared for EDI by purchasing, the EDI module can
generate the outgoing EDI order message.
If you are not using the interchange controller to automate the process, you can
manually generate the outgoing message using one of the following sessions:
n
Generate EDI Messages (ecedi7201m000) session

Constructs the outgoing messages that are eligible for transmission (present
in Messages to be Generated, ecedi700, table) and within the specified
selection range. For external EDI business partners, Baan EDI puts the
messages in the Appl_from directory in the directory defined for the network
specified for the Message by Business Partner. For additional information,
see the Processing files section in Chapter 4.
Direct Network Communication (ecedi7205m000) session

Generates any outgoing messages (if the network is set up to do so) and then
reads in any incoming messages. For additional information, see the
Processing files section in Chapter 4.
Both sessions display the reference number, message and order number of the
order that is currently processed. Notice that the reference number is constructed
as defined in the Networks (ecedi0520m000) session.
Both sessions also generate a report to show which messages have been
generated. This is the Remarks in Generated Messages (ecedi7601m000) report.
Receiving the purchase order change acknowledgment

(865)
You may receive order change acknowledgments from your supplier after he
receives your purchase order change. Such order acknowledgments can take the
form of an Order acknowledgment (855/ORDRSP) or an Order change
acknowledgment (865) incoming message.
You can set up the incoming order acknowledgment message to do one of the
following:
n
Update the purchase order with any values specified on the acknowledgement
that do not agree with the purchase order, and report the differences found
Report the differences only
EDI User Guide

6-13
EDI procedure
This is defined within the conversion setups, on a field by field basis. In

BaanERP, there are two separate conversion setups for the incoming order
change acknowledgment (865):
n
n
865.C - for comparison only

865.U - for update only
See Appendix A for detailed information about conversion setups.

Run the Direct Network Communication (ecedi7205m000) session to receive in
the order (change) acknowledgment, once the ASCII files have been placed in
the appropriate appl_to directory by your translation/communication software.
When the Direct Network Communication receives the order acknowledgment,
the Differences between Purchase Order and Order Acknowledgment report is
generated, which shows the differences between the purchase order and the order
acknowledgment.
Generating and Sending the Purchase Schedule Release

(830/DELFOR, 862/DELFOR, 866/DELJIT)
If you choose to convey your purchase requirements to your supplier (buy-from
business partner) using purchase releases, the following three types of releases
are available to you:
EDI User Guide

6-14
Planning Release (830/DELFOR) which conveys material requirement

information to you supplier.
Shipping Release (862/DELFOR) which is intended to supplement the

Planning Release. This document may contain precise shipping release
requirements sent on a more frequent basis than with the issuance of the
Planning Release.
Sequenced Shipping Release, which is intended to supplement the Shipping

Release, but may follow a Planning Release directly. This document specifies
precise information pertaining to the delivery of goods, which includes the
order in which goods are to arrive at their destination (s), or are to be
unloaded from the conveyance method when received at their destination(s).
EDI procedure
All three of the purchase releases may be prepared for EDI as follows.
Use the Regenerate Schedules (tdpur3207m000) session to generate your
Purchase Schedule Releases (planning release, shipping release or sequenced
shipping release). If the Generate EDI Releases Directly check box defined in the
Item/Supplier Information (tdipu0110s000) session is checked, this session also
prepares the outgoing Purchase Release (830/DELFOR out, 862/DELFOR out or
866/DELJIT out) for EDI transmission.
Figure 67 Regenerate Schedule (tdpur3207m000) session
If the Generate EDI Releases Directly check box defined in the Item/Supplier
Information (tdipu0110s000) session is not checked, then you must additionally
run the Generate Schedule Releases (tdpur3208m000) session to prepare the
outgoing Purchase Release (830/DELFOR out, 862/DELFOR out or 866/DELJIT
out) for EDI transmission.
Figure 68 Generate Schedule Releases (tdpur3208m000) session
EDI User Guide

6-15
EDI procedure

requirements section must be met in before a message can be prepared for EDI.
As with all outgoing EDI message, you may manually generate the outgoing
message using the Direct Network Communication (ecedi7205m000) session, if
the network is setup to generate outgoing messages during Direct Network
Connection, or the Generate EDI Messages (ecedi7201m000) session. A report is
generated listing the messages that were generated. For external EDI, the
outgoing message (ASCII) files are placed in the appl_from directory, under the
networks directory, from which the translation/communication software will
retrieve them.
Receiving the Shipment Notice (856/DESADV)

the Shipment Notice message (856/DESADV) from your supplier (ship-from
business partner), once the ASCII files have been placed in the appropriate
appl_to directory by your translation/communication software.
When the Direct Network Communication receives the Shipment Notice
message (856/DESADV), a Shipment Notice is created in your Baan company,
and the Remarks in Copied Messages report is generated, showing the shipment
notice number and line number(s) generated, along with any pertinent remarks.
When the shipped goods are subsequently received at your site, you can use the
Shipping Notice to facilitate the receiving process. In the Receipts
(whinh3520m000) session you can select a Shipment Notice to automatically
populate the receipt data with the data from the Shipment Notice. (See the
Sending the Receipt Discrepancy Notification (861/RECADV) section in this
chapter for more information).
NOTE
EDI User Guide

6-16
The shipment status code included in the Shipment Notice message is validated
against the Conversion of Shipment Status Codes/In (ecedi3146m000) when a
Shipment Notice is received. In order to support the requirements of some EDI
standards, Baan EDI supports the receipt of two kinds of Shipment Notices, a
canceling Shipment Notice, and an original Shipment Notice. A received
Shipment Notice with an original shipment status is processed as indicated
above. A received Shipment Notice with a canceling shipment status is intended
to cancel a previously sent erroneous Shipment Notice, and will delete the
invalid Shipment Notice message from the Saved Messages to be Received in
EDI, where erroneous messages are stored.
EDI procedure
Sending the error notification

If there is an error in the received Shipment Notice, EDI automatically prepares
an outgoing Error Notification message (824/APERAK) if the following
conditions are met:
n
The Automatically Prepare Error Notification check box in the EDI Messages
Supported by Business Partner (ecedi0111s000) session is checked, for the
business partner and incoming Shipment Notice message.
The Ship-from Business Partner from whom the Shipment Notice was
received is setup to receive the Error Notification message (824/APERAK) in
the EDI Messages Supported by Business Partner (ecedi0111s000) session.
The Error Notification message may also be manually prepared by running the
Print Received Errors (ecedi7451m000) session, and selecting the check box to
Prepare Error Notification.
NOTE
The error notification may be prepared for any erroneous message received, but
is of particular use for the erroneous shipment notice in some supply chain
environments. Baan EDI logs the additional application error data from the
Application Errors (ecedi2191m000) session only for erroneous shipment notices
received. As with all erroneous messages received, when the erroneous Shipment
Notice is received, the message data and corresponding errors are stored in Saved
Messages to be Received and Saved Error Messages, within Baan EDI Message
Data. When the erroneous message received is a Shipment Notice
(856/REVADV), additional information may be logged based on the information
defined in the Application Errors (ecedi2191m000) session. This information
may be included on the outgoing error notification message.
the network is setup to generate outgoing messages during direct network
connection, or the Generate EDI Messages (ecedi7201m000) session. A report is
retrieve them.
EDI User Guide

6-17
EDI procedure
Sending the Receipt Discrepancy Notification

(861/RECADV)
Upon receiving a shipment, use the Receipts (whinh3520m000) session to enter
the receipt information. Using the Special menu, select a shipment notice against
which to receive the goods by zooming to the Expected Shipments
(whinh3820m100) session, selecting the appropriate shipment notice record and
clicking Add to Receipt, as shown in Figures 69 and 70. This will populate the
receipt data with the shipment notice data. Then, you can make any necessary
corrections to the receipt data, using the Receipt Lines (whinh3120s000) session.
Figure 69 Receipts (whinh3520m000) session
Figure 70, Expected Shipments (whinh382m100) session
EDI User Guide

6-18
EDI procedure
If there is any discrepancy between the shipped quantity on the Shipment Notice
and the actual receipt quantity recorded, the discrepancy is logged, and a Receipt
Discrepancy Notification message (861/RECADV) is prepared for EDI once the
receipt is confirmed.
NOTE
The default conversion setup definition (file layout) of the outgoing Receipt
Discrepancy message includes the Receipt Discrepancy Code defined in the
Receipt Discrepancy Code Out (ecedi4147m000) session. This is used to convey
the type of discrepancy encountered during the receipt process, which can be one
of the following:
n
The quantity received was greater then the quantity indicated on the shipment
notice (quantity over);
The quantity received was less then the quantity indicated on the shipment
notice (quantity short);
No Shipment Notice was received prior to the receipt of the goods (No ASN).
If you wish to indicate that no Shipment Notice was received at the time of
receipt, you must manually enter a Shipment Notice with zero quantities,
using the Shipment Notices (whinh3500m000) session, prior to processing
the receipt.
retrieve them.
Receiving the sales invoice (810/INVOIC)

the Invoice message (810/INVOIC) from your supplier (invoice-from business
partner), once the ASCII files have been placed in the appropriate appl_to
directory by your translation/communication software.
When the Direct Network Communication receives the Invoice message
(810/INVOIC), a purchase invoice is created in your Baan company, and two
reports are generated. The first report is the Remarks in Copied Messages report
is generated, showing the invoice number(s) generated, along with any pertinent
remarks. The second report is the Incoming EDI Purchase Invoice report, which
lists the invoiced quantity and amounts at the line level and the tax amounts by
tax code ID, if applicable.
EDI User Guide
6-19
EDI procedure
If the ordered goods were received before receiving the invoice, the invoice will
automatically be matched. If the ordered goods have not yet been received, the
invoice will remain unmatched, and may be manually matched when the goods
are subsequently received.
The invoice matching can occur at either the invoice header or the invoice line
depending on the data received in the incoming purchase invoice message:
n
Invoice Matching at the Invoice Header: In order to do invoice matching at

the header, the Automatic Matching check box in the ACP Parameters
(tfacp0100s000) session must be checked. If the received purchase invoice
message includes a valid customer purchase order number in the invoice
header, and no invoice order line information, the entire order is matched for
all order lines for which goods have been received. If the tolerance is not met,
the entire purchase invoice remains unmatched.
Invoice Matching at the Invoice Line: If the received purchase invoice

message includes order line information, each invoice line is matched to the
included customer order lines for which goods have been received. The
invoice lines for which the ordered goods have not yet been received remain
unmatched.
You can review the received invoice data with the Match/Approve Purchase
Invoices (tfacp2507m000) session.
This concludes an example of a normal order cycle, using the EDI messages
supported by Baan EDI, when you are exchanging EDI documents with a
supplier. However, the orders still need to be closed.
To automate the execution of the Direct Network Communication
(ecedi7205m000) session, see the EDI interchange controller section in
Chapter 4.
EDI User Guide

6-20
EDI procedure
The selling company

This example explains the steps required to exchange EDI documents with a
buyer (customer) when you are the supplier.
Receiving the customer order (850/ORDERS)

To receive in the order, use the Direct Network Communication
(ecedi7205m000) session. You cannot start this process until the following has
occurred:
n
You receive the customer purchase order (850/ORDERS) from your

customer.
The translation/communication software has translated the files from their

standard format into the file format defined by your conversion setups and
placed the files in the appropriate Appl_to directory, if an external EDI
business partner.
All conditions listed previously in the General message processing requirements

section in this chapter must be met before the message can be read.
When the Direct Network Communication (ecedi7205m000) session receives in
the customer order, it creates a sales order in your Baan company, and generates
the Remarks in Copied Messages report showing the customer order number
received, the sales order number and lines generated, and any related and
pertinent remarks.
EDI User Guide

6-21
EDI procedure
Printing and sending the order acknowledgment

(855/ORDRSP)
Figure 71 shows the Print Order Acknowledgments/RMAs (tdsls4401m000)
session. This session prepares the outgoing Order Acknowledgment EDI
message. When you run this session the system verifies that the order(s) is
prepared for EDI and is stored in the Messages to be Generated (ecedi700) table.
Figure 71 Print Order Acknowledgment/RMAs (tdsls4401m000) session

requirements section in this chapter must be met in before a message can be
prepared for EDI. However, if any of the conditions are not met, the hard copy of
the order acknowledgment will still be printed. This hard copy can also be
printed when the previous conditions are met if the Print check box in the EDI
Messages Supported by Business Partner (ecedi0111m000) session is checked. If
a hard copy of the order acknowledgment is printed for an order which has also
been prepared for EDI, the words EDI Copy will appear on the upper left-hand
corner of the printed order acknowledgment document.
NOTE
EDI User Guide

6-22
The order type of the sales order must be defined in the Conversion of Sales
Order Types Out (ecedi4132m000) session in order for the acknowledgment to
be prepared for EDI; and, the Code in Message for the order type conversion
must match the order type specified in the EDI Messages Supported by Business
EDI procedure
Using Acknowledgment Codes

Optionally, you may choose to include acknowledgment codes on your sales
order to indicate to your customer your reaction to the received order or order
change. Once assigned to the sales order, the acknowledgement code may be
included in the outgoing order acknowledgment message. To use
acknowledgment codes within sales control, you must select the Prompt for
Change Codes check box in the Sales Order Parameters (tdsls0100s400) session.
Acknowledgment Codes may be manually assigned to the sales order when
changes are made to the order. Alternatively, acknowledgment codes may be
automatically assigned to the sales order whenever sales order lines are changed
or added based on the data defined in the Sales Acknowledgment Code
Assignments (tdsls0155m000) session.
Acknowledging by Exception
In some cases, your customer may wish to receive an acknowledgment only if
you have made specific changes to the customers order. For example, the
customer may only wish to be notified with an acknowledgment if the item,
price, quantity or delivery date are changed, and is disinterested in receiving
notification of any other changes. If this is the case, you should set up your
customer (sold-to business partner) to be Acknowledged by Exception. You can
accomplish this by checking the Acknowledge By Exception check box in the
Sold-To Business Partner (tccom4110s000) session. If your customer is set up to
be Acknowledged by Exception, only those order lines with an assigned
acknowledgment code will be recognized as changed or new. This allows you to
use the acknowledgment codes to identify those changes that you wish to convey
to your business partner. If an acknowledgment code is assigned to a changed or
new line, the line is recognized as new or changed, respectively.
If no acknowledgment code is assigned to the sales order lines when changes are
made to the order, the lines are not recognized as new or changed.
In this case, when running the Print Order Acknowledgments (tdsls4401m000)
session, set the Order Line Types to Print field to one of the following to ensure
that only those lines with assigned acknowledgment codes are included in the
message:
n
New and Changed Lines, to pick up only changed and new lines (only those
lines with assigned acknowledgement codes)
Only Changed Lines, to include changed lines only
Exclude Printed Lines, to include new lines only
EDI User Guide

6-23
EDI procedure
Once prepared, and if not using the interchange controller to automate the EDI
processing of files, you can manually generate the outgoing message using one
of the following methods (see the Sending the purchase order (850/ORDERS)
section in Chapter 6):
n
Run the Generate EDI Messages (ecedi7201m000) session.
Run the Direct Network Communication (ecedi7205m000), if the network is

designated to generate messages during direct network communication.
As with all outgoing messages, a report is generated showing which EDI

messages have been generated. If an external EDI business partner, the outgoing
messages (ASCII files) are placed in the Appl_from directory under the directory
specified for the network, from which the translation/communication software
will retrieve them. See Chapter 7 for information about generating messages for
internal EDI business partners.
Receiving the sales order change (860/ORDCHG)

To receive in the customers purchase order change, use the Direct Network
Communication (ecedi7205m000) session. You cannot start this process until the
following has occurred:
n
You receive the customer purchase order change (860/ORDCHG) from your
customer.
The translation/communication software has translated the ASCII files from

their standard format into the file format defined by your conversion setups
and has placed the file(s) in the appropriate appl_to directory.
The received order change updates the sales order.

All received order lines in an incoming order change message must include a
change type code. The change type codes, passed in the incoming message, are
validated against the change type codes defined in the Change Types
(tdsls0198m000) session in Sales Control. These change type codes govern the
type of change action that will be processed against the sales order (for example:
add line, change line, delete line, replace line, cancel line, cancel order, change
order header).
EDI User Guide

6-24
EDI procedure
In order to receive sales order changes through EDI, you must be using change
codes within Sales Control. In order to use change codes within Sales Control,
the Prompt for Change Codes check box in the Sales Order Parameters
(tdsls1000s400) session must be checked.
If one of the conditions listed in General procedures: purchasing company in
Chapter 6, is not met, the message will not be read.
As with all incoming messages, the Direct Network Communication
(ecedi7205m000) session generates the Remarks in Copied Messages report to
show which order and order lines were updated, along with any related and
pertinent remarks, if the order change is successfully processed.
Printing and sending the order change acknowledgment

(865)
Use the Print Order Acknowledgment (tdsls4401m000) session to prepare the
outgoing Order Change Acknowledgment EDI message. Acknowledgments sent
in response to sales order changes (changes received or made internally), may
take the form of an order acknowledgment (855/ORDRSP) or an order change
acknowledgment (865).
The EDI Order Change Response field defined in the Sold-To Business Partner
(tccom4110s000) session determines whether the order acknowledgment
(855/ORDRSP) or the order change acknowledgment (865) is generated in
response to sales order changes made after the original order acknowledgment is
sent.
EDI User Guide

6-25
EDI procedure
Figure 72 Print Order Acknowledgments/RMAs (tdsls4401m000) session
If you want to include only new and changed lines that have been added or
modified since the last order acknowledgment generation, set the Order Line
Types to Print field to one of the following three values when running the Print
Order Acknowledgments (tdsls4401m000) session:
n
n
n
NOTE
EDI User Guide

6-26
New and Changed Lines, to include changed and new lines only
Only Changed Lines, to include changed lines only
Exclude Printed Lines, to include new lines only
If your customer is set up to be Acknowledged by Exception, only those order

lines with an assigned acknowledgment code will be recognized as changed or
new. See the printing and sending the order acknowledgement (855/ORDRSP)
section in Chapter 6, for more information regarding the use of acknowledgment
codes and acknowledging by exception.
EDI procedure

the order acknowledgment will still be printed. This hard copy can also be
printed when the previous conditions are met if the Print check box in the EDI
Messages Supported by Business Partner (ecedi0111m000) session is checked. If
a hard copy of the order acknowledgment is printed for an order which has also
corner of the printed order acknowledgment document.
NOTE
The order type of the sales order must be defined in the Conversion of Sales
Order Types Out (ecedi4132m000) session in order for the acknowledgment to
be prepared for EDI; and, the Code in Message for the order type conversion
must match the order type specified in the EDI Messages Supported by Business
Once prepared, and if not using the interchange controller to automate the EDI
processing of files, you can generate the outgoing EDI message using one of the
following methods (see the Sending the purchase order (850/ORDERS) section
in Chapter 6):
n
Use the Generate EDI Messages (ecedi7201m000) session.
Run direct network communication, if the network is designated to generate

messages during direct network communication.
As with all outgoing messages, a report is generated showing which EDI

messages have been generated; If an external EDI business partner, the outgoing
EDI messages (ASCII files) are placed in the Appl_from directory under the
directory specified for the network, from which the translation/communication
software will retrieve them.
See Chapter 7 for information about generating messages for internal EDI
business partners.
EDI User Guide

6-27
EDI procedure
Receiving the Customer Schedule Release (830/DELFOR,

862/DELFOR, 866/DELJIT)
If your customer (sold-to business partner) chooses to convey his purchase
requirements to you using schedule releases, the following three types of
schedule releases may be received:
n
Planning Release (830/DELFOR) which conveys material requirement

information.
Shipping Release (862/DELFOR) which is intended to supplement the

Planning Release. This document may contain precise shipping release
requirements sent on a more frequent basis than the Planning Release.
Sequenced Shipping Release, which is intended to supplement the Shipping

Release, but may follow a Planning Release directly. This document specifies
precise information pertaining to the delivery of goods, which includes the
order in which goods are to arrive at their destination(s), or are to be unloaded
from the conveyance method when received at their destination(s).
Receiving the Planning Release (830/DELFOR):

Run the Direct Network Communication (ecedi7205m000) session to receive the
customer Planning Release (830/DELFOR in). You may receive a new Planning
Release or an update to an existing Planning Release. Updates are indicated by a
new revision. If a new Planning Release is received, a Planning Release and
corresponding schedule(s) are created within Sales Control in your Baan
company; if an update to an existing Planning Release is received, the sales
Planning Release is updated with a new revision, and the corresponding
schedules are updated with a new revision as well. If the update includes a new
item, a new sales schedule may be created and linked to the updated Planning
Release.
As with all incoming EDI messages, the Remarks in Copied Messages report is
generated, indicating the sales release number and corresponding lines added,
along with any related and pertinent remarks.
Receiving the Shipping Release (862/DELFOR):
customer Shipping Release (862/DELFOR in). You may receive a new Shipping
Release or an update to an existing Shipping Release. Updates are indicated by a
new revision. If a new Shipping Release is received, a sales Shipping Release
and corresponding sales schedule(s) are created in your Baan company. If an
update to an existing Shipping Release is received, the sales Shipping Release is
updated with a new revision, and the corresponding sales schedules are updated
with a new revision as well.
EDI User Guide

6-28
EDI procedure
generated, indicating the sales release number and corresponding line added,
Receiving the Sequenced Shipping Release (866/DELJIT):
customer Sequenced Shipping Release (866/DELJIT in). You may receive a new
Sequenced Shipping Release or an update to an existing Sequenced Shipping
Release. Updates are indicated by a new revision. If a new Sequenced Shipping
Release is received, a sales Sequenced Shipping is created in your Baan
company, and the production sequence information is stored as Production
Sequence Information (whinh420) within the Warehousing package. If an update
to an existing Shipping Release is received, the sales Shipping Release is updated
with a new revision.
A Sequenced Shipping Release must reference an existing Planning Release or
Shipping Release. Each line of the Sequenced Shipping Release references an
existing schedule release line, and for that line includes the production
sequencing information. The production sequence information is printed on the
packing slip using the Print Packing Slip (whinh4475m000) session.
generated, indicating the sales release number and corresponding line added,
NOTE
Prior to receiving any of the Sales Schedule Release messages (planning release,
shipping release or sequenced shipping release), the following data must be
defined within your Baan company:
n
A Segment Set and Period Table Code must be defined using the Item
Customer Information (tdisa0510m000) session.
Because the Schedule Quantity Type and Schedule Type fields are required
on the Sales Releases, and must be specified in the incoming Sales Planning
Release (830/DELFOR), you should set up conversion codes for these
enumerated values using the Conversion of Schedule Quantity Types/In
(ecedi3152m000) and Conversion of Schedule Types/In (ecedi3151m000)
sessions, respectively.
EDI User Guide

6-29
EDI procedure
Sending the Shipment Notice (856/DESADV)

The Confirm Shipments (whinh4275m000) session (see Figure 73) prepares the
outgoing Shipment Notice (856/DESADV) and sets the shipments EDI Status to
Confirmed if the Generate ASNs Automatically check box defined in the
Warehouse Parameters (whinh0100s000) session is checked. This session
represents only one of the ways by which a shipment can become confirmed. The
exact means by which a shipment becomes confirmed depends on the procedures
of your company and the procedure steps associated with the shipment.
Confirmed Shipments that are not intended for EDI transmission have a status of
Scheduled.
Figure 73 Confirm Shipments Loads (whinh4275m000) session
On the other hand, if the Generate ASNs Automatically check box defined in the
Warehouse Parameters (whinh0100s000) session is not selected, the shipments
EDI Status is Prepare when the shipment is confirmed. In this case, you must run
the Confirm ASN (whinh4532m000) session to prepare the outgoing Shipment
Notice (856/DESADV) EDI message. The shipments EDI Status is Confirmed
when the EDI message is prepared.
EDI User Guide

6-30
EDI procedure
Figure 74 Confirm ASN (whinh4532m000) session
Figure 75 Shipments (whinh4130m000) session
EDI User Guide

6-31
EDI procedure
message to be generated during the next Direct Network Communication, you
can delete the message from this session.
retrieve them.
NOTE
In order to support the requirements of some EDI standards, Baan EDI supports
the transmission of two kinds of Shipment Notices, a canceling Shipment Notice,
and an original Shipment Notice. A canceling Shipment Notice is intended to
cancel a previously sent erroneous Shipment Notice. The shipments EDI Status
field may be used to indicate to the recipient of the message which type of
Shipment Notice is intended. To utilize this feature, use the Conversion of
Shipment Status Codes Out (ecedi4180m000) session to define codes to include
in the message indicating if the Shipment Notice is an original or a canceling
message. If the shipments EDI status is Confirmed, the Shipment Notice is
considered to be an original message; therefore, if the shipments EDI Status
field is Confirmed at the time the outgoing message is generated, the conversion
code associated with the original value in the Conversion of Shipment Status
Codes Out will be included the outgoing Shipment Notice message. If the
shipments EDI Status is Disapproved, the Shipment Notice is considered to be a
canceling message, and the conversion code associated with the canceled value is
included in the outgoing message. See the Receiving the Error Notification
(824/APERAK) in Chapter 6 for more information on the shipments
disapproved status.
Receiving the Error Notification (824/APERAK)

Once you have received the Error Notification (824/APERAK) from your
customer (ship-to business partner), and the message (ASCII) files have been
placed in the appropriate appl_to directory by the translation/communication
software, use the Direct Network Communication (ecedi7205m000) session to
receive in the Error Notification message. An incoming Error Notification is
associated with a shipment for which an invalid Shipment Notice was originally
sent, and reports application errors that occurred when your business partner tried
to process the previously sent Shipment Notice.
EDI User Guide

6-32
EDI procedure
When the Error Notification is received, the following occurs:

n
The shipment for which the Error Notification was received is Disapproved.
The Remarks in Copied Message report is generated, showing the shipment

notice number against which the Error Notification message was received,
and any related and pertinent remarks.
Optionally, the EDI Information field on the shipment header may be updated
with the contents of the Error Notification message.
The Shipment Notice referenced in the received Error Notification message,

is automatically prepared for EDI transmission (856/DESADV out).
As with all prepared outgoing messages, you can verify that the outgoing
message was prepared for EDI using the Messages to be Generated
(ecedi7100m000) session. If you do not want the message to be generated the
next time the Direct Network Communication session is run, you can delete the
message from this session.
Resending Canceling and Corrected Shipment Notices in Response to
received Error Notifications
If you wish to send a canceling Shipment Notice to your customer, use the Direct
Network Communication (ecedi7205m000), if the network is setup to generate
messages upon Direct Network Communication, or the Generate EDI Messages
(ecedi7201m000) to manually generate the outgoing message. When the
outgoing canceling Shipment Notice is generated, the shipments EDI Status
field is Modify, indicating that the shipment should be modified to correct the
erroneous data, and resent to your business partner.
NOTE
In order to support the requirements of some EDI standards, Baan EDI supports
the transmission of two kinds of Shipment Notices, a canceling Shipment Notice,
and an original Shipment Notice. A canceling Shipment Notice is intended to
cancel a previously sent erroneous Shipment Notice. To utilize this feature, use
the Conversion of Shipment Status Codes Out (ecedi4180m000) session to
define codes to include in the message indicating if the Shipment Notice is an
original or a canceling message. If the shipments EDI status is Confirmed, the
Shipment Notice is considered to be an original message; if the shipments EDI
Status is Disapproved, the Shipment Notice is considered to be a canceling
message.
EDI User Guide

6-33
EDI procedure
Optionally, if the shipments EDI status is Modify, you may correct the reported
errors by correcting the shipments date/time, quantity or weight and any other
EDI data included on the original Shipment Notice, and resend the corrected
Shipment Notice to your business partner. To resend the corrected Shipment
Notice, use the Confirm ASN (whinh4532m000) session to prepare the corrected
Shipment Notice (856/DESADV) for transmission; preparing the outgoing
Shipment Notice sets the shipments EDI Status to Confirmed. Run the Direct
Network Communication (ecedi7205m000), if the network is setup to generate
messages upon Direct Network Communication, or the Generate EDI Messages
(ecedi7201m000) to manually generate the outgoing message. For external EDI,
the outgoing message (ASCII) files are placed in the appl_from directory, under
the networks directory, from which the translation/communication software will
retrieve them.
Receiving the Receipt Discrepancy Notification

(861/RECADV)
Once you have received the Receipt Discrepancy Notification (861/RECADV)
from your customer (ship-to business partner), and the message (ASCII) files
have been placed in the appropriate appl_to directory by the
translation/communication software, use the Direct Network Communication
(ecedi7205m000) session to manually receive the Receipt Discrepancy
Notification message. This message indicates that your business partner may
have found a discrepancy between the quantity of goods indicated on the
Shipment Notice that you previously sent him, and the quantity of goods actually
received.
When the Direct Network Communication receives the Receipt Discrepancy
Notification message, the EDI Information field at the shipment header and the
shipment lines text field are updated with the received discrepancy data (see the
conversion setup definitions in Appendix A for more information), and the
following report is generated.
n
EDI User Guide

6-34
Discrepancies Between Shipments and Business Partner Receipts

This report compares the values included in the Receipt Discrepancy message
to the shipment data and reports any discrepancies the differences between
the values, and any text that is included.
EDI procedure
Sending the sales invoice (810/INVOIC)

After shipping the ordered goods, run the Compose/Print/Post Invoices
(cisli2200m000) session. This session prepares the Invoice (810/INVOIC out)
for EDI transmission when the invoice is composed.
the invoice will still be printed if the print option is selected. This hard copy can
also be printed when the previous conditions are met if the Print check box in the
EDI Messages Supported by Business Partner (ecedi0111m000) session is
checked. If a hard copy of the invoice is printed for an invoice, which has also
corner of the printed invoice document. You can verify that the outgoing
message was prepared for EDI, using the Messages to be Generated
(ecedi7100m000) session.
NOTE
The order type of the sales order for which the invoice is generated must be
defined in the Conversion of Sales Order Types Out (ecedi4132m000) session in
order for the invoice to be prepared for EDI; and, the Code in Message for the
order type conversion must match the order type specified in the EDI Messages
Supported by Business Partner (ecedi0111s000) session for this message and
business partner.
Run the Direct Network Communication (ecedi7205m000), if the network is
setup to generate messages upon Direct Network Communication, or the
Generate EDI Messages (ecedi7201m000) session to manually generate the
outgoing message. As with all outgoing messages, a report is generated showing
which EDI messages have been generated; for external EDI, messages (ASCII
files) are placed in the Appl_from directory in the directory specified for the
network, from which the translation/communication software will retrieve them.
Receiving the Remittance Advice (820/REMADV)

the Remittance Advice message (820/REMADV) from your customer (pay-by
business partner), once the ASCII files have been placed in the appropriate
appl_to directory by your translation/communication software.
When the Direct Network Communication receives the Remittance Advice
message (820/REMADV), a remittance advice message (receipt) is created in
your Baan company, and the Remarks in Copied Messages report is generated,
showing the document number(s) generated, along with any pertinent remarks.
EDI User Guide

6-35
EDI procedure
You can use the Remittance Advice Messages (Receipts) (tfcmg5501m000)

session to review the received information.
This concludes an example of a normal order cycle, using the EDI messages
supported by Baan EDI, when you are exchanging EDI documents with a
customer. However, the orders still need to be closed.
To automate the execution of the Direct Network Communication
(ecedi7205m000) session, see the EDI interchange controller section in
Chapter 4.
The sales or purchasing company

Receiving Functional Acknowledgments (997) / Outgoing
Message Status Updates (STATUS)
There is one final EDI message that may be used by both the selling and
purchasing companies using external EDI. It allows the
translation/communication application to communicate to your Baan company
the processing status of outgoing messages, which may then be visible in Baan
EDIs History of Outgoing (Generated) Messages.
This incoming message may be an incoming functional acknowledgment (for
example, ANSI X12 997) received from your business partners
translation/communication software, indicating the acceptance or rejection of a
previously sent EDI message; or, it may be used as a mechanism for your
translation/communication software application to communicate to your Baan
company, the translation and transmission status of a previously generated,
outgoing message. In either case, the status of the outgoing message is visible in
the Send Status field of the History of Generated Messages session and report
(ecedi7501m000 and ecedi7401m000, respectively).
NOTE
EDI User Guide

6-36
This applies to external EDI only. For internal EDI (multisite), Baan EDI handles
the setting of the processing status of outgoing messages.
EDI procedure
When Baan EDI generates an outgoing message for external EDI and creates the
message ASCII files in the appropriate directory, the Send Status is Generated.
Following are the additional values of the Send Status of the outgoing messages
that may be updated with the receipt of this message:
n
Translated, (Indicates that the outgoing EDI message has been read by your
translation/communication application and translated into the standard EDI
format)
Translation Failed, (Indicates that your translation/communication software

application has attempted to read and translate the outgoing EDI message into
the standard EDI format, and the translation has failed)
Sent, (Indicates that the outgoing EDI message has been translated and
transmitted across the network)
Send Failed (Indicates that the outgoing EDI message has been translated, but
that the transmission of the message across the network has failed)
Read by B. P. (Indicates that the outgoing EDI message has been translated
and transmitted across the network, and that a functional acknowledgement
has been received from the recipient of the message, indicating that the
message has been successfully received and translated at your business
partners site)
Rejected by B. P. (Indicates that the outgoing EDI message has been

translated and transmitted across the network, and that a functional
acknowledgement has been received from the recipient of the message,
indicating that the message has been successfully received at your business
partners site but was not able to be successfully read and translated)
For simplicity, two Baan EDI messages have been provided to update the
processing status of outgoing messages: the STATUS message, and the 997
message. The STATUS message may be used to update the Send Status of the
outgoing message in all cases, in which case you need only this message.
Alternatively, you may use the 997 message when a functional acknowledgement
(997) is received (at which time the Send Status can be Read by B. P. or Rejected
by B. P) and the STATUS message to update the Send Status with the translation
and transmission status maintained by your translation/communication software
application. See Appendix A for more information.
EDI User Guide

6-37
EDI procedure
You may use the Message Status Codes (ecedi2185m000) session to define
codes that correspond to the various EDI Send Status values; some codes have
been provided in your default data (see the EDI default data section in Chapter 2
for more information on EDI default data). Your translation/communication
application may use these codes in the message to indicate the appropriate status.
You may also have additional information written to the EDI Information field
(such as specific error codes or descriptions) stored in the EDI history, and
reported in the History of Generated Message (ecedi7401m000) report.
EDI User Guide

6-38
Internal (multisite) EDI
Introduction
As stated in earlier chapters, the Baan EDI module can generate and read ASCII
files with a flexible format. In external EDI, these ASCII files must be
transferred over commercial or noncommercial networks. This requires
translation of the ASCII files to and from standardized encrypted messages, to
ensure high data integrity and security, and to provide a universal format
supported by all parties.
However, in multisite EDI implementations (also referred to as internal EDI), the
ASCII files are transferred over the internal company network (LAN or WAN),
which means that encryption is not required. Also, because all companies in the
multisite structure use the same format for the ASCII files, translation to an
external EDI standard, such as EDIFACT or ANSI X12, is not required.
Internal EDI can only be accomplished between sites (companies) that share a
common directory on the company network (either by using the same data
server, or through NFS). In addition, all sites must use the same application
server, to allow site A (company 570) to start a background process in site B
(575) that reads messages just sent from A to B, for example. If this real-time
transfer of messages is not required, the transfer of internal EDI messages is
similar to an external EDI situation, with the exception of the translation and
communication software.
EDI User Guide

7-1
Translation
Translation
ASCII
External
EDI relation
EDI Format
ASCII
ASCII
ASCII
Affliliated
company A
Affiliated
company B
ASCII
Figure 76 External and internal EDI
All messages explained in previous chapters, except for the Status Update of
Outgoing Messages message (997/STATUS) and the Remittance Advice
message (820/REMADV) are available for use in a multisite environment:
For the purchasing company:
n
n
n
n
n
n
n
n
n
n
n
EDI User Guide

7-2
Sales Order (850/ORDERS), direction out

Sales Order Acknowledgment (855/ORDRSP) direction in
Purchase Order Change Acknowledgment (865), direction in
Shipping Notice (856/DESADV), direction in
For the sales company:

n
n
n
n
n
n
n
n
n
n
n
Sales Order (850/ORDERS), direction in

Sales Order Acknowledgment (855/ORDRSP), direction out
Purchase Order Change Acknowledgment (865) direction out
Shipping Notice (856/DESADV), direction out
Error Notification (824/APERAK), direction in
Receipt Discrepancy Notification (861/RECADV), direction in
Sales Invoice (810/INVOIC), direction out
This chapter provides setup and procedures for the purchasing and sales
companies. When setup or procedure is the same as external EDI, you will be
referred to the appropriate section.
General setup
In this chapter, two companies, 570 and 575, will be referred to in examples.
Company 570 purchases from 575.
Company data
In company 570, 575 must be defined as a business partner (for example, buyfrom, ship-from, invoice-from); in 575, company 570 must be defined as a
business partner (for example, sold-to, ship-to, invoice-to). In addition, the
business partners must be defined as affiliated companies. This requires the
presence of both company numbers in the Companies (tccom000) table of each
company. This can be accomplished in one of two ways:
1
Add the missing company and related data in the tccom000 table of both
companies with the Table Manager. The Company Data (tccom0500m000)
session only allows you to edit the data of the current company.
Share tccom000 between the two companies, with the data of both companies
present in the table.
Use the Logical Tables (ttaad4120m000) session to share the data between
the two companies. This can be done in either company.
EDI User Guide

7-3
Business Partner data

In order to transfer goods using purchase orders and sales orders, both companies
must identify each other as the appropriate business partners. Although you can
use any business partner code, using the company number is recommended.
In the purchasing company (company 570), set up the business partner data for
company 575 from whom you wish to purchase goods.
Figure 77 Business Partners (tccom4500m000) session
Figure 78 Business Partners (tccom4100s000)session, General
EDI User Guide

7-4
Figure 79 Business Partner (Detailed)
The Affiliated Company No. field determines whether the business partner is a
multisite related company.
In the selling company (company 575), you need to define the business partner
representing the purchasing company 570, to whom you wish to sell goods.
Figure 80 Business Partner (tccom4500m000)
EDI User Guide

7-5
Figure 81 Business Partner (tccom4100s000) session, General
Figure 82 Business Partner (tccom4100s000) session, Detailed
EDI User Guide

7-6
Parameters
See the Parameters section in Chapter 2, for information on setting the EDI
parameters.
Default EDI data

See the EDI default data section in Chapter 2, for information on exporting and
importing default EDI data.
Networks
Because data for internal business partners does not need to be translated into
actual EDI messages, internal EDI data should be separated from external EDI
data by defining a separate network. All multisite companies, among which EDI
messages are to be traded, must share the same network path (directory).
Figure 83 Networks (ecedi0520m000) session
EDI User Guide

7-7
Figure 84 Networks (ecedi0120s000) session
See the Networks section in Chapter 2, for information on networks for external
EDI data. The following fields relate directly to a multisite environment:
EDI User Guide

7-8
Field
Explanation
Multicompany
Indicates if this company is used for internal (multisite)

EDI. If this field is Yes, the system will create the
appropriate subdirectories.
Automatically Read In
Generated Message
Indicate if you want the system to automatically start

the Direct Network Communication in the receiving
company to read in and process the message after
sending a message to that company.
When you save the network definition, the subdirectories are created under the
specified path. However, for internal EDI the subdirectories are not the same as
those created for external EDI.
Subdirectory
Description
appl_comm
The directory where all generated and received EDI

messages are stored.
appl_text
If a message contains any text fields, this directory contains

temporary files that are used to build up the text blocks.
appl_trace
This directory contains the created log (trace) files.
command
This directory is used by the system for semaphores. The

semaphore, or flagging, mechanism is used to indicate
whether a process is active or can be activated. For example,
when messages are read in company 570, a semaphore
named multicmp.570 will be placed in the command directory.
This indicates to other companies that they cannot place any
new messages in the appl_comm/c570 directory for the
duration of the process.
See the External EDI network communication section in
Chapter 4, for additional information about semaphores.
store_send
This is where sent messages are archived based on EDI

parameter settings.
store_recv
This is where received messages are archived based on EDI

parameter settings.
For each company in which you define the same network with the same path, a
subdirectory is created under the Appl directories with the name cXXX (where
XXX is the company number). For example, purchase orders sent from any
company to 575 are placed in the directory Appl_comm/c575. Therefore, with
internal EDI/multisite networks, you do not have to use the company number
when specifying the directory path for the network, because Baan creates the
appropriate company numbers. For more detailed information, see Chapter 2.

See the Business partner data by network section in Chapter 2, for information on
defining Business partner data by network.

For detailed information on code and conversion tables, see the Code and
conversion tables section in Chapter 2.
EDI User Guide

7-9
Purchasing company setup

For additional information, see the Code conversions and Additional parameters
sections in Chapter 3.
You need to determine which purchasing documents you want to exchange with
your supplier. In this case, your supplier is another company in your multisite
environment. The available purchasing documents include:
n
n
n
n
n
n
n
n
n
n
n
Sales Order (850/ORDERS), direction out

Sales Order Acknowledgment (855/ORDRSP) direction in
Purchase Order Change Acknowledgment (865), direction in
Shipping Notice (856/DESADV), direction in
In your purchasing company (company 570), you can set up each of the
messages above for the business partner representing your selling company,
business partner 575, using the EDI Message Supported by Business Partner
(ecedi0511m000) session, as shown in Figure 85. In each case, you need to
specify your multisite network, MSNET as defined in this example.
Figure 85 EDI Messages Supported by Business Partner (ecedi0511m000) session
EDI User Guide

7-10
Figure 86 EDI Messages Supported by Business Partner (ecedi0111s000) session
For more information and examples of how to set up each message type, see the
EDI messages supported by business partner section in Chapter 3.
EDI User Guide

7-11
Sales company setup

For more detailed information on Sales company setup, see the Code conversions
and Additional parameters sections in the Sales company section in Chapter 3.
You need to determine which selling documents you want to exchange with your
customer. In this case, your customer is another company in your multisite
environment. The available selling documents include:
n
n
n
n
n
n
n
n
n
n
n
Sales Orders (850/ORDERS),direction in

Purchase Order Acknowledgment (855/ORDRSP), direction out
Purchase Order Change Acknowledgment (865), direction out
Shipping Notice (Standard) (856/DESADV), direction out
Error Notification (824/APERAK), direction in
Receipt Discrepancy Notification (861,RECADV), direction in
Sales Invoice (810/INVOIC), direction out
In your selling company (company 575), you can set up each of the messages
above for the business partner representing your purchasing company, business
partner 570, using the EDI Message Supported by Business Partner
(ecedi0511m000) session, as shown in Figure 87. In each case, you need to
specify your multisite network, MSNET as defined in this example.
Figure 87 EDI Messages Supported by Business Partner (ecedi0511m000) session
EDI User Guide

7-12
Figure 88 EDI Messages Supported by Business Partner (ecedi0111s000) session
Figure 89 EDI Messages Supported by Business Partner, Series/Conversions (ecedi0111s000)

session
EDI User Guide

7-13
For more information and examples of how to set up each message type, see the
EDI messages supported by business partner section in Chapter 3.
Setup summary
If the two companies supply each other, the following applies:
n
In each company, the company with whom documents are to be exchanged

must be defined as a business partner affiliated to that company.
In both companies, the Order Types table must be filled for all message types
that will be received in that company.
In both companies, the Conversion of Order Types (Out) table must be filled
for the message types pertaining to a single order. This includes outgoing
purchase orders (850/ORDERS out), purchase order changes (860/ORDCHG
out), sales order acknowledgements (855/ORDRSP out), sales order change
acknowledgements (865 out), and invoices (810/INVOIC out).
In both companies, all appropriate EDI messages supported by business

partner must be defined for directions in and out.
Running EDI
For additional information about processing files and the EDI interchange
controller, see the Processing files and EDI interchange controllersections in
Chapter 4.
Multisite network communication

When implementing the interchange controller in multisite situations, make sure
that the connect times of the intercompany network in the individual companies
are not simultaneous.
Whenever the interchange controller initiates the Direct Network
Communication (ecedi7205m000) session, it uses a semaphore to indicate to
other sites that it is currently processing messages.
EDI User Guide

7-14
Figure 90 shows the use of semaphores during direct network communication

initiated by 575 for internal EDI. The second row indicates where the messages
for 575 and 570 are stored, and the location of the command directory, where the
semaphores are stored.
Company 654
../msnet/appl_com/c654
Network
../msnet/command
Company 653
../msnet/appl_comm/c653
Generate Messages
multicmp.653
ASCII files
Direct Network Communication

- Generate Messages
- Activate Read Batch
- Read Messages
multicmp.653
multicmp.653
multicmp.654
ASCII files
Read messages
Figure 90 Semaphores
You can send messages from 570 to 575 in either of the two ways described
below:
1
Use the Generate EDI Messages (ecedi7201m000) session.
This session checks for the presence of the multicmp.575 semaphore in

the command directory. If this semaphore is present, 575 is currently
reading messages.
Company 570 will wait until 575 removes the semaphore and, then,
generate the messages.
Company 570 places the multicmp.575 semaphore in the command

directory for the duration of message generation, to ensure that other
companies do not write to the same files at the same time and that 575
does not read partially finished files.
Use the Direct Network Communication (ecedi7205m000) session.
First, company 570 performs the activities described for the Generate EDI
Messages session.
Then it activates the Read Messages process in 575. This process places
the multicmp.575 semaphore in the command directory to ensure that
other sites do not modify the ASCII files.
When 575 is finished reading the ASCII files, the semaphore is removed.
Next, company 570 continues to read its own messages, which places the
multicmp.570 semaphore in the command directory for the duration of the
read process.
EDI User Guide

7-15
The interaction between the two companies explains the importance of activating
the interchange controllers in the individual companies at sequenced intervals.
For example:
Connect Times
Company 570
Company 575
06:00 AM
07:00 AM
12:00 PM
13:00 PM
18:00 PM
19:00 PM
EDI procedure (standard plus GLO)

Based on the network definition, messages generated from the sending company
may be automatically read by the receiving company with no action to activate
the reading of the message on the receiving side. If the Automatically Read in
Generated Messages check box is checked on the senders network definition,
the receiving side does not need to run the Direct Network Communication
(ecedi7205m000) session to read in the messages generated by the sender.
For a comprehensive explanation about the procedures for purchasing companies
and sales companies, see Chapter 6.
EDI User Guide

7-16
Appendix A: Conversion setups
Overview
Conversion setups define the file layout of the ASCII files received into and
generated from Baan EDI for your EDI messages. They define the mapping
relationship between the ASCII file fields and the Baan application fields, and
the rules for each fields validation and translation (conversion).
The fields of the conversion setups are grouped into levels. Levels represent
different records within the conversion setup structure. These levels may be
distributed over multiple ASCII files (a multifile format) or to a single file (a
single file format). For the multifile format, each level is written to a unique
ASCII file. For the single file format, all levels for a specific conversion setup
are written to a single file where each level is identified with a unique level
identifier. In addition, conversion setup fields may have a delimited or a fixed
length. The default conversion setups supplied by Baan use a delimited structure.
EDI User Guide

8-1
Figure 91 shows a simplified example of the structure of a Baan EDI message. In

this example, the various segments (for example, message header and body) are
distributed over several ASCII files. This is known as a multifile format.
File 1: Message Envelope
19980224000001|570|GCV000355|GCV|X12|850|NE||980224|0126
File 2: Order Header
19980224000001|570|GCV000355|971201234900|971202050000|971202050000||||F.O.B.|
Free on Board|||||NORMAL|Jans Term of Payment |30|10|10|Dutch|Nether||||0|JOHAN|testid||
TINA|testid|BuyFm|ship|testid|ShpFm|inv|testid|InvFm|pay|testid|PayTo|CWAR|testid|ShpTo|2
File 3: Order Header Address
19980224000001|570|GCV000355|ShpTo|U.S.A|Ship-To Business Partner||2350
Mission College Blvd||Santa Clara||95054|CA||||95054|Suite 1200|P.O. 1200|123-45-6789
File 4: Order Header Text
19980224000001|570|GCV000355|Special Order for Baan
File 5: Order Line Detail
19980224000001|570|GCV000355|10|0||BP|vinod|
GCV10|Product Description||11|
971201234900|971202050000|971202050000|PCS|1.11|PCS|0|0|0|0|0||||||||gross|gross|gross|
gross|gross|0|0|0|0|0|Any Lot|||||0|0|0||||ship|testid|ShpFm|CWAR|testid|ShpTo|
Figure 91 Sample Message Structure
The decoding of the message structure is fairly straightforward. Each field has a
definition that is contained in the appropriate conversion setup. For example, to
decode the envelope level (file 1 in Figure 91), you can see that there are a total
of 10 fields within the record. Each field is delimited by a vertical bar [ | ]. Of the
ten possible fields, only 9 are actually populated (field 8 is empty).
The actual field definitions are as follows:
EDI User Guide

8-2
The envelope or overhead level identifies the transaction being transmitted.

The envelope contains a unique reference number that identifies the message
(field 1). This code is generated at the time the message is created, based on
EDI parameter settings. The transmitting business partner identifier is next.
This identifies the internal representation of the sending entity (company).
The order number is the next field in the envelope level. This represents the
transmitting companys internal order number. The fourth field contains the
receiving business partners code based on the transmitting organizations
identification structure for business partners.
The organization code that is used to determine what coding technique and
message structure is applied comes next. It is a mechanism within Baan EDI
that allows grouping by standards such as ANSI X12 or EDIFACT. The next
field is the message code that is used to determine the structure of the data
file exported from or imported into Baan EDI.
In the example shown, the field 8 is empty. Field 9 contains the transmission
date (including time, depending on the date format defined for your
organization) and the last field represents the transmission time, if you wish
to report this separately.
Each one of the files shown in Figure 91 could be similarly decoded.

Default conversion setups are provided for each supported message in the
Defaults.edi file which you imported earlier (see the EDI default data section in
Chapter 2). This takes care of the general mapping between the ASCII file and
the Baan application. This appendix includes the field definitions and the
relationship between the records of the messages provided as default data.
For external EDI, you will be exchanging EDI documents with your business
partners using an EDI standard such as the ANSI X12 standard. If you are
exchanging messages with external trading partners, your next step is to define
the mapping between the ASCII file and the EDI standard format in which you
will transmit or receive the message information with external trading partners.
This mapping to the EDI standard is usually handled in your EDI
translation/communication software. Use this appendix along with the Print
Mapping Information (ecedi5415m000) session to view the file layouts provided
for your EDI messages. This will report the file layout that you can use to map to
your translation/communication software for the corresponding message.
Conversion setups are provided for each supported message as part of the
Defaults.edi data for Baan ERP. This default data provides both a single file
layout and a multiple file layout (referred to as multifile) for each message. A
unique message code is created for each, where the single file version is suffixed
with an S. This way you may choose which file type (single file or multifile) you
wish to use for your EDI messages. The single file and multifile conversion
setups definitions are identical except that each record (level) of the single file
version is preceded by the Level Identifier, and thus all fields are offset by one
from the multifile definition; the definitions for the single and multifile are
otherwise identical. In addition, the default data provides the message codes
using both the ANSI X12 and UN/EDIFACT nomenclature.
EDI User Guide

8-3
The file structure of the ANSI X12 and the UN/EDIFACT versions are the same
within the Baan EDI default data. Which message code you choose to use for a
given message is up to you. In any case, the functionality and fields provided are
the same for a given message regardless of the default message code that you
choose.
The following table lists the message codes provided in the defaults.edi data.
Organization: X12 ANSI X12
Baan EDI
Message Code
EDI Standard Description
Baan Functional
Description
810
Invoice
Invoice (Multifile)
820
Payment Order/Remittance
Advice
Remittance Advice (Multifile)
824
Application Advice
Error Notification (Multifile)
830
Planning Schedule with

Release Capability
Planning Release (Multifile)
850
Purchase Order
Order (Multifile)
855
Purchase Order
Acknowledgment
Order Acknowledgment
(Multifile)
856
Ship Notice/Manifest
Shipment Notice (Multifile)
860

Request Buyer Initiated
Order Change (Multifile)
861
Receiving Advice/Acceptance Receipt Discrepancy

Certificate
Notification (Multifile)
862
Shipping Schedule
Shipping Release (Multifile)
865

Request/ Acknowledgment
Seller Initiated
Order Change
Acknowledgment (Multifile)
866
Production Sequence
Sequenced Shipping Release

(Multifile)
997
Functional Acknowledgment
(Multifile)
(Outgoing Message Status
Update)
EDI User Guide

8-4

Baan EDI
Message Code
Baan Functional Description
810S
Invoice
Invoice (Single file)
820S
Payment Order/ Remittance

Advice
Remittance Advice (Single

file)
824S
Application Advice
Error Notification (Single file)
830S
Planning Schedule with

Release Capability
Planning Release (Single file)
850S
Purchase Order
Order (Single file)
855S
Purchase Order
Acknowledgment
(Single file)
856S
Ship Notice/Manifest
Shipment Notice (Single file)
860S

Request Buyer Initiated
Order Change (Single file)
861S
Receiving Advice/Acceptance Receipt Discrepancy

Certificate
Notification (Single file)
862S
Shipping Schedule
Shipping Release (Single file)
865S

Request/ Acknowledgment
Seller Initiated
Order Change
Acknowledgment (Single file)
866S
Production Sequence

(Single file)
997S
(Multifile)
(Outgoing Message Status
Update)
STATUS
N/A
Outgoing Message Status

(Multifile)
EDI User Guide

8-5
Organization: EDI UN/EDIFACT
EDI User Guide

8-6

Baan EDI
Message Code
Baan Functional
Description
APERAK
Application Error and

Acknowledgment
Error Notification (Multifile)
APERAS
Application Error and

Acknowledgment
Error Notification (Single file)
DELF1S
Delivery Schedule
Planning Release (Single file)
DELF2S
Delivery Schedule
Shipping Release (Single file)
DELFR1
Delivery Schedule
Planning Release (Multifile)
DELFR2
Delivery Schedule
Shipping Release (Multifile)
DELJIS
Delivery Just-in-Time

(Single file)
DELJIT
Delivery Just-in-Time

(Multifile)
DESADS
Despatch Advice
Shipment Notice (Single file)
DESADV
Despatch Advice
Shipment Notice (Multifile)
INVOIC
Invoice
Invoice (Multifile)
INVOIS
Invoice
Invoice (Single file)
ORDCHG

Request
Order Change (Multifile)
ORDCHS

Request
Order Change (Single File)
ORDERS
Purchase Order
Order (Multifile)
ORDESS
Purchase Order
Order (Single File)
ORDRSP
Purchase Order Response
(Multifile)
ORDRSS
Purchase Order Response
(Single file)
RECADS
Receiving Advice
Receipt Discrepancy
Notification (Single file)
RECADV
Receiving Advice
Receipt Discrepancy
Notification (Multifile)
REMADS
Remittance Advice
Remittance Advice (Single

file)
REMADV
Remittance Advice
Remittance Advice (Multifile)
NOTE
Because the following information is subject to change, the Print EDI

Expressions (ecedi5405m000) and Print Mapping Information (ecedi5415m000)
sessions will provide you with current information about the conversion setups.
NOTE
The conversion setup definitions included in this appendix are the ANSI X12,
single file version, under organization X12. The definitions for the equivalent,
single file UN/EDIFACT messages are identical.
General notes
Code Conversions
All fields in which a conversion is indicated are defined within the conversion
setups to use the unconverted value without issuing an error if the conversion
does not exist.
Processing Address Information on Incoming Orders
The conversion setup definitions support processing specific address information
for the appropriate business partners, purchase and sales offices, and warehouses.
For incoming messages, the default address information associated with these
entities is used unless specific address information is received, in which case a
new address code is created for the specific address information and is assigned
to the internal document.
A note on incoming order addresses and outgoing shipment notices. If you
receive specific address information for the ship-to address on your order lines
(verses using the default address code for the ship-to business partner), a new
ship-to address code will be created and assigned to each order line. In this case,
when the outgoing Shipment Notice is created for the order, a unique shipment
notice will be created for each order line even if the ship-to business partner is
the same for each line. This is because shipment notices are grouped by the shipto address for which they are destined; and in this case, the ship-to address code
is unique per order line. On the other hand, if you use the ship-to business
partners default address code, the shipment notice will group the order lines and
create a unique shipment notice for each ship-to business partner. It is up to you
and your business partner to determine whether it is necessary to exchange the
specific address information or to use the default address information defined
within Baan for the ship-to business partner.
EDI User Guide

8-7
Processing Specific Address Information on Outgoing Messages

The evaluation expressions assigned to the specific address information fields of
the outgoing messages result in the following: In general, the specific address
information is always included in the outgoing message if the message is for an
external business partner (a business partner that is not set up to be a multisite, or
intercompany, business partner); on the other hand, if the business partner is a
multisite business partner, the specific address information is included in the
outgoing message only if the address code specified on the outgoing document
differs from the default address code for the corresponding business partner or
warehouse.
If you do not want to include the specific address information in an outgoing
message, you can modify the EDI Expression assigned to the address fields to an
expression that will evaluate to false (for example, add and 1 = 2 to the
expression).
See the field definition sections of the following messages and the EDI
expressions section in this chapter, for more information specific to individual
messages.
Date Fields
The Date Format field defined for the Organization governs the format that is
used to process date fields within Baan EDI.
EDI User Guide

8-8
Conversion setup: 810S, Invoices (Single file)

Message Envelope
Level 1
Mandatory
Key: F1, F2, F3, F4, F5
Invoice Header
Level 2
Mandatory
Key: F1, F2, F3, F4, F5
Order Header Text

Level 4
Optional / Repetitive
Key: F1, F2, F3, F4, F5
Specific Address
Level 3
Key: F1, F2, F3, F4, F5
Specific Address
Level 3
Key: F1, F2, F3, F4, 5
Tax Lines
Level 5
Key: F1, F2, F3, F4, F5
Order Lines
Level 6
Key: F1, F2, F3, F4, F5, F6, F7
Order Line Text

Level 7
Key: F1, F2, F3, F4, F5, F6, F7
Specific Delivery Address

Level 8
Optional
Key: F1, F2, F3, F4, F5, F6, F7
Legend:
Outgoing Key Fields:
F1: Message Reference
F2: Our Identification (Senders ID)
F3: Invoice Transaction Type
F4: Invoice Number
F5: Suppliers Order Number
F6: Order Line (Position) Number
F7: Order Line Sequence Number
Incoming Key Fields:

F2: Business Partners Network Address
F3:
F4: Suppliers Invoice Number
Figure 92 Record relationships, 810S
Figure 92 shows the relationship of the records in this message and the key fields
used to link the records. Each record of the message is identified by a level
number.

Message:
810S, X12 Sales Invoice
Organization: X12
Field type: Delimited
NOTE
Each level is shown in a separate table.
EDI User Guide

8-9
Conversion setup: Global Overhead (In)
Level: 1 Envelope - mandatory
Field name
Description
Pos
Length Conv.
ENV
Level Identifier
Identifies the record as

the Envelope record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as defined
in business partners
network address.
ecedi702.msno
Order Reference
20
Business partners
document number.
ecedi702.orga
Organization
The Baan EDI

organization.
ecedi702.mess
EDI Message
The Baan EDI message

code.
ecedi702.koor
Order Type in
Message
10
35
External reference of
order type (code in
message).
ecedi702.test
Test Message
11
Test indicator: If the

value in this field is nonblank and matches the
value defined for the
organization, the
message will be
processed as a test
message only (it will be
validated, any errors will
be reported, and the
message will be stored in
Saved Messages to be
Received).
ecedi702.send
Date Sent
12
22
The date/time the

message was sent.
EDI User Guide

8-10
EDI
expr.
Comments
Conversion setup: 810S (In)
Level: 2 Invoice Header- Mandatory
Field name
Description
Pos
Length Conv.
HDR
Level Identifier
Identifies the record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
tfacp200.ifbp
Business Partner
tfacp200.isup
Suppliers Invoice
Number.
20
tfacp200.orno
Order
tfacp200.ccrs
Late Payment
Surcharge
16
Late
Payment
Surcharges
tfacp200.cpay
Terms of Payment
18
Terms of
Payment
Codes
tfacp200.ccur
Currency
38
Currency
Codes
tfacp200.docd
Document Date
39
10
tfacp200.amnt
Amount
40
19
tfacp200.vati
Tax Amount in
Invoice Currency
45
19
Business
Partners
EDI Comments
expr.
Defaults from global

overhead records
business partner if
blank.
Purchase order number

being invoiced
EDI User Guide

8-11
Level: 4 Order header text - optional
Field name
Description
Pos
Length Conv.
HTX
Level Identifier

header text
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid Business Partner
Business Partners
identification as
defined in business
partners network
address
tfacp200.isup
Suppliers Invoice
Number
20
tfacp200.text
Text
80
Free form text
tfacp200.text
Text
80
Note: multiple text lines

may be received. Text
is read two fields per
record and may loop
multiple times.
EDI User Guide

8-12
EDI
expr.
Comments
Level: 5 Tax lines - optional
Field name
Description
Pos
Length Conv.
TAX
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
tfacp200.ifbp
Business Partner
Business partners
network address.
tfacp200.isup
Suppliers Invoice
No.
20
Business Partners
invoice number.
tfgld102.cvat
Tax Code
tfgld102.cvat
qual1
tfgld102.amnt
Amount
19
tfgld102.vamt
10
Tax Amount in
Payment Currency
EDI
expr.
Comments
Tax
Codes
Tax Code ID by which
to convert tax code.
Defaults to ZZ.
19
EDI User Guide

8-13
Level: 6 Order lines - Optional
Field name
Description
Pos
Length Conv.
LIN
Level Identifier

the invoice line
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid Business Partner
Business Partners
network address.
tfacp200.isup
20
Business Partners
invoice number.
tfacp240.pono Position
Position of purchase
order line being invoiced
tfacp240.sqnb Sequence
Number
10
Sequence of purchase
order line being invoiced
tfacp240.item
qual1
11
Item Code ID , referring

to item code system,
referring to item code
system by which to
convert item
tfacp240.item
Item
12
47
tfacp250.iqan
Invoiced Quantity
19
19
tfacp240.unit
Purchase Unit
20
tfacp250.iamt
Invoiced Amount
24
19
Suppliers Invoice
Number
Unit
Codes
Message:
810S, X12 Sales Invoice
Organization: X12
Field type:
Delimited
EDI User Guide

8-14
Comments
Item
code by
Item
Code
System
NOTE
EDI
expr.
Purchase unit of measure
Conversion setup: Global overhead
Field name
Description
Pos
Length Conv.
ENV
Level Identifier
ecedi701.bano Our Reference
14
Baan unique message ID

number.
ecedi020.neta
Our Identification
17
External reference (VAN

ID) of the Baan
companys identification
over this network (from
Our Identification field
defined for Networks).
cisli205.ityp
Sales Invoice
Transaction
Needed for Cash

Application if it is possible
for same customer to
have same invoice
number under multiple
transaction types.
cisli205.idoc
Sales Invoice
Document
Invoice number
cisli240.slso
Sales/Warehouse
Order
Sales order for which

invoice is intended
ecedi028.neta
Network Address
17
trading partner (business
partners network
address).
ecedi003.code Code in Message
Organization (for
example, X12).
Message identifier (for

example, 810S).
ecedi011.koor
Order Type
35
order type.
Constant
11
May be used to pass a

constant for test
indicator.
date()
Todays Date
12
Date message extracted

from BAAN. May include
time based on the date
format defined for the
organization
time()
Current Time
13
Time message extracted

from BAAN.
EDI
expr.
Comments
EDI User Guide

8-15
Conversion setup: 810S (out)
Level: 2 Invoice header mandatory
Field name
Description
Pos
Length Conv.
HDR
Level Identifier
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17

ID) of the Baan
defined for Network).
cisli205.ityp
Sales Invoice
Transaction
Needed for Cash

Application if it is
possible for same
customer to have same
invoice number under
multiple transaction
types.
cisli205.idoc
Sales Invoice
Document
cisli240.slso
Sales/Warehouse
Order
cisli240.corn
Customer Order
Number
30
cisli240.odat
Order Date
22
cisli240.date
Header Entry Date 9
22
cisli240.refa
First Reference
10
30
Reference field from

sales order
cisli240.refb
Second Reference 11
20
Reference field from

sales order
cisli40.cdec
Terms of Delivery
12
tcmcs041.dsca Description
13
80
cisli240.cfrw
14
15
30
Forwarding Agent
EDI User Guide

8-16
EDI Comments
expr.
Date sales order

created.
Terms of
Delivery
Codes
Baan delivery code.
Delivery Code
description
Forwarding
Agent
Codes by
B. P.
Forwarding agent
description
Level: 2 Invoice header - mandatory
Field name
Description
Pos
Length Conv.
cisli2440.ccrs
Late Payment
Surcharge
16
17
30
cisli240.cpay
Terms of Payment 18
19
Comments
EDI
expr.
Late
Payment
Surcharges
Late payment
surcharge description
Terms of
Payment
Codes
30
Baan payment term

code.
Payment term code
description.
tcmcs013.pper Payment Period
20
Net payment period.
tcmcs013.disa
21
Discount period.
tcmcs013.prca Discount
Percentage 1
22
Discount percent for

period.
cisli240.cofc
Department
(Sales Office
Code)
23
cisli240.cofc
Qual1
24
Constant
25
cisli205.ofbp
Sold-to Business
Partner
26
cisli205.ofbp
qual1
27
28
Address/
Partner
Type
Codes
cisli205.itbp
Invoice-to
Business Partner
29
Business
Partners
cisli205.itbp
qual1
30
Discount Period 1
Sales/
Purchasing
Office
Codes
Address/Partner Code
ID by which to convert
the department (sales
office) code
Business
Partners
the business partner
code
Address/Partner Type
Code indicating the
type of business
partner (sold-to)
EDI User Guide

8-17

Field name
Pos
Length Conv.
31
Address/
Partner
Type
Codes
cisli205.pfbp
Pay-from
Business Partner
32
Business
Partners
cisli205.pfbp
Qual1
32
24
Address/
Partner
Type
Codes
cisli205.stbp
Ship-to Business
Partner
35
Business
Partners
cisli205.stbp
qual1
26
37
Address/
Partner
Type
Codes
cisli205.ccur
Invoice Currency
38
Currency
Codes
cisli205.idat
Invoice Date
39
22
cisli205.amti
Amount in Invoice
Currency
40
19
cisli205.amti
Goods Amount in
Invoice Currency
41
19
cisli205.csai
Cost Amount in
Invoice Currency
42
19
cisli205.dcai
Discount Amount
Invoice
43
19
cisli205.tbai
Tax Base Amount

in Invoice
Currency
44
19
cisli205.txai
Tax Amount in
Invoice Currency
45
19
EDI User Guide

8-18
Description
Level: 2 Invoice header - mandatory

EDI
expr.
Comments
Code indicating the
type of business
partner (invoice-to)
the business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (pay-from)
the business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (ship-to)
Conversion setup: 810S (Out)
Level: 3 Specific address optional
Field name
Description
Pos
Length Conv.
HAD
Level Identifier
ecedi701.bano
Our Reference
14

number.
ecedi020.neta
Our Identification
17

ID) of the Baan
cisli205.ityp
Sales Invoice
Transaction
Needed for cash

application if it is possible
have same invoice
transaction types.
ecedi224.code
Code in Message
EDI
expr.
Comments
Address/ INVOF Address/Partner Type

Partner
Code indicating the type
INVIT
Type
of address.
INVPF
Code
INVST
NOTE
The following four addresses may be included in the following level of the
outgoing message depending on the criteria of the EDI Expression (see the EDI
expressions section in this chapter for more information):
n
n
n
n
Sold-to
Invoice-to
Pay-from
Ship-to
EDI User Guide

8-19

Field name
Description
tccom130.ccty
Country
Level: 3 Specific address - optional

Pos
Length
Conv.
EDI
expr.
INVOF
INVIT
INVPF
INVST
tccom130.nama
Name
35
INVOF
INVIT
INVPF
INVST
tccom130.namb
Name 2
30
INVOF
INVIT
INVPF
INVST
tccom130.namc
Address
30
INVOF
INVIT
INVPF
INVST
tccom130.namd
Address 2
10
30
INVOF
INVIT
INVPF
INVST
tccom130.name
City
11
30
INVOF
INVIT
INVPF
INVST
tccom130.namf
City 2
12
30
INVOF
INVIT
INVPF
INVST
EDI User Guide

8-20
Comments
Level: 3 Specific address - optional
Field name
Description
Pos
Length Conv.
EDI
expr.
tccom130.pstc
Zip Code/Postal
Code
13
10
INVOF
Comments
INVIT
INVPF
INVST
tccom130.cste
State/Province
14
INVOF
INVIT
INVPF
INVST
tccom130.telp
Telephone
15
15
INVOF
INVIT
INVPF
INVST
tccom130.telx
Telex
16
15
INVOF
INVIT
INVPF
INVST
tccom130.tefx
Fax
17
15
INVOF
INVIT
INVPF
INVST
tccom130.geoc
GEO Code
18
10
INVOF
INVIT
INVPF
INVST
tccom130.hono
House Number
19
10
INVOF
INVIT
INVPF
INVST
EDI User Guide

8-21
Level: 3 Specific address optional
Field name
Description
Pos
Length Conv.
EDI
expr.
tccom130.pobn
P.O. Box Number
20
10
INVOF
INVIT
INVPF
INVST
tccom130.fovn
Tax Number
21
20
INVOF
INVIT
INVPF
INVST
EDI User Guide

8-22
Comments
Level: 4 Order header text optional
Field name
Description
Pos
Length Conv.
HTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
(VAN ID) of the Baan
companys
identification over this
network (from Our
Identification field
cisli205.ityp
Sales Invoice
Transaction
Needed for cash

application if it is
possible for same
customer to have
same invoice number
under multiple
transaction types.
cisli205.idoc
Sales Invoice
Document
cisli240.slso
Sales/Warehouse
Order
cisli240.text
Header Text
80
EDI
expr.
Comments
One record is written

for every two lines of
header text. Up to 100
ASCII records (user
definable) can be
written.
EDI User Guide

8-23
Level: 5 Tax lines optional
Field name
Description
Pos
Length Conv.
TAX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
cisli205.ityp
Sales Invoice
Transaction
Needed for cash

possible for same
customer to have
same invoice number
under multiple
transaction types.
cisli205.idoc
Sales Invoice
Document
cisli240.slso
Sales/Warehouse
Order
cisli206.txid
Tax ID
cisli206.txid
qual1
cisli206.tbai
Tax Base Amount

in Invo
19
cisli206.txai
Tax Amount in
Invoice C
10
19
EDI User Guide

8-24
EDI
expr.
Comments
Tax
Codes
Tax code ID used to
convert tax code.
Defaults to ZZ.
Level: 6 Order lines optional
Field name
Description
Pos
Length Conv.
LIN
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17

ID) of the Baan
cisli205.ittyp
Sales Invoice
Transaction
Needed for cash

possible for same
types.
cisli205.idoc
Sales Invoice
Document
cisli240.slso
Sales/Warehouse
Order
Sales Order Number

invoiced.
cisli245.pono
Line Number
Sales Order Position

number invoiced.
cisli245.sqnb
Sequence
Number
Sales order sequence

number invoiced
cisli245.corp
Customer Order
Position
16
cisli245.cors
Customer Order
Sequence
10
11
cisli245.item
qual1
11
cisli245.item
Item
12
47
tcibd001.dsca
Description
13
30
EDI
expr.
Comments
Item Code ID, referring

system by which to
convert item. Defaults to
BP.
item
codes by
item
code
system
If conversion is defined,
alternative item code;
otherwise, (internal) item
code.
EDI User Guide

8-25
Level: 6 Order lines optional
Field name
Description
Pos
Length Conv.
cisli245.item
Item
14
47
cisli245.stbp
Ship-to Business
Partner
15
cisli245.stbp
qual1
16
ecedi224.code.
Code In Message
17
cisli245.oqua
Ordered Quantity
18
19
cisli245.dqua
Delivered Quantity 19
19
cisli245.cuqs
Quantity Unit
20
EDI
expr.
Comments
(internal) item code
Business
Partners
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
Codes
Indicates the type of

business partner (shipto)
Unit
Codes
cisli245.pric
Price
21
19
cisli245.cups
Price Unit
22
cisli245.ddat
Delivery Date
23
22
cisli245.amti
Amount in Invoice
Curre
24
19
cisli245.shpm
Packing Slip No.
25
cisli245.odai
Order Discount
Amount
26
19
Quantity delivered in
sales price unit of
measure.
cisli245.ldai
Line Discount
Amount
27
19
External amount for

line item (includes line
discount but no line tax
or order discount).
EDI User Guide

8-26
Unit
Codes
Unit of measure for

sales price.
Date shipped.

Field name
Level: 7 Order line text optional
Description
Pos
Length Conv.
Level Identifier
14

number.
ecedi020.neta
Our Identification
17

ID) of the Baan
cisli205.ityp
Sales Invoice
Transaction
Needed for Cash

Application if it is possible
have same invoice
transaction types.
cisli205.idoc
Sales Invoice
Document
cisli240.slso
Sales/Warehouse
Order
Sales Order Number

invoiced.
cisli245.pono
Line Number

number invoiced.
cisli245.sqnb
Sequence
Number

number invoiced
cisli245.dtxt
Detail Text
80
One record is written for

every two lines of header
text. Up to 100 records
(user definable) can be
written.
LTX
NOTE
EDI
expr.
Comments
The following address may be included in the following level of the outgoing
message depending on the criteria of the EDI Expression (see the EDI
n
Ship-to (delivery)
EDI User Guide

8-27

Field name
Description
Level: 8 Specific Delivery Address optional

Pos
Length
Conv.
EDI
expr.
Comments
LAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
cisli205.ityp
Sales Invoice
Transaction
Needed for Cash

Application if it is
possible for same
types.
cisli205.idoc
Sales Invoice
Document
cisli240.slso
Sales/Warehouse
Order
Sales Order Number

invoiced.
cisli245.pono
Line Number

number invoiced.
cisli245.sqnb
Sequence
Number

number invoiced
ecedi224.code
Code in Message
Address/ INVLND Address/Partner Type

Partner
Type
of business partner
Code
address.
tccom130.ccty
Country
10
Country
Codes
tccom130.nama
Name
11
35
INVLND
tccom130.namb
Name 2
12
30
INVLND
tccom130.namc
Address
13
30
INVLND
tccom130.namd
Address 2
14
30
INVLND
EDI User Guide

8-28
INVLND

Field name
tccom130.name
Description
City
Level: 8 Specific Delivery Address optional

Pos
15
Length Conv.
30
EDI
expr.
Comments
INVLND
tccom130.namf
City 2
16
30
INVLND
tccom130.pstc
ZIP Code/Postal
Code
17
10
INVLND
tccom130.cste
State/Province
18
INVLND
tccom130.telp
Telephone
19
15
INVLND
tccom130.telx
Telex
20
15
INVLND
tccom130.tefx
Fax
21
15
INVLND
tccom130.geoc
GEO Code
22
10
INVLND
tccom130.hono
House Number
23
10
NVLND
tccom130.pobn
P.O.Box Number
24
10
NVLND
tccom130.fovn
Tax Number
25
20
INVLND
EDI User Guide

8-29
Conversion setup: 820S, Remittance Advice

number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Header
Level 2
Mandatory
Key: F1, F2, F3
Line Data
Level 3
Mandatory / Repetitive
Key: F1, F2, F3
Legend:
F3: Document Reference Number

Message:
820S, X12 Remittance Advice
Organization: X12
Field type:
Delimited
NOTE
EDI User Guide

8-30

Field name
Description
ENV
Level Identifier
Pos
Length

the Envelope record
ecedi702.bano Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address.
ecedi702.msno Order Reference
20
Business partners
document number.
ecedi702.orga
The Baan EDI

organization.
ecedi702.mess EDI Message

code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message

organization, the
message will be
processed as a test
message will be stored
in Saved Messages to
be Received).
10
22
The date/time the

message was sent.
Organization
ecedi702.send Date Sent
Conv
EDI
expr.
Comments
EDI User Guide

8-31

Field name
Description
HDR
Level Identifier
Level: 2 Header - mandatory

Pos
Length
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
20
Business partners
order number.
tfcmg506.bppb Pay-by Business

Partner
tfcmg506.pbbp qual1
tfcmg506.pbbp qual2
tfcmg506.stdt
10
EDI User Guide

8-32
Business
Partner
Statement Date
Conv.
Business
Partners
EDI
expr.
Comments

overhead records
business partner if
blank.
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

business partner (payby)

Field name
Description
LIN
Level Identifier
Reference
ecedi702.bpid
Level: 3 Line data - mandatory

Pos
Length
35
Unique message
reference. Must be
unique for business
partner.
Business Partner
20
tfcmg506.bppb Pay-by Business

Partner
tfcmg506.pbbp qual1
tfcmg506.pbbp qual2
tfcmg501.ttyp
Transaction
Type
tfcmg501.ninv
Document
15
tfcmg501.docd Document Date
10
10
tfcmg501.trnd
Transaction Date
11
10
tfcmg501.pref
Reference
12
35
tfcmg501.desc Description
13
35
tfcmg501.bano Bank Account
14
25
tfcmg501.nama Name
15
35
tfcmg501.ccur
16
17
19
Currency
tfcmg501.amnt Amount
Conv.
EDI
expr.
Comments
Business partners
order number.
Business
Partners

overhead records
business partner if
blank.
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

business partner (payby)
Currency
Codes

Not available this release.
EDI User Guide

8-33

number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3, F4
Error Header
Level 2
Mandatory
Key: F1, F2, F3, F4
Error Line Detail

Level 3
Key: F1, F2, F3, F4
Legend:
F3: Reference Message Code
(of erroneous message)

F3:

Message:
824S, X12 Error Notification
Field type:
Delimited
EDI User Guide

8-34

Field name
Description
ENV
Level Identifier
Pos Length
Conv.
EDI
expr.
Comments

the Envelope record
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as defined in
business partners
network address.
20
Business partners
document number.
ecedi702.orga
The Baan EDI

organization.

code.
Organization

ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message
10
Test indicator: If the value

in this field is non-blank
and matches the value
defined for the
organization, the
message will be
processed as a test
Received).
11
22
The date/time the

message was sent.
EDI User Guide

8-35
Conversion setup: 824S (in)

Field name
Description
HDR
Level Identifier
Level: 2 Error Header - mandatory

Pos Length
Conv.
EDI
expr.
Comments
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partners
business partners
network address.
ecedi702.msno Our Reference
20
whinh430.shpm Shipment
Identification
EDI User Guide

8-36
Business Partner
Shipment Identification
Number (suppliers SID or
ASN Number)

Field name
Description
LIN
Level Identifier
Level: 3 Error Line Details - mandatory

Pos Length
Conv.
EDI
expr.
Comments
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partners
network address.
ecedi702.msno Our Reference
20
whinh430.iedi
ASN
Identification
80
Free form (text). May be

used to store the error
information received.
whinh430.iedi
ASN
Identification
80

whinh430.iedi
ASN
Identification
80

whinh430.iedi
ASN
Identification
10
80

whinh430.iedi
ASN
Identification
11
80

whinh430.iedi
ASN
Identification
12
80

Business Partner
EDI User Guide

8-37

Message:
824S, X12 Error Notification
Organization: X12
Field type:
Delimited
EDI User Guide

8-38
Field name
Description
ENV
Level Identifier
Identifies the records
14
Unique message
reference.
ecedi020.neta
17

ID) of the Baan
Message Code (for

example, 824S)
ecedi750.eono Order Reference
20
Business partners
document number.
ecedi028.neta
Network Address
17
trading partner
(business partners
network address).
Organization (for
example, X12).

example, 810S).
ecedi011.koor
Order Type in
Message
35
order type.
Constant
10
Date ( )
Our Identification
Pos Length
11
Conv.
EDI
expr.
Comments

constant for test
indicator.
22

from BAAN. May
include time based on
the date format defined
for the organization
EDI User Guide

8-39
Level: 2 Error Header - mandatory
Field name
Description
HDR
Level Identifier
14
Unique message
reference.
ecedi020.neta
17

ID) of the Baan
20
Business partners order

number.
20

number.
EDI User Guide

8-40
Our Identification
Pos Length
Conv.
EDI
expr.
Comments
Level: 3 Error Line Details - mandatory
Field name
Description
LIN
Level Identifier
14
Unique message
reference.
ecedi020.neta
17

ID) of the Baan
20
TR
Constant
ecedi751.rfid
Field Identifier
ecedi751.trfd
Field
15
ecedi751.efld
Field Value
35
ecedi751.ercd
Error Code
Our Identification
Pos Length
10
ecedi751.dsc1 Error Warning

Message L
11
80
ecedi751.dsc2 Error Warning

Message L
12
80
Conv.
EDI
expr.
Comments

number.
EDI User Guide

8-41
Conversion setup: 830S, Planning Release

Record relationships
number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3, F4
Release Header
Level 2
Mandatory
Key: F1, F2, F3, F4
Specific Address
Level 3
Key: F1, F2, F3, F4
Release Header Text

Level 4
Key: F1, F2, F3, F4
Release Lines
Level 5
Key: F1, F2, F3, F4, F5
Release Line Text

Level 6
Key: F1, F2, F3, F4, F5
Specific Address
Level 7
Key: F1, F2, F3, F4, F5
Legend:
F3: Release Number
F4: Release Revision
F5: Release Line (Position) Number

F3: Customer Release Number
F4: Customer Release Revision
F5: Customer Release Line (Position) Number

Message:
830S, X12 Planning Release
Organization: X12
Field type:
Delimited
EDI User Guide

8-42

Field name
Description
ENV
Level Identifier
Pos Length
Conv.
EDI
expr.
Comments

the Envelope record
Reference
14
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address.
20
Business partners
document number.
ecedi702.orga
The Baan EDI

organization.

code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message
10

organization, the
message will be
processed as a test
be Received).
11
22
The date/time the

message was sent.
Organization
EDI User Guide

8-43

Field name
Description
HDR
Level Identifier
Level: 2 Release Header - mandatory

Pos Length
Conv.
EDI
expr.
Comments
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls312.ofbp
Sold-to Business
Partner
tdsls312.ofbp
qual1
tdsls312.ofbp
qual2
Address/
Partner
Type
codes

business partner (soldto)
tdsls312.stbp
Ship-to Business
Partner
Business
Partners
tdsls312.stbp
qual1
10
tdsls312.stbp
qual2
11
tdsls312.fohs
Forecast Horizon
Start
12
22
tdsls312.fohe
Forecast Horizon
End
13
22
EDI User Guide

8-44
Business
Partners

overhead records
business partner if
blank.
ID used to convert
business partner.
Defaults to ZZ.
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

Field name
Description
Pos Length
Conv.
tdsls312.egdt
Generation Date
14
22
tdsls312.tqal.
Schedule Type
Qualifier
15
15
Schedule
Type
Indicates if the dates

communicated are
delivery-based or
shipment-based. If
delivery-based (the date
included represents the
planned shipped date),
leadtimes have been
taken into
consideration. If
shipment-based (the
date included
represents the
requirement, or planned
receipt, date), no
leadtime has been
taken into
consideration.
tdsls312.qqal
Schedule
Quantity Qualifier
16
22
Schedule
Quantity
Type
Indicates if the quantity

received for the
schedule line is a
schedule cumulative or
actual, discrete value. If
cumultaive, the actual
value stored at the
scehdule line
(tdsls307.quan) is
calculated.
EDI
expr.
Comments
.
EDI User Guide

8-45

Field name
Description
HTX
Level Identifier
Level: 4 Release Header Text - optional

Pos Length
Conv.
EDI
expr.
Comments
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
Customers release
revision.
tdsls312.txta
Release Text
80
Two text fields per

ASCII file record;
multiple ASCII file
records can be read.
tdsls312.txta
Release Text
80
EDI User Guide

8-46

Field name
Description
LIN
Level Identifier
Level: 5 Release Lines - mandatory

Pos Length
Conv.
EDI Comments
expr.
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address
20
tdsls312.crlr
Customer
Revision
14
tdsls308.ppon
Customer
Schedule Position
tdsls311.stbp
Ship-to Business
Partner
tdsls311.stbp
qual1
tdsls311.stbp
qual2
Address/
Partner
Type
codes
tdsls311.cono
Contract
10
Sales
Contract
Codes by
B. P.
tdsls311.pono
Position
11
tdsls311.crsd
Delivery Type
14
20
tdsls311.item
Item
15
47
tdsls307.item
qual1
16
Business
Partners
Address/Partner Code ID
used to convert business
partner. Defaults to ZZ.
Contract position
Item
codes by
item code
system
code.
Item Code ID, referring to
item code system,
system by which to
BP.
EDI User Guide

8-47
Field name
Description
tdsls307.sdat
Start Date
17
22
tdsls307.edat
End Date
18
22
tdsls307.cuqs
Sales Unit
19
tdsls307.quan
Quantity
20
19
tdsls307.txta
Schedule Text
22
80
tdsls307.cwar
Warehouse
23
tdsls307.cwar
qual1
24
tdsls311.cofc
Sales Office
25
tdsls311.cofc
Qual1
26
tdsls311.leng
Length
27
tdsls311.widt
Width
28
tdsls311.thic
Thickness
29
tdsls311.cons
Consigned
30
tdsls311.sbim
Self Billed
Invoice
31
tdsls311.lsel
Lot Selection
32
12
tdsls307.revi
Engineering Item
Rev.
33
EDI User Guide

8-48
Pos Length
Conv.
EDI Comments
expr.
Unit Codes
Passing a zero in this
field cancels the item: If
a quantity of zero is
received, all subsequent
dates for the item on the
schedule will be zeroed
out as well.
Warehouse
codes
warehouse. Defaults to
ZZ.
Sales/
Purchasing
Office
Codes
ID used to convert office
code. Defaults to ZZ.
Lot
Selection
Codes by B.
P.

Field name
Description

Pos Length
Conv.
tdsls307.clot
Lot
34
16
tdsls307.clot
qual1
35
Lot Code
ID by
Business
Partner
tdsls311.ccof
Contract Office
38
Sales/
Purchasing
Office
Codes
tdsls311.ccof
Qual1
39
EDI Comments
expr.
Lot Code ID indicating if
the lot code is the
senders lot code or the
recipients lot code.
ID used to convert
office code. Defaults to
ZZ.
EDI User Guide

8-49

Field name
Description
LTX
Level Identifier
Level: 6 Release Line Text- optional

Pos Length
Conv.
EDI Comments
expr.
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls308.ppon
Customer
Schedule
Position
16
Customer release line

number
tdsls307.txta
Schedule Text
80
Two text fields per ASCII

file record; multiple
ASCII file records can be
read.
tdsls307.txta
Schedule Text
80
EDI User Guide

8-50

Field name
Description
LAD
Level: 7 Release Specific Address optional

Pos
Length
Conv.
EDI Comments
expr.
Level
Identifier
ecedi702.bano
Message
Reference
35
Unique message reference.

Must be unique for business
partner.
ecedi702.bpid
Business
Partner
Business partners
business partners network
address
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls308.ppon
Customer
Schedule
Position
16
ecedi224.code
Code in
Message
Address
/Partner
Type
Codes
tccom130.ccty
Country
10
Country
Codes
tccom130.nama Name
11
35
tccom130.namb Name 2
12
30
tccom130.namc Address
13
30
tccom130.namd Address 2
14
30
tccom130.name City
15
30
tccom130.namf
City 2
16
30
tccom130.pstc
ZIP
Code/Postal
Code
17
10
tccom130.cste
State/Provin
ce
18
tccom130.telp
Telephone
19
15
Address/Partner Type Code

indicating the type of
business partner address.
EDI User Guide

8-51
Conversion setup: 830S

Field name
Description
tccom130.telx
Level: 6 Release Line Specific Address optional

Pos
Length
Telex
20
15
tccom130.tefx
Fax
21
15
tccom130.geoc
GEO Code
22
10
tccom130.hono
House
Number
23
10
tccom130.pobn
P.O.Box
Number
24
10
tccom130.fovn
Tax Number
25
20
EDI User Guide

8-52
Conv.
EDI
expr.
Comments
Conversion setup: 830S, X12 Planning

Release
Message:
830S, X12 Planning Release
Organization: X12
Field type:
Delimited
Field name
Description
ENV
Pos
Length
Level Identifier
14

number.
ecedi020.neta
Our Identification
17

ID) of the Baan companys
network (from Our
Identification field defined
for Network).
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
ecedi028.neta
Network Address
17
trading partner (business
partners network address).
Organization (for example,

X12).

example, 810S).
ecedi011.koor
10
35
External reference of order

type.
date ( )
Order Type in
Message
11
Conv.
EDI
expr.
Comments

time based on the date
organization
EDI User Guide

8-53

Field name
Description
HDR
Level: 2 Release Header mandatory

Pos
Length
Level Identifier
14

number.
ecedi020.neta
Our Identification
17

ID) of the Baan
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur312.fohs
Forecast Horizon
12
22
tdpur312.fohe
Forecast Horizon
End
13
22
tdpur312.egdt
Generation Date
14
22
tdpur312.tqal
Schedule Type
Qualifier
15
15
EDI User Guide

8-54
Conv.
EDI
expr.
Comments
Schedule
Type

communicated are
delivery-based or
shipment-based. If
delivery-based (the date
included represents the
leadtimes are taken into
consideration, and the
date included are
adjusted to account for
leadtimes. If shipmentbased (the date included
represents the
requirement, or planned
receipt, date), no
leadtimes are taken into
consideration, and the
dates included are the
requirement dates
reflected on the release
line.

Field name
Description
tdpur312.qqal

Pos
Length
Conv.
Schedule Quantity
Qualifier
16
22
Schedule
Quantity
Type
tdpur312.sfbp
Ship-from B. P.
17
Business
Partners
tdpur312.sfbp
qual1
18
19
Address/
Partner
Type
Codes
tdpur312.bfbp
Buy from B. P.
20
Business
Partners
tdpur312.bfbp
qual1
21
22
NOTE
EDI
expr.
Comments
indicated is a schedule
cumulative or an actual,
discrete value. The
default conversion setup
includes both quantities.
of business partner (shipfrom).
Address/
Partner
Type
Codes
of business partner (buyfrom).
The following two addresses may be included in the following level of the
n
n
Buy-from
Ship-from
EDI User Guide

8-55
Level: 3 Release Header Specific Address Optional
Field name
Description
HAD
Level Identifier
ecedi701.bano
Our Reference
35
Baans unique message ID

number.
ecedi020.neta
Our
Identification
External reference (VAN ID)

of the Baan companys
network (from Our
for Network).
tdpur312.rlno
Release
Number
tdpur312.rlrv
Release
Revision
Number
ecedi224.code
Code in
Message
Country
tccom130.ccty
tccom130.nama Name
Pos Length
35
Conv.
EDI
expr.
Address/
Partner
Type
Code
Country
Codes
PRSF
PRBF
PRSF
PRBF
PRSF
PRBF
EDI User Guide

8-56
Comments


Field name
Description
tccom130.namb
Name 2
Level: 3 Release Header Specific Address Optional

POS Length
9
30
Conv
EDI
Expr
Comments
PRSF
PRBF
tccom130.namc
Address
10
30
PRSF
PRBF
tccom130.namd
Address 2
11
30
PRSF
PRBF
tccom130.name
City
12
30
tccom130.namf
City 2
13
30
PRSF
PRBF
PRSF
PRBF
tccom130.pstc
ZIP Code/Postal
Code
14
10
tccom130.cste
State/Province
15
tccom130.telp
Telephone
16
15
PRSF
PRBF
PRSF
PRBF
PRSF
PRBF
tccom130.telx
Telex
17
15
PRSF
PRBF
tccom130.tefx
Fax
18
15
PRSF
PRBF
tccom130.geoc
GEO Code
19
10
PRSF
PRBF
tccom130.hono
House Number
23
10
tccom130.pobn
P.O.Box Number
24
10
PRSF
PRBF
PRSF
PRBF
tccom130.fovn
Tax Number
20
20
PRSF
PRBF
EDI User Guide

8-57

Field name
Description
HTX
Level: 4 Release Header Text- optional

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
35
Unique message
reference.
ecedi020.neta
Our Identification

ID) of the Baan
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur312.txta
Release Text
80

every two lines of
records (user definable)
can be written.
EDI User Guide

8-58
Conv.
EDI Comments
expr.

Field name
Pos
Length
Level Identifier
35
Unique message
reference.
ecedi020.neta
Our Identification
External reference
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur312.rpon
Release Position
Number
tdpur307.cwar Warehouse
tdpur307.cwar
Address/
Partner
Type
Codes
tdpur311.cono
Contract
10
Purchase
Contract
Codes by
B. P.
tdpur311.pono Position
11
tdpur311.cofc
Purchase Office
12
tdpur311.cofc
Qual1
13
LIN
Description
Level: 5 Release Lines mandatory
qual1
Conv.
Warehou
se Codes
EDI Comments
expr.
The warehouse to
which goods are to be
delivered
ZZ
of address (ship-to, for
the delivery warehouse)
Contract position (line)

number
Sales/
Purchasi
ng Office
Codes
EDI User Guide

8-59

Field name
Description
tdpur311.crsd
Level: 5 Release Lines- mandatory

Pos
Length
Delivery Type
14
20
tdpur307.item.
Item
15
47
tdpur307.item
qual1
16
tdpur307.sdat
Start Date
17
22
tdpur307.edat
End Date
18
22
tdpur307.cuqs
Purchase Unit
19
tdpur307.quan Schedule Quantity
20
19
tdpur.307.rqcm Required
Cumulative
21
Quantity expressed in
schedule cumulative
value.
Whinh302.asnr ASN Receipt Nr.
22
30
Number (Suppliers
ASN Number or SID).
tdpur311.leng
Length
25
tdpur311.widt
Width
28
tdsls311.thic
Thickness
29
tdpur311.cons
Consigned
30
Yes/no
tdpur311.sbim
Self Billed Invoice
31
Yes/no
tdpur311.lsel
Lot Selection
32
12
tdpur307.revi
Engineering Item
Rev.
33
tdpur307.clot
Lot
34
16
EDI User Guide

8-60
Conv.
item
codes by
item
code
system
EDI Comments
expr.
otherwise, (internal)
item code.
system by which to
BP.
Unit
Codes
Lot
Selection
Codes by
B. P.

Field name
Description
tdpur307.clot

Pos
Length
Conv.
qual1
35
Lot Code
ID by B.
P.
whltc100.ltbp
Business Partners
Lot
36
30
whltc100.ltbp
Qual1
37
tdpur309.rccm
Received
Cumulative
40
19
tdpur309.shcm
Shipped
Cumulative
41
19
tdpur309.ivcm
Invoiced
Cumulative
42
19
43
19
tdpur309.rawa
Raw Authorization
tdpur309.hraw
High Raw
Authorization
44
19
tdpur309.ratd
Raw Auth. Through

Date
45
22
tdpur309.faba
Fab Authorization
46
19
tdpur309.hfab
High Fab
Authorization
47
19
tdpur309.fadt
Fab. Auth. Through

Date
48
22
tdpur309.csdt
Cum Start Date
49
22
EDI Comments
expr.
the lot code is the
Unique message
reference. Must be
unique for business
partner.
Lot Code
ID by B.
P.
tdipu015.rtype
Requirement Type
50
12
Tdipu015.setu
Segment Time Unit
51
tcibd001.cuni
Inventory Unit
52
Unit
Codes
tcibd001.cwun
Weight Unit
53
Unit
Codes
tcibd001.wght
Weight
54
10
Unique message
reference. Must be
unique for business
partner.
EDI User Guide

8-61

Field name
Description
whinh210.rstk

Pos
Length
Receipt Quantity
55
19
Last receipt quantity
whinh210.ardt
Actual Receipt
Date
56
22
Date of last receipt
tdpur311.ccof
Contract Office
57
tdpur311.ccof
Qual1
58
Conv.
EDI Comments
expr.
Sales/
Purchasing
Office
Codes
Level: 6 Release Line Text optional
Field name
Description
LTX
Level Identifier
14
Unique message
reference.
ecedi020.neta
Our Identification
17

ID) of the Baan
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur312.rpon
Release Position
Number
tdpur307.txta
Schedule Text
80

every two lines of text. Up
to 100 records (user
definable) can be written.
EDI User Guide

8-62
Pos Length
Conv.
EDI Comments
expr.
NOTE
n
Ship-to
Level: 7 Line Specific Address - Optional
Field name
Description
Pos Length
Conv.
LAD
Level
Identifier
ecedi701.bano
Our
Reference
14
ecedi020.neta
Our
Identification
17

network (from Our
for Network).
tdpur312.rlno
Release
Number
tdpur312.rlrv
Release
Revision
Number
tdpur308.rpon
Release
Position
Number
ecedi224.code
Code in
Message
Address/ PRSTW Address/Partner Type

Partner
Code indicating the type of
Type
Codes
tccom130.ccty
Country
Country
Codes
tccom130.nama
Name
35
EDI
expr.
Comments
PRSTW
PRSTW
tccom130.namb
Name 2
10
30
PRSTW
tccom130.namc
Address
11
30
PRSTW
tccom130.namd
Address 2
12
30
PRSTW
tccom130.name
City
13
30
PRSTW
tccom130.namf
City 2
14
30
PRSTW
EDI User Guide

8-63
Level: 7 Line Specific Address - Optional
Field name
Description
Pos Length
Conv.
tccom130.pstc
ZIP
Code/Postal
Code
15
10
PRSTW
tccom130.cste
State/
Province
16
PRSTW
EDI
expr.
tccom130.telp
Telephone
17
15
PRSTW
tccom130.telx
Telex
18
15
PRSTW
tccom130.tefx
Fax
19
15
PRSTW
tccom130.geoc
GEO Code
20
10
PRSTW
tccom130.hono
House
Number
21
10
tccom130.pobn
P.O.Box
Number
22
10
tccom130.fovn
Tax Number
231
20
EDI User Guide

8-64
PRSTW
Comments
Conversion setup: 850S, Sales Order

number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Order Header
Level 2
Mandatory
Key: F1, F2, F3
Specific Address
Level 3
Key: F1, F2, F3
Order Header Text

Level 4
Key: F1, F2, F3
Order Line Text

Level 6
Key: F1, F2, F3, F4, F5
Order Lines
Level 5
Key: F1, F2, F3, F4, F5
Order Footer Text

Level 8
Key: F1, F2, F3
Specific Address
Level 7
Key: F1, F2, F3, F4, F5
Legend:
F3: Order Number

F3: Customer Order Number
F4: Customer Order Line (Position) Number
F5: Customer Order Line Sequence Number
EDI User Guide

8-65

Message:
850S, Sales Order
Organization: X12 Sales Order
Field type:
Delimited
NOTE
EDI User Guide

8-66
Field name
Description
Pos Lengt
h
Conv.
ENV
Level Identifier

as the Envelope
record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
ecedi702.msno
Order Reference
20
Business partners
document number.
ecedi702.orga
Organization
The Baan EDI

organization.
ecedi702.mess
EDI Message
The Baan EDI

message code.
ecedi702.koor
Order Type
35
order type (code in
message).
ecedi702.test
Test Message

value in this field is
non-blank and
matches the value
defined for the
organization, the
message will be
processed as a test
message only (it will
be validated, any
errors will be
reported, and the
message will be
stored in Saved
Messages to be
Received).
ecedi702.send
Date Sent
10
22
The date/time the

message was sent.
EDI
expr.
Comments
EDI User Guide

8-67

Field name
Description
HDR
ecedi702.bano
Level Identifier
Message
Reference
ecedi702.bpid
Business Partner
tdsls400.corn
tdsls400.refa
tdsls400.refb
tdsls400.prno
Customer Order
Number
Order Date
Plan. Del. Date
Planned Receipt
Date
Reference A
Reference B
Contract
tdsls400.cdec
tsls400.ddat
tdsls400.ddat
tdsls400.prdt
Level: 2 Order Header - mandatory

Pos Length
Conv.
EDI Comments
expr.
1
3
2
35
Unique message
reference. Must be
unique for business
partner.
3
9
Business
Partners
4
30
5
6
7
22
22
22
8
9
10
30
20
9
Term of Delivery
11
tdsls400.cfrw
Forwarding Agent
13
tdsls400.ccrs
Late Payment
Surcharge
15
tdsls400.cpay
Terms of Payment
15
tdsls400.ccur
Currency
22
tdsls400.ccty
Country
23
tdsls400.cpls
tdsls400.creg
tdsls400.cbrn
tdsls400.odis
Sales Price List

Area
Line of Business
Order Discount
24
25
26
27
3
3
6
5
EDI User Guide

8-68
Sales
Contract
Codes by
B. P.
Term of
Delivery
Codes
Forwarding
Agent
Codes by
B. P.
Late
Payment
Surcharges
Terms of
Payment
Codes
Currency
Codes
Country
Codes
Baan delivery code.

Field name
Description
tdsls400.ofbp
Sold-to Business
Partner
tdsls400.ofbp
qual1
tdsls400.ofbp
qual2
tdsls400.cofc
Sales Office
tdsls400.cofc
qual1
tdsls400.cwar
Warehouse
tdsls400.cwar
qual1
tdsls400.stbp
tdsls400.stbp
Ship-to Business
Partner
qual1
tdsls400.stbp
qual2
tdsls400.sbim
Self Billed Invoice
Level: 2 Order Header - mandatory

Pos Length
Conv.
EDI Comments
expr.
28
9
Business
Partner
overhead records
business partner if
blank.
29
6
Address/Partner
Code ID used to
convert business
partner. Defaults to
ZZ.
Address/
30
6
Partner
business partner
Type
(sold-to)
codes
31
6
Sales/
Purchasing
Office
Codes
32
6
Address/Partner
Code ID used to
convert office code.
Defaults to ZZ.
Warehouse
43
6
Codes
44
6
Address/Partner
Code ID by which to
convert warehouse.
Defaults to ZZ.
45
9
Business
Partner
46
6
Address/Partner
Code ID used to
convert business
ZZ.
Address/P
47
6
artner Type
business partner
codes
(ship-to)
48
5
EDI User Guide

8-69
Level: 3 Order header addresses - optional
Field name
Description
HAD
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
tdsls400corn
Customer Order
Number
30
ecedi224.code
Code in Message
Address/
Partner
Type
Codes
tccom130.ccty
Country
Country
Codes
35
tccom130.nama Name
Pos Length
30
30
10
30
tccom130.name City
11
30
tccom130.namf
City 2
12
30
tccom130.pstc
Zip Code/Postal
Code
13
10
tcom130.cste
State/Province
14
tccom130.telp
Telephone
15
15
tcccom130.telx
Telex
16
15
tccom130.tefx
Fax
17
15
tccom130.geoc
GEO Code
18
10
tccom130.hono
House Number
19
10
tccom130.pobn
P.O.Box Number
20
10
tccom130.fovn
Tax Number
21
20
EDI User Guide

8-70
Conv.
EDI
expr.
Comments
of business partner
address.

Field name
Description
HTX
Level Identifier
Reference

Pos Length
35
Unique message
reference. Must be
unique for business
partner.
Business Partner
Customer Order
Number
30
tdsls400.txta
Header Text
80
tdsls400.txta
Header Text
80
LIN
Level Identifier
Comments
tdsls400corn
Description
EDI
expr.
ecedi702.bpid
Field name
Conv.
Two text fields per

ASCII file record;
multiple ASCII file
Level: 5 Order lines - mandatory

Pos Length
Conv.
EDI
expr.
Comments
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
tdsls400.corn
Customer Order
Number
30
tdsls401.corp
Customer
Purchase Order
Position Number
16
Customer order line

number.
tdsls401.cors
Customer Order
Sequence
Number
11
If trading partners order

line structure has
subdelivery line
numbers.
tdsls401.cprj
Project
EDI User Guide

8-71
Field name
Description
Pos Length
tdsls401.item
qual1
tdsls401.item
Item
tdsls401.oqua
Ordered Quantity
12
19
tdsls401.odat
Order Date
13
22
tdsls401.ddta
Planned Delivery
Date
14
22
tdsls401.prdt
Planned Receipt
Date
15
22
tdsls401.cuqs
Sales Unit
16
tdsls401.pric
Price
17
19
tdsls401.cups
Sales Price Unit
18
tdsls401.disc
Line Discount
19
Conv.
EDI
expr.
Comments
used to convert item
code. Defaults to BP. If
qual1 is ZZ, no
conversion is
performed.
Item
Codes
by Item
Code
System
item code.
Unit
Codes
Unit of measure
sold/delivered.
Unit
Codes
Unit of measure for

sales price.
20
21
22
23
tdsls401.cvat
Tax Code
24
tdsls401.cvat
qual1
25
EDI User Guide

8-72
Tax
codes
Tax code ID used to
convert tax code;
defaults to ZZ. No
conversion is performed
if value is ZZ.

Field name
Description
tdsls401.cdis
Discount Code

Pos Length
26
Conv.
EDI
expr.
Comments
27
28
29
30
tdsls401.dmth
Discount Method
31
25
32
Discount
Methods
by B. P.
33
34
35
tdsls401.ldam
Discount Amount
36
19
37
38
39
40
tdsls401.lsel
Lot Selection
41
12
tdsls401.clot
Lot
42
16
tdsls401.clot
qual1
43
tdsls401.leng
Length
46
tdsls401.widt
Width
47
tdsls401.thic
Thickness
48
tdsls401.cmnf
Manufacturer
49
tdsls401.cpcl
Product Class
50
tdsls401.cpln
Product Line
51
Lot
Selection
Codes
by B. P.
Lot Code
ID by B.
P.

the lot code is the
EDI User Guide

8-73
Field name
Description
Pos
Length
Conv.
tdsls401.cwar
Warehouse
52
Warehouse
Codes
tdsls401.cwar
Qual1
53
tdsls401.stbp
Ship-to
Business
Partner
55
tdsls401.stbp
Qual1
55
tdsls401.stbp
Qual2
55
tdsls401.cfrw
Forwarding
Agent
58
EDI User Guide

8-74
EDI Comments
expr.
The warehouse from
which goods are
shipped.
ZZ.
Business
Partners
business partner.
Defaults to ZZ.
Address/
Partner
Type Code

Forwarding
Agent
Codes by
B. P.
Field name
Description
Pos Length
Conv.
LTX
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
tdsls400.corn
Customer Order
Number
30
tdsls401.corp
Customer Order
Position
16
Customer order line

number
tdsls401.cors
Customer Order
Sequence
11
Customer order line

sequence number.
tdsls401.txta
Order line text
80
Two text fields per

ASCII file record;
multiple ASCII file
tdsls401.txta
Order line text
80
EDI
expr.
Comments
EDI User Guide

8-75

Field name
Description
LAD
Level: 7 Lines specific address optional

Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
tdsls400.corn
Customer Order
Number
30
tdsls401.corp
Customer Order
Position
16
tdsls401.cors
Customer Order
Sequence
11
ecedi224.code
Code In
Message
Address
/Partner
Type
Codes
Tccom130.ccty
Country
Country
Codes
tccom130.nama
Name
35
10
30
tccom130..namb Name 2
tccom130.namc
Address
11
30
tccom130.namd
Address 2
12
30
tccom130.name
City
13
30
tccom130.namf
City 2
14
30
tccom130.pstc
Zip Code /Postal

Code
15
10
tcom130.cste
State/Province
14
tccom130.telp
Telephone
15
15
tcccom130.telx
Telex
16
15
tccom130.tefx
Fax
17
15
tccom130.geoc
GEO Code
18
10
EDI User Guide

8-76
Conv.
EDI
expr.
Comments
of business partner
address.

Field name
Level: 7 Lines specific delivery address

optional
Description
Pos
Length
tccom130.hono House Number
19
10
tccom130.pobn P.O.Box Number
20
10
tccom130.fovn
21
20
Tax Number
Conv.
EDI
expr.
Comments
Level: 8 Footer text optional
Field name
Description
FTX
Level Identifier
ecedi702.bano
Message
Reference
35
ecedi702.bpid
Business Partner
tdsls400.corn
Customer Order
Number
30
tdsls400.txtb
Footer Text
80
tdsls400.txtb
Footer Text
80
Po
s
Length
Conv.
EDI
expr.
Comments
Identifies the record.
Unique message
reference. Must be
unique for business
partner.
Two text fields per ASCII

ASCII file records can be
read.

Message:
Organization:
Field type:
NOTE
850S, X12 Sales Order

X12
Delimited
EDI User Guide

8-77
Level: 1 Envelope mandatory
Field name
Description
ENV
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
ecedi028.neta
Network
Address
17
Trading Partner
(business partners
network address).
ecedi003.code
Code in
Message
Organization (X12).
ecedi001.code
Code in
Message
message identifier
(850S).
ecedi011.koor
Order Type
35
order type.
Constant

constant for test
indicator.
Date()
Todays Date
10
Date message
extracted from BAAN.
May include time,
based in the date
organization.
Time()
Current Time
11
Time message
EDI User Guide

8-78
Pos Length
Conv.
EDI
expr.
Comments

Field name
Description
HDR
Level Identifier
Level: 2 Order header mandatory

Pos Length
Conv.
EDI
expr.
Comments
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur400.odat
Order Date
22
tdpur400.ddat
Delivery Date
22
tdpur400.ddtc
Confirmed
Delivery Date
22
tdpur400.ddat
Delivery Date
22
tdpur400.ddtc
Confirmed
Delivery Date
22
tdpur400.refa
Reference A
30
tdpur400.refb
Reference B
20
tdpur400.prno
Contract
10
Purchase
Contract
Codes by
B. P.
tdpur400.cdec
Term of Delivery
11
Terms of
Delivery
Codes
CDH
Per the evaluation

expression: If a
confirmed delivery
date is specified on
the order, the
confirmed delivery
date overwrites the
delivery date.
CDH
Per the evaluation

expression: If a
confirmed delivery
the order, the
confirmed delivery
date overwrites the
delivery date.
EDI User Guide

8-79

Field name
Description

Pos Length
Conv.
12
30
tdpur400.cfrw
13
14
30
tdpur400.ccrs
15
16
30
tdpur400.cpay
17
18
30
19
tcmcs013.disa
20
Percentage 1
21
tdpur400.ccur
Currency
22
Currency
Codes
tdpur400.ccty
Country
23
Country
Codes
tdpur400.cplp
Purchase Price
List
24
tdpur400.creg
Area
25
tdpur400.cbrn
Line of Business
26
tdpur400.odis
Order Discount
27
tdpur400.cofc
Purchase Office
28
tdpur400.cofc
qual1
29
EDI User Guide

8-80
Forwarding Agent
Late Payment
Surcharge
Terms of
Payment
Discount Period 1
EDI
expr.
Comments
Forwarding
Agent
Codes by
B. P.
Late
Payment
Surcharges
Terms of
Payment
Codes
Discount period.
Sales/
Purchasing
Office
Codes
ID used to convert
office code. Defaults
to ZZ.
Field name
Description
Pos Length
Conv.
Constant
30
tdpur400.otbp
Buy From B. P.
31
tdpur400.otbp
qual1
32
33
Address/
Partner
Type
Codes
tdpur400.sfbp
Ship From B. P.
34
Business
Partners
tdpur400.sfbp
qual1
35
36
Address/
Partner
Type
Codes
tdpur400.ifbp
Invoice-from B. P.
37
Business
Partners
tdpur400.ifbp
qual1
38
39
Address/
Partner
Type
Codes
tdpur400.ptbp
Pay-to B. P.
40
Business
Partners
tdpur400.ptbp
qual1
41
EDI
expr.
Comments
Business
Partners
ID used to convert
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (buy-from)
ID used to convert
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (ship-from)
ID used to convert
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (invoice-from)
ID used to convert
business partner.
Defaults to ZZ.
EDI User Guide

8-81

Field name
Description

Pos Length
Conv.
42
Address/
Partner
Type
Codes
tdpur400.cwar
Warehouse
43
Warehous
e Codes
tdpur400.cwar
qual1
44
45
tdpur400.sbim
46
EDI User Guide

8-82
Self Billed
Invoice.
EDI
expr.
Comments
Code indicating the
type of business
partner (pay-to)
warehouse. Defaults
to ZZ.
Address/P
artner
Type
Codes
Code indicating the
type of address (shipto, for the delivery
warehouse)
NOTE
The following four addresses may be included in the following level of the
n
n
n
n
Pay-to
Ship-from
Delivery (ship-to)
Invoice-from
Field name
Description
Pos Length
Conv.
HAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
ecedi224.code
Code in Message
Address/
Partner
Type
Codes
EDI
expr.
SFAD
PTAD
IFAD
Comments
Code indicating the
type of business
partner address.
HDRD
EL
tccom130.ccty
Country
SFAD
PTAD
IFAD
HDRD
EL
tccom130.nama Name
35
SFAD
PTAD
IFAD
HDRD
EL
EDI User Guide

8-83

Field name
Description

Pos Length
8
30
Conv.
EDI expr. Comments

SFAD
PTAD
IFAD
HDRDEL
30
SFAD
PTAD
IFAD
HDRDEL
10
30
SFAD
PTAD
IFAD
HDRDEL
tccom130.name City
11
30
SFAD
PTAD
IFAD
HDRDEL
tccom130.namf City 2
12
30
SFAD
PTAD
IFAD
HDRDEL
tccom130.telp
Telephone
15
15
SFAD
PTAD
IFAD
HDRDEL
tccom130.telx
Telex
16
15
SFAD
PTAD
IFAD
HDRDEL
EDI User Guide

8-84

Field name
Description
tccom130.tefx
Fax

Pos Length
17
15
Conv.
EDI expr. Comments

SFAD
PTAD
IFAD
HDRDEL
tccom130.geoc GEO Code
18
10
SFAD
PTAD
IFAD
HDRDEL
19
10
SFAD
PTAD
IFAD
HDRDEL
tccom130.pobn P.O.Box Number
20
10
SFAD
PTAD
IFAD
HDRDEL
tccom130.fovn
Tax Number
21
20
SFAD
PTAD
IFAD
HDRDEL
EDI User Guide

8-85
Field name
Description
HTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur400.txta
Header Text
80
EDI User Guide

8-86
Pos Length
Conv.
EDI
Expr.
Comments

records (user
definable) can be
written.
Level: 5 Order lines mandatory
Field name
Description
Pos Length
LIN
Level Identifier
14
CDL
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
CDL
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur401.pono Position Number
tdpur401.sqnb
Sequence
Number
tdpur401.cprj
Project
tdpur401.item
qual1
tdpur041.item
Item
27
tdpur041.item
Item
10
27
Tcibd001.dsca Description
11
30
tdpur401.oqua Ordered Quantity
12
19
tdpur401.odat
13
22
Order Date
Conv.
EDI
Expr.
Comments

code; default value is
BP.
Item
Codes by
Item
Code
System
If conversion is
defined, alternative
item code; otherwise,
(internal) item code.
(internal) item code..
EDI User Guide

8-87

Field name
Description
tdpur401.ddtb

Pos
Length
Current Planned
Delivery
14
22
tdpur401.ddtc
Confirmed
Delivery Date
14
tdpur401.ddtc
Confirmed
Delivery Date
tdpur401.cuqp
Purchase Unit
tdpur401.pric
EDI
Expr.
Comments
22
CDL
If a confirmed delivery
date is specified, it will
override the current
planned delivery date
value.
15
22
CDL
value.
16
Price
17
19
tdpur401.cupp
Purchase Price
Unit
18
tdpur401.disc
Line Discount
19
Conv.
Unit
Codes
Unit
Codes
20
21
22
23
tdpur401.cvat
Tax Code
24
tdpur401.cvat
qual1
25
tdpur401.cdis
Discount Code
26
27
28
29
30
EDI User Guide

8-88
Tax
Codes
Tax code ID used to
convert tax code.
Discount
Codes by
B. P.

Field name
Description
tdpur401.dmth Discount Method

Pos
Length
Conv.
31
25
Discount
Methods
by B. P.
32
EDI
Expr.
Comments
33
34
35
tdpur401.ldam Discount Amount
36
19
37
38
39
40
tdpur401.lsel
Lot Selection
41
12
tdpur401.clot
Lot
42
16
tdpur401.clot
qual1
43
whltc100.ltbp
Business
Partners Lot
44
12
whltc100.ltbp
qual1
45
tdpur401.leng
Length
46
tdpur401.widt
Width
47
tdpur041.thic
Thickness
48
tdpur401.cmnf Manufacturer
49
tdpur401.cpcl
Product Class
50
tdpur401.sfbp
Ship-from B. P.
52
Lot
Selection
Codes by
B. P.
Lot Code
ID by B.
P.
Lot Code ID indicating

if the lot code is the
senders lot code or
the recipients lot code.
Lot Code
ID by B.
P.

senders lot code or
Business
Partner
EDI User Guide

8-89

Field name
Description
tdpur401.sfbp
Qual1

Pos Length
Conv.
53
54
Address/
Partner
Type
Codes
55
Warehouse
Codes
tdpur401.cwar Qual1
56
tdpur401.cfrw
58
EDI User Guide

8-90
Forwarding Agent
EDI
Expr.
Comments
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
Type Code
business partner
(ship-from)
Address/Partner
Code ID by which to
convert warehouse.
Forwarding
Agent
Codes by
B. P.
Field name
Description
LTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur401.pono
Position Number
Purchase Order Line

number
tdpur401.sqnb
Sequence
Number
Purchase order line

sequence number
tdpur041.txta
Order line text
80
Two text fields are

written per ASCII file
record (where each
text field refers to a line
of text on the order).
Up to 100 records may
be written.
NOTE
Pos Length
Conv.
EDI
Expr.
Comments
n
n
Delivery (ship-to)
Ship-from
EDI User Guide

8-91
Field name
Description
LAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our Identification
17
External reference
companys
identification over
this network (from
Our Identification
field defined for
Network).
tdpur400.orno
Purchase Order
tdpur401.pono
Position Number
Purchase Order Line

number
tdpur401.sqnb
Sequence
Number
Purchase order line

sequence number
ecedi224.code
Code in Message
Address LNSFAD Address/Partner

/Partner
Type Code indicating
LNDEL
Type
the type of business
Codes
partner address.
tccom130.ccty
Country
Country LNSFAD
Codes
LNDEL
35
LNSFAD
tccom130.nama Name
Pos Length
Conv.
EDI
Expr.
LNDEL
10
30
LNSFAD
11
30
LNSFAD
LNDEL
LNDEL
12
30
LNSFAD
LNDEL
EDI User Guide

8-92
Comments

Field name
Description
tccom130.name

Pos Length
13
Conv.
EDI
Expr.
Comments
LNSFAD
LNDEL
tccom130.namf
City 2
14
30
LNSFAD
LNDEL
tccom130.psct
ZIP Code/Postal
Code
15
10
LNSFAD
tccom130.cste
State/Province
16
LNSFAD
tccom130.telp
Telephone
17
15
LNSFAD
LNDEL
LNDEL
LNDEL
tccom130.telx
Telex
18
15
LNSFAD
LNDEL
tccom130.tefx
Fax
19
tccom130.geoc
GEO Code
20
15
LNSFAD
LNDEL
LNSFAD
LNDEL
tccom130.hono
House Number
21
10
LNSFAD
tccom130.pobn
P.O. Box
Number
22
10
LNSFAD
Tax Number
23
LNDEL
tccom130.fovn
LNDEL
20
LNSFAD
LNDEL
EDI User Guide

8-93

Field name
Description
Level: 8 Footer text optional

Pos
Length
Conv.
EDI
Expr.
Comments
FTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur400.txtb
Footer Text
80
EDI User Guide

8-94

internal text; up to 100
(user definable) ASCII
file records.
Conversion setup: 855S, Purchase Order

Acknowledgment
number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Order Header
Level 2
Mandatory
Key: F1, F2, F3
Header Address
Level 3
Key: F1, F2, F3
Order Header Text

Level 4
Key: F1, F2, F3
Order Lines
Level 5
Key: F1, F2, F3, F4, F5
Order Line Text

Level 6
Key: F1, F2, F3, F4, F5
Specific Address
Level 7
Optional
Key: F1, F2, F3, F4, F5
Legend:
F4: Suppliers Order Line (Position) Number
F5: Suppliers Order Line Sequence Number


Message:
855S, Order Acknowledgment
Organization: X12
Field type:
Delimited
EDI User Guide

8-95
NOTE
Conversion setup: Global Overhead

Field name
Description
ENV

Pos
Length
Level Identifier

the Envelope record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address.
ecedi702.msno
Order Reference
20
Business partners
document number.
ecedi702.orga
Organization
The Baan EDI

organization.
ecedi702.mess
EDI Message

code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message

organization, the
message will be
processed as a test
validated, any errors
will be reported, and the
be Received).
ecedi702.send
Date Sent
10
22
The date/time the

message was sent.
NOTE
EDI User Guide

8-96
Conv.
EDI
Expr.
Comments
There are two conversion setups for 855S. The 855S.U updates the purchase
order with any changes indicated in the purchase order acknowledgment. The
855S.C uses the data on the purchase order and purchase order acknowledgment
to generate a report of the changes; it does not update the purchase order.
Conversion setup: 855S.C and 855S.U (In)

Field name
Description
HDR
Pos
Length
Conv.
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
ecedi702.msno
Order Reference
20
Business partners
order number.
tdpur400.orno
Purchase Order
tdpur400.ddtc
Confirmed
Delivery Date
22
tdpur400.refa
Reference A
30
tdpur400.refb
Reference B
20
tdpur400.prno
Contract
14
Purchase
Contract
Codes by
B. P.
tdpur400.cdec
Term of Delivery
15
Terms of
Delivery
Codes
tdpur400.cfrw
Forwarding Agent
17
Forwarding
Agent
Codes by
B. P.
tdpur400.ccrs
Late Payment
Surcharge
19
Late
Payment
Surcharges
tdpur400.cpay
Term of Payment
21
Terms of
Payment
Codes
tdpur400.ccur
Currency
26
Currency
Codes
tdpur400.odis
Order Discount
28
EDI
Expr.
Comments
EDI User Guide

8-97
Field name
Description
Pos
Length
Conv.
tdpur400.cwar
Warehouse
29
Warehouse
Codes
tdpur400.cwar
qual1
30
tdpur400.cofc
Purchase Office
32
tdpur400.cofc
qual1
33
tdpur400.sfbp
Ship-from B. P.
37
tdpur400.sfbp
Qual1
38
tdpur400.sfbp
Qual2
39
tdpur400.akcd
Acknowledg.
Code
46
EDI User Guide

8-98
EDI
Expr.
Comments
warehouse.
Sales/
Purchasing
Office
Codes
office code.
Business
Partners
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

business partner (shipfrom)

Field name
Description
HAD
Level: 3 Order header addresses optional
Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address.
ecedi702.msno
Order Reference
20
Business partners
order number.

Field name
Description
HTX
Conv.
EDI
Expr.
Comments
Pos
Length
Conv.
EDI
Expr.
Comments
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
network address.
ecedi702.msno
Order Reference
20
Business partners
order number.
tdpur400.txta
Header Text
80
There are two text

fields per ASCII file
record; multiple text
tdpur400.txta
Header Text
80
EDI User Guide

8-99

Field name
Description
LIN
Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business Partners
network address.
ecedi702.msno
Order Reference
20
Business Partners
order number.
ecedi705.refn
Reference Line
Number
10
Business Partners
order line (position)
number.
tdpur401.pono
Position Number
Purchase order position

(line) number
tdpur401.sqnb
Sequence
Number
Purchase order line

sequence number
tdpur401.cprj
Project
tdpur401.item
qual1
10
tdpur401.item
Item
11
27
tdpur401.oqua
Ordered Quantity
12
19
tdpur401.cupp
Purchase Unit
16
tdpur401.pric
Price
17
19
tdpur401.cupp
Purchase Price
Unit
18
EDI User Guide

8-100
Conv.
EDI
Expr.
Comments

qual1 is ZZ, no
conversion is
performed.
Item
Codes by
Item
Code
System
Unit
Codes
Unit
Codes
item code.
Field name
Description
Pos
Length
tdpur401.disc
Line Discount
19
Conv.
EDI
Expr.
Comments
20
21
22
23
tdpur401.oamt
Ordered Amount
24
19
tdpur401.ddta
Planned Delivery
Date
25
22
tdpur401.ddtc
Confirmed
Delivery Date
25
22
EDI User Guide

8-101

Field name
Description
tdpur401.cdis
Discount Code
Pos
Length
Conv.
27
Discount Codes
25
Discount
Methods by B. P.
EDI
Expr.
Comments
28
29
30
31
tdpur401.dmth
Discount Method
32
33
34
35
36
tdpur401.ldam
Discount Amount
37
19
38
39
40
41
tdpur401.lsel
Lot Selection
42
12
tdpur400.clot
Lot
43
16
tdpur400.clot
Qual1
44
Lot Code ID by B.
P.
tdpur401.akcd
Purchase
Acknowledgment
47
Purchasing
Acknowledgment
Codes
tdpur401.cwar
Warehouse
48
Warehouse
codes
tdpur401.cwar
qual1
49
tdpur401.sfbp
Ship-from B. P.
51
EDI User Guide

8-102
Lot Code ID
indicating if
the lot code is
the senders
lot code or the
recipients lot
code.
Address/Partn
er Code ID by
which to
convert
warehouse.
Business partner

Field name
Description
tdpur401.sfbp
Pos
Length
qual1
52
tdpur401.sfbp
qual2
53
tdpur401.ddta
Planned Delivery
Date
54
22
tdpur401.cfrw
Forwarding Agent
57
tdpur401.leng
Length
58
tdpur401.widt
Width
59
tdpur401.thic
Thickness
60
tdpur401.ddtf
Order
Confirmation Date
61
22
tdpur401.cvat
Tax Code
62
tdpur401.cvat
qual1
63
Conv.
EDI
Expr.
Comments
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

Tax
Codes
Tax code ID used to
convert tax code; default
is ZZ.
EDI User Guide

8-103
Conversion setup: 855S,C and 855S,U (In)

Field name
Description
LTX
Level: 6 Order line text
Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business Partners
network address.
ecedi702.msno
Order Reference
20
Business Partners
order number.
ecedi705.refn
Reference Line
Number
10
Business Partners
number.
tdpur401.txta
Order line text
80
There are two text fields

per ASCII file record;
multiple text records
can be read.
tdpur401.txta
Order line text
80

Field name
Description
LAD
Conv.
EDI
Expr.
Comments
Level: 7 Order line address - Optional
Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business Partners
network address.
ecedi702.msno
Order Reference
20
Business Partners
order number.
ecedi705.refn
Reference Line
Number
10
Business Partners
number.
EDI User Guide

8-104
Conv.
EDI
Expr.
Comments

Message:
855S, Purchase Order Acknowledgment
Organization: X12
Field type:
Delimited
NOTE
Conversion setup: Global Overhead

Field name
Description
ENV
Level: 1 Envelope Mandatory

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
tdsls400.orno
Sales Order
20
Business Partners
order number.
ecedi028.neta
Network Address
17
Trading Partner
(business partners
network address).
ecedi003.code
Code in Message
Organization (X12).
ecedi003.code
Code in Message
message identifier
(850S).
ecedi011.koor
Order Type in
Message
35
order type.
Constant

constant for test
indicator.
date ( )
Date sent
10
Date message
May include time,
based in the date
organization.
time ( )
Time sent
11
Time message
Conv.
EDI
Expr.
Comments
EDI User Guide

8-105

Field name
Description
HDR
Level: 2 Order header Mandatory

Pos
Length
Conv.
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our Identification
17
External reference
companys
identification over
this network (from
Our Identification
field defined for
Network).
tdsls400.orno
Sales Order
20
Business Partners
order number.
tdsls400.corn
Customer Order
Number
30
tdsls400.odat
Order Date
22
tdsls400.prdt
Planned Receipt
Date
22
tdsls400.refa
Reference A
30
tdsls400.refb
Reference B
20
tdsls400.crep
Inside Sales Rep
10
tccom001.nama
Name
11
tdsls400.orep
Outside Sales
Rep
12
Name
13
tdpur400.prno
Contract
14
Sales
Contract
Codes
tdsls400.cdec
Term of Delivery
15
Terms of
Delivery
Codes
Description
16
30
tdsls400.cfrw
Forwarding Agent
17
EDI User Guide

8-106
Comments
Employee
Codes by
B. P.
tccom001.nama
tcmcs041.dsca
EDI
Expr.
Forwarding
Agent
Codes by
B. P.
Baan delivery code.
Field name
Description
Pos
Length
Conv.
tcmcs080.dsca
Description
18
30
tdsls400.ccrs
Late Payment
Surcharge
19
Late
Payment
Surcharges
tcmcs011.dsca
Description
20
tdsls400.cpay
Terms of Payment
21
Terms of
Payment
Codes
tcmcs013.dsca
Description
22
30
tcmcs013.pper
Payment Period
23
tcmcs013.disa
Discount Period 1
24
tcmcs013.prca
Discount
Percentage
25
tdsls400.ccur
Currency
26
Currency
Codes
tdsls400.ccty
Country
27
Country
Codes
tdsls400.odis
Order Discount
28
tdsls400.stbp
Ship-to Business
Partner
29
tdsls400.stbp
qual1
30
ecedi224.code
Code in Message
31
Address/
Partner
Type
Codes
tdsls400.ofbp
Sold-to Business
Partner
32
Business
Partner
tdsls400.ofbp
qual1
33
EDI
Expr.
Comments
Business
Partner
ID used to convert
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (ship-to)
ID used to convert
business partner.
Defaults to ZZ.
EDI User Guide

8-107

Field name
Description
ecedi224.code

Pos
Length
Conv.
Code in Message
34
Address/Pa
rtner Type
Codes
tdsls400.cofc
Sales Office
35
Sales/
Purchasing
Office
Codes
tdsls400.ofbp
qual1
36
tdsls400.cwar
Warehouse
37
tdsls400.cwar
qual1
38
ecedi224.code
Code in Message
39
Address/
Partner
Type
Codes
tdsls400.itbp
Invoice-to B. P.
40
Business
Partners
tdsls400.itbp
qual1
41
ecedi224.code
Code in Message
42
Address/
Partner
Type
Codes
tdsls400.pfbp
Pay-by B. P.
43
15
Business
Partners
tdsls400.pfbp
qual1
44
EDI User Guide

8-108
EDI
Expr.
Comments
Address/Partner
partner (sold-to)
Address/Partner
Code ID used to
convert business
ZZ.
Warehouse
Codes
Address/Partner
Code ID by which to
convert warehouse.
Address/Partner
the type of address
(ship-from, for the
ship-from
warehouse)
Address/Partner
Code ID by which to
convert business
partner.
Address/Partner
Address/Partner
Code ID by which to
convert business
partner.

Field name
Description
ecedi224.code
tdsls400.akcd
NOTE

Pos
Length
Conv.
Code in Message
45
Address/
Partner
Type
Codes
Sales
Acknowledgement
46
EDI
Expr.
Comments
Code indicating the
type of business partner
(pay-by)
The following five addresses may be included in the following level of the
n
n
n
n
n
Invoice-to
Sold-to
Pay-by
Ship-to
Warehouse (ship-from)
EDI User Guide

8-109
Field name
Description
Pos Length
HAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdsls400.orno
Sales Order
ecedi224.code
Code in Message
Conv.
Address/
Partner
Type
Codes
EDI
Expr.
STAD
Code indicating the
OFAD
type of business
CWAD partner address.
ITAD
PFAD
tccom130.ccty
Country
Country
Codes
STAD
OFAD
CWAD
ITAD
PFAD
EDI User Guide

8-110
Comments

Field name
Description
tccom130.nama Name

Pos Length
7
Conv.
EDI
expr.
Comments
STAD
OFAD
CWAD
ITAD
PFAD
STAD
OFAD
CWAD
ITAD
PFAD
STAD
OFAD
CWAD
ITAD
PFAD
10
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.name City
10
11
STAD
OFAD
CWAD
ITAD
PFAD
EDI User Guide

8-111

Field name
Description
tccom130.namf
City 2

Pos Length
12
30
Conv.
EDI
Expr.
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.pstc
ZIP Code/Postal
Code
13
10
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.cste
State/Province
14
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.telp
Telephone
15
15
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.telx
Telex
16
15
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.tefx
Fax
17
15
STAD
OFAD
CWAD
ITAD
PFAD
EDI User Guide

8-112
Comments
Conversion setup: 855S (Out)Level: 3 Order header addresses optional

Field name
Description
tccom130.geoc
GEO Code
Pos Length
18
10
Conv.
EDI
Expr.
Comments
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.hono
House Number
19
10
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.pobn
P.O. Box Number
20
10
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.fovn
Tax Number
19
20
STAD
OFAD
CWAD
ITAD
PFAD
EDI User Guide

8-113

Field name
Pos
Length
Level Identifier
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdsls400.orno
Sales Order
tdsls400.txta
Header Text
80
HTX
EDI User Guide

8-114
Description

Conv.
EDI
Expr.
Comments

order header text; up to
100 records (user
definable) can be
written.

Field name
Description
LIN

Pos
Length
Conv.
Level Identifier
ecedi701.bano
Our Reference
14
ecedi020.neta
Our Identification
17
tdsls400.orno
Sales Order
tdsls401.pono
Position Number
tdsls401.sqnb
Sequence
Number
tdsls401.corp
Customer Order
Position
16
Customer order line

number.
tdsls401.cors
Customer Order
Sequence
11
Customer order line

sequence number
tdsls401.cprj
Project
tdsls401.item
qual1
10
tdpur401.item
Item
11
47
tdpur401.item
Item
12
47
Unconverted item:
(internal) item code is
written to file.
tcibd001.dsca
Description
13
30
Item description
tdsls401.oqua
Ordered Quantity
14
19
tdsls401.bqua
Back Order
Quantity
15
19
tdsls401.cuqp
Sales Unit
16
tdsls401.pric
Price
17
19
tdsls401.cups
Sales Price Unit
18
EDI
expr.
Comments
Business Partners
order number.

code. Defaults to BP.
Item
Code by
Item
Code
Systems
Converted Item: If
item code is written to
file.
Unit
Codes
Unit
Codes
EDI User Guide

8-115
Conversion setup: u55S (out)
Field name
Description
Pos
Length
tdsls401.disc
Line Discount
19
Conv.
EDI Comments
expr.
20
21
22
23
tdsls401.oamt
Amount
24
19
tdsls401.prdt
Planned Receipt
Date
25
22
tdsls401.odat
Order Date
26
22
tdsls401.cdis
Discount Code
27
Discount
Codes by
B. P.
25
Discount
Methods
by B. P.
28
29
30
31
tdsls401..dmth
Discount Method
32
33
34
35
36
tdsls401.ldam
Discount Amount
37
19
38
39
40
41
tdsls401.lsel
Lot Selection
42
12
tdsls401.clot
Lot
43
16
tdsls401.clot
qual1.
44
EDI User Guide

8-116
Lot Code
ID by
Business
Partner

whether the lot code is
the senders lot code or

Field name
Description
whltc100.ltbp
Pos
Length
Conv.
Business Partners
Lot
45
30
whltc100.ltbp
qual1
46
Lot Code
ID by
Business
Partner
tdsls401.akcd
Sales
Acknowledgment
47
Sales Ack.
Codes
tdsls401.stbp
Ship-to Business
Partner
48
Business
partner
tdsls401.stbp
qual1
49
ecedi224.code
Code in Message
50
Address/
Partner
Type
Codes
tdsls401.cwar
Warehouse
51
Warehouse
codes
tdsls401.cwar
qual1
52
ecedi224.code
Code in Message
53
tdsls401.ddta
Planned Delivery
Date
54
22
tdsls401.dldt
Delivery Date
55
22
tdsls401.dqua
Delivered Quantity
56
19
tdsls401.cfrw
Forwarding Agent
57
tdsls401.lngth
Length
58
tdsls401.widt
Width
59
tdsls401.thic
Thickness
60
EDI Comments
expr.

the senders lot code
or the recipients lot
code.
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (ship-to)
warehouse.
Address/
Partner
Type
Codes
Code indicating the
type of address (shipfrom, for the ship-from
warehouse)
EDI User Guide

8-117

Field name
Description
date()
Pos
Length
Date/Time
61
22
tdsls401.cvat
Tax Code
62
tdsls401.cvat
qual1
63
EDI User Guide

8-118
Conv.
EDI
expr.
Comments
Date/time that the EDI
message was
generated, based on
date format defined for
the organization. This is
intended to be used as
the confirmation date for
the line.
Tax
Codes
Tax code ID used to
convert tax code;
default is ZZ.

Field name
Description
LTX
Level: 6 Order line text - optional

Pos
Length
Conv.
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
EDI
expr.
Comments
tdsls400.orno
Sales Order
Business Partners
order number.
tdsls401.pono
Position Number
Business Partners
number.
tdsls401.sqnb
Sequence
Number
tdsls401.txta
Order Line Text
80
NOTE

records (user
definable) can be
written.
n
n
Ship-to
EDI User Guide

8-119

Field name
Description
LAD
Level: 7 Order line addresses - optional

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference. Must be
unique for business
partner.
ecedi020.neta
Our Identification
17
External reference
Sales Order
tdsls401.pono
Position Number
Sales order line number
tdsls401.sqnb
Sequence
Number
Sales order line

sequence number
ecedi224.code
Code in Message
Address/
Partner
Type
Codes
tccom130.ccty
Country
Country
Codes
tdsls400.orno
tccom130.nama
Name
35
Conv.
EDI
expr.
LNSTAD Address/Partner Type

Code indicating the
CWAD
type of business
partner address.
LNSTAD
CWAD
LNSTAD
CWAD
EDI User Guide

8-120
Comments
Conversion setup: 855S (Out) Level: 7 Order line addresses - optional

Field name
Description
Pos
Length
Conv.
10
30
LNSTAD
11
30
LNSTAD
EDI
expr.
Comments
CWAD
CWAD
12
30
LNSTAD
CWAD
tccom130.name City
13
30
LNSTAD
tccom130.namf
14
30
LNSTAD
CWAD
City 2
CWAD
tccom130.pstc
ZIP Code/Postal
Code
15
10
LNSTAD
tccom130.cste
State/Province
16
LNSTAD
tccom130.telp
Telephone
17
15
LNSTAD
CWAD
CWAD
CWAD
tccom130.telx
Telex
18
15
LNSTAD
tccom130.tefx
Fax
19
15
LNSTAD
CWAD
CWAD
tccom130.geoc
GEO Code
20
10
LNSTAD
CWAD
tccom130.hono
House Number
21
10
LNSTAD
tccom130.pobn
P.O. Box Number
22
10
LNSTAD
CWAD
CWAD
tccom130.fovn
Tax Number
23
20
LNSTAD
CWAD
EDI User Guide

8-121
Conversion setup: 856, Shipment Notice

number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Shipment Header
Level 2
Mandatory
Key: F1, F2, F3
Shipment Address
Level 3
Key: F1, F2, F3
Shipment Header Text

Level 4
Key: F1, F2, F3
Shipment Routings
Level 5
Key: F1, F2, F3
Shipment Packaging
Level 6
Key: F1, F2, F3
Shipment Lines
Level 7
Key: F1, F2, F3, F4
Shipment Line Text

Level 8
Key: F1, F2, F3, F4
Packing (Load) Structure

Level 9
Key: F1, F2, F3, F4
Legend:
F3: Shipment ID
F4: Shipment Line (Position) Number

Message:
856S, Shipment Notice
Organization: X12
NOTE
EDI User Guide

8-122
EDI Information (Text)

Level 10
Key: F1, F2, F3

F3: Shipment ID
F4: Shipment Line (Position) Number

Field name
Description
ENV
Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
ecedi702.bpid
Business
Partner
ecedi702.msno Order
Reference
ecedi702.orga Organization
20
ecedi702.koor
Order Type in
Message
35
ecedi702.test
Test Message
Date Sent
10
22
ecedi702.send
Conv.
EDI
expr.
Comments
the Envelope record
Unique message
reference. Must be
unique for business
partner.
Business partners
identification as
defined in business
partners network
address.
Business partners
document number.
The Baan EDI
organization.
The Baan EDI
message code.
order type (code in
message).
non-blank and
matches the value
defined for the
organization, the
message will be
processed as a test
will be reported, and
the message will be
stored in Saved
Messages to be
Received).
The date/time the
message was sent.
EDI User Guide

8-123

Field name
Description
HDR
ecedi702.bano
ecedi702.bpid
Level: 2 Shipment Notices Header mandatory

Pos
Length
Level Identifier
Message
Reference
1
2
3
35
Business
Partner
ASN Receipt
Nr.
10
whinh300.stat
EDI Status
25
whinh300.shdt
whinh300.pddt
6
7
22
22
8
9
19
3
whinh300.wght
whinh300.cwun
whinh300.cwar
Shipping Date
Planned
Delivery Date
Freight Value
Terms of
Delivery
Gross Weight
Unit of Measure
Warehouse
10
11
12
19
3
6
whinh300.cwar
qual1
13
whinh300.hazm Hazardous
Material
whinh300.koch Kind of Charge
18
19
15
whinh300.cham
whinh300.bola
whinh300.pcsp
whinh300.curr
20
21
21
22
19
6
6
3
whinh302.asnr
whinh300.fval
whinh300.cdec
EDI User Guide

8-124
Charge Amount
Bill of Lading
Packing Slip
Currency
Conv.
Shipment
Status
Codes
EDI Comments
expr.
Unique message
reference. Must be
unique for business
partner.
Number (Suppliers
ASN Number or SID).
Indicates if this is an
original shipment
notice or a canceling
shipment notice. A
valid Shipment Status
Code is required.
Unit Codes
Warehouse
codes
warehouse.
Kind of
Charge
Currency
Codes

Field name
Description
Level: 2 Shipment Notices Header - mandatory

Pos
Length
Conv.
Business
partner
whinh300.sfbp
Ship-from
Business Part
23
whinh300.sfbp
qual1
24
whinh300.sfbp
qual2
25
Address/
Partner
Type
codes
EDI
expr.
Comments
overhead records
business partner if
blank.
business partner.
EDI User Guide

8-125

Field name
Description
Level: 3 Shipment Header address- optional

Pos Length
Conv.
EDI
expr.
Comments
HAD
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
whinh302.asnr
ASN Receipt
Nr.
10
ecedi224.code
Code in Message
Address/
Partner
Type
Codes
tccom130.ccty
Country
Country
Codes
tccom130.nama
Name
35
tccom130.namb
Name 2
30
tccom130.namc
Address
30
tccom130.namd
Address 2
10
30
tccom130.name
City
11
30
tccom130.namf
City 2
12
30
tccom130.pstc
ZIP Code/Postal
Code
13
10
tccom130.cste
State/Province
14
tccom130.telp
Telephone
15
15
tccom130.telx
Telex
16
15
tccom130.tefx
Fax
17
15
tccom130.geoc
GEO Code
18
10
tccom130.hono
House Number
19
10
tccom130.pobn
P.O. Box Number
20
10
tccom130.fovn
Tax Number
21
20
EDI User Guide

8-126
Number (Suppliers
ASN Number or SID).
address

Field name
Description
HTX
Level: 4 Shipment Header Text - optional

Pos
Length
Conv.
Level identifier
ecedi702.ban
o
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
EDI
expr.
Comments
whinh302.asnr ASN Receipt

Nr.
10
Number (Suppliers
ASN Number or SID).
whinh300.text
Text
80
Two text fields per

ASCII file record;
multiple ASCII file
whinh300.text
Text
80
EDI User Guide

8-127

Field name
Description
Level: 5 Shipment Routings - optional

Pos Length
Conv.
EDI
expr.
Comments
SNR
Level identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
whinh302.asnr
ASN Receipt
Nr.
10
whinh315.rscd
Routing
Sequence Code
whinh315.edcd
Equipment
Description Code
whinh315.eqin
Equipment Initial
whinh315.eqnr
Equipment
Number
10
10
whinh315.seal
Seal Number
11
15
whinh315.carr
Carrier
12
EDI User Guide

8-128
Shipment
Identification
Number (Suppliers
ASN Number or
SID).
Forwarding
Agent Code
by B. P.

Field name
Description
Level: 6 Shipment Packaging optional

Pos Length
Conv.
EDI
expr.
Comments
SNP
Level identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
whinh302.asnr
ASN Receipt
Nr.
10
whinh303.pkcd
Package unit
whinh303.pkqu
Package Quantity
19
whinh303.pkwt
Packaging
Weight
10
whinh303.cwun
Unit of Measure
Number (Suppliers
ASN Number or SID).
Unit
Codes
Unit
Codes
EDI User Guide

8-129

Field name
Description
Level: 7 Shipment Notice Lines - mandatory

Pos Length
Conv.
EDI
expr.
Comments
LIN
Level identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
whinh302.asnr
ASN Receipt
Nr.
10
Number (Suppliers
ASN Number or SID).
ecedi705.refn
Reference Line
Number
10
Suppliers Shipment
Line Number
whinh301.item
qual1

qual1 is ZZ, no
conversion is
performed.
whinh301.item
Item
47
whinh301.squa
Shipped Quantity
in Inventory unit
19
whinh301.cums
CUM Shipped
10
19
whinh301.cuni
Unit of Measure
11
whinh301.grwt
Gross Weight
12
10
whinh301.ntwt
Net Weight
13
10
whinh301.cwun
Unit of Measure
14
whinh301.worn
Warehouse
Order Number
17
Purchase Order
Number or Purchase
Release Number
whinh301.wpon
Warehouse
Position Number
18
Purchase Order line

Number or Purchase
Release line Number
EDI User Guide

8-130
Item
codes by
Item
code
system
If conversion is
Unit
Codes
Unit
Codes

Field name
Description
Level: 7 Shipment Notice Lines - mandatory

Pos Length
whinh301.wsqn.
Sequence
Number
19
whinh301.clot
Lot
25
16
whinh301.clot
qual1
26

Field name
Description
Conv.
EDI
expr.
Comments
Purchase Order line
sequence Number or
Purchase Release
Order line sequence
Number
Lot Code
ID by
Business
Partner

code.
Level: 8 Shipment Line Text- optional

Pos Length
Conv.
EDI
Expr.
Comments
LTX
Level identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
whinh302.asnr
ASN Receipt
Nr.
10
ecedi705.refn
Reference Line
Number
10
whinh301.text
Text
80
Two text fields per

ASCII file record;
multiple ASCII file
whinh301.text
Text
80
Two text fields per

ASCII file record;
multiple ASCII file
Number (Suppliers
ASN Number or SID).
EDI User Guide

8-131

Field name
Description
Level: 9 Item Load Structure optional

Pos Length
Conv.
EDI
Expr.
Comments
ILS
Level identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
whinh302.asnr
ASN Receipt
Nr.
10
ecedi705.refn
Reference Line
Number
10
whinh317.ncon
Number of
Containers
19
whinh317.nupc
Number of Units
per Container
19
whinh317.pkcd.
Packaging Unit

Field name
Description
Number (Suppliers
ASN Number or SID).
Unit
Codes
Level: 10 EDI Information mandatory

Pos Length
Conv.
EDI
Expr.
Comments
ATX
Level identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
whinh302.asnr
ASN Receipt
Nr.
10
Number (Suppliers
ASN Number or SID).
whinh300.iedi
EDI Information
80
Free form (text). Two

text fields per ASCII
ASCII file records can
be read.
whinh300.iedi
EDI Information
80
Free form (text)
EDI User Guide

8-132

Message:
856S, Shipment Notice
Organization: X12
NOTE
EDI User Guide

8-133

Field name
Description
ENV
Pos
Length
Level identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
whinh430.shpm
Shipment
Identification
number (suppliers SID
or ASN Number)
ecedi028.neta
Network
Address
17
Trading Partner
(business partners
network address).
ecedi003.code
Code in
Message
Organization (X12).
ecedi001.code
Code in
Message
message identifier (for
example, 856S).
ecedi011.koor
Order Type in
Message
35
order type. This field is
blank for this message.
Constant
Record Identifier (EDI

Overhead).
date()
Todays Date
10
Date message
May include time,
based in the date
organization.
time()
Current Time
11
Time message
EDI User Guide

8-134
Conv.
EDI
expr.
Comments
Level: 2 Shipment Header- mandatory
Field name
Description
Pos Length
Conv.
HDR
Level identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
Identification
Shipment
Identification number
(suppliers SID or ASN
number)
whinh430.stat
EDI Status
25
whinh430.cdat
Date
22
whinh430.pddt
Planned Delivery
Date/T
22
whinh430.fval
Freight Value
19
whinh430.cdec
Terms of Delivery
whinh430.wght
Total Weight
10
10
whinh430.wght
Location Weight
Unit of Measure
11
10
Unit
Codes
whinh430.stco
Ship to Code
12
Business
Partner
Shipment
Status
Codes
EDI
expr.
Comments
Indicates if the
shipment notice is an
original shipment
notice or a canceling
shipment notice. An
EDI Status of
Confirmed represents
an original ASN; an
EDI status of
Disapproved
represents a
canceling ASN. (see
Chapter 6 for more
information).
Terms of
Delivery
Codes
EDI User Guide

8-135
whinh430.stco
qual1
13
ecedi224.code
Code in Message
14
Address/
Partner
Type
Codes
whinh430.itbp
Invoice-to
Business Partner
15
Business
Partner
whinh430.itpb
qual1
16
ecedi224.code
Code in Message
17
whinh430.risk
Class of Risk
18
15
whinh430.koch
Kind of Charge
19
15
whinh430.cham Charge Amount
20
19
Identification
21
whinh430.curr
22
NOTE
Currency
8-136
Code indicating the
type of business
partner (ship-to)
business partner.
Address/
Partner
Type
Codes
Code indicating the
type of business
Kind of
Charge
Shipment
Number)
Currency
Codes
n
EDI User Guide
business partner.
Ship-to
Level: 3 Shipment Header Address- optional
Field name
Description
HAD
Level identifier
Identifies the
record.
ecedi701.bano
Our Reference
14
Baan unique
message ID
number.
ecedi020.neta
Our Identification
17
External reference
(VAN ID) of the
Baan companys
identification over
this network (from
Our Identification
field defined for
Network).
Shipment
Identification
Shipment
Identification
number (suppliers
SID or ASN
Number)
ecedi224.code
Code in Message
Address/
Partner
Type
Codes
tccom130.ccty
Country
Country
Codes
tccom130.nama Name
35
WHSTAD
30
WHSTAD
30
WHSTAD
10
30
WHSTAD
whinh430.shp
m
Pos Length
Conv.
EDI expr. Comments
WHSTAD Address/Partner
Type Code
indicating the type
of address
WHSTAD
EDI User Guide

8-137

Field name
Description
Level: 3 Shipment Header Address- optional

Pos Length
Conv.
EDI expr. Comments
tccom130.name City
11
30
WHSTAD
12
30
WHSTAD
tccom130.pstc
Zip Code/Postal
Code
13
10
WHSTAD
tccom130.cste
State/Province
14
WHSTAD
tccom130.telp
Telephone
15
15
WHSTAD
tccom130.telx
Telex
16
15
WHSTAD
tccom130.tefx
Fax
17
15
WHSTAD
tccom130.geoc
GEO Code
18
10
WHSTAD
tccom130.hono
House Number
19
10
tccom130.pobn
P.O. Box Number
20
10
tccom130.fovn
Tax Number
21
20
WHSTAD
Level: 4 Shipment Header Text - optional
Field name
Description
HTX
Level identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
Identification
Shipment
Number)
whinh430.text
80

text. Up to 100
records (as defined
within the conversion
setups) can be
written.
EDI User Guide

8-138
Text
Pos Length
Conv.
EDI
expr.
Comments
Level: 5 Shipment Routings optional
Field name
Description
Pos Length
SNR
Level identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
identification over
this network (from
Our Identification
field defined for
Network)
whinh430.shp
m
Shipment
Identification
Shipment
(suppliers SID or
ASN Number)
whinh415.rscd
Routing
Sequence Code
tcmcs080.scac
Standard
Carrier Alpha
Code
20
tcmcs080.trmd
Transport
Category
15
whinh415.edcd Equipment
Description
whinh415.eqin
Equipment
Initial
whinh415.eqnr
Equipment
Number
10
10
whinh415.seal
Seal Number
11
15
whinh415.carr
Carrier
12
Conv.
EDI
expr.
Comments
(SCAC)
Forwarding
Agent
EDI User Guide

8-139

Field name
Description
SNP
Level: 6 Clustered Shipment Lines optional

Pos
Length
Conv.
EDI Comments
expr.
Level identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification 3
17
External reference
companys
network (from Our
Identification
or ASN Number)
whinh432.seqn
Position Number
Shipment line number
whinh432.cuni
Unit of Measure
whinh432.dqua
Shipped Quantity
19
whinh432.grwt
Gross Weight
10
whinh432.cwun
Unit of Measure
EDI User Guide

8-140
Unit
Codes
Unit
Codes

Field name
Description
Level: 7 Shipment Lines mandatory

Pos Length
Conv.
EDI Comments
expr.
LIN
Level identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
identification over
this network (from
Our Identification
field defined for
Network).
Identification
Shipment
(suppliers SID or
ASN Number)
whinh432.seqn
Position
Number
whinh431.item
Qual1
whinh431.item
Item
47
tcibd001.dsca.
Description
12
whinh431.qshp
Shipped
Quantity in
Inventory unit
19
tdsls.309.shcm
Shipped
Cumulative
10
19
whinh431.cuni
Unit of Measure
11
whinh431.grwt
Gross Weight
12
10
whinh431.ntwt
Net Weight
13
10
whinh431.cwun
Unit of Measure
14
whinh220.qstk
Ordered
Quantity in Inv
15
19
tcibd001.cuni
Inventory Unit
16
Item Code ID ,
system, used to
convert item code.
Defaults to BP.
Item codes
by item
code
system
If conversion exists,
item code.
Schedule cumulative
quantity
Unit Codes
Unit Codes WUOM
Unit Codes
EDI User Guide

8-141

Field name
Description

Pos Length Conv. EDI expr. Comments
tdsls308.pchn
Customer
Release
17
30
ORGSHD The customers

document reference
number is written to
position 17. This may
be either a customer
PO number or a
customer purchase
release number.
tdsls401.corn
Customer Order
Number
17
30
ORGSHD
tdsls308.prev
Customer
Release
Revision
18
14
ORGSHD If the document against

which the shipment is
made is a purchase
release, the release
revision is written to
position 18.
EDI User Guide

8-142
Field name
Description
tdsls401.corp
Customer
Order
Position
18
16
ORGSHD
Customer order line

number. If the
document against
which the shipment is
made is a purchase
order, the customer
order line number is
written to position 18.
tdsls308.ppon
Customer
Release
Position
19
16
ORGSHD
If the document
against which the
shipment is made is
a purchase release,
the Customer
Release Line number
is written to position
19.
tdsls401.cors
Customer
Order
Sequence
19
11
ORGSLS
If the document
against which the
shipment is made is
a purchase order, the
Customer order line
sequence number is
written to position 19.
whinh431.cwar Warehouse
20
whinh431.cwar Qual1
21
ecedi224.code Code in
Message
22
whltc100.ltbp
23
30
Business
Partners Lot
Pos Length
Conv.
EDI expr. Comments
Warehouse
Codes
Address/Partner
Code ID by which to
convert warehouse.
Defaults to ZZ.
Address/
Partner
Type Codes
Address/Partner
the type of address
(ship-from, for the
warehouse from
which goods were
shipped)
EDI User Guide

8-143
whltc100.ltbp
Qual1
24
whinh431.clot
Lot
25
16
whinh431.clot
Qual1
26
Lot Code ID
by Business
Partner
Lot Code ID
indicating whether
the lot code is the
senders lot code or
the recipients lot
code.
Lot Code ID
by Business
Partner
Lot Code ID
indicating whether
the lot code is the
senders lot code or
the recipients lot
code.
Conversion setup: 856 (Out)

Field name
Description
Level: 8 Shipment Line Text optional

Pos Length
Conv.
EDI
expr.
Comments
LTX
Level identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
or ASN Number)
Identification
whinh431.pono
Position
Number
whinh431.text
Text
80
EDI User Guide

8-144

(as defined within the
conversion setups) can
be written.
Level: 9 Packing Structure - optional
Field name
Description
ILS
Level identifier
ecedi701.bano
Our Reference
14

number.
ecedi020.neta
Our
Identification
17

network (from Our
for Network).
Identification
number (suppliers SID or
ASN Number)
whinh431.pono
Position
Number
Pos Length
whinh316.npac
Quantity
19
whinh316.quin
Quantity in
Inventory Unit
19
whinh316.pkcd
Packaging Unit

Field name
Description
Conv.
EDI Comments
expr.
Unit
Codes
Level: 10 EDI Information - optional
Pos Length
Conv.
EDI Comments
expr.
ATX
Level identifier
ecedi701.bano
Our Reference
14

number.
ecedi020.neta
Our
Identification
17

network (from Our
for Network).
Identification
number (suppliers SID or
ASN Number)
whinh430.iedi
80
Free form text. One record

is written for every two
lines of header text. Up to
100 records (user
definable) can be written.
EDI Information
EDI User Guide

8-145

Change
number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Order Header
Level 2
Mandatory
Key: F1, F2, F3
Specific Address
Level 3
Key: F1, F2, F3
Order Header Text

Level 4
Key: F1, F2, F3
Order Line Text

Level 6
Key: F1, F2, F3, F4, F5
Order Lines
Level 5
Key: F1, F2, F3, F4, F5
Order Footer Text

Level 8
Key: F1, F2, F3
Specific Address
Level 7
Key: F1, F2, F3, F4, F5
Legend:
F3: Order Number
EDI User Guide

8-146

F3: Customer Order Number
F4: Customer Order Line (Position) Number
F5: Customer Order Line Sequence Number

Message:
860S, Purchase Order Change
Organization: X12
NOTE
Field name
Description
Pos Length Conv.
EDI
expr.
Comments
ENV
Level Identifier

the Envelope record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be unique
for business partner.
ecedi702.bpid
Business
Partner
Business partners
business partners
network address.
ecedi702.msno
Order
Reference
20
Business partners
document number.
ecedi702.orga
Organization
The Baan EDI

organization.
ecedi702.mess
EDI Message

code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message

in this field is non-blank
and matches the value
defined for the
organization, the
message will be
processed as a test
Received).
ecedi702.send
Date Sent
10
22
The date/time the

message was sent.
EDI User Guide

8-147
Level: 2 Order header - mandatory
Field name
Description
HDR
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
tdsls400.corn
Customer Order
Number
tdsls400.ctcd
Change Type
30
Change
Type
Codes
tdsls400.crcd
Change Reason
Change
Reason
Codes
tdsls400.cosn
Change Order
Sequence
Number
tdsls400.odat
Order Date
22
tdsls400.ddat
Plan Del. Date
10
tdsls400.prdt
Planned
Receipt Date
11
22
tdsls400.refa
Reference A
12
30
tdsls400.refb
Reference B
13
20
tdsls400.prno
Contract
14
tdsls400.cdec
Term of
Delivery
15
Terms of
Delivery
Codes
tdsls400.cfrw
Forwarding
Agent
17
Forwarding
Agent
Codes by
B. P.
tdsls400.ccrs
Late Payment
Surcharge
19
Late
Payment
Surcharges
EDI User Guide

8-148
Pos Length
Conv.
22
EDI
expr.
Comments
Indicate the type of

change made.

Field name
Description

Pos Length
Conv.
tdsls400.cpay Terms of
Payment
21
Terms of
Payment
Codes
tdsls400.ccur
Currency
26
Currency
Codes
tdsls400.ccty
Country
27
Country
Codes
tdsls400.cpls
Sales Price List
28
tdsls400.creg
Area
29
tdsls400.cbrn
Line of Business
30
tdsls400.odis
Order Discount
31
tdsls400.ofbp
Sold-to Business
Partner
32
tdsls400.ofbp
qual1
33
tdsls400.ofbp
qual2
34
Address/
Partner
Type codes
tdsls400.cofc
Sales Office
35
Sales/
Purchasing
Office
Codes
tdsls400.cofc
qual1
36
tdsls400.cwar
Warehouse
38
tdsls400.cwar
qual1
39
tdsls400.stbp
Ship-to Business
Partner
47
Business
Partner
EDI
expr.
Comments

overhead records
business partner if
blank.
Address/Partner
Code ID used to
convert business
ZZ.
business partner
(sold-to)
Address/Partner
Code ID used to
convert office codes.
Defaults to ZZ.
Warehouse
Codes
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Business
Partners
EDI User Guide

8-149
Field name
Description
tdsls401.stbp
qual1
48
tdsls400.stbp
qual2
49
50
tdsls400.sbim Self Billed

Invoice
EDI User Guide

8-150
Pos Length
Conv.
EDI
expr.
Comments
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

Yes/no
Field name
Description
Pos Length
Conv.
HAD
Level Identifier
tcedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
tdsls400.corn
Customer
Purchase Order
Number
30
ecedi224.code
code in message
Address/
Partner
Type
Codes
tccom130.ccty
Country
Country
Codes
tccom130.nama Name
35
30
30
10
30
tccom130.name City
11
30
tccom130.namf
City 2
12
30
tccom130.pstc
Zip Code
13
10
tccom130.cse
State/Province
14
tccom130.telx
Telephone
15
15
tccom130.tefx
Telex
16
15
tccom130.tefx
Fax
17
15
tccom130.cste
GEO Code
18
10
tccom130.fovn
Tax Number
19
20
EDI
expr.
Comments
Code indicating the
type of address.
EDI User Guide

8-151
Field name
Description
HTX
Level
Identifier
tcedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
tdsls400.corn
Customer
Purchase
Order
30
tdsls400.txta
Header Text
80
tdsls400.txta
Header Text
80
EDI User Guide

8-152
Pos Length
Conv.
EDI
expr.
Comments
Two text fields per

ASCII file record;
multiple ASCII file
Field name
Description
LIN
ecedi702.bano
Level Identifier
Message
Reference
1
2
3
35
ecedi702.bpid
30
16
11
tdsls401.ctcd
Business
Partner
Customer Order
Number
Customer Order
Position
Customer Order
Sequence
Change Type
tdsls401.crcd
Change Reason
tdsls401.item
qual1
11
tdsls401.item
Item
12
47
tdsls041.oqua
15
19
16
17
22
22
18
22
tdsls401.cuqs
Ordered
Quantity
Order Date
Planned
Delivery Date
Planned
Receipt Date
Sales Unit
19
tdsls401.pric
Price
20
19
tdsls400.corn
tdsls401.corp
tdsls401.cors
tdsls401.odat
tdsls401.ddta
tdsls401.prdt
Pos Length
Conv.
EDI Comments
expr.
Unique message
reference. Must be unique
for business partner.
Sales
Change
Type
Codes
Sales
Change
Reason
Codes
Item code
by item
code
system
Unit
Codes
Item Code ID, referring to

item code system, used to
convert item code. Defaults
to BP. If qual1 is ZZ, no
conversion is performed.
code.
Unit of measure
sold/delivered.
EDI User Guide

8-153

Field name
Description
tdsls401.cups

Po
s
Length
Conv.
Sales Price Unit
21
Unit
Codes
tdsls401.disc
Line Discount
tdsls401.cvat
Tax Code
22
23
24
25
26
27
tdsls401.cdis
qual1
28
tdsls401.cdis
Discount Code
29
30
31
32
33
Discount
Codes
tdsls401.dmth
Discount Method
34
25
Discount
Methods
by B. P.
35
38
39
19
40
41
42
43
tdsls401.lsel
Lot Selection
44
12
tdsls401.clot
Lot
45
16
EDI User Guide

8-154
Unit of measure for

sales price.
Tax code ID used to

convert tax code;
defaults to ZZ. No
conversion is
performed if value is
ZZ.
37
Discount Amount
Comments
Tax
Codes
36
tdsls401.ldam
EDI
expr.
Lot
Selection
Codes by
B. P.
Field name
Description
tdsls401.clot
qual1
46
tdsls401.leng
Length
49
tdsls401.widt
Width
50
tdsls401.thic
Thickness
51
tdsls401.cmnf Manufacturer
52
tdsls401.cpcl
Product Class
53
tdsls401.cpln
Product Line
54
tdsls401.cwar
Warehouse
55
tdsls401.cwar qual1
56
tdsls401.stbp
58
tdsls401.stbp. qual1
59
tdsls401.stbp
qual2
60
Address/
Partner
Type codes
tdsls401.cfrw
Forwarding
Agent
61
Forwarding
Agent
Codes by
B. P.
Ship-to Business
Partner
Pos Length
Conv.
Lot Code
ID by B. P.
EDI
expr.
Comments
Lot Code ID
indicating whether
the lot code is the
senders lot code or
the recipients lot
code.
Warehouse
Codes
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Business
Partners
Address/Partner
Code ID used to
convert business
ZZ.
business partner
(ship-to)
EDI User Guide

8-155

Field name
Description
LTX
ecedi702.bano

Pos
Length
Conv.
Level Identifier
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
EDI
expr.
Comments
ecedi702.bpid
Business Partner
tdsls400.eono
Customer Order
Number
30
tdsls401.corp
Customer Order
Position
16
Customer order line

number
tdsls041.cors
Customer Order
Sequence
11
Customer order line

sequence number (if
business partners
application supports
subline deliveries)
tdsls401.txta
Order line text
80
Two text fields per

ASCII file record;
multiple ASCII file
tdsls401.txta
Order line text
80
EDI User Guide

8-156

Field name
Description
LAD
Level: 7 Lines specific address - optional

Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
tdsls400.corn
Customer Order
Number
30
Customer order line

number
tdsls401.corp
Customer Order
Position
16
Customer order line

sequence number (if
business partners
application supports
subline deliveries)
tdsls401.cors
Customer Order
Sequence
11
Two text fields per

ASCII file record;
multiple ASCII file
ecedi240.code
Code in
Message
tccom130.ccty
Country
tccom130.nama Name
35
10
30
tccom130.namc
11
30
Address
12
30
tccom130.name City
13
30
14
30
tccom130.pstc
Zip Code/Postal
Code
15
10
tccom130.cste
State/Province
16
tccom130.telp
Telephone
17
15
tccom130.telx
Telex
18
15
tccom130.tefx
Fax
19
15
tccom130.geoc
GEO Code
20
10
Conv.
EDI Comments
expr.
Country
Codes
EDI User Guide

8-157

Field name
Description
Level: 7 Lines specific delivery address - optional

Pos
Length
19
10
tccom130.pobn P.O. Box

Number
20
10
tccom130.fovn
21
20
Tax Number

Field name
EDI
expr.
Comments
Level: 8 Order Footer Text - optional

Pos
Length
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
tdsls400.corn
Customer Order
Number
30
tdsls400.txtb
Footer Text
80
tdsls400.txtb
Footer Text
80
FTX
EDI User Guide

8-158
Description
Conv.
Level Identifier
Conv.
EDI
expr.
Comments
Two text fields per

ASCII file record;
multiple ASCII file

Message:
860S, Purchase Order Change
Organization: X12
NOTE

Field name
Description
Pos Length Conv.
EDI
expr.
Comments
ENV
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17

ID) of the Baan
tdpur400.orno
Purchase Order
ecedi028.neta
Network
Address
17
Trading Partner
(business partners
network address).
ecedi003.code
Code in
Message
Organization (X12).
ecedi001.code
Code in
Message
example, 860S).
ecedi011.koor
Order Type in
Message
35
order type.
Constant

constant for test
indicator.
date()
Todays Date
10

time, based in the date
organization.
time()
Current Time
11
Time message extracted

from BAAN.
EDI User Guide

8-159
Field name
Description
HDR
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our
Identification
17
External reference
(VAN ID) of the
Baan companys
identification over
this network (from
Our Identification
field defined for
Network).
tdpur400.orno
Purchase Order
tdpur400.ctcd
Change Type
Purchasing
Change
Type Codes
tdpur400.crcd
Change Reason
Purchasing
Change
Reason
Codes
tdpur400.cosn
Change Order
Sequence
Number
tdpur400.odat
Order Date
22
tdpur400.ddat
Delivery Date
10
22
EDI User Guide

8-160
Pos Length
Conv.
EDI
expr.
Comments

change.
Field name
Description
Pos Length
tdpur400.ddtc
Confirmed
Delivery Date
10
22
tdpur400.ddat
Delivery Date
11
22
tdpur400.ddtc
Confirmed
Delivery Date
11
22
tdpur040.refa
Reference A
12
30
Conv.
EDI Comments
expr.
CDH Per the evaluation
expression: If a
confirmed delivery
the order, the
confirmed delivery
date overwrites the
delivery date.
CDH Per the evaluation
expression: If a
confirmed delivery
the order, the
confirmed delivery
date overwrites the
delivery date.
tdpur040.refb
Reference B
13
20
tdpur040.prno
Contract
14
Purchase
Contract
Codes by B.
P.
tdpur400.cdec
Terms of Delivery
15
Terms of
Delivery
Codes
tcmcs041.dsca
Description
16
30
tdpur400.cfrw
Forwarding
Agent
17
tcmcs080.dsca
Description
18
30
tdpur400.ccrs
Late Payment
Surcharge
19
tcmcs011.dsca
Description
20
30
tdpur400.cpay
Terms of
Payment
21
tcmcs013.dsca
Description
22
30
Forwarding
Agent
Codes by B.
P.
Late
Payment
Surcharges
Terms of
Payment
Codes
EDI User Guide

8-161
tcmcs013.pper
Payment Period
23
tcmcs013.disa
Discount Period
1
24
tcmcs013.prca
Discount
Percentage 1
25
tdpur400.ccur
Currency
26
Currency
Codes
tdpur400.ccty
Country
27
Country
Codes
tdpur400.cplp
Purchase Price
List
28
tdpur400.creg
Area
29
tdpur400.cbrn
Line of Business
30
tdpur400.odis
Order Discount
31
tdpur400.cofc
Purchase Office
32
tdpur400.cofc
qual1
33
Constant
34
tdpur400.otbp
Buy From B. P.
35
tdpur400.otbp
qual1
36
ecedi224.code.
Code in Message
37
Address/
Partner
Type Codes
tdpur400.sfbp
Ship-from B. P.
38
Business
Partners
tdpur400.sfbp
qual1
39
EDI User Guide

8-162
Discount period.
Sales/
Purchasing
Office
Codes
Address/Partner
Code ID used to
convert office codes.
Defaults to ZZ.
Business
Partners
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
partner (buy-from)
Address/Partner
Code ID used to
convert business
ZZ.
ecedi224.code.
Code in Message
40
tdpur400.ifbp
Invoice-from B.
P.
tdpur400.ifbp
qual1
42
ecedi224.code.
Code in Message
43
Address/
Partner
Type Codes
tdpur400.ptbp
Pay-to B. P.
44
Business
Partners
tdpur400.ptbp
qual1
45
ecedi224.code
Code in Message
46
Address/
Partner
Type Codes
tdpur400.cwar
Warehouse
47
Warehouse
Codes
tdpur400.cwar
qual1
48
ecedi224.code.
Code in Message
49
tdpur400.sbim
Self Billed
Invoice
50
41
Address/
Partner
Type Codes
Business
Partners
Address/Partner
partner (ship-from)
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
partner (invoicefrom)
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
partner (pay-to)
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Address/
Partner
Type Codes
Address/Partner
the type of address
(ship-to, for the
warehouse to which
goods are to be
delivered)
Yes/no
EDI User Guide

8-163
NOTE
n
n
n
n
n
Invoice-from
Buy-from
Pay-to
Ship-from
Delivery (ship-to)
Level: 3 Order header address - optional
Field name
Description
Pos
Length
ENV
Level Identifier
Identifies the
record.
14
Baan unique
message ID
number.
ecedi020.neta
Our Identification
17
External reference
(VAN ID) of the
Baan companys
identification over
this network (from
Our Identification
field defined for
Network).
tdpur400.orno
Purchase Order
Conv.
Address/
Partner
Type
Codes
EDI expr. Comments
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.ccty
Country
30
Country
Codes
OTAD
SFAD
IFAD
PTAD
HRDEL
EDI User Guide

8-164
Address/Partner
Type Code
indicating the type
of business partner
address.

Field name
Description
tccom130.nama Name
Level: 3
Pos Length
8
35
Order header address - optional

Conv.
EDI
expr.
Comments
OTAD
SFAD
IFAD
PTAD
HRDEL
30
OTAD
SFAD
IFAD
PTAD
HRDEL
30
OTAD
SFAD
IFAD
PTAD
HRDEL
10
30
OTAD
SFAD
IFAD
PTAD
HRDEL
EDI User Guide

8-165

Field name
Description
tccom130.name City

Pos Length
11
30
Conv.
EDI
expr.
OTAD
SFAD
IFAD
PTAD
HRDEL
12
30
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.pstc
Zip Code
13
10
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.cste
State/Province
14
OTAD
SFAD
IFAD
PTAD
HRDEL
EDI User Guide

8-166
Comments

Field name
tccom130.telp
Description
Telephone

Pos Length
15
15
Conv.
EDI
expr.
Comments
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.telx
Telex
16
15
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.Fax
Fax
17
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.geoc
GEO Code
18
10
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.hono
House Number
19
10
OTAD
SFAD
IFAD
PTAD
HRDEL
EDI User Guide

8-167

Field name
tccom130.pobn
Description
P.O. Box Number

Pos Length
20
Conv.
10
EDI
expr.
Comments
OTAD
SFAD
IFAD
PTAD
HRDEL
tccom130.fovn
Tax Number
19
20
OTAD
SFAD
IFAD
PTAD
HRDEL
Level: 4 Order Header Text optional
Field name
Description
HTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
identification over
this network (from
Our Identification
field defined for
Network).
tdpur400.orno
Purchase Order
tdpur400.txta
Header Text
80
EDI User Guide

8-168
Pos Length
Conv.
EDI
expr.
Comments

header text. Up to
100 records (user
definable) can be
written.
Field name
Description
Pos Length
Conv.
LIN
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our Identification
17
External reference
(VAN ID) of the
Baan companys
identification over
this network (from
Our Identification
field defined for
Network).
tdpur400.orno
Purchase Order
tdpur041.pono
Position Number
Purchase order line

number
tdpur401.sqnb
Sequence
Number
Purchase order line

sequence number
tdpur401.ctcd
Change Type
Purchasing
Change
Type
Codes
tdpur401.crcd
Change Reason
Code
Purchasing
Change
Reason
Codes
tdpur401.cprj
Project
tdpur401.item
qual1
10
tdpur401.item
Item
11
27
EDI
expr.
Comments
Item Code ID ,
referring to item
code system, used
to convert item code;
default value is BP.
Item codes
by item
code
system
If conversion is
item code;
item code.
EDI User Guide

8-169
Field name
Description
Pos Length
tcibd001.dsca
Description
13
30
tdpur401.oqua
Ordered Quantity
15
19
tdpur401.odat
Order Date
16
22
tdpur401.ddtb
Current Planned
Delivery
17
22
tdpur401.ddtc
Confirmed
Delivery Date
17
22
tdpur401.ddtb
Current Planned
Delivery
18
22
tdpur401.ddtc
Confirmed
Delivery Date
18
22
tdpur401.cuqp
Purchase Unit
19
tdpur401.pric
Price
20
19
tdpur401.cupp
Purchase Price
Unit
21
tdpur401.disc
Line Discount
22
Conv.
EDI
expr.
Comments
CDL
value.
CDL
value.
Unit
Codes
Unit
Codes
23
24
25
26
tdpur401.cvat
Tax Code
27
tdpur401.cvat
qual1
28
EDI User Guide

8-170
Tax
Codes
Tax code ID used to
convert tax code;
defaults to CD.

Field name
Description
tdpur401.cdis
Discount Code

Pos Length
29
Conv.
Discount
Codes by
B. P.
25
Discount
Method s
by B. P.
30
EDI
expr.
Comments
31
32
33
tdpur401.dmth
Discount Method
34
35
36
37
38
tdpur401.ldam
Discount Amount
39
19
40
41
42
43
tdpur401.lsel
Lot Selection
44
12
tdpur401.clot
Lot
45
16
tdpur401.clot
qual1
46
whltc100.ltbp
Business
Partners Lot
47
30
whltc100.ltbp
qual1
48
tdpur401.leng
Length
49
tdpur401.widt
Width
50
tdpur401.thic
Thickness
51
Lot
Selection
Codes by
B. P.
Lot Code
ID by B.
P.

code.
Lot Code
ID by B.
P.

code.
EDI User Guide

8-171
Field name
Description
Pos
Length
tdpur401.cmnf
Manufacturer
52
tdpur401.cpcl
Product Class
53
tdpur401.cpln
Product Line
54
tdpur401.sfbp
Ship-from B. P.
55
tdpur401.sfbp
Qual1
56
ecedi224.code
Code in
Message
57
Address/
Partner Type
Codes
tdpur401.cwar
Warehouse
58
Warehouse
Codes
tdpur401.cwar
qual1
59
ecedi224.code
Code in
Message
60
Address/
Partner Type
Codes
tdpur401.cfrw
Forwarding
Agent
61
Forwarding
Agent by B.
P.
EDI User Guide

8-172
Conv.
EDI Comments
expr.
Business
Partner
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
partner (ship-from)
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Address/Partner
the type of address
(ship-to, for the
warehouse to which
goods are to be
delivered)
Level: 6 Order line text- optional
Field name
Description
LTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur401.pono
Position Number
tdpur401.sqnb
Sequence
Number
tdpur401.txta
Order line text
80
NOTE
Pos Length
Conv.
EDI
expr.
Comments

for every line of header
text. Up to 100 lines
(user definable) can be
extracted.
n
n
Delivery (ship-to)
Ship-from
EDI User Guide

8-173
Level 7 Lines specific address - optional
Field name
Description
LAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur401.pono
Position Number
tdpur401.sqnb
Sequence
Number
ecedi224.code
Code in Message
Address/
Partner
Type
Codes
tccom130.ccty
Country
30
Country
Codes
35
tccom130.nama Name
Pos Length
Conv.
EDI
expr.
LNSFAD Address/Partner Type

Code indicating the
type of address.
LNDEL
LNSFAD
LNDEL
LNSFAD
LNDEL
10
30
LNSFAD
LNDEL
tccon130.namc
Address
11
30
LNSFAD
LNDEL
EDI User Guide

8-174
Comments

Field name
Description
Level 7 Lines specific delivery address - optional

Pos Length
Conv.
EDI
expr.
12
30
LNSFAD
tccom130.name City
13
30
LNSFAD
Comments
LNDEL
LNDEL
tccom130.namf
City 2
14
30
LNSFAD
LNDEL
tccom130.pstc
Zip Code
15
10
LNSFAD
tccom130.cste
State/Province
16
10
LNSFAD
LNDEL
LNDEL
tccom130.telp
Telephone
17
10
LNSFAD
LNDEL
tccom130.telx
Telex
18
tccom130.tefx
Fax
19
10
LNSFAD
LNDEL
LNSFAD
LNDEL
tccom130.geoc
GEO Code
20
LNSFAD
tccom130.hono
House Number
21
LNSFA
D
LNDEL
LNDEL
tccom130.pobn
P.O. Box
Number
22
LNSFA
D
LNDEL
tccom130.fovn
Tax Number
23
LNSFA
D
LNDEL
EDI User Guide

8-175
Level 8 Order Footer Text - optional
Field name
Description
FTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur400.orno
Purchase Order
tdpur400.txtb
Footer Text
80
EDI User Guide

8-176
Pos Length
Conv.
EDI
expr.
Comments

records (user
definable) can be
written.
Conversion setup: 861S, Receipt

Discrepancy Notification
Figure 100 shows the relationship of the records in this message and the key
fields used to link the records. Each record of the message is identified by a level
number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Header
Level 2
Mandatory
Key: F1, F2, F3
Shipment Address
Level 3
Key: F1, F2, F3
Header Text
Level 4
Key: F1, F2, F3
EDI Information (Text)

Level 5
Key: F1, F2, F3
Shipment Routings
Level 6
Key: F1, F2, F3
Shipment Packaging
Level 7
Key: F1, F2, F3
Shipment/Receipt Lines
Level 8
Key: F1, F2, F3, F4
Shipment Line Text

Level 9
Key: F1, F2, F3, F4
Shipment Packing (Load) Data

Level 10
Key: F1, F2, F3, F4
Legend:
F3: Internal Shipment ID
F4: Suppliers Shipment Line Number

F3: Customers Document Reference
F4: Shipment Line Number

Message:
861S, Receipt Discrepancy Notification
Organization: X12
Field type:
Delimited
NOTE
Each level is shown in a separate table
EDI User Guide

8-177
Field name
Description
ENV
Level Identifier

the Envelope record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
20
Business partners
document number.
ecedi702.orga
The Baan EDI

organization.
The Baan EDI

message code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message

non-blank and
matches the value
defined for the
organization, the
message will be
processed as a test
the message will be
stored in Saved
Messages to be
Received).
ecedi702.send
Date Sent
10
22
The date/time the

message was sent.
EDI User Guide

8-178
Organization
Pos Length
Conv.
EDI
expr.
Comments
Level: 2 Header - mandatory
Field name
Description
Pos Length
HDR
Level Identifier
ecedi702.bano
Message
Reference
Conv.
EDI
expr.
Comments
35
ecedi702.bpid
Business Partner
ecedi702.msno
Order Reference
20
whinh430.shpm
Shipment
Identification
whinh430.cdat
Date Confirmed
22
whinh430.pddt
Planned Delivery
Date/Time
22
Unique message
reference. Must be
unique for business
partner.
or ASN Number)
whinh430.fval
Freight Value
10
19
whinh430.curr
Currency
11
whinh430.wght
Total Weight
12
10
whwmd000.wght
Location Weight
Unit of Measure
13
10
Unit Code
whinh430.stco
Ship To Code
14
Business
Partners
whinh430.stco
qual1
15
whinh430.stco
qual2
16
Address/
Partner
Type
codes
whinh430.koch
Kind of Charge
18
15
Kind of
Charge
whinh430.cham
Charge Amount
19
19
whinh430.cdec
Terms of
Delivery
20
Ship-to Business
Partner. Defaults from
global overhead
records business
partner if blank.
ID used to convert
business partner.
Terms of
Delivery
Codes
EDI User Guide

8-179
Level: 4 Header Text optional
Field name
Description
Pos Length
HTX
Level Identifier
ecedi702.bano
Message
Reference
ecedi702.bpid
Conv.
EDI
Expr.
Comments
35
Business Partner
20
whinh430.text
Text
80
whinh430.text
Text
80
Unique message
reference. Must be
unique for business
partner.
Two text fields per

ASCII file record;
multiple ASCII file
Level: 5 EDI Information Text optional
Field name
Description
Pos Length
ATX
Level Identifier
ecedi702.bano
Message
Reference
ecedi702.bpid
Conv.
EDI
Expr.
Comments
35
Unique message
reference. Must be
unique for business
partner.
Business Partner
20
Business partners
document reference.
whinh430.iedi
EDI Information
80
Free form (text). Two

text fields per ASCII
ASCII file records can
be read.
whinh430.iedi
EDI Information
80
EDI User Guide

8-180
Level: 8 Shipment Notice/Receipt Lines mandatory
Field name
Description
Pos Length
LIN
Level Identifier
ecedi702.bano
Message
Reference
ecedi702.bpid
Conv.
EDI
Expr.
Comments
35
Unique message
reference. Must be
unique for business
partner.
Business Partner
20
Business partners
document reference
whinh431.pono Position Number

against which the
discrepancy is
reported.
whinh431.item
Item
47
whinh431.item
qual1
10
whinh431.qshp Shipped Quantity

in Inventory unit
11
19
whinh431.cuni
Unit of Measure
12
tdsls309.shcm
Shipped
Cumulative
13
19
whinh431.grwt
Gross Weight
14
10
whinh431.ntwt
Net Weight
15
10
whinh431.cwun Unit of Measure
16
whinh431.clot
17
16
Lot
item
codes by
item
code
system
If conversion is
qual1 is ZZ, no
conversion is
performed.
Unit
Codes
Unit
Codes
EDI User Guide

8-181

Field name
Description
whinh431.clot

Pos
Length
Conv.
qual1
18
Lot Code
ID by B.
P.
whinh431.qrcp
Confirmed
Received Quan
19
30
whinh431.text
Text
23
80
whinh431.text
Text
24
80

Description
LTX
Level Identifier
ecedi702.bano
Message
Reference
35
ecedi702.bpid
Business Partner
20
whinh431.pono Position Number
whinh431.text
Text
80
whinh431.text
Text
80
8-182
Comments
code.
Two text fields per

ASCII file record;
multiple ASCII file
Field name
EDI User Guide
EDI
Expr.
Pos Length
Conv.
EDI
Expr.
Comments
Unique message
reference. Must be
unique for business
partner.
Two text fields per

ASCII file record;
multiple ASCII file
Conversion setup: 861S, Receipt

Discrepancy Notification
This conversion setup is only available in Baan IVb GLO and Baan V.

Message:
861S, Receipt Discrepancy Notification
Organization: X12
NOTE
EDI User Guide

8-183

Field name
Description
ENV
Pos
Length
Level Identifier
ecedi701.bano
Our Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi020.neta
Our
Identification
Business partners
identification as
defined in business
partners network
address.
whinh300.shid
Shipment
Identification
20
Internal (customers)
ASN Identification
number. (This is not
the suppliers shipment
identification number
(SID))
ecedi028.neta
Network
Address
Trading Partner
(business partner) ID
Number.
ecedi003.code
Code in
Message
Organization (X12).
ecedi001.code
Code in
Message
example, 861S).
ecedi011.koor
Order Type in
Message
35
Constant
10
Can be used to pass a

constant for the test
indicator.
date ( )
10
Date message
May include time,
based in the date
organization.
time ( )
11
Time message
EDI User Guide

8-184
Conv.
EDI
expr.
Comments
Level: 2 Shipment Notice Header mandatory
Field name
Description
Pos Length
Conv.
EDI Comments
expr.
HDR
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
whinh300.shid
Shipment
Identification
ASN Identification
the suppliers
shipment
(SID))
whinh302.asnr
ASN Receipt Nr.
30
Shipment
Identification Number
(Suppliers ASN
Number or SID)
against which the
discrepancy is
reported.
Whinh302.bola
Bill of Landing
30
whinh302.pcsp
Packing Slip
whinh300.shdt
Shipping Date
22
whinh300.pddt
Planned Delivery
Date/Time
22
whinh300.fval
Freight Value
10
19
whinh300.curr
Currency
11
whinh300.wght
Gross Weight
12
19
whinh300.cwun
Unit of Measure
13
Unit Codes
whinh300.cwar
Warehouse
14
Warehouse
Codes
whinh300.cwar
qual1
15
Currency
Codes
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
EDI User Guide

8-185

Field name
Description
ecedi224.code
Code in Message
Level: 2 Shipment Notice Header mandatory

Pos Length
16
whinh300.hazm Hazardous
Material
17
whinh300.koch
18
15
whinh300.cham Charge Amount
19
19
whinh300.cdec
20
EDI User Guide

8-186
Kind of Charge
Terms of Delivery
Conv.
Address/
Partner
Type
Codes
Kind of
Charge
Terms of
Delivery
EDI
expr.
Comments
Code indicating the
type of address.

Field name
Description
HAD
Level: 3 Shipment Address optional

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
Whinh300.shid
Shipment
Identification
ASN Identification
(SID))
ecedi224.code
Code in
Message
Address
/Partner
Type
Codes
Tccom130.ccty
Country
Country
Codes
35
tccom130.nama Name
30
tccom130.namc
30
10
30
tccom130.name City
11
30
tccom130.namf
City 2
12
30
tccom130pstc
ZIP Code/Postal
Code
13
10
tccom130.cste
State/Province
14
tccom130.telp
Telephone
15
tccom130.telx
Telex
16
15
Address
Conv.
EDI
expr.
Comments
Code indicating the
type of address.
EDI User Guide

8-187

Field name
Description
tccom130.tefx
Fax
Level: 3 Shipment Address optional

Pos
Length
17
15
18
10
19
10
tccom130.pono P.O. Box

Number
20
10
tccom130.fovn
21
20
Pos
Length
Tax Number

Field name
Description
Conv.
EDI
expr.
Comments
Level: 4 Shipment Header Text optional

Conv.
EDI
Expr.
Comments
HTX
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
whinh300.shid
Shipment
Identification
ASN Identification
(SID))
whinh300.text
Text
5,6
80

be written.
EDI User Guide

8-188
Level: 5 EDI Information Text optional
Field name
Description
Pos Length
Conv.
ATX
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
whinh300.shid
Shipment
Identification
ASN Identification
(SID))
whinh300.iedi
EDI Information
5,6
80
Free form text. One

record is written for
every two lines of
records (user
definable) can be
written.
EDI
Expr.
Comments
EDI User Guide

8-189

Field name
Description
SNR
Level: 6 Shipment Routings optional

Pos
Length
Level Identifier
Identifies the
record.
ecedi701.bano
Our Reference
14
Unique message
reference. Must be
unique for business
partner.
ecedi702.neta
Our Identification
17
whinh300.shid
Shipment
Identification
whinh315.rscd
Routing
Sequence Code
whinh315.edcd Equipment
Description Code
whinh315.eqin
Equipment Initial
whinh315.eqnr
Equipment
Number
10
whinh315.carr
Carrier
tcmcs080.scac
Standard Carrier
Alpha Code
10
20
tcmcs080.trmd
Transport
Category
11
15
whinh315.seal
Seal Number
12
15
EDI User Guide

8-190
Conv.
EDI
Expr.
Comments
Internal
(customers) ASN
Identification
number. (This is
not the suppliers
shipment
identification
number (SID))
Forwarding
Agent
Codes by
B. P.
(SCAC)

Field name
Description
SNP
Level: 7 Shipment Packaging optional

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
whinh300.shid
Shipment
Identification
ASN Identification
(SID))
whinh303.pkcd Packaging Unit

whinh303.pkqu Package Quantity
19
whinh303.pkwt
10
Packaging
Weight
whinh303.cwun Unit of Measure
Conv.
EDI Comments
Expr.
Unit
Codes
Unit
Codes
EDI User Guide

8-191

Field name
Description
LIN

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
whinh300.shid
Shipment
Identification
ASN Identification
(SID))
ecedi705.refn
Reference Line
Number
Suppliers shipment
line (as recorded in
received shipment
notice) against which
discrepancy is
reported.
whinh301.worn
Warehouse
Order Number
tdpur308.rlno
Release
Number
Purchase order or
purchase release
number against which
the shipment was
received.
whinh301.wpon
Warehouse
Position
Number
tdpur308.rlrv
Release
Revision
Number
Purchase order line or

purchase release
revision number
against which the
shipment was
received.
whinh301.wsqn
Sequence
Number
tdpur308.rpon
Release
Position
Number
Purchase order line

sequence or purchase
release position (line)
number against which
the shipment was
received.
EDI User Guide

8-192
Conv.
EDI Comments
Expr.

Field name
Description
whinh301.item

Pos
Length
Conv.
Item
47
Item
codes
by item
code
system
whinh301.item
qual1
10
whinh301.qshp
Shipped
Quantity in
Inventory unit
11
whinh301.cuni
Unit of Measure
12
whinh301.cums
CUM Shipped
13
19
Whinh301.grwt
Gross Weight
14
10
Whinh301.ntwt
Net Weight
15
10
whinh301.cwun
Unit of Measure
16
whinh301.clot
Lot
17
16
whinh301.clot
qual1
18
whinh210.qrcp
Received
Quantity in
19
16
whinh210.ardt
Actual Receipt
Date
20
22
whinh210.psno
Packing Slip
Number
21
10
EDI Comments
Expr.
If conversion is
Item Code ID ,
system, used to
convert item code.
Defaults to BP. If qual1
is ZZ, no conversion is
performed.
Unit
code
Unit
code
Lot
Code ID
by B. P.

code.
EDI User Guide

8-193
Level: 8 Shipment Notice Receipt Lines mandatory
Field name
Description
whinh210.rcno
Receipt Number
22
whinh301.rqua
Received
Quantity
23
19
24
ecedi447.codm Code in Message
EDI User Guide

8-194
Pos Length
Conv.
EDI
Expr.
ADSQ
TY
Comments
The assignment
expression ADSQTY
calculates the
difference between the
ASN shipped quantity
and the quantity
received, and writes
that value to this
position.
Receipt discrepancy
code
Field name
Description
Pos Length
Conv.
LTX
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
whinh300.shid
Shipment
Identification
ASN Identification
(SID))
ecedi705.refn
Reference Line
Number
whinh301.text
Text
6,7
80

be written.
EDI
Expr.
Comments
EDI User Guide

8-195
Conversion setup: 861 (out)Level:

Field name
Description
ILS
10 Item Load Information optional

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference. Must be
unique for business
partner.
ecedi702.neta
Our Identification
17
whinh300.shid
Shipment
Identification
ASN Identification
(SID))
ecedi705.refn
Reference Line
Number
whinh317.pkdf
Package
Definition
whinh317.ncon Number of
Containers
19
whinh317.nupc Number of Units

per Container
19
whinh317.pkcd Packaging Unit
EDI User Guide

8-196
Conv.
Unit
Codes
EDI Comments
Expr.

number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3, F4
Release Header
Level 2
Mandatory
Key: F1, F2, F3, F4
Specific Address
Level 3
Key: F1, F2, F3, F4
Release Header Text

Level 4
Key: F1, F2, F3, F4
Release Lines
Level 5
Key: F1, F2, F3, F4, F5
Release Line Text

Level 6
Key: F1, F2, F3, F4, F5
Specific Address
Level 7
Key: F1, F2, F3, F4, F5
Legend:
F3: Release Number
F5: Release Line (Position) Number

F5: Customer Release Line (Position) Number

Message:
862S, Shipping Release
Organization: X12
NOTE

EDI User Guide
8-197

Field name
Description
ENV
Pos
Length
Level Identifier

the Envelope record
ecedi702.bano
Our Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
20
Business partners
document number.
ecedi702.orga
The Baan EDI

organization.
The Baan EDI

message code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message
10

non-blank and
matches the value
defined for the
organization, the
message will be
processed as a test
the message will be
stored in Saved
Messages to be
Received).
ecedi702.send
Date Sent
11
22
The date/time the

message was sent.
EDI User Guide

8-198
Organization
Conv.
EDI
expr.
Comments
Field name
Description
Pos Length
Conv.
HDR
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
tdsls312.crln
Customer Release
30
tdsls312.crlr
Customer Revision
14
tdsls312ofbp
Sold-to Business
Partner
tdsls312.ofbp
qual1
tdsls312.ofbp
qual2
Address/
Partner
Type
codes
tdsls312.stbp
Ship-to Business
Partner
Business
Partners
tdsls312.stbp
qual1
10
tdsls312.stbp
qual2
11
tdsls312.fohs
Forecast Horizon
Start
12
22
tdsls312.fohe
Forecast Horizon
End
13
22
EDI Comments
expr.
Customers document
reference (purchase
schedule release
number)
Business
Partners

overhead records
business partner if
blank.
ID used to convert
business partner.
Defaults to ZZ.
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

EDI User Guide

8-199

Field name
Description
tdsls312.egdt

Pos
Length
Generation Date
14
22
tdsls312.tqal
Schedule Type
Qualifier
15
15
Schedule
Type

communicated are
delivery based or
shipment based. If
delivery based (the
date included
represents the planned
shipped date),
leadtimes have been
taken into
consideration. If
delivery based (the
date included
represents the
requirement, or
planned receipt, date),
no leadtime has been
taken into
consideration.
tdsls312.qqal
Schedule Quantity
Qualifier
16
22
Schedule
Quantity
Type

received is a schedule
cumulative or actual,
discrete value If
cumulative, the actual
value stored at the
schedule line
(tdsls307.quan) is
calculated.
EDI User Guide

8-200
Conv.
EDI Comments
expr.

Field name
Description
HAD
Level: 3 Release Header Specific Address - optional

Pos
Length
Level Identifier
ecedi702.bano
Our Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
Conv.
EDI
expr.
Comments
Customers document
reference (purchase
schedule release
number)
Level: 4 Release Header Text optional
Field name
Description
Pos Length
Conv.
HTX
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls312.text
Release Text
80
tdsls312.text
Release Text
80
EDI
Expr.
Comments
Customers document
reference (purchase
schedule release
number)
Two text fields per

ASCII file record;
multiple ASCII file
EDI User Guide

8-201
Field name
Description
LIN
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls308.ppon
Customer
Release
Position
16
tdsls311.stbp
Ship-to
Business
Partner
tdsls311.stbp
qual1
tdsls311.stbp
qual2
tdsls311.cono
Contract
10
tdsls311.pono
Position
11
tdsls311.crsd
Delivery Type
14
20
tdsls307.item
Item
15
47
EDI User Guide

8-202
Pos Length
Conv.
EDI
Expr.
Comments
9
Customers document
reference (purchase
schedule release
number)
Customer release line

number
Business
Partners
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

Contract Position
Item
codes
by item
code
system
If conversion is
Field name
Description
Pos Length
tdsls307.item
qual1
16
tdsls307.sdat
Start Date
17
tdsls307.edat
End Date
18
22
tdsls307.cuqs
Sales Unit
19
tdsls307.quan
Quantity
20
19
tdsls307.txta
Schedule Text
22
80
tdsls307.cwar
Warehouse
23
tdsls307.cwar
qual1
24
tdsls311.cofc
Sales Office
25
tdsls311.cofc
Qual1
26
tdsls311.leng
Length
27
tdsls311.widt
Width
28
tdsls311thic
Thickness
29
tdsls311.cons
Consigned
30
tdsls311sbim.
Self Billed
Invoice
31
tdsls311.lsel
Lot Selection
32
12
Conv.
EDI
Expr.
Comments
Item Code ID ,
referring to item
code system, used
to convert item
code. Defaults to
BP. If qual1 is ZZ,
no conversion is
performed.
Unit code
Warehouse
Codes
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Sales/
purchasing
office code
Address/Partner
Code ID used to
Defaults to ZZ. If
value is ZZ, no
conversion is
performed.
Yes/no
Lot Selection
EDI User Guide

8-203
Field name
Description
tdsls307.revi
Engineering Item
Rev.
33
tdsls307.clot
Lot
34
16
tdsls307.clot
qual1
35
Lot Code
ID by
Business
Partner
tdsls311.ccof
Contract Office
38
Sales/
Purchasing
Office
Codes
tdsls311.ccof
qual1
39
EDI User Guide

8-204
Pos Length
Conv.
EDI
Expr.
Comments
Lot Code ID
indicating whether
the lot code is the
senders lot code or
the recipients lot
code.
Address/Partner
Code ID used to
Defaults to ZZ.
Field name
Description
Pos Length
Conv.
LTX
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in Business
Partners Network
Address.
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls308.ppon
Customer
Schedule
Position
16
Customer Release
Line Number
tdsls307.txta
Schedule Text
80
Two text fields per

ASCII file record;
multiple ASCII file
tdsls307.txta
Schedule Text
80
EDI
Expr.
Comments
EDI User Guide

8-205

Field name
Description
LAD

Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
Business partners
identification as
defined in Business
Partners Network
Address.
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls308.ppon
Customer
Schedule Posit
16
ecedi224.code
Code in
Message
Address/
Partner
Type
Codes
tccom130.ccty
Country
Country
Codes
tccom130.nama
Name
35
10
30
tccom130.Name 2 Name 2
tccom130.namc
Address
11
30
tccom130.namd
Address 2
12
30
tccom130.name
City
13
30
tccom130.namf
City 2
14
30
tccom130.pstc
ZIP
Code/Postal
Code
15
10
tccom130.cste
State/Province
16
tccom130.telp
Telephone
17
15
EDI User Guide

8-206
Conv.
EDI
Expr.
Comments
Code indicating the
type of address

Field name
Description
tccom130.telx

Pos
Length
Telex
18
15
tccom130.tefx
Fax
19
15
tccom130.geoc
GEO Code
20
10
21
10
tccom130.hono
House Number
tccom130.pobn
P.O. Box
Number
22
10
tccom130.fovn
Tax Number
23
20
Conv.
EDI
Expr.
Comments

This conversion setup is only available in Baan IVb GLO and Baan V..

Message:
862S, Shipping Release
Organization: X12
NOTE
EDI User Guide

8-207

Field name
Description
ENV
Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17

ID) of the Baan
tdpur312.rlno
Release
Number
tdpur312.rlrv
Release
Revision
Number
ecedi028.neta
Network
address
17
Trading Partner
(business partners
network address)
ecedi003.code
Code in
Message
Organization (X12).
ecedi001.code
Code in
Message
example, 862S).
ecedi011.koor
Order Type in
Message
35
date()
EDI User Guide

8-208
Conv.
EDI Comments
expr.

time, based in the date
organization.
Field name
Description
Pos Length
Conv.
HDR
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur312.fohs
Forecast Horizon
Start
12
22
tdpur312.fohe
Forecast Horizon
End
13
22
tdpur312.egdt
Generation Date
14
22
tdpur312.tqal
Schedule Type
Qualifier
15
15
Schedule
Type
EDI
expr.
Comments

communicated are
delivery based or
shipment based. If
delivery based (the
date included
represents the
leadtimes are taken
into consideration, and
the date included are
adjusted to account for
leadtimes. If delivery
based (the date
included represents
the requirement, or
planned receipt, date),
no leadtimes are taken
into consideration, and
the dates included are
the requirement dates
reflected on the
release line..
EDI User Guide

8-209

Field name
Description
tdpur312.qqal

Pos
Length
Conv.
Schedule
Quantity Quali
16
22
Schedule
Quantity
Type
tdpur312.sfbp
Ship-from B. P.
17
Business
Partner
tdpur312.sfbp
qual1
18
ecedi224.code
Code in Message
19
Address/
Partner
Type
Codes
tdpur312.bfbp
Buy from B. P.
20
Business
Partner
tdpur312.bfbp
qual1
21
ecedi224.code
Code in Message
22
NOTE
8-210
Comments
indicated is a schedule
cumulative or an
actual, discrete value.
The default conversion
setup includes both
quantities.
ID used to convert
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (ship-from)
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
Codes
Code indicating the
type of business
partner (buy-from)
n
EDI User Guide
EDI
expr.
Buy-from
Ship-from

Field name
Description
HAD
Level: 3 Release Header address - optional

Pos
Length
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdpur312.rlno
Release
Number
tdpur312.rlrv
Release
Revision
Number
ecedi224.code
Code in
Message
Country
tccom130.ccty
35
Conv.
EDI
expr.
Address/
Partner
Type
Codes
PRSF
Country
Codes
PRSF
PRBF
Comments
Code indicating the
type of address
PRBF
tccom130.nama Name
35
PRSF
30
PRSF
PRBF
PRBF
10
30
PRSF
PRBF
11
30
PRSF
tccom130.name City
12
30
PRSF
PRBF
PRBF
tccom130.namf
City 2
13
30
PRSF
PRBF
EDI User Guide

8-211

Field name
Description
tccom130pstc
ZIP Code/Postal
Code
tccom130.cste State/Province
Level: 3 Release Header Address optional

Pos Length
14
10
15
Conv.
EDI
expr.
PRSF
PRBF
PRSF
PRBF
tccom130.telp
Telephone
16
15
PRSF
PRBF
tccom130.telx
Telex
17
15
tccom130.tefx
Fax
18
15
PRSF
PRBF
PRSF
PRBF
tccom130.GE
O Code
GEO Code
tccom130.fovn Tax Number
19
10
PRSF
PRBF
20
20
PRSF
PRBF
EDI User Guide

8-212
Comments

Field name
Description
HTX
Level: 4 Release Header Text optional

Pos
Length
Conv.
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdpur312.rlno
Release
Number
tdpur312.rlrv
Release
Revision
Number
tdpur312.txta
Release Text
80
EDI
Expr.
Comments

be written.
EDI User Guide

8-213
Field name
Description
LIN
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
identification over
this network (from
Our Identification
field defined for
Network).
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur308.rpon
Release Position
Number
tdpur307.cwar
Warehouse
tdpur307.cwar
qual1
ecedi224.code
Code in Message
Address/
Partner Type
Codes
tdpur311.cono
Contract
10
Purchase
Contract
Codes by B.
P.
tdpur311.pono
Position
11
tdpur311.cofc
Purchase Office
12
tdpur311.cofc
qual1
13
EDI User Guide

8-214
Pos Length
Conv.
EDI Comments
Expr
Warehouse
Codes
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Address/Partner
the type of address
(ship-to)
Contract position
(line) number
Sales/
Purchasing
Office Codes
Address/Partner
Code ID used to
Defaults to ZZ.

Field name
Description
tdpur311.crsd

Pos
Length
Delivery Type
14
20
tdpur307.item
Item
15
47
tdpur307.item
qual1
16
tdpur307.sdat
Start Date
17
22
tdpur307.edat
End Date
Conv.
item
codes by
item
code
system
EDI
Expr.
Comments
If conversion is
Item Code ID ,
system, used to
convert item code.
Defaults to BP. If qual1
is ZZ, no conversion is
performed.
18
22
tdpur307.cuqp Purchase Unit
19
tdpur307.quan Schedule
Quantity
20
19
tdpur309.rqcm Required
Cumulative
21
19
Quantity expressed in
schedule cumulative
value.
whinh302.asnr ASN Receipt

Nr.
22
Number (Suppliers
ASN Number or SID).
tdpur311.leng
Length
27
tdpur311.widt
Width
28
tdpur311thic
Thickness
29
tdpur311.cons Consigned
30
Yes/no
tdpur311sbim. Self Billed

Invoice
31
Yes/no
tdpur311.lsel
Lot Selection
32
12
tdpur307.revi
Engineering Item
Rev.
33
tdpur307.clot
Lot
34
16
Unit
Codes
Lot
Selection
Codes by
B. P.
EDI User Guide

8-215
Field name
Description
tdpur307.clot
qual1
35
whltc100.ltbp
Business
Partners Lot
36
30
whltc100.ltbp
qual1
37
tdpur309.rccm Received
Cumulative
40
19
tdpur309.shc
m
Shipped
Cumulative
41
19
tdpur309.ivcm Invoiced
Cumulative
42
19
tdpur309.rawa Raw Authorization
43
19
tdpur309.hraw High Raw

Authorization
44
19
tdpur309.ratd
Raw Auth.
Through Date
45
22
tdpur309.faba
Fab Authorization
46
19
tdpur309.hfab
High Fab
Authorization
47
19
tdpur309.fadt
Fab Auth.
Through Date
48
22
tdpur309.csdt
Cum Start Date
49
22
tdpur309.rtype Requirement
Type
50
19
tdipu015.setu
Segment Time
Unit
51
19
tcibd001.cuni
Inventory Unit
52
tcibd001.cwun Weight Unit
53
tcibd001.wght
Weight
54
10
whinh210.rstk
Receipt Quantity
55
19
EDI User Guide

8-216
Pos Length
Conv.
EDI
Expr.
Comments
Lot Code
ID by B.
P.

code.
Lot Code
ID by
Business
Partner

code.
Unit
Codes
Last receipt quantity

Field name
Description

Pos
Length
whinh210.ardt Actual Receipt

Date
56
22
tdpur311.ccof
Contract Office
57
tdpur311.ccof
qual1
58
Conv.
EDI
Expr.
Comments
Date of last receipt
Sales/
Purchasing
Office
Codes
Address/Partner
Code ID used to
Defaults to ZZ.
Field name
Description
Pos Length
LTX
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
17
External reference
companys
network (from Our
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur308.rpon
Release Position
Number
tdour307.txta
Schedule Text
80
Conv.
EDI
Expr.
Comments

records (user
definable) can be
written.
EDI User Guide

8-217
NOTE
n
Ship-to
Level: 7 Release Line Address optional
Field name
Description
Pos Length
Conv.
LAD
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
tdpur312.rlno
Release Number
tdpur312.rlrv
Release Revision
Number
tdpur308.rpon
Release Position
Number
ecedi224.code
Code in Message
tccom130.ccty
Country
EDI
Expr.
17
External reference
companys
network (from Our
Address/
Partner
Type
Codes
PRSTW
35
PRSTW
tccom130.nama Name
35
PRSTW
tccom130.Name Name 2
2
10
30
PRSTW
11
30
PRSTW
12
30
PRSTW
tccom130.name City
13
30
PRSTW
tccom130.namf
City 2
14
30
PRSTW
tccom130.pstc
ZIP Code/Postal
Code
15
10
PRSTW
tccom130.cste
State/Province
16
PRSTW
EDI User Guide

8-218
Comments
Code indicating the
type of address.
tccom130.telp
Telephone
17
15
PRSTW
tccom130.telx
Telex
18
15
PRSTW
tccom130.tefx
Fax
19
15
PRSTW
20
10
PRSTW
21
10
PRSTW
tccom130.pobn P.O. Box Number
22
10
PRSTW
tccom130.fovn
21
20
PRSTW
Tax Number
EDI User Guide

8-219

Change Acknowledgment
number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Order Header
Level 2
Mandatory
Key: F1, F2, F3
Header Address
Level 3
Key: F1, F2, F3
Order Header Text

Level 4
Key: F1, F2, F3
Order Lines
Level 5
Key: F1, F2, F3, F4, F5
Order Line Text

Level 6
Key: F1, F2, F3, F4, F5
Specific Address
Level 7
Optional
Key: F1, F2, F3, F4, F5
Legend:


Message:
865S, Purchase Order Change Acknowledgment
Organization: X12
EDI User Guide
8-220
Field name
Description
ENV
Level Identifier
Identifies the record as the

Envelope record
ecedi702.bano
Message
Reference
35

Must be unique for
business partner.
ecedi702.bpid
Business Partner
Business partners
business partners network
address.
20
Business partners
document number.
ecedi702.orga
The Baan EDI organization.

code.
ecedi702.koor
Order Type
35
External reference of order

type (code in message).
ecedi702.test
Test Message

in this field is non-blank and
matches the value defined
for the organization, the
message will be processed
as a test message only (it
will be validated, any errors
will be reported, and the
Received).
ecedi702.send
Date Sent
10
22
The date/time the message

was sent.
NOTE
Organization
Pos Length Conv.
EDI Comments
expr.
There are two conversion setups for 865S. The 865S.U updates the purchase
order with any changes indicated in the purchase order acknowledgment. The
865S.C uses the data on the purchase order and purchase order acknowledgment
to generate a report of the changes; it does not update the purchase order.
EDI User Guide

8-221
Field name
Description
Pos
Length
HDR
Level Identifier
Conv.
Identifies the
record
ecedi702.bano
Message
Reference
35
Unique
message
reference. Must
be unique for
business
partner.
ecedi702.bpid
Business
Partner
Business
partners
identification as
defined in
business
partners
network
address
ecedi702.msno Order
Reference
20
Business
partners order
number.
tdpur400.orno
Purchase
Order
tdpur400.ddtc
Confirmed
Delivery Date
22
tdpur400.refa
Reference A
30
tdpur400.refb
Reference B
20
tdpur400.prno
Contract
14
tdpur400.cdec
Term of
Delivery
15
Terms of
Delivery
Codes
tdpur400.cfrw
Forwarding
Agent
17
Forwarding
Agent Codes
by B. P.
tdpur400.ccrs
Late Payment
Surcharge
19
Late
Payment
Surcharge
EDI User Guide

8-222
EDI expr.
Purchase
Contract
Codes by
B. P.
Comments

Field name
Description
Pos
Lengt
h
Conv.
tdpur400.cpay Term of Payment
21
Term of
Payment
Codes
tdpur400.ccur
Currency
26
Currency
Codes
tdpur400.odis
Order Discount
28
29
Warehouse
Codes
tdpur400.cofc
Purchase Office
32
Sales/
Purchasing
Office
Codes
tdpur400.sfbp
Ship-from B. P.
37
Business
Partners
tdpur400.sfbp
qual1
38
tdpur400.sfbp
qual2
39
tdpur400cosn
Change Order
Seq no
46
47
Purchasing
Acknowledg
ment Codes
tdpur400.akcd Acknowledg.
Code
EDI Comments
expr.
Address/Partner
Code ID used to
convert business
ZZ.
Address/
Partner
Type codes
tdpur400.ctcd
Change Type
48
Purchasing
Change
Type Codes
tdpur400.crcd
Change Reason
49
Purchasing
Change
Reason
Codes

business partner
(ship-from)
EDI User Guide

8-223
Field name
Description
Conv.
HTX
Pos
Length
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
20
Business partners
order number.
tdpur400.txta
Header Text
80
There are two text

tdpur400.txta
Header Text
80
EDI User Guide

8-224
EDI
expr.
Comments
Field name
Description
LIN
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
20
Business partners
order number.
ecedi705.refn
10
Business Partners
Order Line Number
Reference Line
Number
Pos Length
tdpur401.pono
Position Number
tdpur401.sqnb
Sequence
Number
tdpur401.cprj
Project
tdpur401.item
qual1
10
tdpur401.item
Item
11
27
tdpur401.oqua
Ordered Quantity
14
19
tdpur401.oqua
Purchase Unit
16
tdpur401.pric
Price
17
19
tdpur401.cupp
Purchase Price
Unit
18
Conv.
EDI
expr.
Comments
Item Code ID ,
system, used to
convert item code.
Defaults to BP. If
qualifier1 is ZZ, no
conversion is
performed.
item
codes by
item
code
system
If conversion is
unit
Codes
Unit
Codes
EDI User Guide

8-225
Field name
Description
Pos
Length
tdpur401.disc
Line Discount
19
20
21
22
23
tdpur401.amta Ordered Amount
24
19
tdpur401.ddtc
Planned Delivery
Date
25
22
tdpur401.ddtc
Confirmed
Delivery Date
25
22
EDI User Guide

8-226
Conv.
EDI
expr.
Comments

Field name
Description
tdpur401.cdis
Discount Code
Pos Length
27
Conv.
Discount
Codes by
B. P.
25
Discount
Method
by B. P.
28
EDI
expr.
Comments
29
30
31
tdpur401.dmth Discount Method
32
33
34
35
36
tdpur401.ldam Discount Amount
37
19
38
39
40
41
tdpur401.lsel
Lot Selection
42
12
tdpur041.clot
Lot
43
16
tdpur041.clot
Qual1
44
Lot
Selection
Codes by
B. P.
Lot Code
ID by B.
P.

code.
EDI User Guide

8-227

Field name
Description
Pos Length
Conv.
tdpur401.akcd Purchase
Acknowledgment
47
Purchase
Acknowl
edgment
Codes
48
Warehou
se Codes
tdpur401.cwar qual1
49
tdpur401.sfbp
Ship from B. P.
51
tdpur401.sfbp
qual1
52
tdpur401.sfbp
qual2
53
tdpur401.ddta
Planned Delivery
Date
54
22
tdpur401.cfrw
Forwarding Agent
57
Forwardi
ng Agent
by B. P.
tdpur401.ctcd
Change Type
58
Purchase
Change
Types
tdpur401.crcd
Change Reason
59
Purchase
Change
Reasons
tdpur401.leng
Length
60
tdpur401.widt
Width
61
tdpur401.thic
Thickness
62
tdpur401.ddtf
Order
Confirmation Date
63
22
tdpur401.cvat
Tax Code
64
EDI User Guide

8-228
EDI
expr.
Comments
ID used to convert
ZZ.
Business
Partners
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes
Tax
Codes


Field name
Description
tdpur401.cvat
qual1
Pos Length
65
Conv.
Comments
Tax code ID used to
convert tax code;
defaults to ZZ. No
conversion is
performed if value is
ZZ.

Pos
EDI
expr.
Field name
Description
LTX
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business
Partner
Business partners
identification as
defined in business
partners network
address.
Business partners
order number.
Length
ecedi702.msno Order
Reference
20
ecedi705.refn
Reference Line
Number
10
tdpur401.txta
Order line text
80
tdpur401.txta
Order line text
80
Conv.
EDI
expr.
Comments
There are two text


Message:
865S, Purchase Order Change Acknowledgment
Organization: X12
NOTE
EDI User Guide

8-229
Field name
Description
ENV
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdsls400.orno
Sales Order
ecedi028.neta
Network
Address
Business partners
network address.
ecedi003.code
Code in
Message
Organization (X12).
ecedi001.code
Code in
Message
Message identifier
(865S).
ecedi011.koor
Order Type in
Message
35
order type.
Constant

constant for the test
indicator.
date()
Todays Date
Date message
May include time,
based in the date
organization.
time()
Current Time
Time message
EDI User Guide

8-230
Pos Length
10
11
Conv.
EDI
expr.
Comments
Field name
Description
HDR
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID number.
ecedi020.neta
Our Identification
32
17
External reference
companys
network (from Our
tdsls400.orno
Sales Order
tdsls400.corn
Customer Order
Number
30
tdsls400.odat
Order Date
22
tdsls400.prdt
Planned Receipt
Date
22
tdsls400.refa
Reference A
30
tdsls400.refb
Reference B
20
tdsls400.crep
Inside Sales Rep
10
Employee
Codes by
B. P.
tccom001.nama Name
11
Employee
Codes by
B. P.
tdsls400.osrp
12
Outside Sales
Rep
Pos Length
Conv.
EDI
expr.
Comments
Date sales order

created.
tccom001.nama Name
13
tdsls400.prno
Contract
14
Sales
Contract
Codes
tdsls400.cdec
Term of Delivery
15
Terms of
Delivery
Codes
tcmcs041.dsca
Description
16
30
Customers name.
Baan delivery code.
EDI User Guide

8-231

Field name
Description
tdsls400.cfrw
Forwarding Agent

Pos Length
Conv.
17
18
30
tdsls400.ccrs
19
20
30
tdsls400.cpay
21
22
30
23
tcmcs013.disa
24
Percentage 1
25
tdsls400.ccur
Currency
26
Currency
Codes
tdsls400.ccty
Country
27
Country
Codes
tdsls400.odis
Order Discount
28
tdsls400.stbp
Ship-to Business
Partner
29
tdsls400.stbp
qual1
30
31
Address/
Partner
Type
Codes
tdsls400.ofbp
32
Business
Partner
EDI User Guide

8-232
Late Payment
Surcharge
Terms of Payment
Discount Period 1
Sold-to Business
Partner
EDI
Expr.
Comments
Forwarding
Agent
Codes by
B. P.
Forwarding Agent
description
Late
Payment
Surcharge
s
Terms of
Payment
Codes
Discount period.
Business
Partner
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
Type Code
business partner
(ship-to)
tdsls400.ofbp
qual1
33
34
Address/
Partner
Type
Codes
tdsls400.cofc
Sales Office
35
Sales/
Purchasin
g Office
Codes
tdsls400.cofc
qual1
36
tdsls400.cwar
Warehouse
37
tdsls400.cwar
qual1
38

.
39
Address/
Partner
Type
Codes
tdsls400.itbp.
Invoice-to B. P.
40
Business
Partners
tdsls400.itbp
qual1
41

.
42
Address/
Partner
Type
Codes
tdsls400.pfbp
Pay-by B. P.
43
Business
Partners
tdsls400.pfbp
qual1
44
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
Type Code
business partner
(sold-to)
Address/Partner
Code ID used to
Defaults to ZZ.
Warehous
e Codes
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Address/Partner
Type Code
address (ship-from)
Address/Partner
Code ID used to
convert business
ZZ.
Address/Partner
Type Code
business partner
(invoice-to)
Address/Partner
Code ID used to
convert business
EDI User Guide

8-233
ZZ.
.
45
tdsls400.cosn
Change Order Seq

no
46
tdsls400.akcd
Sales
Acknowledgement
C
47
Sales
Acknow
ledgment
Codes
tdsls400.ctcd
Change Type
48
Sales
Change
Type
Codes
tdsls400.crcd
Change Reason
49
Sales
Change
Reason
Codes
NOTE
n
n
n
n
8-234
Address/Partner
Type Code
business partner
(pay-by)
n
EDI User Guide
Address/
Partner
Type
Codes
Invoice-to
Sold-to
Pay-by
Ship-to

Field name
Description

Pos Length
Conv.
EDI
expr.
Comments
HAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdsls400.orno
Sales Order
ecedi224.code
Code in Message
Address/
Partner
Type
Codes
Code indicating the
OFAD
type of address.
CWAD
STAD
ITAD
PFAD
tccom130.ccty
Country
Country
Codes
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.nama Name
35
STAD
OFAD
CWAD
ITAD
PFAD
EDI User Guide

8-235

Field name
Description

Pos Length
8
30
Conv.
EDI
Expr.
Comments
STAD
).
OFAD
CWAD
ITAD
PFAD
30
STAD
OFAD
CWAD
ITAD
PFAD
10
30
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.name City
11
30
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.name City 2
12
30
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.pstc
Zip Code
13
10
STAD
OFAD
CWAD
ITAD
PFAD
EDI User Guide

8-236

Field name
tccom130.cste
Description
State/Province
Level: 3 Order Header Address- optional

Pos
Length
14
Conv.
EDI
expr.
Comments
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.telp
Telephone
15
15
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.telx
Telex
16
15
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.tefx
Fax
17
15
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.geoc
GEO Code
18
10
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.hono
House Number
21
10
STAD
OFAD
CWAD
ITAD
PFAD
EDI User Guide

8-237

Field name
tccom130.pobn
Description
Level: 3 Order Header Address- optional

Pos
Length
22
10
P.O. Box
Number
Conv.
EDI expr.
Comments
STAD
OFAD
CWAD
ITAD
PFAD
tccom130.fovn
Tax Number
19
20
STAD
OFAD
CWAD
ITAD
PFAD
Field name
Description
LTX
Level Identifier
35
Baan unique message

ID number.
14
External reference
companys
network (from Our
ecedi020.neta
Our Identification
tdsls400.orno
Sales Order
tdsls400.txta
Header Text
EDI User Guide

8-238
Pos Length
4
5
Conv.
EDI
expr.
Comments
6
80

ASCII records (user
definable) can be
written.
Field name
Description
Pos Length
Conv.
LTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdsls400.orno
Sales Order
tdsls401.pono
Position
Number
tdsls401.sqnb
Sequence
Number
tdsls401.corp
Customer Order
Position
16
Customer order line

number
tdsls401.cors
Customer Order
Sequence
11
Customer order line

sequence number
tdsls401.cprj
Project
tdsls401.item
qual1
10
tdsls401.item
Item
11
47
tdsls401.item
Item
12
47
tcibd001.dsca
Description
13
27
tdsls401.oqua
Order Quantity
14
19
tdsls401.bqua
Back Order
15
19
tdsls401.cuqs
Sales Unit
16
tdsls401.pric
Price
17
19
tdsls401.cups
Sales Price Unit
18
EDI
expr.
Comments

code (defaults to BP).
item
codes by
item
code
system
If conversion is
(internal) item code
Unit
Codes
Unit of measure
sold/delivered.
Unit
Codes
Unit of measure for

sales price.
EDI User Guide

8-239

Field name
Description
tdsls401.disc
Line Discount

Pos Length
19
20
21
22
23
tdsls401.amta Amount
EDI User Guide

8-240
24
19
Conv.
EDI
expr.
Comments
Field name
Description
Pos Length
tdsls401.prdt
Planned Receipt
Date
25
22
tdsls401.odat
Order Date
26
22
tdsls401.cdis
Discount Code
27
Discount
Codes by
B. P.
25
Discount
Methods
by B. P.
28
Conv.
EDI
expr.
Comments
29
30
31
tdsls401.dmth Discount Method
32
33
34
35
36
tdsls401.ldam Discount Amount
37
19
38
39
40
41
tdsls401.lsel
Lot Selection
42
12
tdsls401.clot
tdsls401.clot
Lot
43
16
Qual1
44
whltc100.ltbp
Business
Partners Lot
45
30
whltc100.ltbp
qual1
46
47
tdsls401.akcd Sales
Acknowledgeme
nt C
Lot Code
ID by
Business
Partner

Lot Code
ID by
Business
Partner

Sales
Acknowl
edgment
Codes
EDI User Guide

8-241

Field name
Description

Pos Length
tdsls401.stbp. Ship-to Business

Partner
48
tdsls401.stbp
49
EDI User Guide

8-242
qual1
Conv.
Business
Partners
EDI
expr.
Comments
Tax code ID used to
convert tax codes;
defaults to ZZ.
ID used to convert
business partner.
Defaults to ZZ.
Field name
Description
Pos Length
Conv.
ecedi224.code
Code in
Message
50
Address/
Partner
Type
Codes
tdsls401.cwar
Warehouse
51
Warehouse
Codes
tdsls401.cwar
qual1
52
ecedi224.code. Code in
Message
53
tdsls401.ddta
Planned
Delivery Date
54
22
tdsls401.dldt
Delivery Date
55
22
tdsls401.dqua
Delivered
Quantity
56
19
tdsls401.cfrw
Forwarding
Agent
57
Forwarding
Agent
Codes by
B. P.
tdsls401.ctcd
Change Type
58
Sales
Change
Type
Codes
tdsls401.crcd
Change Reason
59
Sales
Change
Reason
Codes
tdsls401.leng
Length
60
tdsls401.widt
Width
61
tdsls401.thic
Thickness
62
EDI
expr.
Comments
Address/Partner
partner (ship-to)
Address/Partner
Code ID used to
convert warehouse.
Defaults to ZZ.
Address/
Partner
Type
Codes
Address/Partner
the type of address.
EDI User Guide

8-243
Field name
Description
Pos Length
date()
Date
61
22
tdsls401.cvat
Tax Code
64
tdsls401.cvat
Qual1
65

Field name
Description
Conv.
EDI
expr.
Comments
Date/time that the EDI
message was
generated, based on
date format defined for
the organization. This
is intended to be used
as the confirmation
date for the line.
Tax
Codes
Tax code ID used to
convert tax code;
defaults to ZZ.
Level: 6 Order line text- optional

Pos Length
Conv.
EDI
expr.
Comments
LTX
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdsls400.orno
Sales Order
tdsls401.pono
Position
Number
tdsls401.sqnb
Sequence
Number
tdsls401.txta
Order Line Text
80
EDI User Guide

8-244

records (user
definable) can be
written.
NOTE
n
n
Ship-to

Field name
Description
Level: 7 Order line addresses optional

Pos Length
Conv.
EDI
Expr.
Comments
LAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique
message ID
number.
ecedi020.neta
Our
Identification
17
External reference
(VAN ID) of the
Baan companys
identification over
this network (from
Our Identification
field defined for
Network).
tdsls400.orno
Sales Order
tdsls401.pono
Position
Number
tdsls401.sqnb
Sequence
Number
Code in
Message
tccom130.ccty
Country
tccom130.nama
Name
35
LNSTAD
tccom130.namb
Name 2
10
30
LNSTAD
tccom130.namc
Address
11
30
LNSTAD
ecedi224.code
Address/ LNSTAD
Partner
Type
Codes
CWAD
Country
Codes
Address/Partner
Type Code
indicating the type
of address.
LNSTAD
CWAD
CWAD
CWAD
CWAD
tccom130.namd
Address 2
12
30
LNSTAD
CWAD
EDI User Guide

8-245
Level: 7 Order line addresses optional
Field name
Description
Pos Length
Conv.
EDI
Expr.
tccom130.name
City
13
30
LNSTAD .
tccom130.namf
City 2
14
30
LNSTAD
tccom130.pstc
Zip Code
15
10
LNSTAD
tccom130.cste
State/Province
16
LNSTAD
tccom130.telp
Telephone
17
15
LNSTAD
CWAD
CWAD
CWAD
CWAD
CWAD
tccom130.telx
Telex
18
15
LNSTAD
CWAD
tccom130.tefx
Fax
19
15
LNSTAD
CWAD
tccom130.geoc
GEO Code
20
10
LNSTAD
CWAD
tccom130.hono
House Number
21
10
LNSTAD
tccom130.pobn
P.O. Box
Number
22
10
LNSTAD
tccom130.fovn
Tax Number
23
20
LNSTAD
CWAD
CWAD
CWAD
EDI User Guide

8-246
Comments
Conversion setup: 866S Sequenced Shipping

Release
number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Release Header
Level 2
Mandatory
Key: F1, F2, F3, F4
Release Lines
Level 3
Key: F1, F2, F3, F4, F5, F6, F7
Release Line Address

Level 4
Key: F1, F2, F3, F4, F5, F6, F7
Production Sequence Data

Level 5
Key: F1, F2, F3, F4, F5, F6, F7, F8
Production Sequence Address

Level 6
Key: F1, F2, F3, F4, F5, F6, F7, F8
Legend:
F3: Release Number
(Sequenced Shipping Release)
F5: Reference Release Number
(Planning/Shipping Release)
F6: Reference Release Revision
F7: Reference Release Line (Position)
F8: Job Sequence Number

(Sequenced Shipping Release)
F5: Customer Reference Release Number
(Planning/Shipping Release)
F6: Customer Reference Release Revision
F7: Customer Reference Release Line (Position)
F8: Job Sequence Number

Message: 866S, Sequenced Shipping Release
Organization: X12
NOTE
EDI User Guide

8-247
Field name
Description
ENV
Level Identifier

the Envelope record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
20
Business partners
document number.
ecedi702.orga
The Baan EDI

organization.
The Baan EDI

message code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message

non-blank and
matches the value
defined for the
organization, the
message will be
processed as a test
the message will be
stored in Saved
Messages to be
Received).
ecedi702.send
Date Sent
10
22
The date/time the

message was sent.
EDI User Guide

8-248
Organization
Pos Length
Conv.
EDI
expr.
Comments
Field name
Description
Pos Length
Conv.
HDR
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
tdsls312.crln
Customer
Release
30
tdsls312.crlr
Customer
Revision
14
tdsls312.ofbp
Sold-to Business
Partner
tdsls312.ofbp
qual1
tdsls312.ofbp
Qual2
Business
Partners
EDI
Expr.
Comments

overhead records
business partner if
blank.
ID used to convert
business partner.
Defaults to ZZ.
Address/
Partner
Type
codes

EDI User Guide

8-249
Level: 3 Release Line mandatory
Field name
Description
LIN
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
tdsls312.crln
Customer
Release
30
Customers document
reference (customer
release number) for
the Sequenced
Shipping Release
(866)
tdsls312.crlr
Customer
Revision
14
Customers revision of
the Sequenced
Shipping Release
(866) document.
tdsls308.pchn
Customer
Release
30
Customers document
reference (customers
release number) for
the planning release
(830) or shipping
release (862) which
this 866 is intended to
supplement.
tdsls308.prev
Customer
Release Revision
14
Customers document
reference revision
(customers release
revision) for the
planning release (830)
or shipping release
(862) which this 866 is
intended to
supplement.
EDI User Guide

8-250
Pos Length
Conv.
EDI
Expr.
Comments

Field name
Description
tdsls308.ppon
Customer
Release Position

Pos Length
8
16
Conv.
EDI
Expr.
Comments
Customers document
line number reference
(customers release
line) for the planning
release (830) or
shipping release (862)
which this sequenced
is intended to
supplement.
EDI User Guide

8-251
Field name
Description
LAD
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
tdsls312.crln
Customer
Release
30
Customers document
reference (customer
release number) for
the Sequenced
Shipping Release
(866)
tdsls312.crlr
Customer
Revision
14
the Sequenced
Shipping Release
(866) document.
tdsls308.pchn
Customer
Schedule
30
Customers document
release number) for
(830) or shipping
release (862) which
supplement.
tdsls308.prev
Customer
Schedule Revis
14
Customers document
reference revision
(customers release
revision) for the
or shipping release
intended to
supplement.
EDI User Guide

8-252
Pos Length
Conv.
EDI
Expr.
Comments

Field name
Description
tdsls308.ppon
Customer
Schedule Posit

Pos Length
8
16
Conv.
EDI
Expr.
Comments
Customers document
(customers release
release (830) or
is intended to
supplement.
EDI User Guide

8-253
Level: 5 Production Sequence Data mandatory
Field name
Description
JOB
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
tdsls312.crln
Customer
Release
30
Customers document
reference (customer
release number) for
the Sequenced
Shipping Release
(866)
tdsls312.crlr
Customer
Revision
14
the Sequenced
Shipping Release
(866) document.
tdsls308.pchn
Customer
Schedule
30
Customers document
release number) for
(830) or shipping
release (862) which
supplement.
tdsls308.prev
Customer
Schedule Revis
14
Customers document
reference revision
(customers release
revision) for the
or shipping release
intended to
supplement.
EDI User Guide

8-254
Pos Length
Conv.
EDI
Expr.
Comments
Level: 5 Production Sequence Data mandatory
Field name
Description
Pos Length
Conv.
tdsls308.ppon
Customer
Schedule Posit
16
Customers document
(customers release
release (830) or
is intended to
supplement.
whinh420.seqn Line Sequence
Production Sequence
Number
whinh420.quan Quantity
10
19
whinh420.bffr
Buffer
12
Free form.
whinh420.refa
Reference
Information
13
30
Free form.
EDI
Expr.
Comments

Message:
866S, Sequenced Shipping Release
Organization: X12
NOTE
EDI User Guide

8-255
Field name
Description
ENV
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur312.rlno
Release Number
Sequenced Shipping
Release (866) release
number
tdpur312.rlrv
Release Revision
Number
Sequenced Shipping
revision
ecedi028.neta
Network Address
17
Business partners
network address.
ecedi003.code
Code in Message
Organization (X12).
ecedi001.code
Code in Message

example, 866S).
ecedi011.koor
Order Type in
Message
35
Constant
10
May be sued to pass a

value to indicate if this
is a test message.
11
Date message
May include time,
based in the date
organization.
date ( )
EDI User Guide

8-256
Pos Length
Conv.
EDI
expr.
Comments
Level: Release Header mandatory
Field name
Description
Pos Length
HDR
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference. Must be
unique for business
partner.
ecedi020neta
Our Identification
17
Business partners
identification as
defined in business
partners network
address.
tdpur312.rlno
Release Number
Sequenced Shipping
number
tdpur312.rlrv
Release Revision
Number
Sequenced Shipping
revision
tdpur312.egdt
Generation Date
Conv.
EDI
expr.
Comments
22
EDI User Guide

8-257
Field name
Description
LIN
Level Identifier
ecedi701.bano
Our Reference
14
Unique message
reference. Must be
unique for business
partner.
ecedi020neta
Our Identification
17
Business partners
identification as
defined in business
partners network
address.
tdpur312.rlno
Release Number
Sequenced Shipping
number
tdpur312.rlrv
Release Revision
Number
Sequenced Shipping
revision
tdpur308.rlno
Release Number
The Planning Release

(830) or Shipping
Release (862) number
which this Sequenced
Shipping Release
(866) is intended to
supplement.
tdpur403.rlrv
Release Revision
Number

(830) or Shipping
Release (862) revision
Shipping Release
supplement.
tdpur308.rpon
Release Position
Number

(830) or Shipping
line number which this
Sequenced Shipping
Release (866) is
intended to
supplement.
EDI User Guide

8-258
Pos Length
Conv.
EDI
expr.
Comments
Field name
Description
Pos Length
Conv.
tdpur311.cofc
Purchase Office
tdpur311.cofc
qual1
10
tdpur311.bfbp
Buy From B. P.
12
tdpur311.bfbp
qual1
13
14
Address/
Partner
Type
Codes
tdpur311.sfbp
Ship-from B. P.
15
Business
Partners
tdpur311.sfbp
qual1
16
17
Address/
Partner
Type
Codes
tdpur311.cono Contract
.
18
Purchase
Contract
Codes by
B. P.
tdpur311.pono Position
19
EDI Comments
expr.
Sales/
Purchasing
Office
Codes
ID used to convert
office code. Defaults to
ZZ.
Business
Partners
ID used to convert
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (buy-from)
ID used to convert
business partner.
Defaults to ZZ.
Code indicating the
type of business
partner (ship-from)
EDI User Guide

8-259
Field name
Description
tdpur307.item
Item
20
47
tdpur307.item
qual1
21
tdpur307.cuqp Purchase Unit
22
Unit Codes
23
Warehouse
Codes
tdpur307.cwar qual1
24
NOTE
Pos Length
Conv.
item codes
by item
code
system
8-260
If conversion is
Item Code ID ,
system, used to
convert item code.
Defaults to BP. If
qual1 is ZZ, no
conversion is
performed.
ID used to convert
warehouse. Defaults
to ZZ.
The following three addresses may be included in the following level of the
P.. Delivery Warehouse (ship-to)
P.. Ship-from
P.. Buy-from
EDI User Guide
EDI Comments
expr.

Field name
Description
Level: 4 Release Line addresses optional

Pos Length
Conv.
EDI
Expr.
Comments
LAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
17
External reference
companys
network (from Our
tdpur312.rlno
Release Number
Sequenced Shipping
number
tdpur312.rlrv
Release
Revisions
Number
Sequenced Shipping
revision
tdpur308.rlno
Release Number

(830) or Shipping
Shipping Release
supplement.
tdpur308.rlrv
Release Revision
Number

(830) or Shipping
Shipping Release
supplement.
tdpur308.rpon
Release Position
Number

(830) or Shipping
Sequenced Shipping
Release (866) is
intended to
supplement.
EDI User Guide

8-261

Field name
Description
ecedi224.code
Code in Message

Pos Length
9
Conv.
EDI Expr.
Address/
Partner
Type
Codes
PRBF
PRSF
PRSTW
OFADPRSF
tccom130.ccty
Country
10
Country
Codes
PRBF
PRSF
PRSTW
tccom130.nama Name
11
35
PRBF
PRSF
PRSTW
EDI User Guide

8-262
Comments
Address/
Partner Type
Code indicating
the type of
address.

Field name
Description

Pos Length
12
30
Conv.
EDI
Expr.
Comments
PRBF
PRSF
PRSTW
13
30
PRBF
PRSF
PRSTW
14
30
PRBF
PRSF
PRSTW
tccom130.name City
15
30
PRBF
PRSF
PRSTW
tccom130.namf
City2
16
30
PRBF
PRSF
PRSTW
tccom130pstc
Zip Code
17
10
PRBF
PRSF
PRSTW
tccom130.cste
State/province
18
PRBF
PRSF
PRSTW
tccom130.telp
Telephone
19
15
PRBF
PRSF
PRSTW
tccom130.telx
Telex
20
15
PRBF
PRSF
PRSTW
tccom130.tefx
Fax
21
15
PRBF
PRSF
PRSTW
EDI User Guide

8-263

Field name
Description
Level: 4 Release Header addresses optional

Pos Length
22
10
Conv.
EDI
Expr.
PRBF
PRSF
PRSTW
tccom130.hono House number
23
10
PRBF
PRSF
PRSTW
tccom130.pobn P.O. Box Number
24
10
PRBF
PRSF
PRSTW
tccom130.fovn
Tax Number
25
20
PRBF
PRSF
PRSTW
EDI User Guide

8-264
Comments

Field name
Description
Level: 5 Production Sequence Data Mandatory

Pos Length
Conv.
EDI
Expr.
Comments
JOB
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our Identification
17
External reference
companys
network (from Our
tdpur312.rlno
Release Number
Sequenced Shipping
number
tdpur312.rlrv
Release
Revisions
Number
Sequenced Shipping
revision
tdpur308.rlno
Release Number

(830) or Shipping
Shipping Release
supplement.
tdpur308.rlrv
Release Revision
Number

(830) or Shipping
Shipping Release
supplement.
tdpur308.rpon
Release Position
Number

(830) or Shipping
Sequenced Shipping
Release (866) is
intended to
supplement.
tisfc730.seqn
Sequence
Number
Production Sequence
Number
EDI User Guide

8-265

Field name
Description
Level: 5 Production Sequence Data Mandatory

Pos Length
ticst001.qune
Net Quantity
10
19
tcms065.cadr
Address
11
tisfc730.asln
Assembly Line
12
ticst001.aldt
Allocation Date
13
22
tisfc703.pdno
Production Order
14
NOTE
8-266
EDI
Expr.
Comments
Internal Address Code

for destination to
which goods are to be
delivered.
n
EDI User Guide
Conv.
Delivery (ship-to)

Field name
Description
Level: 6 Production Sequence address optional

Pos Length
Conv.
EDI
Expr.
Comments
JAD
Level Identifier
ecedi701.bano
Our Reference
14
Baan unique message

ID number.
ecedi020.neta
Our
Identification
17
External reference
companys
network (from Our
tdpur312.rlno
Release
Number
Sequenced Shipping
number
tdpur312.rlrv
Release
Revisions
Number
Sequenced Shipping
revision
tdpur308.rlno
Release
Number

(830) or Shipping
Shipping Release
supplement.
tdpur308.rlrv
Release
Revision
Number

(830) or Shipping
Shipping Release
supplement.
tdpur308.rpon
Release
Position
Number

(830) or Shipping
Sequenced Shipping
Release (866) is
intended to
supplement.
tisfc730.seqn
Sequence
Number
Production Sequence
Number
EDI User Guide

8-267
Level: 6 Production Sequence address optional
Field name
Description
Pos Length
ecedi224.code
Code in
Message
10
Address/
Partner
Type
Codes
tccom130.ccty
Country
11
Country
Codes
tccom130.nama
Name
12
35
PREDP Customers name.
13
Conv.
EDI
Expr.
Comments
PRDEP Address/Partner Type

Code indicating the
type of address.
PREDP
tccom130.namb
Name 2
30
PREDP
tccom130.namc
Address
14
30
PREDP
tccom130.namd
Address 2
15
30
PREDP
tccom130.name
City
16
30
PREDP .
tccom130.name
PREDP

Field name
Pos
Length
17
30
PREDP
tccom130.pstc
Zip Code
18
10
PREDP
tccom130.cste
State/Province
19
PREDP
tccom130.telp
Telephone
20
15
PREDP
tccom130.telx
Telex
21
15
PREDP
tccom130.tefx
Fax
22
15
PREDP
tccom130.geoc
GEO Code
23
10
PREDP
tccom130.hono House number
24
10
tccom130.pobn P.O. Box

Number
25
10
tccom130.fovn
26
20
EDI User Guide

8-268
Description
Level: 6 Production Sequence Address- optional
Tax Number
Conv.
EDI
Expr.
PREDP
Comments
Conversion setup: 977 Message Status

number.
Message Envelope
Level 1
Mandatory
Key: F1, F2, F3
Message Status
Level 2
Mandatory
Key: F1, F2, F3
Legend:
F3: Document Reference
Figure 104 Record relationships, 977

Message:
977, Message Status
Organization: X12
Field type:
Delimited
NOTE
EDI User Guide

8-269
Field name
Description
ENV
Level Identifier

the Envelope record
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
20
Business partners
document number.
ecedi702.orga
The Baan EDI

organization.
The Baan EDI

message code.
ecedi702.koor
Order Type in
Message
35
order type (code in
message).
ecedi702.test
Test Message

non-blank and
matches the value
defined for the
organization, the
message will be
processed as a test
the message will be
stored in Saved
Messages to be
Received).
ecedi702.send
Date Sent
10
22
The date/time the

message was sent.
EDI User Guide

8-270
Organization
Pos Length
Conv.
EDI
expr.
Comments
Level: 2 Message Status mandatory
Field name
Description
Pos Length
Conv.
HDR
Level Identifier
ecedi702.bano
Message
Reference
35
Unique message
reference. Must be
unique for business
partner.
ecedi702.bpid
Business Partner
Business partners
identification as
defined in business
partners network
address.
20
Business Partners
Document reference
Number
ecedi701.bano
Our Reference
14
The unique message

reference of the
original generated
document whose
status this message is
intended to update.
ecedi701.orno
Number
The document number

of the original
generated document
whose status this
message is intended to
update.
The EDI Message

Code of the original
generated document
whose status this
message is intended to
update.
ecedi701.stat
Send Status
22
ecedi701.iedi
EDI Information
80
Message
Status
Codes
EDI
Expr.
Comments
The status of the

outgoing message.
Free form text.
EDI User Guide

8-271
EDI expressions
EDI expressions may be one of two varieties. They may be Evaluation
Expressions, or Assignment Expressions. Evaluation expressions determine
which lines of a conversion setup definition are executed and which are not; that
is, for outgoing messages, which fields in the ASCII file are filled and which are
not, and for incoming messages, which incoming ASCII file fields get assigned
to Baan ERP application fields. Assignment Expressions perform calculations
that may be written to the file for outgoing messages, or to the application table
field for incoming messages.
The following table lists the evaluation expressions used within the default
conversion setups, and includes the expression code referenced in the conversion
setup, along with the description, the expression (in mathematical terms), and an
explanation as to what the expression does.
EDI User Guide

8-272
EDI Expressions
Expression Description
Code
Explanation
Expression
CDH
tdpur400.ddtc <> 0
Confirmed Delivery Date Hdr
Evaluation: True if a delivery date is specified at the order header

CDL
Confirmed Delivery Date Line
tdpur401.ddtc <> 0
Evaluation: True if a delivery date is specified at the order line

CWAD
Warehouse Address
tccom100.inrl = tcyesno.no or
(strip(tcmcs003.cadr) <> )
Evaluation: True if business partner is an external trading partner

(the business partners Affiliated Company check box is selected,
implying not a multisite business partner), or an address code has
been assigned to the warehouse
HDRDEL
P.O. Specific Delivery Address
(strip(tdpur400.cadr) <> and
tdpur400.cadr <>
tcmcs003.cadr)

implying not a multisite business partner); OR business partner is
a multisite business partner and the delivery address code
specified on the purchase order differs from the warehouses
default address code
IFAD
Invoice-from Specific Address
(strip(tdpur400.ifad) <> and
tdpur400.ifad <>
tccom122.cadr)

(affiliated company field of business partner is set No, implying
not a multisite business partner); OR if business partner is a
multisite business partner and the invoice-from address code
specified on the purchase order differs from the invoice-from
business partners default address code
INVIT
Invoice Spec. Invoice-to

Address
(strip(cisli205.itoa) <> and
cisli205.itoa <> tccom112.cadr)

implying not a multisite business partner); OR if business partner
is a multisite business partner and the invoice-to address code
specified on the invoice differs from the invoice-to business
partners default address code
EDI User Guide

8-273
EDI Expressions
Code
Expression
-INVLNT
(strip(cisli245.stoa) <> and
cisli245.stoa <> tccom111.cadr)
Inv. Order line sped. Delivery

is a multisite business partner and the ship-to address code
specified on the invoice differs from the ship-to business partners
INVOF
Invoice-from Specific Address
(strip(tdpur400.ifad) <> and
tdpur400.ifad <>
tccom122.cadr)

is a multisite business partner and the invoice-from address code
specified on the purchase order differs from the invoice-from
INVPF
Inv. Spec. Pay-from Address
(strip(cisli205.pfad) <> and
cisli205.pfad <> tccom114.cadr)

is a multisite business partner and the pay-from address code
specified on the invoice differs from the pay-from business
INVST
Inv. Spec. Ship-to Address
(strip(cisli205.stoa) <> and
cisli205.stoa <> tccom111.cadr)

specified on the invoice differs from the ship-to business partners
EDI User Guide

8-274
EDI Expressions
Code
Expression
ITAD
(strip(tdsls400.itad) <> "" and
tdsls400.itad <> tccom112.cadr)
Invoice-to Specific Address

is a multisite business partner and the invoice-to address code
specified on the sales order differs from the invoice-to business
LNDEL
P.O. Line Specific Del Address
(strip(tdpur401.cadr) <> "" and
tdpur401.cadr <>
tcmcs003.cadr)

is a multisite business partner and the delivery address code
specified on the purchase order line differs from the default
address code of the order lines warehouse
EDI User Guide

8-275
EDI Expressions
Code
Explanation
Expression
LNSTAD
(strip(tdsls401.stad) <> "" and
tdsls401.stad <>
tccom111.cadr)
Line Ship-to Specific Address

specified on the sales order line differs from the ship-to business
OFAD
Sold-to Specific Address
(strip(tdsls400.ofad) <> "" and
tdsls400.ofad <>
tccom120.cadr)

is a multisite business partner and the sold-to address code
specified on the sales order differs from the sold-to business
ORGSHD
Warehouse order - Schedule
strip(tdsls308.pchn) <> ""
Evaluation: True if the customer release number is specified.

OTAD
Buy-from Specific Address
(strip(tdpur400.otad) <> "" and
tdpur400.otad <>
tccom120.cadr)

is a multisite business partner and the buy-from address code
specified on the purchase order differs from the buy-from
EDI User Guide

8-276
EDI Expressions
Code
Expression
PFAD
(strip(tdsls400.pfad) <> and
tdsls400.pfad <>
tccom114.cadr)
Pay-by Specific Address

is a multisite business partner and the pay-by address code
specified on the sales order differs from the pay-by business
PRBF
Pur. Rel. Buy-From B. P.
(strip(tccom120.cadr) <> )
and tccom120.cadr =
tccom130.cadr
Evaluation: True if a default address code has been defined for

the buy-from business partner.
PRSF
Pur. Rel. Ship-From B. P.
(strip(tccom121.cadr) <> ) and

tccom121.cadr =
tccom130.cadr
Evaluation: True if a default address code has been defined for

the buy-from business partner.
PRSTW
Pur. Rel. Ship-To Warehouse
strip(tdpur307.cadr) <> or
strip(tdpur307.cwar) <>
Evaluation: True if a delivery address code or the warehouse

code specified on the schedule line differs from the default
address code has been defined for the buy-from business
partner.
PTAD
Pay-to Specific Address
(strip(tdpur400.ptad) <> and
tdpur400.ptad <>
tccom124.cadr)

is a multisite business partner and the pay-to address code
specified on the purchase order differs from the pay-to business
EDI User Guide

8-277
EDI Expressions
Code
Expression
SFAD
(strip(tdpur400.sfad) <> "" and
tdpur400.sfad <>
tccom121.cadr)
Ship-from Specific Address

is a multisite business partner and the ship-from address code
specified on the purchase order differs from the ship-from
STAD
Ship-to Specific Address
(strip(tdsls400.stad) <> "" and
tdsls400.stad <> tccom111.cadr)

specified on the sales order differs from the ship-to business
WHSTAD
ASN Ship-to Specific Address
(strip(whinh430.stad) <> "" and
whinh430.stad <>
tccom111.cadr)

specified on the shipment notice differs from the ship-to business
WUOM
Weight Unit of Measure
(whinh431.grwt <> 0 or
whinh431.ntwt <> 0)
Evaluation: True if a gross weight or a net weight has been

specified on the shipment line.
ADSQTY
Discrepant Qty (Assignment)
Abs(whinh301.squa
whinh210.astk)
Assignment: Calculates the difference between the quantity

shipped as indicated on the shipment notice (ASN) line, and the
actual quantity received as recorded when entering the receipt.
EDI User Guide

8-278
Appendix B: Glossary
American National Standards Institute

Central body responsible for the identification of a single consistent set of
voluntary standards called American National Standards. ANSI is also the US
representative to nontreaty standards organizations.
Code in application
A code used within the Baan application that needs to be translated before
sending the message. An example of a code in application is the order type or the
trading partner (customer or supplier) code.
Code in message
The code in message refers to a standard code that is used within a specific EDI
message and must be translated to or from to a value within your system. A code
in message might be the standard code for unit of measure. This unit of measure
may or may not be the same as your internal unit of measure and must be
translated in order to transmit the correct unit.
Conversion setups
Conversion setups define the file layout of the ASCII files received into and
generated from Baan EDI for your EDI messages.
Conversion table
A Baan application table that holds the different code conversion values
identifying the relationship between an external code (code in message) and the
code in the Baan application (code in application).
EDI
See Electronic Data Interchange.
EDIFACT
Electronic Data Interchange for Administration, Commerce and Transport.
International Standard defined by ISO.
Electronic Data Interchange (EDI)
The computer to computer transmission of a standard business document in a
standard format. Internal EDI refers the transmission of data between companies
on the same internal company network (also referred to as multisite or
multicompany). External EDI refers to the transmission of data between your
company and external trading partners.
EDI User Guide

9-1
Appendix B: Glossary
Payment order/Remittance advice

Information furnished to the supplier by the customer, detailing the transactions
being settled by a payment. Refer to ANSI X12 820 for additional information
and the standard specification for electronic communication of such data. The
corresponding European transactions are: REMADV (ODETTE and
UN/EDIFACT).
Purchase order
A purchase agreement for goods/services between trading partners. See ANSI
X12 850 for additional information. The corresponding European transactions
are: ORDERR for ODETTE and ORDERS for UN/EDIFACT.
Ship notice (ASN or SN)
An electronic notification to the customer that lists the contents of a shipment of
goods and additional information relating to the shipment prior to receipt. See
ANSI X12 856 for additional information. The corresponding European
transactions are: AVIEXP for ODETTE and DESADV for UN/EDIFACT. Also
referred to as dispatch notes or packing slips.
Trading partner
The sending and/or receiving party involved in the exchange of electronic
business documents.
Transaction set
A complete business document such as a Purchase Order, Invoice, or Sales
Order. Synonym for document or message.
Translation
Commonly used to refer to the conversion of a companys internal data formats
to and from any of the standard data formats, for example: X12, EDIFACT,
ODETTE.
VAN
Value Added Network. A company that provides communications services for
EDI such as line speed conversion and protocol matching.
VDA
Another standard for automotive electronic interchange of business transactions
within Germany. This particular standard uses a fixed length field/record format.
X12
ANSI standard for interindustry electronic interchange of business transactions
within the US.
The accredited subcommittee of American National Standards Institute whose
mandate is to develop standard data formats for business transactions with crossindustry application.
EDI User Guide
9-2

BaanERP - EDI User Guide

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

BaanERP - EDI User Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

EDI User Guide

2 General setup for EDI

3 Setting up your company

5 Incoming message data

Changing the purchase order (860/ORDCHG)

EDI User Guide

8 Appendix A: Conversion setups

EDI User Guide

Conversion setup: 862S, Shipping Release

EDI User Guide

About this document

This document explains the issues involved with the implementation of

Preliminary setup steps

EDI User Guide

EDI User Guide

In todays business environment, companies face increasing order volumes and

Figure 1 Electronic data interchange (EDI)

EDI User Guide

EDI User Guide

Default conversion setups for the supported transaction sets

Outgoing messages by session, which link all supported outgoing messages

EDI User Guide

Advance Ship Notice

Purchase Order Change

Purchase Order Change

EDI User Guide

The setup of data is structured as follows:

General data setup of EDI company

Setup of purchasing company: setup specific to defining your trading partner

Setup of selling company: setup specific to defining your trading partner as

EDI User Guide

EDI User Guide

General setup for EDI

Maintain EDI parameters

EDI User Guide

General setup for EDI

Figure 2 EDI setup

EDI User Guide

General setup for EDI

Figure 3 EDI Parameters (ecedi0100s000) session, defaults

EDI User Guide

General setup for EDI

A check box that indicates if EDI is implemented in this

Select the directory in which all EDI-related data is

The communication address that is used by your

The reference number that is used for outgoing

A string of characters defined in the Fixed Part field

The system date in one of several formats (Date

The fixed part of the reference number.

The date format of the reference number.

First Free Number

The next available sequence number.

Action on New Date

Because the date is included in the reference number,

EDI User Guide

General setup for EDI

Suppress Blank Text

If this check box is selected, empty text lines in text

Suppress Blank Text

If this check box is selected, blank text lines received in

Make Use of Tracefile

A check box that indicates if a Trace file is used. See

The name of the trace file.