Rony,

I hate to say this but, there might be other counters etc. that are not
visible to you.

In my opinion you should do the following:

1.  Refresh the test environment from production.  This will assure that
all of the counters like the next IAN and the GHB counter you last
described are in sync.
2.  Re-load your COA values.
3.  Then test the results.
4.  If successful then load to production.

I know that this might seem like a lot of work at this stage in your
project, but it is the safest way to assure no counter problems.

Good Luck!

Daniel J. Sweeney       
Senior Technical Consultant
PHOENIX Business Consulting, Inc.
P. O. Box 237, Greensburg, PA 15601
Tel: 724.836.4446 x7, Fax: 425.988.7102
Cell:  860-490-6712    E-Fax: 832-550-5144
dsweeney@xxxxxxxxxxxxxxxx
www.phoenixbcinc.com
       
 
SSA GLOBAL Recognized Services Provider
 

-----Original Message-----
From: bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+dsweeney=phoenixbcinc.com@xxxxxxxxxxxx] On Behalf
Of Rony Mayer
Sent: Wednesday, December 28, 2005 9:30 AM
To: SSA's BPCS ERP System
Subject: [BPCS-L] BHSEQ counter in GBH table

Guys,

do you know where the system keeps the last used sequence number that it
uses in the GHB table ? When I try to integrate transactions from our
ACR
(in a test environment), the system generates a sequence number that is
already in the table, causing problems on the integration. It looks like
it
has a counter that is not synchonized with the table and it's
duplicating
the sequence.

Do you guys know where to start looking for the problem ?

TIA,

Rony

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.