1. Implementation Guide
  2. Mobile Application (SOCS)

10 Mobile Application (SOCS)

SOCS is a hybrid mobile platform that gets distributed through a mobile application archive (.maa) file from the Oracle Software Delivery Cloud (OSDC). Go to https://edelivery.oracle.com and search for Store Operations Cloud Service to get the mobile archive file. This .maa needs to be built into either an Android build (apk) or an iOS build (ipa).

For details, see the Oracle Retail Store Operations Cloud Service Mobile Guide.

Configure Manual Quantity Entry Mode

For MAF client, you need to set the numeric entry popup on MAF will have its mode defaulted to either scan mode or override mode.

For details, see the Oracle Retail Enterprise Inventory Cloud Service Administration Guide Configuration chapter.

Enable Mobile Functionalities

By default, the EICS application installer set following value as false.

input.sim.mobile.client.enabled = false

By disabling Access Execution UI, Mobile Client (SOCS) access on following functional areas is disabled. If a customer has purchased SOCS licenses, then following access permissions need to be enabled in order to use these functionalities on mobile client.

  • Access Execution UI

  • Access Inventory Adjustments

  • Access DSD Receiving

  • Access RTV

  • Access RTV Shipment

  • Access Transfer

  • Access Transfer Shipment

  • Access Transfer Receiving

  • Access Customer Order

  • Access Stock Count

  • Access Shelf Replenishment

  • Access Open Transactions

  • Access Notifications

  • Access Item Basket

Mobile Device Management (MDM)

Retailers need to use their own MDM infrastructure to push mobile updates to each store/device.

Due to corporate guidelines, Oracle Retail SOCS is not permitted to be distributed via Google or Apple Play Stores.

We have concerns that any MDM (Mobile Device Management) tool that relies on Google Play Store – even when used in enterprise-managed-deployment mode — may also not be allowed as part of the contractual agreement.

Retailers should not be using any MDM tool that uses Google Play Store – either directly or indirectly. 

Examples of MDM tools that rely on Google Play Store are ManageEngine MDM, Microsoft Intune, Radix MDM, and Vantage MDM.

Note:

Please note that this list is not a complete list. There are 100s of MDM tools available, so Retailers need to do their own verification. 

In case your corporate already uses one of these MDM tools (that rely on Google Play Store) your options could be:

  • Explore the MDM administration, to see if it offers a configuration to use its own internal cloud storage for the application instead of using or indexing the Google Play Store.

  • Explore the MDM administration, to see if it offers a configuration that allows a different MDM tool to be used for SOCS Mobile — one that does not use Google Play Store.

  • Move away from such a MDM tool to another MDM that does not use Google Play Store directly or indirectly.