SAP RHPS_APP_CRITERION_CREATE Function Module for









RHPS_APP_CRITERION_CREATE is a standard rhps app criterion create 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 rhps app criterion create FM, simply by entering the name RHPS_APP_CRITERION_CREATE into the relevant SAP transaction such as SE37 or SE38.

Function Group: RHPS
Program Name: SAPLRHPS
Main Program: SAPLRHPS
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function RHPS_APP_CRITERION_CREATE 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 'RHPS_APP_CRITERION_CREATE'"
  EXPORTING
*  LANGU = SY-LANGU "Language
*  VENDDA = '99991231' "
*  VPAD47 =  "
*  INFTY1044 =  "
*  INHERITED_1048 = 'X' "
*  VTASK = 'D' "Update (B=Buffer,D=Online,V=Update,S=Sync)
   PLVAR =  "Plan Version
*  EXT_NUMBER = '00000000' "External Number
   STEXT =  "Description
*  BEGDA = '19000101' "Start Date
*  ENDDA = '99991231' "End Date
*  VOTYPE =  "
*  VOBJID =  "
*  VBEGDA = '19000101' "

 IMPORTING
   OBJID =  "Object ID

TABLES
*  PTXT1002 =  "Description
*  DESCR_PT1048 =  "Proficiency Description

EXCEPTIONS
   TEXT_REQUIRED = 1    INVALID_DATE = 2    ERROR_DURING_INSERT = 3    WRONG_INFOTYP_INFO = 4    UNDEFINED = 5
.



IMPORTING Parameters details for RHPS_APP_CRITERION_CREATE

LANGU - Language

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

VENDDA -

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

VPAD47 -

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

INFTY1044 -

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

INHERITED_1048 -

Data type: CHAR1
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VTASK - Update (B=Buffer,D=Online,V=Update,S=Sync)

Data type: HRRHAP-VTASK
Default: 'D'
Optional: Yes
Call by Reference: No ( called with pass by value option)

PLVAR - Plan Version

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

EXT_NUMBER - External Number

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

STEXT - Description

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

BEGDA - Start Date

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

ENDDA - End Date

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

VOTYPE -

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

VOBJID -

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

VBEGDA -

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

EXPORTING Parameters details for RHPS_APP_CRITERION_CREATE

OBJID - Object ID

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

TABLES Parameters details for RHPS_APP_CRITERION_CREATE

PTXT1002 - Description

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

DESCR_PT1048 - Proficiency Description

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

EXCEPTIONS details

TEXT_REQUIRED -

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)

ERROR_DURING_INSERT - Error during Insert

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

WRONG_INFOTYP_INFO -

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

UNDEFINED - Other Error

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

Copy and paste ABAP code example for RHPS_APP_CRITERION_CREATE 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_langu  TYPE SY-LANGU, "   SY-LANGU
lv_objid  TYPE HRP1000-OBJID, "   
lt_ptxt1002  TYPE STANDARD TABLE OF PT1002, "   
lv_text_required  TYPE PT1002, "   
lv_vendda  TYPE P1000-ENDDA, "   '99991231'
lv_vpad47  TYPE PAD47, "   
lv_infty1044  TYPE HRI1044, "   
lv_inherited_1048  TYPE CHAR1, "   'X'
lv_vtask  TYPE HRRHAP-VTASK, "   'D'
lv_plvar  TYPE P1000-PLVAR, "   
lt_descr_pt1048  TYPE STANDARD TABLE OF PT1048, "   
lv_invalid_date  TYPE PT1048, "   
lv_ext_number  TYPE HRP1000-OBJID, "   '00000000'
lv_error_during_insert  TYPE HRP1000, "   
lv_stext  TYPE P1000-STEXT, "   
lv_wrong_infotyp_info  TYPE P1000, "   
lv_begda  TYPE P1000-BEGDA, "   '19000101'
lv_undefined  TYPE P1000, "   
lv_endda  TYPE P1000-ENDDA, "   '99991231'
lv_votype  TYPE P1000-OTYPE, "   
lv_vobjid  TYPE P1000-OBJID, "   
lv_vbegda  TYPE P1000-BEGDA. "   '19000101'

  CALL FUNCTION 'RHPS_APP_CRITERION_CREATE'  "
    EXPORTING
         LANGU = lv_langu
         VENDDA = lv_vendda
         VPAD47 = lv_vpad47
         INFTY1044 = lv_infty1044
         INHERITED_1048 = lv_inherited_1048
         VTASK = lv_vtask
         PLVAR = lv_plvar
         EXT_NUMBER = lv_ext_number
         STEXT = lv_stext
         BEGDA = lv_begda
         ENDDA = lv_endda
         VOTYPE = lv_votype
         VOBJID = lv_vobjid
         VBEGDA = lv_vbegda
    IMPORTING
         OBJID = lv_objid
    TABLES
         PTXT1002 = lt_ptxt1002
         DESCR_PT1048 = lt_descr_pt1048
    EXCEPTIONS
        TEXT_REQUIRED = 1
        INVALID_DATE = 2
        ERROR_DURING_INSERT = 3
        WRONG_INFOTYP_INFO = 4
        UNDEFINED = 5
. " RHPS_APP_CRITERION_CREATE




ABAP code using 7.40 inline data declarations to call FM RHPS_APP_CRITERION_CREATE

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 LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
"SELECT single OBJID FROM HRP1000 INTO @DATA(ld_objid).
 
 
 
"SELECT single ENDDA FROM P1000 INTO @DATA(ld_vendda).
DATA(ld_vendda) = '99991231'.
 
 
 
DATA(ld_inherited_1048) = 'X'.
 
"SELECT single VTASK FROM HRRHAP INTO @DATA(ld_vtask).
DATA(ld_vtask) = 'D'.
 
"SELECT single PLVAR FROM P1000 INTO @DATA(ld_plvar).
 
 
 
"SELECT single OBJID FROM HRP1000 INTO @DATA(ld_ext_number).
DATA(ld_ext_number) = '00000000'.
 
 
"SELECT single STEXT FROM P1000 INTO @DATA(ld_stext).
 
 
"SELECT single BEGDA FROM P1000 INTO @DATA(ld_begda).
DATA(ld_begda) = '19000101'.
 
 
"SELECT single ENDDA FROM P1000 INTO @DATA(ld_endda).
DATA(ld_endda) = '99991231'.
 
"SELECT single OTYPE FROM P1000 INTO @DATA(ld_votype).
 
"SELECT single OBJID FROM P1000 INTO @DATA(ld_vobjid).
 
"SELECT single BEGDA FROM P1000 INTO @DATA(ld_vbegda).
DATA(ld_vbegda) = '19000101'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!