CONSOL.KEY NOT LINK TO ACCOUNT (CRF)

Hello everyone,

I met an issue: transactioned is not updated to ledger account on CRF.

---
As I know the process for a transaction debited/credited to General Ledger Account (in CRF) like this:
1. - Transaction --> auto generate Consol.Key in Entry record.
2. - Consol.Key --> update CONSOLIDATE.PRFT.LOSS (OR ASSET)
3. - Consol.Key inserted to RE.STAT.LINE.CONT

I have problem at 3 stage = The amount is not updated in CRF of the day. Then balanace of the Account is wrong.
- I've checked Rep.line and make sure the account mapping is fine.
- Before the similar transaction worked fine.
----
Please help me explain what link a consol.key to re.stat.line.cont (the table I think data reflected in CRF)
- if not what are possible errors that a consol.key is not linked to ledger account?

Thank you so much.

Hi,

Based on the definition in RE.STAT.REP.LINE, during EOD consolidation keys that best fit the line description are stored in RE.STAT.LINE.CONT.

The contracts (here account) under a CAL key are stored in RE.CONSOL.CONTRACT.

Search in RE.STAT.LINE.CONT, whether the CAL is stored in some other line which best fits it.

After a transaction is authorized, you can check CONSOL.UPDATE.WORK file from which CAL is built during EOD.

Hi thank you,

I've checked all CONT file. This consol.key is not belong any record means not account.


I tried to creat a DC that generate same consol.key and have same error.
So I back to wonder REP.LINE (maybe we are misunderstand something?!)
I will test REP.LINE in some other cases.

CAL key is not even there in catch all?

The missing one is PL.52373... - revenue account.
So don't included in CAL Contract. I found.

I tried to create DC: + Credit revenue --> it generate entry with right consol.key PL.52373...
but still not map to revenue account. it come nowhere.

Hi,

Could be a stupid question , but ... have you ran a COB after you booked transaction ?

no problem, anything is possible. Anyway yes I run COB :)

Seems no one change the system, parameter, map REP.LINE...
when I restore to last year and enter the same entry everything is fine. Still researching the issue :(

Can you see the P/L entry in CATEG.ENTRY . If YES, then what is in field 56 (i.e CONSOL.KEY) ?

Yes CATEG.ENTRY is very fine and right all fields.

OK,

What interface do you use : Classic, Desktop or Browser ?

We use Browser.

After many tests with restore, I think have problem when someone change paramter at the end of last year. I restore last year and run throught many days to new year, everything is fine not like the live version.

I hope have some clue to know what make this wrong.

Look, there shouldn't be any magic ;) ... If you have an entry and entry has a consol key then this key must be in :

- line where you mapped this key by using RE.STAT.REP.LINE or

- miscelaneous line , usually it it's 9999 or something similar.

Check the definition of the miscelaneous line in RE.STAT.REP.LINE ...

I FOUND THE SOLUTION.
Open in EDIT status the REP.LINE for account which is wrong then do nothing but Sumit the account. Then everything is fine.
Crazy system.

DEAR OTONO

i faced the same issue the PL is not generating the consol key's from CONSOLIDATE.PRFT.LOSS
the consol are there and the categ.entry is fine
but the PL showing zero balances for all line and nothing in the catch all 9999
but the GL is working fine and showing a balances
i opend the rep.line for the line which the transaction expected to appear and re commit it but the balance still zero

where is the problem!!! help me

- Get a consol key
- Go to RE.STAT.LINE.CONT and search Live file with PRFT.CONSOL.KEY LK your consol key . It should come back with report line ID.
Check the line definition

Dear DUBLIN

I have searched with my PRFT.CONSOL.KEY in RE.STAT.LINE.CONTAND and no results !!