SAP BBP_HEADER_TO_EXT_MAPV Function Module for









BBP_HEADER_TO_EXT_MAPV is a standard bbp header to ext mapv 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 header to ext mapv FM, simply by entering the name BBP_HEADER_TO_EXT_MAPV into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_HEADER_TO_EXT_MAPV 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_HEADER_TO_EXT_MAPV'"
EXPORTING
IS_HEADER = "
IT_STATUS = "
* IV_COMPLETE_TRANSMISSION_I = GC_YES "
* IV_MESSAGE = "
* IV_VENDOR_GUID = "

IMPORTING
ES_HEADER = "
.



IMPORTING Parameters details for BBP_HEADER_TO_EXT_MAPV

IS_HEADER -

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

IT_STATUS -

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

IV_COMPLETE_TRANSMISSION_I -

Data type: BBP_COMPLETE_TRANS_IND
Default: GC_YES
Optional: Yes
Call by Reference: Yes

IV_MESSAGE -

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

IV_VENDOR_GUID -

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

EXPORTING Parameters details for BBP_HEADER_TO_EXT_MAPV

ES_HEADER -

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

Copy and paste ABAP code example for BBP_HEADER_TO_EXT_MAPV 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_es_header  TYPE ANY, "   
lv_is_header  TYPE ANY, "   
lv_it_status  TYPE BBPT_PD_STATUS, "   
lv_iv_complete_transmission_i  TYPE BBP_COMPLETE_TRANS_IND, "   GC_YES
lv_iv_message  TYPE CHAR40, "   
lv_iv_vendor_guid  TYPE BBP_GUID. "   

  CALL FUNCTION 'BBP_HEADER_TO_EXT_MAPV'  "
    EXPORTING
         IS_HEADER = lv_is_header
         IT_STATUS = lv_it_status
         IV_COMPLETE_TRANSMISSION_I = lv_iv_complete_transmission_i
         IV_MESSAGE = lv_iv_message
         IV_VENDOR_GUID = lv_iv_vendor_guid
    IMPORTING
         ES_HEADER = lv_es_header
. " BBP_HEADER_TO_EXT_MAPV




ABAP code using 7.40 inline data declarations to call FM BBP_HEADER_TO_EXT_MAPV

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_complete_transmission_i) = GC_YES.
 
 
 


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!