The important limitations of the above remittance process in ECC are other questions, do you know how advanced invoicing of discounts for indirect sales will work in S4H? The parameters for determining the business volume are also very well configurable in S/4HANA (i.e. non-fixed). The following figure shows the default business volume determination configurations for the 0S01 sales discount, which takes into account the BONBA (discount basis 1) and NETWR (net value of billing item) fields. If the gross value of the billing line is more appropriate for a particular business scenario, this can be achieved with the default configuration. I use 0S12- Sales Discount Credit as the type of billing document and 0S10 as the type of billing process. The process I want to do is to reimburse customers. I have maintained the KUNNR field for determining the volume of business and it is set to Condition Contract. The process diagram for sales delivery in SAP ECC is shown in the following figure. After the creation of the remittance contract and the billing document(s), the VBOF transaction (or the SDBONT06 program) must be executed in order to update the corresponding sales volume in the discount contract. Remittance is usually processed at regular intervals or at the end of the year. A VBOX index table is used to link discount invoices to reduce processing time. Finally, the discount contract is released for billing and subsequent billing creates a direct debit request and a debit note to the customer. In a remittance process, the seller tracks the sales volume of end customers, so some incentive can be offered if certain conditions have been met on a predefined agreement.

This retroactive payment allows us to promote loyalty over a period of time and continue to trade with our partners. In the previous ECC, the processing of rebates was limited to many factors: business volume is the stumbling block on which rebate calculations depend. Volume can be determined by value, quantity, weight and other combinations. The decisive factor here is that the system determines the volume of business separately. The business volume is calculated based on standard system tables, and you can even see how the business volume is calculated. With ERP Business Suite, the VBOX table was the main link between the SD business volume and your discount agreement. With the power of S/4 HANA and its architecture, this table has been removed. Customer contract for 1 year {January to Dec], targets $10,000 in sales, 10% discount on sales when reaching the goal. The requirement is to calculate 10% and not display the provisions [no settlement] on a monthly basis to know the liabilities.

At the end of the year, the customer`s final settlement must be made if the target is met or if all provisions posted from January to November must be cancelled. Does anyone have a setup guide? My discount condition is not retrieved in my sales order, but it allows me to add it manually. Would anyone know what the reason is? There was also a lack of flexibility in establishing commercial criteria for rebates. You had to use separate configuration and transaction codes for the vendor and the customer. The speed achieved with in-memory calculations also eliminates the previously recommended approach of closing and rebuilding delivery agreements each year so that reports can be retrieved without system expiration time. Another great advantage of the conditional contract discount solution is that it can also be applied to supplier discounts (and many other scenarios such as bonuses, commissions, etc.). The process and system solution for Orders to Cash and Procure to Pay discounts are the same as shown in the following figure. I also wanted to know if I wanted to add a combination of fields for business volume.

For example, I just wanted to offer discounts on the number of the sales document. How do I add it to Field Combination for Business Volume? Can you please share how retroactive discounts will work in S4H. Can you explain the process in detail? A discount is a special discount that is paid retroactively to a customer. This discount is based on the customer`s sales volume over a certain period of time. You define the discount details in a discount contract. In the agreement you specify, e.B. If the sales document was created before the contract was created, the discount is provided as part of the invoicing process and the discount condition will be visible in the credit note that displays the correct accumulation amount on the respective accounts. It is therefore no longer necessary to resume the sales order.

Hi Zahid, Retroactive discount should work in the same way as ECC, but without VBOF app. For example, on February 1, 2018, a conditional contract will be created with validity dates from January 1 to December 31, 2018. When the next payment is made, it retrieves all the billing documents that are within the validity period. I hope this helps. Certain settings must be applied to the components of your business (business organization, billing document type, and payer) for discount to be enabled in your contract. This is a prerequisite for starting your business venture with your partners and managing your discount processing in SAP SD ECC. Certain parameters must be configured in your agreement as a criterion to determine the volume of business. After this configuration, the way the system calculates the final discount starts with the sales order throughout the SD flow, but only in the invoice can the system calculate the corresponding discount by updating the VBOX table. In the SAP world, we have the tools to manage this partnership relationship and offer retroactive discounts through discount agreements. The overall CCM process differs from standard remittance processing in that there are no remittance agreements in the first step.

There are conditional contracts that must be created and released. The steps to do this are explained in step 8. The invoicing schedule put in place gives you the traceability of your provisions and this information is immediately reflected in the variety of reports that CCS offers you. Retroactive remittance is implicitly included in the business process and will no longer be a tedious task. And another important improvement is that the discount can now be calculated based on different or multiple sources. Condition of validity of the contract: from 1 July 2017 to 31 December 2017 For invoices issued from 1 July to the end of 2017, provisions for discounts are automatically recognised. When setting up discounts in conventional ERP systems, it should be noted that the discount is retroactive and provisions had to be created. The subsequent processing of remittances required the system to keep track of all relevant documents – invoices, cancellations, credits and direct debits, etc. For example, the ERP system stored all relevant invoices in the Discount Index Table (VBOX). One of the most important areas of innovation was discounts or chargebacks. In the past, SAP provided discount processing in the Sales Billing module and MM Purchases for vendor chargebacks. However, these had several limitations both from the point of view of modelable business processes and for reasons that occurred due to a slower data model in terms of reporting (verification levels), provision calculations, retroactive application of a counterparty, etc.