Reserve functionality no longer working

[cheri_myers]

I have several workflows where the reserve functionality is no longer getting set when a user clicks on an item and exits out.

We have several workflows that use the DECISION object PROCESS method in a customer defined task. We have a Budget Transfer, Travel
Request and Travel Expense that use that object. This is also not working for Purchase Requisition Releases or Parked Vendor Invoice releases which use object methods for those objects.  I do have some work items working but ONLY those which have a webdynpro that we
created with a specific call to either SWK_WI_SELECT or SAP_WAPI_RESERVE_WORKITEM. These workflows are working fine.

This is not working for substitution or Work Center agent determination. It is also not working in UWL or Business Workplace.

We just did a major upgrade to EHP6, SAP Basis release 731 and SP-level 9 and my functional
teams did not test this specifically during upgrade testing but I know this has worked in the past. We didn't have to code for it, it was intuitive.

Any ideas?

Thanks,

Cheri

[I042439]

Hi Cheri

What is the release of your EA-HRGXX component?

Following are the two notes which are created for the similar issue of reserve....though the BASIS release is lower than yours, but no harm in checking if the correction instructions actually exists in your system or not.

- 1314767: Behaviour of Workitems launched from UWL

- 1331372: Locking of Workitems from the UWL

Regards,

Modak

[cheri_myers]

Modak,

Took at look at those notes today. They are both in our system.

EA-HRGXX is release 604 SP level 0067.

The 1331372 note looked promising but but we have the code and it looks like it is only called for HR Process Objects.  When bringing up the work item, the work item is reserved and then if you quit out of the screen with the adobe form it then unreserves. There was no effect or call for my PVI's or Travel.

Karri: I am a step closer to your suggested message to SAP. Thanks for the timely response and thought.

Thanks,

Cheri

[I042439]

Hi Cheri

then it's Karri's way....write to SAP, do mention about the existence of the above two notes in your system to avoid intial back and forth 🙂

Regards,

Modak

[Former Member]

You should create a message for SAP about this. Sounds like something has gone broken in the standard code in the upgrade (assuming that there is no custom code (programming exit, etc.) done that might have an effect for the standard functionality). There might also be an OSS note for this, but at least I was not able to find anything relevant.

Regards,

Karri