<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>The error occurs when determining the subworkflow. There are two
subworkflows, one for account assignment approval (that's the one
you can set in the workflow variant customizing as you have
shown), and one for releasing the document for posting. It's the
latter that fails, and I think it is because you haven't quite
understood how this workflow framework works.<br>
</p>
<p>From your attachment we can see that you have defined a workflow
variant, but have you completed the other customizing (and master
data changes if required)?</p>
<p>The nodes that follow after "Assign Company Code to a Workflow
Variant for Parking Documents" are relevant for the release
workflow. So you have to define (at least) one Release Approval
Group, and (at least) one Release Approval Path, and then you have
to assign combinations of workflow variants, document types and
release approval groups to the release approval paths, and finally
you have to assign a release approval procedure (i.e. define the
amount limits for combinations of workflow variants and release
approval paths and the number of release levels required for
amounts up to those limits and assign a subworkflow for amount
release). It's the same view that is used for release for payment.</p>
<p>And then of course the release approval group you define must be
reflected in vendor/customer master data. I wouldn't recommend
using 'blank' as the group - sooner or later a business scenario
will come up where you need to have separate groups. You may for
instance want to distinguish between employee vendors, ordinary
vendors and customers - assuming you don't need the same strict
controls for employee vendor accounts.<br>
</p>
<p>It's rather intricate, but extremely flexible, and you can use
your own custom subworkflows - so from a user perspective they
don't even have to know it's a workflow (they could e.g. run a
report and have all the invoices presented there and perform their
approval). It is also quite well documented if you read the node
documentation and many fields have good field documentation (F1
help) as well.</p>
<p>Hint:<br>
Each combination of workflow variant and release approval path
(when assigning the procedure) should have an entry where 'amount
to' is filled with 9s to take care of the highest amounts, and
then you add entries for lower amounts if there is any
distinction.<br>
</p>
Have fun with the customizing :-)<br>
<p> There is a high initial effort, but once you figure it out and
have it up and running it is quite elegant :-)</p>
<p><br>
</p>
<div class="moz-cite-prefix">Den 17.10.2018 16:44, skreiv Florin
Wach (SI):<br>
</div>
<blockquote type="cite"
cite="mid:2E542654-27B6-45CB-A334-426D75E80DA8@systems-integration.net">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Hi Glenn,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">I‘d agree with you it‘s customizing.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">For FI doc type you need to flag something, that
you want a preliminary document release.</div>
<div dir="ltr">Because: Posting should not be possible while the
workflow runs.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">This is one thing.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">The other one is with OBWE and you seem to have
made a good guess so I didn‘t look more into the details.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Transaction ppome comes secondary so do not worry
at the moment </div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Florin </div>
<div dir="ltr"><br>
Am 17.10.2018 um 16:00 schrieb Glenn Allen <<a
href="mailto:glenn.a.allen@gmail.com" moz-do-not-send="true">glenn.a.allen@gmail.com</a>>:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Good morning WF experts,</div>
<div>I am a senior ABAP developer but new to WF. My current
client is getting this error monthly. After clicking
through the various messages, reading SAP help and doing
google searches for the issue I have added an entry in
OBWE as an experimental solution (which I'll be testing in
our sandbox).</div>
<div><br>
</div>
<div>I am attaching 2 word docs that have screen shots and
documentation for the issue (hopefully attachments work
here). Is anyone familiar with this error? Am I on the
right track? Any advice is greatly appreciated.</div>
<div> </div>
<div>Thank you,<br clear="all">
</div>
<div>
<div class="m_-6306044571124563866gmail_signature"
dir="ltr" data-smartmail="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>--</div>
<div>Glenn Allen<br>
Software Architect (specializing in SAP)<br>
Excelsior Solutions, LLC<br>
315-453-9132</div>
<div>@glenn_a_allen</div>
<div><a href="http://linkedin.com/in/glennallen"
target="_blank" moz-do-not-send="true">linkedin.com/in/glennallen</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><GL Wflow issue with outlook generating Error
message for any park and Post document.docx></div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><notes.docx></div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>SAP-WUG mailing list</span><br>
<span><a href="mailto:SAP-WUG@mit.edu" moz-do-not-send="true">SAP-WUG@mit.edu</a></span><br>
<span><a
href="http://mailman.mit.edu/mailman/listinfo/sap-wug"
moz-do-not-send="true">http://mailman.mit.edu/mailman/listinfo/sap-wug</a></span><br>
</div>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SAP-WUG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Kjetil Kilhavn</pre>
</body>
</html>