SAP OBJECT_CHECK_WCAW Function Module for WCM: Internal use of the Classification









OBJECT_CHECK_WCAW is a standard object check wcaw SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for WCM: Internal use of the Classification processing and below is the pattern details for this FM, 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 object check wcaw FM, simply by entering the name OBJECT_CHECK_WCAW into the relevant SAP transaction such as SE37 or SE38.

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



Function OBJECT_CHECK_WCAW 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 'OBJECT_CHECK_WCAW'"WCM: Internal use of the Classification
  EXPORTING
*  CALLED_FROM = 1 "1=from doc. 2=from class
*  LANGUAGE = SY-LANGU "Read lang. for short texts (request)
*  LOCK = ' ' "
*  SINGLE = ' ' "
*  DATE_OF_CHANGE =  "Change Date
*  I_AUTH_CHK =  "Indicator

 IMPORTING
   FAULT_TEXT =  "Error Text for Output in Classification
   MESSAGE_TYPE =  "Message Type E,W,I, or S
   NO_AUTH =  "No Authorization for Object

TABLES
   OTAB =  "

EXCEPTIONS
   FOREIGN_LOCK = 1    OBJECT_NOT_FOUND = 2    SYSTEM_FAILURE = 3
.



IMPORTING Parameters details for OBJECT_CHECK_WCAW

CALLED_FROM - 1=from doc. 2=from class

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

LANGUAGE - Read lang. for short texts (request)

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

LOCK -

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

SINGLE -

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

DATE_OF_CHANGE - Change Date

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

I_AUTH_CHK - Indicator

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

EXPORTING Parameters details for OBJECT_CHECK_WCAW

FAULT_TEXT - Error Text for Output in Classification

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

MESSAGE_TYPE - Message Type E,W,I, or S

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

NO_AUTH - No Authorization for Object

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

TABLES Parameters details for OBJECT_CHECK_WCAW

OTAB -

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

EXCEPTIONS details

FOREIGN_LOCK -

Data type:
Optional: No
Call by Reference: Yes

OBJECT_NOT_FOUND - Object Not Found

Data type:
Optional: No
Call by Reference: Yes

SYSTEM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for OBJECT_CHECK_WCAW 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:
lt_otab  TYPE STANDARD TABLE OF RMCLOBTX, "   
lv_fault_text  TYPE RMCLOBTX, "   
lv_called_from  TYPE RMCLOBTX, "   1
lv_foreign_lock  TYPE RMCLOBTX, "   
lv_language  TYPE SYLANGU, "   SY-LANGU
lv_message_type  TYPE SYLANGU, "   
lv_object_not_found  TYPE SYLANGU, "   
lv_lock  TYPE SYLANGU, "   SPACE
lv_no_auth  TYPE SYLANGU, "   
lv_system_failure  TYPE SYLANGU, "   
lv_single  TYPE SYLANGU, "   SPACE
lv_date_of_change  TYPE SYDATUM, "   
lv_i_auth_chk  TYPE ANKREUZ. "   

  CALL FUNCTION 'OBJECT_CHECK_WCAW'  "WCM: Internal use of the Classification
    EXPORTING
         CALLED_FROM = lv_called_from
         LANGUAGE = lv_language
         LOCK = lv_lock
         SINGLE = lv_single
         DATE_OF_CHANGE = lv_date_of_change
         I_AUTH_CHK = lv_i_auth_chk
    IMPORTING
         FAULT_TEXT = lv_fault_text
         MESSAGE_TYPE = lv_message_type
         NO_AUTH = lv_no_auth
    TABLES
         OTAB = lt_otab
    EXCEPTIONS
        FOREIGN_LOCK = 1
        OBJECT_NOT_FOUND = 2
        SYSTEM_FAILURE = 3
. " OBJECT_CHECK_WCAW




ABAP code using 7.40 inline data declarations to call FM OBJECT_CHECK_WCAW

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.

 
 
DATA(ld_called_from) = 1.
 
 
DATA(ld_language) = SY-LANGU.
 
 
 
DATA(ld_lock) = ' '.
 
 
 
DATA(ld_single) = ' '.
 
 
 


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!