SAP JV_AUTHORITY_CHECK_CUSTOMIZE Function Module for Check authority for JVA customizing









JV_AUTHORITY_CHECK_CUSTOMIZE is a standard jv authority check customize SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check authority for JVA customizing processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for jv authority check customize FM, simply by entering the name JV_AUTHORITY_CHECK_CUSTOMIZE into the relevant SAP transaction such as SE37 or SE38.

Function Group: GJU1
Program Name: SAPLGJU1
Main Program: SAPLGJU1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function JV_AUTHORITY_CHECK_CUSTOMIZE pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'JV_AUTHORITY_CHECK_CUSTOMIZE'"Check authority for JVA customizing
EXPORTING
ACTIVITY = "Activity
* BUKRS = ' ' "Company code
* KOKRS = ' ' "Controlling area
TCODE = "Transaction code

EXCEPTIONS
NO_AUTHORITY = 1 CU_GROUP_NOT_EXIST = 2
.



IMPORTING Parameters details for JV_AUTHORITY_CHECK_CUSTOMIZE

ACTIVITY - Activity

Data type: TACT-ACTVT
Optional: No
Call by Reference: No ( called with pass by value option)

BUKRS - Company code

Data type: T001-BUKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

KOKRS - Controlling area

Data type: TKA01-KOKRS
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TCODE - Transaction code

Data type: T8J_AUTH-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_AUTHORITY - User has no authority for process

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CU_GROUP_NOT_EXIST - Transaction has no customizing group

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for JV_AUTHORITY_CHECK_CUSTOMIZE Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

DATA:
lv_activity  TYPE TACT-ACTVT, "   
lv_no_authority  TYPE TACT, "   
lv_bukrs  TYPE T001-BUKRS, "   SPACE
lv_cu_group_not_exist  TYPE T001, "   
lv_kokrs  TYPE TKA01-KOKRS, "   SPACE
lv_tcode  TYPE T8J_AUTH-TCODE. "   

  CALL FUNCTION 'JV_AUTHORITY_CHECK_CUSTOMIZE'  "Check authority for JVA customizing
    EXPORTING
         ACTIVITY = lv_activity
         BUKRS = lv_bukrs
         KOKRS = lv_kokrs
         TCODE = lv_tcode
    EXCEPTIONS
        NO_AUTHORITY = 1
        CU_GROUP_NOT_EXIST = 2
. " JV_AUTHORITY_CHECK_CUSTOMIZE




ABAP code using 7.40 inline data declarations to call FM JV_AUTHORITY_CHECK_CUSTOMIZE

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

"SELECT single ACTVT FROM TACT INTO @DATA(ld_activity).
 
 
"SELECT single BUKRS FROM T001 INTO @DATA(ld_bukrs).
DATA(ld_bukrs) = ' '.
 
 
"SELECT single KOKRS FROM TKA01 INTO @DATA(ld_kokrs).
DATA(ld_kokrs) = ' '.
 
"SELECT single TCODE FROM T8J_AUTH INTO @DATA(ld_tcode).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!