SAP BD_APP_PREP_ADJ Function Module for Preparation of Internet Budget Billing Adjustment









BD_APP_PREP_ADJ is a standard bd app 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 app prep adj FM, simply by entering the name BD_APP_PREP_ADJ into the relevant SAP transaction such as SE37 or SE38.

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



Function BD_APP_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_APP_PREP_ADJ'"Preparation of Internet Budget Billing Adjustment
EXPORTING
I_GPART = "Business Partner Number
* I_USER = SY-UNAME "User Name in User Master Record

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_UCES_EXTENSION = "UCES: Display Customer-Specific Fields from JSP
.



IMPORTING Parameters details for BD_APP_PREP_ADJ

I_GPART - Business Partner Number

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

I_USER - User Name in User Master Record

Data type: USR04-BNAME
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BD_APP_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_APP
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BD_APP_PREP_ADJ

BUDBIPLAN - Table Type for UCES_BBP

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

XT_UCES_EXTENSION - UCES: Display Customer-Specific Fields from JSP

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

Copy and paste ABAP code example for BD_APP_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_PP_TAB, "   
lv_i_user  TYPE USR04-BNAME, "   SY-UNAME
lv_paydates  TYPE UCES_PAY_DATES_TAB, "   
lt_xt_uces_extension  TYPE STANDARD TABLE OF UCES_EXTENSION, "   
lv_return  TYPE BAPIRET2, "   
lv_e_cust  TYPE UCES_CUST_APP. "   

  CALL FUNCTION 'BD_APP_PREP_ADJ'  "Preparation of Internet Budget Billing Adjustment
    EXPORTING
         I_GPART = lv_i_gpart
         I_USER = lv_i_user
    IMPORTING
         ABSLIM = lv_abslim
         PAYDATES = lv_paydates
         RETURN = lv_return
         E_CUST = lv_e_cust
    TABLES
         BUDBIPLAN = lt_budbiplan
         XT_UCES_EXTENSION = lt_xt_uces_extension
. " BD_APP_PREP_ADJ




ABAP code using 7.40 inline data declarations to call FM BD_APP_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.

 
 
 
"SELECT single BNAME FROM USR04 INTO @DATA(ld_i_user).
DATA(ld_i_user) = SY-UNAME.
 
 
 
 
 


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!