Skip to Content
author's profile photo Former Member
Former Member

Error - Variant &0000000000000 does not exist in Job Logs

Hi All,

We have job SWWDHEX running under two different Ids at exactly same time and similar varaint in SAP system:

Job CreatedB Status Start date Start time

SWWDHEX BASISBATCH Canceled 12/13/2011 13:32:07

SWWDHEX BASISBATCH Canceled 12/13/2011 13:35:07

SWWDHEX BASISBATCH Canceled 12/13/2011 13:38:07

SWWDHEX BASISBATCH Canceled 12/13/2011 13:41:07

SWWDHEX WF-BATCH Finished 12/13/2011 13:32:07

SWWDHEX WF-BATCH Finished 12/13/2011 13:35:07

SWWDHEX WF-BATCH Finished 12/13/2011 13:38:07

SWWDHEX WF-BATCH Finished 12/13/2011 13:41:07

As you see jobs running Jobs running successfully under User WF-BATCH.

But while BASISBATCH User jobs are failing with error:

u201CVariant &0000000000000 does not existu201D

I checked in jobs which are in released status for both user contains same varaint &0000000000000.

These jobs are running in different clients.

Please let me know reason of this job failure and also let me know is this job client dependent to make sure both runs are necessery for this job.

Regards,

Shivam Mittal

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 13, 2011 at 09:57 PM

    Hi Shivam,

    Why did you defined this job with two different users? Could you be created SWWDHEX job on the other client?

    Best regards,

    Orkun Gedik

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 13, 2011 at 11:29 PM

    Hello,

    As you see jobs running Jobs running successfully under User WF-BATCH.

    But while BASISBATCH User jobs are failing with error:

    u201CVariant &0000000000000 does not existu201D

    This might be related to the fact that it is executed at the same time.

    Is it possible to postpone the job in one client by one minute?

    Please let me know reason of this job failure and also let me know is this job client dependent to make sure both runs are necessery for this job.

    According to available SAP notes this job seems to be client dependent.

    Related SAP notes:

    Note 1262519 - Functions and monitoring of deadline monitoring

    Note 1059852 - Workflow background jobs are scheduled several times

    Tomas

    Add a comment
    10|10000 characters needed characters exceeded

    • Hello,

      another idea is following - how did you create the job in problematic client - did you used copy function? Or did you schedule it from correct maintenance transaction like the functional one.

      If it was copied then internal variant really might not exist.

      Tomas

  • author's profile photo Former Member
    Former Member
    Posted on Dec 14, 2011 at 02:14 AM

    Hello,

    This is 'workflow' job and is client dependent.

    Discuss with your functional team whether the job is needed in both the clients or not, normally it is needed only in 'production' client and sometimes in more than one too (for e.g. in multiple clients in QAS). For each client there should be a workflow RFC, check with sm59.

    If the workflow job is needed in the client where it is currently getting 'terminated', then rectify it using SWU3. Prerequisite is workflow RFC and this is taken care by SWU3 itself I think.

    Thanks

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.