Sap Agreement Table

On this blog, I would like to give you an overview of framework contracts in SAP® in the Purchasing module. In addition to the sketch of the concept itself, I give you an overview of the image from the point of view of data analysis, in other words SAP® tables and field plan. Therefore, if we add document types to our table above, it looks like this (this time I omitted the categories of documents and the types of documents that are not related to the contract: contract The contract is a draft contract and they do not contain a delivery date for the material. The delivery plan is a long-term sales contract with the seller, in which a supplier is required to supply material on specified terms. information on the delivery date and quantity communicated to the supplier in the form of the delivery plan. The objective of framework agreements is usually to set a ceiling or a total volume (i.e. a target). For quantitative contracts, this is very specific to individual materials and therefore often to a material number (box: EKPO_MATNR), because.B this is where the number of parts or units plays an important role (even if there are other possibilities for an unknown material or consumer, but I will not come back to it here). For this reason, the reference value must be found at the level of the contractual position, because the target quantity (box: EKPO_KTMNG) multiplied by the price of each material gives the reference value (box EKPO_ZWERT) of each position. For value contracts, the quantity of items is often secondary, as the total value of the order matters.

For example, a facility management contract of €1,000,000 can be concluded with a supplier. This includes the three points of building cleaning, possible repairs and disposal. In this case, individual sizes can be assigned much less concretely, and an overall construction makes more sense. Another example would be office equipment (pens, post-it notepads) that is too “singular” at the room level to be defined in a framework agreement. We are in the process of creating modification BDCs in which we do not get the table in which the data is stored. The above categories of supporting documents are assigned to each purchase receipt in the EKKO head data table as an attribute (field: EKKO_BSTYP). This means that the category of documents allows us to distinguish delivery plans from other contracts.. . .