ISHMED_ME_CHECK_ORDER_ED_STATE SAP Function module

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

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

Pattern for FM ISHMED_ME_CHECK_ORDER_ED_STATE - ISHMED ME CHECK ORDER ED STATE

CALL FUNCTION 'ISHMED_ME_CHECK_ORDER_ED_STATE' "
  EXPORTING
    ir_order =                  " cl_ishmed_me_order
    i_vcode =                   " ish_vcode
  IMPORTING
    e_hasseqtext =              " ish_on_off
    e_editable =                " ish_on_off
    e_rc =                      " ish_method_rc
    es_tn1ostatus =             " tn1ostatus
    es_tn1ostatust =            " tn1ostatust
  CHANGING
    cr_errorhandler =           " cl_ishmed_errorhandling
    .  "  ISHMED_ME_CHECK_ORDER_ED_STATE

ABAP code example for Function Module ISHMED_ME_CHECK_ORDER_ED_STATE

The ABAP code below is a full code listing to execute function module ISHMED_ME_CHECK_ORDER_ED_STATE 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_e_hasseqtext  
 
 TYPE ISH_ON_OFF
,
ld_e_editable  
 
 TYPE ISH_ON_OFF
,
ld_e_rc  
 
 TYPE ISH_METHOD_RC
,
ld_es_tn1ostatus  
 
 TYPE TN1OSTATUS
,
ld_es_tn1ostatust  
 
 TYPE TN1OSTATUST
.


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

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

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

CALL FUNCTION 'ISHMED_ME_CHECK_ORDER_ED_STATE'
  EXPORTING
    ir_order =                   ld_ir_order
    i_vcode =                    ld_i_vcode
  IMPORTING
    e_hasseqtext =               ld_e_hasseqtext
    e_editable =                 ld_e_editable
    e_rc =                       ld_e_rc
    es_tn1ostatus =              ld_es_tn1ostatus
    es_tn1ostatust =             ld_es_tn1ostatust
  CHANGING
    cr_errorhandler =            ld_cr_errorhandler
    .  "  ISHMED_ME_CHECK_ORDER_ED_STATE

IF SY-SUBRC EQ 0.
  "All OK
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_cr_errorhandler
 
 TYPE CL_ISHMED_ERRORHANDLING ,
ld_e_hasseqtext
 
 TYPE ISH_ON_OFF ,
ld_ir_order
 
 TYPE CL_ISHMED_ME_ORDER ,
ld_e_editable
 
 TYPE ISH_ON_OFF ,
ld_i_vcode
 
 TYPE ISH_VCODE ,
ld_e_rc
 
 TYPE ISH_METHOD_RC ,
ld_es_tn1ostatus
 
 TYPE TN1OSTATUS ,
ld_es_tn1ostatust
 
 TYPE TN1OSTATUST .


ld_cr_errorhandler = 'Check type of data required'.
ld_ir_order = 'Check type of data required'.
ld_i_vcode = 'Check type of data required'.