Docs / Connectors / mysupply

mysupply Connector

The ASAPIO connector for mysupply links SAP purchase requisitions directly to the mysupply sourcing platform. PR items flagged with a blocked indicator are transferred to mysupply — individually or in batch — where sourcing takes place. Once a deal is closed in mysupply, the connector writes the awarded price and vendor back into the SAP purchase requisition automatically.

This connector is configured via SAP GUI only. Event Studio is not supported.

Overview

Prerequisites

• ASAPIO Integration Add-on – Framework installed
• ASAPIO Integration Add-on – Connector for mysupply installed
• Access to the mysupply Demand API (API key required)
• Access to the mysupply frontend
• SSL certificate from mysupply.io available for import

SAP Connection Setup (in SAP Gui)

Step 1: Import SSL Certificate (STRUST)

Export the SSL certificate from mysupply.io and import it into SAP via transaction STRUST.

Step 2: Create RFC Destination (SM59)

Create a type G (HTTP connection to external server) RFC destination:

• Target Host: test-api.mysupply.io (or production equivalent)
• Port: 443
• SSL: Active

Step 3: Create Connection Instance (SPRO)

Navigate to SPRO → ASAPIO Integration Add-on → Connector for mysupply. Create a new connection instance and link it to the RFC destination created above.

Step 4: Set Cloud Connection Password

Enter the mysupply API key as the Cloud Shared Secret on the connection instance.

Outbound Configuration

The outbound flow reacts to create and change events on purchase requisition items (SAP business object BUS2105). When the blocked indicator on the PR item matches the configured value, the item is sent to the mysupply Demand API.

Outbound Object: PREQ_MYSUPPLY

Event Linkage (SWE2)

Create an event linkage for business object BUS2105, event CHANGED, with receiver function module /ASADEV/ACI_EVENTS_TRIGGER.

Inbound Configuration

A scheduled ASAPIO job polls the mysupply Demand API for closed deals. For each closed deal, an IDoc is created and post-processed to write the awarded values back into the SAP purchase requisition and remove the blocked indicator.

Step 1: Create Message Type (WE81)

Define a new message type for the mysupply inbound IDoc.

Step 2: Link Message Type to IDoc Type (WE82)

Link the message type to IDoc type /ASADEV/ACI_GENERIC_IDOC.

Step 3: Assign Processing Function Module (WE57)

Assign processing FM /ASADEV/INB_DEAL_MYSUPPLY to the message type.

Step 4: Register Function Module (BD51)

Register the inbound processing FM in the IDoc function module table.

Step 5: Create Process Code (WE42)

Create an inbound process code linking the message type to the processing FM.

Step 6: Create Partner Profile (WE20)

Create an inbound partner profile. Default logical system: LOCAL.

Field Mapping

Outbound: PR to mysupply Demand

Inbound: mysupply Deal to PR

Known Restrictions

• Multiple changes to the same PR item create multiple mysupply demands.
• Price unit (EBAN-PEINH) must remain unchanged after transfer.
• Purchase requisitions cannot have a fixed vendor pre-assigned before sending to mysupply.
• Additional custom fields can be added via the Payload Designer.

Enhancements (BAdI)

The following BAdI implementations are available for custom logic:

• MAP_DEAL_FROM_IDOC_SINGLE
• MAP_DEAL_FROM_IDOC
• CHANGE_PR_DATA_BEFORE_POST
• CUSTOM_POST
• CHANGE_RUNTIME_PARAMETER