EDI Setting Up: A purchasing company Or A sales company profile (BaanERP)
EDI Setting Up in BaanERP system can be done for 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.
EDI Setting Up – 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 in BaanERP system 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.
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. 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.
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.