Creating Software Assets from a Procurement Purchase Order After Ordering but BEFORE Receiving

Noah Arwine
Tera Contributor

ServiceNow Procurement Purchase Orders gives some flexibility for Hardware Asset Management to create assets before they have actually received them. This can be done via a link that pops up on the Purchase Order or Purchase Order Line Item when you have created a PO, created a PO Line Item (For Hardware), and then clicked Order.

2023-04-04_15-38-18.png

 

Once the link is clicked, it will automatically create the assets just as it would when they are received. The result is that the assets are simply updated when the PO -> Received button is pressed instead of actually getting created right there.

My question is simple, why do Software Assets not have the exact same capability?


When a Software Line item is created, there is never a link. And therefore, it is impossible to build a software asset from the PO until the "Received" button is pressed. However this skips the whole process of the Asset being in Build status, which allow us the chance to add all relevant information that is not possible to add to the actual Line Item. For instance, you cannot choose the License Type from the Line Item. When received is pressed, they are automatically placed in Perpetual.

 

Is it possible to have this link be available for Software Assets as well?

4 REPLIES 4

dgros
Tera Contributor

Have you received any new information regarding this question? I am working on the same problem in Vancouver.

mikew_samexpert
Mega Guru

My immediate thought is why would you want to create software entitlement records prior to "receipt". What is the value of doing this?

This inquiry is regarding the entitlement being received in a Build state as opposed to Publishing in receiving. The issue this causes is that we now must manually go to the entitlement, publish, then allocate the entitlement which leaves us without a link to the procured entitlement from the request. Likewise, if we choose to allocate instead of purchase, only partial details are translated to the entitlement record and we still must manually go to the record and fully document the key and allocation details. 

Ryan S
Kilo Sage

Any chance you found a solution to this?