Skip to Content
avatar image
Former Member

Contract stuck at status I1015 - Awaiting Approval.

Hi Guru's

I have got a problem suddenly.

In our production system Contract are all of a sudden hanging with status I1015          Awaiting Approval. Works fine in QA system!

Stats:

Status         Description

HEADER I1015          Awaiting Approval

HEADER I1021          Created

HEADER I1038          Complete

HEADER I1180          Document Completed

0000000001 I1143          Item is Active

0000000002 I1143          Item is Active

The contract do not have any approval workflow based on the standard process evaluation

Process Schema Evaluation with Evaluation ID   3EV_CT_600_000

Process Schema Definition BUS2000113       3C_CT_600_000

Object Type     BUS2000113

Process Schema  3C_CT_600_000

Sequence Number 999

Process Level Configuration

Level Type      S  Automatic (System User)

Evaluation ID

  1. Resp. Resolver Name
  2. Resp. Resolver Parameter

Task ID 40007988   Automatic Approval

Decision Type   1 Decision for Entire Document

Any ideas to what could be wrong and how to push those hanging into action again?

Thanks in advance,

Tom

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jul 26, 2016 at 02:54 AM

    Hi,

    You have to check if there is any errors in the workflow log.
    To do this, got workitem id for this contract via bbp_pd,, and then come to trx swi1 and input the workitem id. Then choose the entry and click 'display workflow log' button. Then check the details for each step to see if there is any error.
    If there is no error for workflow, you may then check the document to see if there is any application error. If no error is identified, and issue only happened to this specific contract, you may consider manually approve it using trx swo1.

    BR,
    Ivy

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Ivy Li

      Hi Ivy,

      Thanks a lot for you help!

      Note 1466930 did the trick.

      Event Linkage was broken :-(

      Thanks again for all your support.

      BR,

      Tom