Next-generation platform

Completing common configurations

Edit online

To get started with Sterling Store Engagement, you must complete a few common configuration steps for all the fulfillment and inventory management tasks.

Applications Manager

Complete the following configurations in Applications Manager:
Participant setup
Consists of organizations that participate in the supply chain of the company and defines the relationship between these organizations. Set up the enterprises and nodes to suit your business model. For more information, see Participant modeling.
Store inventory configuration
Select the suitable Store Inventory Configuration option under node attributes as part of the roles and participant associations of the organization. You can enable Store Inventory Management capabilities for the store and choose whether you want to have the inventory that is managed in store or if the store is to be configured as a no-inventory store. For more information, see Configuring inventory management capability in stores.
Pipelines
Model your business workflows by using pipelines. For more information, see Process modeling concepts.
Users and user groups
Based on the tasks that are performed by different store personnel or the roles that they play in an organization, you must define users and group them into appropriate user groups. For more information, see Defining users and Defining user groups.
Team configuration
For additional security, businesses configure teams for users. If the team is configured for users, during the authentication process, the getTeamDetails API is called to read the node access configuration of the team. The isf.login.getTeamDetails mashup that is provided by the application is called with OrganizationCode as the user’s organization in the mashup input. It is assumed that the team is configured at the user’s enterprise level. If you do not create a team at the user’s enterprise level, you must customize the mashup and pass the OrganizationCode of the organization that maintains the team. For example, if the team is configured at the Hub level, in the customized mashup, set the OrganizationCode to DEFAULT. For more information, see Defining teams.
Resource permission
Control which user group has permissions to perform a specific task. For more information, see Administering user group permissions. For more information about the resource permissions that are enabled for Sterling Store Engagement capabilities, see the corresponding section under Configuring Sterling Store Engagement. For example, for the resource permissions that are enabled for the product search capability, see Configuring product search.
Unit of measure
Define the unit of measure (UOM) to be used in association with the products. This is a mandatory configuration and the UOM field for a product cannot be blank. For more information about configuring UOM, see Unit of measure.

System Management Administrator

In the System Management Administrator (SMA) console, configure the isf.user.session.timeout.interval property to set the session timeout interval in minutes. The default value is set to 0, which means the user activity is not tracked.

The isf.user.session.timeout.interval property determines the time a user is inactive in a session. After the time elapses, the session ends and the user must log in again to continue working.

Note: This property is independent of the existing sever-side user session timeout. For more information about configuring the server-side user session timeout, see Setting the user session timeout.

Sterling Business Center

Configure the catalog for your catalog organization. For more information, see Catalog Management.

Catalog data

Ensure that the catalog data from Sterling Order Management System is synchronized with Sterling Store Engagement. For more information about how to synchronize catalog data, such as serialized flag, department, and product velocity, see Updating catalog data.

Store Inventory Management

  • stores

    Use the stores API to configure stores. Complete this configuration before you can proceed to perform other configurations for the various flows in Sterling Store Engagement.

    You can configure a store by specifying either of the following location_configuration attributes:
    • SINGLE - Inventory is tracked in Sterling Store Engagement but it is not tracked at a granular level in store. When a store is created as a single-location store, system creates the following three locations automatically:
      • DEFAULT-LOCATION. This is the default location.
      • PICK-VIRTUAL. This in the virtual location when inventory is being picked.
      • STAGING-VIRTUAL. This is the staging location where customer pick and packed orders are kept.
    • MULTIPLE - Inventory is tracked at granular level locations as defined by the customers.

    You can also use this API to change or update the configurations of an existing store.

  • inventory-statuses

    Use the inventory-statuses API to create inventory statuses to be used in stores.

  • segment-configuration

    Use the segment-configuration API to configure the segments and segment types. By default, the following default values are configured when the tenant is provisioned:"defaultSegment": "WALK_IN""defaultSegmentType": "CHANNEL"

  • supply-type-configuration

    Use the supply-type-configuration API to configure the supply type. By default, the following default value is configured when the tenant is provisioned:"defaultSupplyType": "ONHAND"

  • store-rules

    Use the Store Rules API to configure whether to mandate the location scan. The valid values for IS_LOC_SCAN_MANDATORY are Y and N. The default value is set to N.

    For feature-specific location scan configuration, see configuring Sterling Store Engagement.