<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2>I am not the person who set it up in our company,
so my knowledge is limited, but if you are talking about FI document
parking then IMG menu (4.6C) "Financial Accounting", "Accounts Receivable and
Accounts Payable", "Business Transactions", "Incoming Invoices and Credit
Memos", "Carry Out and Check Settings for Parking Documents" is your starting
point.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2>I've worked more with payment release, and a lot of the
steps are common, e.g. the workflow variants. You have to create (at least) one
workflow variant for each company code currency, but you'll figure that out soon
enough if you try to assign a NOK-variant to a EUR-company. It's the
"Preliminary posting release" group of options you are interested in for parking
documents. Use of release approval groups is optional, you can leave it blank
when you assign release approval paths and procedures if you don't need to have
fine-grained control based on groups of vendors (and customers). In any case you
ought to assign one release approval path and procedure with an empty approval
group to use as a "catch-all" solution.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2>By reading the documentation for the various steps you
should be able to figure it out. It is well documented. Short and to the point.
</FONT></SPAN><SPAN class=438021605-08082006><FONT face=Arial color=#0000ff
size=2>If you define your own subworkflow for this you may not (depending on how
you construct your subworkflow) have to perform the customizing step of defining
users with release authorization.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=438021605-08082006><FONT face=Arial
color=#0000ff size=2>In addition you have the "Materials Management", "Logistics
Invoice Verification" hierarchy, including "Document Parking" if you are
using LIV. It has a lot of additional features compared to the FI solution,
including a much more flexible solution with regards to blocking the document.
There's other types of criteria, including stochastic options (e.g. block 25% of
invoices over 50 NOK, block 50% of invoices over 100 NOK).</FONT></SPAN></DIV>
<DIV align=left><FONT face=Arial size=2>-- </FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Kjetil Kilhavn, Statoil ØFT KTJ
BAS DEV SAP</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; 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>Nash John<BR><B>Sent:</B>
8. august 2006 00:05<BR><B>To:</B> SAP Workflow Users'
Group<BR><B>Subject:</B> FI Parking document<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi Frends,</DIV>
<DIV> </DIV>
<DIV>Can anyone tell me the steps involved in parking document workflow
includng IMG?</DIV>
<DIV> </DIV>
<DIV> Thanks in advance</DIV>
<DIV> </DIV>
<DIV>Nash John</DIV></BLOCKQUOTE><p></p><p><font size=1>-------------------------------------------------------------------<br>The information contained in this message may be CONFIDENTIAL and is<br>intended for the addressee only. Any unauthorised use, dissemination of the<br>information or copying of this message is prohibited. If you are not the<br>addressee, please notify the sender immediately by return e-mail and delete<br>this message.<br>Thank you.</font size></BODY></HTML>