RE: J.D.Edwards Solution Explorer

Carl_Fisher

Well Known Member
RE: J.D.Edwards Solution Explorer

It means OneWorld hasn't finished what it was doing, and you need to wait to
do anything else, often occurs when OneWorld has a complex Update to do, or
a screen fill of data to validate, the hour glass has gone but you still
can't do anything else until it has finished.



OW733.3 Xe SP 14.2
Enterprise Server - Intel NT + Oracle 8.0.6
Client - Citrix TSE + 4 NT PC's for development
 
Re: J.D.Edwards Solution Explorer

A business function is still processing in the background when you try to exit. Maybe what's happening is that the business function is looping when you exit.

Yet another handy, intuitive, informative message when a user tries to exit
from Solution Explorer:

Threaded Business Functions processing. Please wait then try again.

Any ides on what this means


Regards
Malcolm Rolton
Operations Manager
Foodstuffs (SI) Ltd
Phone (03) 353 8661 Cell 025 441 458
######################################################################
This e-mail message has been scanned for Viruses and Content by
both MailMarshal and Norton's Antivirus.

Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addresses and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender
and delete the material from any system and destroy any copies.

Please note that the views and opinions expressed in this message may be
those of the individual and not neccesarily those of Foodstuffs (South Island) Ltd

######################################################################


C Ho
Intermediate Programmer/Analyst
Xe SP 15.1, update1
AS/400 V4R5 coexistant
CO on SQL 7.0 SP2 + hotfix
 
Re: J.D.Edwards Solution Explorer

We used to get this in B73.3.2, AIX. mostly during import functions to the
Financial modules. What we found was happening was during an import OW
would launch additional jobs which ran in the background and didn't have
their own little indicator on the start bar so we never knew when they ran
or how long they took. If we exited the Appl too soon after an import we'd
get that error. If we waited a little while (I think it was about 30 secs
for every 1000 records we imported) then we could exit without getting that
error. JDE never got back to us with a solution and the work around was
painful to come up with to say the least - lots of trial and error. At
least the message was accurate - There was a threaded business function
running locally and we did just have to wait and try again. To bad it
didn't tell us anything else like what and how long.

What process are you running just before you try to exit OW? Maybe you
just have to wait a few minutes for it to finish.

I know... not much help... sorry.

Regards,
Gerald.





CHo
<CHo@dundeerealty To: [email protected]
.com> cc:
Sent by: Subject: Re: J.D.Edwards Solution Explorer
owner-jdelistml@j
delist.com


08/27/2001 08:41
AM
Please respond to
jdelist





A business function is still processing in the background when you try to
exit. Maybe what's happening is that the business function is looping when
you exit.

Yet another handy, intuitive, informative message when a user tries to exit
from Solution Explorer:

Threaded Business Functions processing. Please wait then try again.

Any ides on what this means


Regards
Malcolm Rolton
Operations Manager
Foodstuffs (SI) Ltd
Phone (03) 353 8661 Cell 025 441 458
######################################################################
This e-mail message has been scanned for Viruses and Content by
both MailMarshal and Norton's Antivirus.

Attention:
The information contained in this message and or attachments is intended
only for the person or entity to which it is addresses and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon,
this information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the sender
and delete the material from any system and destroy any copies.

Please note that the views and opinions expressed in this message may be
those of the individual and not neccesarily those of Foodstuffs (South
Island) Ltd

######################################################################


C Ho
Intermediate Programmer/Analyst
Xe SP 15.1, update1
AS/400 V4R5 coexistant
CO on SQL 7.0 SP2 + hotfix

--------------------------
 
Re: J.D.Edwards Solution Explorer

Greetings:

When processing transactions with a large number of rows, the transaction may not actually be 'done' when you leave the OneWorld form.

Instead, in background OneWorld business functions (sub programs called by the form you have exited) are triggered which complete the process of committing/updating the data files with the transaction you have just completed.

For instance, this can happen with large sales orders, purchase orders, journal entries and inventory adjustments.

Suffice to say while these processes are completing in background you will not be able to exit OneWorld.

Also, I have seen COMMIT FAIL errors on these types of transactions when other users/processes are trying to assess or have asserted access to the same data files being updated.

Hope this layman's explanation helps.

Regards,

Robert W. Starinsky
Tradewinds Group, Inc.
Consultants to Management

Author of Implementing J. D. Edwards OneWorld, published in February, 2001 by Prima Tech.
 
Back
Top