File is not Picking eventhough file naming convention is there as *XXXXXX*
I would like to know the exact route cause of why PI behaves like this?
I am doing SYNC Scenario FILE -- RFC -- FILE using Integrated Configuration nothing but Advance Adapter Engine concept.
I kept file naming convention to be picking in the sender File adapter as
Now I am keeping file with file name in FTP as given below:-
But It is not picking the above file I tried and tried so many times finally I have taken one Old success file from Source Team and Compared both XML files using XML Comparison Tool and I found 3 Reasons:- which I wondered It Picks the below Success File
The_3 Differences are:-_
Success File Contains:-
a) <?xml version="1.0" ?>
but old one contains::
<?xml version="1.0" encoding="ISO-8859-1" ?>
I agree there is encoding issue but how can it validation takes place before coming into PI and that to while picking the File at FTP Location?
b) Success File Contains:-
Failure File Contains:
I agree there is TAG issue but how can it validation takes place before coming into PI and that to while picking the File at FTP Location?
c) File Naming conventions:-
FOR Failure File Contains:20100409_121403_000001929023_XXXXX_ConsumerHours.xml
FOR Success File Contains:091023235952188_XXXXX_ConsumerHours.xml
Is there any restriction in keeping FIle name length for placing into the FTP Location. Even though I kept ConsumerHours.xml I donot know why it is not picking the File ?
Kindly let me know if you have any solution on this I mean exact Route Cause:
Amar Srinivas Eli
Edited by: Amar Srinivas Eli on Apr 10, 2010 3:27 PM