on 2023 Jul 19 9:32 AM
Hello Experts,
Our customer is moving from R3 to S4Hana On-premise.
The new Condition Contract Management functionality is going to be used in the new system.
Condition contracts should be created in the new system. However, the R3 system already has billing documents that have to be considered for the business volume calculation in the new system.
We already know that condition type REBD (Rebate BusVol Delta) can be used to correct the business volume to be considered in the new system for the amount calculation of the subsequent settlement documents. However, we think that this particular condition type is only helpful if we work with a percentage scale.
Example 1:
Business Volume:
Conditions:
In this example, if we use condition type REBD = 300.000 EUR, the system will consider a business volume of 400.000 EUR (300.000 + 100.000) and the correct scale is going to be taken > 3% (that's OK).
However, this condition type is not really usefull if the amount calculation of the settlement document has to be done based on a quantity scale.
Example 2:
Business Volume:
Conditions:
In this example, the system calculates the settlement amount taking into account the quantity sold to the customer instead of the amount. The system is going to considered a settlement amount of 1 EUR / KG * 1000 KG = 1000 EUR, instead of considering a settlement amount of 3 EUR / KG * (1000 + 3000) KG ) = 12000 EUR.
¿Is there a way to adjust the business volume quantity? We need to consider the 3000 KG already sold to the customer in the previous system.
We have seen that it is possible to configure additional business volume tables in the "Define and Configure Profiles for Business Volume Determination" configuration step. Is it possible to copy the standard business volume table (for example, table VWB2_VBRKVBRP_1 for rebate contracts) and add to this table the billing documents items from the previous system after mapping the relevant fields between R3 and S4 (customer, material...)? If we go with this workaround, I guess it is not necessary to use particular conditions types to correct the business volume.
Thank you very much in advance for your time and help,
Best regards,
Jorge.
Hi jorgecardos,
When talking about the cutover for CCM, we can only be based on the data you can access.
1. If the condition records only used as % and no need to be realistic at material level, then you can use REBD in the condition contract to true up/down the business volume. This fixed amount will be split over the existing business volume and settlement conditions (%) will consider REBD in the calculation
2. If you are working with Qty condition records, that's another story. You will have to create the historical data into S/4
2.a First option will be to create a custom table + Adjust the CDS view of Business volume table + Profile of BV --> To consider the historical data
2.b Second option will be to create billing documents which are not posting (proforma) for the historical data + make sure to modify the CDS view and consider the relevant document types and proforma
2.c Third option and cleanest, create the historical data with a Proforma settlement document, Adjust CDS view, additional BV table and profile of business volume to consider the historical data.
2.c gives you the opportunity to review the historical data in a document and not in tables which users have barely access.
Regards,
Gauthier V.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you very much for your comments Victor!
We are going to try first with the creation of an additional business volume table that is going to be a copy of the VWB2_VBRKVBRP_1 table. This table will be included in the profile for the business volume determination and will contain the billing documents of the R3 system.
We will finally create an APP for the users to allow them to check the info of this new table.
Best regards,
Jorge.
User | Count |
---|---|
87 | |
8 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.