Inbox substitution interrogation

[Ehrhorn Morten]

Hej,-

 

While we are on the topic of WAPI's and substitution, I thought you
might be interested in a little bug we found last month.

 

SAP_WAPI_GET_WI_AGENTS with the "with_substitutes" flag set will return
all agents + substitutes of a work item, however if you use substitution
profiles and the task was classified AFTER the work item was created
these substitutes will not be included. The is due to a small
programming error in the WAPI where it checks on SWWIHEAD-TCLASS instead
of looking directly at the task classification. Going via the inbox this
check is not performed, leading to a difference in the set of
substitutes in those rare cases (well it was enough to have me puzzled
for a while).

 

SAP released note 1225877 to fix this small issue.

 

Regards,

morten

 

 

Med venlig hilsen/Best Regards

Morten Ehrhorn

Spring Consulting

mobil: +45 2924 5743

mail: morten.ehrhorn at springconsulting.com

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Tuesday, July 15, 2008 6:30 AM
To: SAP Workflow Users' Group
Subject: RE: Inbox substitution interrogation

 

Look at the SAP_WAPI  function modules - there's a bunch on working with
substitutes 

E.g. SAP_WAPI_SUBSTITUES_GET, SAP_WAPI_SUBSTITUTIONS_GET which would
give you the answers to both those questions

and they are all date delimited 

 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com <http://www.sap.com/>  

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 

Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.

Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of James J Seiter
Sent: Saturday, 12 July 2008 4:19 AM
To: sap-wug at mit.edu
Subject: Inbox substitution interrogation


ECC6 

Looking for a method of interrogating what Inbox substitutions have been
made to a userid, both forwards and backwards. 
1) Which users has USERA designated as substitutes.  USERA designated
USERB and USERC. 
2) Which users have designated USERA as a substitute.  USERX and USERZ
designated USERA. 

Aware of table HRUS_D2, but looking for a transaction / report to avoid
customization. 
FM RH_SUBSTITUTES_LIST is only forward looking...USERA designated USERB
and USERC. 

Need method of determining what users have designated USERA as
substitute...USERX and USERZ designated USERA. 

Thank you for your assistance, 
James

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080717/e121bcf9/attachment.htm