Dynamic configuration of Receiver FTP File channel

[Former Member]

Hi,

The scenario is sending an IDOC from an R/3 system (using IDOC adapter) to a FTP file system. I want to dynamically configure the filename and the target directory in the following cases

1. With filename and the target directory coming as a part of the source IDOC

structure

2. There is mapping involved (pass thru) and the file name and target directory are

NOT a part of the source IDOC structure.

I have seen blogs which explains the situation using mapping for File-To-File scenario (Not IDOC-To-File scenario) and some blogs explaining for Http adapter and email adapter, but not for the above scenarios for IDOC-To-File Scenarion.

Your input is highly appreciated.

Regards

Ganesh

[Former Member]

Ganesh,

Dont worry about all the weblogs as michal said. You concentrate on the weblogs where they have discussed for dynamic configuration for filename.

Chech this weblogs which will help you in this regard:

/people/jayakrishnan.nair/blog/2005/06/20/dynamic-file-name-using-xi-30-sp12-part--i

/people/sravya.talanki2/blog/2005/08/11/solution-to-the-problem-encountered-using-variable-substitution-with-xi-sp12

---Satish

[Former Member]

hi

use Varable susbtituion in receiver file adapter

you set the Enable indicator, you can enter variables for the Target Directory and File Name Scheme. Enter the names of the variables and references in the table.

● Enter each variable that you reference in the Target Directory and File Name Scheme fields without the surrounding percentage sign under Name of Variables in the table.

The variables can refer to attributes of the message header or elements of the message payload.

○ If the variables are to refer to an attribute of the message header, add the prefix message: to the name of the variable under Reference. You can specify the following attributes of the message header:

sender_party, sender_service, receiver_party, receiver_service, interface_name, interface_namespace,

message_id (message ID with hyphens, for example 9fbe1ff1-9a0d-11d9-8665-cbf10a126331)

message_id_hex (message ID in hexadecimal format, for example 9fbe1ff19a0d11d98665cbf10a126331)

For example, if you want to specify the interface name from the message header in the target directory or in the file name scheme, enter message:interface_name as the reference.

or look into help

http://help.sap.com/saphelp_nw04/helpdata/en/ae/d03341771b4c0de10000000a1550b0/frameset.htm

please reward points

Thanks

Sreeram.G.Reddy

Message was edited by:

Sreeram Reddy

[Former Member]

Hi Ganesh,

in you target message you could create a field/structure for the filename and directory.

Then use these values in the dinamic filename determination (variable substitution).

In the content conversion do not specify that field/structure and it will not be inserted in the file.

Regards,

Sergio

[MichalKrawczyk]

hi,

>>>>I have seen blogs which explains the situation using mapping for File-To-File scenario (Not IDOC-To-File scenario) and some blogs explaining for Http adapter and email adapter, but not for the above scenarios for IDOC-To-File Scenarion.

that is not important as you set the name inside your mapping

(using adapgter specific attributes - filename )

so just use the solution from any of the described blogs

Regards,

michal