× Discuss about OFS, Temenos Connectors, Various OFS modes, OFS with Versions, OFS performance, Logging, EB.PHANTOM, OFS.SOURCE etc…

OFS

  • vijay_baskar
  • Topic Author
  • Offline
  • New Member
  • New Member
More
19 years 1 month ago #430 by vijay_baskar
OFS was created by vijay_baskar
Hi All,

For OFS I wrote a routine for updating a field for a template I created, accounting entries also need to be raised whenever phantom is runned. But only the fields in templates are getting updated and accounting entries is not getting raised. Is it possible to do this? I have attached my routine in field 27(IN.DIR.RTN) of OFS.SOURCE.

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

More
19 years 1 month ago #431 by ironmaiden
Replied by ironmaiden on topic OFS
Hi Vijay,

here are a few points...,

a. Make sure all the argument going into the EB.ACCOUNTING are correct.
b. Did u call the JOURNAL.UPDATE after calling EB.ACCOUNTING, this is to ensure that your transaction is updated into the SYSTEM and not to the cache.
c. Try running the phantom in interactive mode and put a DEBUG before your accounting program and check the values...
_________________
NJOY LIFE TO THE FULLEST

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

More
19 years 2 weeks ago #432 by ashok
Replied by ashok on topic OFS
Ofcourse that is possible.

Try attaching that routine in EB.PHANTOM 19 Filed RUN.ROUTINE if you used Fantom process. and check the account parameter as well as mandatory values (Company, TXN CODe etc)


* Debit accounting entry
Y.CUST.NO = R.DR.ACCOUNT<AC.CUSTOMER>
Y.ACCOUNT.NO = Y.DR.ACCT
Y.AMOUNT = Y.AMT * (-1)
Y.TXN.CODE = Y.DR.TXN.CODE
Y.CATEGORY = R.DR.ACCOUNT<AC.CATEGORY>
Y.ACCOUNT.CURRENCY = R.DR.ACCOUNT<AC.CURRENCY>
Y.ACCOUNT.OFFICER = R.DR.ACCOUNT<AC.ACCOUNT.OFFICER>
Y.CO.CODE = R.DR.ACCOUNT<AC.CO.CODE>
GOSUB PRODUCE.ENTRIES

* Credit accounting entry
Y.CUST.NO = R.CR.ACCOUNT<AC.CUSTOMER>
Y.ACCOUNT.NO = Y.CR.ACCT
Y.AMOUNT = Y.AMT
Y.TXN.CODE = Y.CR.TXN.CODE
Y.CATEGORY = R.CR.ACCOUNT<AC.CATEGORY>
Y.ACCOUNT.CURRENCY = R.CR.ACCOUNT<AC.CURRENCY>
Y.ACCOUNT.OFFICER = R.CR.ACCOUNT<AC.ACCOUNT.OFFICER>
Y.CO.CODE = R.CR.ACCOUNT<AC.CO.CODE>
GOSUB PRODUCE.ENTRIES

TYPE = ACCTING.MODE
***SAO etc, (When you want to raise entries check with user manual)
CALL EB.ACCOUNTING(APPLICATION,TYPE,MULTI.ENTRIES,'')
CALL JOURNAL.UPDATE('PROCESS')

*****
BUILD.BASE.ENTRY:
*
*build base STMT.ENTRY entry fields
ENTRY = ''
ENTRY<AC.STE.ACCOUNT.NUMBER> = ''
ENTRY<AC.STE.COMPANY.CODE> = Y.CO.CODE
ENTRY<AC.STE.AMOUNT.LCY> = 0
ENTRY<AC.STE.TRANSACTION.CODE> = Y.TXN.CODE
ENTRY<AC.STE.THEIR.REFERENCE> = 'SYSTEM'
ENTRY<AC.STE.NARRATIVE> = ''
.
.
.
.

RETURN
*
*
END
****
_________________
Ashok Pandey
Mayor Street
Dublin
Ireland

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

More
18 years 11 months ago #433 by shenbasp2002
Replied by shenbasp2002 on topic OFS
Hi Vijay,

Just few suggestions...

1. If you are updating the ACCOUNTING entries in BATCH, you can use 'SAO'. Otherwise, you can use 'VALAUT'.

2. Moreover, Instead of attaching the routine as the IN.ROUTINE...
If you have seperate routine for updating the accounting entry (I hope you are updating the template through a version....), Just try to attach your routine as the AUTH.ROUTINE (where the version you have created for updating the details in the template is with '0' authoriser.) instead of using the phantom concept.

When your template is having huge volume of data that needs to be updated, Authorisation routine will execute faster than the phantom routine. It will definitely increase the performance.

Regards,
Shenba

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

Time to create page: 0.028 seconds