Address Book Next Numbers skipping

[i_stevens]

Hi All

First of all, please forgive me as I know this has been discussed on the list
before. I have searched the archives and drawn a blank, so I need your help.

Our address book next numbers are skipping sporadically. This has previously
been reported to JDE and their suggested resolution is to monitor when they are
changing and work out what Applications/UBE's may be being used when the next
number skips. Not an easy task ! Since going live, we have added approximately
5000 records to our address book, but the system thinks we have used 62,000
records (at this rate, we might run out as we have lots of employees and lots of
suppliers).

We have reviewed several things:
- we don't have check digits on
- we are sure there is no conlict between any environments (ie. we are not using
a common Next Numbers file between Dev and Prd).
- we have reviewed all tables that have changed on a particular day, but can't
find any that contain a number that looks like it's been drawn from the Address
book next number range.

I have tried to put event rules on the Next Numbers table to output to a new
table with the User Id and Program Id of the user making the change. As soon as
i put Event Rules on the Next Numbers table, I get "Business Function caused a
memory violation" when trying to enter a new Address Book Record.

I would appreciate any help you can give:

1. Has anyone out there stumbled across a solution for the A/B next numbers
skipping
2. Anyone know why I am getting "Business Function Memory Violation" after
adding new Event Rules to the Next Numbers table
4. Any other ideas for tracking changes to the Next Numbers table (it doesn't
contain the usual "Audit fields" like most tables do).

Please help !

Desperate and about to tear my hair out !

FYI - I am posting this on both the Jdelist and Jdelist Developers forums.

Thanks
Ian

B733.2 SP11.1, AS/400 V4R4M0, World 11 X2 Coexistence.



View our website at http://www.monadel.com.au

|---------------------------------------------------------------------------|
| |
| If this communication is not intended for you and you are not an|
| authorised recipient of this email you are prohibited by law from dealing|
| with or relying on the email or any file attachments. This prohibition|
| includes reading, printing, copying, re-transmitting, disseminating,|
| storing or in any other way dealing or acting in reliance on the|
| information. If you have received this email in error, we request you|
| contact us immediately by returning this email to|
| [email protected] and destroy the original. |
|---------------------------------------------------------------------------|






B733.2 SP11.1, A73 Cum 11 (Payroll)
Ent Svr AS/400 V4R4, Dep Svr NT4 SP5

 

[BBritain]

Ian,

I have also seen skipping, but not to your degree. One of the main things I found cause this is when an Application has the AN8 field on the form without disabling Next Numbers. Because AN8 ties through Data Dictionary to Next Numbers, the field will be autopopulated every time you enter the form or click OK. To troubleshoot this, we had to open next numbers in UTB and start the application and work through the actions, constantly checking the NN table for changes. I'm not sure if any UBE's do the same thing but you can alway put the UBE in debug mode, or add breaks (using MD_Debug) and monitor NN. And then there's always turning debuglog on and then search for hits on the NN table.

Ben again

 

[bioriz]

Ian,

I remember a while back we had an issue where the pickslip program was eating up the address book next numbers. Somehow we were missing the record for next number record for P/S (40/03), and the default for when the next number index wasn't found was the address book next number index. Not sure is this type of issue can still exist, but it may be possible you have a missing record for a similar situation. Perhaps, when you see a gap see whats running during that period to figure out what may be stealing the A/B number.

Hope this helps.

 

[flyingmg]

Ian,

I am at home and can't remember something exactly. Anyway here are some o=
f my thoughts. =20

1. Do a test by using X0010 (internal next number business function) to t=
est if your next number works correctly;
2. If you suspect any UBE or Application, turn your JDEDEBUG on. Search t=
he log file and look for "UPDATE DEVDTA.F0005 SET ......". (I am not sure=
F0005 is the correct NN table)
3. "Business Function caused a memory violation"
Did you use Table I/O event rule on JDE table trigger in your test? If ye=
s, make sure open and close table explicitly. =20
4. You may try to use database level triggers instead of JDE table ER.

Here is the last thing you may try. Turn on SQL Tracing. Control Panel --=
is log file can give any transactions against your database. Caution: It =
grows super fast.

Save some of your hair for bigger issues

MG
----- Original Message -----
From: i_stevens
Sent: Friday, January 25, 2002 5:00 PM
To: [email protected]
Subject: Address Book Next Numbers skipping


Hi All

First of all, please forgive me as I know this has been discussed on the =
list
before. I have searched the archives and drawn a blank, so I need your h=
elp.

Our address book next numbers are skipping sporadically. This has previo=
usly
been reported to JDE and their suggested resolution is to monitor when th=
ey are
changing and work out what Applications/UBE's may be being used when the =
next
number skips. Not an easy task ! Since going live, we have added approx=
imately
5000 records to our address book, but the system thinks we have used 62,0=
00
records (at this rate, we might run out as we have lots of employees and =
lots of
suppliers).

We have reviewed several things:
- we don't have check digits on
- we are sure there is no conlict between any environments (ie. we are no=
t using
a common Next Numbers file between Dev and Prd).
- we have reviewed all tables that have changed on a particular day, but =
can't
find any that contain a number that looks like it's been drawn from the A=
ddress
book next number range.

I have tried to put event rules on the Next Numbers table to output to a =
new
table with the User Id and Program Id of the user making the change. As =
soon as
i put Event Rules on the Next Numbers table, I get "Business Function cau=
sed a
memory violation" when trying to enter a new Address Book Record.

I would appreciate any help you can give:

1. Has anyone out there stumbled across a solution for the A/B next numb=
ers
skipping
2. Anyone know why I am getting "Business Function Memory Violation" aft=
er
adding new Event Rules to the Next Numbers table
4. Any other ideas for tracking changes to the Next Numbers table (it do=
esn't
contain the usual "Audit fields" like most tables do).

Please help !

Desperate and about to tear my hair out !

FYI - I am posting this on both the Jdelist and Jdelist Developers forums=
.

Thanks
Ian

B733.2 SP11.1, AS/400 V4R4M0, World 11 X2 Coexistence.



View our website at http://www.monadel.com.au

|------------------------------------------------------------------------=
---|
| =
|
| If this communication is not intended for you and you are not=
an|
| authorised recipient of this email you are prohibited by law from deal=
ing|
| with or relying on the email or any file attachments. This prohibit=
ion|
| includes reading, printing, copying, re-transmitting, disseminati=
ng,|
| storing or in any other way dealing or acting in reliance on =
the|
| information. If you have received this email in error, we request =
you|
| contact us immediately by returning this email =
to|
| [email protected] and destroy the original. =
|
|------------------------------------------------------------------------=
---|






B733.2 SP11.1, A73 Cum 11 (Payroll)
Ent Svr AS/400 V4R4, Dep Svr NT4 SP5
--------------------------


G
[email protected]

 

[Sef]

Hi Ian,

Ben may be hitting the nail on the head here. Are there any (new) custom applications running that use AN8 on their form? I would hope most standard JDE application no longer have the NN flag ticked when not required, but it is quite common for new applications to forget to set this flag correctly.

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 *

 

[DBohner-(db)]

Ian,

Actually, next number skipping is a common occurrence... when applications
are customized... and next numbering is not disabled for Data Dictionary
items that are tied to NN...

Example of an issue we had. Users request to be able to view Shipment
Number on the Sales Order Detail Revisions of the P4210. Unbeknownst to the
developer(me), SHPN is died to an NN. Initially, NN was not disabled for
the SHPN column on the grid. Immediately users started asking why shipment
numbers were skipping...

Eventually we discovered the issue of NN being assigned.

You may want to review you form objects and validate whether they need to
have the disable NN checkbox disabled.

Best of luck!



Daniel Bohner
[email protected]
www.existinglight.net
JDE - XE & AS/400
JDE - B7331 & MS SQL 7x