Updating catalog data
You can synchronize catalog data, such as serialized flag, department, and product velocity, from IBM® Sterling Order Management System to Store Inventory Management.
Currently, catalog data is configured in Sterling
Order Management System by using the Applications Manager, item loading services, or Sterling
Order Management System APIs such as
Since inventory management, cycle count, and batch picking require the catalog data, such as serialized flag, department, and product velocity, it must be synchronized from Sterling Order Management System to Store Inventory Management. These fields are updated from Sterling Order Management System to Store Inventory Management in two ways – synchronously and asynchronously.
Order Management System can synchronously update the catalog data of published items from Sterling
Order Management System to Store Inventory
Management. Regardless of whether the catalog data is updated in
the Applications Manager or by using the
manageItem API, it is always
synchronized with Store Inventory
Order Management System also supports configuring the catalog data for a published item at the
store level, and it is synchronized with Store Inventory
Management as well. You can perform the task in
Applications Manager, from the Node Item Attributes screen or by using the
modifyItemNodeDefn API, and the change is synchronized with Store Inventory
While synchronous updates can automatically synchronize any addition, deletion, or modification of catalog data from Sterling Order Management System to Store Inventory Management, it does not update the catalog data that are already present in Sterling Order Management System before Store Inventory Management was deployed. To do this one-time synchronization, a Sterling Order Management System agent is provided to synchronize the complete catalog data from Sterling Order Management System to Store Inventory Management.
- Go to .
- Click the User Triggered tab. A sample agent criteria is provided:
- Create a copy of the criteria and rename it. For example,
- Configure the runtime properties such as Agent Server, JMS Queue, and Provider URL. You need not schedule this agent criteria.
- Start the agent server.
- Run the Trigger Agent server by entering the following information in
Agent criteria ID:
<Agent criteria id> -CatalogOrganizationCode <Catalog organization code configured on Sterling Order Management System> -TriggerUser <Valid user name to run the agent>
- It is assumed that as part of participant modelling in Sterling
Order Management System for a Store Inventory
Management customer, a single Catalog Organization owns all catalogs, which must be specified as
part of the Agent criteria ID. Additionally, a valid username is required to run the agent, even
though authentication is not necessary. For example, if the Catalog Organization is
XYZCorp, and username is admin, then pass the
following value as the Agent criteria Id:
SIM_ITEM_SYNC -CatalogOrganizationCode XYZCorp -TriggerUser admin
- If you want to run the
SIM_ITEM_SYNCagent regularly, configure it as a time-triggered agent by specifying the
TriggerUseras parameters in the Criteria Parameters tab in the Agent Criteria screen. For more information, see Specifying a transaction as time-triggered.
GETREST APIs for that product.
DELETEAPIs for products, unless explicitly instructed. You must update the product information only in Sterling Order Management System, and Store Inventory Management is updated synchronously. Using the
DELETEStore Inventory Management APIs can make the Store Inventory Management product data go out-of-sync with the Sterling Order Management System product data, and you must rectify the data by using the