DM: How does EBS Collections determines which OM SO lines to collect for Bookings History — 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

DM: How does EBS Collections determines which OM SO lines to collect for Bookings History

edited Dec 6, 2024 3:05PM in Supply Chain Planning and Collaboration 6 comments

Summary:

DM: How does EBS Collections determines which OM SO lines to collect for Oracle SCP Plan Inputs collected Bookings History?

Content (please ensure you mask any confidential information):

Customer wants to validate the collected SCP Plan Inputs Bookings History showing in a Demand Plan versus EBS OM SO Line data.

DM: How does EBS Collections determines which OM SO lines to collect to input into Oracle Fusion SCP > Plan Inputs > Measure= Bookings History: Booked Item by Requested Date? Is it based on the

  • Line Status
  • Line Type
  • Item Type
  • Unit Selling Price
  • Extended Price
  • Fulfillment Set
  • Ship Set
  • Visible Demand = Y

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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