Sap Pricing Agreement Table

Here are the prices of the selected product. Price for contract items By clicking on the hat icon (head data – remember?) you get to where the target value of the contract is visible (in this case, of course, the sum of both items). I will now take a closer look at the target values for articles and heads in framework agreements. To create a context, we start with ordinary tasks: as far as the database is concerned, these are stored in SAP® in the tables EKKO (command head) and EKPO (command position). If you want to track it, you can use z.B. the table browser SE16 to view the contents of the table. 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. Then you will set access sequences, after this access sequence, check the accesses that contain the tables sought (z.B. A016)…

To return to standard commands, you can use z.B the ME23N transaction. T-code ME33K shows you contracts, and ME33L is correct for delivery plans. You can see that the category of Mnemonics K and L vouchers also appears in part in bookings. First table to get the proof of purchase (contract in your case) – EKKO (head of purchase) – > Pass your type of proof in the field EKKO-BSART and find your proof of contract if you already know that you already know the proof of the contract, then pass your purchase document nr. in the table – A016 (contract article) in the A016-EBELN archive and note the conditionality rate no. A016-KNUMH (Note: If you have as many lines as zeilee in the contract document, you will receive the same no to the A016 registration) if you have three elements in the contract, then you will receive all three records in the A016 by filing the contract document no in the EBELN A016 submitted. Now that you have received the “no” condition of A016-KNUMH, you do not have this condition in the KONP (article) conditions table in the field – KONP-KNUMH and you will discover the value of each wise position value of the contract status. 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. I hope that you have enjoyed addressing the issue of framework agreements and that we will soon meet again for the second part of the “Call Agreements”. In value contracts, the quantity of items is often secondary, since the total value of the contract counts. For example, a “facility management” contract of 1,000,000 euros could be concluded with a supplier. This includes the three building cleaning, repair and disposal items. In this case, individual quantities can be attributed in a much less concrete way and an overall structure is more judicious. Another example would be office equipment (pens, post-it notebooks), too “singular” in individual articles to be punished in a framework agreement. What are the tables that bind the contract (ME33) and its price condition (MEK3 – PB00)? If you want to view individual hardware prices, select this position and press the “These Conditions” button.