How to Restrict the Number of files from being processed in a given duration ?

[Former Member]

Hi All,

I have this File to File/ABAP proxy scenario !!

my question is how to restrict the "number of files" being processed in a given duration of time (which can be customized) with similar name or name-type?

To be clear:
Say we have a directory where we have accedentally received 2 files  by same name type "ABC<ddmmyy>.txt" however we were expecting only one file.
How to restrict the second file from being processed ?

Or inline with above setup:

Say we have a directory where we expect one file in one day where a job is run @9AM everyday and file gets picked up, But by mistake the sender system generates another file just before that job run, how to restrict this new file from being processed?

In both the cases I want the file to be discarded, or say archived.
And I dont want the new file to be processed on next Job run. (channel availability planning wont help much here.)

Can anybody provide a solution to this scenario, so that in addition to basic solution we can send and email alert to concerned teams or people mentioning that we have received duplicate/multiple file for that day ?

Thanks

[Former Member]

Hi Saurabh,

First of all if your file system directory is going to receive two files with same name then it would be listed in directory with below names,

ABC<ddmmyy>.txt

ABC<ddmmyy> - Copy.txt

or it might listed as follows,

ABC<ddmmyy>.txt

ABC<ddmmyy>(2).txt

as you can see these file names have been changed by OS itself then, in sender file communication channel you just need to enable "Advanced selection for source file" in source tab just below file name field, then make entry as below,

Exclusion Mask --> *Copy*.txt        (if multiple file with same name saved like pattern one as above)

or

Exclusion Mask --> *(*).txt           (if multiple file with same name saved like pattern two as above)

this will take only one file for that job run and exclude subsequent files.

Regards

Amit

[Former Member]

Actually problem is it not accepting file with different name type. its over wirting same file as the file's name which coming at source location has same name by which it is received each day. on top of that I cant find someway by which we can add time stamp or something like that to the file as it comes to source location.

[ambrish_mishra]

Hi Saurabh,

What tool is the third party using to drop the files.

Like in PI, the receiver file adapter has an option now to allow file overwrite...similarly, check with the third party if they can enforce such an option or check with the basis team if they can help enforce such a rule at the directory level (OS).

This will ensure either an error while writing the file with same name or a situation where file name is appended with a Copy or counter which you have ways to avoid.

Hope if helps!

Ambrish

[Former Member]

Hello,

Check this:

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/06/05/how-to-handle-duplicate-files-sen...

In case u are using PI7.31 then:

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/04/26/michals-pi-tips-duplicate-handlin...

Thanks

Amit Srivastava

[Dimitri]

Hi Saurabh,

Have a look at this: http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/03/07/what-if-file-is-not-there-active-...

For the alerting part, please have a look at these ones:

http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/03/25/michals-pi-tips-component-based-m...

http://scn.sap.com/docs/DOC-3525

http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/03/27/alerting-on-aaeaex

Kind regards,

Dimitri