Scribd
Upload
447 views4 pages

Transaction Canceled DB 612 Error For Workflow Jobs in SM21

The document describes an issue where workflow jobs are failing in SM37 with a 'Variant '&00000000000XX' does not exist error' after a client copy. The cause is that job definitions are not copied during a client copy. The resolution is to delete and reschedule the affected workflow jobs.

Uploaded by

zzkulvant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
447 views4 pages

Transaction Canceled DB 612 Error For Workflow Jobs in SM21

The document describes an issue where workflow jobs are failing in SM37 with a 'Variant '&00000000000XX' does not exist error' after a client copy. The cause is that job definitions are not copied during a client copy. The resolution is to delete and reschedule the affected workflow jobs.

Uploaded by

zzkulvant
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP Knowledge Base Article

2333686 - Transaction Canceled DB 612 error for workflow jobs in SM21


Component: BC-BMT-WFM (Business Workflow), Version: 8, Released On: 26.07.2022

Symptom
Workflow jobs SWWDHEX, SWWCOND, SWWERRE, SWWCLEAR, SWWWIM are failed in SM37 transaction due to Variant '&00000000000XX' does not exist error. There are
the following logs in SM21 transaction:

Transaction Canceled DB 612 (#0000000000000 RSWWDHEX)


Transaction Canceled DB 612 (#0000000000000 RSWWERRE)
Transaction Canceled DB 612 (#0000000000000 RSWWCOND)
Transaction Canceled DB 612 (#0000000000000 RSWWCLEAR)
Transaction Canceled DB 612 (#0000000000000 RSWWWIM)

Environment
SAP Business Workflow
SAP NetWeaver
SAP Web Application Server for SAP S/4 HANA

Reproducing the Issue


1. Execute client copy from client A to client B.
2. Call transaction SM37 and check workflow jobs: SWWDHEX, SWWERRE, SWWCOND, SWWCLEAR, SWWWIM in client B.

Cause
Before client copy from client A to client B:

In client A, variant '&0000000000000' doesn't exist.


In client B, workflow job is already running with variant '&0000000000000'.

After client copy:

As job definitions are not copied during client copy(see Q6 in SAP Note 31503), the running workflow job in client B still try to find the variant '&0000000000000'.
But variant '&0000000000000' no longer exist in client B due to the variant tables in client B are overwritten by tables in client A.

Resolution
Delete and reschedule workflow jobs according to the following steps:

1. Delete SWWDHEX, SWWCOND, SWWERRE, SWWCLEAR and RSWWWIM jobs in "Released" status in SM37.

2. Go to SWU3 and expand node "Maintain Runtime Environment":

3. Select "Schedule Background Job for Workflow Deadline Monitoring" and click "automatic customizing" for rescheduling SWWDHEX job:
4. Select "Schedule Background Job for Work Items with Errors" and click "automatic customizing" for rescheduling SWWERRE job:

5. Select "Schedule Background Job for Condition Evaluation" and click "automatic customizing" for rescheduling SWWCOND job:

6. Select "Schedule Background Job for clearing report" and click "automatic customizing" for rescheduling SWWCLEAR job:
7. After reschedule these workflow jobs, the relevant nodes in SWU3 will change to green status as below:

8. Run report RSWWWIM_INSERT in transaction SE38 for rescheduling SWWWIM job.

Also note that "Configure RFC Destination" in SWU3 has to be in green light status if workflow business is used in your system.

If users have special requirement (for example: client copy happens frequently) and do not want to reschedule the job every time after the client copy, may consider the following
options:

1. Make sure the original client and target client are using the same variant ID for the same workfow job.

2. Do no copy/overwrite the existing variants to the target client.

3. Utilize the report introduced by SAP Note 2700589 to copy job definitions after the client copy.

See Also
SAP Note 31503 - FAQ: Background jobs
SAP Note 2700589 - Copying background jobs to another system
KBA 2531135 - SWWRUNCNT fails with error "Variant &0000000000000 does not exist"

Keywords
WF_GDPR, SWF_WORKFLOW, WFMSTD, variant does not exist, &0000000000001, &0000000000002, &0000000000003, &0000000000004, SWU3, client copy, Automatic
Workflow Customizing, Schedule Background Job for Workflow Deadline Monitoring, Schedule Background Job for Work Items with Errors, Schedule Background Job for Condition
Evaluation.

Attributes

Key Value

Other Components BC-CCM-BTC (Background Processing)

Products

Products

SAP NetWeaver all versions

SAP Web Application Server for SAP S/4HANA all versions


This document refers to

SAP Note/KBA Title

2531135 SWWRUNCNT fails with error "Variant &0000000000000 does not exist"

31503 FAQ about: Background jobs

2700589 Copying background jobs to another system

This document is referenced by

SAP Note/KBA Title

3137613 Error "Variant SAP&SCHEDULER does not exist" raised in the job log of SAP_WORKFLOW_SYSTEM

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy