Problem with Open Dataset after upgrading to ECC 6.0

[Former Member]

Hi Experts,

We Upgraded from 4.7 to ECC 6.0 and I replaced the function module 'PFL_COPY_OS_FILE' with 'ARCHIVFILE_SERVER_TO_SERVER' as it is obsolete in ECC6.0. One of my user running the program which has this function module is getting into DUMP saying the message as 'No Authorization' when it reaches to the statement 'OPEN DATASET <name> for OUTPUT in binary mode'.

Before replacement(in 4.7) it worked fine without adding any security role which has SE38 in it.

After adding the security role which has Transaction se38 in it, it worked in ECC6.0 as well, but we never give the Transaction SE38 to the user.

Do something needs to be added from ABAP point of view OR something needs to be aded from Security point of view ?

Appreciate your early response.

Thanks,

kalikonda.

[Former Member]

Hi Experts,

We Upgraded from 4.7 to ECC 6.0 and I replaced the function module 'PFL_COPY_OS_FILE' with 'ARCHIVFILE_SERVER_TO_SERVER' as it is obsolete in ECC6.0. One of my user running the program which has this function module is getting into DUMP saying the message as 'No Authorization' when it reaches to the statement 'OPEN DATASET <name> for OUTPUT in binary mode'.

Before replacement(in 4.7) it worked fine without adding any security role which has SE38 in it.

After adding the security role which has Transaction se38 in it, it worked in ECC6.0 as well, but we never give the Transaction SE38 to the user.

Do something needs to be added from ABAP point of view OR something needs to be aded from Security point of view ?

Appreciate your early response.

Thanks,

kalikonda.

[Former Member]

Sounds like that perhaps you had a change of servers, folder names, etc., and users may not have privileges to write files to the target on the applicable Apps/DB server? I'd checked with the systems adminstrators/dba's on whether or not output (new file) to the dataset target/folder is allowed.

Like you, I recently switched from 4.70 (WebAs 6.20) to NetWeaver7.0. I find the f1-help is an invaluable tool for differences between the versions, but I don't think that applies in this case. ;-}

[StMou]

Hi,

- For problem of authorization, run transaction ST01 check Authorization and activate trace.

- Run transaction with open dataset or ask people to run report.

- After run st01. Stop trace and analyse trace. You normaly found RC<>0 and you an analyse wich authorisation is missing.

Another way, ask you people to run st52 when he have problem

Rgds

[rainer_hbenthal]

Sounds that someone has forgotten to giv user SAPADM correct autorization after upgrading. Check with your basis team.