Procedure calling through an abap class , method

[former_member869365]

I want to call a procedure in process chain, so created a abap class and a method to call the procedure. The code goes like this :

class ZAB_X definition
  public
  final
  create public .

public section.
INTERFACES if_amdp_marker_hdb .
   CLASS-METHODS: call_sp_by_name_2.


protected section.
private section.
ENDCLASS.

it is giving an error : CX_AMDP_EXECUTION_FAILED
can you help or give a possible solution to this problem

[Ulrich_Schmidt1]

Tip: To make code more readable, you can use the "Code" font in the editor. (I have done that for you.)

[Sandra_Rossi]

CX_AMDP_EXECUTION_FAILED is the class, but you have the possibility to see the details of the exception (message and attributes). What does it say?

[former_member869365]

This gives me an Insufficient Privilege error

[matt]

Hmm. Looks like there's an insufficient privilege error. Ask you Basis/HANA team to check.

[former_member869365]

The problem is solved.
There was a problem in my Procedure

I used Invoker in place of Definer.

Giving the difference between invoker and definer for future reference .

SQL SECURITY Clause

This clause specifies the context the stored routine or view will run as. It can take two values - DEFINER or INVOKER. DEFINER is

the account specified as the DEFINER when the stored routine or view was created (see the section above). INVOKER is the account invoking

the routine or view.

As an example, let's assume a routine, created by a superuser who's specified as the DEFINER, deletes all records from a table.

If SQL SECURITY=DEFINER, anyone running the routine, regardless of whether they have delete privileges, will be able to delete the records.

If SQL SECURITY = INVOKER, the routine will only delete the records if the account invoking the routine has permission to do so.

INVOKER is usually less risky, as a user cannot perform any operations they're normally unable to. However, it's not uncommon for accounts

to have relatively limited permissions, but be specifically granted access to routines, which are then invoked in the DEFINER context.

SQL SECURITY INVOKER