EB.ACCOUNTING

Hi,

Please tell me the syntax of EB.ACCOUNTING function?

CALL EB.ACCOUNTING("Application_name",'******',ENTRIES record,'')

I want to know the Second parameter.

Thanks in Advance,

Revinath G

Hi:

I have reviewed my whole area and I have found the same call for EB.ACCOUNTING, so I think its some kind of label,

CALL EB.ACCOUNTING("AC","SAO",YENTRY.REC,"")

If you can check the next two links it could help a little more:

groups.google.com/group/jBASE/browse_thr...ead/8cc33449ddce3f4b

www.mail-archive.com/jbase@googlegroups.com/msg01551.html

According to Temenos consultants EB.ACCOUNTING is not an GOD IDEA for local applications. If you can develop solutions without it God will bless you, otherwise you can screw the books and get mistmaches in accounting.

Good luck and regards,

Agustín Velázquez Aguirre

Agustin...I like your "God bless perspective" :-)

Revinath,

EB.ACCOUNTING is a Core and complex routine. Despite Temenos' efforts to educate developers and avoid using this routine in local development, lot of developers have used it.

It definitely improves on the performance especially around interfaces/eod processes and helps in handling volumes, however there are plenty of approaches that can help you avoid using it. This helps the project in the long term especially during upgrades etc.

I would suggest you talk to your T24 Seniors/Project Manager in the Project and then decide on the way forward.

As regards your clarification, the Second parameter is supposedly to be the Type of action you wanted to perform with the entries that you have passed to the routine.

Best Wishes,
Shanthi

Thanks Agustin and Shanthi

Hi,

I am a bit late to the party, but my word of advice... STAY AWAY FROM EB.ACCOUNTING. We have it in our local code and it has endless problems ranging from locks to overwritten statements. If you can NOT find another way of achieving what you want to do, i would suggest you call Temenos Helpdesk.

The documentaion is below.

EB.ACCOUNTING(PGM, TYPE, ENTRIES, FORWARD) - An Application interface routine to the accounting system. Invokes the routines to validate & post entries, determines the suspense categories for value dated transactions (value dated accounting) and maintains currency positions.

Arguments:
1. PGM - Calling application either product(eg FT) or routine name eg DATA.CAPTURE.
2. TYPE - Dynamic array, where first field is action type, second field is optional to say "STORE.OVERRIDES" and is used only in FWD.ACCOUNTING, and the third field which is also optional says "UPDATE.ACTIVITY" which will update the ACCT.ACTIVITY file and is only used in the EOD process.
3. ENTRIES - Dynamic array of entries. Format as per STMT.ENTRY but separators are lowered
4. FORWARD - 1/0 flag to indicate entries as FWD.ACCOUNTING entries "CONSOL" indicates that only CONSOL.ENT.TODAY records are to be raised

Hope this helps.

Rgds
Concern

hi... tbis is shiva here...

EB.ACCOUNTING is a good way of using... but instead you can use EB.ACCOUNTING.WRAPPER.... it is same as EB.ACCOUNTING, but it will validates the records accuratly... and good coding standard... especially followed by TEMENOS...

I don't think EB.ACCOUNTING.WRAPPER is supported by R8 or later.... can you confirm.