Framework contracts are an important issue that we must constantly address in our data analytics for procurement. Unlike individual contracts, which are often ad hoc, framework contracts are constructions aimed at a longer-term business relationship. We can establish a delivery plan with or without connection to an order request or framework contract, a request or even another delivery plan. You can clearly see the category (K or L) and the associated document type (LP, WK, MK). Our system includes a total of 154 contracts. Supplier selection is an important process in the procurement cycle. Suppliers can be selected through the offer process. After pre-selecting a supplier, an organization enters into an agreement with that particular supplier to deliver certain items under certain conditions. When an agreement is concluded, a formal contract is usually signed with the supplier.
A framework contract is therefore a long-term sales contract with a supplier. – The conditions of a framework contract apply up to a specified period and cover a certain quantity or predefined value. SA versions can be generated for delivery plans with output documentation. The release of the delivery plan can be done manually or automatically using a report. SA shares can be generated either for all selected positions in the relevant delivery plan or only for positions for which classifications are rearranged or changed. A contract is a long-term framework contract between a supplier and a customer for a predefined hardware or service over a specified period of time. There are two types of contracts – let`s start with examples of different types of framework agreements. Here it is: a framework agreement can consist of the following two types – the above categories of supporting documents are assigned as attributes to each purchase receipt in the data table of the head of the EKKO (field: EKKO_BSTYP). This means that the class of documents allows us to distinguish delivery plans from other contracts.
But how to distinguish value contracts from volume contracts? This is where the type of evidence described above begins: in the standard is the type of proof “MK” for volume contracts and “WK” for value contracts. However, both types of records have the same class of “K” records. While document categories are primarily used for categorization, document types are often used to customize them, i.e. assign attributes to document types that are then used to organize/control processes in a system. You can also find them in the EKKO table, the field name is EKKO_BSART. 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. Now that we have discovered where framework agreements are held as data – in tables where “standard” commands are suspected – and how to identify them – by document type and document type – we now look at some aspects of the process.
Data model: Orders and framework contracts You can create delivery plans with or without publication. With release, documentation is advantageous, because in this case you have sent a supplier a record of the delivery plan information that you can view at any time. To refer to default commands, you can .B. use the ME23N transaction; T-Code ME33K shows you contracts, and ME33L is the right thing to do for delivery plans. You can see that the category of supporting documents Mnemonik K and L is also present in part in the transactions. 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 the number of parts or units here plays an important role (even if it exists, for example.
B for an unknown material or consumer, other possibilities that I will not discuss here). . . .