Fonction SAP BP_JOB_DELETE - Delete Background Request

Paramètre Reférence Type Long. Valeur par déf. Facultatif Description
COMMITMODE BOOLE-BOOLE C 1 'X' X
FORCEDMODE SYST-BATCH C 1 SPACE X Continue deletion in spite of certain errors
JOBCOUNT TBTCJOB-JOBCOUNT C 8 ID number of the job
JOBNAME TBTCJOB-JOBNAME C 32 Job Name

Exception Description
CANT_DELETE_EVENT_ENTRY Event Scheduling Cannot be Deleted
CANT_DELETE_JOB Job Cannot be Deleted
CANT_DELETE_JOBLOG Job Log Cannot be Deleted
CANT_DELETE_STEPS Job Steps Cannot be Deleted
CANT_DELETE_TIME_ENTRY Deadline Scheduling Cannot be Deleted
CANT_DERELEASE_SUCCESSOR Previous Job Cannot be Modified
CANT_ENQ_PREDECESSOR Succeeding Job Cannot be Locked
CANT_ENQ_SUCCESSOR Previous Job Cannot be Locked
CANT_ENQ_TBTCO_ENTRY Job Cannot be Locked
CANT_UPDATE_PREDECESSOR Previous Job Cannot be Modified
CANT_UPDATE_SUCCESSOR Succeeding Job Cannot be Modified
COMMIT_FAILED COMMIT WORK Failed
JOBCOUNT_MISSING Job ID number was not specified
JOBNAME_MISSING Job Name Not Specified
JOB_DOES_NOT_EXIST Job Does Not Exist
JOB_IS_ALREADY_RUNNING Job Already Active
NO_DELETE_AUTHORITY No Authorization to Delete Jobs


INCLUDE BC_BP_JOB_DELETE OBJECT DOKU ID TX

Description
Select this parameter if all errors that occur when deleting tableentries or job logs are to be ignored.
The most important task of this parameter is to instruct the backgroundprocessing system to continue deleting a job, even if the job logcannot be deleted. The job log is stored in the TEMSE database. TheTEMSE is a component of the SAP system, which is not part of thebackground processing system.
No serious data inconsistencies occur, even if a job is deleted withouta log with FORCEDMODE. The TEMSE database has functions forconsistency checking itself, which can be used to clean up orphaneddata.
INCLUDE 'BP_JOBLOG_READ JOBCOUNT' OBJECT DOKU ID FU
INCLUDE 'BP_JOBLOG_READ JOBNAME' OBJECT DOKU ID FU

1163037P18:DTP:BATCH: Unnecessary BP_JOB_DELETE in batch manager
942801Inefficient SELECTs in background processing