creating abap data flow, open file error

[Former Member]

hello experts,

i am trying to pull all the field of MARA table in BODS.

so i m using abap data flow.but after executing the job i got error "cant open the .dat file"

i am new to abap data flow so i think may be i did some mistake in configuration of datastore.

can any one guide me how to create a datastore for abap data flow???

[Former Member]

In your SAP Applications datastore, are you using "Shared Directory" or "FTP" as the "Data transfer method"? Given the error, probably the former. In that case, the account used by the Data Services job server must have access to wherever SAP is putting the .DAT files. When you run an ABAP dataflow, SAP runs the ABAP extraction code (of course) and then exports or saves the results to a .DAT file, which I believe is just a tab-delimited flat text file, in the folder "Working directory on SAP server." This is specified from the perspective of the SAP server, e.g., "E:\BODS\TX," where the E:\BODS\TX folder is local to the SAP application server. I believe this folder is specified as a directive to the ABAP code, telling SAP where to stick it (the .DAT files). The DS job server then picks it up from there, and you tell it how to get there via "Application path to the shared directory," which, in the above case, might be
SAPDEV1\BODS\TX" if you shared-out the E:\BODS folder as "BODS" and the SAP server was SAPDEV1. Anyway: the DS job server needs to be able to read files at
SAPDEV1\BODS\TX, and may not have any rights to do so, especially if it's just logging-in as Local System. That's likely your problem. In a Windows networking environment, I always have the DS job server log-in using an AD account, which then needs to be granted privileges to the, in our example's case,
SAPDEV1\BODS\TX folder. Also comes in handy for getting to data sources, sometimes.

Best wishes,

Jeff Prenevost

Data Services Practice Manager

itelligence

[Former Member]

Thank you so much for your reply Jeff ,I am using shared directory method and i am really confused with the "working directory on sap server","application path to share directory" "abap file generation directory" and also i am not able to trce the .aba file and .dat file .actully its an urgent requirement in what i m working and i am having few more things to rectify so is it possible for you to talk to me on chat in gmail or yahoo, it will be better for me to discuss on the struck points.thanks

[Former Member]

Yes, it would be possible for me to chat with you, but I'm not interested in getting involved to that extent, smacks of what I usually get paid to do, and doesn't benefit the community.

Of the things you rattled off, the only remaining item is the "ABAP file generation directory," which is just the folder, local to or from the perspective of the DS job server, in which DS will generate the little ABAP programs. It must exist, and the DS job server must have the ability to write to it.

Curiosity is a great quality in this field, but you don't particularly need to "trace" the .aba and .dat files regardless of it being .actually an urgent requirement in what you re working. If you read the manual carefully and understand that DS and SAP transfer .DAT files after they're generated by the ABAP program, and must have both configuration and security properly setup to do so, it should get clearer.

Best wishes,

Jeff Prenevost

Data Services Practice Manager

itelligence

[Former Member]

Ok fine if my sap server is "sapser11",then shared directory can i specify as "C:\bodi" and working directory for sapserver as "
sapserver\bodi" and abap directory as"C:\abap" .

in the abap data flow i will give the abap file name as"z_file.dat" and abap program name as "z_file"

in the data trasport i will giv the file name as"z_file.dat"

is these correct???????

tell me if any rectification required.

thnx.

[Former Member]

Gen ABAP directory - a folder local to job server computer (eg: C:\temp)

Working directory - a directory in ECC server where the job executing user should be given read/write/execute privileges (eg:
ECC Server\folder_name\)

App Shared directory - Give same as Working directory (eg:
ECC Server\folder_name\)