SAP BBP_PD_AVL_CREATE Function Module for









BBP_PD_AVL_CREATE is a standard bbp pd avl create 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 pd avl create FM, simply by entering the name BBP_PD_AVL_CREATE into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_PD_AVL_CREATE 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_AVL_CREATE'"
  EXPORTING
*  I_PARK =  "
*  I_SAVE =  "
*  I_TESTRUN =  "
*  I_HEADER =  "
*  IT_ATTACH =  "

 IMPORTING
   E_HEADER =  "
   ET_ATTACH =  "

TABLES
*  I_ITEM =  "
*  E_LONGTEXT =  "
*  E_HCF =  "
*  E_ICF =  "
*  E_STATUS =  "
   E_MESSAGES =  "
*  I_PARTNER =  "
*  I_ORGDATA =  "
*  I_LONGTEXT =  "
*  I_HCF =  "
*  I_ICF =  "
*  E_ITEM =  "
*  E_PARTNER =  "
*  E_ORGDATA =  "
.



IMPORTING Parameters details for BBP_PD_AVL_CREATE

I_PARK -

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

I_SAVE -

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

I_TESTRUN -

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

I_HEADER -

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

IT_ATTACH -

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

EXPORTING Parameters details for BBP_PD_AVL_CREATE

E_HEADER -

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

ET_ATTACH -

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

TABLES Parameters details for BBP_PD_AVL_CREATE

I_ITEM -

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

E_LONGTEXT -

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

E_HCF -

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

E_ICF -

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

E_STATUS -

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

E_MESSAGES -

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

I_PARTNER -

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

I_ORGDATA -

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

I_LONGTEXT -

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

I_HCF -

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

I_ICF -

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

E_ITEM -

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

E_PARTNER -

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

E_ORGDATA -

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

Copy and paste ABAP code example for BBP_PD_AVL_CREATE 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_i_item  TYPE STANDARD TABLE OF BBP_PDS_AVL_ITEM_ICU, "   
lv_i_park  TYPE XFELD, "   
lv_e_header  TYPE BBP_PDS_AVL_HEADER_D, "   
lt_e_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lt_e_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_AVL, "   
lt_e_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_AVL, "   
lt_e_status  TYPE STANDARD TABLE OF BBP_PDS_STATUS, "   
lt_e_messages  TYPE STANDARD TABLE OF BBP_PDS_MESSAGES, "   
lv_i_save  TYPE XFELD, "   
lv_et_attach  TYPE BBPT_PDS_ATT_T, "   
lt_i_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lt_i_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG, "   
lv_i_testrun  TYPE XFELD, "   
lv_i_header  TYPE BBP_PDS_AVL_HEADER_IC, "   
lt_i_longtext  TYPE STANDARD TABLE OF BBP_PDS_LONGTEXT, "   
lt_i_hcf  TYPE STANDARD TABLE OF BBP_PDS_HCF_AVL, "   
lv_it_attach  TYPE BBPT_PDS_ATT_T, "   
lt_i_icf  TYPE STANDARD TABLE OF BBP_PDS_ICF_AVL, "   
lt_e_item  TYPE STANDARD TABLE OF BBP_PDS_AVL_ITEM_D, "   
lt_e_partner  TYPE STANDARD TABLE OF BBP_PDS_PARTNER, "   
lt_e_orgdata  TYPE STANDARD TABLE OF BBP_PDS_ORG. "   

  CALL FUNCTION 'BBP_PD_AVL_CREATE'  "
    EXPORTING
         I_PARK = lv_i_park
         I_SAVE = lv_i_save
         I_TESTRUN = lv_i_testrun
         I_HEADER = lv_i_header
         IT_ATTACH = lv_it_attach
    IMPORTING
         E_HEADER = lv_e_header
         ET_ATTACH = lv_et_attach
    TABLES
         I_ITEM = lt_i_item
         E_LONGTEXT = lt_e_longtext
         E_HCF = lt_e_hcf
         E_ICF = lt_e_icf
         E_STATUS = lt_e_status
         E_MESSAGES = lt_e_messages
         I_PARTNER = lt_i_partner
         I_ORGDATA = lt_i_orgdata
         I_LONGTEXT = lt_i_longtext
         I_HCF = lt_i_hcf
         I_ICF = lt_i_icf
         E_ITEM = lt_e_item
         E_PARTNER = lt_e_partner
         E_ORGDATA = lt_e_orgdata
. " BBP_PD_AVL_CREATE




ABAP code using 7.40 inline data declarations to call FM BBP_PD_AVL_CREATE

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!