PJOURNAL not being deleted

(0) Share

Report

Posted on by howieb

I have one company whose PJOURNAL is not being dumped. It has remained with 260K records for a long time. Only realizing this because in searching the web for slowness in GP, one of the points is to look at the PJOURNAL table. I can see in the proc that if the REPORT column is TRUE(or 1) the record will be deleted. These 260K records show REPORT = 0.

What does REPORT = 0 mean? Is it bad? I plan to dump the table with the 260K records, but sort of hesitant until I see why those records show that value.

Thanks

I have the same question (0)

All responses (1)

Answers (0)

Jeff Grant on at

Like (0)

Report

Hello,

As the PJOURNAL content is only needed during the post/print it can be cleared out at any time if it is affecting posting performance. If it is not being cleared out automatically in your environment I would recommend establishing a SQL job to clear it out on a scheduled basis. Regarding the table field definition, as it is not listed in the SDK materials I am not able to locate it, but my assumption is it may be temporarily filled with a '1' during the actual print process.

Best Regards,

Jeff

Dynamics GP Support

Was this reply helpful? Yes No