SAP TMS_MGR_ACCEPT_NEW_CLIENT Function Module for

Search SAP Function Modules

TMS_MGR_ACCEPT_NEW_CLIENT is a standard tms mgr accept new client 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 tms mgr accept new client FM, simply by entering the name TMS_MGR_ACCEPT_NEW_CLIENT into the relevant SAP transaction such as SE37 or SE38.

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

Function TMS_MGR_ACCEPT_NEW_CLIENT 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 'TMS_MGR_ACCEPT_NEW_CLIENT'"
  EXPORTING
   IV_CLIENT_NAME =  "
*  IV_INACTIVE =  "
*  IV_VERBOSE =  "

 IMPORTING
   EV_CHECK_GRP_FAILED =  "
   EV_GRP_CHANGED =  "
   EV_NEW_GROUP =  "
   EV_ALERTID =  "

EXCEPTIONS
   READ_CONFIG_FAILED = 1    NOT_A_CONTROLLER = 2    REQUEST_NOT_FOUND = 3    CLIENT_ALREADY_ACTIVE = 4    ENQUEUE_TMS_CONFIG_FAILED = 5    UPDATE_CI_CONFIG_FAILED = 6    UPDATE_TP_CONFIG_FAILED = 7    DIST_CI_CONFIG_ALERT = 8    DIST_CI_CONFIG_FAILED = 9 

.

IMPORTING Parameters details for TMS_MGR_ACCEPT_NEW_CLIENT

IV_CLIENT_NAME -

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

IV_INACTIVE -

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

IV_VERBOSE -

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

EXPORTING Parameters details for TMS_MGR_ACCEPT_NEW_CLIENT

EV_CHECK_GRP_FAILED -

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

EV_GRP_CHANGED -

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

EV_NEW_GROUP -

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

EV_ALERTID -

Data type: STMSCALERT-ID
Optional: No
Call by Reference: Yes

EXCEPTIONS details

READ_CONFIG_FAILED -

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

NOT_A_CONTROLLER -

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

REQUEST_NOT_FOUND -

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

CLIENT_ALREADY_ACTIVE -

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

ENQUEUE_TMS_CONFIG_FAILED -

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

UPDATE_CI_CONFIG_FAILED -

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

UPDATE_TP_CONFIG_FAILED -

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

DIST_CI_CONFIG_ALERT -

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

DIST_CI_CONFIG_FAILED -

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

Copy and paste ABAP code example for TMS_MGR_ACCEPT_NEW_CLIENT 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.

ABAP code using 7.40 inline data declarations to call FM TMS_MGR_ACCEPT_NEW_CLIENT

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