Post-Installation Steps

3 Post-Installation Steps

This chapter describes the post-installation steps.

Perform the following post-installation steps:

Navigate to the $FIC_HOME/ECM_Common_Scripts/Tags/Transaction path and execute the SQL file Tag_utility.sql in Atomic Schema.
As part of introducing the Suppression Condition, you must bring Binding-related additional information to ECM from BD. To populate this data for the existing Events in the system: Navigate to the $FIC_HOME/ECM_Common_Scripts/Event_binding path and run the fcc_event_biding_update.sql script. Before running the script, follow the instructions in fcc_event_biding_update.sql.

If OFS BD and ECM are on the same schema, run the following query in the Config schema and commit the changes:

Update PR2_PROCESS_TASK_PARAMETER set V_TASK_PARAMETER_VALUE =
replace(replace(V_TASK_PARAMETER_VALUE, '"SOURCENAME=##OFS_ECM_AML_SOURCE##"', '"SOURCENAME=”'), '"LOADTYPE=##OFS_ECM_AML_LOADTYPE##”','"LOADTYPE=”') where V_PROCESS_ID in ('1552025714669','1552025648676','1552025714670');

If OFS BD and ECM are on different schemas, run the following query after replacing ##REPLACE_SOURCENAME## and ##REPLACE_LOADTYPE## with their respective values in the Config schema and commit the changes:

Update PR2_PROCESS_TASK_PARAMETER set V_TASK_PARAMETER_VALUE = replace(replace(V_TASK_PARAMETER_VALUE,'”SOURCENAME=##OFS_ECM_AML_SOURCE ##”'
      '"SOURCENAME=##REPLACE_SOURCENAME##”'), '"LOADTYPE=##OFS_ECM_AML_LOADTYPE##”','”LOADTYPE=##REPLACE_LOADTYPE##”')
      where V_PROCESS_ID in
    ('1552025714669','1552025648676','1552025714670');

After the patch application is successful, perform the following steps to map the respective party-party relationship processes:
1. Login to the KYC application.
2. Navigate to Common Tasks -> Rule Run Framework -> Process select Business Data Load For Oracle KYC, and click Edit.
3. Select Component and expand the Process tab in the list.
4. Select Oracle KYC To Consolidation Area Party Relationship Lookup, Oracle KYC To Consolidation Area Party Relationship, Oracle KYC To Consolidation Area Party Relationship Event, and move them to the right side of Tasks in ROOT at the end.
  Note:
  If any processes mentioned above are already mapped, make sure you correct the order of these tasks. The sequence must be as follows:
  1. Oracle KYC To Consolidation Area Party Relationship Lookup
  2. Oracle KYC To Consolidation Area Party Party Relationship
  3. Oracle KYC To Consolidation Area Party Party Relationship Event
5. Click Ok and save the Business Data Load For Oracle KYC process.
6. Select Third Party Generate Cases and click Edit.
7. Select Component, expand Insertion Rules, and expand EXT.ECM_Source.
8. Select the t2t_KDD_CASE_PARTY_PARTY_RLSHPrule and move it to the right side of Tasks in ROOT. This task must be before the Case Completion Flag. Save the Process.
9. SelectPrecedence, select the t2t_KDD_CASE_PARTY_PARTY_RLSHPrule from the drop- down, and add f_insertcases as precedence.
10. Now, select CASE_COMPLETION_FLAG from the Precedence drop-down and add the t2t_KDD_CASE_PARTY_PARTY_RLSHP rule as precedence.
11. Save theProcess.
12. Navigate to Run and save Oracle KYC Event Processing.
After the patch application is successful, if you are using CS Cases, follow these steps to populate case specific attributes in the Case Contextscreen:
1. Login to the ECM application, navigate to Common Tasks -> Rule Run Framework-> Process. Select the process BD_Create_Case and click Edit.
2. SelectComponent, expand Transformation Rules in the List, expand Database Functions- Transformations, and double-click Database Functions-Transformations. Select F_INSERT_WL_ATTR_BATCH_CS and move them to the right side of Tasks in ROOT at the end.
3. SelectF_INSERT_WL_ATTR_BATCH_CSin Tasks under Root, click the up arrow to move it between f_insertcases and t2t_KDD_CASE_ACCOUNTS, and click OK to save.
4. Select Precedence, select F_INSERT_WL_ATTR_BATCH_CS in the drop-down, and add f_insertcases as precedence.
5. Now, select CASE_COMPLETION_FLAG in the Precedence drop-down and add F_INSERT_WL_ATTR_BATCH_CS as precedence.
6. Save the Process and click Yes in the dialog popup.
Add the BD_ENTITY_TAG_MAP DT under BD_Create_Case. Set precedence CASE_COMPLETION_FLAG to the DT.
After the patch application is successful, if you are using KYC Cases, follow these steps to populate Due Date in Cases:
1. Login to the ECM application.
2. Navigate to Common Tasks -> Rule Run Framework -> Process select ThirdParty Generate Cases, and click Edit.
3. SelectComponent, expand Transformation Rules in the List, expand Database Functions- Transformations, and double-click Database Functions-Transformations. Select BD_BATCH_CASE_DUEDATE_UPDATE and move them to the right side of Tasks in ROOT at the end.
4. Select BD_BATCH_CASE_DUEDATE_UPDATE in Tasks under Root, click the up arrow to move it between f_insertcases and t2t_KDD_CASE_ACCOUNTS, and click OK to save.
5. SelectPrecedence, select BD_BATCH_CASE_DUEDATE_UPDATE in the drop-down, and add f_insertcases as precedence.
6. Save theProcess.
7. Navigate to Run and Save Oracle KYC Event Processing.
Restart the servers.
Perform the following steps to move the newly created SMS Functions for app pack movement:
1. Go to $FIC_HOME/utility/AppPckMastSynch/bin.
2. Open the AppPckMastSynch.sh shell file.
3. Replace the token $PackName to OFS_ECM_PACK.
4. Execute the shell file: $./AppPckMastSynch.sh.
5. After execution is complete, replace OFS_ECM_PACK back to $PackName in AppPckMastSynch.sh and close the file.
Before executing the batch, ensure that the Customer Account roles are configured using the Manage Common Parameters screen for the Parameter Customer-Account Role filter. This is a mandatory step to move only selected Customer Account roles through the batch.

Add new processes under the defined existing process. Define the precedence for the newly added process.

Entity Surrogate Key Generation for BD

i. Oracle Behavior Detection to CA Execution Lookup - BD_EXECUTION_LOOKUP
ii.   Oracle Behavior Detection to CA Event Entity Map Execution - BD_EVENT_ENTITY_MAP_EXCTN
iii.  Oracle Behavior Detection to CA Order Lookup - BD_ORDER_LOOKUP
iv.   Oracle Behavior Detection to CA Event Entity Map Order - BD_EVENT_ENTITY_MAP_ORDER
v.    Oracle Behavior Detection to CA Security Lookup - BD_SECURITY_LOOKUP
vi.   Oracle Behavior Detection to CA Event Entity Map Security - BD_EVENT_ENTITY_MAP_SCRTY
vii.  Oracle Behavior Detection to CA Trade Lookup - BD_TRADE_LOOKUP 
viii. Oracle Behavior Detection to CA Event Entity Map Trade -BD_EVENT_ENTITY_MAP_TRADE
ix.   Oracle Behavior Detection to CA Issuer Lookup - BD_ISSUER_LOOKUP
x.    Oracle Behavior Detection to CA Event Entity Map Customer Account Position -- BD_EVENT_ENTITY_MAP_ACCT_POSN
xi.   Oracle Behavior Detection to CA Organization Lookup -BD_ORG_LOOKUP
xii.  Oracle KYC To Consolidation Area Party Relationship Lookup -BD_PARTY_PARTY_RLSHP_LOOKUP

Oracle Behavior Detection Miscellaneous Data Load

i. Oracle Behavior Detection to CA Execution - BD_EXECUTION
ii.   Oracle Behavior Detection to CA Order - BD_ORDR
iii.  Oracle Behavior Detection to CA Security - BD_SCRTY
iv.   Oracle Behavior Detection to CA Security Market Daily Profile - BD_SCRTY_MKT_DAILY
v.    Oracle Behavior Detection to CA Security Firm Daily Profiles - BD_SCRTY_FIRM_DAILY
vi.   Oracle Behavior Detection to CA Trade - BD_TRADE
vii.  Oracle Behavior Detection to CA Issuer - BD_ISSUER
viii. Oracle Behavior Detection to CA Customer Account Position --BD_ACCT_POSN
ix.   Oracle Behavior Detection to CA Organization - BD_ORG
x.    Oracle KYC To Consolidation Area Party Relationship - BD_PARTY_PARTY_RLSHP

Oracle Behavior Detection Evented Miscellaneous Data Load

i. Oracle Behavior Detection to CA Evented Execution - BD_EXECUTION_EVNT
ii.     Oracle Behavior Detection to CA Trade Execution - BD_TRADE_EXECUTION_EVENT
iii.    Oracle Behavior Detection to CA Evented Order - BD_ORDR_EVNT
iv.     Oracle Behavior Detection to CA Order Event - BD_ORDR_EVENT
v.      Oracle Behavior Detection to CA Evented Security -BD_SCRTY_EVNT
vi.     Oracle Behavior Detection to CA Evented Security Market Daily Profile - BD_SCRTY_MKT_DAILY_EVNT
vii.    Oracle Behavior Detection to CA Evented Security Firm Daily Profiles - BD_SCRTY_FIRM_DAILY_EVNT
viii.   Oracle Behavior Detection to CA Evented Trade - BD_TRADE_EVNT
ix.     Oracle Behavior Detection to CA Evented Customer Account Position -- BD_ACCT_POSN_ARC
x.	Oracle KYC To Consolidation Area Party Relationship Event - BD_PARTY_PARTY_RLSHP_EVNT

Loading BD Events
1. Oracle Behavior Detection to CA Event Suppression - BD_EVENT_SUPPRESSION.

Add new t2t tasks under the

Oracle Behavior Detection Generate Cases
                    (BD_Create_Case)

process. Define the precedence for the newly added t2t tasks.

a. t2t_KDD_CASE_EXECUTION
b.	t2t_KDD_CASE_ORDER
c.	t2t_KDD_CASE_SCRTY
d.	t2t_KDD_CASE_TRADE
e.	t2t_KDD_CASE_ORDR_EVENT
f.	t2t_KDD_CASE_SCRTY_FIRM_DAILY
g.	t2t_KDD_CASE_SCRTY_MKT_DAILY
h.	t2t_KDD_CASE_TRADE_EXECUTION_EVENT
i.	t2t_KDD_CASE_PARTY_PARTY_RLSHP

For JIT implementation, perform these steps:
1. Login as SYSADMN and provide the following details under the System Configuration Details:
  1. Select Authentication Type as LDAP Authentication and SMS Authorization. Click Add and provide your LDAP Server details and save.
  2. Check the JIT Provisioning Enabledoption.
2. Login to the LDAP Server. Create and map the Application User Groups and Users.
3. In the Atomic schema, a new table FCC_GROUP_SEC_ATTR_MAP is introduced to configure the security attributes mapping to the Application User Groups. Login to Atomic schema and configure security attributes to the User Groups.
  1. Populate the V_GROUP_CD column with the User groups mapped to User in step b above.
  2. For ECM, valid values for the V_SEC_ATTR_CDcolumn are JRSDCN,ORG, BUSDMN and CASETYPE.
  3. For ECM, valid values for the V_SEC_ATTR_VAL column are Jurisdiction, Organization, Business Domain and Casetype values. Ensure that those are available in the KDD_JRSDCN and KDD_JRSDCN_TL,KDD_ORG and KDD_ORG_TL, KDD_BUS_DMN and KDD_BUS_DMN_TL,KDD_CASE_TYPE_SUBTYPE and KDD_CASE_TYPE_SUBTYPE_TLtables respectively.
4. Perform the following User Attribute configuration:
  1. Case Own Flag: Create a CMCASEOWNFLUG group in LDAP Server and map it to the User in LDAP. If CaseOwn Flag for a user needs to be Y, then map this group to the user. If CaseOwn Flag for a user needs to be N, then make sure it is not mapped to the user.
  2. Reporting/Line Organization: Create a User group with Prefix as ORG_CD (from the KDD_ORG table) and a suffix as LORG. For example: if TestOrgA is the Line organization, create a User group as TESTORGALORG.
  Note:
  The above User Group must be created and mapped to the Infodom/Segment and CMLINEORG Role in the OFSAA application. In LADP, it must similarly be created and mapped to the User. Ensure that only one LORG group is assigned to each given User. If the LORG group mapping is already available as part of any other Application then there is no need to map again.
5. The FCC_GROUP_SEC_ATTR_MAP table in Atomic Schema is used for Configuring Security Mapping for the Pool Users.
  1. The V_GROUP_CD column must be populated with the LORG group created in step ii in point d above.
  2. For ECM, valid values for the V_SEC_ATTR_CD column are JRSDCN, BUSDMN and CASETYPE.
  3. For ECM, the valid values for the V_SEC_ATTR_VAL column are Jurisdiction, Business Domainand Casetypevalues. Ensure that those are available in the KDD_JRSDCN and KDD_JRSDCN and KDD_JRSDCN_TL,KDD_ORG and KDD_ORG_TL,KDD_BUS_DMN and KDD_BUS_DMN_TL,KDD_CASE_TYPE_SUBTYPE and KDD_CASE_TYPE_SUBTYPE_TL tables respectively.
6. Login with the New User in the Application and observe the security attributes mapping all done. Users can view pages based on their Roles and the Cases based on the security attribute mapping.
7. For an existing user:
  1. If extra User groups are mapped in the LDAP Server, then once the User logs in to the application, confirm that the security attributes mapping is done. Also, ensure that the Users can view pages based on their Roles and can see the Cases based on the security attribute mapping.
  2. If few User groups are unmapped in the LDAP server, then:
    - Unmap the User groups from the application.
    - Follow the step under point iii:
  3. If User group mapping does not have any change and there are only changes in security attribute mapping to be done:
    - Login with Admin user. Navigate to Batch Maintenance and create a Batch. For ECM, add the ECM task FCC_ECM_JIT_SYNCH to it.
    - Execute the Batchvia the BatchExecution screen. This can be monitored via the Batch Monitor screen. Once the Batch is executed, it will sync up the security attributes mapping for all the users in the kdd_review_owner table.
8. To disable a user/user(s) disabled on LDAP, log in with Admin user, navigate to Batch Maintenance and create a Batch.
  1. For ECM, add the ECM task FCC_ECM_JIT_DIS_USR to it.
  2. Edit the Task. Mention the User/User IDs, separated by commas, in the Parameter section. This has to be enclosed in Single Quotes. For example: CMSUP, CASEANA where CMSUP, CASEANA are users who need to be disabled in the kdd_review_owner table.
To display the status of historical migrated FCCM alerts in related events, navigate to Atomic Schema and run the procedure P_ECM_EVENT_MIGRATED_STATUS_POPULATION.
To view the next periodic re-review on the KYC Case Context screen, update end Point / DnextRereviewDate in ECM UI as follows:
1. Go to Case Management Configuration then to the Open Manage Common Parameters
2. Select Deployment Based from the Parameter Categorydrop-down.
3. Select KYC Deployment from the Parameter Namedrop-down.
4. UpdateAttribute8 Value with http://hostname:portnumber/contextname/restapi/ kycrest/DnextRereviewDate end pointed.
To create Customer Screening events based on the Quantifind output JSON file, update the endpoint in the properties file. Perform the following steps to make the update:
1. Go to <<FICDB>>/conf/.
2. Open the ECMQuantifindBulkService.properties file.
3. Update ECM_SERVICE_URLwith http://hostname:portnumber/contextname/rest-api/ CMRestService/RealTimeCaseCreationService/saveEvents.
To access the AIF_ANOMALY_SCORE and AIF_ANOMALY_SCORE_ECM_DETAILS tables available in BD schema from ECM schema, when BD and ECM setups are not pack on pack.
Create synonyms using the following scripts:
1. If KYC and ECM are in the same DB, execute the following scripts:
  1. Create or replace synonym AIF_ANOMALY_SCORE for &&bd_schema_owner.AIF_ANOMALY_SCORE;
  2. Create or replace synonym AIF_ANOMALY_SCORE_ECM_DETAILS for &&bd_schema_owner.AIF_ANOMALY_SCORE_ECM_DETAILS;
2. If KYC and ECM are in different DBs, replace the AMDBLINK with the DB link of the current setup in the following scripts and execute them. @AMDBLINK is a placeholder.
  1. Create or replace synonym AIF_ANOMALY_SCORE for AIF_ANOMALY_SCORE@AMDBLINK;
  2. Create or replace synonym AIF_ANOMALY_SCORE_ECM_DETAILS for AIF_ANOMALY_SCORE_ECM_DETAILS@AMDBLINK;
Navigate to $FIC_HOME/ECM_Common_Scripts/Tags/Transaction and execute Tag_utility.sql in Atomic Schema.