Order Processing

JerryCousart

Member
Having a problem with some lines on orders not advancing properly. When picking, I'm getting a pick number, hard commitment but the order status on the Customer Service Inquiry Screen is still at a 520-540 status. The Sales Ledger shows the line status at 540-460 (Picked)
A similar problem with Ship confim. Status on Customer Service Inquiry is 540-560 (Picked), but the line is confirmed in the Ledger 560-565 (Ship Confirmed) We just went live 2 weeks ago with phase 2 of our project. This problem is started happening with phase 1 and 2 when phase 2 went live. Anybody seem problems like this?
Thanks

XE SP17.1 Up2 Win2K SQL2000 CITRIX
 
Jerry,

One thing to check may be that the order lines are not on hold.
If the customer master has a 'Hold Code' set against it, when the order was
entered it will have gone on hold.
The order may have been picked, but prior to this someone has modified the
order, thus setting it back on hold.
I would expect that the Ship Confirm will not update the Sales Order Detail
file, but will still write a Sales
Ledger record.
It may not be the case for you - but worth a check all the same.

Regards,

Adrian
 
Jerry, we ran into a similar problem way back with B7321 and it still dogs us today in Xe. It gets down to lack of record lock. If an order in status 520/540 is being revised (eg quantity being changed for a specific detail line) and the warehouse runs pick slips before the revision is complete, the order will be advanced to 540/560, assigned a pick number and hard committed only to be bumped back to 520/540 after the order desk finishes revising the order.

This doesn't happen too often obviously but its really a pain when it does. I have contacted Denver twice about this problem (once after we discovered it in B7321 and once during XE testing). Both times the resulting SAR was mysteriously cancelled.

I'm not sure if this is your problem especially given that its also happening at ship confirmation but you can tell if you see extra sales ledger lines for 520/540 with time stamps within seconds of the pick slip print sales ledger lines. If this is your problem I hope you have a more sympathetic ear in Denver than we did. We are presently considering having our order desk staff print pick slips instead of the warehouse so that order revisions and pick slip printing can be coordinated to avoid this problem.

B7333, SP14.2, Update 1, Intel NT4, SQL7
 
This looks to be the exact problem we are having. I'll let you know if we have any better luck!


XE SP17.1 Up2 Win2K SQL2000 CITRIX
 
Jerry,

I don't know if it will help you any but the last SAR that I know of for this problem was 5043421. Denver closed it with status "Returned - Reconsider in Future".

Let me know if there is anything I can do to help you pursue Denver on this. Of all the dead ends that I have run into with JDE Support, this one bothers me the most.

HP

B7333, SP14.2, Update 1, Intel NT4, SQL7
 
I agree with Henry on pick slip processing when a user has the record open.
I've seen the same happen in our system. I've never seen the same issue
with ship confirm. We're using the interactive ship confirm program P4205
it issues an error message when the file is in use. Are you using the batch
ship confirm program R42500? If so, the issue resides with the UBE programs
not checking to see if the record is locked. They can certainly add our
name to the list of customers who'd like to see this corrected.



Walt Sellers
Heil Environmental Industries, Ltd.
OW B733.2 SP10, Citrix, Windows NT TS2000, Oracle 8.1.6
 
We have experienced this issue here as well. Took us a while to find out
why orders printed but didn't get updated. Our resolution is to not
generate the pick tickets until we are reasonable sure that that group of
order number shouldn't be open for edits (usually about 50 orders back from
the current order number). However sometimes this creates a problem for
shipping if they are caught up and waiting for orders.... Certainly this
issue should be able to have a SAR entered and have it fixed? We have not
yet opened a call for this but please add our name to the list of customers
who would like it corrected. Or if someone opens a SAR before we do, please
post the # for us.

We have also seen the same thing with the ship confirm. When we were
testing the batch process to run as part of our night operations. At the
time, the answer from JDE is for us to be sure that no one is doing manual
ship confirms when we run the batch process. This works for us for now,
since our customer service is not a 24 hour operation. Even with that we
are finding that we have to call people to check if they have completed all
the manual ship confirms for the day. What a pain. Maybe this issue should
be reopened as well - hoping for a SAR to generate a fix..

Karen

Karen Riner
OneWorld System Administrator, JDE PCP
Awana Clubs International
OWB733.2 SP16, NT, 2000, Oracle 8.1.6
 
Back
Top