In this post, I will describe the relationships of Contract and ContractLine with Pricing model and Option/OptionChoices in BMC Cloud Lifecycle Management. By taking a closer look at how this functionality works, we can troubleshoot and resolve any Pricing and Chargeback related issues on our own.
See my previous blog The Pulse: Insights of Contract and ContractLine, to understand basic Contract/ContractLine concepts described in this blog.
The contract line holds the service offering price shown to the user when they request the service offering. The fields for price are: PriceAmount (the amount), PricePeriod (time period), and PriceUOM (the pricing unit of measure). This price represents the on-going price for the service offering. The quantity is always assumed to be one service offering instance.
A BMC_ContractLine configuration item is created for each option choice selected. It is related to the parent contract line for the service offering through a BMC_Component relationship with the name
OPTIONLINEPARTOFSOLINE as shown below.
The contract line for the option choice is related to the BMC_OptionChoice configuration item with a BMC_Component relationship with a name of OPTIONLINERECORDSOPTIONCHOICE.
The StartDate, EndDate and TerminationDate of this contract line have the same semantics as the Service Offering Line. The price fields for this contract line have the same meaning as they do for the service offering line (Refer to The Pulse: Insights of Contract and ContractLine).
All of the above captures the price of the service offering and the selected options. There might be another price component, which is the one-time price entered when defining the request definition. The request definition is persisted as a BMC_RequestableOffering configuration item. The value of the OfferingType field is either null or set to Service. It is related to the BMC_ServiceOffering configuration item by a BMC_Dependency relationship with a Name of SOENABLESRO.
The BMC_RequestableOffering configuration item is related to a BMC_Price configuration item by a BMC_Component relationship with a Name of OFFERINGPRICE.
Alternatively, you can use the ServiceRequestId field in the BMC_ContractLine for the service offering to query the service request and get the price. This method is better because it reflects the request definition price at the time the order was placed, whereas BMC_Price shows the current price.
If a service offering has post-deployment actions and the Add On radio button was set to Yes in the wizard, then a contract line is created when the user requests the post-deployment action.
The contract line has a ContractLineType of AddOnServiceLine. It is related to the contract line for the service offering with a BMC_Component relationship with the name of SOLINEISPARENTOFADDONLINE. The date fields and price fields in an add-on service line are the same as those in the service offering line.
I hope information is useful to understand the relationships of Contract and ContractLine with Pricing model and Option/OptionChoices in BMC Cloud Lifecycle Management.
The information will not only help you to understand the concept but will also help you to troubleshoot and resolve any Pricing and Chargeback related issue on your own.
KA390592 - Unable to edit price of Post Deploy Action.
KA373354 - How to create Chargeback Report in CLM?
KA365533 - Where does the CLM store the "Post Deploy Option" "pricing" information?
Visit my other blogs. You can share the links with others if you find these useful.
Please rate this blog, regarding the usefulness of the shared information, by clicking below option.
PS: At BMC we always strive to make our customers realize more value from our Products and be successful.
As you all know that we have introduced a new communication channel-“CHAT”. This gave our customers an additional option to contact us. For details, please refer Connect with BMC Support Team over Chat sessions.
You can also join the Customer Support Community to learn about and provide feedback on ways Customer Support can enable your success.