Parallel Subflow inside a Parallel Subflow??

Mark Pyc mark.pyc at gmail.com
Wed Apr 4 05:06:06 EDT 2018


G'day Wuggers,

Wow, been a long time, but scratching my head again so once again come to
the fount of all WF knowledge.

I'm helping another developer who has got to a point of confusion in a
parked Logistics Inv. scenario where an Invoice is Held with reference to
multiple POs and multiple items within those POs. It is Saved as Held as
there are no Service Entry Sheets. The solution is to send create parallel
WFs out per PO to the PO creator/requestor asking them to create Service
Entry Sheets (SES) if appropriate. The desire is to have a Wait for
Correlated Event that an SES has been created for each item. You can't seem
to create parallel Wait for Correlated Event steps, so have put the Waits
inside a Subflow.

The binding to the Sub-Subflow  is based on
&PO_ITEMS[&_WF_PARFOREACH_INDEX&]& with the Items table indicated on the
Misc tab.

The system doesn't throw an error, but it doesn't create the subflow
either. In the log there is a phantom step with a step type of "STEP" which
I can't ever remember seeing before. Note that although there is a Node
number there is no Task Number and no Workitem Number

Is this some weird restriction that you can't have a parallel subflow
within a parallel subflow???

The WF just carries on like that Step doesn't exist, which indeed it
doesn't seem to.

I'm not justifying the design either from a business process or technical
build, but I'm at a loss as to what is happening technically when trying to
implement this.

Appreciate any sagely input!

Have fun,
Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20180404/3e894870/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 56345 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20180404/3e894870/attachment-0001.png


More information about the SAP-WUG mailing list