SAP RHPT_POPUP_TRAINPLANGROUP Function Module for

Search SAP Function Modules

RHPT_POPUP_TRAINPLANGROUP is a standard rhpt popup trainplangroup 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 rhpt popup trainplangroup FM, simply by entering the name RHPT_POPUP_TRAINPLANGROUP into the relevant SAP transaction such as SE37 or SE38.

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

Function RHPT_POPUP_TRAINPLANGROUP 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 'RHPT_POPUP_TRAINPLANGROUP'"
  EXPORTING
   PLVAR =  "
*  Y1 = 2 "
*  OBJID =  "
*  STEXT =  "
*  BEGDA = '19000101' "
*  ENDDA = '99991231' "
*  BASE_OTYPE =  "
*  BASE_OBJID =  "
*  CHANGE =  "
*  X1 = 30 "

 IMPORTING
   MODIFIED =  "
   OBJID =  "
   STEXT =  "
   BEGDA =  "
   ENDDA =  "

EXCEPTIONS
   NOT_FOUND = 1    INVALID_DATE = 2 

.

IMPORTING Parameters details for RHPT_POPUP_TRAINPLANGROUP

PLVAR -

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

Y1 -

Data type: SY-CUROW
Default: 2
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJID -

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

STEXT -

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

BEGDA -

Data type: HRP1000-BEGDA
Default: '19000101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

ENDDA -

Data type: HRP1000-ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: No ( called with pass by value option)

BASE_OTYPE -

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

BASE_OBJID -

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

CHANGE -

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

X1 -

Data type: SY-CUCOL
Default: 30
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RHPT_POPUP_TRAINPLANGROUP

MODIFIED -

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

OBJID -

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

STEXT -

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

BEGDA -

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

ENDDA -

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

EXCEPTIONS details

NOT_FOUND -

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

INVALID_DATE -

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

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

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