SAP OCS_CHECK_DECLARATION Function Module for









OCS_CHECK_DECLARATION is a standard ocs check declaration 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 ocs check declaration FM, simply by entering the name OCS_CHECK_DECLARATION into the relevant SAP transaction such as SE37 or SE38.

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



Function OCS_CHECK_DECLARATION 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 'OCS_CHECK_DECLARATION'"
EXPORTING
IS_PAT07 = "
IT_PAT07 = "

IMPORTING
EV_OK = "
ES_BAD_PATCH = "

EXCEPTIONS
NEED_SPAM_UPDATE = 1 INTERNAL_ERROR = 2
.



IMPORTING Parameters details for OCS_CHECK_DECLARATION

IS_PAT07 -

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

IT_PAT07 -

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

EXPORTING Parameters details for OCS_CHECK_DECLARATION

EV_OK -

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

ES_BAD_PATCH -

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

EXCEPTIONS details

NEED_SPAM_UPDATE -

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

INTERNAL_ERROR -

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

Copy and paste ABAP code example for OCS_CHECK_DECLARATION 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_ev_ok  TYPE C, "   
lv_is_pat07  TYPE PAT07, "   
lv_need_spam_update  TYPE PAT07, "   
lv_it_pat07  TYPE TT_PAT07, "   
lv_es_bad_patch  TYPE BAD_PATCH, "   
lv_internal_error  TYPE BAD_PATCH. "   

  CALL FUNCTION 'OCS_CHECK_DECLARATION'  "
    EXPORTING
         IS_PAT07 = lv_is_pat07
         IT_PAT07 = lv_it_pat07
    IMPORTING
         EV_OK = lv_ev_ok
         ES_BAD_PATCH = lv_es_bad_patch
    EXCEPTIONS
        NEED_SPAM_UPDATE = 1
        INTERNAL_ERROR = 2
. " OCS_CHECK_DECLARATION




ABAP code using 7.40 inline data declarations to call FM OCS_CHECK_DECLARATION

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.

 
 
 
 
 
 


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!