SRM 5.0 - SC Line Item Approval - How to handle agent errors

[Griffiths, Mark]

Hi Mark,
 
I worked on this earlier in the year.  The administration table seems to
be ignored by the line item badi.  I think it is just there for the
header level badi.  I was advised by colleagues in Germany to set the
administrator for each line - this meant I had to add a fair amount of
extra code into the badi so that if a user wasn't found or valid I
returned an administrator - I then also assigned this to all the other
lines and GUIDs too for restart processing reasons.
 
Hope this helps,
 
Mark
 
SAP UK

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mark Pyc
Sent: 16 August 2006 17:57
To: WUG
Subject: SRM 5.0 - SC Line Item Approval - How to handle agent errors


G'day all,
 
More questions. 
 
Has anyone successfully used the APPROVAL_ADMINISTRATION table of the
approval BAdI in association with Line Item approval? (I'm not
interested in whether it works or not for Cart Level)
 
I expect that it should be possible to get items where an approver
hasn't be maintained to appear in the Applications Monitor section
Approval > Approver Assignment but nothing I've tried manages this.
 
If I just include the approval GUID in the APPROVAL_ADMINISTRATION table
and not in the normal APPROVAL_TABLE the items are ignored for approval
and are effectively auto-approved. Not what I want.
 
If I include the entries in both tables and either include no user-id
but do include a name, or include name or user-id then Workitems without
agents are created but again the Admin table seems to be ignored.
 
I could include Admin agents as the agents, but this would mean they
could approve/reject the items rather than just forward the Workitem. If
I don't give them access to BBPSC07 to prevent this then it is very
difficult for them to tell which line items are having problems. 
 
Another option which I've seen recommended which will work (Thanks Carol
Thomas / Natasha Baunach) is to check that all agents are available
before the cart is saved. This has the advantage that the requestor is
kept informed but requires them to pick up a phone and contact a help
desk - this manual intervention grates on me since it seems to fly in
the face of WF process automation. 
 
The standard SAP demos only reference the scenario where no agents at
all can be determined (not that I can that I can get that to work
either) but it's important to also handle the situation where maybe just
one line doesn't have an approver determined. 
 
Any inputs greatly appreciated.
 
Thanks,
Mark
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060818/bcbb02a8/attachment.htm