Hi Ankit, that is an interesting use case. However, it is not fully clear what you want to achieve. If the target is to pick a price condition dependant on the year of a contract, then this is a valid approach. However, there are two observations:Fir...
Hi Prasannakrishna,The rate plan template outlines the basic structure of a rate plan, including relevant charges, billing options, and the billing cycle. To provide more flexibility and encourage reuse, you can define a rate plan template with param...
Hmm, probably you need to re-asses your table definition and adapt it accordingly.If you are new to the topic, did you try to use the pricing scheme Initial provided by the predefined content?
Hi Lukas,for the definition of the lookup table it is not required to include the quantity. This is reflected in the price condition itself already, specifically the 'Range Value' and 'Range UoM or Currency' column. You maintain these columns for pri...
Hi Lukas,so you have a field 'quantity' configured in your lookup table, which is used as a quantity range.That's why you get this error in the import as I've described in my first reply.The question is what do you want to achieve with this column - ...