A file created by the Process Integration (PI) File Receiver Adapter on a Window's file system is ASCII though the file encoding channel parameter is set to UTF-8. SAP Knowledge Base Article - Preview. SAP SFTP Receiver Adapter with Dynamic Filename This example show SAP own SFTP receiver adapter to connect to Concur SFTP site, to send master data to Concur. Enter Server host name, default port for SSH is 22.

In this article, we are going to learn about SAP PI/PO File Adapter.

First, we will understand the File adapter configuration for both sender and receiver. Then we will have a look at File Content Conversion (FCC) with simple and complex file structures.

File Adapter converts the incoming files into XML and vice versa. The File adapter resides on the J2EE stack of the PI server. It can read/write files directly from/to the PI server at the OS level using File System protocol. It also works using FTP protocol, using which it can read/write files from/to any server location. The configuration of File Adapter is quite simple and straightforward.

Sender File Adapter

Select the Transport protocol as FTP or NFS and Message Protocol as File. Specify the Directory and filename from where the source file needs to be picked up. File type can be either text (or XML) or binary. In the case of FTP protocol, you will need to provide FTP connection parameters as well. Below configuration for the File sender channel for NFS.

Below configuration for File sender channel for FTP

The adapter supports all the three QoS

Sap Pi 7.1

• • BE (Best Effort),
  • EO (Exactly Once) and
  • EOIO (Exactly Once in Order).

Specify QoS as per your scenario. Poll Interval indicates the time interval between two consecutive attempts by PI to read the files from the source directory. Processing mode defines how the file should be handled once it is processed by the adapter engine. The file will not get deleted If processing mode selected as “Test”. The File will get deleted if the processing mode is selected “Delete” after the processing. If you specify a queue name (in case of EOIO) it is automatically created in PI. You can also specify the empty file handling.

Receiver File Adapter

Select the Transport protocol as FTP or NFS and Message Protocol as File. Specify the directory and filename where the target file is to be put. The target directory if it does not exist gets created automatically. Specify connection parameters in the case of FTP protocol. You can specify the File Construction mode as per your choice. QoS possible here are EO and EOIO and is inherited from the Integration Server.

You can also Specify the “Add Timestamp” to append file create time to filename. Also, specify the way to handle an empty file.

To see an example of a file adapter using NFS protocol, go through this article about File to IDoc scenario.

In the next part, we shall discuss setting up File Adapter for File Content Conversion with simple structure (CSV File) at sender File Adapter

File Content Conversion In Sap Pi Receiver

and also check

File Content Conversion In Sap Pi At Receiver For Sale

File Content Conversion with simple structure (Fixed Length Fields ) at sender File Adapter