Overriding OOB Domain Order Validations (PO Cancelation) in TSM

Kailash Bhange · ‎12-01-2022

After you capture a customer order, the order fulfilment manager selects and verifies the order, line item, product specification, and characteristics data, and then decides whether to approve or reject the order. If it's approved, the order decomposition process initiates and triggers the order fulfilment flow to fulfil the customer order.

When a customer order is approved, order decomposition occurs. In this process, the Now Platform generates the product orders and associated service and resource orders for each customer order line Item. The generation of these orders is based on the Specifications, Specification relationships and Decomposition rules for the related product, service, and resource specifications.

To learn more about this process, see the following:

Each generated product order contains service and resource orders that are created when a customer order is approved and then decomposed. So here comes the OOB validations attached to the Domain order of your customer order.

When these validations fail or are not satisfied by your customer order, fallouts are created with different error messages. Below are some of the common errors in the fallout tasks.

Order Auto Closure Failure.
Product Characteristics missing.
The following order characteristics do not contain proper values.
The following child orders have not been closed.
The following order line item\'s characteristics are incorrect or missing :
One or more related items are required. Provide the related inventory details prior to closure of the related domain orders.
One or more related inventory/domain orders are not compatible. Provide the correct dependent inventory details prior to closure of the related domain orders.

So here we will discuss about above red highlighted error message.

The most common reason for getting this error message is that the child’s of the domain order are open, and the system or agent is trying to close the domain order. (This means the domain order has some open dependency)

This works fine in case of closing the complete order but when we try to cancel the domain order, system again checks if the child order tasks are closed or not (irrespective of whether the tasks are closed or cancelled). So, the use case is when the child order tasks are cancelled, system should allow us to cancel the domain order, but it gives the error as below and applies the validation that child tasks should be closed complete.

Use Case: -

System should allow us to cancel the domain order (PO) when its child’s (PO, SO) are cancelled.

OOB it does not allow the agents to cancel the PO and gives the fallout with below error:

The following child orders have not been closed

Analysis & Solution: -

To address this issue, you need to override the OOB code (required script include, methods).

Below are the OOB entities, responsible for the fallout to occur.

Script includes: -

DomainOrder

Method: -

_retrieveOpenChildDomainOrders

To know more or learn more about extending /overriding OOB code please check below: -

If you need any help, please reach out to me!

Hope this helps.
If my answer resolves your issue, please mark my answer as ✅ Correct & Helpful based on the validations.

Thank You!

Regards,
Kailash Bhange

RISING 🌟 2022
LinkedIn

Tom Schnarr · ‎12-06-2022

Great comments Kailash. - I stand by the default validations within the product - one should not close a parent domain order while the child domain orders are still in progress, however, i can understand that there may be times when it is appropriate - that when we close the parent object (say the product domain order) all the child (product/service/resource) domain orders should also be closed and your suggestion is valid. Do we also need to force close any open tasks?