ODS / Release Guide / 3.1

Section 1 Functional Enhancements
Common
Common
New F_GET_PERSON_INFO function
1-SSIDA
In release 3.0 the MST_PERSON table was joined to a number of reporting views to
retrieve the Name and ID fields so that clients would not be required to join in
MST_PERSON in their reporting tools. In doing so, a performance decrease could
result when joining multiple reporting views together that all have a join to
MST_PERSON.
In release 3.1 the hard joins to MST_PERSON were removed from the reporting
view scripts, and a function called F_GET_PERSON_INFO in the MGKFUNC
package was added in their place to retrieve the Name and ID information. The
result is that the MST_PERSON table is only accessed when trying to retrieve these
two columns from a reporting view instead of being accessed anytime the reporting
view is accessed. This new function can also be used to return a select number of
other columns from the MST_PERSON table.
Changed PREFERRED_ADDRESS Reporting View
1-12ZOQH
The TELEPHONE_PREFERRED reporting view contained one active, primary
telephone for each address in the ADDRESS_PREFERRED reporting view (if an
active, primary telephone exists for that address).
Since the data in TELEPHONE_PREFERRED is, for all intents and purposes, an
attribute of preferred addresses, we have added the telephone related columns from
this reporting view to the ADDRESS_PREFERRED reporting view. Doing so will
simplify reporting by eliminating the need for users to join these views to retrieve
the corresponding telephone information.
In making this change, we have in turn made the TELEPHONE_PREFERRED
reporting view obsolete or redundant, since the same information can now be
retrieved from ADDRESS_PREFERRED, as necessary. Therefore, we have removed
the TELEPHONE_PREFERRED reporting view from the ODS.
Changed Relationship Reporting View
1-EKBA1
The Relationship reporting view was enhanced to combine a person’s distinct
spousal or child records with a corresponding cross reference record to the
respective spouse or child, as applicable. This ensures the most accurate
presentation of these relationships by eliminating duplicate or redundant spousal
or child records when both sources exist.
April 2007 Operational Data Store Release 3.1
Confidential Release Guide 13