Showing results for 
Search instead for 
Did you mean: 

Proration of flat rate

0 Kudos


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?

View Entire Topic
Product and Topic Expert
Product and Topic Expert
0 Kudos

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

0 Kudos

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.