SAP HR_ECM_IMPORT_FROM_PCP Function Module for Import values from Personnel Cost Planning
HR_ECM_IMPORT_FROM_PCP is a standard hr ecm import from pcp SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Import values from Personnel Cost Planning 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 hr ecm import from pcp FM, simply by entering the name HR_ECM_IMPORT_FROM_PCP into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRECM00BUDGETSTRUC
Program Name: SAPLHRECM00BUDGETSTRUC
Main Program: SAPLHRECM00BUDGETSTRUC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HR_ECM_IMPORT_FROM_PCP 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 'HR_ECM_IMPORT_FROM_PCP'"Import values from Personnel Cost Planning.
EXPORTING
* PLVAR = ' ' "Plan Version
* UICALL = ' ' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
MESSAGE_HANDLER = "HR Master Data: Messages
BUTYP = "Budget Type for Compensation Management
FINYR = "Budget period
OTYPE = "Object Type
BUDID = "Object ID
SOURCE = "Budget Determination
* PCPLAN = "Personnel Cost Plan
* CITEM = "
* XTEST = 'X' "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING
ERROR_LIST = "Return parameter table
IS_OK = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
CHANGING
BUDGET_STRUC_TAB = "Table of budget objects
IMPORTING Parameters details for HR_ECM_IMPORT_FROM_PCP
PLVAR - Plan Version
Data type: PLVARDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
UICALL - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: SPACE
Optional: Yes
Call by Reference: Yes
MESSAGE_HANDLER - HR Master Data: Messages
Data type: IF_HRPA_MESSAGE_HANDLEROptional: No
Call by Reference: Yes
BUTYP - Budget Type for Compensation Management
Data type: ECM_BUTYPOptional: No
Call by Reference: Yes
FINYR - Budget period
Data type: CMP_BU_FINYROptional: No
Call by Reference: Yes
OTYPE - Object Type
Data type: OTYPEOptional: No
Call by Reference: Yes
BUDID - Object ID
Data type: OBJEKTIDOptional: No
Call by Reference: Yes
SOURCE - Budget Determination
Data type: CMP_BU_SOURCEOptional: No
Call by Reference: Yes
PCPLAN - Personnel Cost Plan
Data type: HCP_PLAN_F4Optional: Yes
Call by Reference: Yes
CITEM -
Data type: HRHCP00_CITM_TEXT_RFCOptional: Yes
Call by Reference: Yes
XTEST - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HR_ECM_IMPORT_FROM_PCP
ERROR_LIST - Return parameter table
Data type: BAPIRET2_TOptional: No
Call by Reference: Yes
IS_OK - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE_DOptional: No
Call by Reference: Yes
CHANGING Parameters details for HR_ECM_IMPORT_FROM_PCP
BUDGET_STRUC_TAB - Table of budget objects
Data type: HRECM00BUDGET_STRUC_TABOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_ECM_IMPORT_FROM_PCP 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 PLVAR, " SPACE | |||
lv_error_list | TYPE BAPIRET2_T, " | |||
lv_budget_struc_tab | TYPE HRECM00BUDGET_STRUC_TAB, " | |||
lv_uicall | TYPE BOOLE_D, " SPACE | |||
lv_message_handler | TYPE IF_HRPA_MESSAGE_HANDLER, " | |||
lv_butyp | TYPE ECM_BUTYP, " | |||
lv_is_ok | TYPE BOOLE_D, " | |||
lv_finyr | TYPE CMP_BU_FINYR, " | |||
lv_otype | TYPE OTYPE, " | |||
lv_budid | TYPE OBJEKTID, " | |||
lv_source | TYPE CMP_BU_SOURCE, " | |||
lv_pcplan | TYPE HCP_PLAN_F4, " | |||
lv_citem | TYPE HRHCP00_CITM_TEXT_RFC, " | |||
lv_xtest | TYPE BOOLE_D. " 'X' |
  CALL FUNCTION 'HR_ECM_IMPORT_FROM_PCP' "Import values from Personnel Cost Planning |
EXPORTING | ||
PLVAR | = lv_plvar | |
UICALL | = lv_uicall | |
MESSAGE_HANDLER | = lv_message_handler | |
BUTYP | = lv_butyp | |
FINYR | = lv_finyr | |
OTYPE | = lv_otype | |
BUDID | = lv_budid | |
SOURCE | = lv_source | |
PCPLAN | = lv_pcplan | |
CITEM | = lv_citem | |
XTEST | = lv_xtest | |
IMPORTING | ||
ERROR_LIST | = lv_error_list | |
IS_OK | = lv_is_ok | |
CHANGING | ||
BUDGET_STRUC_TAB | = lv_budget_struc_tab | |
. " HR_ECM_IMPORT_FROM_PCP |
ABAP code using 7.40 inline data declarations to call FM HR_ECM_IMPORT_FROM_PCP
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.DATA(ld_plvar) | = ' '. | |||
DATA(ld_uicall) | = ' '. | |||
DATA(ld_xtest) | = 'X'. | |||
Search for further information about these or an SAP related objects