Condition Record Of Rebate Agreement

Final statement: here we must specify the type of proof `B1` for the establishment of the Belegrabatt credit requirement during the final statement to the customer. Below you can see all transactions to reflect how the discount is calculated at the invoice level Here, the packaging mode is assigned to the condition type group that is assigned through BO01 – Customer/Material or Customer/Discount Group = % BO02 discount – Customer/Material = based on BO03 quantities – Customer = % BO04 discount – Customer hierarchy = % BO05 discount – Customer/material hierarchy = BO06 discount – Sales volume. Independent For the most part, you will find most of the reduction configuration in the following node in SPRO: several packaging sets for each material or a group of materials purchased by a customer are created in the discount contract. Each registration may indicate the amount of the rebate either as a percentage or as a fixed value. In addition, condition records can use rates, which allows the customer to earn more discounts by purchasing more products. Discount agreements are indicated in the header of the billing slips (in the area of price data) and allow SAP to track the business volume of a given customer. Depending on the SAP configuration, it is possible to automatically account for provisions at the same time as the billing slips, so that the cumulative amount of discounts is recorded in the accounting. For the payment of the discount to the customer, it is necessary to pay the discount contract. The settlement of the reduction contract leads to the issuance of a credit to the customer on the amount of the accumulated discount. Default Status: Specifies the default status of the discount agreement. In general, it will be “open”. With this contribution, we continue our series of articles, which deals with potential SAP interview questions.

Today we will discuss the issue of the interview as part of the discount agreements concluded at SAP. This SAP feature relates to sales and distribution (SD), Billing (BIL). Therefore, this contribution should be of great interest to SAP SD consultants. You should not consider the message as an “error” only as a warning. As Suresh noted, an inconsistent message is displayed whenever a discount has been made a posteriori (in fact, with a launch date of today or in the past); (b) You have changed the discount that would affect the value of the discount: demarcation rate, validity period, products. . . .