T24 - CATCH ALL suspense account

[Wilson Chikatala]

Dear Friends,

Does any one out there know the systematic way of tracing the route cause of unallocated amounts in the CATCH ALL suspense line? Or if there's a write-up on the same that I can use to troubleshoot such, I would appreciate to have it.

Regards,
Wilson.

[John Watson]

There is a utility called RE.STAT.BAL.REC that takes an inputted GL
line and reports the contents.

The use of this application is pretty self explanatory once you see
the screen - enter the details and verify the record.

You can also append the report line with *D to see details of the
CONSOL KEY used to make up the line.

There is also a table called RE.STAT.LINE.CONT where you can see the
consol keys currently on each report line.

HTH

John.

[Wilson Chikatala]

Hi John!

I have this CATCH ALL line in my GL:
TOTAL FOR 9980000 Other Profit/l|                                                            670,246,803.77

How do I use the RE.STAT.BAL.REC utility to look at the contents of the line.

Please let me know.

--
Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines

IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24

To post, send email to jB...@googlegroups.com
To unsubscribe, send email to jBASE-un...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en

[kanesolve]

Hi,

 

I think what you need to do is to read the Reporting manuals which gives the answer for your question. Anyway, to explain the reason for your problem:

 

-          First of all whenever you are using a new code in any of parameters that constitute the CAL Key you need to clearly define the lines also. 

For example: If you creating a new loan product with a new category say 21057 then there should be a GL line that will take this. Otherwise this CAL key will end up in CATCH all.

 

In case you get a catch all, look at the detailed CRF which will list all the CAL keys that went into CATCH ALL.  From that discuss with your GL people to find where these lines are to be reported. They may be added to an existing line or a new line might have to be created.  Make the necessary modifications to RE.STAT.REP.LINE your catch all should be gone.

 

Thanks and Regards

[Wilson Chikatala]

Thanks for your explanation.

Now I am remaining with one puzzle. I have tried to crack but failed. If I can be helped again I would appreciate.

The CATCH ALL  that is appearing is a difference between the two SAVINGS ACCOUNT  figures. Kindly look at these below:

7,"26/07/2011",G,7782270,,Savings A/C,121879588.2,0,0,,,7782270,1,1,0,0,0,121879588.2
7,"26/07/2011",G,7782270,,Savings A/C,-124460740.69,0,0,,,7782270,1,1,0,0,0,-124460740.69

The difference between the above lines is what is appearing in the CATCH ALL line.

7,"26/07/2011",G,9980000,,Branch Difference,2581152.49,0,0,,,0000000,1,1,0,0,0,2581152.49

For those with experience, please help. What would be your first five suspected causes of the above CATCH ALL ?

Regards,
Wilson.

On Tue, Jun 21, 2011 at 7:17 AM, kanesolve <kane...@gmail.com> wrote:

Hi,

 

I think what you need to do is to read the Reporting manuals which gives the answer for your question. Anyway, to explain the reason for your problem:

 

-          First of all whenever you are using a new code in any of parameters that constitute the CAL Key is