SAP OIUREP_TRBT550 Function Module for OIUREP_TRBT550
OIUREP_TRBT550 is a standard oiurep trbt550 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for OIUREP_TRBT550 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 oiurep trbt550 FM, simply by entering the name OIUREP_TRBT550 into the relevant SAP transaction such as SE37 or SE38.
Function Group: OIUREP_TRBT550
Program Name: SAPLOIUREP_TRBT550
Main Program: SAPLOIUREP_TRBT550
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function OIUREP_TRBT550 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 'OIUREP_TRBT550'"OIUREP_TRBT550.
EXPORTING
LS_PARAM = "Parameter String Layout
TABLES
TEMP1 = "ROIUREP_trbf0240
EXCEPTIONS
GOBACK = 1 WARNING = 2 FAILED = 3
IMPORTING Parameters details for OIUREP_TRBT550
LS_PARAM - Parameter String Layout
Data type: OIUH_DD_CONFIG-PARM_LAYOUTOptional: No
Call by Reference: Yes
TABLES Parameters details for OIUREP_TRBT550
TEMP1 - ROIUREP_trbf0240
Data type: ROIUREP_TRBF0240Optional: No
Call by Reference: Yes
EXCEPTIONS details
GOBACK -
Data type:Optional: No
Call by Reference: Yes
WARNING -
Data type:Optional: No
Call by Reference: Yes
FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for OIUREP_TRBT550 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: | ||||
| lt_temp1 | TYPE STANDARD TABLE OF ROIUREP_TRBF0240, " | |||
| lv_goback | TYPE ROIUREP_TRBF0240, " | |||
| lv_ls_param | TYPE OIUH_DD_CONFIG-PARM_LAYOUT, " | |||
| lv_warning | TYPE OIUH_DD_CONFIG, " | |||
| lv_failed | TYPE OIUH_DD_CONFIG. " |
|   CALL FUNCTION 'OIUREP_TRBT550' "OIUREP_TRBT550 |
| EXPORTING | ||
| LS_PARAM | = lv_ls_param | |
| TABLES | ||
| TEMP1 | = lt_temp1 | |
| EXCEPTIONS | ||
| GOBACK = 1 | ||
| WARNING = 2 | ||
| FAILED = 3 | ||
| . " OIUREP_TRBT550 | ||
ABAP code using 7.40 inline data declarations to call FM OIUREP_TRBT550
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 PARM_LAYOUT FROM OIUH_DD_CONFIG INTO @DATA(ld_ls_param). | ||||
Search for further information about these or an SAP related objects