cancel
Showing results for 
Search instead for 
Did you mean: 

TS17900101 - No step object GUID is assigned to work item ID; ESS MSS UWL

Former Member
0 Kudos
219

Working on ESS MSS implementation using UWL to approve work items.

Approval task (TS17900101) is sending workitem to UWL, but when I click on it I get the message:

No step object GUID is assigned to the work item ID

I read a little bit on here and noticed that the mandatory bindings need to be set.

Post :

Talks about setting mandatory bindings:

FORM_SCENARIO

FORM_SCENARIO_VERSION

SUPPRESS_SAVE

FORM_SCENARIO_STAGE

But the post doesn't go into detail on what I need to connect these to. So far I have what is below.

Binding from the workflow looks like this:

'X' @0EQAssign Value@ @9TQGets data for...@ &BACK_BUTTON_VISIBLE&

&FORM_STANDARD& @0EQAssign Value@ @9TQGets data for...@ &FORM&

'APPROVEREQUEST' @0EQAssign Value@ @9TQGets data for...@ &FORM_SCENARIO_STAGE&

'X' @0EQAssign Value@ @9TQGets data for...@ &SAVE_DRAFT_BUTTON_VISIBLE&

'HRASRB' @0EQAssign Value@ @9TQGets data for...@ &PROCESSOR_ROLE&

&NOTIFY_VIA_MAIL& @0EQAssign Value@ @9TQGets data for...@ &NOTIFY_VIA_MAIL&

&BUSINESS_STATUS& @0EQAssign Value@ @9TQGets data for...@ &BUSINESS_STATUS&

'X' @0EQAssign Value@ @9TQGets data for...@ &FORM.SUPPRESS_SAVE&

'00000' @0EQAssign Value@ @9TQGets data for...@ &FORM.FORM_SCENARIO_VERSION&

Binding to to the workflow as follows:

&PROCSTATE& @9SQReceives data from...@ @0DQAssign Value@ &PROCSTATE&

&WORKITEM_ID& @9SQReceives data from...@ @0DQAssign Value@ &STEP_OBJECT.GUID&

Can I please have assistance setting up the binding for this step such that we can make that error stop?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

We have figured this one out.

We needed a User Exit.

Addition of user exit resolves the issue: CL_HRASR00_POBJ_WF_EXIT u2013 looked at ABAP and saw that it generates a workitem ID u2013 that probably populated the workitem id binding that I had set~ But wasnu2019t working yet because the exit was not in place.

former_member185167
Active Contributor
0 Kudos

Thank you for the follow-up.