SAP BBP_PO_FLAT_APO_MAP_PD Function Module for









BBP_PO_FLAT_APO_MAP_PD is a standard bbp po flat apo map pd 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 po flat apo map pd FM, simply by entering the name BBP_PO_FLAT_APO_MAP_PD into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_PO_FLAT_APO_MAP_PD 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_PO_FLAT_APO_MAP_PD'"
EXPORTING
I_APO_CTRL = "
I_APO_DEMAND = "

IMPORTING
E_PD_POFLAT = "

TABLES
* E_RETURN = "
.



IMPORTING Parameters details for BBP_PO_FLAT_APO_MAP_PD

I_APO_CTRL -

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

I_APO_DEMAND -

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

EXPORTING Parameters details for BBP_PO_FLAT_APO_MAP_PD

E_PD_POFLAT -

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

TABLES Parameters details for BBP_PO_FLAT_APO_MAP_PD

E_RETURN -

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

Copy and paste ABAP code example for BBP_PO_FLAT_APO_MAP_PD 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:
lt_e_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_i_apo_ctrl  TYPE BBPCIF_CIFCTRLPAR, "   
lv_e_pd_poflat  TYPE BBP_PDS_PO_FLAT, "   
lv_i_apo_demand  TYPE BBPCIF_CIFPUOROUT. "   

  CALL FUNCTION 'BBP_PO_FLAT_APO_MAP_PD'  "
    EXPORTING
         I_APO_CTRL = lv_i_apo_ctrl
         I_APO_DEMAND = lv_i_apo_demand
    IMPORTING
         E_PD_POFLAT = lv_e_pd_poflat
    TABLES
         E_RETURN = lt_e_return
. " BBP_PO_FLAT_APO_MAP_PD




ABAP code using 7.40 inline data declarations to call FM BBP_PO_FLAT_APO_MAP_PD

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!