SAP BBP_PDH_WFL_GET_OBJECTTEXT Function Module for Ermittelt sprach- und versionsabhängige Bezeichnung des Objektes









BBP_PDH_WFL_GET_OBJECTTEXT is a standard bbp pdh wfl get objecttext 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 sprach- und versionsabhängige Bezeichnung des Objektes 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 get objecttext FM, simply by entering the name BBP_PDH_WFL_GET_OBJECTTEXT 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_GET_OBJECTTEXT 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_GET_OBJECTTEXT'"Ermittelt sprach- und versionsabhängige Bezeichnung des Objektes
EXPORTING
* IV_OBJECT_TYPE = "Objekttyp
* IV_VERSIONTYPE = "Art der Version (aktiver Beleg, 'normal', Arbeitsversion)
* IV_SUBTYPE = "Ausprägung eines Einkaufsbelegs (z.B. Gutschrift/Rechnung)
* IV_TEMPLATE_TYPE = "Vorlagentyp eines CRM-Vorgangs
* IV_LANGUAGE = "Sprachenschlüssel der aktuellen Textumgebung

IMPORTING
EV_VERSIONTYPE_NAME = "Text für Genehmigungsstatus
.



IMPORTING Parameters details for BBP_PDH_WFL_GET_OBJECTTEXT

IV_OBJECT_TYPE - Objekttyp

Data type: TOJTB-NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_VERSIONTYPE - Art der Version (aktiver Beleg, 'normal', Arbeitsversion)

Data type: BBP_PDS_HEADER-VERSION_TYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SUBTYPE - Ausprägung eines Einkaufsbelegs (z.B. Gutschrift/Rechnung)

Data type: BBP_H_SUBTYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_TEMPLATE_TYPE - Vorlagentyp eines CRM-Vorgangs

Data type: CRMT_TEMPLATE_TYPE_DB
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LANGUAGE - Sprachenschlüssel der aktuellen Textumgebung

Data type: SPRAS
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BBP_PDH_WFL_GET_OBJECTTEXT

EV_VERSIONTYPE_NAME - Text für Genehmigungsstatus

Data type: BBP_S_WFL_APPROVALSTATE-WF_SCENARIO_T
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BBP_PDH_WFL_GET_OBJECTTEXT 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_object_type  TYPE TOJTB-NAME, "   
lv_ev_versiontype_name  TYPE BBP_S_WFL_APPROVALSTATE-WF_SCENARIO_T, "   
lv_iv_versiontype  TYPE BBP_PDS_HEADER-VERSION_TYPE, "   
lv_iv_subtype  TYPE BBP_H_SUBTYPE, "   
lv_iv_template_type  TYPE CRMT_TEMPLATE_TYPE_DB, "   
lv_iv_language  TYPE SPRAS. "   

  CALL FUNCTION 'BBP_PDH_WFL_GET_OBJECTTEXT'  "Ermittelt sprach- und versionsabhängige Bezeichnung des Objektes
    EXPORTING
         IV_OBJECT_TYPE = lv_iv_object_type
         IV_VERSIONTYPE = lv_iv_versiontype
         IV_SUBTYPE = lv_iv_subtype
         IV_TEMPLATE_TYPE = lv_iv_template_type
         IV_LANGUAGE = lv_iv_language
    IMPORTING
         EV_VERSIONTYPE_NAME = lv_ev_versiontype_name
. " BBP_PDH_WFL_GET_OBJECTTEXT




ABAP code using 7.40 inline data declarations to call FM BBP_PDH_WFL_GET_OBJECTTEXT

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 NAME FROM TOJTB INTO @DATA(ld_iv_object_type).
 
"SELECT single WF_SCENARIO_T FROM BBP_S_WFL_APPROVALSTATE INTO @DATA(ld_ev_versiontype_name).
 
"SELECT single VERSION_TYPE FROM BBP_PDS_HEADER INTO @DATA(ld_iv_versiontype).
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!