Quality of service in Receiver file/ftp adapter (SAP PI 7.1)?

[Former Member]

Hi,

We are building an IDoc to File scenario in SAP PI 7.1, where a single incoming idoc will create three different output files. Also files must be created in target server in a specific order.

Our first idea to ensure that files would be created following a specific order was that Message mapping (in Java) build target payload with all three files following expected sequence.

In addition, receiver file/ftp adapter is setup with a dynamic variable to create each file with a different filename adding also timestamp.

Testing the scenario, we see that three files are created in target server but when we sort them by creation date, it seems they don't follow always same sequence.

Sometimes adapter creates File1, File2, File3; next time it created File2, File1, File3 and so on.

Our problem is that files must be created always with a specific order and we cannot use BPM. Does anyone know if a receiver file/ftp adapter can be setup to create files following specific sequence (EOIO)?

I know that sender file/ftp adapter can be setup with a quality of service, but I didn't find anything similar for Receiver file/ftp adapter.

Suggestions will be welcome.

Kind Regards,

Aitor

[Former Member · Accepted solution]

After data is getting splitted how are you creating target file?

Did you used three Business systems for that,if used then you can set the option order sequence button(check box)

Rajesh

[Former Member]

Hi,

First, thanks all of you for your quick answers. They were helpful because we learnt a new configuration setting.

We tried your suggestions but they didn't really fix our problem.

Finally interface has been re-designed and we will not have to apply this logic, so no issue from our side.

However, let me continue with this topic in case that somebody else will have the same issue, then it will be able to review this thread.

When adapter created the files in the target directory (windows server), files had the expected timestamp in each filename. However, if we sorted windows directory contents by "Date Creation", files were sorted different that timestamp shows in the filename.

For example, adapter created following files:

File1_20090325-115117-169

File2_20090325-115117-174

File3_20090325-115117-180

But when we sorted windows folder contents, files were sorted as follows:

File2_20090325-115117-174

File1_20090325-115117-169

File3_20090325-115117-180

It seems that timestamp was pre-assigned by the adapter, but when adapter created the files, it did it with a temporary name and finally assigns the filename. If a file size was bigger than other, maybe it takes more time and windows creation date is higher.

If so, it means that adapter is not following same instructions as itu2019s indicated in "maintain order at runtime" checkbox.

Do you know if there is any way where we can push also the order in the adapter as we did in interface determination?

Regards,

Aitor

[prateek]

In the interface determination, have you checked the checkbox "Maintain order at runtime"?

Does anyone know if a receiver file/ftp adapter can be setup to create files following specific sequence (EOIO)?

Quality of Service could be set only at sender. Sender only decides it for the entire flow. This could not be done at the receiver end.

Regards,

Prateek

[former_member206760]

1. use only 1 receiver buisness system and use 3 different communication channels in it ..one for each target

2. use 3 inbound message interfaces

3. use 3 mappings between source structure and target structure1..same source structure and target struture2 and source strcuture and target structure3

3. use 1 receiver determination and one interface deermination where u have to specify 3 inbound interfaces with 3 interface mappings...

remeber that in that interrface determination tick the "maintain order at runtime " chk box

4. create 1 sender agreement and 3 recceiver agreement ...

This will solve your problem