SOME POS' HAVE STATUS CLOSED BEFORE THEY HAVE BEEN
Posted: Wed Oct 15, 2008 10:40 am
Hi All,
### Detailed Problem Statement ###
Some standard purchase orders for one supplier with two way match have been automatically closed when there are outstanding quantity items stll to be matched against the order. They are orders for quantity three. They were closed after matching to invoice for quantity 1, then re-openned after it was decided that the orders were going to continue for the remaining 2 quantities. On matching the second quanitity of 1, the orders autmatically closed when the AP autoapprove process took place.
I need to know why these orders closed when they were not fully matched.
### Workaround ###
THESE ORDERS HAVE BEEN RE-OPENNED
### Impact on Business ###
Need to know why this has happened to prevent further instances of this issue
Can you easily recover from, bypass or work around the problem?
Yes
Does your system or application continue normally after the problem occurs?
Yes
Are the standard features of the system or application still available; is the loss of
service minor?
Yes
Additional Info:
Shipments> More Tab
1) RECEIVE_CLOSE_TOLERANCE is 100
2) INVOICE_CLOSE_TOLERANCE is 0%
3) Receiving controls are configured on 0
We are not able to replicate the same issue in test instance.
Please adwise on this issue asap.
Rgds,
Suresh gaddam
### Detailed Problem Statement ###
Some standard purchase orders for one supplier with two way match have been automatically closed when there are outstanding quantity items stll to be matched against the order. They are orders for quantity three. They were closed after matching to invoice for quantity 1, then re-openned after it was decided that the orders were going to continue for the remaining 2 quantities. On matching the second quanitity of 1, the orders autmatically closed when the AP autoapprove process took place.
I need to know why these orders closed when they were not fully matched.
### Workaround ###
THESE ORDERS HAVE BEEN RE-OPENNED
### Impact on Business ###
Need to know why this has happened to prevent further instances of this issue
Can you easily recover from, bypass or work around the problem?
Yes
Does your system or application continue normally after the problem occurs?
Yes
Are the standard features of the system or application still available; is the loss of
service minor?
Yes
Additional Info:
Shipments> More Tab
1) RECEIVE_CLOSE_TOLERANCE is 100
2) INVOICE_CLOSE_TOLERANCE is 0%
3) Receiving controls are configured on 0
We are not able to replicate the same issue in test instance.
Please adwise on this issue asap.
Rgds,
Suresh gaddam