Service Start Delay (Days) Attribute Doesn't Appear to Have Any Effect in Order Management
(Doc ID 2953883.1)
Last updated on JUNE 19, 2023
Applies to:
Oracle Fusion Product Hub Cloud Service - Version 11.13.23.04.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
After setting Service Start Delay in PIM > Manage Items, user is finding in OM that that is not having an effect.
EXPECTED BEHAVIOR
-----------------------
Service Start Delay in PIM > Manage Items should delay order by specified amount of days
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) In Fusion > PIM create new Ext Warranty Item
On Service tab, set:
Service Duration Type = Variable
Duration = 15
Duration Period = MTH
Service Start Type = Milestone
Service Start Delay (Days) = 30
2) In OM, create new sales order with Finished Good, and Ext Warranty Item (covering the Fin Good Item)
3) In INV, pick and ship order
4) Back in OM, after orchestration completion, the service start date of the Ext Warranty Item equals the ship-date of the Finished Good.
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 |