SAP REYC_GUI_CAPPING_PBO Function Module for PBO des Parent-Screens (initialisiert Subscreen)

Search SAP Function Modules

REYC_GUI_CAPPING_PBO is a standard reyc gui capping pbo SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PBO des Parent-Screens (initialisiert Subscreen) 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 reyc gui capping pbo FM, simply by entering the name REYC_GUI_CAPPING_PBO into the relevant SAP transaction such as SE37 or SE38.

Function Group: REYC_GUI_CAPPING
Program Name: SAPLREYC_GUI_CAPPING
Main Program: SAPLREYC_GUI_CAPPING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function REYC_GUI_CAPPING_PBO 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 'REYC_GUI_CAPPING_PBO'"PBO des Parent-Screens (initialisiert Subscreen)
  EXPORTING
   IO_TERM_MNGR =  "
   ID_TERMTYPE =  "
   ID_TERMNO =  "
   ID_VALIDFROM =  "
*  IF_READONLY =  "
*  IO_NAVIGATION_DATA =  "
*  IO_CURRENT_NAV_DATA =  "

 IMPORTING
   ES_SUBSCREEN =  "

.

IMPORTING Parameters details for REYC_GUI_CAPPING_PBO

IO_TERM_MNGR -

Data type: IF_RETM_TERM_MNGR
Optional: No
Call by Reference: No ( called with pass by value option)

ID_TERMTYPE -

Data type: RETM_TERM-TERMTYPE
Optional: No
Call by Reference: No ( called with pass by value option)

ID_TERMNO -

Data type: RETM_TERM-TERMNO
Optional: No
Call by Reference: No ( called with pass by value option)

ID_VALIDFROM -

Data type: RETMTERMVALIDFROM
Optional: No
Call by Reference: No ( called with pass by value option)

IF_READONLY -

Data type: ABAP_BOOL
Optional: Yes
Call by Reference: No ( called with pass by value option)

IO_NAVIGATION_DATA -

Data type: CL_RECA_DATA_CONTAINER
Optional: Yes
Call by Reference: No ( called with pass by value option)

IO_CURRENT_NAV_DATA -

Data type: CL_RECA_DATA_CONTAINER
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for REYC_GUI_CAPPING_PBO

ES_SUBSCREEN -

Data type: RECASCREEN
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for REYC_GUI_CAPPING_PBO 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.

ABAP code using 7.40 inline data declarations to call FM REYC_GUI_CAPPING_PBO

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