<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.E-MailFormatvorlage17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.E-MailFormatvorlage18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:468671381;
mso-list-type:hybrid;
mso-list-template-ids:1220722958 -457017470 67567619 67567621 67567617 67567619 67567621 67567617 67567619 67567621;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=DE link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Hello Miguel,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>you can combine the
workflows into one, when you let the same workflow pattern start on each event
ob<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>BUS2081.BlockedPrice<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>BUS2081.BlockedQuant<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>In the
BlockedQuant-part you create a check function module that checks for existence
of a price block in at least one line item. If so, the check-function module
prohibits the event to become (just another) workflow instance. This way you
avoid having two instances when there’re both blocks set.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>I would not recommend
to prevent the IDoc inbound posting for various reasons:<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
lang=EN-US style='color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US style='color:#1F497D'>The
partner had send a (correct) invoice. The company’s system needs to be
made aware of that invoice in a fair time. If the workflow would get stuck for
some reaons (e.g. employees absence), the invoice cannot be paid, although the material
was posted to the purchase order meanwhile. This will bring you into trouble on
various workflow steps<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
lang=EN-US style='color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US style='color:#1F497D'>You have
to create your own dialog representation in order to display the invoice, and
what it is all about. This is exactly where you’re currently at, and you
had to create a full dynpro from scratch, including all the necessary extractions
from the IDoc segments<o:p></o:p></span></p>
<p class=MsoListParagraph style='text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if !supportLists]><span
lang=EN-US style='color:#1F497D'><span style='mso-list:Ignore'>-<span
style='font:7.0pt "Times New Roman"'>
</span></span></span><![endif]><span lang=EN-US style='color:#1F497D'>There
/is/ a standard process for BlockedQuant already in place (the system already
provides the appropriate event), so you should try to stick on this scenario,
as long as possible<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>There’s also
the possibility that you use the BUS2081.Created event, instead of the two
other blocking events, if you feel like that you need more to be checked than
just the blocks.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'>Best wishes,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'> Florin<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <b>On Behalf Of </b>Viera, Miguel<br>
<b>Sent:</b> Monday, April 12, 2010 2:38 PM<br>
<b>To:</b> 'sap-wug@mit.edu'<br>
<b>Subject:</b> Question regarding Price Block and Quantity Block Workflows for
incoming EDI invoices<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Hello Wugger’s ,<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Was wondering if anyone in the Workflow
User Group has experience with EDI and Price Block/Quantity Block
Workflows? We currently have incoming EDI invoices into our ECC 6.0 SAP
system that trigger Price Block Workflows during a pricing discrepancy and
Quantity Block Workflows for quantity discrepancies. The invoice is
posted in our system which generates a document number; however, it is blocked
for payment due to the respective discrepancy. Each workflow routes the
invoice to the appropriate personnel in Supply Management to determine the
outcome of the invoice.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>The problem we are having is that when an
EDI invoice comes in with both a price discrepancy and quantity discrepancy,
two workflows are generated which has proven to be a problem for the A/P
Department due to the timing of when and if the block on the invoice should be
released or perhaps the invoice needs to be cancelled. <o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>The best thing I can think of is to block
invoices with quantity discrepancies from being posted in the system through a
error status of 51 in WE05 and route them via workflow for resolution.
The challenge with this option is that IDOC information is not very friendly to
put in a query for user review and resolution.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><span lang=EN-US>Any help or insight would be greatly
appreciated.<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
<p class=MsoNormal><b><span lang=EN-US style='font-size:14.0pt;color:black'>Miguel
R. Viera<o:p></o:p></span></b></p>
<p class=MsoNormal><span lang=EN-US style='color:black'>Deere-Hitachi C.M.C<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'>SAP Business Analyst
for FI-CO & SD Modules<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'>Workflow Admin. &
Winshuttle Template Designer<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'>Phone: (336) 992-5759<o:p></o:p></span></p>
<p class=MsoNormal><span lang=EN-US style='color:black'><o:p> </o:p></span></p>
<p class=MsoNormal><b><i><span lang=EN-US style='color:#17365D'>"Let us
realize that the privilege to work is a gift, that power to work is a blessing,
that love of work is success." David O. McKay<o:p></o:p></span></i></b></p>
<p class=MsoNormal><span lang=EN-US><o:p> </o:p></span></p>
</div>
</body>
</html>