Data feed types overview

The IBM® Sterling Intelligent Promising optimization process relies on transaction and configuration data feeds to train the AI model to customize optimisation for your organization. Data input is accepted in CSV file format. As part of the file ingestion pipeline, it is mandatory that data is in a standardized format where column order and data type are crucial to successful data ingestion. For complete data ingestion, you must ensure that all defined data feed types are configured with data flowing into the system.

Ensure that you configure the endpoints for file ingestion. For more information, see Configuring endpoints for file ingestion rules.

For IBM Sterling Intelligent Promising to process files that are uploaded to your IBM Cloud Object Storage bucket, you must provide the following information to IBM:
    • Bucket name.
    • Prefix of the file location where your files are stored.
    • Endpoint URL for your IBM Cloud Object Storage service instance.
    • Region or geographical location of your service instance.
    • HMAC keys for IBM Cloud Object Storagewith sufficient privileges to perform these operations on files:
      • List
      • Read
      • Download
      • Upload
      • Copy
      • Delete

If you are managing your inventory by using Inventory Visibility, you don't need to upload supply or availability data. However, if you manage your data by using an external system, you must configure all the various data types.

Transactional data types

The transactional data types contain order information. Each time an order is created, modified, or deleted, the content type must be updated to reflect the new changes. Depending on your setup, some data feed types are not required. For example, if you are using the catalog service API to maintain your catalog data, you don't need to upload catalog item data.
Transaction log data type:
Required: To predict the stock out and markdown avoidance patterns.
Data capture methods: File-based upload. For more information, see Transferring T-log data.
contentType: TLOG
Markdown data type:
Required: To predict the stock out and markdown avoidance patterns.
Data capture method: File-based upload. For more information, see Transferring markdown data.
contentType: MKC
Order line status
Required: To determine stock out and markdown avoidance.
Data capture method: File-based upload. For more information, see Transferring order line status data.
Catalog item
Required only if you are not using the Catalog service: To transfer item data from an external system to IBM Sterling Intelligent Promising.
Data capture method: File-based upload. For more information, see Transferring catalog item data.
Availability
Required only if you are not using the Inventory service: To determine stock out possibilities.
Data capture method: File based-upload. For more information, see Transferring availability data.
Supply plan
Required only if you are not using the Inventory service: To determine when the inventory is replenished.
Data capture method: File-based upload. For more information, see Transferring supply plan data.