OMR_HAS_SELECTION_CONDITION SAP Function module

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

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

Pattern for FM OMR_HAS_SELECTION_CONDITION - OMR HAS SELECTION CONDITION

CALL FUNCTION 'OMR_HAS_SELECTION_CONDITION' "
  EXPORTING
    iself =                     " cocom_insts
    object_id =                 " cocom_object_id
    cfg =                       " xco_cfg
  IMPORTING
    standard =                  " x
  CHANGING
    source =                    " omdep_source
*   sap_source =                " omdep_source
  EXCEPTIONS
    NO_SELECTION_CONDITION = 1  "
    MORE_THEN_ONE = 2           "
    .  "  OMR_HAS_SELECTION_CONDITION

ABAP code example for Function Module OMR_HAS_SELECTION_CONDITION

The ABAP code below is a full code listing to execute function module OMR_HAS_SELECTION_CONDITION 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_standard  
 
 TYPE X
.


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

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

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

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

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

CALL FUNCTION 'OMR_HAS_SELECTION_CONDITION'
  EXPORTING
    iself =                      ld_iself
    object_id =                  ld_object_id
    cfg =                        ld_cfg
  IMPORTING
    standard =                   ld_standard
  CHANGING
    source =                     ld_source
*   sap_source =                 ld_sap_source
  EXCEPTIONS
    NO_SELECTION_CONDITION =     1
    MORE_THEN_ONE =              2
    .  "  OMR_HAS_SELECTION_CONDITION

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_source
 
 TYPE OMDEP_SOURCE ,
ld_standard
 
 TYPE X ,
ld_iself
 
 TYPE COCOM_INSTS ,
ld_sap_source
 
 TYPE OMDEP_SOURCE ,
ld_object_id
 
 TYPE COCOM_OBJECT_ID ,
ld_cfg
 
 TYPE XCO_CFG .


ld_source = 'Check type of data required'.
ld_iself = 'Check type of data required'.
ld_sap_source = 'Check type of data required'.
ld_object_id = 'Check type of data required'.
ld_cfg = 'Check type of data required'.