SAP CCDSNU_UPLOAD_JOB Function Module for Upload via Stored Procedure DSNACCDS as FTP replacement
CCDSNU_UPLOAD_JOB is a standard ccdsnu upload job SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Upload via Stored Procedure DSNACCDS as FTP replacement 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 upload job FM, simply by entering the name CCDSNU_UPLOAD_JOB 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_UPLOAD_JOB 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_UPLOAD_JOB'"Upload via Stored Procedure DSNACCDS as FTP replacement.
EXPORTING
OS390_DATASET_MEMBER_NAME = "Name of partitioned dataset (PDS) member
* REMOTE_DBCON = "Logical name for a database connection
IMPORTING
OS390_UPLOAD_TARGET = "Full name of a PDS member (incl. PDS name and brackets)
MESSAGE = "Area of the CC stored procedures output values
TABLES
DS_TBL = "Structure of global temp DS input table DSNACC.DSNRECORDS
EXCEPTIONS
ERROR_IN_CHECK_VERSION = 1 LESS_THAN_V7 = 2 STOPROC_ABORTED = 3 DSNACCDS_NOT_INSTALLED = 4 CREATE_DATABASE_FAILED = 5 NO_INPUT_TABLES = 6 SQL_ERROR = 7 DATASET_BLOCKED = 8
IMPORTING Parameters details for CCDSNU_UPLOAD_JOB
OS390_DATASET_MEMBER_NAME - Name of partitioned dataset (PDS) member
Data type: DB2MEMBERNAMEOptional: No
Call by Reference: No ( called with pass by value option)
REMOTE_DBCON - Logical name for a database connection
Data type: DBCON_NAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CCDSNU_UPLOAD_JOB
OS390_UPLOAD_TARGET - Full name of a PDS member (incl. PDS name and brackets)
Data type: DB2FULLMEMBERNAMEOptional: No
Call by Reference: Yes
MESSAGE - Area of the CC stored procedures output values
Data type: DB2CCMTXTOptional: No
Call by Reference: Yes
TABLES Parameters details for CCDSNU_UPLOAD_JOB
DS_TBL - Structure of global temp DS input table DSNACC.DSNRECORDS
Data type: DB2CCDSINOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_IN_CHECK_VERSION - Error in Function DBSYCHK_COMPARE_VERSION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
LESS_THAN_V7 - The DB version is less than V7.1 => DSNACCOR is not available
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STOPROC_ABORTED - Call of stored procedure didn't work
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DSNACCDS_NOT_INSTALLED - DSNACCDS is not found in SYSIBM.SYSROUTINES
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CREATE_DATABASE_FAILED - Creation of TEMP database or tablespace failed.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_INPUT_TABLES - The required global temp tables are not installed.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SQL_ERROR - EXEC SQL resulted in error.
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATASET_BLOCKED - Dataset already in use (i.e. allocated to another job or user)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CCDSNU_UPLOAD_JOB 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_ds_tbl | TYPE STANDARD TABLE OF DB2CCDSIN, " | |||
| lv_os390_upload_target | TYPE DB2FULLMEMBERNAME, " | |||
| lv_error_in_check_version | TYPE DB2FULLMEMBERNAME, " | |||
| lv_os390_dataset_member_name | TYPE DB2MEMBERNAME, " | |||
| lv_message | TYPE DB2CCMTXT, " | |||
| lv_less_than_v7 | TYPE DB2CCMTXT, " | |||
| lv_remote_dbcon | TYPE DBCON_NAME, " | |||
| lv_stoproc_aborted | TYPE DBCON_NAME, " | |||
| lv_dsnaccds_not_installed | TYPE DBCON_NAME, " | |||
| lv_create_database_failed | TYPE DBCON_NAME, " | |||
| lv_no_input_tables | TYPE DBCON_NAME, " | |||
| lv_sql_error | TYPE DBCON_NAME, " | |||
| lv_dataset_blocked | TYPE DBCON_NAME. " |
|   CALL FUNCTION 'CCDSNU_UPLOAD_JOB' "Upload via Stored Procedure DSNACCDS as FTP replacement |
| EXPORTING | ||
| OS390_DATASET_MEMBER_NAME | = lv_os390_dataset_member_name | |
| REMOTE_DBCON | = lv_remote_dbcon | |
| IMPORTING | ||
| OS390_UPLOAD_TARGET | = lv_os390_upload_target | |
| MESSAGE | = lv_message | |
| TABLES | ||
| DS_TBL | = lt_ds_tbl | |
| EXCEPTIONS | ||
| ERROR_IN_CHECK_VERSION = 1 | ||
| LESS_THAN_V7 = 2 | ||
| STOPROC_ABORTED = 3 | ||
| DSNACCDS_NOT_INSTALLED = 4 | ||
| CREATE_DATABASE_FAILED = 5 | ||
| NO_INPUT_TABLES = 6 | ||
| SQL_ERROR = 7 | ||
| DATASET_BLOCKED = 8 | ||
| . " CCDSNU_UPLOAD_JOB | ||
ABAP code using 7.40 inline data declarations to call FM CCDSNU_UPLOAD_JOB
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