Purchase Order Header Release

[Marc Correia]

Hi all

I made a typo, I meant purchase requisition header release. 

In OMGQ the release code is set to 1 and the agent assignment is US. 

Richard, where do I set the communication info-type?

Thanks
Marc.



-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Richard Marut
Sent: Thursday, 3 March 2005 6:12 p.m.
To: 'SAP Workflow Users' Group'
Subject: RE: Purchase Order Header Release

Marc,

I have just a few questions that I use as a check list with PO agent
assignments.

Can you tell us a little more about your agent assignment?

Did you configure workflow for release codes with value 1 or 9 and what
organization object is being identified?

At the position level, do you have a holder relationship for a user
and/or
person? If person, do you have the communication info-type set up with a
user relationship?

Richard...

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of
Marc Correia
Sent: Wednesday, March 02, 2005 8:35 PM
To: SAP Workflow Users' Group
Subject: Purchase Order Header Release

Hi all

I am trying to release purchase orders at the header level. (Version
4.6C). 
The release strategy is set for a two stage release. The workflow fails
at the first step with the following error message.
Agents of type A cannot be determined. 

If I test the business object BUS2105 it launches into transaction ME54
no problem. That means somehow when you create the requisition and the
parameters are determined at runtime something is going wrong. I have
checked OSS and could find nothing. Anyone got any ideas, perhaps
something to check in config?

Thanks in advance
Marc.
 
 
 
Marc Correia
Manager
CGNZ Ltd
Ph +64 29 289 9008
Fax +64 9 358 1018
 
CGNZ DISCLAIMER: This email and any attachments are confidential and
intended exclusively for the person to whom the email is addressed. If
you
are not the intended recipient, do not read, copy, disclose or use the
contents in any way. Please notify us immediately by return email and
destroy the email and attachments. CGNZ does not accept any liability
for
any changes made to this email or attachments after sending by CGNZ. You
must scan this email and attachments for viruses. The opinions expressed
are
not necessarily those of CGNZ. 
 
CGNZ accepts no liability for any loss, damage or consequence, whether
caused by our own negligence or not, resulting directly or indirectly
from
the use of this email and attachments.

 
--------------------------------------------------------

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug