Hi,
You ca try another technique to resolve this issue. You can create 2
LIVE FILES for your purpose. 1st LIVE File can contain all the FT txn IDS
for a particular TXN TYPE on a particulate date an its record ID should be
like *OT-20101103. *While the second LIVE FILE contains the actual FT txn
data with FT txn ID as their ID.
By this you have to select the records of 1st LIVE file and then by
reading FT Ids from those records, you can fetch the FT data from the 2nd
LIVE FILE.
Regards,
Imran Khan
On Fri, Nov 12, 2010 at 5:09 PM, VK <[email protected]> wrote:
> Hi,
>
> if ID of your local app is the same as in FT it won't help you much.
> Temenos includes FT history into the list of files that they
> discourage to do SELECT on.
>
> Try to create a compound ID like: BH0010001.OT01.FT10111QWERT
>
> VK
> P.S. I know what lakh is :)))
>
>
> On 11 нов, 19:51, "Jim Idle" <[email protected]> wrote:
> > Outside India, I doubt that too many people know what a lakh is! J
> >
> > However, why are you using SSELECT here? It will be a lot slower than
> SELECT
> > I suspect, especially when you come to use the list afterwards. I think
> that
> > you have just created a huge query without any indexes and lots of
> > conditions and it is going to take a long time to do that. Create some
> > indexes to help this. Maybe on CO.CODE for instance.
> >
> > Jim
> >
> > From: [email protected] [mailto:[email protected]] On Behalf
> Of
> > Ramkumar Sreeni
> > Sent: Thursday, November 11, 2010 3:46 AM
> > To: [email protected]
> > Subject: T24: Select on local template - performance issue
> >
> > Hi All,
> >
> > We created a report which will list the FT transactions that are with
> > TRANSACTION.TYPE LK OT..., for outward remittance report, so we created a
> > local template which will have the list of FT id's from the history file
> and
> > also fields which will store information like TRANSACTION.TYPE, CO.CODE
> and
> > 9 more fields as these fields are the same fields that will appear in the
> > enquiry dynamic select criteria, when we run the enquiry, internally the
> > enquiry is running a select criteria as shown in the mw42 jbase monitor
> >
> > SSELECT F.FT.BMITPL.OTPASTS WITH TRANSACTION.TYPE LIKE OT... AND CO.CODE
> EQ
> > BH0010001 etc
> >
> > The above select query is taking more time and the browser enquiry is
> timing
> > out, since the local template has 3 lakh records.
> >
> > Please suggest me a suitable solution so as to avoid browser enquiry
> getting
> > timed out.
> >
> > Regards,
> >
> > Ramkumar.S
> >
> > --
> > 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 [email protected]
> > To unsubscribe, send email to [email protected]
> > 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 [email protected]
> To unsubscribe, send email to [email protected]
> For more options, visit this group at
> http://groups.google.com/group/jBASE?hl=en
>
--
Imran Khan
T24 Technical Consultant
+92 334 3545114
--
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 [email protected]
To unsubscribe, send email to [email protected]
For more options, visit this group at http://groups.google.com/group/jBASE?hl=en
