2021 Sep 01 1:07 PM
Hi,
there is an installation with two registers. Each register has its own register operand and its own register rate.
We want to determine the difference between the consumption of those two registers
The quantity in the register operands has the following two timeslices:
01.07.2020 – 31.12.2020
01.01.2021 – 30.06.2021.
The difference should be determined by regarding the timeslices:
consumption register1 01.07.2020 – 31.12.2020 minus consumption register2 01.07.2020 – 31.12.2020
consumption register1 01.01.2021 – 30.06.2021 minus consumption register2 01.01.2021 – 30.06.2021
Our problem is:
It is not possible to subtract two register operands directly from another.
Therefore we have to transfer the register operand to another quant operand with QUANTI14.
But after that the timeslices are lost. It only remains one timeslice for the whole billing period (01.07.2020 – 30.06.2021).
Please advise how to determine the comsumption difference regarding the timeslices.
Thanks.
Best regards
Gunnar
2021 Sep 02 8:02 AM
Hi Gunnar,
Quantities are not time dependent. Therefore, the billing program always merges quantity time slices as long as there is no reason not to do so.
You can try to force a proration at 31.12.2020 by changing the factor or a price which is later on used, for example. May be you need to use also a more "stronger" characteristic like a rate category change. This need to be tried out....
Or, you try to create your own variant programs and try to make them work per time slice and "suppress" the merge of the time slice.
Or, you can try to use the Serial Switching (where the system will automatically subtract the consumption of register 2 from the consumption of register 1). The following documentation in the SAP Help Portal contains a description how this is working: https://help.sap.com/viewer/2ac7fe29a0c94cdd88fb80c2cb9f7758/2020.002/en-US/7790d0533f8e4308e1000000...
Best regards,
Katrin
SAP Product Support
2021 Sep 02 8:02 AM
Hi Gunnar,
Quantities are not time dependent. Therefore, the billing program always merges quantity time slices as long as there is no reason not to do so.
You can try to force a proration at 31.12.2020 by changing the factor or a price which is later on used, for example. May be you need to use also a more "stronger" characteristic like a rate category change. This need to be tried out....
Or, you try to create your own variant programs and try to make them work per time slice and "suppress" the merge of the time slice.
Or, you can try to use the Serial Switching (where the system will automatically subtract the consumption of register 2 from the consumption of register 1). The following documentation in the SAP Help Portal contains a description how this is working: https://help.sap.com/viewer/2ac7fe29a0c94cdd88fb80c2cb9f7758/2020.002/en-US/7790d0533f8e4308e1000000...
Best regards,
Katrin
SAP Product Support
2021 Sep 02 11:06 AM
Hi Gunnar,
I will try to answer your question. But first of all when reading the whole text, I got question from my side. The most important question is why you want to have the proration coming with the register operands? And second question why you want to have this proration still when calculating the consumption? When there is just one price used to calculate the amount, we do not need two time slices. But if there is a price change, the proration should be shown in each line, means also in the one where you are using QUANTI02 I think, to calculate the difference.
If you have used just user exit EBIA0002 to get the proration at the line items with the register operands, you may change this and do the proration in the schema step when the price calculates the amount. Then the proration is also shown in each step before.
Hope this helps.
Best regards
Jörg
2021 Sep 08 2:07 PM