SAP RS_B4HTRF_API_OBJECT_UPDATE Function Module for Get List of Objects of open Scope Definition Task List Runs
RS_B4HTRF_API_OBJECT_UPDATE is a standard rs b4htrf api object update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get List of Objects of open Scope Definition Task List Runs 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 rs b4htrf api object update FM, simply by entering the name RS_B4HTRF_API_OBJECT_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RS_B4HTRF_API
Program Name: SAPLRS_B4HTRF_API
Main Program: SAPLRS_B4HTRF_API
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RS_B4HTRF_API_OBJECT_UPDATE 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 'RS_B4HTRF_API_OBJECT_UPDATE'"Get List of Objects of open Scope Definition Task List Runs.
EXPORTING
* I_TLOGO = "BW: Object Type (TLOGO)
* I_OBJNM = "Object Name in Object Directory
* IT_OBJECT = "List of objects
* I_METADATA = '-' "Metadata is transferred
* I_DATA = '-' "Data is transferred
* I_REQUESTS = '-' "Requests are transferred
* I_REPLACE = ' ' "Replace all entries with same old_object
* I_SHELL = ' ' "Dummy, only needed in receiver
EXCEPTIONS
FAILED = 1
IMPORTING Parameters details for RS_B4HTRF_API_OBJECT_UPDATE
I_TLOGO - BW: Object Type (TLOGO)
Data type: RSTLOGOOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJNM - Object Name in Object Directory
Data type: SOBJ_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_OBJECT - List of objects
Data type: RSB4HPREP_T_OBJECT_MAPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_METADATA - Metadata is transferred
Data type: RS_BOOLDefault: '-'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_DATA - Data is transferred
Data type: RS_BOOLDefault: '-'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_REQUESTS - Requests are transferred
Data type: RS_BOOLDefault: '-'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_REPLACE - Replace all entries with same old_object
Data type: RS_BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SHELL - Dummy, only needed in receiver
Data type: RS_BOOLDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RS_B4HTRF_API_OBJECT_UPDATE 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_failed | TYPE STRING, " | |||
| lv_i_tlogo | TYPE RSTLOGO, " | |||
| lv_i_objnm | TYPE SOBJ_NAME, " | |||
| lv_it_object | TYPE RSB4HPREP_T_OBJECT_MAP, " | |||
| lv_i_metadata | TYPE RS_BOOL, " '-' | |||
| lv_i_data | TYPE RS_BOOL, " '-' | |||
| lv_i_requests | TYPE RS_BOOL, " '-' | |||
| lv_i_replace | TYPE RS_BOOL, " SPACE | |||
| lv_i_shell | TYPE RS_BOOL. " SPACE |
|   CALL FUNCTION 'RS_B4HTRF_API_OBJECT_UPDATE' "Get List of Objects of open Scope Definition Task List Runs |
| EXPORTING | ||
| I_TLOGO | = lv_i_tlogo | |
| I_OBJNM | = lv_i_objnm | |
| IT_OBJECT | = lv_it_object | |
| I_METADATA | = lv_i_metadata | |
| I_DATA | = lv_i_data | |
| I_REQUESTS | = lv_i_requests | |
| I_REPLACE | = lv_i_replace | |
| I_SHELL | = lv_i_shell | |
| EXCEPTIONS | ||
| FAILED = 1 | ||
| . " RS_B4HTRF_API_OBJECT_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM RS_B4HTRF_API_OBJECT_UPDATE
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.| DATA(ld_i_metadata) | = '-'. | |||
| DATA(ld_i_data) | = '-'. | |||
| DATA(ld_i_requests) | = '-'. | |||
| DATA(ld_i_replace) | = ' '. | |||
| DATA(ld_i_shell) | = ' '. | |||
Search for further information about these or an SAP related objects