SAP Function Modules

LB_BIL_INV_OUTP_READ_DBDATA SAP Function module







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

Associated Function Group: LB_BIL_OUTPUT
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM LB_BIL_INV_OUTP_READ_DBDATA - LB BIL INV OUTP READ DBDATA





CALL FUNCTION 'LB_BIL_INV_OUTP_READ_DBDATA' "
  EXPORTING
    it_bil_number =             " lbbil_invoice_key_t  Billing Documents
*   if_language =               " nast-spras    Message Language
*   is_db_data_to_read =        " lbbil_db_data_to_read  Limit Data Selection for Issuing Outputs
*   if_read_mode = SPACE        " mem_access    Buffer access to SD tables
*   if_refresh_buffer = SPACE   " xfeld         Checkbox
  IMPORTING
    es_bil_outp_dbdata =        " lbbil_outp_dbdata  Database Tables for Issuing Billing Output
  EXCEPTIONS
    RECORDS_NOT_FOUND = 1       "               No invoices exist
    RECORDS_NOT_REQUESTED = 2   "
    .  "  LB_BIL_INV_OUTP_READ_DBDATA

ABAP code example for Function Module LB_BIL_INV_OUTP_READ_DBDATA





The ABAP code below is a full code listing to execute function module LB_BIL_INV_OUTP_READ_DBDATA 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_es_bil_outp_dbdata  TYPE LBBIL_OUTP_DBDATA .

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

SELECT single SPRAS
FROM NAST
INTO @DATA(ld_if_language).

DATA(ld_is_db_data_to_read) = 'Check type of data required'.
DATA(ld_if_read_mode) = 'Check type of data required'.
DATA(ld_if_refresh_buffer) = 'Check type of data required'. . CALL FUNCTION 'LB_BIL_INV_OUTP_READ_DBDATA' EXPORTING it_bil_number = ld_it_bil_number * if_language = ld_if_language * is_db_data_to_read = ld_is_db_data_to_read * if_read_mode = ld_if_read_mode * if_refresh_buffer = ld_if_refresh_buffer IMPORTING es_bil_outp_dbdata = ld_es_bil_outp_dbdata EXCEPTIONS RECORDS_NOT_FOUND = 1 RECORDS_NOT_REQUESTED = 2 . " LB_BIL_INV_OUTP_READ_DBDATA
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_es_bil_outp_dbdata  TYPE LBBIL_OUTP_DBDATA ,
ld_it_bil_number  TYPE LBBIL_INVOICE_KEY_T ,
ld_if_language  TYPE NAST-SPRAS ,
ld_is_db_data_to_read  TYPE LBBIL_DB_DATA_TO_READ ,
ld_if_read_mode  TYPE MEM_ACCESS ,
ld_if_refresh_buffer  TYPE XFELD .

ld_it_bil_number = 'Check type of data required'.

SELECT single SPRAS
FROM NAST
INTO ld_if_language.

ld_is_db_data_to_read = 'Check type of data required'.
ld_if_read_mode = 'Check type of data required'.
ld_if_refresh_buffer = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name LB_BIL_INV_OUTP_READ_DBDATA or its description.