SAP SUSR_SYNC_USER_TABLES Function Module for









SUSR_SYNC_USER_TABLES is a standard susr sync user tables 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 susr sync user tables FM, simply by entering the name SUSR_SYNC_USER_TABLES into the relevant SAP transaction such as SE37 or SE38.

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



Function SUSR_SYNC_USER_TABLES 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 'SUSR_SYNC_USER_TABLES'"
EXPORTING
* TABLETYPE = 'U' "Synchronize U=usr04, P=usr10, A=usr12
* CLIENT = "Client (if empty: sy client)
* DISPLAY_MESSAGES = ' ' "

TABLES
* IT_MSGS = "

EXCEPTIONS
BAD_CLIENT = 1
.



IMPORTING Parameters details for SUSR_SYNC_USER_TABLES

TABLETYPE - Synchronize U=usr04, P=usr10, A=usr12

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

CLIENT - Client (if empty: sy client)

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

DISPLAY_MESSAGES -

Data type: CHAR01
Default: SPACE
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for SUSR_SYNC_USER_TABLES

IT_MSGS -

Data type: CMD_T_MSG
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

BAD_CLIENT - CLIENT does not exist in table T000

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

Copy and paste ABAP code example for SUSR_SYNC_USER_TABLES 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_it_msgs  TYPE STANDARD TABLE OF CMD_T_MSG, "   
lv_tabletype  TYPE CHAR01, "   'U'
lv_bad_client  TYPE CHAR01, "   
lv_client  TYPE SYMANDT, "   
lv_display_messages  TYPE CHAR01. "   SPACE

  CALL FUNCTION 'SUSR_SYNC_USER_TABLES'  "
    EXPORTING
         TABLETYPE = lv_tabletype
         CLIENT = lv_client
         DISPLAY_MESSAGES = lv_display_messages
    TABLES
         IT_MSGS = lt_it_msgs
    EXCEPTIONS
        BAD_CLIENT = 1
. " SUSR_SYNC_USER_TABLES




ABAP code using 7.40 inline data declarations to call FM SUSR_SYNC_USER_TABLES

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_tabletype) = 'U'.
 
 
 
DATA(ld_display_messages) = ' '.
 


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!