Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix BT180 - Job is event-periodic. Period values cannot be specified


SAP Error Message - Details

  • Message type: E = Error

  • Message class: BT - Background processing messages

  • Message number: 180

  • Message text: Job is event-periodic. Period values cannot be specified

  • Show details Hide details
  • What causes this issue?

    You have specified that this job is to be started when a particular
    event is triggered and that the job should be repeated whenever the
    event recurs. You have also tried to enter a time interval for
    restarting the job.
    Since the job is to be repeated when an event occurs, you cannot enter
    a time interval for repeating the job.

    System Response

    No action taken.

    How to fix this error?

    Select <LS>Immediate start</><ZV>Sofort</> or <LS>Date/time</><ZV>
    Datum/Uhrzeit</> as the start specification for this job if it must be
    repeated according to a time interval.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message BT180 - Job is event-periodic. Period values cannot be specified ?

    The SAP error message BT180, which states "Job is event-periodic. Period values cannot be specified," typically occurs when you are trying to schedule a background job that is defined as event-driven (event-periodic) but also attempting to specify periodic values (like start times or intervals) that are not compatible with event-driven jobs.

    Cause:

    1. Job Type: The job you are trying to schedule is defined as an event-driven job. Event-driven jobs are triggered by specific events rather than running at regular intervals.
    2. Conflicting Parameters: When you attempt to set periodic parameters (like daily, weekly, etc.) for a job that is already defined to be triggered by events, SAP does not allow this configuration, leading to the error.

    Solution:

    To resolve this error, you need to ensure that you are not mixing job types. Here are the steps you can take:

    1. Check Job Definition: Review the job definition in transaction code SM37 or SM36 to confirm that it is set as an event-driven job.
    2. Remove Periodic Values: If you want to keep the job as event-driven, do not specify any periodic values. Instead, ensure that the job is only set to trigger based on the defined events.
    3. Change Job Type: If you intended for the job to run periodically, you may need to redefine the job as a periodic job instead of an event-driven job. You can do this by:
      • Deleting the existing event-driven job.
      • Creating a new job with the desired periodic settings.

    Related Information:

    • Event-Driven Jobs: These jobs are typically used for processes that need to be executed in response to specific events, such as the completion of another job or the arrival of data.
    • Periodic Jobs: These jobs are scheduled to run at regular intervals (e.g., daily, weekly) and are defined with specific start times and frequency.
    • Transaction Codes:
      • SM36: To create or modify background jobs.
      • SM37: To monitor and manage background jobs.
    • Documentation: Refer to SAP Help documentation for more details on job scheduling and the differences between event-driven and periodic jobs.

    By following these steps, you should be able to resolve the BT180 error and successfully schedule your background job as intended.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant