SAP BBP_PD_MSG_CONVERT_STEP2 Function Module for Meldungen gem IMG-Aktitivt 'XML-Meldungssteuerung' umschlsseln

Search SAP Function Modules

BBP_PD_MSG_CONVERT_STEP2 is a standard bbp pd msg convert step2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Meldungen gem IMG-Aktitivt 'XML-Meldungssteuerung' umschlsseln 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 pd msg convert step2 FM, simply by entering the name BBP_PD_MSG_CONVERT_STEP2 into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_PDH_MSG
Program Name: SAPLBBP_PDH_MSG
Main Program: SAPLBBP_PDH_MSG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_PD_MSG_CONVERT_STEP2 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_PD_MSG_CONVERT_STEP2'"Meldungen gem IMG-Aktitivt 'XML-Meldungssteuerung' umschlsseln
  EXPORTING
*  IV_OBJECT_TYPE =  "Geschäftsvorgangstyp
*  IV_MSG_SCENARIO =  "Szenario für flexible Meldungssteuerung
*  IV_COMPANY =  "Unternehmen im MarketSet Procurement
*  IV_GUID =  "Globally Unique Identifier

 IMPORTING
   EV_ERROR_AFT_CONV =  "'X': Auch nach Umschlüsselung gibt es noch E- bzw. A-Fehler

TABLES
   CT_MESSAGES =  "Fehlermeldungen zu einer PD-Methode

.

IMPORTING Parameters details for BBP_PD_MSG_CONVERT_STEP2

IV_OBJECT_TYPE - Geschäftsvorgangstyp

Data type: CRMD_ORDERADM_H-OBJECT_TYPE
Optional: Yes
Call by Reference: Yes

IV_MSG_SCENARIO - Szenario für flexible Meldungssteuerung

Data type: BBP_MSG_SCENARIO
Optional: Yes
Call by Reference: Yes

IV_COMPANY - Unternehmen im MarketSet Procurement

Data type: BBP_MS_COMPANY
Optional: Yes
Call by Reference: Yes

IV_GUID - Globally Unique Identifier

Data type: BBP_GUID
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for BBP_PD_MSG_CONVERT_STEP2

EV_ERROR_AFT_CONV - 'X': Auch nach Umschlüsselung gibt es noch E- bzw. A-Fehler

Data type: XFELD
Optional: No
Call by Reference: Yes

TABLES Parameters details for BBP_PD_MSG_CONVERT_STEP2

CT_MESSAGES - Fehlermeldungen zu einer PD-Methode

Data type: BBP_PDS_MESSAGES
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_PD_MSG_CONVERT_STEP2 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.

ABAP code using 7.40 inline data declarations to call FM BBP_PD_MSG_CONVERT_STEP2

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.

Search for further information about these or an SAP related objects