SAP BD_ABBP_PREP_ADJ Function Module for Preparation of Internet Budget Billing Adjustment









BD_ABBP_PREP_ADJ is a standard bd abbp prep adj SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Preparation of Internet Budget Billing Adjustment 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 bd abbp prep adj FM, simply by entering the name BD_ABBP_PREP_ADJ into the relevant SAP transaction such as SE37 or SE38.

Function Group: BDISU_ABBP
Program Name: SAPLBDISU_ABBP
Main Program: SAPLBDISU_ABBP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BD_ABBP_PREP_ADJ 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 'BD_ABBP_PREP_ADJ'"Preparation of Internet Budget Billing Adjustment
  EXPORTING
   I_GPART =  "Business Partner Number
   I_VAR =  "Variant of Internet Budget Billing Adjustment

 IMPORTING
   ABSLIM =  "Absolute Limits for Budget Billing Plan Adjustment
   PAYDATES =  "Data for Future Budget Billing Payments
   RETURN =  "Return Parameter(s)
   E_CUST =  "UCES: Customizing for Budget Billing Plan Adjustment

TABLES
   BUDBIPLAN =  "Table Type for UCES_BBP
*  XT_REG_READ_EVBS =  "Registers to be Read for Premise
*  XT_MRRES =  "BAPI upload structure for MR document
*  XT_UCES_EXTENSION =  "UCES: Display Customer-Specific Fields from JSP
.



IMPORTING Parameters details for BD_ABBP_PREP_ADJ

I_GPART - Business Partner Number

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

I_VAR - Variant of Internet Budget Billing Adjustment

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

EXPORTING Parameters details for BD_ABBP_PREP_ADJ

ABSLIM - Absolute Limits for Budget Billing Plan Adjustment

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

PAYDATES - Data for Future Budget Billing Payments

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

RETURN - Return Parameter(s)

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

E_CUST - UCES: Customizing for Budget Billing Plan Adjustment

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

TABLES Parameters details for BD_ABBP_PREP_ADJ

BUDBIPLAN - Table Type for UCES_BBP

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

XT_REG_READ_EVBS - Registers to be Read for Premise

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

XT_MRRES - BAPI upload structure for MR document

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

XT_UCES_EXTENSION - UCES: Display Customer-Specific Fields from JSP

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

Copy and paste ABAP code example for BD_ABBP_PREP_ADJ 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_abslim  TYPE UCES_ABS_LIM, "   
lv_i_gpart  TYPE GPART_KK, "   
lt_budbiplan  TYPE STANDARD TABLE OF UCES_BBP_TAB, "   
lv_i_var  TYPE UCES_VAR, "   
lv_paydates  TYPE UCES_PAY_DATES_TAB, "   
lt_xt_reg_read_evbs  TYPE STANDARD TABLE OF REGREADEVBS, "   
lv_return  TYPE BAPIRET2, "   
lt_xt_mrres  TYPE STANDARD TABLE OF BAPIEABLU, "   
lv_e_cust  TYPE UCES_CUST_ABBP, "   
lt_xt_uces_extension  TYPE STANDARD TABLE OF UCES_EXTENSION. "   

  CALL FUNCTION 'BD_ABBP_PREP_ADJ'  "Preparation of Internet Budget Billing Adjustment
    EXPORTING
         I_GPART = lv_i_gpart
         I_VAR = lv_i_var
    IMPORTING
         ABSLIM = lv_abslim
         PAYDATES = lv_paydates
         RETURN = lv_return
         E_CUST = lv_e_cust
    TABLES
         BUDBIPLAN = lt_budbiplan
         XT_REG_READ_EVBS = lt_xt_reg_read_evbs
         XT_MRRES = lt_xt_mrres
         XT_UCES_EXTENSION = lt_xt_uces_extension
. " BD_ABBP_PREP_ADJ




ABAP code using 7.40 inline data declarations to call FM BD_ABBP_PREP_ADJ

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!