stored procedure glppostbatch returned the following results:

[Doug]

I am getting this message after posting:

The Stored Procedure glppostbatch returned the following results: DBMS: O
Microsoft Dynamics GP: 20286

I am not sure if should use PSTL KB 898996 missing the triggers.cmp file

or if I should use the new Database maintenance with V10?

I am on V10, SP3

Can someone clarify the steps I need to take?

thanks
--
Doug

[Mariano Gomez]

Doug,

I would use PSTL to recreate the SY00500 table as it would maintain the
existing data. If you use the SQL maintenance option in GP, you will then
have to run check links and reconcile to recreate and update all batches
across all series. You will also need to take into account third party
products.

Best regards,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com

[Childers@discussions.microsoft.com Shaun Childers]

Mariano,

I have the exact same issue as Doug did last year. However, when I was
reading the notes in KB 898996 it said that it applies to versions 8 and 9,
but not 10.0. We are running 10.0 SP3. The triggers.cmp file did not ship
with version 10.0, and so I am not sure if those triggers need to be updated
or not. Do you know if there is an updated version of this script to run
with PSTL?

Thank you.

Shaun Childers

[Patrick [MSFT]]

On v10, you should use the new dbmaintenance.exe utlity to reload
tables/procs/etc.

patrick
dev support

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Shaun Childers" <Shaun Chil...@discussions.microsoft.com> wrote in message
news:3A1A4FCF-DB19-48FF...@microsoft.com...

[nate d]

Would it be best to use the PSTL procedure if you are on GP 2013 we are having the same issue in one of our companies with the exception that it appears that a few of the transactions have posted and some have not how does that effect the fix???

Thanks,
Nathan D