Defining the costing procedure In the SAP standard unit, the BO01 to BO06 discount constitution types are assigned to the costing procedure If you configure your own discount conditions, make sure that you have added the request routine 24. This ensures that the conditions are only retrieved in the billing documents. Also note that the conditions must be assigned to the ERB and ERU account keys. We will discuss aspects of account assignment later in this chapter. The new discount processing procedure was enabled when the S136 default statistics structure update was enabled. Arrangement schedule An arrangement schedule defines the end of the validity period of a remission agreement and also helps to extend the remission agreement to the next period. SAP provides the RV15C005 report to extend the discount agreements to subsequent periods. You can access it using the transaction code VB(D). On the Billing Documents tab page of the client master files, a check box is used to enable discounts. sales. Make sure this option is selected for your customers in the payer role. After using Tcode VBOF to update the billing document, I use Tcode VBO2 -> discount payment -> select the verification level. The screen appears as the image “rebate01”.
We will discuss the allocation of the account. In this phase, however, we will see how to manage accounts for discount processing using the IMG menu path ➢ Sales ➢ Billing ➢ Discount processing ➢ Determining the account for discounts ➢ Assigning G/L accounts (VKOA). We have assigned G/L accounts for the ERB and ERU transaction keys, as already mentioned. reflects the effects of accrual accounting and settlement transactions on the recognition of the general account. Agreement Type 0002 (Hardware Delivery) This type of agreement allows state records for a customer/material and uses a quantity-dependent calculation. The customer is the payer. Have you kept the type of condition in the costing process? To test at the sales order level, you can remove requirement 24 for now so that you can see the discount provisions in the sales order. Now we`ll discuss the most important steps in setting up discounts. The quantities sold are not up to date for the 100 agreement In SAP, the remittance process consists of three main processing steps.
You start the process by creating a remittance agreement, followed by automatic or manual accounting for provisions, and you complete the process by executing remittance statements. Here is a detailed explanation of these steps in the process. The next screen is the presentation screen of the reduction agreement. Here you provide all the information about a discount contract. A discount recipient is a customer who must receive the discount and whose sales must be tracked for the processing of the discount. The validity period represents the validity of the discount and the verification level represents the level at which you would review a sales volume report for this discount agreement. A discount is a sales promotion technique that a salesperson uses to improve sales volume. This is usually a time-limited after-sales discount based on a sales volume to a specific customer and has a prospective or retroactive effect. For example, a customer may be eligible for a 2% discount as a discount for total purchases over $100,000 over the next six months.
Another example may be a $1 discount on each part eligible for the discount if a customer purchases 5,000 pieces of a particular product over a four-month period, including one month in the past and three months in the future. Discounts can also be independent of sales volume. An example is performance discounts. Default statusHere you configure a default state when you create the agreement. The default value here is empty, which means that the agreement is in the Open state. I just upgraded our SAP system from 3.1I to ECC6. With the remission agreement, I am faced with the following problem. So far, we have made the retroactive adjustment of the discount via VOB3. After the upgrade, the system asked us to run VBOF to update the sales value to see the value in VOB2. Running VBOF also updates the retroactive discount, which has already been adjusted via VOB3 in version 3.1.
The previous restrictions result from the following reasons: The processing of discounts allows the creation or subsequent modification of agreements. It is expected that these changes will also affect, for example, the amount of the discount to be paid retroactively. These changes to condition records do not automatically modify existing documents. For this reason, only a limited interpretation of the relevant documents is available for the processing of remittances. For performance reasons, full pricing functionality is not allowed. New procedure 1. Technical background Starting with version 4.5A, the new procedure for processing discounts is available. The difference between this procedure and the previous procedure is that in the new procedure, all relevant billing documents are updated with changes relevant for delivery.
In this procedure, the options for the pricing functions (e.B. condition exclusion) are also available. . . .