Build a Supply Risk API with API Composition

Before creating the Business Data Graph, configure four HTTP destinations in your SAP BTP subaccount. Each destination points to one of the publicly hosted mock APIs as mentioned below:

Repeat the steps below for each destination.

From SAP Integration Suite, click the grid icon (⠿) in the top-right navigation bar and select SAP BTP Cockpit.

In the BTP Cockpit, go to your subaccount. In the left sidebar, navigate to Connectivity → Destinations and click Create.

Fill in the following fields, then click Save.

Under Additional Properties, add:

The IntegrationCell.Include = true additional property is required to make the destination visible in the Integration Cell runtime. Without it, the destination will not appear when selecting data sources for a Business Data Graph.

In SAP Integration Suite, go to Design → Business Data Graphs.

Click Create → New business data graph.

Fill in the details in the creation dialog:

Under Data Source Destinations, select all four destinations:

• LocationRisk
• S4_API_MATERIAL_STOCK_SRV
• S4_sap-s4-ce-plant-0001-v1
• s4hana_api_business-partner

Click Next.

On the Model Extension screen, leave Model Extension as Select a Model Extension (you will link it in Step 7), and keep Enable OData Containment checked.

Click Next.

SAP Integration Suite will connect to each destination and analyze the data landscape. Wait until all destinations show a green Success status.

Click Next, then click Done.

You will land on the Overview page of your Business Data Graph in Draft status.

The bestrun namespace will appear in the Schema after you link the Model Extension and re-activate the Business Data Graph in Step 7.

Click Activate at the bottom of the page.

The status changes to Available and the Overview page shows the generated URLs.

You will copy the final OData URL after re-activating the Business Data Graph with the Model Extension in Step 7. That is the URL to use in your MCP Server configuration.

A Model Extension allows you to extend or customize the schema of your Business Data Graph.

From the Business Data Graphs page, click Model Extensions (top-right).

Click Create → New Model Extension

fill in the details:

From the Model Extension detail page, click the Custom Entities tab. Click Create a custom entity.

Name

Fill in the details:

Click Next.

Source Entities

Set the Main Source Entity to my.custom.Plant.

Click Add under Additional Source Entities and configure each as follows:

Additional Source Entity 1

Additional Source Entity 2

Both additional sources are now listed. Click Next.

Attributes

Select the attributes from each source entity as shown. Use the Add as column to rename the attribute in the custom entity schema.

my.custom.Plant (Main Source Entity)

my.custom.AddressRisk (many — composition name: addressRisks)

sap.s4.A_MatlStkInAcctMod (many — composition name: matlStkInAcctMods)

Click Create.

The attributes selected above reflect the fields relevant to the plant supply risk use case. In a real implementation, select attributes based on your own business requirements.

Apply and Save

After clicking Create, you land on the Custom Entity detail page. Click Apply to confirm.

You are returned to the Model Extensions page where bestrun.assessment now appears in the Custom Entities list. Click Save.

Navigate to Design → Business Data Graphs and open plantsupplyrisk.

After opening, the graph status changes to Draft. Linking a Model Extension is a configuration change that requires a fresh activation cycle.

Click the Model Extensions tab, then click Edit followed by Add a Model Extension.

Click on Add a Model Extension

In the Edit Model Extensions dialog, select plantsupplyrisk and click Apply.

Click Activate.

Click on Update

The status returns to Available and the bestrun namespace now appears in the Schema. Copy the OData URL from this page — you will need it when configuring the MCP Server in the next tutorial.

Click the grid icon (⠿) in the top-right and select API Composition Navigator.

Click on plantsupplyrisk.

In the left panel, expand the bestrun (1) namespace and click assessment. The entity overview shows the source entities and connected navigation properties. Click OpenAPI Specification to download the spec file — you will need this in the next tutorial.

Click the Try Out tab. Click $expand and check both addressRisks and matlStkInAcctMods. The query updates to:

/bestrun/assessment?$top=1&$expand=addressRisks,matlStkInAcctMods

Click Run.

The response returns a 200 OK with a live plant record showing the composed structure — plant details, expanded address risks with riskScope, and material stock records with matlWrhsStkQtyInMatlBaseUnit:

{
  "@odata.context": "$metadata#assessment(addressRisks(),matlStkInAcctMods())",
  "value": [
    {
      "id": "my.custom~0010",
      "plantName": "Berlin",
      "addressRisks": [
        {
          "addressId": "4678045",
          "riskFactor": "ground transport interruption",
          "riskCategory": "low",
          "riskScore": "0.1",
          "riskTrend": "increasing",
          "riskScope": "local"
        }
      ],
      "matlStkInAcctMods": [
        {
          "material": "Brake Pad",
          "storageLocation": "0010",
          "batch": "612912",
          "supplier": "Windmill Components",
          "customer": "",
          "wbsElementInternalID": "",
          "sdDocument": "4",
          "sdDocumentItem": "5",
          "inventorySpecialStockType": "2",
          "inventoryStockType": "4",
          "matlWrhsStkQtyInMatlBaseUnit": 10
        }
      ]
    }
  ]
}

You have successfully built a unified supply risk API. The OData URL and OpenAPI Specification from this tutorial are the inputs for Create an MCP Server for Enterprise AI Agents.