Functionality
With this method, you execute a job in the R/3 background processingsystem. The method specifies that the job should be startedimmediately. If this is not possible (for example, if no backgroundwork processes are free at that time), the job is placed in a queue andis processed as soon as possible.
Alternative: Method BackgroundJob.StartImmediately. If the job cannotbe executed immediately, this method returns an error.
Before you can use this method, you must first define the job with themethods BackgroundJob.Open and BackgroundJob.AddABAPStep orBackgroundJob.AddExternalStep and BackgroundJob.Close.

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 a detailed description of the problem in the R/3system log.
MSG_NO_RELEASE_PRIVILEGE: The R/3 user with whom the calling programhas logged onto the R/3 System does not have authorization to releasejobs. Jobs cannot be started until they are released.
MSG_CANT_LOG: The method call was terminated due to an error in the R/3XMI logging system.
MSG_EXT_USER_MISSING: The name of the external user was not specifiedin the call. This name specifies the user who triggered the method callin the external system.
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