Category: PI/PO

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: 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

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 “<Adapter Metadata Object Name of Adapter>” In this example file and SFTP ASMA are used in file to

Number Range Objects Example SAP PI/PO B2B

If you have a requirement to assign an unique sequence number to a target field you can do that using below method in PI 7.3 or higher single stack versions. This type of unique sequence number requirements are common when you have EDI communications with partners. EDI segments ISA.13 (Interchange Control Number), ST.02 (Transaction Set

File to File Scenario without IR (ESR) Objects

This article shows a PI integration File to File scenario which is configured to move files from application server location to FTP location. This interface is able to move any type of file regardless of its structure and extension. For this kind of interface you do not require integration repository objects as file structure is