This is the point when a software asset manager can reasonably go ahead and start to model an entitlement or whatever else is appropriate for the purchase.

I suggest the best point in time to bring purchase information into FlexNet is generally when the PO has been approved.

Information identifying the type of purchase (software license, maintenance, subscription, etc).

Information about who the purchaser is so that they can be contacted for further information.

Accurate start and end date information for subscriptions, maintenance and the like.

A SKU (if the software publisher uses SKUs).A clear and precise description identify exactly what has been purchased.As commented, fundamental properties that a software asset manager will be looking for to understand what has been purchased include:.As such, having clear policies, practices, education and governance processes in place can help control the quality of data that is entered on POs. People entering PO information will often fail to appreciate many of the complexities that SAM practitioners have to deal with, or what sort of data they need. Often entry of procurement data about software into Ariba (or whatever procurement system is in place) is done by many people who are widely spread throughout a large organisation.These are good questions touching on the flow of procurement data through an organisation.

Ariba integration with sap pi