• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Order Approval Routing Bizarreness

We have about 20 orders whose statuses have behaved quite weirdly covering a
month or so of time. The order approval technique is that a processing
option (on a copy of P4310) specifies the approval route - yet a few orders
do not behave as we would expect.

Anyone had experience with the following sorts of strange behaviour?

1- Orders are approved without being released.
I found that some orders are approved (status 440) but they are still
awaiting to be released. To my suprise, they are appearing in the Release
Order screen of some managers not in the approval route. Normally, when a
order is entered, it falls into the approval route code that is specified in
the processing options and then goes into the different levels of approval.
However, if the order is on hold, it should be released first to allow
others in the approval route to approve it. That is not case for some orders
within nesta.

2- Statuses moving from 440 to 440
When all managers in an approval route code approve an order, it should then
move to the approved status 440 for A/P voucher matching. It appears for
some orders that the statuses are moved to 440 twice. That should never
happen. It seems that every single action done by an approver in the
approval route is moving the status to 440.

cheers

Will


This email and any attachments are confidential and may be the subject of
legal privilege. Any use, copying or disclosure other than by the intended
recipient is unauthorised. If you have received this message in error,
please notify the sender immediately via +44 (020) 7645 9500 or by email to
nesta@nesta.org.uk and delete this message and any copies from your computer
and network.
The views expressed in this email are those of the author and do not
necessarily reflect the views of NESTA.
 
We are OW 7332 SP10. We have seen orders with approval routes changing
status on their own. Our situation seems to be that if an individual that
has approval authority in a route enters or inquires on an order it will
bump the statuses.

There has been a SAR issued in regards to P43081 and statusing.
 

Mike Dupaix

VIP Member
Will,

Approval routes do not follow a single path. All individuals are notified that an order needs attention in the route. If an approver at a 'higher' level approves an order, the order can be released.

Here is an example.
Route 1 has three approval levels; 1,000, 5,000, 10,000. If the individual at the 10,000 level approves the order before either the 1,000 or 5,000 level approvers release the order, the 10,000 level overrides the lower level and the order is approved to continue.

> We have about 20 orders whose statuses have behaved quite weirdly covering a
month or so of time. The order approval technique is that a processing
option (on a copy of P4310) specifies the approval route - yet a few orders
do not behave as we would expect.

Anyone had experience with the following sorts of strange behaviour?

1- Orders are approved without being released.
I found that some orders are approved (status 440) but they are still
awaiting to be released. To my suprise, they are appearing in the Release
Order screen of some managers not in the approval route. Normally, when a
order is entered, it falls into the approval route code that is specified in
the processing options and then goes into the different levels of approval.
However, if the order is on hold, it should be released first to allow
others in the approval route to approve it. That is not case for some orders
within nesta.

2- Statuses moving from 440 to 440
When all managers in an approval route code approve an order, it should then
move to the approved status 440 for A/P voucher matching. It appears for
some orders that the statuses are moved to 440 twice. That should never
happen. It seems that every single action done by an approver in the
approval route is moving the status to 440.

cheers

Will


This email and any attachments are confidential and may be the subject of
legal privilege. Any use, copying or disclosure other than by the intended
recipient is unauthorised. If you have received this message in error,
please notify the sender immediately via +44 (020) 7645 9500 or by email to
nesta@nesta.org.uk and delete this message and any copies from your computer
and network.
The views expressed in this email are those of the author and do not
necessarily reflect the views of NESTA.





--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=519
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************

<
 
Thanks Mike

You're suggesting that if the higher approver gets to the order first, then
when the middle approver approves it in their queue it goes no further. This
maybe happening to some, as we have multiple approvers, but I think it's
worse than that - the status has to be manually moved onto 999.

Some list members have suggested SARs - we've put on some - but I'll double
check if any are outstanding (so to speak).

Thanks

Will
 

scottw

Well Known Member
I suggest running the process that is updating, if possible thru debug to
see where the problem is. Thanks
 
SARs 4577157 and 4577991 (mini ESUs) were suppose to address the issues with
'Purchase Order Statusing' for both objects P4310 and P43081. JDE took some
time before addressing the issues. Both SARs released in October and seem
to be included in the November ESU 4605023.

Leah
 
Top