[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
RE: [sqr-users] Thinking about trying something - looking for ideas
- Subject: RE: [sqr-users] Thinking about trying something - looking for ideas
- From: "Elvis Pressly" <elvisdman@hotmail.com>
- Date: Fri, 05 Jan 2007 16:02:52 +0000
- Bcc:
- Delivery-date: Fri, 05 Jan 2007 11:05:29 -0500
- In-reply-to: <6998266.1167933964277.JavaMail.oracle@web265.oracle.com>
- List-id: "This list is for discussion about the SQR database reportinglanguage from Hyperion Solutions." <sqr-users.sqrug.org>
John,
I have done this with one of my client long time ago (I think it was in
version 7.5). I'm telling you it can be very ugly to find orphan records.
The way I did it is first consider which fields are the driving mechanism to
establish what you will consider orphan record. You have to understand that
different application has different mechanism. For HR and related
application you will use EMPLID and PS_JOB,
for AP, AR, INVENTORY or Financial it's different.
For HR you create a temporay table that contains unique EMPLID from PS_JOB.
This table should only have one field or column (EMPLID). It's up to you
what type of employee to be inserted into the temp table. Use PSRECFLDFN
table (select only tables that has field EMPLID) as your reference.
depending on which platform, use that table name or schema name from the
PSRECFLDFN. In SQR you can then use the table name as a dynamic table name.
The rest is just comparing EMPLID vs the temp table.
Hope this help.
_________________________________________________________________
>From photos to predictions, The MSN Entertainment Guide to Golden Globes has
it all. http://tv.msn.com/tv/globes2007/?icid=nctagline1
_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users