Proration of flat rate

[diptarkaroy]

Hello,

I'm facing the below situation:

We have a flat price maintained in the system with time category as Month ($12/month). Price operand is maintained in the Rate cat level.

A factor operand is maintained in the Installation level and LUMSUM01 is used in the rate with period control 02. 

Let's say, there is a billing period with dates 01/01/2024 to 31/01/2024. Factor value is 0 from 01/01/2024 to 10/01/2024 and factor value is 1 from 11/01/2024 to 31/01/2024. 

In this scenario, system is completely ignoring the price and customer is not charged for 20 days ($8). However, if the contract is moved in on 11/01/2024 and first bill period is valid from 11/01/2024 to 31/01/2024, then proration is happening and customer is getting charged for $8. 

Could you please suggest what change needs to be done if we want to charge the customer for $8 (proration to happen) for the 1st sceanrio?

[katrin_frenzel · Accepted solution]

Hello @diptarkaroy,

I have just tested it out in an internal test system and it works w/o problems.
Schema setup:

All operands are defined with operand access "All operand values".
Factor is prorated in installation facts:

Price is defined as month based and not prorated.
Outcome in billing document:

This is exactly the expected result.

Best regards, Katrin

[diptarkaroy · Accepted solution]

Hello @katrin_frenzel ,

I'm not sure what wrong I have done. 

My schema setup:

My operand setup (factor is maintained as 1 from 03/16/2024): 

Operand access control (All operand values selected):

Bill period (03/07 to 04/05) : Charge not appearing at all (wrong - it should have been prorated from 03/16 to 04/05)

Bill period (04/06 to 04/05) : Charge is appearing for the full period (correct)

Price key setup:

I'm not able to understand where I'm going wrong 

[diptarkaroy]

Following

[diptarkaroy]

Hello @katrin_frenzel ,

I'm not sure what wrong I have done. 

My schema setup:

My operand setup (factor is maintained as 1 from 03/16/2024): 

Operand access control (All operand values selected):

Bill period (03/07 to 04/05) : Charge not appearing at all (wrong - it should have been prorated from 03/16 to 04/05)

Bill period (04/06 to 04/05) : Charge is appearing for the full period (correct)

Price key setup:

I'm not able to understand where I'm going wrong 

[katrin_frenzel]

You need to maintain also the time slice with factor 0.

[katrin_frenzel]

The variant will be only executed when values are available for complete billing period.

[diptarkaroy]

Hello @katrin_frenzel 

I have added the 0 factor value from 03/01 top 03/15 where the bill period start date is 03/07.

This is working now. Thanks a lot for your help. 

Marking your solution as working. 😃

[katrin_frenzel]

Hello @diptarkaroy

If the operand access is all operand values it should work and system should calculate 2 time slices (in that case it would not be month based but day based with basis 365 days).
Is the factor operand somewhere in the former steps used as an output operand?
It could be due to schema dependencies that this will lead to a 0 factor.
Please try it out for a simple example where only a LUMSUM01 is used to see if it is working in general.
If so, it is an issue of schema setup when it is not working in a more complex schema.

Best regards, Katrin

[diptarkaroy]

Hello @katrin_frenzel ,

I have checked the Schema as you advised. This factor operand is used only once in the entire Schema to calculate the amount using LUMSUM01. 

Factor operand - M_ADT_CW

Price operand - L_ADT_CW (flat rate)

When you are saying it could a Schema setup issue, what exactly should I check? Sorry, but I'm not getting that. 

[katrin_frenzel]

Hello,

This sounds like an issue of Operand access control which is maintained in the operand itself.
Which value(s) is / are taken depends on the setting, if for example all operand values should be considered or operand value at start of billing period.
Please check the operand access in the factor operand. You will also find a comprehensive F1-documentation for the Access control.

Best regards,
Katrin 
SAP Support

[diptarkaroy]

Hello @katrin_frenzel ,

Thanks for providing quick response. 

Actually I also thought about this initially and checked the same in operand access. This is already set at "All operand values" so it whould consider the entire period from 01.01 to 31.01.

I just changed that to "End of bill period", and as expected the it starts considering the operand value on 31.01, and the customer is getting charged for the entire bill period (entire month - $12). 

However, my requirement was to charge the customer only for 20 days (from 11.01 to 31.01 - around $8). I thought "All operand values" would fix that, but sadly, it is not working. 

Thanks anyway!!!