This is another capability of the receiver file Communication Channel that you might use to influence the file name or path under which the file is generated. Pros and cons: + The easiest implementation of all possible options, - Limited options to influence the file name, - No flexibility. Refer here for configuration details: Įxample filenames: xi_output_20120213-180304-425.xml (with xi_output_.xml and Add Time Stamp) xi_output_005056a4-7bae-1ee1-95df-3964c12edd64.xml (with xi_output_.xml and Add Message ID) xi_output_0002.xml (xi_output_.xml and Add Counter) This is only possible with the NFS Transport Protocol. Following rules apply:Īdd Time Stamp: the time stamp is added as the last part of the name, directly before the extension, and it is always formatted yyyyMMdd-HHmmss-SSS.Īdd Message ID: PI’s message ID is added to the file name, formatted as xxxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.Īdd Counter: a consecutive number is added to the file name, directly before the extension. However, you cannot influence the way the dynamic part of the file name is generated. As of SAP Help description, this was originally designed to guarantee that no file is overwritten, but you could possibly also use it for some business requirements. The last three of them lead to the file name being generated dynamically. You have the following options for File Construction Mode: Create, Append, Add Time Stamp, Add Message ID, and Add Counter (only for NFS Transport Protocol). You can find the respective option in the Processing tab page of your receiver file Communication Channel. This is by far the simplest solution, and it can only match the simplest requirements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |