App Connect

Using IBM® App Connect to interact with IBM® Supply Chain Intelligence Suite

By Shahmini Arumugam posted Wed September 01, 2021 12:05 AM

  


IBM Supply Chain Intelligence Suite is an open, integrated platform that easily connects to your supplier ecosystem. It helps you to establish end-to-end visibility and real-time insights by using advanced technologies like AI and blockchain.

Using IBM Supply Chain Intelligence Suite with IBM® App Connect

You can use App Connect to perform actions on the following objects:

  • Catalogs
  • Demand plans
  • Inventories
  • Orders
  • Products

Building a flow in App Connect with IBM Supply Chain Intelligence Suite

You can now use IBM App Connect to build flows that integrate with IBM Supply Chain Intelligence Suite and other applications. The connector is displayed as IBM Supply Chain Intelligence Suite on the IBM App Connect User Interface (UI).

Provide the following information to connect App Connect to your IBM Supply Chain Intelligence Suite account.

Required credentials Description
Host URL The IBM Sterling Supply Chain Suite GraphQL service URL.
Client ID The unique identifier of IBM Sterling Supply Chain Suite. Get the client ID key from your IBM Sterling Supply Chain Suite account user interface.
Client secret The client secret key for the unique identifier of your IBM Sterling Supply Chain Suite account. Get the client secret key from the IBM API Explorer site; log in with your IBM Sterling Supply Chain Suite account credentials.
Tenant ID The unique tenant ID of the IBM Sterling Supply Chain Suite instance.


Scenario: Orders ingestion to IBM Supply Chain Intelligence Suite from Microsoft Dynamics 365

Consider this scenario where you use App Connect to create a scheduler-based flow that retrieves orders from Microsoft Dynamics 365 Customer Relationship Management (CRM), sets unique global IDs for each of the orders and concatenates these IDs into an array as CRM identifiers. For each of the CRM ID arrays, it outputs the global IDs as name and value pairs to be uploaded to the IBM Supply Chain Intelligence Suite.


For this scenario:

  1. You run a scheduler-based flow that retrieves orders.
  2. The Microsoft Dynamics 365 for Sales Retrieve orders operation fetches the orders from Microsoft Dynamics 365 CRM.
  3. The flow includes a For each conditional statement node to process each of the orders.
    • A Set variable node is added to the conditional statement node to set the global identifiers for each order that is retrieved from the Microsoft Dynamics 365 CRM system.


               The following are the global identifiers that are defined as name-value pairs in strings.

    • Order ID

    • Order name

    • Created on

     
    Global identifiers are required by IBM Supply Chain Intelligence Suite.


    • The second Set variable node is added to concatenate the global identifier strings into an array as CRMIdentifiers for each of the orders.

    • A For each conditional statement node is added to process each of the CRMIdentifiers. For each string array, it generates the output of the global identifiers as name-value pairs.


            4. The IBM Supply Chain Intelligence Suite upsert operation creates and uploads the order’s global identifiers of the CRMIdentifiers arrays as name-value pairs to the Supply Chain Intelligence Suite.

                  The IBM Supply Chain Intelligence Suite accepts only the global identifiers as a name-value format to be stored in its system.                                 

                  For example, the following is the output from the GraphQL tool.



     

    You can opt to add a response payload from IBM Supply Chain Intelligence Suite to a dedicated Slack channel to list all the retrieved order IDs.


    To summarize, this scenario helps a user to retrieve multiple global identifiers of an order from a Microsoft Dynamics 365 CRM system and ingest these global identifiers as name-value pairs to the IBM Supply Chain Intelligence Suite.



    IBM® App Connect supports a wide range of data formats, application infrastructures, and integration styles. For more information, see IBM® App Connect connectors.

     

    Permalink