Contracts are agreements between the customer and the seller for the supply of materials/services at a fixed price between a specified period of time. Many types of Contract Management subscription contracts help manage complex contracts that can be bundled across multiple product and service offerings. Users can manage contracts for customers by adding items, changing terms, tracking usage, and removing contract items. It can be treated in two ways in SAP S/4HANA. The “Manage the sales contract” app is used to process subscription contracts in SAP S/4HANA. Below, you`ll see a comparison with the contract over the course of a year by monthly payments based on a defined billing plan. These monthly payments are obtained by creating down payment payments. After the delivery of all items and open balances, this subscription contract can be concluded. Note: If you first complete your relevant distribution organization, distribution channel and division and then choose the corresponding type of contract, only the types of contracts relevant to the selected distribution organization, distribution channel and division will be displayed. Billing Request Here you assign the type of billing requirement you want to use to initiate billing processing into your contract. In short, it is an agreement on the distribution of quantities and dates. Press Entry once you`ve selected the sold part, so the SAP system can accept the debitor and continue the implementation of the contract.
Choose Ship-To Party The following basic data is involved in creating a contract. This basic data collects relevant information and fills the relevant fields accordingly. Contract data is allowed Here, you determine whether the type of proof of sale should allow the display of the contract`s data screens when you enter a sales accounting using your type of contract. You can select X to authorize the contract data for the sales receipt, you can use Y to force the flow of article contract data from the head contract data, and you can leave the value in that empty field to remove the contract data screens for your contract type. Junior contracts, which refer to basic contracts, are bound by referencing requirements. The referencing criteria are indicated in the SDGK reference procedure. Fields that can be mentioned in the contract at a lower level are listed as technical fields (table, field combination) with copy rule and message. As shown in the illustration below, the rules of reference copy can be “A” – Check on the agreement, “B” – always copy or “C” – copy only if it is. These copying rules are used to exaggerate customer-related data (incoterms, payment terms, controllability, etc.) through the data in the head of the contract. The message flag is used to display a warning message if the data differs. However, this message cannot be changed to configuration errors. A quantity contract is a delivery agreement of a fixed quantity over a specified period of time.
As the customer promises to buy the fixed amount of goods/services, he gets a reduced price. Contracts can be executed through a single contract or by several contracts called to the contract during the specified period. These unlocking contracts must be established with reference to the contract. If the customer knows the execution data at the time of creation, a delivery plan can be drawn up in place of the contract. Quantity Contract – This type of contract indicates the total value of the equipment provided by the supplier.