Hello SAP Community! 

Picture this: you have spent time setting up your recurring Process Scheduler jobs, the nightly allocation run, the weekly consolidation, the monthly reporting cycle. Everything is humming along. Then you need a new environment, a copy for testing, or a fresh import to another tenant. You open the Process Scheduler in the new environment and it is empty. Every recurring Process Scheduler jobs gone, waiting to be rebuilt from scratch. 

If that scenario sounds familiar, this post is for you. 

SAP Profitability and Performance Management Cloud Standard Model now introduces full lifecycle management of recurring Process Scheduler jobs. Recurring Process Scheduler jobs travel with their environment, through copy, through export and import, and through deletion. The Process Scheduler is finally a first-class citizen of the environment lifecycle, and this post walks through exactly what that means for each operation. 

Why Does This Matter? 

Recurring Process Scheduler jobs represent deliberate decisions: which process to run, how often, on what schedule, for which environment. Those decisions belong to the environment configuration. When they were left behind during copy or import, two problems built up over time. 

The first was effort. Recreating jobs manually is manageable once. It becomes a slow, error-prone task when an organization rotates multiple environments regularly. 

The second was clutter. Deleting an environment left its associated recurring jobs behind, attached to nothing. Those orphaned jobs accumulated in the Process Scheduler with no parent environment, making it harder to tell what was still running and what was safe to clean up. 

This release solves both. Recurring Process Scheduler jobs now travel with the environment, and they are automatically removed when the environment is deleted. 

Before You Begin 

Before exploring each operation, the following apply across the board and are worth knowing upfront.  

• Recurring Process Scheduler jobs are automatically remapped to the target Environment ID and Version for both copy and import operations, so no manual adjustment is needed. 

• When an environment is copied, the functions referenced by Process Scheduler jobs are not automatically activated in the target environment. Activate them before allowing the first scheduled run. 

• Process instances from Process Management are not included in environment copy or import operations. Jobs configured with Based on: Existing Process Instance will not run successfully until the referenced process instance exists in the target environment. 

What Has Changed: The Four Operations 

Copy Environment: Optional Inclusion of Recurring Jobs 

When you copy an environment, the Copy Environment dialog now includes an opt-in control to include the recurring Process Scheduler jobs from the source environment in the copy. By default, the copy proceeds without jobs, preserving existing behavior and avoiding unintended scheduling in new environments. Selecting the option includes all recurring Process Scheduler jobs in the copy. 

The entire copy operation, including job transport, is tracked in the Application Monitor, giving you a clear record of what was copied and when. 

Export Environment: Job Data Included in the Content Package 

The environment export package has been enriched. When you export an environment from Menu > Administration > Content Management, recurring Process Scheduler jobs  are now included in the exported ZIP file alongside the environment model content. 

One key structural difference worth knowing upfront: this is handled automatically at export time. There is no separate toggle in the Export Environment dialog to include or exclude jobs. If recurring jobs exist in the environment, they are exported. The export package therefore reflects the full environment configuration, ready for import.

Import Environment: Optional Inclusion of Recurring Jobs

On the import side, the Import Environment dialog now includes an opt-in control to include the recurring Process Scheduler jobs from the content package into the target environment. 

This is a deliberate design choice. Unlike export, where jobs are always included if present, import gives you the choice. The scheduling context may differ between environments, and a job that runs nightly in one environment may not be appropriate to start immediately in another. The opt-in lets you decide at import time rather than discovering an unexpected running job afterward. 

Like copy, the full import operation including job configuration is tracked in the Application Monitor.

Environment Deletion: Automatic Cleanup of Orphaned Jobs

This is the quietest of the four operations, and arguably the most impactful for long-running tenants. When an environment is deleted or overwritten during an import, all recurring Process Scheduler jobs associated with that environment are automatically removed from the Process Scheduler. 

No manual cleanup is required. The recurring Process Scheduler jobs are identified by their association with the environment and removed as part of the deletion operation. 

Important: This cleanup is automatic and immediate. If you delete an environment that has recurring jobs you intended to preserve or transfer, export the environment first. Once the environment is deleted, its recurring Process Scheduler jobs cannot be recovered from the Process Scheduler. 

Wrapping Up 

Think about the scenarios where this makes a real difference. You copy a production environment to test a model change, and the full scheduling setup comes with it, ready to review before you switch anything on. You transport a configured environment to another tenant via export and import, and the recurring jobs arrive as part of the package rather than as a manual follow-up task. You retire an old environment and its jobs disappear with it automatically, leaving the Process Scheduler clean. 

That is the shift this release delivers: the Process Scheduler setup is now part of the environment, not something that lives separately and needs to be maintained by hand every time the environment moves. 

We are eager to hear how you are using the Process Scheduler across your environments. Which of these four operations will make the biggest difference in your day-to-day work? Share your thoughts in the comments below. 

As always, feel free to reach out via the SAP Profitability and Performance Management Community with questions.