soft commit problem

[lorser98]

List,

I hope someone can help me because I am desperate and out of leads. The
problem is this: All of a sudden our soft commits are not working, but
only sometimes. I have an example where for the same branch, same item,
same doc type the commit worked on one order but not the other order. When
I say not worked I mean it did not appear on the summary availability
screen as committed. Once the order goes thru sales update it seems to
reduce the on-hand properly. Now the only thing that happened just prior
to this problem was that we took a physical inventory. The JDE consultant
that I am working with said that this should not have caused any problem.
Please, if anyone has had this problem or might be aware of what could be
wrong please let me know. Thanks in advance.



WORLD 8.1

Lori Orser
Senior Programmer/Analyst
Cookson Electronics PWB Materials and Chemistry
ENTHONE
193 Marsh Hill Road
Orange, CT. 06477
Ph: 203-799-4969
Fax: 203-799-8179
email: [email protected]
______________________________________________________
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.
_____________________________________________________

 

[JSisson]

when do you run repost - before or after Sales Update?

j

 

[Guest]

A possible solution, but not the cause, is to run the Repost Open Orders
program, which resets the commitment numbers. Just the fact that this
program exists means that there are some very difficult to find problems in
commitments.

Andy Klee
www.JDETips.com

 

[curryj]

Is it possible that when your commits "don't work" it's because you're
creating future commitments? In Branch Plant Constants there is a "Specific
Commitment Days" field. If the Promised Ship Date (which in our system is
the same as Request Date) is more than this many days out from today, it
creates a Future Commitment. You can see future commitments by putting a 1
in the option field on Summary Availability.

Unless your Item Availability Definition (also in Branch Plant Constants)
includes a "-" beside Future Commitments, you won't see a commitment
reducing availability.

__________________________________________________

Jon Curry
Farmers Co-operative Dairy Limited A7.3 cum 8

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: [email protected]

 

[nbbhatiaoff]

Hi,
Commitment:
You need to check the following specifically:-
Promised date of order where commitment did not occur. You should note that if promised date in order falls outside commitment fence, the order is treated as future commit. You have mentioned that for same order and same BP, commitment is occuring for one order and not occuring for the other. You define commitment fence in Br-Plant constant through menu G4141. Whenever promised date in order falls beyond date calculated by formula (today+commitment days), the order goes on future commit.
Check processing option of P4211 (Sale Order Entry) in all versions which are used in various menus. See that you are soft commiting inventory therein.
Reduction of Qty.on hand:
System reduces qty. on hand either at the time of ship confirmation or during day end. This is dependent on UDC 40-IU. If sale order document type is mentioned in this table, qty. for such order type gets reduced during ship confirmation, otherwise it gets reduced during day end.
I hope this helps.
Regards,
Niranjan
[email protected]
lorser98 <[email protected]> wrote: List,

I hope someone can help me because I am desperate and out of leads. The
problem is this: All of a sudden our soft commits are not working, but
only sometimes. I have an example where for the same branch, same item,
same doc type the commit worked on one order but not the other order. When
I say not worked I mean it did not appear on the summary availability
screen as committed. Once the order goes thru sales update it seems to
reduce the on-hand properly. Now the only thing that happened just prior
to this problem was that we took a physical inventory. The JDE consultant
that I am working with said that this should not have caused any problem.
Please, if anyone has had this problem or might be aware of what could be
wrong please let me know. Thanks in advance.



WORLD 8.1

Lori Orser
Senior Programmer/Analyst
Cookson Electronics PWB Materials and Chemistry
ENTHONE
193 Marsh Hill Road
Orange, CT. 06477
Ph: 203-799-4969
Fax: 203-799-8179
email: [email protected]
______________________________________________________
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.
_____________________________________________________
--------------------------

 

[lorser98]

Before sales update........Is that a problem ???


Lori Orser
Senior Programmer/Analyst
Cookson Electronics PWB Materials and Chemistry
ENTHONE
193 Marsh Hill Road
Orange, CT. 06477
Ph: 203-799-4969
Fax: 203-799-8179
email: [email protected]



JSisson
<JSisson@2onesou To: [email protected]
rce.com> cc:
Sent by: Subject: RE: soft commit problem
owner-jdeworld@j
delist.com


05/10/02 08:32
PM
Please respond
to jdeworld





when do you run repost - before or after Sales Update?

j
--------------------------

 

[lorser98]

Sorry, actually after sales update and I found that we are not doing
sales update every night.

Lori Orser
Senior Programmer/Analyst
Cookson Electronics PWB Materials and Chemistry
ENTHONE
193 Marsh Hill Road
Orange, CT. 06477
Ph: 203-799-4969
Fax: 203-799-8179
email: [email protected]



lorser98
<lorser@cooksonelectr To: [email protected]
onics.com> cc:
Sent by: Subject: RE: soft commit problem
owner-jdeworld@jdelis
t.com


05/13/02 10:07 AM
Please respond to
jdeworld






Before sales update........Is that a problem ???


Lori Orser
Senior Programmer/Analyst
Cookson Electronics PWB Materials and Chemistry
ENTHONE
193 Marsh Hill Road
Orange, CT. 06477
Ph: 203-799-4969
Fax: 203-799-8179
email: [email protected]



JSisson
<JSisson@2onesou To: [email protected]
Sent by: Subject: RE: soft commit problem
owner-jdeworld@j
delist.com


05/10/02 08:32
PM
Please respond
to jdeworld





when do you run repost - before or after Sales Update?

j
--------------------------
--------------------------

 

[hamida]

We are on A7.3.11+ (we patch and customize - sometimes to our
detriment!)

We also have had numerous problems with inaccurate commitments. The only
way we found to resolve problems was to run repost programs daily and to
create file update programs that would zero out all related fields in the
F41021 before we ran repost programs (SO, WO, and PO). Seems like an
overkill but it worked for us - at least so far.

If you do a little research in the KG, JDE actually stated that this may be
a possible solution for certain SO related conditions (why JDE can't "fix"
repost programs is a mystery to me!).

We also decided to do the same for WO and PO related fields. Proceed with
caution and do a lot of testing if you go down this path.






lorser98 <[email protected]>@jdelist.com on 05/13/2002 07:05:02
AM