RE: User space blues; JD Edwards

Sorry to hear that that you are unhappy with Oracle Tech Support for the
reasons you stated below.
I, on the other hand, am extremely happy and satisfied with Oracle Tech
Support, and
I posted your question to Oracle as a favor to you and will now share
with you the prompt, knowledgeable tech support that JDE is famous for.
Your solution is:

Error 3672 - User space record not retrieved
The number of journal entries in the batch you are trying to process is
too large. The maximum number of transactions the P09110Z program can
process in one batch is approximately 17700. Reduce the number of items
you are processing. [This is a known issue and the workaround is to
break up the batches. It has been documented under SAR 5646046.]


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of SJL
Sent: Friday, March 21, 2008 1:26 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: User space blues; JD Edwards

Eric -

I have given up on Oracle-Peoplesoft-JDE support. In my opinion, they
are
essentially worthless at supporting their own products.
When you call the support line for help, nine times out of ten you'll
get
one of the following (useless) responses:

1) Did you modify the program (I learned after the first call to answer
NO
to this question, once I tested the pristine program to determine that
the
bug was in the original code).

If you answer "yes", they'll probably say "then you obviously broke the
code
when you modified it!"

OR

2) They'll ask pertinent questions to determine how to set up a scenario
on
their system, and after an interminable period of time they'll call you
back
and say:

a) We can't duplicate the problem here! (...thus it must not exist)
or
b) The program is working as designed (i.e., what you reported as a
'bug', they consider a 'feature')

OR finally they'll say:

3) Oh, yes - we know about that problem, and the fix will be in the
next
release of the software, if you care to wait that long. If not, we have
a
'paper' fix that you can apply to your code, but we won't guarantee that
it
will fix your problem.


In this case, the only 'fix', IMO, is to not use a user space for the
transactions.
It is not broken, per se, rather poorly designed and implemented.

- sjl