FI Parked Doc workflows in 4.6c

[Griffiths, Mark]

Hi Susan,
 
The problem you are experiencing does sound like a slow update problem.
 
Firstly, rather than using three check function modules have you considered
'Start Conditions' or a Receiver Type Function Module.
 
If these don't reliably work then you could try triggering a dummy workflow,
which shells a single step background task with a requested start deadline
delay.  Set the delay for a minute and your problems should be solved. The
background step can contain the same code as your Check function modules and
either trigger a new event or start a subflow.
 
Hope this helps,
 
Mark
 
Mark Griffiths
SAP UK
 
 
 
-----Original Message-----
From: Susan R. Keohan [mailto:skeohan at MIT.EDU]
Sent: 07 December 2000 14:29
To: SAP-WUG at MITVMA.MIT.EDU
Subject: FI Parked Doc workflows in 4.6c
 
 
Greetings Workflow-ers,
 
Before you stop reading, this is not my typical plea for speakers or
presentation ideas for our next ASUG conference... but IF you are
interested, please send me e-mail at skeohan at mit.edu !!  Time is running
out for planning this conference, and there are some sessions that need
speakers at this time.
 
We are upgrading from 4.5 to 4.6c.  We have workflows which should kick off
when an FI Parked document is created.  There are 3 entries in the event
linkage tables for this event (FIPP CREATED).  For each entry, there is a
Check Function Module, which will determine what the document type is, and
based on that value, the correct workflow will be started. (Only one of
three should start for any given doc type).
 
So, the documents are created, sometimes manually, sometimes via a feed.
The event FIPP Created is raised.  The check function modules are executed,
but all three fail when they attempt to access the document.
 
And, to make it more interesting, this problem does not occur in all of our
4.6c environments, but most noticeably, in the integration system.
 
These events, function modules, workflows, etc., all work fine in our 4.5
environment, and in our 4.6c development environment.
 
Personally, I suspect that the FI documents (table VBKPF) are not actually
in the database at the time the check FMs run.  I know that the workflow
engine has had some performance improvements made.  But I am having a hard
time convincing my basis friends to take a closer look.
 
What fun!
 
Sue