Skip to main content

Fast way to integrate SAP and Salesforce with JITTERBIT

About Us
Published by jetbi
25 May 2021
219

Jitterbit is an integration platform that allows you to integrate any business processes quickly. In this article, we consider the creating process of connecting operations between SAP and Salesforce in a few steps. For this demonstration, we will use the desktop application named Jitterbit studio. 

Here is an example where it needs to upsert Prices in Salesforce from SAP data. Our operation will contain two steps: Extract Prices from SAP and Upsert prices in Salesforce

1. For the first operation we start by configuring SAP Endpoint.

1.1 In Jitterbit studio you can easily use one of the preconfigured connectors. In our case, we choose SAP connector and create a new SAP Endpoint, just enter credentials from your instance and check the connection with the “Test Connection” button.

Configure SAP Endpoint:

jitterbit-1

1.2 On the next step we add a new SAP Function. To configure the function there is a need to choose Endpoint, select function type, start typing function name, and choose needed from the list of available functions.

1.3 After the new Sap Function added, create Operation from this function, configure necessary transformations, and select the target function.

jitterbit-2

This operation will call SAP PRICE_EXTRACT function and will add data to the temporary storage.

2. Upsert Price Book Entries operation

2.1 Start by clicking on the “Jitterbit Connect” button and select Salesforce Org. In the next window, we need to enter credentials from the Salesforce organization and Test connection.

2.2 Right after adding a new Salesforce org to the connector, create a new Upsert operation by clicking on the “Jitterbit Connect” button and selecting “Salesforce Upsert”. Follow the instructions, choose the organization, required object, External ID field.

jitterbit-3

As a parameter “where your data comes from” choose temporary storage and select the source that was created from the target of our previous operation.

2.3 And the last step of upsert Operation is configuring Mapping.

jitterbit-4

The mapping page also allows you to configure each field value with Formula Builder if it’s needed.
The second operation is configured.

3. There are only a few steps to finish.

3.1 Return to our Price Extract operation and select Salesforce Upsert operation on success.

jitterbit-5

3.2 Create a schedule to execute your operations. 

That’s all. Created operations will execute Prices from SAP and upsert records in Salesforce, each time when the schedule is running on.

We created Jitterbit integration operations in less than 15 minutes, without any specific knowledge. With big perspectives to future upgrades of these integrations.

Jitterbit gets the highest marks in comparison of integration services based on The Gartner Critical Capabilities report and provides a broad array of critical capabilities to help implement integration projects. A bunch of preconfigured connectors to popular applications and databases helps you to create integrations in a few clicks. Easily extend your applications to create leading solutions. Big Partner community provides tons of materials: about 75% of projects go live in under 30 days.

RESOURCES: success.jitterbit.com


Sergey Korobko
Salesforce Developer
image
Question to the expert
image

We have available resources to start working on your project within 5 business days

1 UX Designer

image

1 Admin

image

2 QA engineers

image

1 Consultant

image
Related Articles
All articles
image
Is Salesforce Winning the Public Sector Race?
An analysis of Salesforce's rapid expansion into the U.S. public sector, tracing its path from cautious early government licensing deals in the 2010s through the launch of Government Cloud in 2012, its pivotal role in COVID-19 vaccine rollouts, and its 2025–2026 push into military and intelligence work via Agentforce and Missionforce. The piece covers major 2026 contracts — including a $5.6 billion Army deal, a $1.6 billion VA agreement, and Pentagon Impact Level 5 authorization — alongside real-world case studies like California's REAL ID processing and the UK's NHS back-office operations. It also examines the structural obstacles still facing Salesforce and other vendors in government tech: legacy IT systems decades old, outdated federal procurement rules, budget constraints, and organizational caution around AI adoption, plus the competitive pressure from Palantir, Microsoft, and Oracle in the race for public sector AI spending.
28 August 2026
image
Why Your Salesforce Flows Are Agentforce's Biggest Problem
This article argues that the most underestimated risk in Agentforce deployments isn't data quality — it's the automation layer: years of overlapping Flows, Process Builder processes, Apex triggers, and managed package logic that no one has reviewed end-to-end. It explains why AI agents inherit automation complexity without the tribal knowledge human admins carry, why technical debt only becomes visible after an agent hits it in production, and why a clean demo is no indicator of production readiness. The article closes with a concrete, tool-by-tool inventory approach using Flow Trigger Explorer, Salesforce Optimizer, Setup Audit Trail, Apex Debug Logs, Agent Builder, and Health Check — scoped to the specific processes the agent will actually use rather than the whole org.
23 July 2026
image
How to Wire Multiple Salesforce Projects in One Org Without Breaking Everything
This article maps the real integration patterns that emerge when multiple Salesforce projects — both managed packages and unpackaged code — share a single org. It covers four concrete patterns: attaching custom triggers to package-owned objects, calling global members exposed by managed packages, writing directly into another project's objects, and runtime-guarded reads of package data. It then addresses access control for authenticated and guest users, including the Master-Detail wall and the without sharing elevation pattern. The piece closes with eight concrete risks (compile-time dependencies that block uninstall, upgrade coupling, silent cascade failures, access invisible to admins) and six actionable recommendations for keeping cross-project coupling manageable.
08 July 2026