The Complete Refresh method clears all previously collected planning 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 because it copies all of the planning information from
the EBS application tables.

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. Process manufacturing (OPM) is not supported using
Net Change Refresh. Instead, use a targeted refresh for OPM.

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 Comments

Sales orders : Cancellations of or modifications to sales orders and sales order

reservations are captured. Net change collections always collects sales orders; it
is not dependent on any parameters or settings, including Pull collection parameter
Sales Orders.

Reservations against demands : Reservations against both external and internal

sales order demands are captured. Set the Planning Data Pull parameter Reservations
to Yes.

Master production schedule demands : MPS demands that are added, modified or
relieved in the source instance are captured. Set the Planning Data Pull parameter
Master Production Schedules to Yes to collect just these changes during a Net
Change collection.

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 jobs (for example, operations within a job have been performed or
cancelled), and changes to WIP jobs because of changes in item information are
captured. Set the Planning Data Pull parameter Work in Process to Yes.

WIP repetitive item demands : Demand changes due to cancellation of WIP repetitive
schedules, changes in the state of WIP repetitive schedules, and changes to WIP
repetitive schedules because of changes in item information 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 parameter Forecasts to Yes.

Master production schedule supplies : Changes in supply schedules or item

information are captured. Set the Planning Data Pull parameter Master Production
Schedules to Yes
User supplies and demands : Changes to user supplies and demands because of changes
to item information are captured. Set the Planning Data Pull parameter User
Supplies and Demands to Yes.

Purchase order supplies : Changes to PO supplies because of rejections, returns, or

cancellations or changes to item information are captured. Set the Planning Data
Pull parameter Purchase Orders/Purchase Requisitions to Yes.
On-hand supplies : Set the Planning Data Pull parameter On Hand to Yes.

Work orders in Oracle Work in Process : Changes in WIP Jobs are captured. Set the
Planning Data Pull parameter Work in Process to Yes.

Resource availability : You can use net change mode in discrete manufacturing
organizations. Set the Planning Data Pull parameter Resource Availability to
Collect and Regenerate Data.
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, component quantities, effectivity dates, BOM revisions, and component
substitutes. Set the Planning Data Pull parameter Bills of Materials / Routings /
Resources to Yes.

Routing operations : Changes to and deletions of routing operations as a result of

changes to operation sequences (for example, the addition of new operations, the
disabling of operations, or the changing of operation dates), the disabling of a
routing, the changing of routing dates, or changes to item information (for
example, the disabling of an item, the creation of a new item) are captured. Set
the Planning Data Pull parameter Bills of Materials / Routings / Resources to Yes.

Components needed for a routing operation : Changes to and deletions of components

needed for a routing operation are captured. Set the Planning Data Pull parameter
Bills of Materials / Routings / Resources to Yes.

Resources attached to a routing operation : Changes to and deletions of operation

resources or operation resource sequences within a routing are captured. Set the
Planning Data Pull parameter Bills of Materials / Routings / Resources to Yes.

Resource requirements for WIP jobs : Changes in resource requirements of WIP jobs
because of completion of the WIP jobs, completion of operations within the WIP
jobs, or changes in item information are captured. Set the Planning Data Pull
parameter Work in Process to Yes.
Items or Item categories : Changes in items and items categories are captured. Set
the Planning Data Pull parameter Items to Yes.

Transactions (supply and demand) change more frequently than setup entities. After
data collections, the Advanced Supply Chain Planning program maintains logs of
entity transactions. Each time you run data collections, the collections program
applies the logged transactions to a snapshot. Net Change collections selects the
transactions applied to the snapshot since the last Planning Data Collection and
pulls only those new transactions to the staging tables. 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 entities.
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)