Final count: Here we must indicate the “B1” file to create Belegra`s discount credit requirement, while the final tally is final to the debitor. Thank you very much and I appreciate your contributions so far and I wonder how you will get all this information on the transparencies and internal tables. Hey, Mike. Do you know if it is possible to include a new field in the preview agreement, scope? I need the reference number. view the VBRK-XBLNR billing document. Thank you in advance for your comments. Claudio. In a standard system, four types of discounts are available. Note: The type of sale “R3” is identical to “CR,” with the exception of the corresponding type of billing ,B3` (partial compensation). In discount management, supplier agreements are recorded, purchases and sales are tracked on the basis of agreements, and discount limits and requests are managed. Discounts are not paid until after the validity period of the rebate contract has expired.

Thus, the system tracks all billing documents (bills, credits and invoices) that are relevant to the processing of discounts in SAP SD. The system automatically reserves demarcations. By creating limits, you`ll get an overview of the cumulative value of the discount. Payment method: Shows the standard method for paying the amount of the discount to the debiteur. For example, it could be a credit or a cheque, etc. I assume you are using the new delivery procedure (activated S136). When you go to the VBo2 or VBo3 verification stage, the system reads S136 and returns the documents relating to the condition number agreement (KNUMH) and the relevant validity data. Alternatively, I have considered removing the condition data and the value and limit of the billing document, but I do not have the OS option to get the AGREEMENT REBATE from the KONV table for a certain amount of packaging data. Our users used the verification level in the discount agreement to see which documents were collected.

Recently, many billing documents have disappeared from the rebate contract and we are unable to determine the cause. Can someone explain how documents are added and removed from the verification level? I have reviewed some specific documents that I know have discounts, and the analysis correctly indicates the discount condition and the rebate agreement. All thoughts would be very helpful. A discount agreement defines the details of the discount. In the agreement, z.B says: I`m a little confused. KNUMH is not able to give me an appropriate link between all the tables. I understand that KOTE001-004 is also related to the rebate. It doesn`t give me a precise result either.

Reduction of hierarchy: It allows packaging kits for a node/material of the customer hierarchy or only according to the hierarchy. Mike It was a masterpiece of information. Thank you so much for all these valuable comments. As you said, the discount funcitonality is not activated in my client. Finally, I would like to make a little clarification. I must receive the amount of partial or total compensation. I saw the values be in the koNPD structure. Any idea of getting the data (amount paid, balance, etc.).

I have a scenario to draw some details regarding the discount agreement. I have the level of verification in VBO3 for a partial discount contract. The values (discount base, delimitation, customer, sales organization) come from a “BOITEM” structure. Is there a way to extract data from it? Default status: indicates the default status of the discount agreement. In general, it will be “open.” Hello Everything Is there a Standarad report in SAP that shows all the invoices, limits, etc., that are part of the discount agreement? For all agg discounts. we go to the retail screen (VBo2) and check the SALES VOLUME and VERIFICATION LEVEL. Is there another standard fun causality with which I can draw all reports relating to certain data/bill/org/client or one of these reports? To view the updated discount limits in the discount agreement, select the conditionality rate managed in the agreement and select the “Payment Data” symbol.