Can the Depot Repair Service Order Orchestration rules work retrospectively
(Doc ID 2517911.1)
Last updated on MAY 05, 2021
Applies to:
Oracle Depot Repair - Version 12.2.5 and laterInformation in this document applies to any platform.
Goal
Setup Orchestration rules to close the Service Order upon Job Status changing to Complete
Setup the following conditions
Service Request Account = XYZ
Service Type = Repair and Repair
Post Update Job Status= Complete
Scheduled the program 'Depot Repair Service Order Orchestration'
The rules get applied to those Service Orders where Jobs are completed post rule setup and program scheduling
However those Service Orders where the Jobs got complete before the rule setup and program scheduling still do not get closed which means the rules do not apply if the job got completed before the rule setup. Need to apply this retrospectively.
EXPECTED BEHAVIOR
Expect that the 'Depot Repair Service Order Orchestration' works correctly for the Service Orders where the Jobs got complete before the rule setup
STEPS
1. Login to Oracle Apps
2. R) Depot Repair Super User -> Setup -> Service Order Orchestration Rules.
3. Create a rule for the Job..as mentioned above
4. Run the concurrent program 'Depot Repair Service Order Orchestration' and provide the repair number that has a repair job which is in the 'complete' status...
5. Find that the status is not getting updated in Service Order...However, for the service orders created post the creation of this orchestration rule, it works fine...
Solution
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
Goal |
Solution |
References |