What Effects Does 'Replicate Seed Data' Concurrent Request Have On Appls?

 

The information in this article applies to:

Oracle Incentive Compensation - Version: 11.5.8
This problem can occur on any platform.

Goal

System wide consequences of running "Replicate Seed Data"
and is it safe to run the program.

Fix

The purpose of the Replicate Seed Data Concurrent Program is to populate the Installed modules
to be populated with Seeded values, so that the module can be worked upon with.

Whenever new Organizations are created ( under the Multi-org Setup and Multi-org setup is mandatory now) it is a prerequired Step to be completed before you can start work upon using that newly created Organization.

The Replicate Seed Data Concurrent Program can always be run for a particular Operating Unit or for all Operating Units (as it is not mandatory parameter) and you cannot run the program for a particular module , for example, Incentive compensation.

The idea behind running the concurrent program is - as stated above - whenever new Organizations are created - it should be provided with Seeded data from all relevant modules for normal integration among the modules and to get functionalities of the module being used also well. For example, even if you are not going to Use Oracle Inventory, the seeded Item information is required in other modules to choose Item related information.

The Replicate Seed data concurrent program cannot be run for invidiual module but for only for one or all Operating Units.
Note: When running the Replicate Seed Data process ensure no users are logged-in.