SAP PI Lookups

SAP PI/PO Lookups

Look up is nothing but to get (or) validate (or) fetch the data from the backend database at runtime.

SAP PI lookups allow you to retrieve additional data from external systems during message
processing. This data can then be used to modify, verify, or enhance the original message before it
is sent to the target system.

Lookups in Different SAP PI Versions

• Up to PI 7.0:
Implementing lookups required writing custom Java code, JCO (Java Connector) programs,
or User-Defined Functions (UDFs). Developers had to manually handle the connection, data
retrieval, and error handling within these custom implementations.

• From PI 7.1 Onwards:

The need for Java, JCO, or UDF-based lookups was eliminated. Instead, SAP introduced a
wizard-based graphical lookup tool, simplifying the process. This enhancement allowed
users to configure lookups directly within the integration framework without coding.

SHAGUN UPADHYAY 1
 SAP PI Lookups

Types of Lookups in SAP PI

Lookups in SAP PI are categorized based on the backend database system they interact with:

1. Database Lookup

o Retrieves data from external databases using JDBC (Java Database Connectivity).

o Requires a JDBC communication channel to establish a connection.

o Useful for fetching reference data, mapping values, or validating input data.

2. RFC Lookup

o Calls remote function modules (RFCs) in SAP systems.

o Uses an RFC communication channel to fetch data.

o Commonly used for integrating with SAP ECC, fetching master data, or checking
business rules.

3. Web Service Lookup

o Calls external web services (SOAP/REST) to retrieve data.

o Requires a SOAP/REST communication channel.

o Useful for real-time data enrichment from third-party systems.

SHAGUN UPADHYAY 2
 SAP PI Lookups

Database (JDBC) Lookup in SAP PI

Business Requirement:

When there is a need to fetch or validate data from the backend Oracle system at runtime, a JDBC
Lookup is used.

Prerequisites:

• Create a JDBC Receiver Communication Channel (CC) in Integration Directory (ID) to

establish a connection with the backend Oracle system.

• Import the relevant database table using an External Definition.

• Ensure proper connection to the database by configuring the correct JDBC driver and
providing valid authentication credentials (username and password).

How JDBC Lookup Works in SAP PI/PO:

1. Message Processing Begins – A message enters SAP PI/PO through a sender system.

2. JDBC Lookup Execution – The system queries the backend database using JDBC lookup
logic.

3. Data Retrieval & Mapping – The retrieved data is used in the message mapping step.

4. Message Sent to Receiver – The enriched or validated data is forwarded to the target
system.

Configuration Steps:

1. Create a JDBC Receiver Communication Channel

o Configure JDBC adapter settings.

o Define database connection parameters (URL, Driver, Username, Password).

2. Define a JDBC Lookup in Message Mapping

o Use a Conversions in the graphical mapping to execute the lookup.

o Query the database using SQL statements in conversions.

3. Deploy & Test the Integration Flow

o Ensure the lookup retrieves and processes data correctly.

SHAGUN UPADHYAY 3
 SAP PI Lookups

RFC Lookup in SAP PI

Business Requirement:

RFC Lookup is used when there is a need to fetch or validate data from a backend SAP system at
runtime.

Prerequisites:

• Configure the RFC Receiver Communication Channel in the Integration Directory (ID) to
establish a connection with the SAP system.
• Import the required RFC or BAPI structure into the Enterprise Service Repository (ESR)
from SAP applications to enable communication with the SAP backend.
• Ensure proper SAP credentials, configure RFC destinations in SAP NetWeaver, and verify
network connectivity for seamless integration.

How RFC Lookup Works in SAP PI/PO:

1. Message Processing Begins – A message enters SAP PI/PO from the sender system.

2. RFC Lookup Execution – The system calls the RFC/BAPI function module in SAP.

3. Response Handling – The retrieved data is mapped to the message structure.

4. Message Sent to Receiver – The enriched or validated data is forwarded to the target
system.

Configuration Steps for RFC Lookup:

1. Create an RFC Receiver Communication Channel

o Configure the SAP System Details, RFC Destination, and Authentication

Parameters.

2. Import RFC/BAPI into ESR

o Import the required RFC or BAPI structure to use in message mappings.

3. Implement Conversions in the Graphical Mapping for RFC Lookup

o Use Conversions in the mapping to call the RFC dynamically.

4. Deploy & Test the Integration Flow

o Ensure the lookup retrieves and processes data correctly.

SHAGUN UPADHYAY 4
 SAP PI Lookups

WEB Service (SOAP) Lookup in SAP PI

Business Requirement:

SOAP Lookup is used when there is a need to fetch or validate data from a backend web service
system at runtime.

Prerequisites:

• Configure the SOAP Receiver Communication Channel in the Integration Directory (ID)
to establish a connection with the backend web service.
• Import the Web Service Definition Language (WSDL) file into External Definitions in the
Enterprise Service Repository (ESR) to define the service structure.
• Ensure proper authentication credentials, configure the endpoint URL, and set up SSL/TLS
encryption if required for secure communication.

How SOAP Lookup Works in SAP PI/PO:

1. Message Processing Begins – A message enters SAP PI/PO from the sender system.

2. SOAP Lookup Execution – SAP PI/PO calls the backend web service using SOAP.

3. Service Response Handling – The retrieved data is processed and mapped.

4. Message Sent to Receiver – The enriched or validated message is forwarded to the target
system.

Configuration Steps for SOAP Lookup:

1. Create a SOAP Receiver Communication Channel

o Configure the Service URL, SOAP Action, and Authentication Details.

o Enable SSL/TLS if the web service requires a secure connection.

2. Import WSDL & Define Message Mapping

o Import the WSDL file into the External Definitions.

o Use Message Mapping to define how the retrieved data should be used.

3. Implement a UDF (User-Defined Function) for SOAP Lookup

o Call the SOAP web service dynamically from a UDF in the mapping.

4. Deploy & Test the Integration Flow

o Ensure the lookup retrieves data correctly and integrates seamlessly.

SHAGUN UPADHYAY 5
 SAP PI Lookups

Why Do We Use RFC, JDBC, and SOAP as Receiver Communication Channels Instead of
Sender Channels?

• Initiating Communication: SAP PI/PO sends a request to an external system (SAP via RFC,
databases via JDBC, or web services via SOAP) and expects a response.

• Response Handling: Since the external system returns a response, we need a receiver
communication channel to process it.

• Not a Sender Channel: Sender channels are used when external systems push data to
SAP PI/PO, which is not the case for RFC, JDBC, and SOAP in most scenarios.

• Appropriate Configuration: To successfully fetch data or trigger actions in external

systems, receiver communication channels are required instead of sender channels.

SHAGUN UPADHYAY 6
 SAP PI Lookups

JDBC / RFC / SOAP Parameter table

NAME CATEGORY TYPE PARAMETER

JDBC / RFC / SOAP Adapter JDBC / RFC / SOAP Import
Communication
Channel

High Level Message Flow

ESR:

SOURCE PI/PO TARGET

BS1/BC1 BS2/BC2

DT RFC DT

Request Response

MT MT

MM

SI SI

OM

SHAGUN UPADHYAY 7