CATS_UPDATE SAP Function module

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

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

Pattern for FM CATS_UPDATE - CATS UPDATE

CALL FUNCTION 'CATS_UPDATE' "
* EXPORTING
*   commit_work = 'X'           " catsfields-yesorno  Yes/No Switch with Values 'SPACE' and 'X'
*   cats_text_format =          " cats_text_format  Text Format for Long Text
*   get_counter = 'X'           " catsfields-yesorno
*   update_database = 'X'       " catsfields-yesorno  Yes/No Switch with Values 'SPACE' and 'X'
  TABLES
    catsdb_in =                 " catsdbcomm    CATS: Communication Structure for CATSDB
    longtext =                  " longtext_ext  External Format of CATS Long Text
    .  "  CATS_UPDATE

ABAP code example for Function Module CATS_UPDATE

The ABAP code below is a full code listing to execute function module CATS_UPDATE 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:
it_catsdb_in  
 
 TYPE STANDARD TABLE OF CATSDBCOMM,"TABLES PARAM
wa_catsdb_in
 
 LIKE LINE OF it_catsdb_in
,
it_longtext  
 
 TYPE STANDARD TABLE OF LONGTEXT_EXT,"TABLES PARAM
wa_longtext
 
 LIKE LINE OF it_longtext
.



DATA(ld_commit_work) = some text here

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


DATA(ld_get_counter) = some text here


DATA(ld_update_database) = some text here
 

"populate fields of struture and append to itab
append wa_catsdb_in to it_catsdb_in.
 

"populate fields of struture and append to itab
append wa_longtext to it_longtext.
.

CALL FUNCTION 'CATS_UPDATE'
* EXPORTING
*   commit_work =                ld_commit_work
*   cats_text_format =           ld_cats_text_format
*   get_counter =                ld_get_counter
*   update_database =            ld_update_database
  TABLES
    catsdb_in =                  it_catsdb_in
    longtext =                   it_longtext
    .  "  CATS_UPDATE

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_commit_work
 
 TYPE CATSFIELDS-YESORNO ,
it_catsdb_in
 
 TYPE STANDARD TABLE OF CATSDBCOMM ,
wa_catsdb_in
 
 LIKE LINE OF it_catsdb_in,
ld_cats_text_format
 
 TYPE CATS_TEXT_FORMAT ,
it_longtext
 
 TYPE STANDARD TABLE OF LONGTEXT_EXT ,
wa_longtext
 
 LIKE LINE OF it_longtext,
ld_get_counter
 
 TYPE CATSFIELDS-YESORNO ,
ld_update_database
 
 TYPE CATSFIELDS-YESORNO .



ld_commit_work = some text here 

"populate fields of struture and append to itab
append wa_catsdb_in to it_catsdb_in.
ld_cats_text_format = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_longtext to it_longtext.

ld_get_counter = some text here

ld_update_database = some text here