CALL C FUNCTION NO AUTHORITY

[Former Member]

HI Experts,

We are getting dumps CALL C FUNCTION NO AUTHORITY dumps in ECC system from user SOLMAN_BTC.

Regards,

LChitrasen

[Former Member]

Hello!

Try add the authorization object 'S_C_FUNCT' with follow options:

• PROGRAM = * (that is, for calling from all programs)
• ACTVT = 16 (call authorization)
• CFUNCNAME = * (authorization for all operating system functions)

Hope this could help you.

Regards,

César

[Former Member]

Some authority-checks are implemented in kernel functions. You cannot debug them or read the code even.

But the dump in this case is clearly telling you how you can fix the problem - the function module AUTHORITY_CHECK_C_FUNCT is well documented in SE37 and you can avoid such ugly dumps (and more configuration options in this case as well!!) by first calling the ABAP function to check authority, then call the kernel function to execute the system command.

It does not have to be coming from an ABAP program in a job though. It could be coming from any RFC client. In this case you can safely assume that it is coming from the SAP "Tuning" monitors. Most likely you are on a UNIX system and this user is in an RFC connection coming from your SOLMAN and calling FM SAPTUNE_SIZE_DW.

You can either switch to Windows or read the instructions of the function module documentation. The latter is much much easier, but you should actually report this to SAP as well as customers should have the option of deactivating this system function and using SXPG instead.

Cheers,

Julius

[Former Member]

create extra role:

e.g.

- PFCG  -> z_bgd_btc

- add following authorization object

   S_ADMI_FCD

- select stor as the value

- generate the profile

- assign this role to SOLMAN_BTC. run user comparison.

Regards, Henry

[Former Member]

HI Henry,

The above roles are already in our solution manager.

The SOLMAN_BTC user exist in our ECC and solman.

The above role S_ADMI_FCD is present in solman.

Please confirm us if we need to maintain the same role in ECC too.

Also we can see SAP_SM_BATCH is missing in ECC.

Please reply.

Regards,

L.Chitrasen

[Former Member]

The above role S_ADMI_FCD is present in solman.
Please confirm us if we need to maintain the same role in ECC too.

you need this in your ECC system to avoid mentioned ABAP Dump.

Also we can see SAP_SM_BATCH is missing in ECC.

SAP_SM_BATCH is for solution manager. In your case, most likely the background user in ECC has different role assigned for background job  authorization.

[Former Member]

We have the role S_ADMI_FCD in ECC. But still we are getting the error.

Please suggest.

Regards,

L.Chitrasen

[Former Member]

check background job detail, running in what client? most probably the client is 000.

adjust the profile for SOLMAN_BTC in that client.

Regards, Henry

[Former Member]

There is no job running with this user in ECC.

There are lot of jobs running with this ID in solman.

Sending you the entire dumps which in on ECC.

Category                       ABAP Programming Error

Runtime Errors              CALL_C_FUNCTION_NO_AUTHORITY

ABAP Program             SAPLSTUB

Application Component  BC-CCM

Date and Time              11/10/2012 10:47:01

Short text

No authorization to call the C function "SYSTEM".

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSTUB" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

What can you do?

  Note down which actions and inputs caused the error.

  To process the problem further, contact you SAP system

  administrator.

  Using Transaction ST22 for ABAP Dump Analysis, you can look

  at and manage termination messages, and you can also

  keep them for a long time.

    The ABAP program "SAPLSTUB" attempated to execute a statement with which

    the system automatically checks authorizations and for which the

    user "SOLMAN_BTC" has no authorization.

    The application program did not take the missing authorization

    into consideration and the program must therefore be terminated.

How to correct the error

    You can check the authorization beforehand with the

    function module AUTHORITY_CHECK_C_FUNCTION.

[Former Member]

scroll the dump to below, look for "user and transaction part"

can you paste the detail here:

Client..............

User................

Language key......

Transaction........

Transaction ID....

  EPP Whole Context ID....

EPP Connection ID.......

EPP Caller Counter......

Program.............

Screen..............

Screen Line........

Debugger Active.....

and this part "Information on where terminated"

Termination occurred in the ABAP program "xxxxxxxxxxx" - in

"yyyyyyyyyyyyyyyyyyyyy".

The main program was "zzzzzzzzzzzzzzz ".

  In the source code you have the termination point in line xxxxxxx

of the (Include) program "xxxxxxxxxxxxxxx".

The program "xxxxxxxxxxx" was started as a background job.

Job Name....... "xxxxxxxxxxxxxxxx"

Job Initiator.. "xxxxxxxxxxxx"

Job Number..... xxxxxxxxxxxx