OCS_CHECK_ADD_ON SAP Function module

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

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

Pattern for FM OCS_CHECK_ADD_ON - OCS CHECK ADD ON

CALL FUNCTION 'OCS_CHECK_ADD_ON' "
  EXPORTING
    is_pat07 =                  " pat07
*   iv_no_pat03_search = SPACE  " c
*   iv_consider_sfw_state = SPACE  " c
*   iv_strict_check = SPACE     " c
    it_patq =                   " tt_pat_q2
  IMPORTING
    ev_ok =                     " c
    ev_patch =                  " pat03-patch
    es_bad_patch =              " bad_patch
  EXCEPTIONS
    INTERNAL_ERROR = 1          "
    .  "  OCS_CHECK_ADD_ON

ABAP code example for Function Module OCS_CHECK_ADD_ON

The ABAP code below is a full code listing to execute function module OCS_CHECK_ADD_ON 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_ev_ok  
 
 TYPE C
,
ld_ev_patch  
 
 TYPE PAT03-PATCH
,
ld_es_bad_patch  
 
 TYPE BAD_PATCH
.


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

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

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

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

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

CALL FUNCTION 'OCS_CHECK_ADD_ON'
  EXPORTING
    is_pat07 =                   ld_is_pat07
*   iv_no_pat03_search =         ld_iv_no_pat03_search
*   iv_consider_sfw_state =      ld_iv_consider_sfw_state
*   iv_strict_check =            ld_iv_strict_check
    it_patq =                    ld_it_patq
  IMPORTING
    ev_ok =                      ld_ev_ok
    ev_patch =                   ld_ev_patch
    es_bad_patch =               ld_es_bad_patch
  EXCEPTIONS
    INTERNAL_ERROR =             1
    .  "  OCS_CHECK_ADD_ON

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_ev_ok
 
 TYPE C ,
ld_is_pat07
 
 TYPE PAT07 ,
ld_ev_patch
 
 TYPE PAT03-PATCH ,
ld_iv_no_pat03_search
 
 TYPE C ,
ld_es_bad_patch
 
 TYPE BAD_PATCH ,
ld_iv_consider_sfw_state
 
 TYPE C ,
ld_iv_strict_check
 
 TYPE C ,
ld_it_patq
 
 TYPE TT_PAT_Q2 .


ld_is_pat07 = 'Check type of data required'.
ld_iv_no_pat03_search = 'Check type of data required'.
ld_iv_consider_sfw_state = 'Check type of data required'.
ld_iv_strict_check = 'Check type of data required'.
ld_it_patq = 'Check type of data required'.