SAP AUTH_TRACE_WRITE_USOBHASH Function Module for
AUTH_TRACE_WRITE_USOBHASH is a standard auth trace write usobhash 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 auth trace write usobhash FM, simply by entering the name AUTH_TRACE_WRITE_USOBHASH into the relevant SAP transaction such as SE37 or SE38.
Function Group: SAUTHTRACE
Program Name: SAPLSAUTHTRACE
Main Program: SAPLSAUTHTRACE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function AUTH_TRACE_WRITE_USOBHASH 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 'AUTH_TRACE_WRITE_USOBHASH'".
EXPORTING
PGMID = "Program ID in requests and tasks
OBJECT = "Object Type
OBJ_NAME = "Object Name in Object Directory
SERVICE_TYPE = "Name of External Service
SERVICE = "Name of the Service
IMPORTING
HASH_VALUE = "Program, transaction or function module name
HASH_VALUE_TYPE = "Report type
EXCEPTIONS
HASH_ERROR = 1 HASH_INVALID_INPUT = 2 HASH_TOO_LONG = 3
IMPORTING Parameters details for AUTH_TRACE_WRITE_USOBHASH
PGMID - Program ID in requests and tasks
Data type: USOBHASH-PGMIDOptional: No
Call by Reference: Yes
OBJECT - Object Type
Data type: USOBHASH-OBJECTOptional: No
Call by Reference: Yes
OBJ_NAME - Object Name in Object Directory
Data type: USOBHASH-OBJ_NAMEOptional: No
Call by Reference: Yes
SERVICE_TYPE - Name of External Service
Data type: USOBHASH-SERVICE_TYPEOptional: No
Call by Reference: Yes
SERVICE - Name of the Service
Data type: USOBHASH-SERVICEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for AUTH_TRACE_WRITE_USOBHASH
HASH_VALUE - Program, transaction or function module name
Data type: USOBHASH-NAMEOptional: No
Call by Reference: Yes
HASH_VALUE_TYPE - Report type
Data type: USOBHASH-TYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
HASH_ERROR - Error in hash function
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
HASH_INVALID_INPUT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
HASH_TOO_LONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for AUTH_TRACE_WRITE_USOBHASH 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_pgmid | TYPE USOBHASH-PGMID, " | |||
| lv_hash_error | TYPE USOBHASH, " | |||
| lv_hash_value | TYPE USOBHASH-NAME, " | |||
| lv_object | TYPE USOBHASH-OBJECT, " | |||
| lv_hash_value_type | TYPE USOBHASH-TYPE, " | |||
| lv_hash_invalid_input | TYPE USOBHASH, " | |||
| lv_obj_name | TYPE USOBHASH-OBJ_NAME, " | |||
| lv_hash_too_long | TYPE USOBHASH, " | |||
| lv_service_type | TYPE USOBHASH-SERVICE_TYPE, " | |||
| lv_service | TYPE USOBHASH-SERVICE. " |
|   CALL FUNCTION 'AUTH_TRACE_WRITE_USOBHASH' " |
| EXPORTING | ||
| PGMID | = lv_pgmid | |
| OBJECT | = lv_object | |
| OBJ_NAME | = lv_obj_name | |
| SERVICE_TYPE | = lv_service_type | |
| SERVICE | = lv_service | |
| IMPORTING | ||
| HASH_VALUE | = lv_hash_value | |
| HASH_VALUE_TYPE | = lv_hash_value_type | |
| EXCEPTIONS | ||
| HASH_ERROR = 1 | ||
| HASH_INVALID_INPUT = 2 | ||
| HASH_TOO_LONG = 3 | ||
| . " AUTH_TRACE_WRITE_USOBHASH | ||
ABAP code using 7.40 inline data declarations to call FM AUTH_TRACE_WRITE_USOBHASH
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 PGMID FROM USOBHASH INTO @DATA(ld_pgmid). | ||||
| "SELECT single NAME FROM USOBHASH INTO @DATA(ld_hash_value). | ||||
| "SELECT single OBJECT FROM USOBHASH INTO @DATA(ld_object). | ||||
| "SELECT single TYPE FROM USOBHASH INTO @DATA(ld_hash_value_type). | ||||
| "SELECT single OBJ_NAME FROM USOBHASH INTO @DATA(ld_obj_name). | ||||
| "SELECT single SERVICE_TYPE FROM USOBHASH INTO @DATA(ld_service_type). | ||||
| "SELECT single SERVICE FROM USOBHASH INTO @DATA(ld_service). | ||||
Search for further information about these or an SAP related objects