cancel
Showing results for 
Search instead for 
Did you mean: 

Work flow started but not completed .

0 Kudos

We have an issue regarding the employee separation Work Flow process. Work flow is started but not completed ( Not moving further steps ) . All the work flows are stopped at Update Step (Which is update the back end data), i.e. middle of the process and the status In Process . It is not throwing any error and the data also updating at back end. we have debugged that step and method logic is fine . If we trying to complete that Update step work item ,it is also completed without errors.

Can you please suggest us how to resolve this issue .

Any help really appreciable ..!!

Graphical screen shot where it has struck.

Accepted Solutions (0)

Answers (13)

Answers (13)

0 Kudos

Hi Sandy ,

We have tested FM with vtask = "B'. Still issue is not resolved .

When we run the RH_CUT_INFTY_1001_EXT function module for the Position to employee id (Rel-008, rsign-A) data for the delimition . It is working fine . When run the Employee Id(Penrnr) to position (Rel-008, rsign-B) , it is not working . Please find the below screen shot . And there is no dump in ST22 . Please suggest us.

SandySingh
Active Contributor
0 Kudos

Hi Ravi,

Looks like this more a HR data issue and not a WF issue. May be you are delimiting the record incorrectly. Check if you can do this via Transaction PO13.

http://scn.sap.com/message/7188853#7188853

Regards

Sandy

0 Kudos

Hi All ,

Thanks Vijay...!!

I thoroughly debugged method, I found one issue. While delimiting the position i am using this FM RH_CUT_INFTY_1001_EXT . It is not working properly when i run Work Flow through the Portal . But if i run this FM at back end and passing the same data, it is working fine. It is not throwing any errors also (in ST22). I deeply checked within that function module it is mainly got stuck (Not working) at FM  INTEGRATION_AFTER_UPDATE .

Can you please suggest me ? What i need to analyze .

Please find the below screen shots for your reference .

Data passing to the FM.

Mainly i got the error .

SandySingh
Active Contributor
0 Kudos

Looks like the PD update mode "vtask" is not correct. Try calling the FM with vtask = B as shown below. B stands for PD Update in Buffer.

CALL FUNCTION 'RH_CUT_INFTY_1001_EXT'

       EXPORTING

         vtask                   = 'B'

         gdate                   = cut_date

         histo                   = ' '

       TABLES

         innnn                   = relations_cut

       EXCEPTIONS

         error_during_cut        = 1

         no_authorization        = 2

         gdate_before_begda      = 3

         cut_of_timco_one        = 4

         relation_not_reversible = 5

         corr_exit               = 6

         OTHERS                  = 6.

Regards

Sandy

0 Kudos

Hi Madak ,

Thankss..!!

Please find the below screen shot . There is no error status in Step History tab.

and we have also checked the SMQA T.code . No issues.

SandySingh
Active Contributor
0 Kudos

Check if there is a WAIT statement in the code.

Could you please share the code written in this background step. Looks like there are errors updating the Separation infotype. Are you updating a HR infotype? HR infotype update via WF is bit complex.Have you checked ST22 logs.

Regards

Sandy

I042439
Employee
Employee
0 Kudos

what about the step history of the step which is in process?

Former Member
0 Kudos

Hi Ravi,

For testing, create new dialog method with the same code used in Update method and insert to workflow and set the agent as workflow initiator.

Now once the workflow is initiated and approved, the update work item will come to your SAP inbox.

Once the work item received, put the break point in the method and debug the method.

You might get some clues about the issue.

Thanks,

Vijay.

SandySingh
Active Contributor
0 Kudos

ccheck the logs in Transaction SM12 SM21 ..

check transaction SWPC.

You can also check in tx SWU2 if there aren't any local rfc's stuck in there

You could check the application log to see if there are any errors when the workitems got stuck.



regards

sandy

former_member185167
Active Contributor
0 Kudos

Maybe the records to be updated are locked and it's waiting for them to be unlocked.

former_member186746
Active Contributor
0 Kudos

Hi,

Also check in sm50 if maybe the log is correct and the process is still running (maybe infinite loop or something).

Kind regards, Rob Dielemans

I042439
Employee
Employee
0 Kudos

if these have only green lights - also check SMQA for any RFC errors.

I042439
Employee
Employee
0 Kudos

Hi Ravi


Can you please give the screen shots of:

1) Technical WF Log -> Select the main WF step (top one) and then click step history tab in lower half of the screen

2) Then Select the last step which shows "In Process" and provide the step history tab screen shot

Regards,

Modak

0 Kudos

Hi Anjan ,

Thanks..!

It is back end data update step .Hence there is no deadline maintained .

anjan_paul
Active Contributor
0 Kudos

Hi,

  also check the is there any Deadline maintain for Requested Start

Also check is the TASK is asynchronous and it is    needed any Terminatin Events to completes

0 Kudos

Hi Vijay ,

Thanks for your reply .

WF-BATCH user has necessary authorization . And we have checked the SWUD and Work item log there is no error (No dump in ST22 ).

@ Hi Karri ,

Thanks for your quick response.

There is no error and warnings it is throwing .

Please suggest further to find out the issue .

Thanks ,

Ravi

Former Member
0 Kudos

Check that WF-BATCH user has not been locked.

Open SWU3 and check if the RFC part is green.

Start the verification WF from SWU3. Does it work? (If there are other workflows in use in your system, and you know that they work without problems, then you don't need to do this.)

Kind regards,

Karri

Former Member
0 Kudos

Sounds like there has been a short dump. See ST22.

Also, take a look to the technical workflow log. You might find an error/warning messages that will help you to solve the problem.

Regards,

Karri

Former Member
0 Kudos

Hi Ravi,

Is this issue happening in production ?

Check for any dumps in transaction ST22.

Check for the authorization of user WF-BATCH & analyze the work item using transaction SWUD.

Thanks,

Vijay.