Re: Ghost Commits

Re: Ghost Commits

Has anyone else encountered this problem....

We seem to have developed an issue with "Ghost Commits". It seems the
commitments from some deleted sales orders or sales lines are staying
behind.
I've talked with the users who swear that they are deleting these orders or
lines
properly. I tend to believe them since the problem is intermittent. I'm
currently
searching the KG with no success.

JDE support was of no help because "We can't recreate the problem" God I
hate
hearing that. As you can imagine these Ghost commits are causing us
problems
with over ordering items when we don't actually have the demand. I have run
the
sales order repost with no success! Any help is of course appreciated.
Thanks.


Bert R. Sternal
IT Business Analyst
Wabash National
(765) 772-2779 Voice
(765) 772-2299 Fax
 

Eric_Lehti

Active Member
RE: Ghost Commits

Bert, How about journalling the files? This would provide an audit trail
that you could review at your convenience.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Eric Lehti    Certified JD Edwards Professional
Fike Corporation, mailto:Eric.Lehti@fike.com
* Phone (816) 229-3405 ext. 231   * Fax (816) 229-4615
JD Edwards A73 Cume 10, AS/400 9406-730, OS/400 V4R4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

dkazinski

Member
Re: Ghost Commits

Yes,
I am currently experiencing this problem. I'm on cum 8 now and when at my
last client had the same problem, they were on 10. I had placed calls to
Edwards and searched for related SAR's. Edwards told me they could not
replicate and I found nothing in the Knowledge Garden. I don't have any
resolution, sorry. Debbie




Bert_Sternal <Bert_Sternal@wabashnational.com> on 02/28/2001 12:42:10 PM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Debbie Kazinski/FLECKHQ/PENTAIR/US)

Subject: Re: Ghost Commits




Has anyone else encountered this problem....

We seem to have developed an issue with "Ghost Commits". It seems the
commitments from some deleted sales orders or sales lines are staying
behind.
I've talked with the users who swear that they are deleting these orders or
lines
properly. I tend to believe them since the problem is intermittent. I'm
currently
searching the KG with no success.

JDE support was of no help because "We can't recreate the problem" God I
hate
hearing that. As you can imagine these Ghost commits are causing us
problems
with over ordering items when we don't actually have the demand. I have run
the
sales order repost with no success! Any help is of course appreciated.
Thanks.


Bert R. Sternal
IT Business Analyst
Wabash National
(765) 772-2779 Voice
(765) 772-2299 Fax




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=6417
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

dkazinski

Member
Re: Ghost Commits

Repost won't work because it bypasses canceled lines. (Just thought I would
add that.) Debbie




Bert_Sternal <Bert_Sternal@wabashnational.com> on 02/28/2001 12:42:10 PM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Debbie Kazinski/FLECKHQ/PENTAIR/US)

Subject: Re: Ghost Commits




Has anyone else encountered this problem....

We seem to have developed an issue with "Ghost Commits". It seems the
commitments from some deleted sales orders or sales lines are staying
behind.
I've talked with the users who swear that they are deleting these orders or
lines
properly. I tend to believe them since the problem is intermittent. I'm
currently
searching the KG with no success.

JDE support was of no help because "We can't recreate the problem" God I
hate
hearing that. As you can imagine these Ghost commits are causing us
problems
with over ordering items when we don't actually have the demand. I have run
the
sales order repost with no success! Any help is of course appreciated.
Thanks.


Bert R. Sternal
IT Business Analyst
Wabash National
(765) 772-2779 Voice
(765) 772-2299 Fax




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=6417
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

alzakkr

Active Member
RE: Ghost Commits

Are you using lots or serial numbers? If you are I am also experiencing the
same problem. I found a few SARS out there with no fixes. If I remember
correctly I was told I need to periodically clean the F41021 using WW update
or DFU.

Kristin Alzak
A7.3 c 8
(781) 324-8094 x2330

New England Coffee Company
www.necoffeeco.com
 
Re: Ghost Commits

Pardon me, what was I thinking!

I forgot to mention we are running World A73 cum 8.


Bert R. Sternal
IT Business Analyst
Wabash National
(765) 772-2779 Voice
(765) 772-2299 Fax



Bert_Sternal
<Bert_Sternal@wabashnat To: jdeworldml@jdelist.com
ional.com> cc:
Sent by: Subject: Re: Ghost Commits
owner-jdeworldml@jdelis
t.com


02/28/2001 01:42 PM
Please respond to
jdeworld







Has anyone else encountered this problem....

We seem to have developed an issue with "Ghost Commits". It seems the
commitments from some deleted sales orders or sales lines are staying
behind.
I've talked with the users who swear that they are deleting these orders or
lines
properly. I tend to believe them since the problem is intermittent. I'm
currently
searching the KG with no success.

JDE support was of no help because "We can't recreate the problem" God I
hate
hearing that. As you can imagine these Ghost commits are causing us
problems
with over ordering items when we don't actually have the demand. I have run
the
sales order repost with no success! Any help is of course appreciated.
Thanks.


Bert R. Sternal
IT Business Analyst
Wabash National
(765) 772-2779 Voice
(765) 772-2299 Fax




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=6417

*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

RBond

Member
RE: Ghost Commits

The commitments do not clear if there is not an open order when you run
the recommitment program. A work around is to write a program to clear
the commits when you run the recommit program.
 

curryj

Well Known Member
RE: Ghost Commits

I have encountered this issue several times with our users. I think I can
say that in every case, we've found that the "ghost commit" wasn't really a
ghost. We've always found another order or combination of orders out there
that add up to the same quantity as the one they've just deleted or
cancelled.

We've started teaching them to go to the Customer Service inquiry, enter the
branch plant and item number, and selecting status codes 525 through 562 (we
load confirm at 562). This always turns up an old order that was never
shipped for some reason, that they didn't realize was out there causing a
commitment.

We're on A7.3 cum 8. Repost Active Sales orders has never failed us once
we've identified and gotten rid of orders we're never going to ship.

__________________________________________________

Jon Curry
Farmers Co-operative Dairy Limited

Mailing Address:
P.O. Box 8118
Halifax, Nova Scotia, Canada B3K 5Y6

Physical Address:
745 Hammonds Plains Road
Bedford, Nova Scotia, Canada B4B 1A8

Phone: (902) 835-4005 Ext. 3155
Fax: (902) 835-1583
E-mail: jon.curry@farmersdairy.ns.ca
 

scott_parker

Reputable Poster
Re: Ghost Commits

We have almost this same problem except its with Reciept Routing and not Sales.
Items will be moved from Reciepts routing and the F41021 file now shows the qty avaliable but still shows the qty in the Other bucket 2.

JDE couldn't recreate. (Everyone knows that line.)

One of our Power Users has a DFU that is limited to the fields she needs to clear it up.


Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R5
 

MGrejtak

Member
RE: Ghost Commits

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C0A1C1.9D73DCB0
Content-Type: text/plain

We have narrowed down this problem to credit orders. We usually just clean
them up as we find them by creating a dummy sales order for the item and
then running a repost. Always works!

Michael Grejtak
Mfg. Systems Analyst
Manufacturing/Inventory/Raw Materials
Hancor, Inc.
(419)424-8253

>
 

JFilipek

Member
RE: Ghost Commits

I have a similar problem. I have resolved by creating a small program that
will zero out all the committment fields in the F41021. This program is
inserted in the repost CL before calling the RPG. Seems to have resolved the
problem.
Jim Filipek
 

tpayne

Reputable Poster
RE: Ghost Commits

Hi Bert,
Yes we also have the same problem.
The reset program only selects items with open orders from the order file,
therefore any items with nothing open will not get reset. This type of
problem frequently occurs with resets, due to niaive system design. We have
a program that resets the committed quantity for all items with a non-zero
quantity before we run the recalculate program.
There is no SAR out there to fix it - it's up to everyone to invent their
own wheel.
----------------------------------------------------------
Tony Payne - Senior Systems Analyst
United Musical Instruments USA Inc.
1000 Industrial Parkway
Elkhart, Indiana 46516
Tel: (219) 295 0079 ext. 2337
Fax: (219) 295 8613
Email: tpayne@umi-usa.com
(Running JDE A73 cum 10 on V4R3M0)
 

tstauffer

Member
RE: Ghost Commits

Bert: How's things going.

This is a issue that JDE requires that there be a order for an item for the
system to recalculate commitments. If there is no order it doesn't do
anything. We have solved the problem with a short RPG program to blank the
commitment fields before reposting. This makes sure that there isn't "ghost"
leftovers from orders canceled and commitment not reset correctly. I
recommend running this often.

Tim Stauffer
VP Marketing Systems, Strings and Accessories
United Musical Instruments USA
219-295-0079
219-295-8613 fax
tstauffer@umi-usa.com
 
RE: Ghost Commits

1.) Yes we are using lots, but not serial numbers.

2.) Journalizing the files sounds good! I could use this on several other
issues. How is this done?
My current programming staff has never done it!



Bert R. Sternal
IT Business Analyst
Wabash National
(765) 772-2779 Voice
(765) 772-2299 Fax



Eric_Lehti
<eric.lehti@fike.c To: jdeworldml@jdelist.com
om> cc:
Sent by: Subject: RE: Ghost Commits
owner-jdeworldml@j
delist.com


02/28/2001 02:19
PM
Please respond to
jdeworld






Bert, How about journalling the files? This would provide an audit trail
that you could review at your convenience.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Eric Lehti    Certified JD Edwards Professional
Fike Corporation, mailto:Eric.Lehti@fike.com
* Phone (816) 229-3405 ext. 231   * Fax (816) 229-4615
JD Edwards A73 Cume 10, AS/400 9406-730, OS/400 V4R4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=6423

*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

RBond

Member
RE: Ghost Commits

If you place a call to the program that clears the commitment field from
the cl program for reposts and run it every night keep the commitments
clean.
 

alaindee

Member
Re: Ghost Commits

Scott,

We are having the same problem as you but have no sulotions to it yet. But
I discovered just yesterday that If a P.O. is cancelled and there is a
quantity in-transit or a pre-reciept was made, it will leave the quantity
in F41021. I also tried reversing or cancelling the pre-reciept before
cancelling the actual P.O. line it is clearing F41021. There are still more
to discover on this. Hope this helps!




scott parker
<scott.parker@grot To: jdeworldml@jdelist.com
e.com> cc:
Sent by: Subject: Re: Ghost Commits
owner-jdeworldml@j
delist.com


01/03/2001 07:01
Please respond to
jdeworld






We have almost this same problem except its with Reciept Routing and not
Sales.
Items will be moved from Reciepts routing and the F41021 file now shows the
qty avaliable but still shows the qty in the Other bucket 2.

JDE couldn't recreate. (Everyone knows that line.)

One of our Power Users has a DFU that is limited to the fields she needs to
clear it up.


Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R5
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=6437

*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

scott_parker

Reputable Poster
RE: Ghost Commits

I do not claim to know anything about journaling a file but I have heard
some "Horror" stories.
Make SURE your staff knows how to attach a new Journal receiver? file
because I know that once the file gets "FULL" it will completely STOP all
changes to that file until this is done.
Also, from what I have heard, reading the journal files can become a huge
task in deciphering what it was that was changed.

We had the above problems before I came to work here and so what we have
done now is create our own "Audit" files.
Yes this required us to find each program that does any updates to that file
and place code in that program but at least then we have the audit file.
This unfortunately does not then track any WW update or SQL update type
changes.


Scott Parker
Grote Industries, LLC
mailto:scott.parker@grote.com





Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R5
 

prumschlag

Active Member
RE: Ghost Commits

I agree with Scott that journalling is not something that you should enter into
without a thorough understanding of its capabilities and requirements. But on
the other hand, once you have it established, it can be a terrific recovery and
"who dunnit" tool.

However, journaling will not directly address this issue. As others have
already noted, your problem is not "where did the commitments come from". The
problem is "why were the commitments not recalculated". Journaling will not
tell you that. The solution previously proposed will take care of this issue.

Phil







scott parker <scott.parker@grote.com> on 03/01/2001 09:27:09 AM

Please respond to jdeworld@jdelist.com








To: jdeworldml@jdelist.com

cc: (bcc: Phil Rumschlag/PHD)



Subject: RE: Ghost Commits








I do not claim to know anything about journaling a file but I have heard
some "Horror" stories.
Make SURE your staff knows how to attach a new Journal receiver? file
because I know that once the file gets "FULL" it will completely STOP all
changes to that file until this is done.
Also, from what I have heard, reading the journal files can become a huge
task in deciphering what it was that was changed.

We had the above problems before I came to work here and so what we have
done now is create our own "Audit" files.
Yes this required us to find each program that does any updates to that file
and place code in that program but at least then we have the audit file.
This unfortunately does not then track any WW update or SQL update type
changes.


Scott Parker
Grote Industries, LLC
mailto:scott.parker@grote.com





Scott Parker
Grote Industries, LLC.
WorldSoftware Version 8.1.2 AS/400 V4R5
--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=6484
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

paul

Member
Re: Ghost Commits

> I do not claim to know anything about journaling a file but I have heard
> some "Horror" stories.
> Make SURE your staff knows how to attach a new Journal receiver? file
> because I know that once the file gets "FULL" it will completely STOP all
> changes to that file until this is done.

No problem: when creating the journal, specify MNGRCV(*SYSTEM), and the
system will change out full receivers for you. It is a good idea to read
the data management guides in the iSeries online library before doing any
journalling.

> Also, from what I have heard, reading the journal files can become a huge
> task in deciphering what it was that was changed.

True. Journalling is not intended for use as an audit trail, but as a
backup and recovery tool. Hence, your next suggestion is more appropriate:

> We had the above problems before I came to work here and so what we have
> done now is create our own "Audit" files.
> Yes this required us to find each program that does any updates to that
file
> and place code in that program but at least then we have the audit file.
> This unfortunately does not then track any WW update or SQL update type
> changes.

To solve this problem, add a trigger to the file you want to audit:
ADDPFTRG. Your trigger program can then create an audit trail, and it works
no matter how the file is updated (apart from CLRPFM, which a journal will
record).

Again, reading the data management guides is strongly indicated.

--
Paul
 
Top