SAP CCDSNU_DSNACCOR_BACKUP Function Module for Call StoProc DSNACCOR for image COPY info

Search SAP Function Modules

CCDSNU_DSNACCOR_BACKUP is a standard ccdsnu dsnaccor backup SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Call StoProc DSNACCOR for image COPY info 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 dsnaccor backup FM, simply by entering the name CCDSNU_DSNACCOR_BACKUP 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_DSNACCOR_BACKUP 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_DSNACCOR_BACKUP'"Call StoProc DSNACCOR for image COPY  info
  EXPORTING
   CON_NAME =  "Logical name for a database connection
   USE_AL_LAZY =  "
*  CALLER =  "Transaction name of caller of DSNACCOR / DSNACCOX

TABLES
*  SMG_ALERT =  "DB2/390: Alert Tree: Single Messages

EXCEPTIONS
   ERROR_IN_CHECK_VERSION = 1    LESS_THAN_V7 = 2    UTILITY_ABORTED = 3    DSNACCOR_NOT_INSTALLED = 4    CREATE_DATABASE_FAILED = 5    SQL_ERROR = 6    RTS_NOT_INSTALLED = 7 

.

IMPORTING Parameters details for CCDSNU_DSNACCOR_BACKUP

CON_NAME - Logical name for a database connection

Data type: DBCON-CON_NAME
Optional: No
Call by Reference: Yes

USE_AL_LAZY -

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

CALLER - Transaction name of caller of DSNACCOR / DSNACCOX

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

TABLES Parameters details for CCDSNU_DSNACCOR_BACKUP

SMG_ALERT - DB2/390: Alert Tree: Single Messages

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

EXCEPTIONS details

ERROR_IN_CHECK_VERSION - Error in Function DBSYCHK_COMPARE_VERSION

Data type:
Optional: No
Call by Reference: Yes

LESS_THAN_V7 - The DB version is less than V7.1 => DSNACCOR is not available

Data type:
Optional: No
Call by Reference: Yes

UTILITY_ABORTED - Call of stored procedure didn't work

Data type:
Optional: No
Call by Reference: Yes

DSNACCOR_NOT_INSTALLED - DSNACCOR is not found in SYSIBM.SYSROUTINES

Data type:
Optional: No
Call by Reference: Yes

CREATE_DATABASE_FAILED - Creation of TEMP database or tablespace failed.

Data type:
Optional: No
Call by Reference: Yes

SQL_ERROR - EXEC SQL resulted in error.

Data type:
Optional: No
Call by Reference: Yes

RTS_NOT_INSTALLED - RTS database is not installed

Data type:
Optional: No
Call by Reference: Yes

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

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