Message type: E = Error
Message class: BD - cross-application: data transfer
Message number: 075
Message text: This job must not be scheduled as periodic
You wanted to schedule the job as a periodic job. But this is not
permitted for the job.
The job was not scheduled.
You must flag the job as 'periodic allowed' in the job definition. Whey
you restart, you must never specify a period.
Error message extract from SAP system. Copyright SAP SE.
BD075
- This job must not be scheduled as periodic ?The SAP error message BD075, which states "This job must not be scheduled as periodic," typically occurs when you attempt to schedule a background job that is not allowed to run periodically. This is often related to jobs that are intended to be executed only once or at specific intervals rather than on a recurring basis.
Cause: Job Type: The job you are trying to schedule is designed to run only once or is not intended to be executed periodically. This could be due to the nature of the job, such as data transfers or specific reports that should not be run repeatedly. Job Configuration: The job might have been configured in a way that it does not support periodic execution. This could be due to settings in the job definition or the underlying program logic. System Restrictions: Certain jobs in SAP are restricted from being scheduled as periodic jobs due to system constraints
Get instant SAP help. Sign up for our Free Essentials Plan.
BD074
Dialog canceled
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
BD073
No authorization for locking/unlocking
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
BD076
&: This job was started periodically or directly from SM36/SM37
What causes this issue? You have started a program in the background, but not with transaction BMV0 (direct input management), or you have scheduled ...
BD077
There is a job & that has not yet ended
What causes this issue? You wanted to start a job (periodically). However, it has a predecessor with the same name (&V1&), which has not yet ...
Click on this link to search all SAP messages.