SAP FKK_DOC_AUTHORITY_CHECK Function Module for
FKK_DOC_AUTHORITY_CHECK is a standard fkk doc authority check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fkk doc authority check FM, simply by entering the name FKK_DOC_AUTHORITY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKB3
Program Name: SAPLFKB3
Main Program: SAPLFKB3
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function FKK_DOC_AUTHORITY_CHECK 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 'FKK_DOC_AUTHORITY_CHECK'".
EXPORTING
* I_BUKRS = ' ' "Company Code
* I_SEGMENT = ' ' "Segment for Segmental Reporting
* I_GSBER = ' ' "Business Area
* I_BEGRU = ' ' "
* I_SUBAP = ' ' "Subapplication
* I_VTREF = ' ' "Contract
* I_LDGRP = ' ' "Ledger Group
* I_ACTVT = '01' "Activity: 01 Post 02 Change 03 Display
IMPORTING Parameters details for FKK_DOC_AUTHORITY_CHECK
I_BUKRS - Company Code
Data type: FKKOP-BUKRSDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SEGMENT - Segment for Segmental Reporting
Data type: FKKOP-SEGMENTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_GSBER - Business Area
Data type: FKKOP-GSBERDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BEGRU -
Data type: FKKVKP-BEGRUDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SUBAP - Subapplication
Data type: FKKOP-SUBAPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VTREF - Contract
Data type: FKKOP-VTREFDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LDGRP - Ledger Group
Data type: LDGRP_KKDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTVT - Activity: 01 Post 02 Change 03 Display
Data type: TACT-ACTVTDefault: '01'
Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FKK_DOC_AUTHORITY_CHECK 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_i_bukrs | TYPE FKKOP-BUKRS, " SPACE | |||
lv_i_segment | TYPE FKKOP-SEGMENT, " SPACE | |||
lv_i_gsber | TYPE FKKOP-GSBER, " SPACE | |||
lv_i_begru | TYPE FKKVKP-BEGRU, " SPACE | |||
lv_i_subap | TYPE FKKOP-SUBAP, " SPACE | |||
lv_i_vtref | TYPE FKKOP-VTREF, " SPACE | |||
lv_i_ldgrp | TYPE LDGRP_KK, " SPACE | |||
lv_i_actvt | TYPE TACT-ACTVT. " '01' |
  CALL FUNCTION 'FKK_DOC_AUTHORITY_CHECK' " |
EXPORTING | ||
I_BUKRS | = lv_i_bukrs | |
I_SEGMENT | = lv_i_segment | |
I_GSBER | = lv_i_gsber | |
I_BEGRU | = lv_i_begru | |
I_SUBAP | = lv_i_subap | |
I_VTREF | = lv_i_vtref | |
I_LDGRP | = lv_i_ldgrp | |
I_ACTVT | = lv_i_actvt | |
. " FKK_DOC_AUTHORITY_CHECK |
ABAP code using 7.40 inline data declarations to call FM FKK_DOC_AUTHORITY_CHECK
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 BUKRS FROM FKKOP INTO @DATA(ld_i_bukrs). | ||||
DATA(ld_i_bukrs) | = ' '. | |||
"SELECT single SEGMENT FROM FKKOP INTO @DATA(ld_i_segment). | ||||
DATA(ld_i_segment) | = ' '. | |||
"SELECT single GSBER FROM FKKOP INTO @DATA(ld_i_gsber). | ||||
DATA(ld_i_gsber) | = ' '. | |||
"SELECT single BEGRU FROM FKKVKP INTO @DATA(ld_i_begru). | ||||
DATA(ld_i_begru) | = ' '. | |||
"SELECT single SUBAP FROM FKKOP INTO @DATA(ld_i_subap). | ||||
DATA(ld_i_subap) | = ' '. | |||
"SELECT single VTREF FROM FKKOP INTO @DATA(ld_i_vtref). | ||||
DATA(ld_i_vtref) | = ' '. | |||
DATA(ld_i_ldgrp) | = ' '. | |||
"SELECT single ACTVT FROM TACT INTO @DATA(ld_i_actvt). | ||||
DATA(ld_i_actvt) | = '01'. | |||
Search for further information about these or an SAP related objects