3718752 - Technical ID Automatically Populated in "Run After Job" When Rescheduling Resource Calendar Availability Background Job

Upon selecting "Reschedule" for the background job Resource Calendar Availability Calculation, a Technical ID is automatically displayed in the "Run After Job" field.

SAP Business ByDesign

1. Go to Application and User Management Work Center.
2. Go to Background Jobs View.
3. Select All Scheduled Jobs
4. Select the "Resource Calendar Availability Calculation" job that needs to be rescheduled and Choose "Reschedule"
5. In Run After Job field, a technical ID is automatically displayed
   For example: AA99AA9999AA99AA999A999A9A999AA
                       
                       

When the Reschedule option is selected, the "Run After Job" field is automatically populated with the background job schedule ID (e.g.,AA99AA9999AA99AA999A999A9A999AA). If no value is entered in the UI, the system automatically determines the predecessor job ID and binds it to the "Run After Job" UI field.

Possible reasons why the system auto‑populates the "Run After Job" field:

• Sequential Execution Enforcement:
  SAP Business ByDesign does not allow parallel execution of the same Mass Data Run (MDR) to prevent database locking or inconsistent results. If a previous Mass Data Run is still in Scheduled or Waiting status, the system enforces a sequence by adding a predecessor ID.
  
  
• Change Notification Requests (CNR) Based System Triggers:
  The "Resource Calendar Availability Calculation" job can be triggered by Change Notification Requests (e.g., changes in project tasks, resource calendars, or work schedules). If any such trigger is pending, the system automatically links your new Mass Data Run to the existing chain.
  
  
• Process Integrity:
  The Reschedule function is designed to maintain an execution sequence. If a logical predecessor exists at the time of rescheduling, the system ensures chronological processing by inserting the associated ID.
  
  
• Avoiding Overlapping Runs:
  Since the availability calculation is resource-intensive, the auto-populated ID helps avoid concurrent executions and ensures system stability.

This behavior is due to Standard SAP Business ByDesign job handling logic, which enforces sequential execution to prevent database locking or inconsistent results.

As a workaround, if you wish to run the job independently:

1. Manually clear the Preceding Schedule ID in "Run After Job" field.
2. Set the trigger to Start Immediately.
3. If the system continues to populate the ID, review the Background Jobs view and cancel any prior Scheduled or Waiting instances of the relevant AVAIL_CALC Mass Data Run.

Resource Calendar Availability Calculation, AVAIL_CALC, Mass Data Run, Run After Job, Background Jobs, Reschedule, Random ID. , KBA , AP-LM-AM-BGJ , UIs for Background Jobs , Problem