workflow problem with status Ready

[Former Member]

HI,

I have a problem with the workflow not getting completed.

The workflow is for the employee attendace 20000081 .

After the manager of the employee accepts the leave application posted by employee , The workflow is in the following state: -

ID 000000340552 Work item type Background step

Work Item text Find Employee .

Status <b>Ready</b>

.

Now the question is there any background job which needs to be scheduled for changing the all the workitem with status 'Ready' to be executed .

since once I execute this step manually then the workflow again goes in the ready status with the next step and the next step in this case is 'Create attendance/absence' This stpe of the workflow is in again status 'Ready'.

Please let me know if some know about this problem.

Thanks in advance .

Ankur

[Former Member]

Hi Ankur,

Did you check if there is any starting date / time specified for these tasks?

In that case you need to check if deadline monitoring is scheduled or not ...check in Xn SWU3 ..

cheers,

Ram

[Former Member]

Hi ,

I have checked but there is no start date and time specified and i have scheduled the deadline job

The deadline data is as given below

Created Start End

Current 2005.06.27.

Requested 'blank'

Latest 'blank'

Please let me know if you have some other suggestion .

Thanks for the prompt help.

REgards,

Ankur

[sudhindra_chandrashekar]

If the Task you have created is a background processing step then it should execute automatically. If it is not then there is an issue with the customising. Go to transaction 'SWU3' and check for the check marks against all the items there or else just carry out a Automatic Customisation by hitting the Generate button.

Sudhi

[Former Member]

Hi ,

Thanks for the prompt reply.

I have tried the auto customizing and I am geeting the following log generated :

Auto-Customizing: General tasks

E WZ:119 Instances for task TS60001307 already exist

Task TS60001307 not classified as general task

E WZ:119 Instances for task TS70008037 already exist

Task TS70008037 not classified as general task

E WZ:119 Instances for task TS70008125 already exist

Task TS70008125 not classified as general task

And while checking the customizing setting in SWU3 the folling entires exists but as I understand the seeting is proper, please have alook below:

An active plan version exists

Workflow administrator maintained

RFC destination: User locked

Generic decision task classified completely

Tasks for document generation fully classified

T77* tables all available

Monitoring job for missed deadlines is scheduled

Monitoring job for work items with errors is scheduled

Sending to objects and HR objects activated

Entries missing in PD control tables

Default Domain for Internet Mail Maintained

Workflow development environment

Customizing incomplete

Prefix numbers for standard object types maintained

An active plan version exists

T77* tables all available

Number range defined for customer tasks

Entries missing in PD control tables

Please let me know if this is not proper .

Thanks and Regards,

Ankur

[Former Member]

Contact your BASIS Team ,...

USER WF-BATCH is locked ....why ??

Understand that all the Background WIs get executed by this user.

You might check if you can delete and re-create this user WF-BATCH from SWU3 itself.

But first check with Basis if this user can be un-locked.

Cheers,

Ram

Message was edited by: Ram Manohar Tiwari

[Former Member]

Hi ,

I have tried unlocking this user but still i get the password is incorrect and then I have tried changing the password for this user and then synchronize the password .

then it comes to the the 'Workflow RFC Destination configured completly '

but still I am not able to get the problem solved .

Do you have some other clue .

thanks and Regards,

Ankur

[Former Member]

Did you run the workflow again or looking at the last instance itself?

see the business workflow menu..

Also activate the workflow trace..and then run the workflow..

and then check the workflow trace.

Cheers,

Ram