Managing reference data
The topics in this section describe reference data that supports entity types and
relationships between parties. Pega Client Lifecycle Management and KYC comes with reference data that supports different
entity types. The data entity is stored in two different tables of the database. Use
the following database tables to add entity types that you might need to manage in
the applications. To closely resemble the structure of financial institutions, reference data about
entity types is enhanced. During this enhancement process, some entity types and
relationship codes and their attributes are removed from the application reference
data as they are no longer applicable. Removed data does not appear in new
installations. In the environments that are upgraded from previous versions of the
application (8.2 version and earlier), you need to filter out the deprecated entity
types and relationship codes during retrieval make them unavailable to the
users. If your organization needs to use some of the removed codes, you can adjust the
PegaFS-Int-FSF_REF_PARTYSUBTYPEXREF.IsRecordSetAsDeleted
rule, which applies to the D_PartySubTypeXRefDescSummary entity
type. Pega Client Lifecycle Management and KYC comes with reference data that supports different
relationships between parties. The data entity is maintained in the following
database tables: You can add additional values to these tables to make them immediately available in
your application. The following tables list the data pages to use to retrieve this
data: To closely resemble the structure of financial institutions, reference data about
the modeling of relationships (codes and their attributes). During this enhancement
process, some entity types and relationship codes and their attributes are removed
from the application reference data as they are no longer applicable. Removed data
does not appear in new installations. In the environments that are upgraded from
previous versions of the application (8.2 and earlier), filter out the deprecated
entity types and relationship codes need to be filtered out during retrieval to make
them unavailable to the users.Entity types
Data entity Database table Description Entity types fsf_ref_partysubtype List of all entity types in the system. For example, Bank,
Mutual Fund, Insurance Company, and so on. Entity types per party fsf_ref_partysubtypexref List of entity types per party type (organization or fund).
For example, Bank can be used for organizations while Mutual
Fund can only be used for funds. Relationship codes and roles
Data entity Database table Description Relationship codes fsf_relcodes All the relationship codes and their categories irrespective
of party type, for example, Primary Contact, Beneficial Owner,
and so on. Relationship codes per party fsf_partyrelcodexref The role codes based on party types (individual or entity),
for example, show Beneficial Owner only for
individuals). Relationship code attributes fsf_partyrelatttype All reference data of attributes based on the relationship
code, for example, the percentage of ownership for a Beneficial
Owner. Relationship codes
Data page Description D_RelCodeSummary Retrieves all relationship codes D_RelCodeOpen Opens a particular relationship code D_GetRelType Fetches a list of relationship types and their
descriptions Relationship codes per party
Data page Description D_PartyRelCodeXRefOpen Opens a particular code and party type D_PartyRelCodeXRefSummary Retrieves a list of relationship codes based on the party
type Relationship code attributes
Data page Description D_PartyRelAttribTypesOpen Opens a particular attribute D_PartyRelAttribTypesSummary Retrieves a list of attributes based on the relationship
code Relationship codes
Data entity Filtering rule D_RetrieveRelcodeByCategoryAndDesc PegaFS-Int-FSF_RELCODES. IsRecordSetAsDeleted Relationship code attributes
Data entity Filtering rule D_PartyRelAttribTypesSummary PegaFS-Int-FSF_PARTYRELATTTYPE. IsRecordSetAsDeleted
Previous topic Creating a new journey subtype Next topic Managing business rules