EDI Setting Up: Code and Conversions Menu (BaanERP)
EDI Setting Up in BaanERP system depends on how a particular company is used – a company needs to set up the purchasing profile, the sales profile or both. See previous post for detailed information.
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. Additional code conversions that you may want to consider as the purchasing company include the following:
- 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.
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 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.