Should the price of a Catalog Item be obtained from alm_license and displayed?

[nagaryu]

For example, assuming a scenario in which "Microsoft 365 is requested in a Catalog Item and a license is granted to the applicant," what is the best practice for holding the amount?

Catalog Item has a Price field OOTB, so should the currency and amount be set here, or would it be better to add a Reference type field that links to the alm_license table and display the currency and amount set in the Unit cost field of the alm_license table there?

If it is preferable to obtain the amount from the alm_license table, can the currency and amount be obtained from a Reference type field? Or do I need to use some kind of script to handle this?

I need to output monthly assessment information such as "how much each department spent this month" in a report or view, and I am wondering how I should hold onto the original amounts, which is my question.

------------------------------------------

P.S.

Sorry, after that, I investigated a little more myself and found an item called Publish to Software Catalog in Related Links at the bottom of the record in the cmdb_software_product_model table.

When I clicked on this, the Catalog Item was published to the pc_software_cat_item table.

I'm not sure whether the Cost specified in cmdb_software_product_model is reflected in the Catalog Item's Price, but it seemed that the amount specified in the Catalog Item's Price field was displayed in the Catalog Item.

Is it best practice to use Publish to Software Catalog in Related Links as shown above?

[dreinhardt · Accepted solution]

Hi @nagaryu,

I think using the entitlement price as a reference for the catalog item is a good idea, but in most cases it doesn't reflect reality, does it? In my experience, the ITAM team rarely passes on the prices 1:1 to the end customer; instead, there are additional costs that may have to be cross-financed per monthly additional service fees. (e.g., service fees, IT costs, infrastructure, etc.). Catalog item offers additional fields to include service fees if needed

The action "Publish to Software Catalog" will use the Software model - Tab General - Cost field to add the price and costs once to the catalog item. Changes to the cost field will apply only to the catalog item "Cost field" and not to the "Price field" which is ootb shown during catalog item check-out. Please keep this in mind.

Best, Dennis

[dreinhardt · Accepted solution]

Hi @nagaryu,

I think using the entitlement price as a reference for the catalog item is a good idea, but in most cases it doesn't reflect reality, does it? In my experience, the ITAM team rarely passes on the prices 1:1 to the end customer; instead, there are additional costs that may have to be cross-financed per monthly additional service fees. (e.g., service fees, IT costs, infrastructure, etc.). Catalog item offers additional fields to include service fees if needed

The action "Publish to Software Catalog" will use the Software model - Tab General - Cost field to add the price and costs once to the catalog item. Changes to the cost field will apply only to the catalog item "Cost field" and not to the "Price field" which is ootb shown during catalog item check-out. Please keep this in mind.

Best, Dennis

[nagaryu]

Hi @dreinhardt ,

Thank you for your reply.

I don't fully understand the work yet, and I didn't know the difference between cost and price, but I understand that,
- cost is the amount spent, for example, when purchasing a product from Microsoft, and
- price is the in-house price charged to the end user (or the department to which they belong) when using the Catalog Item.

If that's the case, the amount I wanted to know this time was the "price," so I understand that the monthly report should tally up the "Price" column of the pc_software_cat_item record that was automatically created when I pressed the Publish to Software Catalog button.