We are getting the below error while executing an ABAP dataflow
5100 5152 R3C-150607 24/10/2012 4:12:29 AM Execute ABAP program <//vwmexappd001/DSCompartido/Z_ABAP_PGPB_LFA1.aba> error < Open File Error
Our analysis is as below :
During the transformation the .aba files get generated on the WINDOWS shared location (\vwmexappd001\DSCompartido\Z_ABAP_PGPB_LFA1.aba)
To generate the .dat file the ABAP program reads the .aba file located on WINDOWS shared location using the UNIX path (//vwmexappd001/DSCompartido/Z_ABAP_PGPB_LFA1.aba)
o NOTE: to access the shared folder in WINDOWS the folder path should be separated using backward slash ()
The Program fails to find the .aba using the UNIX PATH on the WINDOWS OS.
o Following is the Exact Error Message: 5100 5152 R3C-150607 24/10/2012 4:12:29 AM Execute ABAP program <//vwmexappd001/DSCompartido/Z_ABAP_PGPB_LFA1.aba> error < Open File Error
Please let us know what could be the issue.Waiting for a quick reply.
Not the most intuitive error message I have to agree…
No, the problem is a different one and not related to the aba file. It just tells what the program is that failed, not that is failed with reading the program file.
Your problem is the “working directory on SAP server” datastore setting. The ABAP starts (check the trace log, it says “ABAP dataflow started” I am sure) and when it gets to the place where it wants to store the data, it cannot open the file in that directory on the ABAP server(!).
Do I dare to contradict you Werner? Normally with a error on the SAP side is gives it in an RFC error message. And normally it should complain about CANNOT OPEN DATASET or something similar.
Well I really think that it is not an error from the SAP side.
But I am not sure if the problem is that the job can reach the location where the abap is stored. I tested a non-existing share and got the following error: