3 Configuring Tables

You must configure specific tables to populate and save events on the Consolidation and Case layers. By configuring these tables, you will get the flexibility to select which data (such as Evented Entity and Entity details) should be saved.

Note:

This section applies only to the following API Services:
  • Create Event
  • Create Event and Promote to Case
  • Create Event and Extend to Existing Case

Oracle clients can configure these tables before utilizing the API service. The following tables must be configured:

FCC_RT_EVENT_ENTITY_TABLES

The FCC_RT_EVENT_ENTITY_TABLES table stores entities that the service accepts. For example, if this table has entries for only entities such as Account and Customer, then the API service will accept only events generated which have a focus on Account and Customer.

Table 3-1 FCC_RT_EVENT_ENTITY_TABLES

Column Name Description
N_ENTITY_TYPE_ID Entity Type unique ID.
V_ENTITY_TYPE Entity type name. It should be the same as what is sent in the JSON. For example, Customer, Account, and so on.
V_EVENTED_TABLE_NAME Name of the entity evented table where evented data is stored.
V_ENTITY_TABLE_NAME Name of the corresponding CA business table name. For example, FCC_CUST.
V_ENTITY_LOOK_UP_TABLE_NAME Name of the entity lookup table.
IS_LOOK_UP_PER_REQD Determines if the entity details are required to copy to the entity lookup table. You can set this to Y or N. If flag is Y, then it will update the corresponding entity lookup tables. If you are adding a new entity and this flag is Y, then it will check the newly added entity in the lookup table and will not update it in the table if it is a duplicate.
IS_ENTI_PER_REQD Determines if the entity details are required to copy to the entity table. You can set this to Y or N. If this flag is N, then entity information at the time of event generation will not be updated to the corresponding entity tables.
IS_EVENT_PER_REQD Determines if the entity details are required to copy to the event table. That is, you can choose in which table data is to be populated. You can set this to Y or N. If this flag is N, then entity information at time of event generation will not be updated to the corresponding event tables.
V_LOOKUP_SEQUENCE_NAME Sequence name to SKey generation of the lookup. This is required if lookup persistence is required. You can find the sequence from the Sequences (CM_CUST_SEQ) option on the left panel of the database.

FCC_RT_EVENT_ENTITY_TABLES_COL

The following table maps the lookup, evented, and business entity information required to be captured for the respective entities, that is, the columns of the lookup, evented, and business entities that are required on the JSON. The mapping must match the data accepted in the relevant entity tables.

Table 3-2 FCC_RT_EVENT_ENTITY_TABLES_COL

Column Name Description
N_ENTITY_TYPE_ID Sequence ID of the entity. It must be the same as defined in the FCC_RT_EVENT_ENTITY_TABLES table.
V_TABLE_NAME Table name for the entity which is given in the FCC_RT_EVENT_ENTITY_TABLES table.
V_COL_BUSINESS_NAME Business name of the entity attribute.
V_COL_NAME Column name of the entity attribute.
V_DATA_TYPE Data type of the entity attribute.
V_COL_TYPE Column type of the entity attribute.
V_IS_SURROG_KEY Defines the surrogate key.

FCC_RT_EVENTTYPE_PTC

The following table maps the case type and corresponding T2T query IDs that must be triggered during case creation or case extension. These queries are triggered only if the service triggered is required to create or extend a case.

Table 3-3 FCC_RT_EVENTTYPE_PTC

Column Name Description
V_CASE_TYPE The type of the case. For example, AML_DD
N_SEQUENCE Order in which the queries should run for the corresponding case type.
V_T2T_CODE Code name of the corresponding T2T query.

FCC_RT_EVENTTYPE_PTC_QUERIES

The following table stores T2T queries against corresponding T2T codes. Queries are triggered on a case service call, but only the queries mapped to the case type for which the event is triggered will be called.

Table 3-4 FCC_RT_EVENTTYPE_PTC_QUERIES

Column Name Description
V_T2T_CODE Code name of the corresponding T2T query.
C_T2T_QUERY T2T query which populates data to the ECM tables.

FCC_RT_EVNTTYP_CORRELATION_MAP

The following table maps the event type to the correlation rule, so the case generated through the service will be of case type (AML_SURV, CS_SAN, and so on) to which the correlation rule is mapped. For example, Correlation rule 1 is mapped to case type AML_SURV. If the ingesting AML event has to generate a case type of AML_SURV, the entry must be passed in this table mapping event type and correlation rule.

Table 3-5 FCC_RT_EVNTTYP_CORRELATION_MAP

Column Name Description
N_EVENT_TYPE The type of event used for correlation.
N_CORRELATION_RULE_SKEY This is the correlation rule unique Identification number. The value of N_CORRELATION_RULE_SKEY column (rule number) should be the same as defined in the FCC_CORRELATION_RULE table.

FCC_CORRELATION_CASE_TYPE_MAP

The following table maps the correlation rule with the case type, so cases created through this correlation rule will be all of the given case type. For more information on how to design the case type, see Oracle Financial Services Enterprise Case Management Admin Guide.

Table 3-6 FCC_CORRELATION_CASE_TYPE_MAP

Column Name Description
V_CASE_TYPE This is the type of case.
N_CORRELATION_RULE_SKEY This is the correlation rule unique Identification number. The value of N_CORRELATION_RULE_SKEY column (rule number) should be same as defined in the FCC_CORRELATION_RULE table.