T24: FUNDS.TRANSFER with no STMT.NOS
2,232 views
Skip to first unread message
Despina
May 12, 2010, 11:06:10 AM5/12/10
to jBASE
Hi all,
I'm having the problem below:
1. On a TELLER 0 authorisation version, at AUTHORISATION level,
I have a VAR routine that creates FUNDS.TRANSFER that debits customer
a/c and credits PL category.
2. On reversal of TELLER record through same version, at AUTHORISATION
level again,
I want the FUNDS.TRANSFER created during Input function to be
'undone'.
So I have another VAR routine that creates FUNDS.TRANSFER with exactly
the 'reverse' entry i.e. debit
PL category and credit customer a/c. What goes wrong is that the
FUNDS.TRANSFER is created,
I can read it when listing FT table, but it is without STMT.NOS.
Has anyone else encountered the same problem?
Thanks a lot,
Despina
--
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
I'm having the problem below:
1. On a TELLER 0 authorisation version, at AUTHORISATION level,
I have a VAR routine that creates FUNDS.TRANSFER that debits customer
a/c and credits PL category.
2. On reversal of TELLER record through same version, at AUTHORISATION
level again,
I want the FUNDS.TRANSFER created during Input function to be
'undone'.
So I have another VAR routine that creates FUNDS.TRANSFER with exactly
the 'reverse' entry i.e. debit
PL category and credit customer a/c. What goes wrong is that the
FUNDS.TRANSFER is created,
I can read it when listing FT table, but it is without STMT.NOS.
Has anyone else encountered the same problem?
Thanks a lot,
Despina
--
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
Srinivas
May 12, 2010, 2:46:40 PM5/12/10
to jb...@googlegroups.com
Hi,
Instead of creating the new funds transfer record , reverse the already created FT .
--
Regards,
SrinivasYadav. G
Mobile No: 00966 - 540625165
Regards,
SrinivasYadav. G
Mobile No: 00966 - 540625165
Mohankumar Balasubramaniam
May 13, 2010, 1:16:18 AM5/13/10
to jb...@googlegroups.com
Hi,
The best way is to use EB.ACCOUNTING to raise entries instead of using FT.
FT have lot of validations, so it will also consume execution time when teller processing also increases storage spaces.
You can use the types "VAL"( For Input entries in INAU), "AUT"(For Authorising entries),
and "REV" for reversing already raised entries for EB.ACCOUNTING. Please note set ID.NEW as different when raising entries.
If you need example code to raise entries using EB.ACCOUNTING plz reply, so that i will send to you.
or still if you want to use FT, reverse already raised FT, set HIS.REVERSAL field in FT.TXN.TYPE.CONDITION to Y and reverse already raised FT using OFS.
Regards,
Mohankumar B
VK
May 13, 2010, 10:15:35 AM5/13/10
to jBASE
Hi,
EB.ACCOUNTING is strongly not recommended for local developments... in
doubt better ask Temenos helpdesk.
BTW, what is "VAR" routine?
and how you create FT?
VK
On May 13, 9:16 am, Mohankumar Balasubramaniam
> For more options, visit this group athttp://groups.google.com/group/jBASE?hl=en
EB.ACCOUNTING is strongly not recommended for local developments... in
doubt better ask Temenos helpdesk.
BTW, what is "VAR" routine?
and how you create FT?
VK
On May 13, 9:16 am, Mohankumar Balasubramaniam
<mohankumarm...@gmail.com> wrote:
> Hi,
>
> The best way is to use EB.ACCOUNTING to raise entries instead of using FT.
> FT have lot of validations, so it will also consume execution time when
> teller processing also increases storage spaces.
> You can use the types "VAL"( For Input entries in INAU), "AUT"(For
> Authorising entries),
> and "REV" for reversing already raised entries for EB.ACCOUNTING. Please
> note set ID.NEW as different when raising entries.
> If you need example code to raise entries using EB.ACCOUNTING plz reply, so
> that i will send to you.
>
> or still if you want to use FT, reverse already raised FT, set HIS.REVERSAL
> field in FT.TXN.TYPE.CONDITION to Y and reverse already raised FT using OFS.
>
> Regards,
> Mohankumar B
>
> Hi,
>
> The best way is to use EB.ACCOUNTING to raise entries instead of using FT.
> FT have lot of validations, so it will also consume execution time when
> teller processing also increases storage spaces.
> You can use the types "VAL"( For Input entries in INAU), "AUT"(For
> Authorising entries),
> and "REV" for reversing already raised entries for EB.ACCOUNTING. Please
> note set ID.NEW as different when raising entries.
> If you need example code to raise entries using EB.ACCOUNTING plz reply, so
> that i will send to you.
>
> or still if you want to use FT, reverse already raised FT, set HIS.REVERSAL
> field in FT.TXN.TYPE.CONDITION to Y and reverse already raised FT using OFS.
>
> Regards,
> Mohankumar B
>
> On Thu, May 13, 2010 at 12:16 AM, Srinivas <srinivasyada...@gmail.com>wrote:
>
>
>
> > Hi,
>
> > Instead of creating the new funds transfer record , reverse the already
> > created FT .
>
>
>
>
> > Hi,
>
> > Instead of creating the new funds transfer record , reverse the already
> > created FT .
>
Despina Hapeshi
May 13, 2010, 10:33:25 AM5/13/10
to jb...@googlegroups.com
Can you please send me an example of using EB.ACCOUNTING?
(for creating - input and reversing entries?)
Thanks a lot Mohan
Date: Thu, 13 May 2010 10:46:18 +0530
Subject: Re: T24: FUNDS.TRANSFER with no STMT.NOS
From: mohanku...@gmail.com
To: jb...@googlegroups.com
Hotmail: Powerful Free email with security by Microsoft. Get it now.
Mukanya
May 14, 2010, 1:38:35 AM5/14/10
to jBASE
Stay away from EB.ACCOUNTING....
On May 13, 4:33 pm, Despina Hapeshi <despinahape...@hotmail.com>
wrote:
> Hotmail: Powerful Free email with security by Microsoft.https://signup.live.com/signup.aspx?id=60969
On May 13, 4:33 pm, Despina Hapeshi <despinahape...@hotmail.com>
wrote:
> Can you please send me an example of using EB.ACCOUNTING?
>
> (for creating - input and reversing entries?)
>
> Thanks a lot Mohan
>
>
> (for creating - input and reversing entries?)
>
> Thanks a lot Mohan
>
> Date: Thu, 13 May 2010 10:46:18 +0530
> Subject: Re: T24: FUNDS.TRANSFER with no STMT.NOS
> From: mohankumarm...@gmail.com
> Subject: Re: T24: FUNDS.TRANSFER with no STMT.NOS
> To: jb...@googlegroups.com
>
> Hi,
>
> The best way is to use EB.ACCOUNTING to raise entries instead of using FT.
> FT have lot of validations, so it will also consume execution time when teller processing also increases storage spaces.
> You can use the types "VAL"( For Input entries in INAU), "AUT"(For Authorising entries),
> and "REV" for reversing already raised entries for EB.ACCOUNTING. Please note set ID.NEW as different when raising entries.
> If you need example code to raise entries using EB.ACCOUNTING plz reply, so that i will send to you.
>
> or still if you want to use FT, reverse already raised FT, set HIS.REVERSAL field in FT.TXN.TYPE.CONDITION to Y and reverse already raised FT using OFS.
>
> Regards,
> Mohankumar B
>
>
> Hi,
>
> The best way is to use EB.ACCOUNTING to raise entries instead of using FT.
> FT have lot of validations, so it will also consume execution time when teller processing also increases storage spaces.
> You can use the types "VAL"( For Input entries in INAU), "AUT"(For Authorising entries),
> and "REV" for reversing already raised entries for EB.ACCOUNTING. Please note set ID.NEW as different when raising entries.
> If you need example code to raise entries using EB.ACCOUNTING plz reply, so that i will send to you.
>
> or still if you want to use FT, reverse already raised FT, set HIS.REVERSAL field in FT.TXN.TYPE.CONDITION to Y and reverse already raised FT using OFS.
>
> Regards,
> Mohankumar B
>
> On Thu, May 13, 2010 at 12:16 AM, Srinivas <srinivasyada...@gmail.com> wrote:
>
> Hi,
>
> Instead of creating the new funds transfer record , reverse the already created FT .
>
>
> Hi,
>
> Instead of creating the new funds transfer record , reverse the already created FT .
>
> On 12 May 2010 18:06, Despina <despinahape...@hotmail.com> wrote:
>
> Hi all,
>
> I'm having the problem below:
>
> 1. On a TELLER 0 authorisation version, at AUTHORISATION level,
> I have a VAR routine that creates FUNDS.TRANSFER that debits customer
> a/c and credits PL category.
>
> 2. On reversal of TELLER record through same version, at AUTHORISATION
> level again,
> I want the FUNDS.TRANSFER created during Input function to be
> 'undone'.
> So I have another VAR routine that creates FUNDS.TRANSFER with exactly
> the 'reverse' entry i.e. debit
> PL category and credit customer a/c. What goes wrong is that the
> FUNDS.TRANSFER is created,
> I can read it when listing FT table, but it is without STMT.NOS.
>
> Has anyone else encountered the same problem?
>
> Thanks a lot,
> Despina
>
> --
> 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 athttp://groups.google.com/group/jBASE?hl=en
>
> Hi all,
>
> I'm having the problem below:
>
> 1. On a TELLER 0 authorisation version, at AUTHORISATION level,
> I have a VAR routine that creates FUNDS.TRANSFER that debits customer
> a/c and credits PL category.
>
> 2. On reversal of TELLER record through same version, at AUTHORISATION
> level again,
> I want the FUNDS.TRANSFER created during Input function to be
> 'undone'.
> So I have another VAR routine that creates FUNDS.TRANSFER with exactly
> the 'reverse' entry i.e. debit
> PL category and credit customer a/c. What goes wrong is that the
> FUNDS.TRANSFER is created,
> I can read it when listing FT table, but it is without STMT.NOS.
>
> Has anyone else encountered the same problem?
>
> Thanks a lot,
> Despina
>
> --
> 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
>
> --
> Regards,
>
> SrinivasYadav. G
> Mobile No: 00966 - 540625165
>
> --
>
> 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 athttp://groups.google.com/group/jBASE?hl=en
> --
> Regards,
>
> SrinivasYadav. G
> Mobile No: 00966 - 540625165
>
> --
>
> 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
>
> --
> 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 athttp://groups.google.com/group/jBASE?hl=en
>
> _________________________________________________________________
> --
> 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 athttp://groups.google.com/group/jBASE?hl=en
>
> Hotmail: Powerful Free email with security by Microsoft.https://signup.live.com/signup.aspx?id=60969
>
> --
> 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 athttp://groups.google.com/group/jBASE?hl=en
> --
> 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
Mohankumar Balasubramaniam
May 14, 2010, 3:34:28 AM5/14/10
to jb...@googlegroups.com
Hi Despina,
Please find below code for sample of EB.ACCOUNTING.
RAISE.ENTRY:
*-----------*
* Form the stmt entry array
*-----------*
* Form the stmt entry array
LOCKER.ENTRY<AC.STE.ACCOUNT.NUMBER> = ACCOUNT.ID
LOCKER.ENTRY<AC.STE.CUSTOMER.ID> = CUSTOMER.ID
LOCKER.ENTRY<AC.STE.PRODUCT.CATEGORY> = ACCT.CATEGORY
LOCKER.ENTRY<AC.STE.CURRENCY.MARKET> = CCY.MKT
LOCKER.ENTRY<AC.STE.COMPANY.CODE> = ID.COMPANY
LOCKER.ENTRY<AC.STE.SYSTEM.ID> = 'FT'
LOCKER.ENTRY<AC.STE.TRANS.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.BOOKING.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.REVERSAL.MARKER> = ''
LOCKER.ENTRY<AC.STE.POSITION.TYPE> = ACCT.POSITION.TYPE
LOCKER.ENTRY<AC.STE.PL.CATEGORY> = ''
LOCKER.ENTRY<AC.STE.DEPARTMENT.CODE> = DEPT.CODE
LOCKER.ENTRY<AC.STE.OUR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.THEIR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.VALUE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.EXPOSURE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.CURRENCY> = ACCT.CURR
LOCKER.ENTRY<AC.STE.AMOUNT.LCY> = -1 * AMOUNT.LCY
IF AMOUNT.FCY THEN
LOCKER.ENTRY<AC.STE.AMOUNT.FCY> = -1 * AMOUNT.FCY
END
LOCKER.ENTRY<AC.STE.ACCOUNT.OFFICER> = ACCT.OFFICER
LOCKER.ENTRY<AC.STE.TRANSACTION.CODE> = DR.TRANS.CODE
LOCKER.ENTRY = LOWER(LOCKER.ENTRY)
TEMP.ENTRY<-1> = LOCKER.ENTRY
LOCKER.ENTRY<AC.STE.CUSTOMER.ID> = CUSTOMER.ID
LOCKER.ENTRY<AC.STE.PRODUCT.CATEGORY> = ACCT.CATEGORY
LOCKER.ENTRY<AC.STE.CURRENCY.MARKET> = CCY.MKT
LOCKER.ENTRY<AC.STE.COMPANY.CODE> = ID.COMPANY
LOCKER.ENTRY<AC.STE.SYSTEM.ID> = 'FT'
LOCKER.ENTRY<AC.STE.TRANS.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.BOOKING.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.REVERSAL.MARKER> = ''
LOCKER.ENTRY<AC.STE.POSITION.TYPE> = ACCT.POSITION.TYPE
LOCKER.ENTRY<AC.STE.PL.CATEGORY> = ''
LOCKER.ENTRY<AC.STE.DEPARTMENT.CODE> = DEPT.CODE
LOCKER.ENTRY<AC.STE.OUR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.THEIR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.VALUE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.EXPOSURE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.CURRENCY> = ACCT.CURR
LOCKER.ENTRY<AC.STE.AMOUNT.LCY> = -1 * AMOUNT.LCY
IF AMOUNT.FCY THEN
LOCKER.ENTRY<AC.STE.AMOUNT.FCY> = -1 * AMOUNT.FCY
END
LOCKER.ENTRY<AC.STE.ACCOUNT.OFFICER> = ACCT.OFFICER
LOCKER.ENTRY<AC.STE.TRANSACTION.CODE> = DR.TRANS.CODE
LOCKER.ENTRY = LOWER(LOCKER.ENTRY)
TEMP.ENTRY<-1> = LOCKER.ENTRY
* Form the Categ entry array
LOCKER.ENTRY = ''
LOCKER.ENTRY<AC.STE.CURRENCY.MARKET> = CCY.MKT
LOCKER.ENTRY<AC.STE.COMPANY.CODE> = ID.COMPANY
LOCKER.ENTRY<AC.STE.SYSTEM.ID> = 'FT'
LOCKER.ENTRY<AC.STE.TRANS.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.BOOKING.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.REVERSAL.MARKER> = ''
LOCKER.ENTRY<AC.STE.POSITION.TYPE> = ACCT.POSITION.TYPE
LOCKER.ENTRY<AC.STE.CUSTOMER.ID> = CUSTOMER.ID
LOCKER.ENTRY<AC.STE.PL.CATEGORY> = PL.CATEG
LOCKER.ENTRY<AC.STE.ACCOUNT.OFFICER> = ACCT.OFFICER
LOCKER.ENTRY<AC.STE.PRODUCT.CATEGORY> = ACCT.CATEGORY
LOCKER.ENTRY<AC.STE.DEPARTMENT.CODE> = DEPT.CODE
LOCKER.ENTRY<AC.STE.OUR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.THEIR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.VALUE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.EXPOSURE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.CURRENCY> = LCCY
LOCKER.ENTRY<AC.STE.AMOUNT.LCY> = AMOUNT.LCY
IF AMOUNT.FCY THEN
LOCKER.ENTRY<AC.STE.AMOUNT.FCY> = AMOUNT.FCY
END
LOCKER.ENTRY<AC.STE.TRANSACTION.CODE> = CR.TRANS.CODE
LOCKER.ENTRY = LOWER(LOCKER.ENTRY)
TEMP.ENTRY<-1> = LOCKER.ENTRY
LOCKER.ENTRY = ''
LOCKER.ENTRY<AC.STE.CURRENCY.MARKET> = CCY.MKT
LOCKER.ENTRY<AC.STE.COMPANY.CODE> = ID.COMPANY
LOCKER.ENTRY<AC.STE.SYSTEM.ID> = 'FT'
LOCKER.ENTRY<AC.STE.TRANS.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.BOOKING.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.REVERSAL.MARKER> = ''
LOCKER.ENTRY<AC.STE.POSITION.TYPE> = ACCT.POSITION.TYPE
LOCKER.ENTRY<AC.STE.CUSTOMER.ID> = CUSTOMER.ID
LOCKER.ENTRY<AC.STE.PL.CATEGORY> = PL.CATEG
LOCKER.ENTRY<AC.STE.ACCOUNT.OFFICER> = ACCT.OFFICER
LOCKER.ENTRY<AC.STE.PRODUCT.CATEGORY> = ACCT.CATEGORY
LOCKER.ENTRY<AC.STE.DEPARTMENT.CODE> = DEPT.CODE
LOCKER.ENTRY<AC.STE.OUR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.THEIR.REFERENCE> = TRANS.REF
LOCKER.ENTRY<AC.STE.VALUE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.EXPOSURE.DATE> = BOOK.DATE
LOCKER.ENTRY<AC.STE.CURRENCY> = LCCY
LOCKER.ENTRY<AC.STE.AMOUNT.LCY> = AMOUNT.LCY
IF AMOUNT.FCY THEN
LOCKER.ENTRY<AC.STE.AMOUNT.FCY> = AMOUNT.FCY
END
LOCKER.ENTRY<AC.STE.TRANSACTION.CODE> = CR.TRANS.CODE
LOCKER.ENTRY = LOWER(LOCKER.ENTRY)
TEMP.ENTRY<-1> = LOCKER.ENTRY
LOCKER.ENTRY = ''
LOCKER.ENTRY = TEMP.ENTRY
CALL EB.ACCOUNTING('EB',"SAO",LOCKER.ENTRY,'0')
CALL EB.ACCOUNTING('EB',"SAO",LOCKER.ENTRY,'0')
RETURN
REVERSE.ORIGINAL.ENTRIES:
*-----------------------*
FT.TAPES.STMT.NO = R.TELLER<TT.TE.STMT.NO>
V = FT.AUDIT.DATE.TIME
APPLICATION = "FUNDS.TRANSFER"
R.NEW(FT.STMT.NOS) = FT.TAPES.STMT.NO
CALL EB.ACCOUNTING('FT','REV',"",'')
CALL EB.ACCOUNTING('FT','AUT',"",'')
RETURN
*-----------------------*
FT.TAPES.STMT.NO = R.TELLER<TT.TE.STMT.NO>
V = FT.AUDIT.DATE.TIME
APPLICATION = "FUNDS.TRANSFER"
R.NEW(FT.STMT.NOS) = FT.TAPES.STMT.NO
CALL EB.ACCOUNTING('FT','REV',"",'')
CALL EB.ACCOUNTING('FT','AUT',"",'')
RETURN
The argument descriptions for EB.ACCOUNTING is been given below for your feature reference, in case if you want to use it for any other developments.
EB.ACCOUNTING(PGM, TYPE, ENTRIES, FORWARD)
*
*************************************************************************
*
*** <region name= Modification log>
***
* 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
* ---------
* PGM Calling application either product, FT, or routine
* name eg DATA.CAPTURE.
*
* 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.
*
* Action Type can be:
*
* CHG Change previous entries
* DEL Delete previous entries
* VAL Input entries
* VALAUT Input & authories entries
* REV Reverse authorised entries
* SAO Automatically overridden when an override conditions
* SNP Return control to calling application when an override
* SSS Customer account entries suspensed when an override
* For More details for SAO,SSS & SNP see EOD.ACCOUNTING routine.
* RSAO Reversal - store overrides
* SNP Suspense on override
* ADD Input entries
* AUT Authorise entries
* ADD.AUT Input & authorise entries
*
* ENTRIES Dynamic array of entries.
* Format as per STMT.ENTRY but separators are lowered
*
* FORWARD 1/0 flag to indicate entries a FWD.ACCOUNTING entries
* "CONSOL" indicates that only CONSOL.ENT.TODAY records
* are to be raised
*
*************************************************************************
*
*** <region name= Modification log>
***
* 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
* ---------
* PGM Calling application either product, FT, or routine
* name eg DATA.CAPTURE.
*
* 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.
*
* Action Type can be:
*
* CHG Change previous entries
* DEL Delete previous entries
* VAL Input entries
* VALAUT Input & authories entries
* REV Reverse authorised entries
* SAO Automatically overridden when an override conditions
* SNP Return control to calling application when an override
* SSS Customer account entries suspensed when an override
* For More details for SAO,SSS & SNP see EOD.ACCOUNTING routine.
* RSAO Reversal - store overrides
* SNP Suspense on override
* ADD Input entries
* AUT Authorise entries
* ADD.AUT Input & authorise entries
*
* ENTRIES Dynamic array of entries.
* Format as per STMT.ENTRY but separators are lowered
*
* FORWARD 1/0 flag to indicate entries a FWD.ACCOUNTING entries
* "CONSOL" indicates that only CONSOL.ENT.TODAY records
* are to be raised
Regards,
Mohan
Mohankumar Balasubramaniam
May 14, 2010, 3:26:37 AM5/14/10
to jb...@googlegroups.com
Hi VK,
If you want to raise charges, its better to use EB.ACCOUNTING, and it reduces execution time, and reduces disk I/O as well.
as you know FT has lots of validations, and it require database storage as well. Also many developments has EB.ACCOUNTING only for charges, and we have used EB.ACCOUNTING for many clients in Temenos. But till now I didnt get any objections for that.
Can you provide me a single reason that why we should not use EB.ACCOUNTING?
Please do mind if you say mistake on anything, there should be a reason for that. You need to provide reason for that along with
your words of rejection.
Regards,
Mohan
Srinivas
May 14, 2010, 6:34:11 AM5/14/10
to jb...@googlegroups.com
Hi VK ,
May i know under what situations EB.ACCOUNTING is recommended to use .
Jane Hong
May 15, 2010, 6:03:17 AM5/15/10
to jb...@googlegroups.com
With no EB.ACCOUNTING makes life uneasy :-)
On Fri, May 14, 2010 at 7:41 PM, Takura Mambonde <taku...@gmail.com> wrote:
EB.ACCOUNTING should be used with great caution. You may create unnecessary GL Differences or Mismatches.
Reply all
Reply to author
Forward
Message has been deleted
0 new messages