This article gives an overview of a typical Change Order in Order Management.
Feature: Change Order in OM
Application: Order Management
Release: All applicable
DYK (Did You Know) is a series of articles that introduces simple and basic concepts of the working of ServiceNow TMT Applications.
Once the ‘Provide’ (or Add) order is completed, the instantiated Catalog (i.e. Domain Orders) is stored in an ‘Active’ state as Inventory records.
Change orders such as to Change the characteristic of a Product that may or may not have a commercial impact can then be raised against an existing Product or Service.
But do you know how is the Change order processed by the Order Management Application?
A Change Order (be it for TMF622 Product Order or TMF641 Service Order) must always contain the Inventory Record Id against which the change is being raised.
Note: The Inventory Record Id can either be the ServiceNow Sys Id or an External Id.
The action mapped against the Order Line Item is ‘change’.
Once the order is submitted and approved, OM creates ‘Domain Orders’ (sub orders) corresponding to each Order Line Item.
The change action from the OLI is cascaded to the respective Domain Order.
OM then starts the decomposition process and validates the specification relationship configuration, and subject to it creates further decomposed Domain Orders.
The logic is described in the diagram below.
If you found this article useful, please mark is as Helpful 👍. Also, I look forward to your comments/questions.
