GLBCTL to PO Module

[iwells]

Hi,

We're having issues with new users deleting batches from the GL before posting and I'm wondering if it's possible to determine what receipts/invoices/debit/credit notes should be associated with a batch?

Is it possible there's a way to associate BATCHID from GLBCTL to anything in the PO module to determine what transactions are missing?

Clearly we need to remove the delete batch button from the screen for all users ...

 

[iwells]

What I'm doing at the moment is searching the HSEQ in GLPOST.DRILLDWNLK to see if it exists, if it hasn't then the item wasn't posted. I was trying to find a more efficient way of doing this

 

[Jay Converse]

Set the batches to automatically post, then they can't be deleted.

 

[DjangMan]

Do you send the document number to the reference or description fields in the GL?

 

[iwells]

Tuba: autoposting isn't an option management or controllers want to use ...

DjangMan: yes we do, its either or depending on which branch we're dealing with ... we've evolved over time so it isn't consistent. How can this be used?

 

[Jay Converse]

Then your management and controllers are being stupid. There is no valid business reason not to autopost subledger batches.

 

[iwells]

The business reason is validation and verification before posting, that's pretty much par for the course across most other billing/accounting systems I've ever dealt with, I do appreciate the response but I think the stupid thing here is this system doesn't have a batch recovery. I've dealt with multiple "ERP" or accounting system before Accpac and all had a batch recovery or "re-post" workaround at the minimum. Additionally I'm blown away that there's no BatchID info in the subledger to show what's been rolled up to the ledger.

 

[Jay Converse]

There is no need for validation and verification if you've set up your account sets properly. You should not be changing subledger batches, that's a violation of SOX audit controls.

 

[ramam1]

You might consider revoking the permission to delete batches, it's not a privilege everyone needs to have. Having said that I don't know that it's possible to manage the right - you can probably suppress the 'delete' button in the GUI.

 

[iwells]

Ramam1: that's the plan going forward as it seems to be the only logical workaround in the system

 

[Jay Converse]

If you remove the delete button, then you can't delete manually entered GL batches. You're making a mountain out of a molehill, and bypassing good audit controls. Set the batches to autopost.

 

[iwells]

Unfortunately Tuba I don't have the luxury of telling people above my pay grade what to do in terms of our business processes.