accounts not showing up in GL

[sreekuax]

In eb2 two invoice related accounts are not showing up...

Invoice IN519657 and IN519661 have August effective dates on. So they should show up the GL accounts the invoices are hitting in August. One of the accounts hit on both was 21857-000-000. However, when account activity report 25.15.2 is run on 21857-000-000 for August, neither show up. Don’t know what the problem is.

please help..

 

[sreekuax]

can anybody help ?? am i missing to give more info ?

 

[mosfin]

i suspect these invoices were not posted properly
to check if the ar_mstr contains these, write this code
in progress editor:

for each ar_mstr no-lock where ar_nbr="IN519657" or ar_nbr="IN519661" :
  display ar_nbr.
end.

if nothing is displayed, they were not posted properly.

 

[sreekuax]

i suspect these invoices were not posted properly
to check if the ar_mstr contains these, write this code
in progress editor:

for each ar_mstr no-lock where ar_nbr="IN519657" or ar_nbr="IN519661" :
  display ar_nbr.
end.

if nothing is displayed, they were not posted properly.

attached is the results..

 

[sanjus]

here's what I would suggest:
1. Check your ih_inv_date for those 2 invoices
2. What's the selection criteria on the Invoice Posting? Does it post with GL Details?
3. Do you have the output of the Invoice Posting stored in print files?

IIRC, if invoice posting is done in Details, then it stores the Invoice# (or the SO#) in the gltr_desc or gltr_doc. Check those 2 fields as well.

Can u also display the ar_date in the above query and see what's the date?

As always, providing the screen-shots are helpful to understand the issue.

 

[sreekuax]

here's what I would suggest:
1. Check your ih_inv_date for those 2 invoices
2. What's the selection criteria on the Invoice Posting? Does it post with GL Details?
3. Do you have the output of the Invoice Posting stored in print files?

IIRC, if invoice posting is done in Details, then it stores the Invoice# (or the SO#) in the gltr_desc or gltr_doc. Check those 2 fields as well.

Can u also display the ar_date in the above query and see what's the date?

As always, providing the screen-shots are helpful to understand the issue.

Hello Sajus - below are my answers :
1.Check your ih_inv_date for those 2 invoices -
checked and found its 10/08/10

2 and 3rd - I will get back to you soon..

I extracted the gltr_hist data and found that these two invoices are not there in gltr_histView attachment gltr_ext.txt

I checked ar_date as well its same 10/08/10 !!

 

[sanjus]

Looks like your gltr_hist file does not have any records for the date 10/08/10 which means most likely it has not been posted - check your glt_det (Unposted Transaction file).

 

[sreekuax]

Looks like your gltr_hist file does not have any records for the date 10/08/10 which means most likely it has not been posted - check your glt_det (Unposted Transaction file).

I guess its not posted..or posted am confused !!

see screenshots For this account only 2 records exist !!

Now how to proceed !!! ?

 

[sanjus]

The 2 entries listed on your screen shot are Journal Entries entered manually.

Can you kindly display all the contents of the glt_det file (without the where condition)?

Did you get the answer on #3?

 

[sreekuax]

The 2 entries listed on your screen shot are Journal Entries entered manually.

Can you kindly display all the contents of the glt_det file (without the where condition)?

Did you get the answer on #3?

Here it is : View attachment glt_det.txt

no answer yet on #3

 

[sanjus]

Did you ever find out what happened to the missing GL transactions?

 

[sreekuax]

Did you ever find out what happened to the missing GL transactions?

Really sorry bro : I didnt worked for last 3 days as I was not feeling well... I have got an answer from the users !! its interesting

"Looks like they posted these invoices, thought there was a problem, then had Sherry Devito delete the journal entry on the GL side. No one ever rekeyed the entry into the GL (once AR generates an entry from an invoice posting it cannot be redone).

So we now know what happened. The fix is to manually key in a journal entry for these invoices"...