SAP RHPS_APP_SCHEME_WRITE Function Module for HR-PD: Create Appraisal Model (Relationships)









RHPS_APP_SCHEME_WRITE is a standard rhps app scheme write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HR-PD: Create Appraisal Model (Relationships) 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 rhps app scheme write FM, simply by entering the name RHPS_APP_SCHEME_WRITE 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_SCHEME_WRITE 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_SCHEME_WRITE'"HR-PD: Create Appraisal Model (Relationships)
EXPORTING
PLVAR = "Plan Version
OTYPE = "Object type
OBJID = "Object ID
* VTASK = 'D' "Update (B=Buffer,D=Online,V=Update,S=Sync)

TABLES
RELATION = "Relationships
* ERR_RELATION = "

EXCEPTIONS
NO_AUTHORITY = 1 RELATION_NOT_ALLOWED = 2 DATE_ERROR = 3 ERROR_DURING_INSERT = 4 UNDEFINED = 5
.



IMPORTING Parameters details for RHPS_APP_SCHEME_WRITE

PLVAR - Plan Version

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

OTYPE - Object type

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

OBJID - Object ID

Data type: P1000-OBJID
Optional: No
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)

TABLES Parameters details for RHPS_APP_SCHEME_WRITE

RELATION - Relationships

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

ERR_RELATION -

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

EXCEPTIONS details

NO_AUTHORITY - No Authorization

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

RELATION_NOT_ALLOWED - Relationship not allowed

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

DATE_ERROR -

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)

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_SCHEME_WRITE 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_plvar  TYPE P1000-PLVAR, "   
lt_relation  TYPE STANDARD TABLE OF HRPE_APPR, "   
lv_no_authority  TYPE HRPE_APPR, "   
lv_otype  TYPE P1000-OTYPE, "   
lt_err_relation  TYPE STANDARD TABLE OF HRPE_APPR, "   
lv_relation_not_allowed  TYPE HRPE_APPR, "   
lv_objid  TYPE P1000-OBJID, "   
lv_date_error  TYPE P1000, "   
lv_vtask  TYPE HRRHAP-VTASK, "   'D'
lv_error_during_insert  TYPE HRRHAP, "   
lv_undefined  TYPE HRRHAP. "   

  CALL FUNCTION 'RHPS_APP_SCHEME_WRITE'  "HR-PD: Create Appraisal Model (Relationships)
    EXPORTING
         PLVAR = lv_plvar
         OTYPE = lv_otype
         OBJID = lv_objid
         VTASK = lv_vtask
    TABLES
         RELATION = lt_relation
         ERR_RELATION = lt_err_relation
    EXCEPTIONS
        NO_AUTHORITY = 1
        RELATION_NOT_ALLOWED = 2
        DATE_ERROR = 3
        ERROR_DURING_INSERT = 4
        UNDEFINED = 5
. " RHPS_APP_SCHEME_WRITE




ABAP code using 7.40 inline data declarations to call FM RHPS_APP_SCHEME_WRITE

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 PLVAR FROM P1000 INTO @DATA(ld_plvar).
 
 
 
"SELECT single OTYPE FROM P1000 INTO @DATA(ld_otype).
 
 
 
"SELECT single OBJID FROM P1000 INTO @DATA(ld_objid).
 
 
"SELECT single VTASK FROM HRRHAP INTO @DATA(ld_vtask).
DATA(ld_vtask) = 'D'.
 
 
 


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!