Thanks a lot for your replies!
There is one point I dont understand. I thought synthetic profiles were the recommended solution for my scenario. Let me explain it in detail:
We want to bill all our customers using profiles and RTP interfaces.
The RTP interface to be applied is a simple LIMIT02 that uses hourly consumptions and hourly prices to get the amounts to be billed.
The problem we have is that for some customers, we dont have hourly consumptions as they have assigned old meter devices. We only have the total consumption for the billing period.
How can we convert this periodic reading into a profiled reading? It sounds as a very common requirement (you dont read a customer using profiles, but still you want to bill using profiles).
As we know which is the common curve for that kind of customers, we had created a synthetic profiles with this curve.
The idea was to convert the registered consumption into a profile consumption using this synthetic profile (the example I wrote in my previous comment).
In order to make this, I had assigned at RTP interface the synthetic profile as consumption profile, and also the same synthetic profile at load profile allocation tab.
After the tests done and your comments above, it seems my understanding of the synthetic profiles is not correct (I have read your amazing blog but still has not found any clue to solve this scenario).
Could you please let me know your opinion regarding which you think is the best way to manage this requirement?
Thanks a lot!