SAP CCDSNU_CHECK_MULTICONNECTION Function Module for Creates connection in DBCON for multiconnect if necessary

Search SAP Function Modules

CCDSNU_CHECK_MULTICONNECTION is a standard ccdsnu check multiconnection SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Creates connection in DBCON for multiconnect if necessary 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 ccdsnu check multiconnection FM, simply by entering the name CCDSNU_CHECK_MULTICONNECTION into the relevant SAP transaction such as SE37 or SE38.

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

Function CCDSNU_CHECK_MULTICONNECTION 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 'CCDSNU_CHECK_MULTICONNECTION'"Creates connection in DBCON for multiconnect if necessary
  EXPORTING
*  FORCED_TSOUSER =  "z/OS user ID
*  REMOTE_DBCON =  "Logical name for a database connection

 IMPORTING
   CONNECTION_NAME =  "Logical name for a database connection

EXCEPTIONS
   CONNECTION_NOT_DEFINED = 1    NOT_AUTHORIZED = 2    ENCRYPT_USER_FAILED = 3    DECRYPT_PASSWD_FAILED = 4    ENCRYPT_PASSWD_FAILED = 5    NO_TSO_USER = 6    CONNECT_FAILED = 7    ERROR_IN_CHECK_VERSION = 8 

.

IMPORTING Parameters details for CCDSNU_CHECK_MULTICONNECTION

FORCED_TSOUSER - z/OS user ID

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

REMOTE_DBCON - Logical name for a database connection

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

EXPORTING Parameters details for CCDSNU_CHECK_MULTICONNECTION

CONNECTION_NAME - Logical name for a database connection

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

EXCEPTIONS details

CONNECTION_NOT_DEFINED - Connection not defined in table DBCON

Data type:
Optional: No
Call by Reference: Yes

NOT_AUTHORIZED - User lacking authorization S_DB_DBSYS

Data type:
Optional: No
Call by Reference: Yes

ENCRYPT_USER_FAILED - Internal Error: Encryption of user failed

Data type:
Optional: No
Call by Reference: Yes

DECRYPT_PASSWD_FAILED - Internal Error: Decryption of password failed

Data type:
Optional: No
Call by Reference: Yes

ENCRYPT_PASSWD_FAILED - Internal Error: Encryption of password failed

Data type:
Optional: No
Call by Reference: Yes

NO_TSO_USER - Userr has not maintained his password in transaction DB2J

Data type:
Optional: No
Call by Reference: Yes

CONNECT_FAILED - Test connection failed

Data type:
Optional: No
Call by Reference: Yes

ERROR_IN_CHECK_VERSION - Checking version of remote DB failed

Data type:
Optional: No
Call by Reference: Yes

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

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