KBPS_FIND_LEDGER SAP Function module - Ledger determination budgeting/planning

KBPS_FIND_LEDGER 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 KBPS_FIND_LEDGER into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM KBPS_FIND_LEDGER - KBPS FIND LEDGER

CALL FUNCTION 'KBPS_FIND_LEDGER' "Ledger determination budgeting/planning
* EXPORTING
*   currency = SPACE            " bpin-owaer    Currency
*   new_ledger = SPACE          "               New ledger may be created
*   periv = SPACE               " bpin-periv    Period version
  IMPORTING
    ledger =                    "               Ledger number
    op_decim =                  "
* TABLES
*   bp_cur =                    "
  EXCEPTIONS
    NO_LEDGER = 1               "               No ledger for currency determined
    LOCKING_ERROR = 2           "
    .  "  KBPS_FIND_LEDGER

ABAP code example for Function Module KBPS_FIND_LEDGER

The ABAP code below is a full code listing to execute function module KBPS_FIND_LEDGER 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_ledger  
 
 TYPE STRING
,
ld_op_decim  
 
 TYPE STRING
,
it_bp_cur  
 
 TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_bp_cur
 
 LIKE LINE OF it_bp_cur
.



DATA(ld_currency) = Check type of data required

DATA(ld_new_ledger) = 'some text here'.


DATA(ld_periv) = some text here
 

"populate fields of struture and append to itab
append wa_bp_cur to it_bp_cur.
.

CALL FUNCTION 'KBPS_FIND_LEDGER'
* EXPORTING
*   currency =                   ld_currency
*   new_ledger =                 ld_new_ledger
*   periv =                      ld_periv
  IMPORTING
    ledger =                     ld_ledger
    op_decim =                   ld_op_decim
* TABLES
*   bp_cur =                     it_bp_cur
  EXCEPTIONS
    NO_LEDGER =                  1
    LOCKING_ERROR =              2
    .  "  KBPS_FIND_LEDGER

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
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_ledger
 
 TYPE STRING ,
ld_currency
 
 TYPE BPIN-OWAER ,
it_bp_cur
 
 TYPE STANDARD TABLE OF STRING ,
wa_bp_cur
 
 LIKE LINE OF it_bp_cur,
ld_op_decim
 
 TYPE STRING ,
ld_new_ledger
 
 TYPE STRING ,
ld_periv
 
 TYPE BPIN-PERIV .



ld_currency = Check type of data required 

"populate fields of struture and append to itab
append wa_bp_cur to it_bp_cur.
ld_new_ledger = 'some text here'.

ld_periv = some text here