on 01-09-2015 1:29 PM
Hello,
I'm trying to setup material replication from ERP to SAP Sourcing 10 via standard mechanism - files through FTPs.
I've configured the following:
1) Setup -> System Setup -> Integration -> File Transfer Configuration
2) Setup -> System Setup ->Scheduled Tasks
Schedule task refers to configured in Step 1) FTPs profile "FTP Indeksy, Usługi"
I put correct XML files (representing single material) into this FTP to directory /ftp/sourcing/TST/inbound/materials
But material files does not get imported. I've observed the following in the logs:
Setup -> System Administration -> Administrative Reports -> Background Task Status
It seems, that that import mechanism is searching for that directory as if "Local Directory" option was chosen and not on the FTP profile I provided.
When I created directory (/ftp/sourcing/TST/inbound/materials) on the local filesystem - just to confirm my theory and I put file with material there, everything worked fine - material got imported.
It means, that Schedule Tasks which base on Configured Directory option (which referes to FTP profile) is being ignored, and importing mechanism keep using "Local Directory" option.
Anyone experienced same problem?
Best Regards,
TG
Hi TG,
Could it be that the Scheduled task is unable to interpret the Folder structure like
ftps://10.149.30.20/ftp/sourcing/TST/inbound/materials. can you check to make sure that 'ftp' is your root directory.. (at least this is what we are seeing from the log file.. )
Can you also make sure that you can somehow access the ftp server from the esourcing server hopefully there is no firewall or such that is stopping the call also check any proxy server settings..
Thanks
Prasad
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Tomasz,
The directories for Upload, Queue and Archive are actually LOCAL directories on the CLM server and should be created and accessible. (same as previous versions before 10)
As the scheduled task runs, it will copy the files from the FTP server to the local directory Upload and execute it from there moving it through Queue to Archive.
One problem in v10 is that there is no configuration for the FTP directory as in v9 ... not really sure how this is handled.
Bogdan
Hi Tomasz, Bogdan,
Regarding the configuration of the FTP directory, in Release 10.0 you need to specify the FTP directory in the File Transfer Configuration URL field:
Please note that that this URL field should contain the protocol, ftp hostname, and remote directory, e.g.:
Regards,
Ed
Hi Bogdan,
I haven't done the configuration personally - but I have worked with a customer who was successful with the configuration once I explained to him that the FTP remote directory now needs to be part of the new File Transfer Config URL field - which is change from the 9.0 UI. I also have observed this config working successfully in our 10.0 integrated test environments.
If you would like to provide screen shots of your File Transfer Config and the Scheduled Task config for your Data Import Monitor, I can take a look and see if I notice anything. Otherwise, you may want to create a Customer Support message.
Regards,
Ed
Hello Ed,
After loads of struggles I finally managed to make it work...
Some points to add after migration from V9 -> V10; maybe to be taken into consideration for an SP.
- automated tool that converts data import tasks didn't add the "Remote Directory" (V9) to the URL config (V10)
- the automatically converted Data Import Scheduled Task (V9 to V10) had to be dropped and recreated because it was configured as FTP but logs showed it was behaving like a "Local Directory" task (no FTP connectivity logs) ... possibly DB issue? After creating a new SchedTask from scratch logs were OK.
- FTP URL had to be forced with %2F to correctly change directories.
Regards,
Bogdan
Hello Bogdan,
I am facing a very similar issue now post upgrade from 9.16 to 10.06. I did all the steps as you has mentioned, but still get error.
I did not understand the point you mentioned "FTP URL had to be forced with %2F to change directories". Can you please help on this.
We also have a simple FTP.
Thanks,
Arahanth
Hello Arahanth,
In fact, our problem proved to be a hundred problems into one.
We were on SAP Hosted cloud at the migration time and eventually we had to switch from FTP to SFTP because of some misalignment between Sourcing code and FTP configuration on SAP side.
%2F is just the encoded value of '/'. I have no idea why, but initially it worked by sending a double-slash in the URL like so:
ftp://10.10.10.10%2F/sourcing/outbound/pi/ (instead of just a single slash - something to do with the FTP config related to chroot).
If you want, send me more details about the issue on my email and I'll try my best to assist.
Bogdan
Hi Bogdan,
I am trying to get SFTP working with no luck.
SFTP server folder structure:
- PTP
- 5533_ESOURCING_MATERIAL_ERP
- From_SAP
- Archive
- Queue
FTP configuration:
- sftp://<hostname>/PTP/5533_ESOURCING_MATERIAL_ERP
Scheduled task directories:
- /From_SAP
- /Archive
- /Queue
Error in background task status:
- *** Discarding event because upload directory (/From_SAP) does not exist ***
I even tried with the following in the scheduled task with no luck:
- /PTP/5533_ESOURCING_MATERIAL_ERP/From_SAP
Could you help with what I am missing?
Thanks & Regards,
Subhasini
Hi Subhasini,
The 3 directories in the clm config (Upload/Queue/Archive) have to be on the CLM application server, not the ftp.
System actually does following actions:
1 - connect to FTP location and copy everything locally in the configured Upload dir
2 - process files from Upload dir.
So you will need 4 directories
- FTP location dir (where PI or ECC will put the files)
- Upload dir (on CLM app server or mapped drive)
- Queue dir (on CLM app server or mapped drive)
- Archive dir (on CLM app server or mapped drive)
Bogdan
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.