PO Status is wrong

[Luvsql]

I just entered a PO with to items. One item qty 100, one item qty 50.
I approved the PO.
I entered a shipment for first item of 50, second 25 adn posted.
I entered another shipment for first item of 25, second 20.
This PO now have 25 remaining to ship, 0 invoiced for item 1, 5 remaining to ship and 0 invoiced for second item.
If you go into the edit PO status, the status of the PO and the line items shows as Released and it also does not show on the REceived/Not Invoiced report. The status should be Received.
This is the very first example I have posted to see how the report would print and the first post does not even work.

Does this not work if you use PO Approvals?

 

[Luvsql]

I have restored our live company into test (live does not have PO approvals). I entered a PO for inventory and non-inventoried items, then posted a shipment. The status is still showing 2 (released) even though it posted amounts to the accrual account and the POs do not show on the received not invoiced report.

There are no errors. GP is just not doing what it is supposed to be doing. How do we really know what's outstanding if the status of the line and PO is not getting updated properly?

 

[barbola]

Are you sure you used shipment and not shipment/invoice when you received against the PO? That's the only reason I can think of that the shipments should not show up on the received/not invoiced report unless there is a problem in posting.

The PO should not show status received until the remaining amounts were fully received. Also the PO changes to Released once the PO has been printed.

Did you do an inquiry on the PO and receivings? This might give more info than using edit PO Status.



Thanks!
Barb E.

 

[Luvsql]

Yes I'm positive. I've done 4 or 5 tests in 2 of our test companies (with fresh data). However, it looks like the "Live" companies work fine. I don't want to post dummy entries in our live company to test this. If I restored directly from a live company's backup, why would it behave differently? I've tried it on 4 machines using 2 different login accounts.

I know it should be received, that is why I don't understand what's going on. I've been using GP for 9 years, so I know what it's supposed to do. I ran a dexsql log and see no reference to any stored procedures on the POP10110 table or the POP10100 table when posting the receipt, but it should be running something to update those fields.

 

[Luvsql]

I ran the exact same test using another login ID who posts all the time, in the same company. Their POs get updated properly.

How can it be possible that one GP login has the field updated properly and the others not? I ran the exact same tests. 2 logins so far do not get this field updated properly.

I had the same sort of issue in payables once where a couple users had different data results doing the exact same processes and we had data corrution. Microsoft's only solution was to delete the user and recreate, except we had to recreate with a different login ID as some of the tables were not cleared out.

My user ID that I use does not even have a user class assigned so I have NO restrictions.

 

[Luvsql]

The issue is with the PO creation. So far is 2 of our users create a PO, no matter who receives is as shipment, PO status does not get updated properly (if status new, goes to released). If other users create PO, anyone can post the shipment and the status gets updated properly.

What the heck is wrong with this system? How can a user's GP account control how the code and sp's on sql and data get updated?

 

[barbola]

That's interesting. Our vendor has suggested the userid thing before.

Did you try those users on different machines? It has also been suggested to us to copy the Dynamics.dic from one machine to another.

The dumb thing is that you can tell your vendor there is a problem, but they'll charge you for looking into it.


Thanks!
Barb E.

 

[Luvsql]

We work in a citrix environment and I've tried it on 2 of the servers. I also tested it on my local workstation with the same results.

We have no way of knowing what our accruals should be now.

 

[jazgeek]

Luvsql, this might help you. These are two views I use to calculate the amount left to receive on an open PO

------------------
CREATE VIEW dbo.[1RECEIVEDAMTS]
AS
SELECT PONUMBER, POLNENUM AS POLIN, ITEMNMBR,
SUM(QTYSHPPD) AS QTYSHIP, SUM(QTYREJ)
AS QTYREJ
FROM POP10500
WHERE (POPTYPE = 1 OR
POPTYPE = 3)
GROUP BY POLNENUM, PONUMBER, ITEMNMBR
-------------------
gets all quantities shipped
-------------------
CREATE VIEW dbo.POP_LINE_QTS
AS
SELECT POP10110.ORD, POP10110.ITEMNMBR, POP10110.UOFM,
POP10110.PRMDATE, POP10110.PONUMBER,
POP10110.POLNESTA,
POP10110.QTYORDER - POP10110.QTYCANCE AS QTY,
ISNULL([1RECEIVEDAMTS].QTYSHIP, 0) AS QTYSHIP,
POP10100.BUYERID, SY04200.CMMTTEXT,
POP10110.COMMNTID, POP10100.SHIPMTHD,
POP10110.ITEMDESC, POP10110.PRMSHPDTE,
POP10100.POSTATUS
FROM POP10110 LEFT OUTER JOIN
SY04200 ON
POP10110.COMMNTID = SY04200.COMMNTID LEFT OUTER JOIN
POP10100 ON
POP10110.PONUMBER = POP10100.PONUMBER LEFT OUTER JOIN
[1RECEIVEDAMTS] ON
POP10110.PONUMBER = [1RECEIVEDAMTS].PONUMBER AND
POP10110.ORD = [1RECEIVEDAMTS].POLIN
WHERE (POP10110.POLNESTA < 6) AND
((POP10100.POSTATUS = 2) OR
(POP10100.POSTATUS = 3) OR
(POP10100.POSTATUS = 4))
-------------------
the last where statement is optional, it just filters out closed PO's
-------------------


-----------
and they wonder why they call it Great Pains!

jaz