EB.SYSTEM.SUMMARY amount exception

  • Malvarez
  • Topic Author
  • Offline
  • Junior Member
  • Junior Member
More
12 years 7 months ago #11028 by Malvarez
EB.SYSTEM.SUMMARY amount exception was created by Malvarez
Dear all,

If the EB.SYSTEM.SUMMARY show amount exception, I need to know in what category or internal account this amount was register, and identify the especific transaction or transactions.In that report I get this information?

Thanks

Please Log in or Create an account to join the conversation.

More
12 years 7 months ago #11031 by jpb
Replied by jpb on topic Re: EB.SYSTEM.SUMMARY amount exception
Checking RG.TRANS.YEST2 (or its equivalent TXN.JOURNAL.PRINT) is a good point to start, the total debit/credit per application should match...
The following user(s) said Thank You: armin

Please Log in or Create an account to join the conversation.

  • Steph.
  • Visitor
  • Visitor
12 years 7 months ago #11034 by Steph.
Replied by Steph. on topic Re: EB.SYSTEM.SUMMARY amount exception
RG.TRANS.YEST2... is it field somewhere or table jpb?

Please Log in or Create an account to join the conversation.

More
12 years 7 months ago - 12 years 7 months ago #11038 by DUBLIN
Replied by DUBLIN on topic Re: EB.SYSTEM.SUMMARY amount exception
This is a COB's report . Check the HOLD.CONTROL for the report with name as RG.TRANS.YEST2 ;) The total line there shouldn't be unbalanced.

In most cases the difference in EB.SYSTEM.SUMMARY is causing the revaluation error . So , it could be a good idea to check the report's section for revaluation (or by other words RV). The real fun will begin :))
Last edit: 12 years 7 months ago by DUBLIN.
The following user(s) said Thank You: jpb

Please Log in or Create an account to join the conversation.

  • sureshnelakurthi
  • Offline
  • Senior Member
  • Senior Member
More
12 years 7 months ago #11039 by sureshnelakurthi
Replied by sureshnelakurthi on topic Re: EB.SYSTEM.SUMMARY amount exception
Hi,

u can even check RG.TRANS.JOURNAL6 to find the culprit.

Please Log in or Create an account to join the conversation.

More
12 years 6 months ago #11479 by nirmal.mcc
Replied by nirmal.mcc on topic Re: EB.SYSTEM.SUMMARY amount exception
You can check the EB.JOURNAL.SUMMARY in which you can find the amount difference along with application names like RV, AC etc., Based on that we can narrow down using TRANS.JOURNAL of the problematic date and check from where/when the exception amount start accumulated.

Please Log in or Create an account to join the conversation.

  • mkht24all
  • Visitor
  • Visitor
11 years 4 months ago #14289 by mkht24all
Replied by mkht24all on topic Re: EB.SYSTEM.SUMMARY amount exception
What if total debit/credit (application wise) are equal in TXN.JOURNAL but EB.SYSTEM.SUMMARY shows exception and EB.JOURNAL.SUMMARY SHOWS error in RV application

Please Log in or Create an account to join the conversation.

  • Alex Olawale
  • Visitor
  • Visitor
11 years 4 months ago #14402 by Alex Olawale
Replied by Alex Olawale on topic Re: EB.SYSTEM.SUMMARY amount exception
I have a situation where my EB.SYSTEM.SUMMARY (ESS) exception amount cannot be trace to EB.JOURNAL.SUMMARY (EJS)for the application that has caused the difference.

Also, the GL Difference in my CRB is not the same as my ESS amount.

Please Log in or Create an account to join the conversation.

More
11 years 4 months ago #14403 by DUBLIN
Replied by DUBLIN on topic Re: EB.SYSTEM.SUMMARY amount exception
Hi,

Could you prvide more details . E.g. screenshot of the problematic record in EB.SYSTEM.SUMMARY.
Also, is there anything in EB.EOD.ERROR ? What about TRANS.JOURNAL report ?

Please Log in or Create an account to join the conversation.

  • Alex Olawale
  • Visitor
  • Visitor
11 years 4 months ago #14409 by Alex Olawale
Replied by Alex Olawale on topic Re: EB.SYSTEM.SUMMARY amount exception
The EB.SYSTEM.SUMMARY (ESS)exception occurred in various days (990days)in just one branch and providing screenshot of the problematic days will be cumbersome.

Please Log in or Create an account to join the conversation.

Time to create page: 0.091 seconds