Step-by-Step Initial Data Loading Process for Oracle Retail SIOCS

This guide explains the recommended sequence for loading foundation, store, and transactional data into the Oracle Retail Store Inventory Operations Cloud Service (SIOCS) DEV3 environment.

Following the correct sequence is essential because store-level and transactional records depend on foundation data such as items, suppliers, warehouses, currencies, units of measure, and inventory statuses.

Data-Loading Sequence at a Glance

The migration is performed in three main phases:

1. Load foundation data.
2. Load store and item-store data.
3. Load transactional data in the required sequence.

Each phase must finish successfully before the next phase begins.

Phase 1: Load Foundation Data

Step 1: Upload the Foundation Files

Upload the following files to File Transfer Services (FTS) or the configured Object Storage location:

IDL-DIFFERENTIATORTYPE-0001.csv
IDL-DIFFERENTIATOR-0001.csv
IDL-CURRENCY-0001.csv
IDL-UOMCLASS-0001.csv
IDL-UOM-0001.csv
IDL-CODETYPE-0001.csv
IDL-CODE-0001.csv
IDL-INVENTORYSTATUS-0001.csv
IDL-ITEMHIERARCHY-0001.csv
IDL-ITEM-0001.csv
IDL-SUPPLIER-0001.csv
IDL-SUPPLIERITEM-0001.csv
IDL-WAREHOUSE-0001.csv
IDL-WAREHOUSEITEM-0001.csv
IDL-STORE-0001.csv

Step 2: Run the Foundation Import Batch

Navigate to:

SIOCS Admin UI → Batch Admin → Run Job

Run the following batch job:

Initial Foundation Data File Import

Important considerations:

• A Store ID is not required for this batch.
• Monitor the file-processing status through the Integration Dashboard.
• Do not proceed to the next phase until all required foundation files have completed successfully.

Step 3: Review and Correct Errors

If any file fails:

1. Review the error details in the Integration Dashboard.
2. Correct the rejected records or file structure.
3. Re-upload the corrected file.
4. Run the batch job again.
5. Confirm that processing has completed successfully.

Foundation data must be successfully loaded before processing store-level or transactional files.

Phase 2: Load Store and Item-Store Data

Step 4: Upload the Item-Store Files

Upload the item-store files for each store:

IDL-ITEMSTORE-1001-0001.csv
IDL-ITEMSTORE-1002-0001.csv

In this example, the files contain item-store relationships for stores 1001 and 1002.

Step 5: Run the Store Data Import Batch

Run the following batch job:

Initial Store Data File Import

Leave the Store ID blank when the batch must process files for both stores.

When no Store ID is provided:

• Files for stores 1001 and 1002 can be processed in the same batch execution.
• Processing may occur in parallel, depending on the environment and batch configuration.
• Progress and results can be monitored through the Integration Dashboard.

Step 6: Resolve Store-Data Errors

If processing errors occur:

1. Review the rejected records.
2. Correct the data.
3. Re-upload the affected files.
4. Run the batch again.
5. Wait until all item-store files have completed successfully.

Do not begin loading transactional data until the item-store relationships are available.

Phase 3: Load Transactional Data

Transactional data should be loaded only after the required foundation and store data has been successfully processed.

Step 7: Upload Purchase Order Files

Upload the purchase order files:

IDL-PURCHASEORDER-1001-0001.csv
IDL-PURCHASEORDER-1002-0001.csv

Step 8: Import Purchase Orders

Run:

Initial Store Data File Import

Leave the Store ID blank if files for both stores must be processed.

Wait for the batch to complete successfully before uploading the next transaction type.

Step 9: Upload Direct Store Delivery Files

Upload the DSD files:

IDL-DSD-1001-0001.csv
IDL-DSD-1002-0001.csv

Step 10: Import Direct Store Deliveries

Run:

Initial Store Data File Import

Monitor the results and wait for successful completion.

Step 11: Upload Transfer Shipment Files

Upload the transfer shipment files:

IDL-TRANSFERSHIPMENT-1001-0001.csv
IDL-TRANSFERSHIPMENT-1002-0001.csv

Step 12: Import Transfer Shipments

Run:

Initial Store Data File Import

Review the Integration Dashboard and confirm that processing has completed successfully.

Step 13: Upload Allocation Files

Upload the allocation files:

IDL-ALLOCATION-1001-0001.csv
IDL-ALLOCATION-1002-0001.csv

Step 14: Import Allocations

Run:

Initial Store Data File Import

Wait for the allocation files to complete successfully.

Once the foundation, store, and transactional files have all been processed without unresolved errors, the DEV3 initial data migration is complete.

Complete File and Batch-Job Summary

* The supplied loading sequence places IDL-STORE-0001.csv in the Foundation phase, while the file summary maps it to the Initial Store Data File Import batch. Confirm the correct batch mapping for your SIOCS version and implementation before executing or publishing the procedure.

Recommended Validation Checklist

Before moving to the next phase, verify the following:

• Every expected file was uploaded to the correct location.
• File names follow the required SIOCS naming convention.
• The correct batch job was selected.
• The appropriate Store ID option was used.
• All files show a successful status in the Integration Dashboard.
• Rejected records have been corrected and reprocessed.
• The expected record counts match the source-system counts.
• There are no unresolved dependency or reference-data errors.
• Sample items and transactions are visible in the SIOCS application.
• Batch logs and migration evidence have been retained for audit and troubleshooting.

Key Implementation Guidelines

• Always load foundation data before store and transactional data.
• Process one transaction category at a time.
• Wait for each batch to finish before uploading the next dependent dataset.
• Do not assume that a completed batch means every record was accepted; review record-level results.
• Maintain separate reconciliation totals for every file.
• Retain the original files, corrected files, batch logs, and error reports.
• Test the full process in DEV3 before repeating it in higher environments.

Conclusion

A successful SIOCS initial data load depends on correct sequencing, accurate file naming, controlled batch execution, and careful error monitoring. Loading foundation, store, and transactional data in clearly separated phases reduces dependency failures and makes reconciliation and troubleshooting significantly easier.