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
Lets look at how to configure Variable Substitutions at receiver File adapter. Variables or data elements from xml payload can be assigned to file name at PI/PO runtime using this method. Receiver file channel has capabilities of defining the file directory and the file name of the output file. Variable substitution method is a
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
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
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
Hi Guys! It has been a while since my last post and most of my previous blogs are related to ABAP. This time thought of writing an article on PI. This article shows how to send data from SAP though a Proxy interface to PI. In this example PI convert this data to create a
I came across this error when working with file to iDoc interface. Check the below settings if the error occurs. 1. Maintian Communication Channel Configuration. In your receiver iDoc communication channel maintain the correct RFC destination and port. 2. Connection settings in SM59 Check if the connection is working without errors. 3. Port Settings
I came across the error “Receiver Service Cannot be Converted into an ALE Logical System” when I was working on a File to iDoc interface. This error can occur for iDoc sender of receiver if the business system is not configured properly. You have to check the settings shown below if the error occurs.. 1.