SAP PS_DO_PROFILING_FM Function Module for Perform Profiling
PS_DO_PROFILING_FM is a standard ps do profiling fm SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Perform Profiling 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 ps do profiling fm FM, simply by entering the name PS_DO_PROFILING_FM into the relevant SAP transaction such as SE37 or SE38.
Function Group: PS_HLP_API_FG
Program Name: SAPLPS_HLP_API_FG
Main Program: SAPLPS_HLP_API_FG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function PS_DO_PROFILING_FM 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 'PS_DO_PROFILING_FM'"Perform Profiling.
EXPORTING
IS_NODE_INFO = "PSHLP SUB NODE Definition
* IV_ACL_XML = "
IT_NODE_DATA = "Master Data
IT_INIT_PROFILES = "PSHLP Profile Table Type
* IV_PROJ_XML = "
* IV_WBS_XML = "
* IV_OVERVIEW_TYPE = "Object Type
IV_TABLE_TYPE = "Name of table type
* IV_RFC_FLAG = ABAP_TRUE "abap_true
* IV_STATUS_XML = "
IMPORTING
ET_PROFILES = "Table Type PSHLP Celltab
IMPORTING Parameters details for PS_DO_PROFILING_FM
IS_NODE_INFO - PSHLP SUB NODE Definition
Data type: PSHLP_UI_SUBNODE_DEF_STOptional: No
Call by Reference: No ( called with pass by value option)
IV_ACL_XML -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_NODE_DATA - Master Data
Data type: STRINGOptional: No
Call by Reference: No ( called with pass by value option)
IT_INIT_PROFILES - PSHLP Profile Table Type
Data type: PSHLP_PROFILES_TTOptional: No
Call by Reference: No ( called with pass by value option)
IV_PROJ_XML -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_WBS_XML -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OVERVIEW_TYPE - Object Type
Data type: J_OBARTOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_TABLE_TYPE - Name of table type
Data type: TTYPENAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_RFC_FLAG - abap_true
Data type: BOOLE_DDefault: ABAP_TRUE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_STATUS_XML -
Data type: STRINGOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for PS_DO_PROFILING_FM
ET_PROFILES - Table Type PSHLP Celltab
Data type: PSHLP_CELLTAB_TTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for PS_DO_PROFILING_FM 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_et_profiles | TYPE PSHLP_CELLTAB_TT, " | |||
| lv_is_node_info | TYPE PSHLP_UI_SUBNODE_DEF_ST, " | |||
| lv_iv_acl_xml | TYPE STRING, " | |||
| lv_it_node_data | TYPE STRING, " | |||
| lv_it_init_profiles | TYPE PSHLP_PROFILES_TT, " | |||
| lv_iv_proj_xml | TYPE STRING, " | |||
| lv_iv_wbs_xml | TYPE STRING, " | |||
| lv_iv_overview_type | TYPE J_OBART, " | |||
| lv_iv_table_type | TYPE TTYPENAME, " | |||
| lv_iv_rfc_flag | TYPE BOOLE_D, " ABAP_TRUE | |||
| lv_iv_status_xml | TYPE STRING. " |
|   CALL FUNCTION 'PS_DO_PROFILING_FM' "Perform Profiling |
| EXPORTING | ||
| IS_NODE_INFO | = lv_is_node_info | |
| IV_ACL_XML | = lv_iv_acl_xml | |
| IT_NODE_DATA | = lv_it_node_data | |
| IT_INIT_PROFILES | = lv_it_init_profiles | |
| IV_PROJ_XML | = lv_iv_proj_xml | |
| IV_WBS_XML | = lv_iv_wbs_xml | |
| IV_OVERVIEW_TYPE | = lv_iv_overview_type | |
| IV_TABLE_TYPE | = lv_iv_table_type | |
| IV_RFC_FLAG | = lv_iv_rfc_flag | |
| IV_STATUS_XML | = lv_iv_status_xml | |
| IMPORTING | ||
| ET_PROFILES | = lv_et_profiles | |
| . " PS_DO_PROFILING_FM | ||
ABAP code using 7.40 inline data declarations to call FM PS_DO_PROFILING_FM
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_iv_rfc_flag) | = ABAP_TRUE. | |||
Search for further information about these or an SAP related objects