SAP UPBR_DATA_MAPPING_EXIT Function Module for Planungsfunktion vom Typ Exit (ALV Datenanzeige)









UPBR_DATA_MAPPING_EXIT is a standard upbr data mapping exit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Planungsfunktion vom Typ Exit (ALV Datenanzeige) 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 upbr data mapping exit FM, simply by entering the name UPBR_DATA_MAPPING_EXIT into the relevant SAP transaction such as SE37 or SE38.

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



Function UPBR_DATA_MAPPING_EXIT 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 'UPBR_DATA_MAPPING_EXIT'"Planungsfunktion vom Typ Exit (ALV Datenanzeige)
  EXPORTING
*  I_AREA =  "Planungsgebiet
*  I_PLEVEL =  "Planungsebene
*  I_METHOD =  "Planungsfunktion
*  I_PARAM =  "Parametergruppe
*  I_PACKAGE =  "Planungspaket
*  IT_EXITP =  "Planungsfunktionen: Parameter der Exitfunktionen
*  ITO_CHASEL =  "Merkmalsselektion
*  ITO_CHA =  "Merkmale
*  ITO_KYF =  "Kennzahlen

 IMPORTING
   ET_MESG =  "Messages

CHANGING
   XTH_DATA =  "
.



IMPORTING Parameters details for UPBR_DATA_MAPPING_EXIT

I_AREA - Planungsgebiet

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

I_PLEVEL - Planungsebene

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

I_METHOD - Planungsfunktion

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

I_PARAM - Parametergruppe

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

I_PACKAGE - Planungspaket

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

IT_EXITP - Planungsfunktionen: Parameter der Exitfunktionen

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

ITO_CHASEL - Merkmalsselektion

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

ITO_CHA - Merkmale

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

ITO_KYF - Kennzahlen

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

EXPORTING Parameters details for UPBR_DATA_MAPPING_EXIT

ET_MESG - Messages

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

CHANGING Parameters details for UPBR_DATA_MAPPING_EXIT

XTH_DATA -

Data type: HASHED TABLE
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for UPBR_DATA_MAPPING_EXIT 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_i_area  TYPE UPC_Y_AREA, "   
lv_et_mesg  TYPE UPC_YT_MESG, "   
lv_xth_data  TYPE HASHED TABLE, "   
lv_i_plevel  TYPE UPC_Y_PLEVEL, "   
lv_i_method  TYPE UPC_Y_METHOD, "   
lv_i_param  TYPE UPC_Y_PARAM, "   
lv_i_package  TYPE UPC_Y_PACKAGE, "   
lv_it_exitp  TYPE UPF_YT_EXITP, "   
lv_ito_chasel  TYPE UPC_YTO_CHASEL, "   
lv_ito_cha  TYPE UPC_YTO_CHA, "   
lv_ito_kyf  TYPE UPC_YTO_KYF. "   

  CALL FUNCTION 'UPBR_DATA_MAPPING_EXIT'  "Planungsfunktion vom Typ Exit (ALV Datenanzeige)
    EXPORTING
         I_AREA = lv_i_area
         I_PLEVEL = lv_i_plevel
         I_METHOD = lv_i_method
         I_PARAM = lv_i_param
         I_PACKAGE = lv_i_package
         IT_EXITP = lv_it_exitp
         ITO_CHASEL = lv_ito_chasel
         ITO_CHA = lv_ito_cha
         ITO_KYF = lv_ito_kyf
    IMPORTING
         ET_MESG = lv_et_mesg
    CHANGING
         XTH_DATA = lv_xth_data
. " UPBR_DATA_MAPPING_EXIT




ABAP code using 7.40 inline data declarations to call FM UPBR_DATA_MAPPING_EXIT

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



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!