BD_APP_GET_LIM SAP Function module - Determination of Absolute Limits

BD_APP_GET_LIM is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BD_APP_GET_LIM into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BDISU_APP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM BD_APP_GET_LIM - BD APP GET LIM

CALL FUNCTION 'BD_APP_GET_LIM' "Determination of Absolute Limits
  EXPORTING
    i_uces_pp =                 " uces_pp_tab   Table Type for UCES_BBP
    i_gpart =                   " gpart_kk      Business Partner Number
*   i_obj =                     " isu25_budbilplan  Budget Billing Plan
*   i_create =                  " kennzx        Indicator
  IMPORTING
    e_uces_abs_lim =            " uces_abs_lim  Absolute Limits for Budget Billing Plan Adjustment
    e_bapiret2 =                " bapiret2      Return Parameter(s)
    e_cust =                    " uces_cust_app  UCES: Customizing for Budget Billing Plan Adjustment
    .  "  BD_APP_GET_LIM

ABAP code example for Function Module BD_APP_GET_LIM

The ABAP code below is a full code listing to execute function module BD_APP_GET_LIM including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_uces_abs_lim  
 
 TYPE UCES_ABS_LIM
,
ld_e_bapiret2  
 
 TYPE BAPIRET2
,
ld_e_cust  
 
 TYPE UCES_CUST_APP
.


DATA(ld_i_uces_pp) = 'Check type of data required'.

DATA(ld_i_gpart) = 'Check type of data required'.

DATA(ld_i_obj) = 'Check type of data required'.

DATA(ld_i_create) = 'Check type of data required'.
.

CALL FUNCTION 'BD_APP_GET_LIM'
  EXPORTING
    i_uces_pp =                  ld_i_uces_pp
    i_gpart =                    ld_i_gpart
*   i_obj =                      ld_i_obj
*   i_create =                   ld_i_create
  IMPORTING
    e_uces_abs_lim =             ld_e_uces_abs_lim
    e_bapiret2 =                 ld_e_bapiret2
    e_cust =                     ld_e_cust
    .  "  BD_APP_GET_LIM

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_uces_abs_lim
 
 TYPE UCES_ABS_LIM ,
ld_i_uces_pp
 
 TYPE UCES_PP_TAB ,
ld_e_bapiret2
 
 TYPE BAPIRET2 ,
ld_i_gpart
 
 TYPE GPART_KK ,
ld_e_cust
 
 TYPE UCES_CUST_APP ,
ld_i_obj
 
 TYPE ISU25_BUDBILPLAN ,
ld_i_create
 
 TYPE KENNZX .


ld_i_uces_pp = 'Check type of data required'.
ld_i_gpart = 'Check type of data required'.
ld_i_obj = 'Check type of data required'.
ld_i_create = 'Check type of data required'.