How to Request Foundation, Initial Data Seeding and Transactional Data Cleanup for SIOCS Non-Production/Test Data Including Production Environment Readiness Check for Go live
(Doc ID 2677710.1)
Last updated on JULY 23, 2024
Applies to:
Oracle Retail Enterprise Inventory Cloud ServiceInformation in this document applies to any platform.
Purpose
Retailers and Implementation partners require a way to clean up non-production data in the SIOCS environment during the project implementation phase before go-live. This may be required for any environment type (non-prod or prod) depending on which environments Retailers use for testing during implementation prior to go-live. The document also provides details on additional activities that would be required if the DB clean up request is related to a go-live pre cutover, cutover phases.
This activity does NOT apply to a PRODUCTION environment after SIOCS is live.
Scope
The data clean up scripts defined for this process would purge the following data from the target environment.
- Initial Data Seeding Staging Data
- Foundation Data
- Transaction Data
Data that will not be altered:
- System Configuration table. i.e. any changes made by the customer/SI will remain as is after the data clean up is complete
- Default Store Configuration table. When new stores data is seeded, default records from the default store configuration will be copied for each seeded store location
- User roles and permissions related tables
- Translation tables
- Base data that is required and installed as part of the installation process will remain untouched. This includes all the tables below:
'DBMANIFEST',
'BARCODE_PROCESSOR',
'BATCH_JOB',
'CODE_DETAIL', -- keeps datas inserted by installer
'CODE_TYPE', --keeps datas inserted by installer
'CONFIG_EXT_SERVICE'
'CONFIG_SYSTEM',
'DCS_WORK',
'DCS_WORK_TYPE'
'REPORT_TEMPLATE'
'INV_ADJUST_REASON', (Note: Additional Data loaded to this table is untouched)
'MPS_WORK_TYPE',
'NONSELLABLE_TYPE', (Note: Additional Data loaded to this table is untouched)
'REPORT_TEMPLATE',
'SHIPMENT_CARRIER',
'SHIPMENT_CARRIER_SERVICE',
'SHIPMENT_CARTON_DIM',
'SHIPMENT_REASON',
'SHIPMENT_WEIGHT_UOM',
'SUBSCRIPTION_USAGE'
'STORE', -- keep store_id = 0
'STORE_PRINTER_TYPE',
'RDS_REPLICATION_CONFIG',
'SECURITY_CRED_STORE',
'SERVER_SYNC_WORK',
'SEQUENCE_ADMIN',
'IDL_TYPE',
'ITEM_ISN_TYPE',
'UIN_LABEL'
NOTE:
- If the SIOCS environment where the data base tables clean up is being performed is integrated with Oracle Retail Data Storage Cloud Service (RDS), SIOCS RDS replication will be stopped before the cleanup. You will need to submit a separate Service Request against RDS to start SIOCS replication after new data is seeded into SIOCS.
- If the SIOCS environment where the data base tables clean up is being performed is integrated with OCI GoldenGate Cloud Service, you will be required to do the following:
1. Stop REPLICAT on the Target side before Oracle can begin the data cleanup activity.
2. Submit a Service Request for a new DAS export to be provided after new data is seeded into SIOCS.
3. Immediately after the DAS export is provided, start Target Replicat and DAS export imported into Target database.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |