1 Oracle SIOCS Implementation Overview

EICS (Enterprise Inventory Cloud Service) and SOCS (Store Operations Cloud Service) are two separately licensed products.

EICS includes:

  • EICS Desktop Client that runs on a browser

  • EICS Web Services

  • EICS Server Tier

  • EICS Database Tier with data access code, batches, reports

SOCS includes:

  • Oracle MAF Client that runs on mobile devices

  • Oracle Jet Mobile Client that runs on mobile devices and browser

In order to use SOCS, EICS needs to be deployed.

The implementation process includes a needs assessment, business impact analysis, requirements gathering, and other activities. However, this document is concerned only with the specific aspects of a technical implementation. In a typical project life cycle, technical implementations can begin only after the environment has been provisioned. Once a subscription agreement has been signed and Service Activation Request is logged, the Oracle Cloud team will start the provisioning process.

Once the account is provisioned, the Oracle Cloud team provides the following:

  • URL to access the EICS Application User Interface (UI) for production and staging environments.

  • One Customer Delegate Administrator user account.

  • URLs to access the various web services associated with the staging and production environments.

NextGen SaaS SIOCS

  • UI:

    • No Wavelink UI, No Swing UI. (If you are migrating from on-premise SIM V16.x.)

    • Uses Oracle JET (JavaScript extension technology) based UI for Administration UI.

    • Oracle MAF (mobile application framework). ** Deprecation has been started.

    • Oracle Jet Mobile for mobile UI. ** This would be go forward direction.

  • Server:

    • No change in server technology. (If you are migrating from on-premise SIM V16.x.)

    • Some changes to support modified/new functionalities.

  • Database:

    • Minimal Schema Change.

  • Integration:

    • Integrates with RICS (Retail Integration Cloud Service).

    • Direct Database integration with MFCS. ** This would be go forward direction.

  • Web Service APIs :

    • REST services. ** This would be go forward direction.

      Note:

      Point of sale integration web services must use REST interface.

    • SOAP services. ** Deprecation has been started.

  • Security Model:

    • Authentication: using IDCS.

    • Authorization: EICS Administration UI.

  • Batch scheduling:

    • Internal to EICS. It has a batch scheduler interface.

    • Using POM (Process Orchestration Management). ** This would be go forward direction.

  • Deployment:

    • Deploys with NextGen-MFCS in a shared pluggable deployment. ** This would be go forward direction.

    • Deploys with GBUCS-MFCS in a hybrid deployment.

    • Deploys with on-premise RMS in a hybrid deployment.

Oracle Retail Integration Components

EICS requires other systems, such as a merchandising system, to provide foundation (item, location, and so on) and transaction data (purchase order, stock order) to operate. This would be integrated through either Direct Database integration with MFCS OR RICS (Retail Integration Cloud Service).

Please note Direct Database integration (shared pluggable database) is the go forward approach.

For more details, see the information on integration in the Oracle Retail Enterprise Inventory Cloud Service Inbound and Outbound Administration Guide.

Implementation Considerations

In general, a technical implementation involves the following key steps areas:

URL Reference

The EICS URLs required for reporting, apex data viewer, EICS to RICS Message Publishing and Web service APIs will need to be formed using the format provided in the Oracle Retail Enterprise Inventory Cloud Service Inbound and Outbound Integration Guide.