SAP Function Modules

comments icon Comments

CTS_WBO_API_CHECK_OBJECTS SAP Function module







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

Associated Function Group: CTS_WBO_API
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CTS_WBO_API_CHECK_OBJECTS - CTS WBO API CHECK OBJECTS 





CALL FUNCTION 'CTS_WBO_API_CHECK_OBJECTS' "
  EXPORTING
    recording_entries =         " cts_recording_entries
*   as4user = SY-UNAME          " tr_as4user
*   req_attr_keys =             " cts_req_attr_keys
*   no_explicit_dbcommit = SPACE  " cts_boolean
  IMPORTING
    check_result =              " cts_check_result
    messages =                  " cts_messages
    requests =                  " cts_requests
    object_locks =              " cts_object_locks
* CHANGING
*   ct_ko200 =                  " tredt_objects
*   ct_e071k =                  " tredt_keys
    .  "  CTS_WBO_API_CHECK_OBJECTS

ABAP code example for Function Module CTS_WBO_API_CHECK_OBJECTS





The ABAP code below is a full code listing to execute function module CTS_WBO_API_CHECK_OBJECTS 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_check_result    TYPE CTS_CHECK_RESULT
,
ld_messages    TYPE CTS_MESSAGES
,
ld_requests    TYPE CTS_REQUESTS
,
ld_object_locks    TYPE CTS_OBJECT_LOCKS
.




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

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

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

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

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

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

CALL FUNCTION 'CTS_WBO_API_CHECK_OBJECTS'
  EXPORTING
    recording_entries =          ld_recording_entries
*   as4user =                    ld_as4user
*   req_attr_keys =              ld_req_attr_keys
*   no_explicit_dbcommit =       ld_no_explicit_dbcommit
  IMPORTING
    check_result =               ld_check_result
    messages =                   ld_messages
    requests =                   ld_requests
    object_locks =               ld_object_locks
* CHANGING
*   ct_ko200 =                   ld_ct_ko200
*   ct_e071k =                   ld_ct_e071k
    .  "  CTS_WBO_API_CHECK_OBJECTS

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_ct_ko200  TYPE TREDT_OBJECTS ,
ld_check_result  TYPE CTS_CHECK_RESULT ,
ld_recording_entries  TYPE CTS_RECORDING_ENTRIES ,
ld_ct_e071k  TYPE TREDT_KEYS ,
ld_messages  TYPE CTS_MESSAGES ,
ld_as4user  TYPE TR_AS4USER ,
ld_requests  TYPE CTS_REQUESTS ,
ld_req_attr_keys  TYPE CTS_REQ_ATTR_KEYS ,
ld_object_locks  TYPE CTS_OBJECT_LOCKS ,
ld_no_explicit_dbcommit  TYPE CTS_BOOLEAN .




ld_ct_ko200 = 'Check type of data required'.
ld_recording_entries = 'Check type of data required'.
ld_ct_e071k = 'Check type of data required'.
ld_as4user = 'Check type of data required'.
ld_req_attr_keys = 'Check type of data required'.
ld_no_explicit_dbcommit = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CTS_WBO_API_CHECK_OBJECTS or its description.


   
 

CTS_WBO_API_CHECK_OBJECTS - 
CTS_UPLOAD_BYTES_INTO_FILE - uploads some bytes into the file
CTS_UPDATE_TABDIRDEVC - 
CTS_UPDATE_CUSDVCLANG - 
CTS_UNLOCK_TRKORR - 
CTS_TABLINES_GET_ORIG_LANG_STR -