Publish inventory availability details
Orders that are placed with Adobe Commerce are fulfilled by Sterling Order Management System, and the inventory availability at the ShipNode level is published from Sterling Intelligent Promising Inventory Visibility to Adobe Commerce. The inventory availability information that is published from Sterling Intelligent Promising Inventory Visibility is used to refresh the cache in Adobe Commerce and the availability is displayed in the product details page.
The integration supports publishing of the inventory availability details from Sterling Intelligent Promising Inventory Visibility and not from IBM Sterling Global Inventory Visibility. The integration publishes the full availability snapshot from Sterling Intelligent Promising Inventory Visibility to Adobe Commerce.
Prerequisites
You must provision a separate IBM Cloud Object Storage bucket for each event to push the inventory availability details from Sterling Intelligent Promising Inventory Visibility to Adobe Commerce.
You must subscribe to events in Sterling Intelligent Promising Inventory Visibility and verify that the events are published to IBM Cloud Object Storage. For more information, see Event subscriptions.
You must map the source and stock levels in Adobe Commerce with ship nodes and distribution groups in Sterling Intelligent Promising Inventory Visibility. For more information, see Mapping for inventory details.
Agents for pushing inventory details
Inventory Publish, an asynchronous interface, uses the IAC_IV_INVENTORY_TRIGGER
and IAC_IV_INVENTORY_PUBLISH agents to publish the inventory details from Sterling Intelligent Promising Inventory
Visibility to
Adobe Commerce.
You must set separate schedules in the Self Service tool to start the
IAC_IV_INVENTORY_TRIGGER and the IAC_IV_INVENTORY_PUBLISH agent
servers. Ensure that you schedule the servers to start at an interval of minimum half an hour.
For example, if you schedule IAC_IV_INVENTORY_TRIGGER to run daily at 12:00 AM,
you might schedule the IAC_IV_INVENTORY_PUBLISH agent server for 12:30 AM. This is
to ensure that the files are loaded into the IBM Cloud Object Storage bucket before they can be
processed.
IAC_IV_INVENTORY_TRIGGERThe
IAC_IV_INVENTORY_TRIGGERagent run per the pre-defined schedule or on-demand and triggers the publish_all Sterling Intelligent Promising Inventory Visibility REST API for all the ShipNodes of Sterling Intelligent Promising Inventory Visibility. This API then publishes theProductAvailabilityToSell.ShipNodeSnapshotevents for all ShipNodes to the IBM Cloud Object Storage bucket.IAC_IV_INVENTORY_PUBLISHTheIAC_IV_INVENTORY_PUBLISHagent reads the published files from the IBM Cloud Object Storage bucket, transforms the data into the Adobe Commerce format, and calls the Adobe CommerceInventory UpdateAPI to publish the inventory availability status. TheInventory Update (Source-Items)API is called by using theBulkasynchronous end point of Adobe Commerce.
For more information, see Bulk endpoints.http://<host>/magento2/rest/async/bulk/V1/inventory/source-itemsNote: TheIAC_IV_INVENTORY_PUBLISHagent runs only in the full sync mode. For more information about the full sync mode, see Full sync mode.
Service for publishing inventory details
You must use the IACInventoryUpdate service to publish inventory details from
Sterling Intelligent Promising Inventory
Visibility to
Adobe Commerce.
The IACInventoryUpdate service uses the IACValueMaps.xml to map
ship nodes in Sterling Intelligent Promising Inventory
Visibility to sources in
Adobe Commerce.
You can customize the IACValueMaps.xml for mappings between Sterling Intelligent Promising Inventory Visibility and Adobe Commerce. For more information, see Configuring IACValueMaps.xml.
The IACInventoryUpdate service converts the Sterling Intelligent Promising Inventory
Visibility messages to the
Adobe Commerce messages and prepares the bulk payload. The total
number of payloads in a bulk payload is based on the value set for the
iac.integration.inventory.payloadinbulk.count property. The default value is 20.
This service is used to make a REST API call to
Adobe Commerce with bulk
payload.