Here we would like to draw your attention to the ME31L transactional code in SAP. As we know, it is used in the SAP MM-PUR component (purchase in MM) included in the MM module (materials management). ME31L is a transactional code used to establish delivery plans in SAP. Contract The contract is a decision of a contract that does not contain a delivery date for the material. The contract is composed of two types: the purchasing system takes care of the requirement and offer information to help you fulfill an order. As with order requests, you can generate pods yourself or have them generated automatically by the system. Suppliers` delivery plans and contracts (types of longer-term sales contracts in the SAP system) are also supported. Step 4 – Indicate the delivery date and target quantity. Click Save. For the delivery plan, classifications are now maintained. The Purchase component helps you identify potential sources of supply based on past orders and existing longer-term sales contracts.
This speeds up the process of developing Requests for Tenders (RFQs) that can be sent electronically to suppliers via SAP EDI upon request. A delivery plan is a long-term framework contract between the supplier and the customer for predefined material or service that is provided on predefined dates within a time frame. A delivery plan can be established in two ways: the delivery plan is a long-term sales contract with the supplier, in which a supplier is required to supply material according to the set conditions. information on the delivery date and quantity communicated to the supplier in the form of the delivery plan.