Job without start date.
To execute the job, use the methods BackgroundJob.StartAsSoonAsPossibleor .StartImmediately.
You must first create the job with the method BackgroundJob.Open andthen add at least one job step to the job using the methodsBackgroundJob.AddABAPStep or .BackgroundJob.AddExternalStep.
Further information
XBP documentation (SAPnet/CCMS)
Description
INCLUDE BAPI_TABLE
Value range
MSG_JOBID_MISSING: You have not identified the job to which the jobstep is to be added. Either the job name or the job count is missing,or both.
MSG_JOB_DOES_NOT_EXIST: The job that you specified by job name and jobcount does not exist in the R/3 System.
MSG_PROBLEM_DETECTED: The background processing system has detected anerror. You can find an exact description of the problem in the R/3System log.
MSG_CANT_LOG: The method call was terminated due to an error in the R/3XMI logging system.
MSG_EXT_USER_MISSING: The external user name was not specified in thecall. This name specifies the user in the external system who triggeredthe method call.
MSG_NOT_LOGGED_ON: The external system administration tool has notlogged onto the CCMS XMI interface. The method call was terminated as aresult.
INCLUDE BAPI_XBP_EXTERNAL_USER_NAME ID TX
INCLUDE BAPI_XBP_JOBCOUNT ID TX
INCLUDE BAPI_XBP_JOBNAME ID TX
Description
Optional: With this parameter you can have the job executed on the R/3instance that you specify. This instance must be available at the jobstart date to the work processes for the background processing system.
You should normally leave this parameter empty. Assigning a job to aspecific instance automatically cancels automatic load distribution inthe background processing system. Assigning a job to a specificinstance is only useful if, for example, a specific resource can onlybe accessed from the instance.