Your UX is waiting ...interact, engage, explore in Las Vegas at CloudWorld 2023

Learn more
Implementation Notes – Orchestration Process Definition and Order Processing — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Implementation Notes – Orchestration Process Definition and Order Processing

Received Response
79
Views
2
Comments
edited Jun 20, 2018 4:42PM in Order Management 2 comments

Summary

Orchestration process start date and order processing

Content

From Oracle Order Management Cloud product team:

Orchestration processes are defined with an effectivity period. We recommend that you define your orchestration process with a start date that is line with your specific business context to achieve appropriate process assignment of orders.

For customers who are getting on boarded on any release prior to 18C:

If you bring in orders from legacy systems with ordered date that is set prior to the orchestration process start date, it would result in orchestration process error. In these cases, you may need to adjust the ordered date to get them processed. If there are any requirements for tracking/legal purposes, these orders may need to be tracked from the legacy system until the cutover is complete.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!