1. Forum
  3. T24 Technical Discussions
  5. T24 Development & Customization
  7. Help on EB.ACCOUNTING: Format of the "ENTRIES"
× Discuss on Template programming, jBASE programming, Enquiries, No-File enquiry, Enquiry routines, Version, Version routines, Menus, Abbriviations, Creating local reference fields, Fast path enquiries, Creating charts and graphs, Generating Reports, Deal slips, Straight through processing, Multi Company and Multi Book setup, Tabbed screens, Composite Screens, T24 API, etc...

Help on EB.ACCOUNTING: Format of the "ENTRIES"

  • gm.saran
  • Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
11 years 5 months ago - 11 years 5 months ago #15458 by gm.saran
Help on EB.ACCOUNTING: Format of the "ENTRIES" was created by gm.saran
Dear All,

Require some assistance on "EB.ACCOUNTING"

1. What is the format/fields of the 3rd Parameter, ENTRIES
2. How should a STMT.ENTRY/CATEG,ENTRY be formed (the minimum fields that should be populated in an ENTRY)
3. Do we need to pass the ID for each entry? If so, what should be the suggested format?
4. What is the result RETURNED after calling EB.ACCOUNTING?

Thanks
Saravanan
Last edit: 11 years 5 months ago by gm.saran.

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

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
11 years 5 months ago #15461 by jpb
Replied by jpb on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
- ENTRIES are LOWER(STMT.ENTRY) coalesced by FM
- no need to pass the ID, it will be generated
- TEXT variable will be set to "NO" if an error occured

e.g.:
RAISE.ENTRIES:

*---Pass Cr. Entry to Customer Account -----------------
    ENTRIES = ''
    GOSUB BUILD.BASE.ENTRY
    ENTRY<AC.STE.ACCOUNT.NUMBER>   = ...
    ENTRY<AC.STE.NARRATIVE>        = ...
    ENTRY<AC.STE.TRANSACTION.CODE> = ...
    ENTRY<AC.STE.PL.CATEGORY>      = ...
    ENTRY<AC.STE.CURRENCY>         = ...
    ENTRY<AC.STE.AMOUNT.LCY>       = ...
    ENTRY<AC.STE.AMOUNT.FCY>       = ...
    ENTRY<AC.STE.EXCHANGE.RATE>    = ...
    ENTRY<AC.STE.PRODUCT.CATEGORY> = ...
    ENTRY       = LOWER(ENTRY)
    ENTRIES<-1> = ENTRY

*---Pass Dr. Entry to Internal Account ----------------
    CR.FEE.LCY = CR.FEE.LCY * -1
    GOSUB BUILD.BASE.ENTRY
    ENTRY<AC.STE.ACCOUNT.NUMBER>   = ...
    ENTRY<AC.STE.NARRATIVE>        = ...
    ENTRY<AC.STE.TRANSACTION.CODE> = ...
    ENTRY<AC.STE.PL.CATEGORY>      = ...
    ENTRY<AC.STE.CURRENCY>         = ...
    ENTRY<AC.STE.AMOUNT.LCY>       = ...
    ENTRY<AC.STE.AMOUNT.FCY>       = ...
    ENTRY<AC.STE.EXCHANGE.RATE>    = ...
    ENTRY<AC.STE.PRODUCT.CATEGORY> = ...
    ENTRY = LOWER(ENTRY)
    ENTRIES<-1> = ENTRY

    IF ENTRIES THEN
        TYPE = ''
        TYPE<1> = 'SAO'
        TYPE<3> = 'UPDATE.ACTIVITY'
        CALL EB.ACCOUNTING('XX',TYPE,ENTRIES,'')
    END

    RETURN

BUILD.BASE.ENTRY:
    ENTRY = ''
    ENTRY<AC.STE.COMPANY.CODE>    = ID.COMPANY
    ENTRY<AC.STE.ACCOUNT.OFFICER> = ...
    ENTRY<AC.STE.VALUE.DATE>      = TODAY
    ENTRY<AC.STE.OUR.REFERENCE>   = ...
    ENTRY<AC.STE.TRANS.REFERENCE> = ...
    ENTRY<AC.STE.CUSTOMER.ID>     = ...
    ENTRY<AC.STE.BOOKING.DATE>    = ...
    ENTRY<AC.STE.DEPARTMENT.CODE> = ...
    ENTRY<AC.STE.EXPOSURE.DATE>   = ...
    ENTRY<AC.STE.SYSTEM.ID>       = ...
    ENTRY<AC.STE.CURRENCY.MARKET> = ...

    RETURN
The following user(s) said Thank You: gm.saran

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

  • gm.saran
  • Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
11 years 5 months ago - 11 years 5 months ago #15462 by gm.saran
Replied by gm.saran on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
Hi Andreas,

Thanks for the help and the sample code too. Few more queries

1. The sample entries which you have provided will raise STMT.ENTRY, right? Can you send me a sample for a "CATEG.ENTRY"?
2. Other than STMT_ENTRY insert file, any other insert file need to be declared, specifically for EB.ACCOUNTING call?
3. How are the Interbranch and Currency position entries handled in this case? Do we need to raise or system handles them?
4. First Parameter is MODULE, right? What does "XX" refer to?
5. TYPE<> - Can you explain on this various values

Thanks in advance
Saravanan
Last edit: 11 years 5 months ago by gm.saran.

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

  • gm.saran
  • Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
11 years 5 months ago #15465 by gm.saran
Replied by gm.saran on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
Hi Andreas,

Got most of the points clarified googling around and going through the forum. But i found something strange with the entries raised through "EB.ACCOUNTING"; the "INPUTTER" field is not generated. Any idea on this?

Thanks

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

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
11 years 5 months ago #15469 by jpb
Replied by jpb on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
1.
NEW.CATEG.REC = ''
NEW.CATEG.REC<AC.CAT.COMPANY.CODE> = ID.COMPANY
NEW.CATEG.REC<AC.CAT.AMOUNT.LCY> = 
NEW.CATEG.REC<AC.CAT.TRANSACTION.CODE> = 
NEW.CATEG.REC<AC.CAT.NARRATIVE> = 
NEW.CATEG.REC<AC.CAT.PL.CATEGORY> = 
NEW.CATEG.REC<AC.CAT.CUSTOMER.ID> = 
NEW.CATEG.REC<AC.CAT.ACCOUNT.OFFICER> = 
NEW.CATEG.REC<AC.CAT.PRODUCT.CATEGORY> = 
NEW.CATEG.REC<AC.CAT.VALUE.DATE> = 
NEW.CATEG.REC<AC.CAT.CURRENCY> = 
IF CATEG.REC<AC.CAT.AMOUNT.FCY> THEN
    NEW.CATEG.REC<AC.CAT.AMOUNT.FCY> = 
    NEW.CATEG.REC<AC.CAT.EXCHANGE.RATE> = 
END
NEW.CATEG.REC<AC.CAT.POSITION.TYPE> = 
NEW.CATEG.REC<AC.CAT.OUR.REFERENCE> = 
NEW.CATEG.REC<AC.CAT.REVERSAL.MARKER> = 
NEW.CATEG.REC<AC.CAT.EXPOSURE.DATE> = TODAY
NEW.CATEG.REC<AC.CAT.CURRENCY.MARKET> = 
NEW.CATEG.REC<AC.CAT.DEPARTMENT.CODE> = 
NEW.CATEG.REC<AC.CAT.TRANS.REFERENCE> = 
NEW.CATEG.REC<AC.CAT.SYSTEM.ID> = 
NEW.CATEG.REC<AC.CAT.BOOKING.DATE> = TODAY

NEW.CATEG.REC = LOWER(NEW.CATEG.REC)
ENTRIES<-1> = NEW.CATEG.REC

2. NO special inserts needed
3. We don't use interbranch - no idea
4. XX was just an example
5. TYPE - see www.t24all.com/index.php/component/kunen...d-entries.html#14749

INPUTTER - not sure but I think it will be taken from OPERATOR. I use EB.ACCOUNTING out of VERSION-routines and the INPUTTER is always OK
The following user(s) said Thank You: gm.saran

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

  • gm.saran
  • Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
11 years 5 months ago #15470 by gm.saran
Replied by gm.saran on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
Thanks again. The interbranch/currency position entries are automatically created. So that is handled by the system directly based on the existing setup.

I tried a sample routine with Hardcoded values, as MainLine as well as "Subroutine" from a TCServer interface. In both cases, INPUTTER was blank and only one DATE.TIME is updated. We are on R9. May be it requires some T24 update.

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

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
11 years 5 months ago #15472 by jpb
Replied by jpb on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
When the INPUTTER is passed in ENTRIES it should be taken as that,
if the field is empty the standard TNO:"_":OPERATOR is used.

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

  • gm.saran
  • Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
11 years 5 months ago #15479 by gm.saran
Replied by gm.saran on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
I tried updating the OPERATOR variable; tried updating the "AC.STE.INPUTTER". None of them works. Weird!

Working on a way to read the STMT.ID's after EB.ACC call and updating the INPUTTER.

Anyway, thanks a ton, for your help, as always!

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

More
11 years 5 months ago #15542 by kripesh
Replied by kripesh on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
Saran,

Why do you require the Inputter to be updated in the EB.ACCOUNTING... EB Accounting is to update STMT.ENTRY or CATEG.ENTRY or SPEC Entries only. All these files are LIVE files in T24 and will not have any AUDIT fields nor Audit Information..

Not clear as the where you want the INPUTTER information..
Have a great day !

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

  • jpb
  • jpb's Avatar
  • Offline
  • Moderator
  • Moderator
  • retired . . . ¯\_(ツ)_/¯
More
11 years 5 months ago #15548 by jpb
Replied by jpb on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
@KRIPESH:
You are confusing me, I have the audit-fields on all 3 entries files.
How else will you be able to trace who originated an accounting entry when you use it in a local routine ?

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

  • gm.saran
  • Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
11 years 5 months ago #15563 by gm.saran
Replied by gm.saran on topic Help on EB.ACCOUNTING: Format of the "ENTRIES"
@Kripesh
INPUTTER,DATETIME,AUTHORISER fields are always updated in the STMT/CATEG/SPEC entries, whether it is used through T24 core modules or from an external interface like ATM or other systems. So this is the first time, i've noticed that the INPUTTER field is not updated, when i make a call to EB.ACCOUTING.

And lot of our reports, for audit/control purpose, are based on INPUTTERS & AUTHORISERS. So in this case, we wont have the txns listed, if it searched thru "INPUTTER". that's my concern.

===

@Andreas,
I was able to get it worked by reading the entries raised, updating the INPUTTER field and writing it back; but not sure of the overhead of this on the system performance. Planning to raise it with HD. Thanks for your inputs!

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

  1. Forum
  3. T24 Technical Discussions
  5. T24 Development & Customization
  7. Help on EB.ACCOUNTING: Format of the "ENTRIES"
Time to create page: 0.046 seconds