Service Order not closing after shipping when using Service Order Orchestration
(Doc ID 2191682.1)
Last updated on DECEMBER 09, 2023
Applies to:
Oracle Depot Repair - Version 12.2.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.3 version, Logistics Management
ACTUAL BEHAVIOR
---------------
Profile option CSD: Default Service Order Status After Final Shipping is set to Closed.
Service Orders transitions have been defined to be able to go from WIP COMPLETE to Closed.
Defined Service order Orchestrations Rules for Shipping.
However, after shipping, the Service Order status is not updating to Closed.
EXPECTED BEHAVIOR
-----------------------
The Service Order should go to Closed
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set profile option CSD: Default Service Order Status After Final Shipping to Closed
2. Service Orders transitions have been defined to be able to go from WIP COMPLETE to Closed
3. Define two Service Orchestration Rules:
Rule#1:
Event: Shipping: Delivery Line Status Change
New SO status: Closed
Condition:
Context: Post-Update Delivery Status of Ship Line
Operator: =
Criterion: Shipped
Rule#2:
Event: Order Management: Ship Line Status Change
New SO status: Closed
Condition:
Context: Post-Update Order Management Status of Ship Line
Operator: =
Criterion: Closed
4. Create the service order
5. Create the logistic Ship line
5. Perform the shipping
6. Execute the Service Order Orchestration concurrent program. The Service Order is still in WIP COMPLETE
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |