SAP ISHMED_CHANGE_MED_DATAS Function Module for









ISHMED_CHANGE_MED_DATAS is a standard ishmed change med datas 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 ishmed change med datas FM, simply by entering the name ISHMED_CHANGE_MED_DATAS into the relevant SAP transaction such as SE37 or SE38.

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



Function ISHMED_CHANGE_MED_DATAS 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 'ISHMED_CHANGE_MED_DATAS'"
EXPORTING
SS_EINRI = "Institution
* SS_NFAL = "Case
SS_UNFNR_I = "Accident Number
* SS_OLD_NBEW = "
* SS_NEW_NBEW = "
SS_AUFRUFER = "Caller
* SS_BAPI = ' ' "
* SS_MESSAGES = 'X' "

IMPORTING
SS_RC = "Return Code
SS_UNFNR = "Accident Number
SS_DSPTY = "Scheduling Type
SS_VISTY = "Visit Category
ET_MESSAGES = "Notifications

EXCEPTIONS
NUMKR_NOT = 1
.



IMPORTING Parameters details for ISHMED_CHANGE_MED_DATAS

SS_EINRI - Institution

Data type: TNK01-EINRI
Optional: No
Call by Reference: No ( called with pass by value option)

SS_NFAL - Case

Data type: NFAL
Optional: Yes
Call by Reference: No ( called with pass by value option)

SS_UNFNR_I - Accident Number

Data type: NBEW-UNFNR
Optional: No
Call by Reference: No ( called with pass by value option)

SS_OLD_NBEW -

Data type: NBEW
Optional: Yes
Call by Reference: No ( called with pass by value option)

SS_NEW_NBEW -

Data type: NBEW
Optional: Yes
Call by Reference: No ( called with pass by value option)

SS_AUFRUFER - Caller

Data type: SY-REPID
Optional: No
Call by Reference: No ( called with pass by value option)

SS_BAPI -

Data type: RNT40-MARK
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SS_MESSAGES -

Data type: RNT40-MARK
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ISHMED_CHANGE_MED_DATAS

SS_RC - Return Code

Data type: INRI-RETURNCODE
Optional: No
Call by Reference: No ( called with pass by value option)

SS_UNFNR - Accident Number

Data type: NBEW-UNFNR
Optional: No
Call by Reference: No ( called with pass by value option)

SS_DSPTY - Scheduling Type

Data type: NBEW-DSPTY
Optional: No
Call by Reference: No ( called with pass by value option)

SS_VISTY - Visit Category

Data type: NBEW-VISTY
Optional: No
Call by Reference: No ( called with pass by value option)

ET_MESSAGES - Notifications

Data type: ISHMED_T_RN1CHKRET
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NUMKR_NOT - Number range not found

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ISHMED_CHANGE_MED_DATAS 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_ss_rc  TYPE INRI-RETURNCODE, "   
lv_ss_einri  TYPE TNK01-EINRI, "   
lv_numkr_not  TYPE TNK01, "   
lv_ss_nfal  TYPE NFAL, "   
lv_ss_unfnr  TYPE NBEW-UNFNR, "   
lv_ss_dspty  TYPE NBEW-DSPTY, "   
lv_ss_unfnr_i  TYPE NBEW-UNFNR, "   
lv_ss_visty  TYPE NBEW-VISTY, "   
lv_ss_old_nbew  TYPE NBEW, "   
lv_et_messages  TYPE ISHMED_T_RN1CHKRET, "   
lv_ss_new_nbew  TYPE NBEW, "   
lv_ss_aufrufer  TYPE SY-REPID, "   
lv_ss_bapi  TYPE RNT40-MARK, "   SPACE
lv_ss_messages  TYPE RNT40-MARK. "   'X'

  CALL FUNCTION 'ISHMED_CHANGE_MED_DATAS'  "
    EXPORTING
         SS_EINRI = lv_ss_einri
         SS_NFAL = lv_ss_nfal
         SS_UNFNR_I = lv_ss_unfnr_i
         SS_OLD_NBEW = lv_ss_old_nbew
         SS_NEW_NBEW = lv_ss_new_nbew
         SS_AUFRUFER = lv_ss_aufrufer
         SS_BAPI = lv_ss_bapi
         SS_MESSAGES = lv_ss_messages
    IMPORTING
         SS_RC = lv_ss_rc
         SS_UNFNR = lv_ss_unfnr
         SS_DSPTY = lv_ss_dspty
         SS_VISTY = lv_ss_visty
         ET_MESSAGES = lv_et_messages
    EXCEPTIONS
        NUMKR_NOT = 1
. " ISHMED_CHANGE_MED_DATAS




ABAP code using 7.40 inline data declarations to call FM ISHMED_CHANGE_MED_DATAS

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.

"SELECT single RETURNCODE FROM INRI INTO @DATA(ld_ss_rc).
 
"SELECT single EINRI FROM TNK01 INTO @DATA(ld_ss_einri).
 
 
 
"SELECT single UNFNR FROM NBEW INTO @DATA(ld_ss_unfnr).
 
"SELECT single DSPTY FROM NBEW INTO @DATA(ld_ss_dspty).
 
"SELECT single UNFNR FROM NBEW INTO @DATA(ld_ss_unfnr_i).
 
"SELECT single VISTY FROM NBEW INTO @DATA(ld_ss_visty).
 
 
 
 
"SELECT single REPID FROM SY INTO @DATA(ld_ss_aufrufer).
 
"SELECT single MARK FROM RNT40 INTO @DATA(ld_ss_bapi).
DATA(ld_ss_bapi) = ' '.
 
"SELECT single MARK FROM RNT40 INTO @DATA(ld_ss_messages).
DATA(ld_ss_messages) = 'X'.
 


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!