You can create a new type of document by managing the existing type of document, and then rename it with your new type of contract. 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 timetable can be established in two ways: very good information in this forum about the delivery plan As a general rule, the objective of the 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. Framework agreements are an important issue that we must constantly address in our analysis of procurement data. Unlike individual contracts, which are often ad hoc, framework agreements are constructs for a longer-term business relationship. Customer contracts are framework customer agreements that indicate when sales materials or services are sold within a specified time frame. It is possible to create a delivery plan by being a legal document, the system will ask you to fill out the validity data: the main points they must respect in a framework agreement are as follows: press F3 or return to the main screen. Switch to Edit > Incompletion Log or Ctrl-F8 to see if the delivery plan we just created is complete. Open Incompleteness Protocol for a Delivery Plan In value contracts, the quantity of items is often of minor importance because the total value of the contract is significant.
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. 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. Delivery plans are defined and managed as supporting documentation in the system. It is possible to group these documents into different types of documents according to commercial requirements.
First, you need to define the types of document and their attributes when adjusting. A contract is a framework agreement between you and your client, valid for a specified period of time. The contract does not include classifications, quantities or delivery dates. The same functions are available in contracts as in orders. They can also agree on specific price agreements. The customer completes the contract with individual permissions. Divisions are created in the share command when they are placed. The release order is then treated like any standard command.