– Discount agreement access sequences (tables T682) Now that we`ve discovered where framework agreements are kept as data — in tables where you really think “standard” commands are by document category and document type, and how to identify them, let`s now see some aspects of the process. You can clearly display the category (K or L) and the type of document associated (LP, WK, MK). Our system includes 154 agreements. Appendixes: Up to 10 attachments (including images) can be used with a maximum of 1.0 Mb and a total of 10.5 Mb. Access EKKO and BSART (purchase type) as wK or MK with BSTYP (purchase category). Let`s start with examples of different types of framework agreements. Here I look: in which table are the contract data (ME31K) stored? – Conditions for discount agreements (tables T685, T685A, T685T) In many areas, SAP follows® a proof category concept and type of proof. The document category is a rough classification, the type of document is the finer differentiation of the document category. When analyzing a market scenario, you may be interested in the following four categories of documents: Framework agreements are an important topic that we need to constantly address in our data analysis for purchases.
Unlike individual contracts, which are often ad hoc, framework agreements are constructs for a longer-term business relationship. 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. The storm board is the BSTYP field of the EKKO table. – Range of numbers for arrangement types (to be maintained manually) Now it becomes exciting (at least for data analysts): framework agreements such as volume contracts, value contracts and delivery plans are not stored in their own tables, but also in the EKKO and EKPO tables. So don`t get confused by names or take them too literally. Agreements are now at the origin of a long-term structured procurement process. But what about individual buying on the concrete basis of an agreement? We are also talking about call-offs. These are specific specific markets, in reference to the framework agreement.
How you can determine these searches by analyzing the data, the tables in which they are recorded, and whether the information about goods and invoices is relevant or relevant in this context – this is something for the next post in the series. 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. Data model – commands and framework agreements I hope you enjoyed starting the topic of framework agreements, and that we will soon meet here for the second part, “Outline Agreements – Call-off Documentation “. – Copying the order settlement note (TVCPF, BM1 and BM3 tables) This is a little more technical, but here, for the sake of completeness, a screenshot of the document type table with customization settings in SAP® if they are necessary for data analysis purposes. The circles of numbers for the corresponding types of proofs, such. B that field selection parameters, etc., are included in this table: the objective of framework agreements is usually 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).