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. It`s a little more technical, but here, for the sake of completeness, a screenshot of the document type table with customizing settings in SAP® if they are needed for data analysis purposes. This table contains numbers for the corresponding types of proofs, such as. B as field selection parameters, etc.: in SAP-MM purchases, these agreements are subdivided into “contracts” and “delivery plans.” The delivery plan is nothing more than a long-term sales contract in which you can set delivery times whenever predefined needs or intervals change. We can categorize the delivery plan by hour or day or week or month. In many areas, SAP follows® a category concept of proofs and occupancy. The document category is a rough classification, the type of document is the finer differentiation of the document category. With regard to the analysis of a command scenario, you may be interested in the following four categories of documents: I hope you enjoyed entering the theme of framework agreements and that we will meet soon for the second part “Outline Agreements – Call-off Documentation “. Step 2 – Include the delivery plan number.
As with other purchase documents, a framework agreement consists of the following: The delivery contract 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. The main points to be taken into account in a framework agreement are: A contract is a long-term framework agreement between a borrower and a customer via pre-defined equipment or a service over a certain period of time. There are two types of contracts – contracts are often superior. This may be the case with SAP® because the buying organization is essential (and the work that may be related to the purchase organization). The purchase organization is shown in the EKKO table for each agreement (field: EKKO_EKORG). However, in high-demand structures, large contracts (for example. B the purchase of laptops throughout the company) are negotiated centrally and can then be used in a decentralized manner.
In this case, it is possible to cooperate with near-superior purchasing organizations, which are attached to decentralized purchasing organizations as a reference purchasing organization. They can then use and consult framework agreements established under the reference purchasing agency. From the data analyst`s perspective, you will find in table T024Z the allocation of purchasing organizations (field: T024Z_EKORG) to possible business reference organizations (field: T024Z_EKORZ). When creating a contract, you can choose between the following types of contracts: You can clearly display the category (K or L) and the number of corresponding occupants (LP, WK, MK). Our system includes 154 agreements. Futures agreements, on the other hand, are based more on quantities and, in addition, on concrete quantities of delivery on certain delivery dates (we are talking about dates). Quite simply, these are more restrictive quantitative contracts – but in the analysis of the data in SAP® they appear separately with their own category of supporting documents in relation to volume or value contracts.