SAP ISH_CH_MCD_BFS_GET Function Module for









ISH_CH_MCD_BFS_GET is a standard ish ch mcd bfs get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 ish ch mcd bfs get FM, simply by entering the name ISH_CH_MCD_BFS_GET into the relevant SAP transaction such as SE37 or SE38.

Function Group: NWCHDRG_BFS
Program Name: SAPLNWCHDRG_BFS
Main Program: SAPLNWCHDRG_BFS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ISH_CH_MCD_BFS_GET 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 'ISH_CH_MCD_BFS_GET'"
EXPORTING
I_EINRI = "
* IT_NAPX_BEW = "
* IT_NAPX_DIA = "
* IT_NAPX_ICP = "
* IT_NDIA = "
* IT_NICP = "
* IT_NGEB = "
* I_MEDI = '' "
* IT_NLEI = "
I_FALNR = "
* I_READMISSION = '' "
* I_DATVON = "
* I_DATBIS = "
* IS_NFAL = "
* IS_NPAT = "
* IT_NBEW = "
* IT_NAPX_FAL = "

IMPORTING
ES_MCD_BFS = "
ES_MED = "

EXCEPTIONS
NO_RELEVANT_DATA = 1 NO_READMISSION_CASE = 2
.



IMPORTING Parameters details for ISH_CH_MCD_BFS_GET

I_EINRI -

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

IT_NAPX_BEW -

Data type: ISH_T_NAPX_BEW
Optional: Yes
Call by Reference: Yes

IT_NAPX_DIA -

Data type: ISH_T_NAPX_DIA
Optional: Yes
Call by Reference: Yes

IT_NAPX_ICP -

Data type: ISH_T_NAPX_ICP
Optional: Yes
Call by Reference: Yes

IT_NDIA -

Data type: ISH_T_NDIA
Optional: Yes
Call by Reference: Yes

IT_NICP -

Data type: ISH_YT_NICP
Optional: Yes
Call by Reference: Yes

IT_NGEB -

Data type: ISH_YT_NGEB
Optional: Yes
Call by Reference: Yes

I_MEDI -

Data type: ISH_ON_OFF
Default: ''
Optional: Yes
Call by Reference: Yes

IT_NLEI -

Data type: ISH_T_NLEI
Optional: Yes
Call by Reference: Yes

I_FALNR -

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

I_READMISSION -

Data type: ISH_ON_OFF
Default: ''
Optional: Yes
Call by Reference: Yes

I_DATVON -

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

I_DATBIS -

Data type: SY-DATUM
Optional: Yes
Call by Reference: Yes

IS_NFAL -

Data type: NFAL
Optional: Yes
Call by Reference: Yes

IS_NPAT -

Data type: NPAT
Optional: Yes
Call by Reference: Yes

IT_NBEW -

Data type: ISH_T_NBEW
Optional: Yes
Call by Reference: Yes

IT_NAPX_FAL -

Data type: ISH_T_NAPX_FAL
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ISH_CH_MCD_BFS_GET

ES_MCD_BFS -

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

ES_MED -

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

EXCEPTIONS details

NO_RELEVANT_DATA -

Data type:
Optional: No
Call by Reference: Yes

NO_READMISSION_CASE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISH_CH_MCD_BFS_GET 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_i_einri  TYPE EINRI, "   
lv_es_mcd_bfs  TYPE RNWCH_SDRG_BFS_DATA, "   
lv_no_relevant_data  TYPE RNWCH_SDRG_BFS_DATA, "   
lv_it_napx_bew  TYPE ISH_T_NAPX_BEW, "   
lv_it_napx_dia  TYPE ISH_T_NAPX_DIA, "   
lv_it_napx_icp  TYPE ISH_T_NAPX_ICP, "   
lv_it_ndia  TYPE ISH_T_NDIA, "   
lv_it_nicp  TYPE ISH_YT_NICP, "   
lv_it_ngeb  TYPE ISH_YT_NGEB, "   
lv_i_medi  TYPE ISH_ON_OFF, "   ''
lv_it_nlei  TYPE ISH_T_NLEI, "   
lv_es_med  TYPE RNWCH_SDRG_MED_DATA, "   
lv_i_falnr  TYPE FALNR, "   
lv_no_readmission_case  TYPE FALNR, "   
lv_i_readmission  TYPE ISH_ON_OFF, "   ''
lv_i_datvon  TYPE SY-DATUM, "   
lv_i_datbis  TYPE SY-DATUM, "   
lv_is_nfal  TYPE NFAL, "   
lv_is_npat  TYPE NPAT, "   
lv_it_nbew  TYPE ISH_T_NBEW, "   
lv_it_napx_fal  TYPE ISH_T_NAPX_FAL. "   

  CALL FUNCTION 'ISH_CH_MCD_BFS_GET'  "
    EXPORTING
         I_EINRI = lv_i_einri
         IT_NAPX_BEW = lv_it_napx_bew
         IT_NAPX_DIA = lv_it_napx_dia
         IT_NAPX_ICP = lv_it_napx_icp
         IT_NDIA = lv_it_ndia
         IT_NICP = lv_it_nicp
         IT_NGEB = lv_it_ngeb
         I_MEDI = lv_i_medi
         IT_NLEI = lv_it_nlei
         I_FALNR = lv_i_falnr
         I_READMISSION = lv_i_readmission
         I_DATVON = lv_i_datvon
         I_DATBIS = lv_i_datbis
         IS_NFAL = lv_is_nfal
         IS_NPAT = lv_is_npat
         IT_NBEW = lv_it_nbew
         IT_NAPX_FAL = lv_it_napx_fal
    IMPORTING
         ES_MCD_BFS = lv_es_mcd_bfs
         ES_MED = lv_es_med
    EXCEPTIONS
        NO_RELEVANT_DATA = 1
        NO_READMISSION_CASE = 2
. " ISH_CH_MCD_BFS_GET




ABAP code using 7.40 inline data declarations to call FM ISH_CH_MCD_BFS_GET

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.

 
 
 
 
 
 
 
 
 
DATA(ld_i_medi) = ''.
 
 
 
 
 
DATA(ld_i_readmission) = ''.
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_datvon).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_i_datbis).
 
 
 
 
 


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!