Spend Management Blogs by Members
Check out community member blog posts about spend management and SAP Ariba, SAP Fieldglass, and SAP Concur solutions. Post or comment about your experiences.
Showing results for 
Search instead for 
Did you mean: 
Hello Everyone,

Welcome to my first blogpost on S/4 HANA(On-premise) integration with Fieldglass

The purpose of this blog post is to explain the general configuration steps required to set up the integration for SAP S/4 HANA(On-Premise) with SAP Fieldglass for Master data and Transactional data flow.


  • Key Benefits:


  • With S/4 HANA as digital core, Fieldglass external workforce management and service procurement are essential components of the digital transformation.

  • SAP Fieldglass as Vendor Management system designed to handle external workforce management and service engagements from identifying the external talent to manage the work with in the Organization.

  • Organizations running SAP S/4 HANA can take advantage of Standard productized integrations from SAP Fieldglass that connects external workforce and Services procurement activity and spend with key business process

  • Many clients utilizing SAP S/4 HANA Enterprise Resource Planning (ERP) may also utilize SAP Fieldglass to manage their contingent labor and external services activity and spend.

  • Since the SAP Fieldglass application is an offering within SAP’s product suite, the need for seamless connectivity(eg: via BTP-CPI) to be present is imperative and something that should be available for clients to easily implement and configure.


  • How can we setup integration between S/4 HANA and Fieldglass?


  •            With Direct Connectivity setup

  •            With Mediated Connectivity setup

  •            With Third-party(Add-on) integration


  • There are 3 Integration common deployment scenarios between S/4 HANA and Fieldglass


  • Scenario 1: Business Partner Integration with Relationships – Replicating Business Partner(vendors) from SAP S/4HANA to SAP Fieldglass via DRF(Data Replication Framework).

  • Scenario 2: Master Data Integration of Finance and Procurement data – Replicating master data from SAP S/4HANA to SAP Fieldglass

  • Scenario 3: Transactional Data Integration of Finance and Procurement data – Replicating transactional data from SAP Fieldglass to SAP S/4HANA


Business Partner Integration flow map

References:  https://help.sap.com/doc/00fb8d5a81ab4bccadcff55194e91cc4/cloud/en-US/SAPFieldglassandSAPS4HANAInteg...

SAP Business Partner Integration with Fieldglass

High level steps are as follows:

  • Business Partner created & saved in S/4 HANA ERP system.

  • Automated Direct Connectivity  integration initiates business partner push to SAP Fieldglass

  • Pass through optionally available via SAP Business Technology Platform.

  • Business Partner is loaded into vendor master object within the SAP Fieldglass application.

  • Administrator manually selects the supplier required to register based on the vendor data

  • Email invitation is distributed to the supplier to register and accept agreement.

  • After the supplier is invited and registered from the invitation, the Vendor Master record will be marked as registered, and no further invitations can be driven off it

  • SAP Fieldglass registered supplier can transact within the SAP Fieldglass network


Master Data integration flow map:

References: https://help.sap.com/doc/00fb8d5a81ab4bccadcff55194e91cc4/cloud/en-US/SAPFieldglassandSAPS4HANAInteg...

The following is the high-level summary of the implementation tasks associated with Master data integration:

  • Configure integration connectivity based on the direct connectivity or mediated connectivity integration method. The preferred method for both Cloud and On-Premise tenants is to utilize the SAP BTP mediated connectivity path and the standard developed integration flows for Master Data management, but both formats can be utilized based on the client’s configuration and/or preference.

  • In SAP Fieldglass, configure web services and enable integration connectors for the buyer company. Send related web services files and details to the client for configuration on the client’s system

  • Map fields for each of the master data objects(if required) supported by SAP Fieldglass and S/4 HANA. The mapping specifications for data imports are provided by SAP Fieldglass

Settings needed in S/4 HANA and BTP(CPI) systems for Fieldglass integration.

Reference: SAP S/4HANA integration with SAP Fieldglass (1L8)-Building Block Configuration Guide

Following are the settings required to be done from Functional and Technical SMEs, we need take help from SAP Fieldglass SMEs for the support on Fieldglass Parameter settings, End point setup.

Framework settings in S/4 HANA:

  •        Update credentials for Fieldglass in S/4 HANA


  •        Mediated connectivity settings for BTP (CPI)

Tasks like Certificate settings, CPI tenant settings, SOAMANAGER settings for Master data,              Transfer Services, Business Partner integration are needed

  •        Data Replication framework settings for replication- data framework settings are to be              added in Configuration

Exchange of information through S/4 HANA,CPI to facilitate quality reviews for Batch                      Record, Change Request and/or Customer Complaints.

       Application Specific settings in S/4 HANA:

  • Reference data Replication settings in S/4 HANA

Business system settings, Replication model with outbound implementation, Communication              channel settings, Outbound implementation for each Master data objects, Business                            transaction events, output control settings.

  •  Data Replication objects from S/4 HANA

Company code, GL account, Cost Center, WBS element, Internal order, GL account,                           Purchase Org, Plant, Business Partner objects can be replicated from S/4 HANA to Fieldglass

  • Interfaces setup in S/4 HANA, CPI and additional Fieldglass connectors setup for Master data


         SAP S/4 HANA Fieldglass Integration Services, Outbound Implementations

Following are the settings required to be done from Functional and Technical SMEs

Data Transfer technical Service settings are as follows:

  • The Service named CO_ARBFND_FG_PRX_DATA_TRF_OUT is for the data transfer consumer service to be deployed.


  • The service named CO_ARBFND_FG_PRX_DAT_BY_ID_OUT is for getting data by transaction ID consumer service to be deployed


  • Iflows in CPI landscape to be deployed with help of CPI SME and Integration connectors in Fieldglass to be enabled

Business Partner(Supplier) integration settings are as follows:

  • The Service named CO_MDG_BP_RPLCTRQ for Business Partner data replication to be deployed


  • The Service CO_MDG_BP_RELATIONSHIP_OUT for Business Partner relationship replication to be deployed


  • Iflows in CPI landscape to be deployed with help of CPI SME and Integration connectors in Fieldglass to be enabled

Master Data Transfer technical Service settings are as follows:

  • The Services named CO_PSWBSELEMENT_MASTER_DATA_RE, CO_BNSCOMPANY_CODE_MASTER_DATA,CO_BNSGLACCOUNT_MASTER_DATA_RE are to be deployed for WBS, Company code and GL account information with CPI-iflows


  • Outbound Implementations FG_CC, FG_IO, FG_PLANT, FG_PUR_ORG are to be implemented- If you want to replicate master data including cost center, internal order, plants and purchasing organization


  • Integration connectors in Fieldglass to be enabled for Master data elements.

Functional and Technical settings added are the starting point for the Integration setup between S/4 HANA and Fieldglass based on the Business scope requirements.

Above information added in this Blog post will give more details, guidance always for the SMEs during S/4 HANA and Fieldglass integration work. As the integration of Fieldglass-S/4 HANA is key to success of deployments, we can save time by referring the blog post.

I will continue to add more details to Fieldglass-S/4 HANA integration blog.

Please give your feedback on my blog post in the comments section.




Nagesh Srinivasappa
1 Comment