2 Data Seeding

This chapter contains the following:

• What is Data Seeding?

• Why Use Data Seeding?

• When To Run Data Seeding

• How BDI Data Seeding Functions

• EICS Data Seeding Preparation

• BDI-Based Data Seeding

What is Data Seeding?

Using Oracle EICS Data Seeding, you can load data in bulk, including inventory and stock holding entities, from a data producing system into Oracle EICS.

Data Seeding is most suitable for:

• Loading initial inventory holding data

• Loading large volumes of data

Typically, you use data seeding for an initial data seeding and maintain the data in Oracle EICS thereafter, or through near-real time data integration with data producing system systems.

Business Objects for Data Seeding

The following table shows the business objects that can be seeded from a data producing system to EICS using BDI-Based Data Seeding. For the initial data seeding, data objects must be loaded the group order shown here to respect dependencies between objects.

Table 2-1 EICS Data Loading Dependencies

Group Order	Business Object	Dependency
1	Warehouse	None
1	Warehouse Address	None
1	Partner	None
1	Partner Address	None
1	Supplier	None
1	Supplier Address	None
1	Merchandise Hierarchy	None
2	Partner Org Unit	Partner
2	Item Header	Supplier
2	UDA (User Defined Attribute)	None
2	Differentiator Group	None
2	Code Head	None
3	Pack Item	Item Header
3	Related Item	Item Header
4	Item Supplier	Item Header, Supplier
4	Item Supplier Country Dimension	Item Header, Supplier
4	Item Supplier Country	Item Header, Supplier
4	Item Supplier Manufacturing Country	Item Header, Supplier
4	Item Supplier UOM	Item Header, Supplier
5	Store	None
5	Store Address	None
6	Item Location	Store, Warehouse, Partner, Item
6	Inventory Available Store	Store, Item
7	Replenishment Item Location	Store, Item
7	Price History	Store, Item
8	Item Image	Item
8	UOM Class	None
8	UDA Item Date	UDA
8	UDA Item Free Form	UDA
8	UDA Item LOV	UDA
8	UDA Values	UDA
9	Code Detail	Code Head
9	Delivery Slot	None
9	Differentiator	None
9	UOM Conversion	UOM Class

Why Use Data Seeding?

When a full installation of the EICS application takes place there is no inventory data in ECIS tables. The initial inventory positions will need to be seeded from a data producing system. By default, EICS seeds its data from Oracle Retail Merchandise Cloud Service System as its out-of-box solution.

When To Run Data Seeding

EICS initial inventory data seeding is applicable for new or fresh full EICS installation, and should only be run once.

Once the initial set of data is seeded into ECIS, the subsequent inventory changes are communicated between sourcing/destination applications via Oracle Retail Integration Cloud Service.

How BDI Data Seeding Functions

EICS data seeding uses the Oracle Retail Bulk Data Integration (BDI) process to extract data from a data producing system and load the same data into Oracle EICS application tables.

The BDI data seeding process:

• An Extractor extracts data from a data producing system into an outgoing intermediate integration interface table.

• A Downloader and transporter services data to receiver service.

• An Uploader uploads the data to an incoming intermediate integration interface tables.

• An Importer imports the data from the interface tables into EICS application tables.

The following figure shows the key stages of the data seeding process using Oracle BDI-Based Data Seeding.

Figure 2-1 Data Seeding Process

For additional detail on BDI Data Integration Topologies, please see Oracle Retail Bulk Data Integration Implementation Guide.

EICS Data Seeding Preparation

This topic contains the following:

• EICS Data Seeding Security Settings

• EICS Data Seeding Configuration Parameters

• Managing Data Seeding Process Configurations

EICS Data Seeding Security Settings

EICS System Ops user must be assigned to following EICS application security permissions:

Permission Name	Description
Access Batch Admin	Allows access to EICS batch job screen.
Access Data Seed	Allows EICS user to manually run data seeding importer jobs via EICS batch job admin.

EICS Data Seeding Configuration Parameters

The EICS Data Seeding Importer process in EICS loads data from the staged or intermediate tables into ECIS application tables. The configuration parameters determine how the importer process operates in EICS.

Because the full set of data should only be loaded once for foundation inventory data and store Inventory data, when EICS is initially installed, the data seeding system configuration flags are disabled.

The following table shows the configuration parameters and their default values.

Configuration Name	Description
Data Seed Foundation Data	The foundation data can be used for initial bulk load of EICS foundation data (such as Supplier, Merchandise Hierarchy, Item and others) from data producing system during initial setup of ECIS system. This option should be disabled after EICS data seeding is completed. Default value is set to No. If you set this parameter to Yes, then data from sourcing system are automatically loaded into EICS application tables during BDI Process Flow process. If you leave this parameter to No, the process loads the data from sourcing system into EICS BDI inbound interface tables, then you must run Importer Job to load data from interface tables into application tables manually via EICS Batch Job Admin Console, see Appendix: Run Importer Separately from EICS Job Admin for details.
Data Seed Store Data	The seed store data can be used for initial bulk data load of EICS store inventory data (such as Store Item, and Store Item Stock) from a data producing system. Default value is set to No. If you set this parameter to Yes, then store data from sourcing system are automatically loaded into EICS application tables during BDI Process Flow process. If you leave this parameter to No, the process loads the store data from sourcing system into EICS BDI inbound interface tables, then you must run Importer Job to load store data from interface tables into application tables manually via EICS Batch Job Admin Console, see Appendix: Run Importer Separately from EICS Job Admin for details.
Data Seed By Store	Determines whether the store data are automatically loaded for a single store only when Data Seed Store Data is set to Yes. By default, this parameter is set to No, then all stores and inventory are seeded. To rollout a single store, enable this configuration allow only a single store's inventory data to be seeded. Default value is set to No. If you set this parameter to Yes, then you must run Importer Job for store data manually via EICS Batch Job Admin Console, see Appendix: Run Importer Separately from EICS Job Admin for details.
Data Seed Chunk Limit	Controls the data seeding transaction size limit. Default value is set to 10000.
Data Seed On Error Continue	This flag determines how the error should be handled during data seeding import process. If the flag is turned on (true), the process will skip the current chunk of data, and continue to process next chunk of data. If the flag is turned off (false), the data loading process will be terminated when an error occurs. Default value is set to No.

To change configuration values:

1. Login to Oracle Enterprise Inventory Cloud Service page as ECIS System Ops user.

   
   

   Note: Full details about the configuration screens can be found in the Oracle Retail Enterprise Inventory Cloud Service User Guide.

   
   

2. On Main Menu, select Admin/Configuration/System Administration.

3. Search for data seed in option field, change value and save the change.

Figure 2-2 Data Seed Settings

Managing Data Seeding Process Configurations

To seed initial inventory foundation data from sourcing system directly into destination application tables, an application implementation consultant must perform the following configuration steps:

1. Use EICS System Administration Console to set data seeding foundation to Yes.

2. Use EICS System Administration Console to set data seeding store to Yes.

Optionally, if you want to manual control the importer steps, then you perform following steps:

1. Use EICS System Administration Console to set data seeding foundation to No.

2. Use EICS System Administration Console to set data seeding store to No.

3. Start BDI Process Flow (see BDI Process Flow Admin Console section for details).

4. Once data is loaded into inbound interface table, if you want to import interface data into application tables, set data seeding foundation to Yes, set data seeding store to Yes.

5. Use EICS Batch Job Admin Data Seeding jobs to manually start data seeding importer job.

For additional details, please see Appendix: Run Importer Separately from EICS Job Admin.

BDI-Based Data Seeding

This topic contains the following:

• BDI-Based Data Seeding Pre-requisites

• Start BDI-Based Data Seeding Process

• BDI Process Flow Admin Console

• BDI-Based Data Seeding Post-Load Processes

BDI-Based Data Seeding Pre-requisites

• Sourcing System (for example, Oracle RMS)

  The sourcing system is installed and initial inventory holding entities and data set up is completed within the data producing system.

• EICS

  EICS database and applications installations are completed.

• BDI Components

  The following BDI components have been installed as part of Oracle Retail Integration Cloud Service.

  BDI Process Flow: Provides a mechanism to run multiple dependent batch jobs.

  BDI-RMS Batch Job Admin: Provides management of BDI for RMS batch jobs.

  BDI-SIM Batch Job Admin: Provides management of BDI for EICS batch jobs.

  Please refer to the Oracle Retail Bulk Data Integration Installation Guide for BDI installations.

Start BDI-Based Data Seeding Process

You only need to run one time full data seeding to initially seed functional inventory data into EICS.

The data seeding processes can be started via BDI Process Flow Admin Console. Please followData Seeding Process Flow Dependencies List to start data seeding process.

Note: There is no dependencies within the same process group.

Table 2-2 Data Seeding Process Flow Dependencies List

Group#	Process Flow	Notes
1	MerchHier_Fnd_ProcessFlow_From_RMS	Merchandise Hierarchy foundation data seed from Merchandising Foundation Data System. Run once for initial full data seed.
1	Supplier_Fnd_ProcessFlow_From_RMS	Supplier foundation data seed from Merchandising Foundation Data System. Run once for initial full data seed.
1	SupplierAddr_Fnd_ProcessFlow_From_RMS	Supplier address foundation data seed from Merchandising Foundation Data System.
1	Partner_Fnd_ProcessFlow_From_RMS	Partner foundation data seed from Merchandising Foundation Data System.
1	PartnerAddr_Fnd_ProcessFlow_From_RMS	Partner address foundation data seed from Merchandising Foundation Data System.
1	Wh_Fnd_ProcessFlow_From_RMS	Run once for initial full warehouse foundation data seed from Merchandising Foundation Data System.
1	WhAddr_ProcessFlow_From_RMS	Run once for initial full warehouse address foundation data seed from Merchandising Foundation Data System.
2	PartOrgUnit_Fnd_ProcessFlow_From_RMS	Run once for initial full partner Org Unit foundation data seed from Merchandising Foundation Data System.
2	ItemHdr_Fnd_ProcessFlow_From_RMS	Run once for initial full item foundation data seed from Merchandising Foundation Data System.
2	Uda_Fnd_ProcessFlow_From_RMS	Run once for initial full User Defined Attribute (UDA) foundation data seed from Merchandising Foundation Data System.
2	DiffGrp_Fnd_ProcessFlow_From_RMS	Run once for initial full foundation data seed from Merchandising Foundation Data System.
2	CodeHead_Fnd_ProcessFlow_From_RMS	Run once for initial full Code Head foundation data seed from Merchandising Foundation Data System.
3	PckitemBrkout_Fnd_ProcessFlow_From_RMS	Run once for initial full Pack Item Breakout foundation data seed from Merchandising Foundation Data System.
3	RelatedItem_Fnd_ProcessFlow_From_RMS	Run once for initial full Related Item foundation data seed from Merchandising Foundation Data System.
4	ItemSupplier_Fnd_ProcessFlow_From_RMS	Run once for initial full Item Supplier foundation data seed from Merchandising Foundation Data System.
4	ItSupCtryDim_Fnd_ProcessFlow_From_RMS	Run once for initial full Item Supplier Country Dimension foundation data seed from Merchandising Foundation Data System.
4	ItSupCtry_Fnd_ProcessFlow_From_RMS	Run once for initial full Item Supplier Country foundation data seed from Merchandising Foundation Data System.
4	ItSupCtryManCtry_Fnd_ProcessFlow_From_RMS	Run once for initial full Item Supplier Manufacturing Country foundation data seed from Merchandising Foundation Data System.
4	ItemSuppUom_Fnd_ProcessFlow_From_RMS	Run once for initial full Item Supplier Unit of Measure foundation data seed from Merchandising Foundation Data System.
5	Store_Fnd_ProcessFlow_From_RMS	Run once for initial full store foundation data seed from Merchandising Foundation Data System.
5	StoreAddr_Fnd_ProcessFlow_From_RMS	Run once for initial full store address foundation data seed from Merchandising Foundation Data System.
6	ItemLoc_Fnd_ProcessFlow_From_RMS	Run once for initial full item location foundation data seed from Merchandising Foundation Data System.
6	InvAvailStore_Tx_ProcessFlow_From_RMS	Run once for initial full store available inventory foundation data seed from Merchandising Foundation Data System.
7	ReplItemLoc_Fnd_ProcessFlow_From_RMS	Run once for initial full replenishment item location inventory foundation data seed from Merchandising Foundation Data System.
7	PriceHist_Fnd_ProcessFlow_From_RMS	Run once for initial full item pricing history foundation data seed from Merchandising Foundation Data System.
8	ItemImage_Fnd_ProcessFlow_From_RMS	Run once for initial full item image foundation data seed from Merchandising Foundation Data System.
8	UomClass_Fnd_ProcessFlow_From_RMS	Run once for initial full Unit Of Measure foundation data seed from Merchandising Foundation Data System.
8	UdaItemDate_Fnd_ProcessFlow_From_RMS	Run once for initial full UDA Item Date foundation data seed from Merchandising Foundation Data System.
8	UdaItemFF_Fnd_ProcessFlow_From_RMS	Run once for initial full UDA Item Free Form foundation data seed from Merchandising Foundation Data System.
8	UdaItemLov_Fnd_ProcessFlow_From_RMS	Run once for initial full UDA Item LOV foundation data seed from Merchandising Foundation Data System.
8	UdaValues_Fnd_ProcessFlow_From_RMS	Run once for initial full UDA Values foundation data seed from Merchandising Foundation Data System.
9	CodeDetail_Fnd_ProcessFlow_From_RMS	Run once for initial full Code Detail foundation data seed from Merchandising Foundation Data System.
9	DeliverySlot_Fnd_ProcessFlow_From_RMS	Run once for initial full Delivery Slot foundation data seed from Merchandising Foundation Data System.
9	Diff_Fnd_ProcessFlow_From_RMS	Run once for initial full Differentiators foundation data seed from Merchandising Foundation Data System.
9	UomConversion_Fnd_ProcessFlow_From_RMS	Run once for initial full UOM Conversion foundation data seed from Merchandising Foundation Data System.

BDI Process Flow Admin Console

To start the process flow: login to BDI Process Flow Console, click Manage Process Flow tab, choose group SIM from Select Group drop-down list.

1. Login to BDI Process Flow Console.

2. Click Manage Process Flow.

3. Choose group SIM from Select Group drop-down list.

Figure 2-3 BDI Process Flow Console

To start the process:

1. Select the process name.

2. Navigate to the lower panel, and click Launch Process Flow.

3. Click Run.

Figure 2-4 Launch Process

To view BDI Process Flow details, navigate to Process Flow Execution tab to track the status of process flow.

Figure 2-5 Process Flow Details

View Process Flow component details:

• Extractor

• Downloader

• Uploader/Receiver

• Importer

Extractor

To view extract data from source app, launch edge app batch job admin. The following shows the steps to view extractor from RMS:

1. Launch RMS Batch Job Admin console.

2. Login as BDI Job Admin user.

   Figure 2-6 RMS Batch Job

   
   

   For details, please see Oracle Retail Bulk Data Integration Implementation Guide.

Downloader

To view BDI Downloader job details:

1. Launch BDI for edge app batch admin console.

   Follow these steps to view download from RMS.

2. Launch BDI RMS Batch Job Admin console.

3. Login as BDI RMS Job Admin user.

   Figure 2-7 BDI RMS Batch Job

   
   

   For details, please see Oracle Retail Bulk Data Integration Implementation Guide.

Uploader/Receiver

To view BDI SIM uploader details:

1. Launch BDI SIM Edge Batch Job Admin console.

2. Login as SIM BDI Job Admin user.

   Figure 2-8 BDI SIM Batch Job

   
   

   For details, please see Oracle Retail Bulk Data Integration Implementation Guide.

Importer

To View ECIS Importer details:

1. Launch EICS application, login ECIS as System Ops user.

2. On Main Menu, select Admin/ Technical Maintenance/Job Admin.

   Figure 2-9 EICS Job Admin

   
   

3. To view detail record, select the record, then click hyperlink on the execution id. This will bring you to the Job Execution Detail screen.

   Figure 2-10 Job Execution

   
   

Load Staging Data to Application Tables

If you set the EICS seed options to enabled, the data from external source system is automatically loaded into application table, and you can skip the following steps.

If you set the seed options to disabled, and want to load data from staging table to applications through manual steps, please refer to the following:

Task	Step
Enable Data Seed Flags	Login ECIS as System Ops userOn Main Menu, Select Admin - Configuration - System AdministrationSearch for data seed on option field, change to desired value and save the change. Enabled Data Seed Foundation Data: true Enable Data Seed Store Data: true
Load data from stage tables to application tables	See Appendix: Run Importer Separately from EICS Job Admin.

Re-running EICS Importer Data Loads

After correcting the errors during process flow, you may re-run the initial data seeding process flow.

Important: Before executing additional runs of data seeding, please choose the appropriate re-seed options in EICS Job Admin Console.

Note: To import data for a specific store, please see Addition Notes: Importing Data for Single Store section

EICS system ops user login EICS, from Main Menu, navigate to Admin Technical Maintenance/Job Admin

On Job Admin Screen, click Data Seed. This will bring you to the Data Seed screen (for screen details, see Data Seed Importer Job), follow following steps:

Task	Step
Delete the previous seeded module data	Choose desired module from job drop-down list, and then select Data Seed Option Deleted. For example: Choose Job Name Store End. Select Seed Option Delete Seeded. If you enter the store id, then only the seed data for that store is deleted.
Re-load data from stage tables (see Re-import data from Source System, Re-import data step)	Choose Job Name Store from job drop-down list, and then select Data Seed Option Seed. For example: If you enter the store id, then only the seed data for that store is seeded. If you want to import all stores, leave the store id as blank.
Re-import data from Source System	Delete the previous seeded module data Go to BDI process flow, choose the flow to be re-run, start the BDI process flow

BDI-Based Data Seeding Post-Load Processes

1. Enable Oracle Enterprise Inventory Cloud Service (EICS) constraints after data seeding.

   1. Login EICS as ECIS System Ops user.

   2. On Main Menu, navigate to Admin/Technical Maintenance/Job Admin

   3. On Job Admin Screen, click Data Seed. This will bring you to the Data Seed screen.

   4. Select Job Name Database Constraints.

   5. From Seed Option drop-down list, select Enable Constraint, click Start Job.

2. Purge data from inbound data seeding stage tables.

   To purge the data from inbound staging tables:

   1. Login EICS as ECIS System Ops user.

   2. On Main Menu, navigate to Admin Technical Maintenance/Job Admin.

   3. On Job Admin Screen, click Data Seed. This will bring you to the Data Seed screen.

   4. Select Each Importer Job Name (for example Code Head), then choose Seed Option Delete In, click Start Job.

3. Turn off EICS Data Seeding System Configuration Flags.

   1. Login EICS as ECIS System Ops user.

   2. On Main Menu, navigate to Admin/Configuration/System Administration.

   3. Search for data seed on option field, change value and save the change.

   4. Set the following values:

      Enabled Seed Foundation: No.

      Enable Seed Store Data: No.