EDI Messages Additional Parameters (BaanERP)
EDI messages are represented by various purchasing documents such as purchase orders, purchase changes and purchase schedule releases (planning release, shipping release, sequenced shipping release) sent from one party to another. After completing the general setup BaanERP system steps (see previous posts for basic info), 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.
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.
- n 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.
EDI Parameters for Purchase Invoice and Credit notes: You can define a Transaction Type and a Batch Reference for EDI Purchase Invoices in the ACP Parameters (tfacp0500m000) session. You can also indicate if you want a separate Transaction Type for Credit Notes. If so, can also specify the Transaction Type and Batch Reference for Credit Notes.