This batch has been marked for posting by another user.

[KTN]

I got an error message above in GP 8.0 when trying to transfer items through
a batch. I reset the MKDTOPST field in SY00500 from 1 to 0 to disable the
error message and deleted the matching record in IV30200 in order for posting
to run. Is this the method to resolve the issue or not? Am I missing any
other backend tables? If you have experience the similar issue or know how
to troubleshoot this issue, please help. Thanks!

[Frank]

KTN:

You also need to delete the batch from SY0800 in the DYNAMICS
database. Do not delete anything from IV30200 - this is a transaction
history file.

It is really dangerous to do what you are doing at the server level if
you're not absolutely sure what you should do. Please always backup
your database prior to making any chnages to the table data. If you
do anything wrong, you can always restore the backup.

Did the batch post after you made the changes?

Resetting the MKDTOPST field in SY0500 in the company database and
deleting the batch in SY0800 in the DYNAMICS db is the fix for this
error.

Good luck,

Frank Hamelly, MCP-GP
NOVA Solutions LLC
Melbourne, FL

[KTN]

First, I updated MKDTOPST field in SY00500 and run the post. But I got an
error of duplicate records in table IV30200. Therefore, I deleted a matching
record in IV30200 and run the posting successfully. I saved the deleting
record from IV30200 before deleting it. Once the posting ran completely, I
checked the new record and saved record, they matched with the different is
DEX_ROW_ID. It appears to me the update SY00500 and deleting matching
IV30200 works, but I don't know if I need to check any other tables as well.
I did check for SY00800, but found no matching record.

Is there another way to deal with this issue beside going to back-end
tables? I could not find help anywhere on the web. If back-end is the only
option, what other tables should I check. Thanks!

Post by Frank
You also need to delete the batch from SY0800 in the DYNAMICS
database. Do not delete anything from IV30200 - this is a transaction
history file.
It is really dangerous to do what you are doing at the server level if
you're not absolutely sure what you should do. Please always backup
your database prior to making any chnages to the table data. If you
do anything wrong, you can always restore the backup.
Did the batch post after you made the changes?
Resetting the MKDTOPST field in SY0500 in the company database and
deleting the batch in SY0800 in the DYNAMICS db is the fix for this
error.
Good luck,
Frank Hamelly, MCP-GP
NOVA Solutions LLC
Melbourne, FL

[Frank]

There's are two scripts you can run against the tables, but as you can
see, the scripts do the same thing as modifying the tables directly.
These scripts are from the Knowledgebase on either Dynamics GP
Partnersource or Customersource - either of which are a good reference
source.

--------------
1. Run the following script against the company database. Replace XXX
with the batch number or the name of the batch that you are trying to
post.
UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='XXX'

Note The value of BACHNUMB is the same as the value of the Batch ID
window in Great Plains.

2. View the contents of the SY00800 table that is located in the
DYNAMICS database to determine the value of the DEX_ROW_ID field for
the batch that you are trying to unmark. You can view the contents of
this table by running the following script.
SELECT * FROM DYNAMICS..SY00800

Note If no results are returned, go to step 4.

3. Run the following delete script that is based on the results that
you received in step 3. Replace XXX with the DEX_ROW_ID value of the
batch that you are trying to unmark.
DELETE DYNAMICS..SY00800 where DEX_ROW_ID= 'XXX'


4. Verify the accuracy of the transactions.
5. Verify that you can edit and post the batches.
--------------------

Hope this helps,

Frank Hamelly, MCP-GP
NOVA Solutions LLC
Melbourne, FL

[KTN]

Step 1 ran succesfully. Step 2 produced no matching record. For steps 4 &
5, I was able to edit the batch. But when I run the posting, I got an error
message:

A Save operation on table 'IV_TRX_HIST_HDR' has created a duplicate key.

After closing the pop-up error message window, I checked table SY00500 and
the record is no longer there. It is the same thing as using GP tool in
Inventory Batch Entry screen. Apparently, the record is deleted or somehow
no long there. Do you know why this happens?

BUT..........if I restored the database and ran steps 1 & 2 as you suggested
along with removing a matching record in IV30200, then the duplicate error
message is not showing and the posting ran successfully.

I am clueless of what to do next at this time. If I removed the matching
record in IV30200, then it appears to fix the problem but do not know if it
is the right thing to do. If I do step 1,2,4, and 5 and then posting, then
I got duplicate error in IV30200. Any suggestion to where to go next would
be helpful. I looked on CustomerSource but they don't have much helpful
info. Thanks!

Post by Frank
There's are two scripts you can run against the tables, but as you can
see, the scripts do the same thing as modifying the tables directly.
These scripts are from the Knowledgebase on either Dynamics GP
Partnersource or Customersource - either of which are a good reference
source.
--------------
1. Run the following script against the company database. Replace XXX
with the batch number or the name of the batch that you are trying to
post.
UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='XXX'
Note The value of BACHNUMB is the same as the value of the Batch ID
window in Great Plains.
2. View the contents of the SY00800 table that is located in the
DYNAMICS database to determine the value of the DEX_ROW_ID field for
the batch that you are trying to unmark. You can view the contents of
this table by running the following script.
SELECT * FROM DYNAMICS..SY00800
Note If no results are returned, go to step 4.
3. Run the following delete script that is based on the results that
you received in step 3. Replace XXX with the DEX_ROW_ID value of the
batch that you are trying to unmark.
DELETE DYNAMICS..SY00800 where DEX_ROW_ID= 'XXX'
4. Verify the accuracy of the transactions.
5. Verify that you can edit and post the batches.
--------------------
Hope this helps,
Frank Hamelly, MCP-GP
NOVA Solutions LLC
Melbourne, FL

[Frank]

It's pretty tough to troubleshoot this without seeing the tables KTN.
I'm not sure what may have occurred. It sounds like you may have a
stranded record out there that running Checklinks should fix.

I would restore the backup to a test database, run Checklinks on the
Inventory tables, run the scripts, and then see if the batch posts
properly.

Good luck,

Frank Hamelly, MCP-GP
NOVA Solutions LLC
Melbourne, FL