We just updated to GP 2013 the other day and are running into an error when doing batches for receivings. According to the sales guy, this is how he can re-create the error
Entering Recievings transaction entry – create batch – saved – auto received – search for PO#
When he hit search, he got the error
*This post is locked for comments
We just had a the same problem but only for one vendor. Using the script provided, "Select * from POP10110 where NONINVEN = 0 AND ITEMNMBR not in (Select ITEMNMBR FROM IV00101)" While looking at the Purchase order line items which were non currently item numbers, the POLNESTA was listed as 5 (closed) for all but one shown as 2 (Released). The POnumber and item number of this PO was the problem. By changing the above query to "Select * from POP10110 where NONINVEN = 0 AND POLNESTA = 2 AND ITEMNMBR not in (Select ITEMNMBR FROM IV00101)". We were able to determine the problem PO number and DEX_ROW_ID of the problem line item.
I then checked with the purchasing agent and found the item was an error on the original PO and he could not change or delete this line item from the existing PO. To correct the problem I ran this query to delete this problem line item from the PO.
"Delete POP10110 where DEX_ROW_ID = xxxx1" Where the xxxx1 is equal to the DEX_ROW_ID from the original Script. After this reconcile the PO the problem is solved.
We opened a case with MS a few months ago so we could get the issue fixed. What you wrote is about what they told is to do.
OK, just fixed this. Run this script to identify items that have an incorrect NONINVEN status..
select * from pop10110 where NONINVEN = 0 and ITEMNMBR not in (select ITEMNMBR from IV00101)
Then update the status to NONINVEN status to 1 and the error will go away...
update pop10110 set noninven = 1 where NONINVEN = 0 and ITEMNMBR not in (select ITEMNMBR from IV00101)
Hi, we have the same problem for one vendor. Did this get resolved?? Thanks Robert
nudge
Some are, some aren't.
It seems to be tied to one specific vendor.
If we create a new PO for this vendor it does not work.
Were these POs created in the prior version? If you create a PO in the 2013 version, does it work ok? I looked but did not see anything that needed to be set in PO line items but who knows, there are a lot of fields and I could have missed one.
That's what our partner suggested...these were his words:
The column referenced is in the IV00101. You could run a select statement for this item number and verify the digit in the IV00101. Mine are set to not use the tolerances and the value is set to 0. Yours might be blank or NULL and GP may not like this. Maybe you will have to run an update statement against all items making this column and the Shortage one as well equal to 0.
We ran a SQL query and got this:
Short story, they’re all zeros.
select
UseQtyOverageTolerance,
UseQtyShortageTolerance,
QtyOverTolerancePercent,
QtyShortTolerancePercent,
count(*)
from iv00101
group by
UseQtyOverageTolerance,
UseQtyShortageTolerance,
QtyOverTolerancePercent,
QtyShortTolerancePercent
UseQtyOverageTolerance UseQtyShortageTolerance QtyOverTolerancePercent QtyShortTolerancePercent COUNT(*)
0 0 0 0 5569
From the WEST (California) company:
UseQtyOverageTolerance UseQtyShortageTolerance QtyOverTolerancePercent QtyShortTolerancePercent COUNT(*)
0 0 0 0 5327
So those columns are all zeros for all our SKUs.
One of the upgrades is the ability to allow tolerances. Perhaps during the upgrade, these fields did not get filled in correctly. Go to Inventory and open the Class IDs one by one. Set the tolerance option (near bottom on left) and allow GP to roll these down to the items.
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
