VARIANTS and BATCHJOBS Packages Import Errors

Symptom

  1. A warning message shows up when trying to select the VARIANTS and BATCHJOBS packages in the same configuration as other packages.

Figure 1: Warning Message - Adding VARIANTS or BATCHJOB in the Same Configuration as s Other Packages

  1. A warning message appears prompting you to import the VARIANTS and BATCHJOBS packages at the start of the FLUX™ post–System Refresh export/import process.

Figure 2a: Warning Message - Importing VARIANTS and/or BATCHJOB packages at the beginning of a System Refresh
Figure 2b: Warning Message - Importing VARIANTS and/or BATCHJOB packages at the beginning of a System Refresh

  1. A warning message appears when trying to re-import the VARIANTS and BATCHJOBS packages at the start of the FLUX™ post–System Refresh import process.

Figure 3: Warning Message - Reimporting VARIANTS and/or BATCHJOB packages

  1. Deadlock errors may be recorded in the VARIANTS or BATCHJOBS import log during the FLUX™ import process. Import jobs may fail, or ABAP short dumps can occur.

Figure 4: Deadlock Error

Environment

All SAP environments

Cause

  • The VARIANTS and BATCHJOBS packages must be imported first after a System Refresh to prevent their history from being overwritten.

  • These packages are automatically executed in dialogue mode by FLUX™, which can lead to timeouts if the system parameter rdisp/scheduler/prio_[high normal low]/max_runtime is too low.

  • FLUX™ executes VARIANTS and BATCHJOBS in dialogue mode, which increases the risk of conflicts if other jobs are active.

Resolution

  1. Import Order

    1. Always include VARIANTS and BATCHJOBS in the same configuration and import them first in the post–System Refresh FLUX™ import process.

    2. If FLUX™ displays a warning message, select “Continue” only if you are importing these packages as the first step.

    3. If you are attempting to import them later in the process, select Cancel and reschedule the import so it runs first. Importing them out of sequence may overwrite their history.

  2. System Parameters

    1. Increase the following SAP system profile parameters (and check their dependency on rdisp/wp_max_runtime) to avoid ABAP short dump timeouts.

      1. rdisp/scheduler/prio_high/max_runtime

      2. rdisp/scheduler/prio_normal/max_runtime

      3. rdisp/scheduler/prio_low/max_runtime

      4. rdisp/max_wprun_time

    2. Refer to SAP Notes

      1. 2129291 - Session Priority and Work Process Quota in SAP Kernels >= 7.4x - SAP for Me

      2. 3221120 - Dialog work process runs for longer than the "rdisp/scheduler/prio_high/max_runtime" defined period - SAP for Me

  3. Warning Message During VARIANTS and BATCHJOBS Re-Import

    1. When the warning message appears, carefully verify whether you intend to re-import the VARIANTS and BATCHJOBS packages.

      1. If you do intend to proceed (e.g., you are importing them at the start of the post–System Refresh process), click “Continue.”

      2. If you do not intend to re-import them, or if this was triggered by mistake, click “Cancel” to avoid unintended overwriting of package history.

  4. Suspend Background Jobs

    1. Before running the FLUX™ import, suspend all SAP background jobs by executing program BTCTRNS1. This helps prevent conflicts that can lead to deadlocks or short dumps during the import of VARIANTS and BATCHJOBS. Once post–System Refresh testing is complete, resume the background jobs by executing BTCTRNS2.

Previous‘Export/Import Jobs Still Running’ ErrorNextSID-Refresh

Last updated