This brings the input data that the solver needs from the execution system.
The plan input data comes from the execution (source or transaction) systems to the planning server.
The data from collections can come from these source systems:
Oracle E-Business Suite execution products
Oracle JD Edwards EnterpriseOne execution products: Financials, Forecasting, Order Management, Procurement, Inventory, Manufacturing, Configurator
Third-party systems
| Questions | Answers |
|---|---|
| Do you use E-Business Suite as your source system? | Yes, use regular collections. No, use legacy collections. |
| Do you want an automated way that chooses the type and frequency of update or do you want to control these? | Automated, use continuous collections if your source system is E-Business Suite. You control, use standard collections, with modes:
|
See Oracle Value Chain Planning Collections Implementation Guide. It includes information about the entities that the collection process collects.
For more information about Oracle:
E-Business Suite execution products as a source of collected data, see MyOracleSupport note 746824.1: 12.x - Latest Patches and Installation Requirements for Value Chain Planning (aka APS Advanced Planning & Scheduling), Upgrade Matrix for VCP Products.
JD Edwards EnterpriseOne execution products as a source of collected data, see MyOracleSupport note 1125094.1: Value Chain Planning Integration Documentation Library, Oracle E-Business Suite to EnterpriseOne, Oracle Value Chain Planning Integration Base Pack 3.1 -- Implementation Guide.