4 Integration Configurations

Merchandising System Configuration

Direct database integration method between Merchandising and SIOCS is governed by the following indicators. It is advisable that before requesting to turn this integration on, ensure you have a discussion with your implementation partner and Oracle on how to best plan for this effort. Refer to Document 2963593.1 for details on the process for initiating the integration configuration change request.

• SIOCS ICL Indicator^Foot 1 – Indicates whether SIOCS gets data from the Merchandising applications through ICL (integration change log) tables. If set to Yes (Y), integration through RIB is disabled and ICL tables are populated. It is defaulted to N. This should be set in sync with the corresponding indicator in SIOCS as part of implementation. There is no user interface option for this and can be managed through a service request to Oracle.
• Inbound Data History Months – Specifies the number of months the archived inbound transactions will remain in the import history tables and can be set through the System Options screen. All history dated later than this is automatically removed by a batch process.
• Inbound Data Unprocessed Error Days –Specifies the number of days the inbound data error records are retained in the inbound staging and error logging tables and can be set through the System Options screen.

SIOCS System Configuration

To use the direct database integration method, a few restricted system configuration values need to be updated through a service request to Oracle. Please refer to Document 2963593.1 to know more about integration configuration change request procedure.

---

Footnote Legend

Footnote 1: SIOCS_ICL_IND in PRODUCT_CONFIG_OPTIONS table