Migration Cockpit - Synchronize Staging Tables Activities running for a very long time

[shak9828]

Dear all,

We are using SAP S/4HANA 2022 (ON PREMISE). All notes for Migration Cockpit - Migrate Data Using Staging Tables have been implemented in DEV system and transported to QAS system (transaction CNV_NA_MC).

We have created a project in DEV system and transported to QAS system. We needed to add some fields to Migration Object, so we added in DEV system and transported to QAS system. After transporting, we are having 17 activities - Synchronize Staging Tables - that are running for a very long time and we cannot stop them.

How can we stop these Activities?

Thanks,
Best Regards,
Shak

[TamasFodor]

Hi,

We helped you to accept the answer, since there were no updates after a few days. You can unaccept it anytime if you have further questions.

Kind regards,

Tamas

SAP Community Topic Expert

[zsombordanka · Accepted solution]

Dear Shak,

The Migration Cockpit activities may get stuck when a user -- a dialog user or a system user (such as a step user) -- with insufficient authorization starts these activities.

You can use transaction SU53 to identify failed authorization checks while a given user initiates Migration Cockpit activities.

To prevent the Migration Cockpit activities from getting stuck, please do the following:

Roles and Authorizations

Assign the following roles to all users working in the Migration Cockpit app, regardless of whether they are already assigned to the SAP_ALL profile or to any custom roles or profiles.

SAP_CA_DMC_MC_USER

SAP_BR_CONFIG_EXPERT_DATA_MIG

The SAP_CA_DMC_MC_USER role grants users the authorization to start and run Migration Cockpit activities, including creating projects or deleting instances. The SAP_BR_CONFIG_EXPERT_DATA_MIG role allows users to open and browse the Migration Cockpit app, only.

Here's more information about that from our Help Portal:

• Roles and Authorizations

Step User

Create a default step user using transaction SJOBREPO_STEPUSER.

The Technical Job Repository (transaction SJOBREPO) should be active on your system.

If the Technical Job Repository is active on your system, the Migration Cockpit app uses it to schedule and run the application jobs. The Technical Job Repository requires a step user, also called a technical user, to properly work.

You can find more help on that in our Help Portal:

• Technical Job Repository

Creating and Maintaining a Stepuser

Once the step user and automatic job scheduling is set up properly, you may check whether there are any entries stuck in table /LTB/JOB_QUEUE, if yes you can clear them.

Kind regards,
Zsombor