SAP TXX_VIEW_AUTHORITYCHECK Function Module for
TXX_VIEW_AUTHORITYCHECK is a standard txx view authoritycheck 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 txx view authoritycheck FM, simply by entering the name TXX_VIEW_AUTHORITYCHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: TXX5
Program Name: SAPLTXX5
Main Program: SAPLTXX5
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TXX_VIEW_AUTHORITYCHECK 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 'TXX_VIEW_AUTHORITYCHECK'".
EXPORTING
* ID_COMPANY_CODE = "
ID_TAX_VIEW = "
ID_ACTIVITY = "
* ID_GJAHR = "
EXCEPTIONS
INVALID_VIEW = 1 NO_AUTHORITY = 2
IMPORTING Parameters details for TXX_VIEW_AUTHORITYCHECK
ID_COMPANY_CODE -
Data type: BUKRSOptional: Yes
Call by Reference: Yes
ID_TAX_VIEW -
Data type: TXX_TXVIEWOptional: No
Call by Reference: Yes
ID_ACTIVITY -
Data type: ACTIV_AUTHOptional: No
Call by Reference: Yes
ID_GJAHR -
Data type: GJAHROptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INVALID_VIEW -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for TXX_VIEW_AUTHORITYCHECK 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_invalid_view | TYPE STRING, " | |||
| lv_id_company_code | TYPE BUKRS, " | |||
| lv_id_tax_view | TYPE TXX_TXVIEW, " | |||
| lv_no_authority | TYPE TXX_TXVIEW, " | |||
| lv_id_activity | TYPE ACTIV_AUTH, " | |||
| lv_id_gjahr | TYPE GJAHR. " |
|   CALL FUNCTION 'TXX_VIEW_AUTHORITYCHECK' " |
| EXPORTING | ||
| ID_COMPANY_CODE | = lv_id_company_code | |
| ID_TAX_VIEW | = lv_id_tax_view | |
| ID_ACTIVITY | = lv_id_activity | |
| ID_GJAHR | = lv_id_gjahr | |
| EXCEPTIONS | ||
| INVALID_VIEW = 1 | ||
| NO_AUTHORITY = 2 | ||
| . " TXX_VIEW_AUTHORITYCHECK | ||
ABAP code using 7.40 inline data declarations to call FM TXX_VIEW_AUTHORITYCHECK
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.Search for further information about these or an SAP related objects