The type of command commands z.B. assigning numbers for an order and determines which fields you need to maintain. Try to do it as well, I hope the planning details will be stored in the VBEP table, then get the vbeln from there and get the non-state set The EKKO-BSART document type distinguishes the different types of requirement and control in the SAP system. A contract is a long-term framework agreement between a lender and a customer via pre-defined equipment or service over a period of time. There are two types of contracts – the first list contains only tables of data in. In the next part, the customization tables for the order will be listed in the SAP-MM purchase. A delivery plan is a long-term framework agreement between the lender and the customer on pre-defined equipment or service obtained on pre-defined dates over a period of time. A delivery plan can be drawn up in two ways: the basic data table of lenders in SAP is LFA1 for general information. (Note that some of the following SAP tables contain SAP-PO-related masters) The main SAP control tables are EKKO. Each order is identified by EBELN (PO number) It was in KONP,But there is no link field for each delivery plan. A framework contract is a long-term sales contract with a creditor that contains terms and conditions for the equipment to be provided by the creditor.
Step 4 – Indicate delivery date and target quantity. Click Save. The planning lines are now maintained for the delivery plan. A framework agreement may be of the following two types: The delivery plan is a long-term sales contract with the Kreditor, in which a creditor is required to provide equipment on pre-established terms. Details of the delivery date and the amount communicated to the creditor in the form of the delivery plan. Step 2 – Include the name of the creditor, the type of contract, the purchase organization, the buying group and the factory with the date of the contract. The framework agreement is a long-term sales contract between Kreditor and Debitor.