OMT Specification Relationship Quantity Characteristics Behaviour

[vijaykumar_k]

We are using Quantity Characteristics in Specification Relationship to decompose from Parent CFS to number of child CFS instances. I have observed that when Quantity Characteristics value is provided as order enrichment on Service Order of Parent CFS then decomposition into number of child CFS instances based on the Quantity Characteristics  value does not work. Am i missing something or this is how ServiceNow works?

[ShashankInamdar]

Hello @vijaykumar_k 

Quantity mapping for Service Specs is a supported feature from the Utah release.

Please check a couple of things -

[1] Set the mandatory flag = true against the relationship between the parent CFS and the Child CFS.

Example -

[2] Set a decomposition rule against the Spec relationship, such that for the characteristic being used as quantity char - the decomposition happens only if some value is set to it.

Example -

Decomposition Rule -

Quantity Char -

Quantity mapping -

Hope this helps. Please mark this as an Answer/Helpful if it solves the problem.

Regards

Shashank

[ShashankInamdar · Accepted solution]

Hi @vijaykumar_k ,

As we discussed, in your specific case the change to quantity characteristics is to be done after the order has been submitted and approved.

ServiceNow OMT triggers the decomposition as soon as the Order is approved and generates the fulfilment domain orders based on the characteristics information available (from inventory) or char info that has changed as part of the Order.

In your use case, a Change Order is raised but the char is not changed as the requirement is to update/enrich the char as part of order fulfilment journey.

Since OMT already completes the decomposition by this time - even though the char value is enriched afterwards - the decomposition does not re-trigger, as the decomposition rules condition was already met at the time of order submission. (condition configured is - char has 'some' value, which it gets from the existing inventory)

A solution to your requirement will be to submit an Inflight Change with the updated char value against the 'Change' Order. With the Inflight change, OMT will reassess & re-trigger the decomposition.

And as a result, the change in quantity value will create the necessary child domain orders with the appropriate actions against them (Change/Add/Disconnect) depending upon increase/decrease of quantity.

Hope this helps. Please mark this as an Answer/Helpful if it solves the problem.

Regards

Shashank

[vijaykumar_k]

Thanks Shashank for the solution, this was helpful.