Is EDI implementation in LN different than Baan5 C or Baan IV?
Refer to the SSA-ERP-LN documentation ->
Document code : P3496B US
Release : SSA® ERP LN 6.1
Document title : Functions & Features
Publication date : July 04
10-2 | Electronic Commerce
Before you can use EDI, a great deal of setup must be made. As a result,
codes for organizations, such as BEMIS, must be entered, the messages that
must be exchanged, such as MRL001 for sending data related to material
releases, the messages that are relevant for each business partner (not all
business partners will need EDI messages) and the moment (the SSA ERP
session) the EDI message must be generated. For example, during the
Approve Release Lines (tdpur322m100) session an EDI Message for the
Material Release (MRL001) must be generated.
All the EDI messages must be stored somewhere, because all the
information is all electronic data. The user must define in the Network
session, where the data must be stored. The business partner data is linked
to this type of network.
The conversion sessions are an important of the entire EDI module. You can
enter the codes, for example, for addresses, currencies, countries, and
schedule types in the system. This helps to interpret the meaning of the EDI
The user can see, in the conversion setups for each message, which table
fields will become part of this type of message, what level the table field has
in that message, and the length of the message.
When all codes are defined, the setup can be made for conversion-in data,
so that incoming EDI messages can be transferred in the standard SSA ERP
data, and for conversion-out data, so that messages are correctly
transformed from the SSA ERP system. A good example where this
functionality is required is the item code. In the SSA ERP system, an item
can have code ABC, whereas at the other party, the same item has code
123. To make sure that the other party will get the right information, this type
of conversion must be made.
In addition, you can define specific conversions for each business partner,
and you can perform import and export of messages.
Electronic Commerce | 10-3
A separate module is present that handles the processing of the EDI
messages. Messages can be generated for a particular network or being
imported from a particular network.
If message-generation fails, and required changes are made (either in ERP
or in the EDI module), you can try again to generate EDI messages.
You can view the messages that were received. If the conversion failed so
that the message could not be processed, the old data remains there, and
you can retry to perform the conversion. The user can always see the old
In the outgoing file, the EDI-messages are stored, which must be processed.
If processing the message was successful, the data for being processed is
removed from the Messages to Be Generated session. In the history
sessions, all relevant data is still available for the user.
In EDI, the sessions that are triggering the BEMIS EDI message are defined.
As a result, the functional session, for example, the Print Release session
checks if the session is defined in EDI and, if so, a trigger is set in EDI that a
BEMIS EDI message must be created for the printed release.
10-4 | Electronic Commerce
The following table lists the messages that can be generated from the
various SSA ERP entities:
Code Name of the message Related Business Object where
message is used
DIS Dispatch Advise ASN
FML Load info to Carrier Freight Management
FMS Carrier Status info Freight Management
INV Trading Invoice Invoice
MRL Material Release Purchase Schedule
OCA Order Change
Purchase Order & Sales Order
ORC Order Change Purchase Order & Sales Order
ORD Orders Purchase Order & Sales Order
ORS Order Response Order Management
RAD Remittance Advise Finance
SEQ Sequential Shipping Schedule Purchase Schedule
SHP Shipping Schedule Purchase Schedule
ERN Error Notification
RDN Receipt Discrepancy
You can group data from multiple Business Objects into one EDI message.
The order information, for example, also contains address information, which
is another Business Object.
To be able to compare data present in an EDI message, a print session
called the Print Compare Conversion Setups (ecedi5400m000) session is
available, which provides an overview of which data is present in the
incoming messages and which data is present in the outgoing messages.