Category: PI/PO

Use of Context Objects with Example

Context Objects are a great alternative to Xpath expressions in SAP PI/PO. When creating Xpath based (Content Based) Receiver Rules or Receiver Conditions in Integration Directory, sometimes rules can becomes unreadable and complex due to the long Xpaths. Context Objects allows us to represent a Xpath with easily readable Context Names and reuse them in

Alert Configuration Example in PI/PO Single Stack

Article is a guide on Alert configuration in Process Integration (PI) single stack installation or Process Orchestration (PO) with an step by step example. Before we jump to configuration steps and example, first we will try to understand the architecture of SAP message alerting framework. SAP replaced the Netweaver Alert Framework which was included until

Data Type Enhancements for ABAP Proxy Interfaces

Data Type Enhancements in SAP Process Integration (PI)/Process Orchestration (PO) facilitates modification of input/output data structures of a standard Service Interface or Proxies Interfaces provided with SAP standard applications. Although you can use Data Type Enhancements to append structures to input or output structures of any ABAP proxy (Standard or custom), standard use of the

B2B Add-On Installation Guide

SAP introduced B2B Integration Cockpit (add-on) to facilitate all EDI communications of an organization with one component. Lets look at how to install B2B add-on in Process Integration (PI) or Process Orchestration (PO). We will look at the steps that should be carried out as part of the Post Installation of B2B Integration Cockpit. B2B

Parametarized Mapping Example in SAP PI/PO

Parameterized mapping is a great way to leverage your mapping program to have multiple applications. SAP introduced this technique first in SAP PI version 7.1. Parameterized mapping allows you to transfer values to mapping program or values from the mapping program. Similar to how we use import and export parameters in a function, parameters can

Proxy Communication Error SLD_NO_OWN_BS

While setting up proxy communication between PI/PO and SAP backend, after a new PI/PO 7.4 single stack server installation, I came across error “SLD_NO_OWN_BS”. Full Error in PI Message Log: “SOAP: Call failed: com.sap.aii.af.sdk.xi.srt.BubbleException: System Error Received. HTTP Status Code = 200: However System Error received in payload ErrorCode = SLD_NO_OWN_BS ErrorCategory = XIServer Parameter1

Dynamic File Name UDF Example – SAP PI/PO

There are several ways to create dynamic file names at receiver adapter in SAP PI/PO. In this example we will discuss how to create a dynamic file name at receiver file channel using a User Defined Function (UDF).  Filename creation with UDF is a great way when the file name logic is too complicated to