<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1528" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>Hello Mark,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>You can do all sorts of clever stuff with the line item
badi workflow - the only bounds are your imagination ... and a large number
of oss notes of course, but given some patience you can get it to work pretty
nicely.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>On my last project I ended up finding all the required
approvers at a particular level by line. I then generated a set
of approvalguids which were generated on a combination of userid and
value. I then looped through and assigned the approvalguids to the
relevant lines. If a line had more than one approvalguid then the
necessary numbers of work items were generated and all assigned approvers could
approve or reject the line. The only minor restriction was that one
approver could override the decision of the previous approver but this can be
controlled by your process i.e. if you approve a previous rejection you will get
disciplined.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>So, yes, I think you can do what you want with the
approvalguids generation and assignment to lines. I can't get anyone to
pay for me to go to ASUG so a nice warm beer in London will
suffice.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>Give me a call if you need to discuss in any more
detail.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>Cheers,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>Mark</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=191192014-05042006><FONT face=Arial
color=#0000ff size=2>SAP UK</FONT></SPAN></DIV><BR>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Mark Pyc<BR><B>Sent:</B>
05 April 2006 12:41<BR><B>To:</B> WUG<BR><B>Subject:</B> SRM 4.0 Line Item SC
Completion<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>G'day all,</DIV>
<DIV> </DIV>
<DIV>I've made some progress from my last query in this area. I've now
convinced the customer that the SAP recommended way forward is for Early Buyer
Completion i.e. prior to the Approval WF commencing. </DIV>
<DIV> </DIV>
<DIV>We will be implementing the Line Item Approval process (and yes I've been
thoroughly warned about how many OSS notes will be needed). My query now is is
it possible to have 'Line Item Completion'. </DIV>
<DIV> </DIV>
<DIV>The situation will be that Buyers (agents for completion) will be
determined by material groups. Since there will be no restriction to prevent
it there will be cases where a cart will require completion by different
buyers by line item. I can find no reference in the help to suggest that this
is possible. Although I can send the Workitem for completion to multiple
buyers, it would still be only a single Workitem and a single buyer would need
to complete it in it's entirety. There can be an offline coordination between
the buyers, but I want to confirm if genuine line item completion is possible.
</DIV>
<DIV> </DIV>
<DIV>FYI - the plan is to force all text items through completion as well as
any non-contracted catalogue items (a mini tender type process will take place
at this point). Sourcing cock-pit will not be used. Classic will be used (not
extended Classic). </DIV>
<DIV> </DIV>
<DIV>Many thanks for any insights - although there is no points system here,
I'll happily reward with beer at the Spring ASUG conference.</DIV>
<DIV> </DIV>
<DIV>Have fun,</DIV>
<DIV>Mark<BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 3/7/06, <B class=gmail_sendername>Mark Pyc</B>
<<A href="mailto:mark.pyc@gmail.com">mark.pyc@gmail.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">G'day
Wuggers,<BR><BR>The general recommendation (and the only way I've seen
implemented) is<BR>to invoke the Buyer Completion WF for incomplete carts
prior to <BR>Financial Approval. My current client is contemplating
reversing this<BR>order so that Financial Approval will be confirmed before
the buying<BR>group will be involved in completeing the cart.<BR><BR>I
understand that this will bring in the potential for changes at a <BR>late
stage which will cause the cart to run back round the Financial<BR>Approval
loop.<BR><BR>Has anyone implemented such a scenario? What comments do you
offer?<BR><BR>I believe this desire has come as a result from the client
previous <BR>experience in EBP 3.5 whereby incomplete carts were approved
and then<BR>sent to the ECC/R3 backend as a requisition. Therefore
buyer<BR>completion took place in the form of conversion from PReq to PO.
In<BR>the new solution the intention is to perform buyer completion in SRM
<BR>so that all carts are transfered as PO's. So although they
are<BR>implementing a new process the desire is to keep the basic sequence
of<BR>Approval prior to Buyer Completion.<BR><BR>FYI - The intention is to
use Classic rather than Extended Classic. <BR><BR>Any
comments??<BR><BR>Somewhat less technically WF, has anyone implemented SRM
Purchasing<BR>which handles EU Article 32 compliance for Public Purchasing??
This<BR>directive requires a mini-tender process where framework orders
exist <BR>for the same Good or Service with multiple vendors. The
proposed<BR>solution here is simply to invoke the Buyer Completion WF even
though<BR>the cart will be technically complete.<BR><BR>Again, any comments
warmly welcomed. <BR><BR>Have
fun,<BR>Mark<BR></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>