SAP RHPP_COMMON_PROFILE_WRITE Function Module for

Search SAP Function Modules

RHPP_COMMON_PROFILE_WRITE is a standard rhpp common profile write 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 rhpp common profile write FM, simply by entering the name RHPP_COMMON_PROFILE_WRITE into the relevant SAP transaction such as SE37 or SE38.

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

Function RHPP_COMMON_PROFILE_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 'RHPP_COMMON_PROFILE_WRITE'"
  EXPORTING
   SUBTY =  "Link text strings
   PLVAR =  "Plan Version
   OTYPE =  "Object type
   OBJID =  "Object ID
*  VTASK = 'D' "
*  NO_AUTHORITY_CHECK =  "

TABLES
   PROFILE =  "
*  ERR_PROFILE =  "

EXCEPTIONS
   NO_AUTHORITY = 1    ERROR_DURING_INSERT = 2    WRONG_OTYPE = 3    OBJECT_NOT_FOUND = 4    OBJECT_REQUIRED = 5    TIME_NOT_VALID = 6    WRONG_DATE_FORMAT = 7    UNDEFINED = 8 

.

IMPORTING Parameters details for RHPP_COMMON_PROFILE_WRITE

SUBTY - Link text strings

Data type: HRP1001-SUBTY
Optional: No
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)

OTYPE - Object type

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

OBJID - Object ID

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

VTASK -

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

NO_AUTHORITY_CHECK -

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

TABLES Parameters details for RHPP_COMMON_PROFILE_WRITE

PROFILE -

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

ERR_PROFILE -

Data type: HRPE_RELAS
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)

ERROR_DURING_INSERT - Error during Insert

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

WRONG_OTYPE - Unauth. object type

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

OBJECT_NOT_FOUND - Object does not exist

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

OBJECT_REQUIRED -

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

TIME_NOT_VALID -

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

WRONG_DATE_FORMAT -

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 RHPP_COMMON_PROFILE_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.

ABAP code using 7.40 inline data declarations to call FM RHPP_COMMON_PROFILE_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.

Search for further information about these or an SAP related objects