Hi Schumacher,<br>&nbsp;&nbsp; Thanks a lot for your nice explanation. I have used the BTE 2213 to trigger the event.<br><br>Regards,<br>Ibrahim Khan<br><br><div class="gmail_quote">2008/10/22 Schumacher, Margaret <span dir="ltr">&lt;<a href="mailto:mschumacher@teleflexmedical.com">mschumacher@teleflexmedical.com</a>&gt;</span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">



<div>
<div dir="ltr" align="left"><font size="2" color="#0000ff"><span><font face="Arial">You might investigate the Business 
Transaction Events (tcode FIBF)&nbsp;1140 and&nbsp;2213.&nbsp; We 
didn&#39;t&nbsp;use&nbsp;the SAP configuration to trigger the parked document 
approval but rather issue our own event in 2213 and restrict the Post button in 
1140.&nbsp; I believe&nbsp;the existence of the configuration for a company code 
is what disables&nbsp;the post button.&nbsp; Also since we don&#39;t use the sap 
method the field BKPF-XWFFR had to be set to&nbsp;<span><span>&#39;X&#39; 
<font face="Arial">to avoid messages that appear in the FIPP.Release method.&nbsp; 
For sure this is a more involved means than just using the SAP configuration but 
if you can&#39;t find a way to enable the post button this&nbsp;is an option to 
disable it for the circumstances you 
require.</font></span></span></font></span></font></div>
<div dir="ltr" align="left"><font size="2" color="#0000ff"><span><span><span></span></span></span></font><font size="2" color="#0000ff" face="Arial"><span><span style="font-size: 11pt; font-family: Arial;"><br></span><font color="#000000"><span style="font-size: 10pt; font-family: Arial;">Business 
Transaction Event Interface 1140.&nbsp; During the creation and maintenance of 
Journal Entries this</span><span style="font-size: 10pt; font-family: Tahoma;"> 
</span><span style="font-size: 10pt; font-family: Arial;">interface 
will be used to restrict the POST button.<span>&nbsp; 
</span>All finance documents need to be parked so that the Approval Workflows 
will execute. The checking of called and batch processing to allow posting when 
the&nbsp;document is created&nbsp;by lockbox process or some other automated 
load pgm.</span></font></span></font></div>
<div dir="ltr" align="left"><font size="2" color="#0000ff" face="Arial"><span><font color="#000000"><span style="font-size: 10pt; font-family: Arial;"><font size="3"><font face="Times New Roman">&nbsp;

</font></font><span>&nbsp;&nbsp;<span>if</span>&nbsp;sy-tcode&nbsp;=&nbsp;<span>&#39;FV50&#39;</span><br>&nbsp;&nbsp;<span>or</span>&nbsp;sy-tcode&nbsp;=&nbsp;<span>&#39;FB50&#39;</span><br>&nbsp;&nbsp;<span>or</span>&nbsp;sy-tcode&nbsp;=&nbsp;<span>&#39;FB50L&#39;</span><br>&nbsp;&nbsp;<span>or</span>&nbsp;(&nbsp;sy-tcode&nbsp;=&nbsp;<span>&#39;FBB1&#39;</span>&nbsp;&nbsp;<span>and</span>&nbsp;sy-binpt&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;<span>and</span>&nbsp;sy-calld&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;)<br>
&nbsp;&nbsp;<span>or</span>&nbsp;(&nbsp;sy-tcode&nbsp;=&nbsp;<span>&#39;FB01&#39;</span>&nbsp;&nbsp;<span>and</span>&nbsp;sy-binpt&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;<span>and</span>&nbsp;sy-calld&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;)<br>&nbsp;&nbsp;<span>or</span>&nbsp;(&nbsp;sy-tcode&nbsp;=&nbsp;<span>&#39;FB01L&#39;</span>&nbsp;<span>and</span>&nbsp;sy-binpt&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;<span>and</span>&nbsp;sy-calld&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;)<br>
&nbsp;&nbsp;<span>or</span>&nbsp;(&nbsp;sy-tcode&nbsp;=&nbsp;<span>&#39;FB05&#39;</span>&nbsp;&nbsp;<span>and</span>&nbsp;sy-binpt&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;<span>and</span>&nbsp;sy-calld&nbsp;=&nbsp;<span>&#39;&nbsp;&#39;</span>&nbsp;).<br>&nbsp;&nbsp;&nbsp;&nbsp;t_exctab-okcod&nbsp;=&nbsp;<span>&#39;BU&#39;</span>.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>&quot;Post&nbsp;Button&nbsp;ok&nbsp;code&nbsp;to&nbsp;exclude</span><br>
&nbsp;&nbsp;&nbsp;&nbsp;<span>append</span>&nbsp;t_exctab.<br>&nbsp;&nbsp;<span>endif</span>.</span><font size="3" face="Times New Roman"> 
</font></span></font></span></font><span style="font-size: 11pt; font-family: Arial;"><b><br></b></span><span style="font-size: 11pt; font-family: Arial;"><br></span><span style="font-size: 10pt; font-family: Arial;">Business 
Transaction Event Interface 2213 when a user parks a journal entry.&nbsp; First 
it determines if the document is being parked for the first time or being 
changed.&nbsp; If it is the first time, the document is checked that it was 
parked with transaction FV50, FB50, FB50L, FB01, FB01L, <span>&nbsp;</span>or FB05 and that the company code, 
document number and fiscal year are filled and then the event FIPP.CREATED is 
created.&nbsp;&nbsp; The FIPP.CREATED event triggers a new journal entry 
approval workflow.</span><span style="font-size: 12pt;">&nbsp;<span>&nbsp;</span></span></div>
<div style="margin: 0in 0in 0pt;"><span style="font-size: 11pt; font-family: Arial;"><font size="3"><font face="Times New Roman">&nbsp;

</font></font><span><span>*&nbsp;Check&nbsp;if&nbsp;Document&nbsp;is&nbsp;parked&nbsp;for&nbsp;the&nbsp;first&nbsp;time&nbsp;or&nbsp;changed</span><br>&nbsp;&nbsp;<span>if</span>&nbsp;i_funcl&nbsp;<span>eq</span>&nbsp;<span>&#39;I&#39;</span>.<br><br><span>*&nbsp;&nbsp;&nbsp;Check&nbsp;document&nbsp;is&nbsp;parked&nbsp;with&nbsp;certain&nbsp;tcodes&nbsp;to&nbsp;kick&nbsp;off&nbsp;workflow</span><br>
&nbsp;&nbsp;&nbsp;&nbsp;<span>if</span>&nbsp;t_vbkpf-tcode&nbsp;<span>eq</span>&nbsp;<span>&#39;FV50&#39;</span><br>&nbsp;&nbsp;&nbsp;&nbsp;<span>or</span>&nbsp;t_vbkpf-tcode&nbsp;<span>eq</span>&nbsp;<span>&#39;FB50&#39;</span><br>&nbsp;&nbsp;&nbsp;&nbsp;<span>or</span>&nbsp;t_vbkpf-tcode&nbsp;<span>eq</span>&nbsp;<span>&#39;FB50L&#39;</span><br>
&nbsp;&nbsp;&nbsp;&nbsp;<span>or</span>&nbsp;t_vbkpf-tcode&nbsp;<span>eq</span>&nbsp;<span>&#39;FB01&#39;</span><br>&nbsp;&nbsp;&nbsp;&nbsp;<span>or</span>&nbsp;t_vbkpf-tcode&nbsp;<span>eq</span>&nbsp;<span>&#39;FB01L&#39;</span><br>&nbsp;&nbsp;&nbsp;&nbsp;<span>or</span>&nbsp;t_vbkpf-tcode&nbsp;<span>eq</span>&nbsp;<span>&#39;FB05&#39;</span>.<br>
<br><span>*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Check&nbsp;if&nbsp;document&nbsp;number&nbsp;is&nbsp;filled</span><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>if</span>&nbsp;wf_id-bukrs&nbsp;<span>ne</span>&nbsp;space&nbsp;<span>and</span>&nbsp;wf_id-gjahr&nbsp;<span>ne</span>&nbsp;space<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>and</span>&nbsp;wf_id-belnr&nbsp;<span>ne</span>&nbsp;space.<br>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>call</span>&nbsp;<span>function</span>&nbsp;<span>&#39;SWE_EVENT_CREATE_FOR_UPD_TASK&#39;</span><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>exporting</span><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>event</span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=&nbsp;<span>&#39;CREATED&#39;</span><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;objtype&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=&nbsp;<span>&#39;FIPP&#39;</span><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;objkey&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=&nbsp;wf_objkey<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>tables</span><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;event_container&nbsp;=&nbsp;container_instanz.<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span>endif</span>.<br>
&nbsp;&nbsp;&nbsp;&nbsp;<span>endif</span>.</span><font size="3" face="Times New Roman"> 
</font></span></div>
<div style="margin: 0in 0in 0pt;"><span style="font-size: 11pt; font-family: Arial;"><font size="2" color="#0000ff"></font>&nbsp;</span></div>
<div><span style="font-size: 12pt;"><span></span></span><span style="font-size: 12pt;"><span></span></span><span style="font-size: 12pt;"><span><font size="2" color="#0000ff" face="Arial"></font></span></span>&nbsp;</div>
<div align="left">
<p style="margin: 0in 0in 0pt;" align="left"><span style="font-size: 10pt; font-family: Arial;">Regards</span></p>
<p style="margin: 0in 0in 0pt;"><span style="font-size: 10pt; font-family: Arial;">&nbsp;</span></p>
<p style="margin: 0in 0in 0pt;"><span style="font-size: 10pt; font-family: Arial;">Margaret 
Schumacher</span></p>
<p style="margin: 0in 0in 0pt;">
</p><p style="margin: 0in 0in 0pt;"><font size="2" color="#0000ff" face="Arial"></font><br></p></div>
<div dir="ltr" align="left" lang="en-us">
<hr>
<font size="2" face="Tahoma"><b>From:</b> Nat 4 Govender 
[mailto:<a href="mailto:ngovender4@toyota.co.za" target="_blank">ngovender4@toyota.co.za</a>] <br><b>Sent:</b> Wednesday, October 22, 2008 
4:57 AM<div class="Ih2E3d"><br><b>To:</b> SAP Workflow Users&#39; Group<br></div><b>Cc:</b> SAP Workflow 
Users&#39; Group<br><b>Subject:</b> Re: Issue with Park document release 
workflow<br></font><br></div><div><div></div><div class="Wj3C7c">
<div></div><font size="2" face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif">
<div>Hi Ibrahim,</div>
<div>&nbsp;</div>
<div>Prior to these changes could you see &#39;Post&#39; option in FBV0 or FBV2 to post 
the document manually?</div>
<div>&nbsp;</div>
<div>If no then check with your authorisation department.</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>If yes then get the system to automatically released the document and this 
will allow the user to post manually or viw workflow.</div>
<div>&nbsp;</div>
<div>Thanks </div>
<div>Nat Govender<br></div>
<div><br>
<div><br></div><font color="#990099">-----<a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a> wrote: 
-----<br><br></font>
<blockquote style="border-left: 2px solid rgb(0, 0, 0); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">To: 
  &quot;SAP Workflow Users&#39; Group&quot; &lt;<a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a>&gt;<br>From: &quot;Ibrahim Khan&quot; 
  &lt;<a href="mailto:ikhansap@gmail.com" target="_blank">ikhansap@gmail.com</a>&gt;<br>Sent by: <a href="mailto:sap-wug-bounces@mit.edu" target="_blank">sap-wug-bounces@mit.edu</a><br>Date: 
  10/22/2008 04:11AM<br>Subject: Issue with Park document release 
  workflow<br><br>Hi Friends, <br>&nbsp; I am using a custom workflow for 
  Invoice approval. For triggering the standard FIPP.CREATED event i have done 
  the following customising in SPRO: <br><br>1. SPRO -&gt; FI -&gt; AR &amp; AP 
  -&gt; Business Transactions -&gt; Outgoing inv/credit -&gt; Carry out or check 
  settings for doc parking <br>(or transaction O7L2). <br>&nbsp; <br>2. Define 
  your Workflow Variants for Preliminary Posting Release (Workflow you will use 
  to &#39;Release&#39; the FI for Posting) (tx OBWA). <br>&nbsp; <br>3. Assign your 
  Workflow variants to the company codes for which it will apply (tx OBWJ). 
  <br>&nbsp; <br><br>But after doing the above settings i am not able to see the 
  &#39;Post&#39; option in FBV0 or FBV2 to post the document manually. I am able to see 
  this only after setting the released flag. But the user wants both option to 
  post it manually as well as through workflow. How to achieve this. Please 
  advice. <br><font size="2" face="Default Monospace,Courier New,Courier,monospace">_______________________________________________<br>SAP-WUG mailing 
  list<br><a href="mailto:SAP-WUG@mit.edu" target="_blank">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br></font></blockquote>
<br></div></font><br>
<hr style="width: 100%; height: 2px;">

<p><small>This message is a privileged and private communication and may be 
read,copied and used only by the intended recipient(s). If you are not an 
intended recipient, please let us know by return email. Please then delete the 
message and do not disclose its contents to any person. Neither the sender nor 
Toyota South Africa Motors accepts any liability whatsoever as a result of the 
further dissemination of this message. Whilst all reasonable steps are taken to 
avoid corruption of data or information, we do not accept any liability should 
such corruption occur. </small></p></div></div></div>
<br>_______________________________________________<br>
SAP-WUG mailing list<br>
<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br></blockquote></div><br>