SAP BBP_PDH_WFL_APPROVAL_TABLE_GET Function Module for Ermittelt die Liste der Genehmiger für dynamische Loops
BBP_PDH_WFL_APPROVAL_TABLE_GET is a standard bbp pdh wfl approval table get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ermittelt die Liste der Genehmiger für dynamische Loops 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 bbp pdh wfl approval table get FM, simply by entering the name BBP_PDH_WFL_APPROVAL_TABLE_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_PDH_WFL
Program Name: SAPLBBP_PDH_WFL
Main Program: SAPLBBP_PDH_WFL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PDH_WFL_APPROVAL_TABLE_GET 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_APPROVAL_TABLE_GET'"Ermittelt die Liste der Genehmiger für dynamische Loops.
EXPORTING
* IV_TASK = "Aufgabenkürzel
* IV_WORKITEM_ID = "Workitem-Kennung
* IV_OBJECT_ID = "Vorgangsnummer
* IV_GUID = "Globally Unique Identifier in 32-Char-Darstellung
* IV_OBJECT_TYPE = "Geschäftsvorgangstyp
* IV_WF_STATE = "WF: API: Knotentyp
TABLES
* IT_APPROVAL_AGENTS = "Struktur für die Genehmigungstabelle
* ET_APPROVAL_AGENTS = "Struktur für die Genehmigungstabelle
IMPORTING Parameters details for BBP_PDH_WFL_APPROVAL_TABLE_GET
IV_TASK - Aufgabenkürzel
Data type: SWD_STEP_TOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_WORKITEM_ID - Workitem-Kennung
Data type: SWW_WIIDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_ID - Vorgangsnummer
Data type: CRMD_ORDERADM_H-OBJECT_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_GUID - Globally Unique Identifier in 32-Char-Darstellung
Data type: BBP_GUID_32Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_OBJECT_TYPE - Geschäftsvorgangstyp
Data type: CRMD_ORDERADM_H-OBJECT_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_WF_STATE - WF: API: Knotentyp
Data type: SWD_NODETYOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_PDH_WFL_APPROVAL_TABLE_GET
IT_APPROVAL_AGENTS - Struktur für die Genehmigungstabelle
Data type: BBP_WFL_APPROVAL_TABLEOptional: Yes
Call by Reference: Yes
ET_APPROVAL_AGENTS - Struktur für die Genehmigungstabelle
Data type: BBP_WFL_APPROVAL_TABLEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BBP_PDH_WFL_APPROVAL_TABLE_GET 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_iv_task | TYPE SWD_STEP_T, " | |||
| lt_it_approval_agents | TYPE STANDARD TABLE OF BBP_WFL_APPROVAL_TABLE, " | |||
| lv_iv_workitem_id | TYPE SWW_WIID, " | |||
| lt_et_approval_agents | TYPE STANDARD TABLE OF BBP_WFL_APPROVAL_TABLE, " | |||
| lv_iv_object_id | TYPE CRMD_ORDERADM_H-OBJECT_ID, " | |||
| lv_iv_guid | TYPE BBP_GUID_32, " | |||
| lv_iv_object_type | TYPE CRMD_ORDERADM_H-OBJECT_TYPE, " | |||
| lv_iv_wf_state | TYPE SWD_NODETY. " |
|   CALL FUNCTION 'BBP_PDH_WFL_APPROVAL_TABLE_GET' "Ermittelt die Liste der Genehmiger für dynamische Loops |
| EXPORTING | ||
| IV_TASK | = lv_iv_task | |
| IV_WORKITEM_ID | = lv_iv_workitem_id | |
| IV_OBJECT_ID | = lv_iv_object_id | |
| IV_GUID | = lv_iv_guid | |
| IV_OBJECT_TYPE | = lv_iv_object_type | |
| IV_WF_STATE | = lv_iv_wf_state | |
| TABLES | ||
| IT_APPROVAL_AGENTS | = lt_it_approval_agents | |
| ET_APPROVAL_AGENTS | = lt_et_approval_agents | |
| . " BBP_PDH_WFL_APPROVAL_TABLE_GET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_PDH_WFL_APPROVAL_TABLE_GET
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). | ||||
Search for further information about these or an SAP related objects