Solved

Invoice not picked up by GL Distribution batch

  • 31 October 2023
  • 4 replies
  • 45 views
S
Rank
Badge +1

There is one invoice which is not picked up by GL Distribution Batch and doesn’t have GL batch ID for this invoice. We checked other corresponding invoices and we could see that they have been picked up by GL distribution batch and has GL Batch ID.

 

What should be done in this case and what is the reason to why this invoice wasn’t picked by GL Distribution batch.

 

Thanks in advance.

icon

Best answer by Phil Seifert 31 October 2023, 11:25

View original

4 replies

Phil Seifert
Rank
Userlevel 7
Badge +21

Hi Sudeep,

I can think of a few reasons:

  1. The invoice date is not in the period you are running the GL Distribution against.
  2. The invoice is locked and not released.  Perhaps it was picked up in an earlier attempt but failed and was not released from the lock?  Look at the bill locked by column.  Use this query but update the invoice_id appropriately.
select
bill_locked_by,
invoice_stat_id,
gl_batch_id

from invoice_head

where invoice_id = 'invoice_id'
  1. There is corrupted data somewhere that stopped the distribution.

Also take a look at the GL Distribution Logs that are generated.  Usually this is in the Asteashare\<profile>\filestorage\logs folder.  You may see something in the log file.

S
Rank
Badge +1

Hello Phil,

Thanks for your suggestions.

This is what we found in error log file for the invoice number :

Processing “Invoice_id”
-- System is unable to distribute the document “Invoice_id”:
An error occurred during Segment Format retrieval for the Node/Warehouse financial codeIndex 1 is either negative or above rows count. Segment Format Name.

 

Could you kindly let me know what needs to be done in this case.

Phil Seifert
Rank
Userlevel 7
Badge +21

Sounds like data corruption and you should log a support ticket.  This will not be resolved in a Community forum.  Please indicate the invoice number in the ticket and support will see if it is in the DB copy they recently received.

Basically, it appears to be an incorrect configuration for the segment in the GL translation rules.  You also might make sure this customer has all their financial reference data configured correctly in the customer center.

It seems to have a problem with the Node and Warehouse combination related to the invoice somehow and will have to be analyzed by support.

S
Rank
Badge +1

Thanks for your help and quick response.

Reply


Terms & ConditionsCookie settings