Collection Methods
Collecting data can take a significant amount of time compared to the time for the overall
planning cycle. Oracle Advanced Supply Chain Planning (ASCP) provides a collection method
that allows the collections duration to be reduced in cases where information about some - but
not all - planning-related business entities on the planning server needs to be updated.
There are three collection methods:
The Complete Refresh method clears all transaction data for all business
entities from the planning server (for the source instance being collected),
then copies over information about the user-selected entities. This method
can be time consuming.
The Targeted Refresh method clears transaction data for only the user-
selected business entities from the planning server, and then copies the entity
information over from the transaction instance. Information about unselected
entities remains intact on the planning server. All planning business entities
are supported by Targeted Refresh collections. When running targeted refresh
for entity Trading partners, also collect entity Calendars. This ensures that the
Oracle Project Manufacturing organizations are set up as organization type
process so that the release process from Oracle Advanced Supply Chain
Planning to Oracle Project Manufacturing succeeds.
The Net Change Refresh method copies only incremental changes to business
entities to the planning server (and is thus faster), but is supported mainly for
demand and supply business entities only.
Running Standard Collections
To collect data from an Oracle Applications transaction
instance
1. Sign on using the Advanced Supply Chain Planner responsibility or the
Advanced Planning Administrator responsibility.
2. Navigate to the Planning Data Collection window by selecting Collections >
Oracle Systems > Standard Collection.
The Planning Data Collection window appears.
This window shows you that the collections process consists of two
sequentially executed concurrent programs. The first program, Planning Data
Pull, copies information from the source instance into the APS staging tables
on the planning server. Here, against the data held in the staging tables, ASCP
performs some basic cleansing. For example, it ensures that items with the
same names that are collected from different source instances will be
assigned the same internal IDs (recognized as the same item). Further
cleansing operations on the staging tables (if desired) may be done at this
point via any custom concurrent program. This custom concurrent program
would need to be inserted into the Planning Data Collection request set, in
between Planning Data Pull and Planning ODS Load. The second program,
Planning ODS Load, copies information from the APS staging tables into the
operation data store on the planning server, where it becomes available for
use during planning.
3. Select the Parameters field for the Planning Data Pull program.
The Planning Data Pull Parameters window appears.
4. Use the information in the following table to set up parameters in the Planning
Data Pull Parameters window.
Parameter
Instance Source instance code from list of values.
Number of Workers One or greater. Increase this number to increase the amount of computational reso
now be different from the number of workers specified for the ODS load process.
Timeout (Minutes) The maximum amount of time you would like to allocate to the Planning Data Pull p
Purge Previously Yes (default) or No. Setting this to Yes wipes out all data in the APS planning server
Collected Data the only allowable collection method is Complete Refresh. If you set this to No, the
Collection Method Complete Refresh/Targeted Refresh/Net Change Refresh.
Analyze Staging Tables Yes or No (default). Set this to Yes periodically to recompute database access statis
User Company The possible values are:
Association
o No: During data collections, the destination instance does
association.
o Create users and enable user company association: A user
instance. You can use this option when you need to work w
Create a new user, specify the user's contact information d
and is assigned the Supply Chain Collaboration Planner res
associated company.
o Create a new user, specify the user's contact information d
and is assigned the Supply Chain Collaboration Planner res
associated company.
Create a new user on the source instance and specify the u
and assign the user responsibilities. Start a data collection
5. The remaining parameters in the Planning Data Pull Parameters are a list of
business entities. Selecting Yes for an entity means collect the information for
that entity over from the source instance. Selecting No for an entity means
don't collect the information for that entity over from the source instance.
6. Note: The default value for these entities is set to Yes. Collecting information
for Resource Availability and Sourcing History takes a significant amount of
time. Collect this information only when necessary.
7. Select OK.
8. Select the Parameters field for the Planning ODS Load program.
The Parameters window appears.
9. Use the information in the following table to specify the fields and options in
this window.
Parameter
Instance Source instance code from list of values.
Timeout (Minutes) Number of minutes before the concurrent program will end.
Number of Workers One or greater. Increase this number to increase the amount of computational res
Recalculate Resource This defaults to the value (Yes or No) that you set for the Resources Availability bu
Availability resources availability is collected or not.
Recalculate Sourcing This defaults to the value (Yes or No) that you set for the Sourcing History business
History sourcing history is collected or not. If you select Yes, then ASCP will collect all new
transaction system. The number x is given by the value that you set for the profile
the planning server in addition to the planned sourcing in the plan to determine w
Purge Sourcing History Valid values are Yes and No (default). If you select Yes, then all sourcing history pre
10. Select OK.
11. Select Submit in the Planning Data Collection window to run collections
immediately, or select Schedule to schedule collections for some later time.
If you select Schedule, the Schedule window appears.
Note: If you want to perform an incremental refresh frequently, use this
feature.
You have complete control over the timing and frequency of the collection of
data from the transaction systems, and the timing and frequency of planning.
You can manage the balance between network traffic and the need to monitor
current status in your plans.
12. Select a frequency for running the job in the left pane. Complete any
additional fields that appear based on your selection.
13. Click OK.
14. Choose Submit in the Planning Data Collection window.
15. From the toolbar, choose View > Requests to view the status of the collection
process.
The Find Requests window appears.
16. Select a type of requests to view then select Find.
The Requests Window displays data collection progress.
17. After the collection process completes, view your results.
If concurrent process Refresh Snapshot ends in a warning and you have
configure-to-order items, there may be a setup issue with those items.
Concurrent process Refresh Snapshot calls the configure-to-order applications
programming interface to explode the configured bills of material and create
demand in the proper manufacturing organizations. Check the log file of the
configure-to-order applications programming interface for details of the setup
issues and take corrective action.
If your collections process runs on an Oracle 8i database and the collections
process fails, attend to the following troubleshooting information:
o If it fails with an Autonomous Transaction within Distributed
Databases error either at any point in the Data Pull /Pull Workers
run or when launching Refresh Snapshots, set profile option
FND:Log Enabled to No.
o If it fails in Planning Data Pull Worker when collecting sales orders
or hard reservations, either set profile option OM:Debug Level to
null value or set it to a value lower than 5
18. From the Navigator window, choose Collection > Workbench.
Notice that data is brought over from selected instances.
Note: Users can collect forecasts into the planning server. If you want the
collections program to collect a forecast set, select the Advanced Planning
Collections checkbox while defining the forecast set.
Data Changes That Can Be Collected in
Net Change Mode
When the net change mode for collections is selected (by setting the collections parameter
Complete Refresh to No), the data changes shown in the following table can be collected. If you
set the collections parameter Complete Refresh to yes, the collections program collects the
entire data for the entity.
All other data changes must be collected by running full collections (by setting the collections
parameter Complete Refresh to Yes). Net change collections run more quickly than full
collections.
You can run data collections in net change mode for these transactions:
Data Element
Sales orders Cancellations of or modifications to sales orders and sales order reservations ar
including collection parameter Pull Sales Orders.
Reservations against Reservations against both external and internal sales order demands are captur
demands
Master production schedule MPS demands that are added, modified or relieved in the source instance are c
demands
Master demand schedule Set the Planning Data Pull parameter Master Demand Schedules to Yes.
WIP component demands Demand changes due to cancellation of WIP jobs, changes in the state of WIP j
changes in item information are captured. Set the Planning Data Pull parameter
WIP repetitive item demands Demand changes due to cancellation of WIP repetitive schedules, changes in th
are captured. Set the Planning Data Pull parameter Work in Process to Yes.
Forecast demands Changes and deletions in forecasts are captured. Set the Planning Data Pull pa
User demands Changes to user demands because of changes to item information are captured
Master production schedule Changes in supply schedules or item information are captured. Set the Planning
supplies
User supplies Changes to user supplies because of changes to item information are captured.
Purchase order supplies Changes to PO supplies because of rejections, returns, or cancellations or chan
Yes.
On-hand supplies Set the Planning Data Pull parameter On Hand to Yes.
Work orders in Oracle Work in Changes in WIP Jobs are captured. Set the Planning Data Pull parameter Work
Process
Resource availability You can use net change mode in discrete manufacturing organizations. Set the
If you are a process manufacturing organization, use complete refresh.
Supplier capacity Set the Planning Data Pull parameter Approved Supplier Lists to Yes.
Bills of material All BOM changes are captured: new components, disabled components, compo
Bills of Materials / Routings / Resources to Yes.
Routing operations Changes to and deletions of routing operations as a result of changes to operati
dates), the disabling of a routing, the changing of routing dates, or changes to it
Pull parameter Bills of Materials / Routings / Resources to Yes.
Components needed for a Changes to and deletions of components needed for a routing operation are cap
routing operation
Resources attached to a Changes to and deletions of operation resources or operation resource sequenc
routing operation Yes.
Resource requirements for Changes in resource requirements of WIP jobs because of completion of the WI
WIP jobs Data Pull parameter Work in Process to Yes.
Items or Item categories Changes in items and items categories are captured. Set the Planning Data Pul
Transactions (supply and demand) change more frequently than setup entities. After data
collections, the collections program maintains snapshots of transaction entities. Each time you
run data collections, the collections program looks at the snapshot to determine if the transaction
entity has changed since the previous collections. If it has, the collections program collects the
incremental data changes and updates the snapshot. As setup entities change less frequently,
the collections process does not keep snapshots for these and cannot perform net change
collections on them. Schedule either a targeted or a complete refresh for setup.
You cannot run data collections in net change mode for the following setup entities:
Simulation sets
Resource shift setup
Projects or project tasks
Units of measure (class conversion, conversions)
Sourcing information
Bills of resources
Calendar information (start dates calendar dates, calendar week, calendar
shifts, shift Dates, shift exceptions, shift times, period start dates)
Interorganization ship methods
Planning parameters
Planners
Business intelligence systems periods
Resource groups
Demand classes
Available to promise (ATP) rules
Trading partners (customer or customer sites, suppliers, supplier sites,
organization, organization sites, location associations, customer, vendor,
buyer, contacts)
Continuous Collections
Continuous collection is an automated process that synchronizes snapshot-enabled data entities
(supply and demand) and snapshot-disabled setup entities (suppliers, customers and supplier
rules) between the sources and the planning server. You can schedule separate collection
programs for collecting data entities and setup entities.
The Continuous Collections concurrent program performs the process of continuous collections.
You have to select only those business entities for which the collections process needs to run
automatically. The Continuous Collections concurrent program determines the appropriate mode
of performing collections for the selected business entities. You can run continuous collections
on the following entities:
For entities that have snapshots associated with the source, you need to
specify a threshold value (as a percent). Based on this value, the Continuous
Collections concurrent program determines whether the collections should run
in the Targeted mode or the Net Change refresh mode. If continuous
collections are run frequently, then for most entities, the data collections are
performed in the Net Change Refresh mode.
If the changed records percent is below the threshold percent, the concurrent
process collects only the changed records (Net Change Refresh) from the
snapshot log.
If the changed records percent is higher than the threshold percent, the
concurrent process collects all of the rows (Targeted Change Refresh) from
the snapshot.
If there are no changed records, the concurrent process does not collect any
data.
The following table details whether or not snapshots are associated for the entities supported by
continuous collections:
Entities
Approved supplier lists (Supplier capacity)
Bills of material
Routings
Resources
Bills of resources
Forecasts
Items
Master demand schedule
Master production schedule
On hand quantity
Purchase orders
Purchase requisitions
Sales orders
User supplies and demands
Work in process
Available to promise rules
Calendars
Demand classes
End item substitution
Key performance indicator targets
Planning parameters
Planners
Projects and tasks
Reservations
Resource availability
Safety stock
Sourcing history
Sourcing rules
Subinventories
Trading partners (customers and suppliers)
Unit numbers
Units of measure
User company association
For entities without snapshots, the concurrent program always initiates targeted refresh.
You can plan to use continuous collections when extensive transactions are involved. For
example, a manufacturing company with extensive work in process transactions might setup
continuous collections to run every 20 minutes to collect on hand balance. Similarly, Oracle
Collaborative Planning users might schedule continuous collections every 2 minutes if they want
to view the current supplies status.
Running Continuous Collections
To collect data from an Oracle Applications transaction
instance
1. Sign on using the Advanced Supply Chain Planner responsibility or the
Advanced Planning Administrator responsibility.
2. From the Navigator, select Collections > Oracle Systems > Continuous
Collection.
The Continuous Collections window appears.
This window enables you to schedule the process of data collection, set
parameters that are required for running Continuous collections, select
language preferences, and specify the notification tasks that need to be
triggered on completion of Continuous collections.
3. Click in the Parameters field to set values that the concurrent program would
require to perform Continuous collections.
The Parameters window appears.
Specify Yes for the entities that you want the Continuous Collections
concurrent program to consider for collection. Most of the fields in this window
are similar to the parameter fields for the Standard collections process. The
parameter that distinguishes the Continuous collections process from the
Standard collections process is Snapshot Threshold (%). By default, the
threshold value is set to 40%. You can change this value.
4. Select OK.
5. Select Schedule in the Continuous Collections window to schedule collections.
The Schedule window appears.
6. Select the frequency for running collections in the left pane. Complete any
additional fields that appear based on your selection.
7. Click OK.
8. Select Submit in the Continuous Collections window.
9. From the toolbar, choose View > Requests to view the status of the
collections process.
The Find Requests window appears.
10. Specify the type of request you want to view.
11. Select Find.
The Requests window displays the status of the data collection process.
After the collection process completes, view the result in the Collection
Workbench.