Contract is the agreement between the customer and the company on the basis of equipment, quantity and price over a specified period of time. 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. But later. Select the right type of contract to prepare for the next step. Please note that each field with a “ick-sign” means that it is mandatory and must be replenished, otherwise the system will not allow you to go any further. To choose the type of contract required, either tap F4 on the respective field and all LoVs (value list) are displayed. List of types of contracts The main points you must meet for a framework agreement are: The delivery plan is also an agreement with the debtors, but contains the preset delivery dates (schedule positions) and quantities. After entering the start screen of the contract setting up, you must choose the corresponding type of contract. Each type of contract has its own functionality and configuration-based display that runs during the backend. 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). I will now take a closer look at the target values for articles and heads in framework agreements. Quantity Contract – This type of contract indicates the total value of the equipment provided by the supplier.
So if we add types of proofs to our table above, the situation is this (this time I omitted the categories of proofs and the types of proofs that are not relevant to the contract: by a brief narrative, it is an agreement on quantities and filing dates. 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. 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: “A contract is a framework agreement…… The contract does not contain futures, deliveries or delivery dates.” You can set your own type of document for contracts in the following way: It`s a little more technical, but here, to be complete, a screenshot of the document type table with customizing settings in SAP® if they are needed for data analysis purposes. This table contains circles of numbers for the corresponding types of proofs, z.B. The parameters for selecting fields, etc., are included in this table: contracts are often higher. 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).