Sef
VIP Member
Hi all again
Last week I posed a question about the 'Commit Failed' error message in ship confirm and hopefully Larry's suggestion to include
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
into the JDE.INI will resolve that particular issue (the jury is still out on this one).
On top of this issue we have been experiencing lines on orders being ship confirmed twice or even three times. Most orders are confirmed using the 'confirm shown' form exit and if the user, upon completion, presses the find button, it can take up to a full minute until the order no longer appears.
It is still possible now to reselect the order and process again and thus to ship confirm the order (or part there of) for a second time.
The reason for this is because the ship confirm program runs like a dog (allegedly due to transaction processing) and because ShipConfirmEndDoc of N4200790 is called asynchronously.
Even though there are multiple SARs complaining about P4205 performance and there even is an enhancement SAR out there, JDE still haven't taken any action.
To keep a long story short, we are sick to death of the Ship Confirm program performance and are contemplating doing one or both of two things:
1) Turn transaction processing off in P4205
2) Call ShipConfirmEndDoc of N4200790 in-line
Has anybody out there had the same experience and has anybody tried solutions 1 and/or 2. Please let us know about your experiences.
Thanks for your contributions,
Rgds,
Sef van den Nieuwelaar
Australia
B732 on NT, XE on NT, B732/A73 on AS400, B733 on NT
* Coming to a European City near you soon *
Last week I posed a question about the 'Commit Failed' error message in ship confirm and hopefully Larry's suggestion to include
[DB SYSTEM SETTINGS]
OracleServerHandleReuse=0
into the JDE.INI will resolve that particular issue (the jury is still out on this one).
On top of this issue we have been experiencing lines on orders being ship confirmed twice or even three times. Most orders are confirmed using the 'confirm shown' form exit and if the user, upon completion, presses the find button, it can take up to a full minute until the order no longer appears.
It is still possible now to reselect the order and process again and thus to ship confirm the order (or part there of) for a second time.
The reason for this is because the ship confirm program runs like a dog (allegedly due to transaction processing) and because ShipConfirmEndDoc of N4200790 is called asynchronously.
Even though there are multiple SARs complaining about P4205 performance and there even is an enhancement SAR out there, JDE still haven't taken any action.
To keep a long story short, we are sick to death of the Ship Confirm program performance and are contemplating doing one or both of two things:
1) Turn transaction processing off in P4205
2) Call ShipConfirmEndDoc of N4200790 in-line
Has anybody out there had the same experience and has anybody tried solutions 1 and/or 2. Please let us know about your experiences.
Thanks for your contributions,
Rgds,
Sef van den Nieuwelaar
Australia
B732 on NT, XE on NT, B732/A73 on AS400, B733 on NT
* Coming to a European City near you soon *