SAP PI

SAP PI tutorials

Enhancing CBMA Alerts and Message Monitoring with UDS Attributes

It is very difficult to understand the SAP PI alert JSON message sent to functional/business users. Business users keep asking about the key attributes for alert is generated. This requirement normally takes some custom development for earlier PI versions but for new CBMA alerts we have UDS attributes, which takes cares of this requirement. At least, adding these attributes will let business/functional team know that for which key values errors

Conversion From EDI to XML

There was a requirement of transferring the files in EDI formats to SAP system or vice versa. As these files cannot be interpreted by the SAP system, these need to be converted into some format which can be processed by SAP. SAP PI accepts the file in XML and that XML files can be converted into IDOC and transferred to SAP.Converting this EDI file into XML can be achieved by either Conversion Agent

Setup Multiple Operations Scenario in ESR and ID SAP PI 7.31

I came across with  a situation where client was looking out for one WSDL with multiple operations in it. Lets say, If one cleint program depending upon incoming values from legacy, want to route messages to a particular endpoint which will do some operation in R/3 side. For example – If data is sepecific for insert/Update/Delete in legacy. We often receive requirements to create separate interfaces for Insert/Modify/Delete and normally we follow

Simple File To File Scenario in SAP PI 7.31

In this example, I am going to demonstrate a simple File To File scenario steps, which will contain steps for how to send one XML file from one location to another location. Assumptions – I assume, Product and Software Component are already defined in SLD and also imported into PI – ESR. Step 1 – ESR Developments. Create Source and Target Data types. Source Data Type Target Data type   Step 2 – Create Source and Target Message type.

Multiple Idoc Segment occurance to Multiple File – 1 to N Multimapping

We received a requirement where based on one segment’s multiple occurance of an Idoc, we need to create multiple files as output (Based on occurance of a particular segment). Normally, in the receiver side we change occurances to 0..n to accommodate these kind of requirement. But, in this scenario, XSD used were standard XSD’s with occurance 1 and client didn’t want to change it in custom ways as receiving system is bound to receive one message/file at a time. Because of this

E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -1

Background The Bank Communication for many corporations is a mess because of different interfaces and protocols are involved between data communications. This results in high cost and a lack of cash flow transparency. For Communication between Corporations and bank, SAP provides Bank Communication Management application, which helps companies to streamline payment processes and lower the cost of managing multiple communication interfaces. For the integration purpose SAP provides SAP Integration Package

E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -2

This blog is continuation of E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -1 Background Payment run will generate files in ECC and those files will be picked up by SAP PI. SAP PI will merge incoming files into one and then it will encrypt the file. Later, PI will fetch encrypted file to send it to bank network. Whole process will be something like below

E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -3

This blog is continuation of E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -1 E-Payment: A Customized Solution other than SAP Integration Package SWIFT – Part -2 Payment run will generate files in ECC and those files will be picked up by SAP PI. SAP PI will merge incoming files into one and then it will encrypt the file. Later, PI will fetch encrypted file to

Configuring a Local Consumer on AS ABAP in SAP PI 7.31

By setting an alert rule to use a local alert consumer and scheduling a background job for running a dedicated program in SAP PI 7.31 you can configure a simple notification mechanism. Using this mechanism, the system would generate notifications upon message alert events, and would send these notifications via e-mail or SMS to users who should receive them. Consider the following about the local alert consumer described here: It applies only

Alerting API on Alert Engine in SAP PI 7.31

The API for accessing the Alert Engine is available as a Web service. This service is available both on AS ABAP and AS Java systems that support component-based message alerting. You can use the following versions of the API: AlertRetrieveAPI is available both on AS ABAP and AS Java systems. AlertRetrieveAPI_V2 is an extended version that features additional input and output parameters. This Web service is available only on Advanced Adapter Engine

Transporting Alert Rules in SAP PI 7.31

Alert rules are objects in the Integration Directory. Similarly to the other PI configuration objects, an alert rule can be transported from the originating Integration Directory to other Integration Directory systems in different system landscapes. Transporting Rules The process of transporting an alert rule consists of the following steps: The user transports an alert rule from a source to a target system. The target system creates an alert rule with exactly

Analyzing the Adapter Framework in SAP PI

This blog describes checks and possible reasons for bottlenecks in the Adapter Framework. The following aspects are important to know for the analysis of a performance problem on the AFW: The AFW contains the Messaging System that is responsible for the persistence and queuing of messages. Within the flow of a message, it is placed in between the sender adapter (for example, a file adapter that polls from a folder)