SAP CNVCF_SCWB_JOB_RELEASE Function Module for Release of background job (remote enabled)









CNVCF_SCWB_JOB_RELEASE is a standard cnvcf scwb job release SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release of background job (remote enabled) 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 cnvcf scwb job release FM, simply by entering the name CNVCF_SCWB_JOB_RELEASE into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNVC_SCWB_SATELLITE
Program Name: SAPLCNVC_SCWB_SATELLITE
Main Program: SAPLCNVC_SCWB_SATELLITE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function CNVCF_SCWB_JOB_RELEASE 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 'CNVCF_SCWB_JOB_RELEASE'"Release of background job (remote enabled)
EXPORTING
* JOBNAME = ' ' "
* JOBCOUNT = ' ' "

EXCEPTIONS
MISSING_JOBNAME = 1 JOB_HAVE_NO_STEPS = 10 ERROR_JOB_MODIFY = 11 MISSING_JOBCOUNT = 2 MISSING_START_DATE = 3 STATUS_NOT_SCHEDULED = 4 CANT_ENQ_JOB = 5 CANT_START_JOB_IMMEDIATELY = 6 NO_PRIVILEGE_TO_RELEASE_JOB = 7 CANT_RELEASE_JOB = 8 JOB_NOT_EXIST = 9
.



IMPORTING Parameters details for CNVCF_SCWB_JOB_RELEASE

JOBNAME -

Data type: TBTCJOB-JOBNAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

JOBCOUNT -

Data type: TBTCJOB-JOBCOUNT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

MISSING_JOBNAME -

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

JOB_HAVE_NO_STEPS -

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

ERROR_JOB_MODIFY -

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

MISSING_JOBCOUNT -

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

MISSING_START_DATE -

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

STATUS_NOT_SCHEDULED -

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

CANT_ENQ_JOB -

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

CANT_START_JOB_IMMEDIATELY -

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

NO_PRIVILEGE_TO_RELEASE_JOB -

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

CANT_RELEASE_JOB -

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

JOB_NOT_EXIST -

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

Copy and paste ABAP code example for CNVCF_SCWB_JOB_RELEASE 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:
lv_jobname  TYPE TBTCJOB-JOBNAME, "   SPACE
lv_missing_jobname  TYPE TBTCJOB, "   
lv_job_have_no_steps  TYPE TBTCJOB, "   
lv_error_job_modify  TYPE TBTCJOB, "   
lv_jobcount  TYPE TBTCJOB-JOBCOUNT, "   SPACE
lv_missing_jobcount  TYPE TBTCJOB, "   
lv_missing_start_date  TYPE TBTCJOB, "   
lv_status_not_scheduled  TYPE TBTCJOB, "   
lv_cant_enq_job  TYPE TBTCJOB, "   
lv_cant_start_job_immediately  TYPE TBTCJOB, "   
lv_no_privilege_to_release_job  TYPE TBTCJOB, "   
lv_cant_release_job  TYPE TBTCJOB, "   
lv_job_not_exist  TYPE TBTCJOB. "   

  CALL FUNCTION 'CNVCF_SCWB_JOB_RELEASE'  "Release of background job (remote enabled)
    EXPORTING
         JOBNAME = lv_jobname
         JOBCOUNT = lv_jobcount
    EXCEPTIONS
        MISSING_JOBNAME = 1
        JOB_HAVE_NO_STEPS = 10
        ERROR_JOB_MODIFY = 11
        MISSING_JOBCOUNT = 2
        MISSING_START_DATE = 3
        STATUS_NOT_SCHEDULED = 4
        CANT_ENQ_JOB = 5
        CANT_START_JOB_IMMEDIATELY = 6
        NO_PRIVILEGE_TO_RELEASE_JOB = 7
        CANT_RELEASE_JOB = 8
        JOB_NOT_EXIST = 9
. " CNVCF_SCWB_JOB_RELEASE




ABAP code using 7.40 inline data declarations to call FM CNVCF_SCWB_JOB_RELEASE

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.

"SELECT single JOBNAME FROM TBTCJOB INTO @DATA(ld_jobname).
DATA(ld_jobname) = ' '.
 
 
 
 
"SELECT single JOBCOUNT FROM TBTCJOB INTO @DATA(ld_jobcount).
DATA(ld_jobcount) = ' '.
 
 
 
 
 
 
 
 
 


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!