SAP Integration Suite – Connect Everything FEATURING Coupa

[FrederickDimmer]

Introduction

Welcome to another insightful edition of our "SAP Integration Suite – Connect Everything" blog series. In this post, we focus on unlocking the potential of connecting Coupa, a leading cloud-based spend management solution, with your enterprise’s existing ecosystem using the SAP Integration Suite. As organizations strive for operational efficiency and superior financial management, integrating Coupa seamlessly with other enterprise applications has become a strategic priority.

The SAP Integration Suite offers a robust, cloud-based platform designed to facilitate secure and efficient connections between SAP and non-SAP systems alike. Through a detailed exploration of technical setups and best practices, this article will guide you on how to effectively implement Coupa integration, enabling streamlined procurement processes and enhanced data visibility across your enterprise landscape.

Join us as we uncover the possibilities of creating a unified, interconnected system that empowers your business to achieve new heights of innovation and performance.

Pre-Requisites

In this blog, we dive into the seamless integration using the Coupa Adapter for SAP Cloud Integration Suite. Keep in mind that access to this adapter hinges on the specifics of your SAP Integration Suite service plan. For a detailed breakdown of service plans and what features they support, check out SAP Notes 2903776 and 3188446. Additionally, the adapter documentation serves as a valuable resource for further insights into the adapter.

Integration Scenario

The integration of suppliers from SAP S/4HANA to Coupa is an essential process for organizations that rely on SAP for enterprise resource planning and Coupa for spend management. By replicating supplier data automatically, companies can ensure consistency across both platforms, enhancing procurement processes and supplier relationship management.

In this integration setup, suppliers from SAP S/4HANA are replicated to Coupa, allowing businesses to have synchronized supplier records. The replication process is facilitated through the SAP Integration Suite, which manages the transfer and transformation of data between the systems. A scheduled job within Cloud Integration retrieves updated or newly created supplier records from SAP S/4HANA, then processes and reformats these records to comply with Coupa’s requirements. If no new changes are detected, the process concludes; otherwise, the transformed supplier data is sent to Coupa, where new supplier entries are created or existing entries are updated.

This seamless replication of suppliers ensures that procurement teams have accurate and updated supplier information in Coupa, streamlining operations, reducing manual data errors, and fostering better supplier communications.

High Level Architecture

Remarks for Coupa Integration

The integration between SAP S/4HANA and Coupa can be tailored to fit the specific needs of your business. It is recommended that you adapt the process to align with your unique operational requirements. Modifications may be applied across several components, including:

• Tweaking the externalized parameters in the integration flow,
• Making changes to the Coupa configuration,
• Adjusting the mapping step to incorporate any custom properties within Coupa.

If the standard tables in Coupa have been altered to include custom fields, it is necessary to generate XSD files using the Eclipse Plug-in. These XSDs should then be uploaded to the Integration Flow, and the mapping should be adjusted accordingly.

To install the Adapter, please consult section 2.4 of the Coupa Adapter for SAP Integration Suite documentation.

Remarks for SAP S/4HANA Service Oriented Architecture Setup

SAP provides a range of output configuration patterns via its Service-Oriented Architecture (SOA), tailored to streamline web service management across different systems. These patterns include single or manual web service configuration, central configuration, and local configuration, each offering unique features and benefits.

Single or Manual Web Service Configuration:

In SAP, single or manual web service configuration is managed through the transaction SOAMANAGER -> Web Service Configuration. This approach allows for individual consumer proxies to be configured separately, providing detailed control over specific web services. It's a straightforward method suitable for systems with minimal integration requirements or where individualized configuration of web services is preferred.

Central Configuration:

Central configuration represents a more holistic approach, diverging from the singular focus on individual consumer proxies. Instead, central configuration involves setting up service groups—ABAP Web service design-time objects that encompass a collection of consumer proxies configured with uniform settings. This method is characterized by the presence of a central or managing system that coordinates multiple managed systems. Key aspects of central configuration include:

• Business Scenario Management: A comprehensive business scenario is maintained in the central system, integrating all connections across involved systems.
• Service Registry Role: The central system acts as a service registry, publishing endpoints within the business scenario and facilitating the creation of logical ports using endpoint-WSDLs.
• Task Processing Efficiency: The central system's change processor efficiently manages task sequences across managed systems with a single trigger upon scenario release.

Local Configuration:

By contrast, local configuration also deals with service groups but disperses the management of scenarios across all involved systems. The local configuration requires manual setup and coordination in each system, emphasizing individualized system controls.

Differences between Local and Central Configuration include:

• Scenario Management: In local configuration, scenarios are distributed across systems; in central configuration, scenarios are centrally maintained.
• Service Access Creation: Local configuration requires manual creation of WSIL/WSDL access; central configuration automatically generates access within domain systems.
• Task Processing: Local configuration processes tasks individually for each system, often repetitively; central configuration relies on a single, scenario-based task processing sequence managed centrally.
• Profiles and Scenarios Setup: Local configuration demands manual creation across systems with consistent naming; central configuration manages this centrally and ensures distribution.
• Service Definition Matching: In local configuration, service definition matching is achieved through related and matching interfaces; central configuration utilizes the Central Determination Tool for Consumer (CDTC) for matching, based on thorough operation comparison on both inbound and outbound sides.

Overall, SAP’s diverse configuration patterns through SOA enable organizations to choose the best-fitting strategy for their web service needs, ensuring flexibility, efficiency, and scalability. For more detailed technical guidance, SAP Note 2933829 provides in-depth information on implementing central management using SOAMANAGER.

Setup Instructions

Configuration in SAP S/4HANA

The instructions are designed around a local configuration pattern approach, focusing on integrating your local system landscape with an external, non-ABAP third-party system. Leveraging SAP S/4HANA’s robust integration features, you will be equipped to establish foundational connectivity, ensuring seamless information exchange and data consistency. For those interested in more advanced configuration strategies, SAP Note 2985701 provides extensive guidance on using both local and central configurations with external systems.

Access the SOA Management of the SAP S/4HANA system via transaction SOAMANAGER. Navigate to the Technical Administration section and select Profile. Select Create Profile and enter a name for the profile and select Next. Set the Transport Layer Security settings to SSL, set the Authentication Method of choice e.g. User ID/Password and select Next. To finalize the Profile setup select Finish.

After creating the Profile navigate back to the Technical Administration and select Provider Systems. Navigate to the Create Special drop-down list and select Create Third Party System. Set Name for the profile and assign the previously created Profile and select Next. Switch the WSIL access from HTTP to HTTPS by selecting Switch to HTTPS. Assign a user for the WSIL access and validate the successful access via the Check button. User creation and authorization assignment is not part of this blog post. Finalize the setup by selecting Finish.

Once the external provider system is set up, you can upload the endpoint WSDLs from the external system. The prebuild SAP Integration Suite, Cloud Integration scenarios for the Coupa integration do not utilize WSDL in the sender channel. Consequently, the WSDL obtained from the runtime node endpoint is generic and cannot be directly uploaded into SOAMANAGER. To address this, the WSDL must be manually modified. To download the WSDL definition navigate to transaction SE80. Navigate to package MDG_BS_BP_XI_PROXY. Select Enterprise Services and choose the Service Consumer CO_MDG_BP_RPLCTRQ. Download the service definition by navigating to the WSDL tab and select the "Save to file …" button.

Launch a text editor and load the WSDL file. Insert a binding element WSDL. Then, under this binding, add an operation with a SOAP action. Afterwards, create a service element that utilizes the binding details you just established. For the SOAP address, set the SAP Integration Suite, Cloud Integration runtime URL for the iFlow.

Head over to SOAMANAGER. Go to the Technical Administration menu and select Provider System. Select the previously created Provider System. Navigate to the WSDL assignments menu and select Upload button. Upload the previously created file and select Next. Hence no further changes are required navigate with Next through the following menu tabs and save the results by selecting Confirm.

The system supports WSIL access, containing these uploaded endpoint WSDLs. While processing pending tasks, this WSIL is used to obtain the relevant WSDL for the corresponding logical port. It's vital to remember that each external provider system corresponds to exactly one external system. Ensure you upload endpoint WSDLs from a single system to each external provider system only. If your scenario involves multiple external non-ABAP systems, you'll need to create a separate external provider system for each one. If your scenario involves multiple ABAP systems connected to the external system, this setup must be replicated for each ABAP system (create the external provider system and upload the endpoint WSDLs).

Set up the Logon Data and ensure it's activated. You can do this by navigating through Service Administration to reach Logon Data Management. Select Create within the Maintenance tab in the Logon Data section. Enter a Logon Data Name and select Next. Select the authentication method e.g. User/Password or X.509 set the access details and select Finish.

Set up a local integration scenario by configuring the integration parameters by navigating to the Service Administration menu and selecting the Local Integration Scenario Configuration. Start the setup via the Create button. Set the scenario name and select Next. Hence for the Coupa supplier integration scenario no Service Definitions are required nothing needs to be configured in the second step. Therefore select Next to head to the Service Group configuration. Select Add and choose the Service Group Object MDG_BP_REPLICATEREQ. As a next step assign the IBC reference that has been created through profile by selecting the Assign IBC Reference button assign the previously created profile and select Next. In the Logon Data Assignment section assign the previously created Logon Data and select Finish. Activate the Local Integration Scenario in the following dialog.

Upon activation of the Integration Scenario, the system unveils a link enabling you to configure and activate consumer proxies via Pending Tasks. Alternatively, you can navigate to Service Administration, then proceed to Pending Tasks. Select Process List and validate successful execution.

Ensure the BC switch BSSOAV_WS_ACTIVE is enabled within the IMG (SPRO transaction). This activation is essential for the DRFOUT process to utilize the service group configuration effectively.

DRFOUT relies on the DRFIMG settings for its operations. To transmit data to the provider systems via the logical ports established in SOAMANAGER, it is necessary to adjust two specific elements within the DRFIMG configuration. Select New Entries and provide a Data Replication Model name. Select the previously created record and navigate to the Assign Outbound Implementation. Add configuration 986_3 with Communication Channel Replication via Services. Select the configuration and navigate to Assign Target Systems for Repl. Model / Outb. Impl. Assign the previously created Provider System as the Business System Name.

Configuration in Coupa

This integration package SAP S/4HANA Integration with Coupa makes use of OAuth Authentication for the integration with Coupa. For detailed instructions on setting up OAuth, refer to section 9.1, Initialize OAuth Setup in Coupa, found in the Coupa Adapter for SAP Integration Suite Guide. The guide is available via the SAP Buisness Accelerator Hub.

Configuration in SAP Integration Suite

To utilize the Coupa adapter within the Cloud Foundry setup, it's essential to first deploy it on the SAP Cloud Platform Integration tenant. For successful deployment, ensure that you possess the necessary privilege to "Coupa Adapter for SAP Integration Suite" included in your SAP Integration Suite license.

The adapter can be copied via the Discover section of your SAP Integration Suite instance.

Install the duplicated adapter from the Design section.

After deployment, the adapter becomes ready for use in integrating Coupa as the receiver. For the specific scenario of supplier replication, SAP has introduced the readily deployable IFlow named "Replicate One-To-One Suppliers From SAP S4HANA To Coupa." This integration flow is designed to streamline the synchronization of supplier data between SAP S4HANA and Coupa, ensuring a seamless transfer of information with minimal configuration effort.

In order to copy the integration to your instance navigate to the Discover section and search for "SAP S/4HANA Integration with Coupa". Select the package and copy the content to your instance.

After copying the content to your instance go to the Design menu and select the previously copied package, navigate to the artifacts section and start configuring the "Replicate Supplier from SAP S4HANA to Coupa one-to-one" flow. Once opened, select the 'Configure' option. Proceed by setting up the Sender, ensuring to assign an endpoint to the integration flow that aligns with your organization's naming conventions.

Proceed by navigating to the Receiver section. Subsequently, set up the Receiver connector to Coupa, tailoring it to suit the specific requirements of your landscape.

Effective exception handling is crucial in productive environments as it ensures smooth and uninterrupted operations by managing and resolving unexpected errors. Within the IFlow, there is support for customizing error handling processes, allowing organizations to tailor responses to potential issues. This customization is accessible through the Receiver connector named Email_Handler, enabling tailored notifications and resolutions based on specific error conditions. However, it's important to note that the intricacies of setting up these customizations will not be detailed within this blog post, as the focus is on broader integration concepts.

After finalizing the customizing save and deploy the IFlow. In order to check for successful deployment navigate the Monitoring section. Select Manage Integration Content, search for the previously deployed artifact and validate the status.

Execute Integration Scenario

After setting up the integration this section will explain how to run the scenario. Start by navigating to transaction DRFOUT. Select the Replication Model created previously. Maintain the Outbound Implementation and choose the Replication Mode. For demonstration purposes the blog will make use of the Manual replication. Moving forward with the Manual mode enables selecting a business partner of preference. To select the business partner select Manual Replication Filter Criteria. To test the output select Test Run Only and after successful execution execute the replication.

After successful replication navigate to the SAP Integration Suite, Cloud Integration capability, navigate to the Monitoring menu, go to the Monitor Message Processing section and validate successful transmission state.

The final step is the validation of the data within Coupa. Navigate to the Supplier menu. Use the inbuild filter criteria to search the previously transmitted supplier. To validate select the newly supplier and checking the master data.

Conclusion

In conclusion, integrating Coupa with SAP S/4HANA using the SAP Integration Suite represents a strategic enhancement for enterprises seeking streamlined procurement processes and superior spend management capabilities. Through this advanced connectivity, organizations can ensure consistent and up-to-date supplier information, reducing manual data errors and fostering improved supplier relationships. The SAP Integration Suite, with its robust platform and Coupa Adapter, provides the necessary tools and flexibility to tailor integrations based on specific business needs, allowing for the adaptation of parameters, configurations, and mappings to suit unique operational environments.

As we have explored in this blog, leveraging the SAP Integration Suite for Coupa integration not only enhances data visibility and operational efficiency but also enables enterprises to unlock new possibilities in innovation and performance. By replicating supplier data and synchronizing records between SAP and Coupa, businesses can achieve a unified, interconnected system that empowers procurement teams to operate more effectively.

Organizations are encouraged to explore the full potential of this integration by consulting the Coupa Adapter documentation and SAP Notes for comprehensive insights and guidelines. With a strategic approach to integration, companies can elevate their financial management and procurement operations, positioning themselves for success in an increasingly digital and interconnected business landscape.

Thank you for joining us in this edition of the "SAP Integration Suite – Connect Everything" blog series. Stay tuned for more insightful discussions and technical deep-dives into SAP integration topics that drive enterprise innovation and growth.