SAP BBP_PDH_WFL_TRACE Function Module for
BBP_PDH_WFL_TRACE is a standard bbp pdh wfl trace 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 bbp pdh wfl trace FM, simply by entering the name BBP_PDH_WFL_TRACE into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_WFLH
Program Name: SAPLBBP_WFLH
Main Program: SAPLBBP_WFLH
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PDH_WFL_TRACE 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 'BBP_PDH_WFL_TRACE'".
EXPORTING
* IV_OBJECT_ID = "
* IV_ACTUAL_INDEX = "
* IV_OBJECT_TYPE = "
* IV_USER = "
* IV_IN_DIALOG = "
IV_FUNCTION = "
* IV_WORKITEM_ID = "
* IV_MAIN_WORKITEM_ID = "
* IV_ACTION = "
* IV_ADD_INFO = "
CHANGING
* CV_IN_DIALOG = "
TABLES
* IT_BADI_APPROVER_LIST = "
* IT_BADI_APPR_ITEMS = "
* IT_APPROVAL_TABLE = "
* IT_ITEM_APPROVAL = "
* IT_ITEM_APPROVAL_OBJ = "
IMPORTING Parameters details for BBP_PDH_WFL_TRACE
IV_OBJECT_ID -
Data type: CRMD_ORDERADM_H-OBJECT_IDOptional: Yes
Call by Reference: Yes
IV_ACTUAL_INDEX -
Data type: SWH_NUMC10Optional: Yes
Call by Reference: Yes
IV_OBJECT_TYPE -
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: Yes
Call by Reference: Yes
IV_USER -
Data type: SYST-UNAMEOptional: Yes
Call by Reference: Yes
IV_IN_DIALOG -
Data type: XFELDOptional: Yes
Call by Reference: Yes
IV_FUNCTION -
Data type: BBP_WFL_TRACE-FUNCTIONOptional: No
Call by Reference: Yes
IV_WORKITEM_ID -
Data type: BBP_WFL_TRACE-WORKITEMOptional: Yes
Call by Reference: Yes
IV_MAIN_WORKITEM_ID -
Data type: BBP_WFL_TRACE-MAIN_WIOptional: Yes
Call by Reference: Yes
IV_ACTION -
Data type: BBP_WFL_TRACE-ACTIONOptional: Yes
Call by Reference: Yes
IV_ADD_INFO -
Data type: BBP_WFL_TRACE-ADD_INFOOptional: Yes
Call by Reference: Yes
CHANGING Parameters details for BBP_PDH_WFL_TRACE
CV_IN_DIALOG -
Data type: XFELDOptional: Yes
Call by Reference: Yes
TABLES Parameters details for BBP_PDH_WFL_TRACE
IT_BADI_APPROVER_LIST -
Data type: BBPT_WFL_APPROVAL_TABLE_BADIOptional: Yes
Call by Reference: Yes
IT_BADI_APPR_ITEMS -
Data type: BBPT_WFL_ITEM_APPROVAL_BADIOptional: Yes
Call by Reference: Yes
IT_APPROVAL_TABLE -
Data type: BBP_WFL_APPROVAL_TABLEOptional: Yes
Call by Reference: Yes
IT_ITEM_APPROVAL -
Data type: BBPS_WFL_ITEM_APPROVALOptional: Yes
Call by Reference: Yes
IT_ITEM_APPROVAL_OBJ -
Data type: BBPS_WFL_ITEM_APPROVAL_OBJOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PDH_WFL_TRACE 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_cv_in_dialog | TYPE XFELD, " | |||
| lv_iv_object_id | TYPE CRMD_ORDERADM_H-OBJECT_ID, " | |||
| lt_it_badi_approver_list | TYPE STANDARD TABLE OF BBPT_WFL_APPROVAL_TABLE_BADI, " | |||
| lv_iv_actual_index | TYPE SWH_NUMC10, " | |||
| lv_iv_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lt_it_badi_appr_items | TYPE STANDARD TABLE OF BBPT_WFL_ITEM_APPROVAL_BADI, " | |||
| lv_iv_user | TYPE SYST-UNAME, " | |||
| lt_it_approval_table | TYPE STANDARD TABLE OF BBP_WFL_APPROVAL_TABLE, " | |||
| lv_iv_in_dialog | TYPE XFELD, " | |||
| lt_it_item_approval | TYPE STANDARD TABLE OF BBPS_WFL_ITEM_APPROVAL, " | |||
| lv_iv_function | TYPE BBP_WFL_TRACE-FUNCTION, " | |||
| lt_it_item_approval_obj | TYPE STANDARD TABLE OF BBPS_WFL_ITEM_APPROVAL_OBJ, " | |||
| lv_iv_workitem_id | TYPE BBP_WFL_TRACE-WORKITEM, " | |||
| lv_iv_main_workitem_id | TYPE BBP_WFL_TRACE-MAIN_WI, " | |||
| lv_iv_action | TYPE BBP_WFL_TRACE-ACTION, " | |||
| lv_iv_add_info | TYPE BBP_WFL_TRACE-ADD_INFO. " |
|   CALL FUNCTION 'BBP_PDH_WFL_TRACE' " |
| EXPORTING | ||
| IV_OBJECT_ID | = lv_iv_object_id | |
| IV_ACTUAL_INDEX | = lv_iv_actual_index | |
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_USER | = lv_iv_user | |
| IV_IN_DIALOG | = lv_iv_in_dialog | |
| IV_FUNCTION | = lv_iv_function | |
| IV_WORKITEM_ID | = lv_iv_workitem_id | |
| IV_MAIN_WORKITEM_ID | = lv_iv_main_workitem_id | |
| IV_ACTION | = lv_iv_action | |
| IV_ADD_INFO | = lv_iv_add_info | |
| CHANGING | ||
| CV_IN_DIALOG | = lv_cv_in_dialog | |
| TABLES | ||
| IT_BADI_APPROVER_LIST | = lt_it_badi_approver_list | |
| IT_BADI_APPR_ITEMS | = lt_it_badi_appr_items | |
| IT_APPROVAL_TABLE | = lt_it_approval_table | |
| IT_ITEM_APPROVAL | = lt_it_item_approval | |
| IT_ITEM_APPROVAL_OBJ | = lt_it_item_approval_obj | |
| . " BBP_PDH_WFL_TRACE | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PDH_WFL_TRACE
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 OBJECT_ID FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_id). | ||||
| "SELECT single OBJECT_TYPE FROM CRMD_ORDERADM_H INTO @DATA(ld_iv_object_type). | ||||
| "SELECT single UNAME FROM SYST INTO @DATA(ld_iv_user). | ||||
| "SELECT single FUNCTION FROM BBP_WFL_TRACE INTO @DATA(ld_iv_function). | ||||
| "SELECT single WORKITEM FROM BBP_WFL_TRACE INTO @DATA(ld_iv_workitem_id). | ||||
| "SELECT single MAIN_WI FROM BBP_WFL_TRACE INTO @DATA(ld_iv_main_workitem_id). | ||||
| "SELECT single ACTION FROM BBP_WFL_TRACE INTO @DATA(ld_iv_action). | ||||
| "SELECT single ADD_INFO FROM BBP_WFL_TRACE INTO @DATA(ld_iv_add_info). | ||||
Search for further information about these or an SAP related objects