The configuration of connections to the Managed Gateway for Spend&Network involves setting up outbound and inbound proxies through SOAMANAGER. This enables supplier data exchange and confirmation messages between SAP Ariba SLP and either SAP ERP, SAP S/4HANA (on-premise), or SAP MDG-S.
The Managed Gateway Add-On package streamlines the programmatic creation of these necessary outbound and inbound proxies using the Interface Setup program under the General Settings configuration activities. You can install the Managed Gateway Add-On on your SAP system, which will configure the following proxies when you run the Interface Setup program:
- SLP Outbound Request: This proxy sends Supplier/BP data from the SAP system to SAP Ariba SLP.
- SLP Confirmation In Request: This proxy receives confirmation from SAP Ariba SLP regarding the supplier data request sent from the SAP system.
- SLP Inbound Request: This proxy receives supplier data requests from SAP Ariba SLP and sends them to the SAP system.
- SLP Confirmation Out Request: This proxy sends confirmations from the SAP system in response to supplier data requests received from SAP Ariba SLP.
For detailed instructions on executing the Interface Setup program, refer to the course Configuring General Settings in Managed Gateway for Spend and Network Add-On, which is part of the Learning Journey Administering SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network.
While it is recommended to install the Managed Gateway Add-On for optimal configuration, doing so is not mandatory. You can manually manage configurations using the appropriate transaction codes (TCodes) in your SAP system.
If you plan to send supplier or business partner (BP) data to multiple cloud systems from your SAP system, refrain from using the automatic outbound creation option. In the Interface Setup Program for SAP Ariba Strategic Sourcing, ensure that you select only the checkboxes for "SLP Inbound Request" and "SLP Confirmation In Request." The inbound proxies will still be configured automatically by the Interface Setup Program. For instructions on configuring the outbound proxy, please refer Integrating SAP Master Data Governance (MDG) with Ariba Supplier Lifecycle and Performance (SLP) without using Default Logical Port on SAP S/4HANA.
As a best practice, SAP Ariba doesn't recommend using custom generic fields as they require additional customization in SAP ERP, SAP S/4HANA (on-premise), or SAP MDG and custom implementation on a case-to-case project basis.
However, SAP Ariba Supplier Management solutions integration with SAP ERP, SAP S/4HANA, or SAP MDG supports the extension of the business partner data structure to enable you to use custom fields to address your specific requirements. These extensions are only supported in solutions where bidirectional integration is supported.
If you don't use SAP Process Integration (PI), SAP Process Orchestration (PO), or a System Landscape Directory (SLD) to maintain the data type enhancements to customize the fields for SAP Ariba Supplier Lifecycle and Performance integration, refer to the steps described in the SAP Integration Suite, Managed Gateway for Spend Management, and SAP Business Network Configuration Guide. Navigate to:
Working with Master Data>Configuring Supplier Data Integration with SAP Integration Suite, managed gateway for spend management andSAP Business Network>Configuring Supplier Data Integration>Configuring SAP ERP>Customizing the Fields for SAP Ariba SupplierManagement solutions Without a Middleware section.
For those who use SAP Process Integration (PI), and SAP Process Orchestration (PO), to address their customization requirements, refer to the information in the SAP Integration Suite, Managed Gateway for Spend Management, and SAP Business Network Configuration Guide. Navigate to:
Working with Master Data>Configuring Supplier Data Integration with SAP Integration Suite, managed gateway for spend management andSAP Business Network>Configuring Supplier Data Integration>Configuring SAP ERP>Configuring SAP Process Integration section.