SAP RH_CPCALC_PLANNING_GROUP Function Module for
RH_CPCALC_PLANNING_GROUP is a standard rh cpcalc planning group 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 rh cpcalc planning group FM, simply by entering the name RH_CPCALC_PLANNING_GROUP into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHPF
Program Name: SAPLRHPF
Main Program:
Appliation area: H
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_CPCALC_PLANNING_GROUP 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 'RH_CPCALC_PLANNING_GROUP'".
EXPORTING
PLAN_BEGDA = "
PLAN_ENDDA = "
PLAN_ABART = "
PLAN_CURCY = "
* PLAN_CURDT = SY-DATUM "
* PLAN_CURTY = 'M ' "
* PLAN_CALCM = ' ' "
* NO_EMPTY_LINE = ' ' "
* SORT_TABLE = 'X' "
TABLES
ORG_COST = "
ORG_TEXT = "
POS_COST = "
POS_TEXT = "
ORG_CTYPE = "
COST_TAB = "
COST_PER_COST_CENTER = "
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLRHPF_001 Personnel Cost Planning: User Exit for Cost Elements for Person
IMPORTING Parameters details for RH_CPCALC_PLANNING_GROUP
PLAN_BEGDA -
Data type: PP0N-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
PLAN_ENDDA -
Data type: PP0N-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
PLAN_ABART -
Data type: PP0N-ABARTOptional: No
Call by Reference: No ( called with pass by value option)
PLAN_CURCY -
Data type: PP0N-CURCYOptional: No
Call by Reference: No ( called with pass by value option)
PLAN_CURDT -
Data type: PP0N-CURDTDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
PLAN_CURTY -
Data type: PP0N-CURTPDefault: 'M '
Optional: Yes
Call by Reference: No ( called with pass by value option)
PLAN_CALCM -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_EMPTY_LINE -
Data type: PLOG-HISTODefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SORT_TABLE -
Data type: PLOG-HISTODefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RH_CPCALC_PLANNING_GROUP
ORG_COST -
Data type: PPCOCOptional: No
Call by Reference: No ( called with pass by value option)
ORG_TEXT -
Data type: PPCOTOptional: No
Call by Reference: No ( called with pass by value option)
POS_COST -
Data type: PPCPCOptional: No
Call by Reference: No ( called with pass by value option)
POS_TEXT -
Data type: PPCOTOptional: No
Call by Reference: No ( called with pass by value option)
ORG_CTYPE -
Data type: PPCOWOptional: No
Call by Reference: No ( called with pass by value option)
COST_TAB -
Data type: PPCWTOptional: No
Call by Reference: No ( called with pass by value option)
COST_PER_COST_CENTER -
Data type: PPCCOOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RH_CPCALC_PLANNING_GROUP 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: | ||||
| lt_org_cost | TYPE STANDARD TABLE OF PPCOC, " | |||
| lv_plan_begda | TYPE PP0N-BEGDA, " | |||
| lt_org_text | TYPE STANDARD TABLE OF PPCOT, " | |||
| lv_plan_endda | TYPE PP0N-ENDDA, " | |||
| lt_pos_cost | TYPE STANDARD TABLE OF PPCPC, " | |||
| lv_plan_abart | TYPE PP0N-ABART, " | |||
| lt_pos_text | TYPE STANDARD TABLE OF PPCOT, " | |||
| lv_plan_curcy | TYPE PP0N-CURCY, " | |||
| lt_org_ctype | TYPE STANDARD TABLE OF PPCOW, " | |||
| lv_plan_curdt | TYPE PP0N-CURDT, " SY-DATUM | |||
| lt_cost_tab | TYPE STANDARD TABLE OF PPCWT, " | |||
| lv_plan_curty | TYPE PP0N-CURTP, " 'M ' | |||
| lv_plan_calcm | TYPE PP0N, " SPACE | |||
| lt_cost_per_cost_center | TYPE STANDARD TABLE OF PPCCO, " | |||
| lv_no_empty_line | TYPE PLOG-HISTO, " SPACE | |||
| lv_sort_table | TYPE PLOG-HISTO. " 'X' |
|   CALL FUNCTION 'RH_CPCALC_PLANNING_GROUP' " |
| EXPORTING | ||
| PLAN_BEGDA | = lv_plan_begda | |
| PLAN_ENDDA | = lv_plan_endda | |
| PLAN_ABART | = lv_plan_abart | |
| PLAN_CURCY | = lv_plan_curcy | |
| PLAN_CURDT | = lv_plan_curdt | |
| PLAN_CURTY | = lv_plan_curty | |
| PLAN_CALCM | = lv_plan_calcm | |
| NO_EMPTY_LINE | = lv_no_empty_line | |
| SORT_TABLE | = lv_sort_table | |
| TABLES | ||
| ORG_COST | = lt_org_cost | |
| ORG_TEXT | = lt_org_text | |
| POS_COST | = lt_pos_cost | |
| POS_TEXT | = lt_pos_text | |
| ORG_CTYPE | = lt_org_ctype | |
| COST_TAB | = lt_cost_tab | |
| COST_PER_COST_CENTER | = lt_cost_per_cost_center | |
| . " RH_CPCALC_PLANNING_GROUP | ||
ABAP code using 7.40 inline data declarations to call FM RH_CPCALC_PLANNING_GROUP
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 BEGDA FROM PP0N INTO @DATA(ld_plan_begda). | ||||
| "SELECT single ENDDA FROM PP0N INTO @DATA(ld_plan_endda). | ||||
| "SELECT single ABART FROM PP0N INTO @DATA(ld_plan_abart). | ||||
| "SELECT single CURCY FROM PP0N INTO @DATA(ld_plan_curcy). | ||||
| "SELECT single CURDT FROM PP0N INTO @DATA(ld_plan_curdt). | ||||
| DATA(ld_plan_curdt) | = SY-DATUM. | |||
| "SELECT single CURTP FROM PP0N INTO @DATA(ld_plan_curty). | ||||
| DATA(ld_plan_curty) | = 'M '. | |||
| DATA(ld_plan_calcm) | = ' '. | |||
| "SELECT single HISTO FROM PLOG INTO @DATA(ld_no_empty_line). | ||||
| DATA(ld_no_empty_line) | = ' '. | |||
| "SELECT single HISTO FROM PLOG INTO @DATA(ld_sort_table). | ||||
| DATA(ld_sort_table) | = 'X'. | |||
Search for further information about these or an SAP related objects