The only time we use an order is for a testbuild in which the components are not approved for use by our customers, then EVERYTHING goes to a schedule agreement. We have set our schedules for the expiry of 31.12.9999, unless of course we have a planned reduction in Credit A on Credit B at a predetermined date. Step 2 – Include the delivery plan number. As a general rule, contract functionality is used, but normally the agreement is used in the automotive industry. Delivery of the total amount of material indicated in a delivery plan item is distributed, over a period of time, in a delivery plan consisting of positions indicating the different quantities with the expected delivery dates. The delivery contract is a long-term sales contract in which you establish delivery plans whenever needs change or at predetermined time intervals. The delivery plan can be made on time/day/week/monthly. But it will contain different areas, z.B. Enterprise/Tradeoff/Forecast. Fixed zone plans are confirmed requirement and must be taken by the designated party. The trading area is the purchase of raw carpets and the customer is required to pay the costs of the raw material in case of cancellation of the requirements.
The requirement of the forecast area is to help the lender plan its requirements. The delivery plan is a long-term sales contract with the Kreditor, in which a creditor is required to provide equipment on pre-determined terms. Details of the delivery date and the amount communicated to the creditor in the form of the delivery plan. Now that we have discovered where the framework agreements are kept as data — in tables where you actually suspect standard commands — and how to identify them — by document category and document type — let`s look at some aspects of the process. The framework agreement is a framework for long-term agreements, such as contracts and supply contracts. In the case of a value contract or volume contract, you must enter into sharing contracts. In the case of delivery plans, delivery dates must be included in the classifications, so that no release order is required. SA is also an agreement with the seller for the delivery of matl, can be a quantity or a value. Delivery dates are maintained in ITS SA`s ME38 ref, which are referred to as delivery plans. This allows you to manage the delivery plan and communicate the credit carrier on the basis of Forecase or JIT. And if you need a little more matl, then only SA deliveries are created with ME38. SA can be 2 types:- without an exit documentation system, delivery information is transmitted to the supplier as soon as you have registered the document.
As a general rule, the objective of framework agreements is to set a ceiling or a total volume (i.e. a target value). For quantity contracts that are very specific to individual materials and therefore often related to a material number (field: EKPO_MATNR), because the number of parts or the number of parts play an important role here (although there are other possibilities. B for an unknown material or consumables that I will not study here). This is why the target value here is at the level of the respective contract position, since the target quantity (field: EKPO_KTMNG) multiplied by the price of the material in question gives the reference value (field: EKPO_ZWERT) of each item. By clicking on the hat icon (which recalls the head data -?) you get to where the target value of the contract is visible (in this case, of course, the sum of the two elements).