Wait Condition Not Resolved Between Line Items Of Different Promotion
(Doc ID 2723074.1)
Last updated on JANUARY 27, 2021
Applies to:Oracle Communications Order and Service Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.0]
Information in this document applies to any platform.
There is an order defined with 2 promotions P1 and P2. There are 3 line items of which 2 are siblings .i.e. belong to the same promotion. The 2 line items P1L1 and P1L2 are part of different functions(Function-1 and Function-2 respectively) and fulfillment Patterns FP1 and FP2 respectively. The third line item belongs to promotion P2 and is part of function Function-2 but belongs to a third fulfillment pattern FP-3.
In fulfillment pattern, FP2 customer has defined dependency defined from FP1.Function-1 to Function-2 and have a wait condition (data change notification) defined based on milestone(Milestone-1) for line item P1L1 in Function-1.
The same dependency and wait condition have been defined in FP3. But the wait condition has a different milestone(Milestone-2) check.
Milestone-1 reaches earlier than Milestone-2.
As soon as Milestone-1 is reached, the dependency between Function-1 and Function-2 is resolved as expected, and Function-2 triggers. At the same time, Function-3 also triggers, which is not expected.
How to resolve this.
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