Tag: PI/PO

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

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 in SAP PI

In SAP PI/PO there are several ways to create dynamic file names at receiver channel. Depending on the requirment you can make use of either Adapter Specific Massage Attributes (ASMA), User Defined Function (UDF) or Variable Substitution to set the file name dynamically. I have three articles explaining each method step by step with an

Adapter Specific Message Attributes SAP PI

ASMA or adapter specific message attributes are additional information about the message. Each adapter has set of ASMA and these are available inĀ in message header. These attributes can be accessed in message mapping or routing under namespace “http://sap.com/xi/XI/System/<Adapter Metadata Object Name of Adapter>” In this example file and SFTP ASMA are used in file to