ISM_BANKDETAILS_READ_FROM_DB SAP Function module - IS-M: Read Intended Purpose and Addit.Data for Coll.Auth from Master Dat

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

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

Pattern for FM ISM_BANKDETAILS_READ_FROM_DB - ISM BANKDETAILS READ FROM DB

CALL FUNCTION 'ISM_BANKDETAILS_READ_FROM_DB' "IS-M: Read Intended Purpose and Addit.Data for Coll.Auth from Master Data
  EXPORTING
    pv_flg_sapgp_active =       " rjhallg-xsapgpactive
    pv_flg_bank_sales_area =    " rjhallg-xbanksalesarea  IS-M: Bank details valid on sales area level
*   pv_flg_sales_area_check = 'X'  " xfeld
*   pv_vkorg =                  " rjhak-vkorg   Sales Organization
*   pv_vtweg =                  " rjhak-vtweg   Distribution Channel
*   pv_spart =                  " rjhak-spart   Division
    pv_regulierer =             " rjhaisz-regulierer  IS-M: Payer
    pv_bkvid =                  " but0bk-bkvid  Bank Details ID
  IMPORTING
    ps_rjhabank =               " rjhabank_str  IS-M/AM: Bank Details
  EXCEPTIONS
    PARAMETER_ERROR = 1         "               Errors in passing parameters
    BKVID_DOESNT_EXIST = 2      "
    LOCKED_IN_SALES_AREA = 3    "
    SALES_AREA_DOESNT_EXIST = 4  "              Sales area does not exist
    NOT_IN_SALES_AREA = 5       "
    .  "  ISM_BANKDETAILS_READ_FROM_DB

ABAP code example for Function Module ISM_BANKDETAILS_READ_FROM_DB

The ABAP code below is a full code listing to execute function module ISM_BANKDETAILS_READ_FROM_DB 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_ps_rjhabank  
 
 TYPE RJHABANK_STR
.



DATA(ld_pv_flg_sapgp_active) = some text here


DATA(ld_pv_flg_bank_sales_area) = some text here

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


DATA(ld_pv_vkorg) = some text here


DATA(ld_pv_vtweg) = some text here


DATA(ld_pv_spart) = some text here


DATA(ld_pv_regulierer) = some text here
 

SELECT single BKVID 
  FROM BUT0BK 
  INTO @DATA(ld_pv_bkvid).

.

CALL FUNCTION 'ISM_BANKDETAILS_READ_FROM_DB'
  EXPORTING
    pv_flg_sapgp_active =        ld_pv_flg_sapgp_active
    pv_flg_bank_sales_area =     ld_pv_flg_bank_sales_area
*   pv_flg_sales_area_check =    ld_pv_flg_sales_area_check
*   pv_vkorg =                   ld_pv_vkorg
*   pv_vtweg =                   ld_pv_vtweg
*   pv_spart =                   ld_pv_spart
    pv_regulierer =              ld_pv_regulierer
    pv_bkvid =                   ld_pv_bkvid
  IMPORTING
    ps_rjhabank =                ld_ps_rjhabank
  EXCEPTIONS
    PARAMETER_ERROR =            1
    BKVID_DOESNT_EXIST =         2
    LOCKED_IN_SALES_AREA =       3
    SALES_AREA_DOESNT_EXIST =    4
    NOT_IN_SALES_AREA =          5
    .  "  ISM_BANKDETAILS_READ_FROM_DB

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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 5. "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_ps_rjhabank
 
 TYPE RJHABANK_STR ,
ld_pv_flg_sapgp_active
 
 TYPE RJHALLG-XSAPGPACTIVE ,
ld_pv_flg_bank_sales_area
 
 TYPE RJHALLG-XBANKSALESAREA ,
ld_pv_flg_sales_area_check
 
 TYPE XFELD ,
ld_pv_vkorg
 
 TYPE RJHAK-VKORG ,
ld_pv_vtweg
 
 TYPE RJHAK-VTWEG ,
ld_pv_spart
 
 TYPE RJHAK-SPART ,
ld_pv_regulierer
 
 TYPE RJHAISZ-REGULIERER ,
ld_pv_bkvid
 
 TYPE BUT0BK-BKVID .



ld_pv_flg_sapgp_active = some text here

ld_pv_flg_bank_sales_area = some text here
ld_pv_flg_sales_area_check = 'Check type of data required'.

ld_pv_vkorg = some text here

ld_pv_vtweg = some text here

ld_pv_spart = some text here

ld_pv_regulierer = some text here

SELECT single BKVID 
  FROM BUT0BK 
  INTO ld_pv_bkvid.