General purchase dataBefore you can perform purchase procedures, you must specify general purchase data, such as an approver list for use in the purchase requisition procedure, data to track order changes and to determine the reason for the changes, and additional cost sets. Specifying additional cost sets Additional costs can be placed on an order as extra cost (items) after the last item is recorded. Several additional cost items can be assigned to an order by bringing them together in a cost set. LN can automatically apply these cost sets to purchase orders. For more information, refer to Additional costs on purchase orders. Setting up the approver list Before a purchase requisition can be converted to a purchase order or a request for quotation (RFQ), it must be approved by an approver that appears on the approver list. For more information, refer to Purchase requisition approval process. Specifying data to track order changes and determine the
reason for the changes Because a company’s requirements can change during the order process, purchase orders are dynamic documents. You can specify change codes and acknowledgement codes to track order changes and the reasons why these changes occurred. Although this functionality is designed to work specifically with EDI, a company without EDI functionality can also use these codes to record changes. You can use change codes to maintain information regarding order changes that are tracked for historical purposes. You can use acknowledgement codes to manually record information regarding changes that are communicated by the purchase business partner. A purchase order acknowledgment is a message sent by the purchase business partner to the purchaser to confirm the receipt of the purchase order. This usually implies the acceptance of the order by the purchase business partner. To maintain and track changes:
| |||