This batch has been marked for posting by another user

  • Follow


Hi GP Experts;

I need help to solve my problem found in GP 10 inventory module, in "Item 
Transaction Entry", a transaction stucked in the entry window, when I select 
this entry from document number magnifier, it pops up a message saying "This 
batch has been marked for posting by another user", and when I go back to 
Inventory Batch, there was one batch with a blank batch ID.

I tried to issue this command in my SQL2005, the result is 
bchsourc = 'IV_Trans'
bachnumb = 
mkdtopst = 0
bchsttus = 0

select bchsourc,bachnumb,mkdtopst,bchsttus from sy00500 where bachnumb = ''

Also, there is another batch called "TEST2' and has nothing transaction 
associated to it but whenever I delete this batch and run Check Link, this 
batch always displays in Inventory Batch again.

when I issue this command in SQL2005, I saw it in my result pane.

SELECT * FROM DYNAMICS..SY00800 

How can I solve these two problems.

Thanks!
-- 
Kane
0
Reply Utf 5/19/2010 9:21:01 PM

have all users log out and run these in SQL:

DELETE DYNAMICS..ACTIVITY 
DELETE DYNAMICS..SY00800 
DELETE DYNAMICS..SY00801 
DELETE TEMPDB..DEX_LOCK 
DELETE TEMPDB..DEX_SESSION 

above should clear out any stuck record out there.

Regards,

Rheiner


"Kane" wrote:

> Hi GP Experts;
> 
> I need help to solve my problem found in GP 10 inventory module, in "Item 
> Transaction Entry", a transaction stucked in the entry window, when I select 
> this entry from document number magnifier, it pops up a message saying "This 
> batch has been marked for posting by another user", and when I go back to 
> Inventory Batch, there was one batch with a blank batch ID.
> 
> I tried to issue this command in my SQL2005, the result is 
> bchsourc = 'IV_Trans'
> bachnumb = 
> mkdtopst = 0
> bchsttus = 0
> 
> select bchsourc,bachnumb,mkdtopst,bchsttus from sy00500 where bachnumb = ''
> 
> Also, there is another batch called "TEST2' and has nothing transaction 
> associated to it but whenever I delete this batch and run Check Link, this 
> batch always displays in Inventory Batch again.
> 
> when I issue this command in SQL2005, I saw it in my result pane.
> 
> SELECT * FROM DYNAMICS..SY00800 
> 
> How can I solve these two problems.
> 
> Thanks!
> -- 
> Kane
0
Reply Utf 5/20/2010 12:26:04 AM


sorry i was rushing when I posted my previous reply.

Anyway, I would still run the scripts to clear out any stuck record. Then 
what you will want to do is just delete the damaged inventory transaction in 
the back end. I would assume though this transaction was not interrupted 
during posting or anything. 

You can look at the following tables:

IV10000	Inventory Transaction Work
IV10001	Inventory Transaction Amounts Work
IV10002	Inventory Serial and Lot Number Work


as for the other batch that gets recreated after running check links, check 
the three tables above and make sure there is no record assigned to the batch 
in those tables.

hope this helps.

Rheiner

"Kane" wrote:

> Hi GP Experts;
> 
> I need help to solve my problem found in GP 10 inventory module, in "Item 
> Transaction Entry", a transaction stucked in the entry window, when I select 
> this entry from document number magnifier, it pops up a message saying "This 
> batch has been marked for posting by another user", and when I go back to 
> Inventory Batch, there was one batch with a blank batch ID.
> 
> I tried to issue this command in my SQL2005, the result is 
> bchsourc = 'IV_Trans'
> bachnumb = 
> mkdtopst = 0
> bchsttus = 0
> 
> select bchsourc,bachnumb,mkdtopst,bchsttus from sy00500 where bachnumb = ''
> 
> Also, there is another batch called "TEST2' and has nothing transaction 
> associated to it but whenever I delete this batch and run Check Link, this 
> batch always displays in Inventory Batch again.
> 
> when I issue this command in SQL2005, I saw it in my result pane.
> 
> SELECT * FROM DYNAMICS..SY00800 
> 
> How can I solve these two problems.
> 
> Thanks!
> -- 
> Kane
0
Reply Utf 5/20/2010 12:35:01 AM

2 Replies
1806 Views

(page loaded in 0.051 seconds)


Reply: