Scribd
Upload
144 views3 pages

INTERFACE

This document summarizes the integration of Salesforce and SAP via MuleSoft. It involves 4 steps: 1) Establishing connections between MuleSoft and SAP systems. 2) Implementing an external package in SAP consisting of data elements, tables, functions, transactions, and enhancements. 3) Configuring the interface in SAP. 4) Using function modules and BAPIs to support processes like creating sales orders and timesheets that are exchanged between the systems.

Uploaded by

susmita jena
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
144 views3 pages

INTERFACE

This document summarizes the integration of Salesforce and SAP via MuleSoft. It involves 4 steps: 1) Establishing connections between MuleSoft and SAP systems. 2) Implementing an external package in SAP consisting of data elements, tables, functions, transactions, and enhancements. 3) Configuring the interface in SAP. 4) Using function modules and BAPIs to support processes like creating sales orders and timesheets that are exchanged between the systems.

Uploaded by

susmita jena
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Interface between FSL and SAP via MuleSoft

This is an integration of Salesforce and SAP via MuleSoft interface. The service order is created in FSL
which in turn create a sales order in SAP without any line items and with required fields (as per the local
development). Then in SAP the line items are added manually with service item category and then the
same is retrieved in FSL. With the retrieved line items, the timesheet is booked by the workers and
engineers who are dispatched at different work. The booked and approved timesheet will be data based
in CATDB table which is handled by SAP

Step 1: first the connection between MuleSoft and SAP was established by creation of new RFC
connections, type “TCP/IP Connection by tcode SM59.

To establish the connections with all environments the IP address for each system is required.

To be done by BASIS and ABAP.

Step 2: an external package was implemented in SAP by ABAP. The external package consists of the
below:

 Dictionary object: Data Element, Domains. Tables and Structure; the Domains and Data
Elements are specifically created to be used in the Structures and Tables to store the
information exchanged with Salesforce.
 Function Modules (including BAPI) to perform the activity in SAP pushed by SFDC; inside these
customized function module, standard BAPI are used to create / update the SAP objects like:
o Create Notification, CS Sales Order, SD Sales Order.
o Update Service Order.
o Create / Update CATS Timesheet entry.
o Delete CATS Time Sheet and send Cancelled to SFDC (specific transaction created);
 Transactions:
o “Configuration Transaction” (explained in detail in chapter 5.2);
o “Time Sheet Cancellation”, that it is used to cancel the CATS confirmation related to a
specific Service Order; it is an enhancement of the standard transaction in order to send
back to SFDC the cancellation information.
 Enhancements:
o On Service Order standard SAP “User-Exit” (PPCO0023) to update transfer table for the
interface with SFDC (explained in detail in chapter 4.3.2.3);
o Enhancements Spots for local development: specific “user-exit” where the local
implementation of the functionality can be developed.

Step 3: configuration of the interface is done in SAP (SD)

Required configuration are done for SFDC table.

Step 4: FM and BAPI used in context of processes and functionalities that are supported by package.
Business blueprint

FSL - SAP
Implementation Guide – Version 1.2.docx

You might also like