Pre-batch Execution Configuration

Configuring Processing Group

Add a new entry in the FCC_PROCESSING_GROUPtable.For example, N_GROUP_IDcanbe 100 or 104 and V_GROUP_NAME can be E2E BATCH ALL SOURCE or MAN. For example, E2E BATCH ALL SOURCE and MAN are the group names provided in the table FCC_PROCESSING_GROUP. N_GROUP_ID should be the next greater numeric value.

Table 5-1 FCC_PROCESSING_GROUP (Metadata Table)

Column Name	Primary Key	Column Type	Nullable
N_GROUP_ID	Y	NUMBER(10)	No
V_GROUP_NAME		VARCHAR2(50)	No

Configure the parameters in Process UI (under components) from the FCC_PROCESS- ING_GROUP table.
For example: "MAN","","ALL","START","IND"

This is required to indicate the name of the Group for which processes are executing. Here, MAN is the Group Name.

For more information, see the Starting a Batch Run section.

When the Start Batch run is executed, it loads the data into the FCC_BATCH_RUN table.

Configuring Correlation

Note:

From ECM 8.0.7.0.0 onwards, the default correlation is PGX. PGX correlation does the same job as JAVA/SQL correlation (BD_Correlation) do, but further drill down approach. It helps us to identify all the relationships between the entities and present it in a graph. If you want to use BD_Correlation process, then follow the below steps:

Remove the PGX Process.
Add the BD_Correlation process.
Trigger the batch.

Initiating Correlation

Before executing the batch, trigger the shell file (initiateCorrelation.sh)to load all query definitions. This shell script must be run if there are changes in query definitions or in paths defined for correlation.

To initiate the correlation, follow these steps:

Navigate to $FIC_HOME/ficdb/bin.
Execute initiateCorrelation.sh. This populates the data in business entity path tables (FCC_CORR_BUS_ENTITY_PATHandFCC_CORRELATION_BUS_ENTITY_CFG).
For more information, see the Using Business Entity Paths section.

Configuring Correlation Rules

After events are correlated to business entities, the event-to-business entity relationships are used to correlate events to each other. Events are grouped into a correlation if they share common business entities, and if they meet the criteria defined in the Event Correlation Rules. The logic of an Event Correlation Rule is defined in the FCC_CORRELATION_RULE table.

The following is an example of the rule logic defined in the FCC_CORRELATION_RULE table:

Note:

In the FCC_CORRELATION_RULE table, the range of N_CORRELATION_RULE_SKEY must be 900-999 for customizations.

Table 5-2 FCC_CORRELATION_RULE

Column Name	Primary Key	Column Type	Nullable
N_CORRELATION_RULE_SKEY	Y	NUMBER(10)	No
V_RULE_NAME		VARCHAR2(50 )	No
N_PATH_PRECEDENCE		NUMBER	No
V_EVENT_FILTER_OPERATIONS		VARCHAR2	Yes
V_EVENT_LINK_OPERATIONS		VARCHAR2	Yes
N_LOOKBACK_VALUE		NUMBER(10)	Yes
V_LOOKBACK_UNIT		VARCHAR2(50 )	Yes
F_EXTEND_FLAG		VARCHAR2	No
V_CASE_STATUS		VARCHAR2	No
V_STATUS		VARCHAR2	No
F_CORRELATION_REQUIRED_FLAG		VARCHAR2	No
F_LOOKBACK_PROCESS_IND		NUMBER	Yes
V_CASE_TITLE_RULE		VARCHAR2	Yes

N_CORRELATION_RULE_SKEY(required): This is the correlation rule unique Identification number.
V_RULE_NAME (required): Defines the name of the correlation rule.
N_PATH_PRECEDENCE(required): Number indicating the maximum precedence value that a business entity shared between events must have to be considered a correlation by this rule. The lower the precedence number the stronger the relationship. Events are not considered for the correlation unless the precedence number associated with the business entity-to- event is less than or equal to (<=) the value defined.
V_EVENT_FILTER_OPERATIONS and V_EVENT_LINK_OPERATIONS (optional): Defines operations used to further constrain the events to be used for correlation. An operation consists of an event attribute compared to a numerical value, such as from event and to event which can be correlated if they both have SCORE_CT>= 0,represented by CORR.SCORE_CT>= 0, or a from event and to event which can be correlated if CORR._CT > 2. The set of supported comparison operators are: =, !=, <, >, <=, >=, IN, and NOT IN.
Because the SCNRO_IDattributeof both events and correlations can potentially have multiple values, only the INandNOTIN operatorsshould be used in expressions involving SCNRO_ID. The rest of the operators can only support single value operands. Also, there should be no space in the scenario ID list specified. For example, BOTH.SCNRO_ID IN (115600002,114690101).
Multiple operations can be joined together by logical AND and OR operators and operation precedence can be defined with parentheses.
N_LOOKBACK_VALUE(optional): The numberattribute indicates the number of days to look back from the current date/time to create a time window to consider events for correlation. This is a created time stamp of the event.
If the look back value is defined, then the look back unit is also required.
V_LOOKBACK_UNIT(required): The unit attribute identifies the unit of the look back number. Possible values are D and CM for days and current month, respectively. All of these require a valid number value except for CM, which essentially makes the look back to the first of the current month, such as if the current date is October 14, we will look back to October 1 if the CM unit is selected. The created time stamp of the event is used to determine whether or not an event falls within the look back period.
Do not use a unitless granular than a day in rules intended for batch events.
F_EXTEND_FLAG (required): Defines the conditions for extending existing correlations. When a new correlation is discovered, it may be a superset (with only the triggering event not already included in the existing correlation) of a correlation that is previously identified. F_EXTEND_FLAG defines whether this correlation rule can result in extending an existing correlation. If this is set to FALSE (do not extend) then a new correlation is created when this condition is identified. If F_EXTEND_FLAG is set to TRUE then the existing correlation is added to unless it is already promoted to a case that has a status identified in the V_CASE_STATUS tags of NonExtendableCaseStatuses.
F_CORRELATION_REQUIRED_FLAG (required): Defines the conditions for correlation required. You can set this as Y or N. If this is set to N, then every event is self linked and promoted to the case. If this is set to Y, then multiple events are linked if they have a common business entity and are promoted to the case.
F_LOOKBACK_PROCESS_IND(required): Indicates if the date of look back is event processing date or sysdate. If this is set to 1, then the processing date is picked. If this is set to 0, then the event created date is picked.
V_STATUS(required):Defines the status of the correlation rule. By default, the correlation rule is Active.
- To deactivate a correlation rule, modify the V_STATUS value to INACT.
- To activate a correlation rule, modify the V_STATUS value to ACT.
Changes made to the metadata are effective immediately and are utilized the next time correlation is run.
V_CASE_TITLE_RULE: This is used for defining the title of the case.

Configuring Ending Batch Process

Before ending a batch, configure the parameters in Process UI (under components).

For example: Configure the following parameters in Process UI (under components):

"","","ALL","END",""

For more information, see the Ending a Batch Run section.

ASC Batch Configuration

The following configurations must be completed before ASC batch run:

Add AML_SURV_BTL case type in Business Hierarchy. To add:
1. Navigate to Common Tasks > Unified Metadata Manager > Business Metadata Management > Build Hierarchy.
2. Select PCASTYP (Pre Case type) and click Edit.
3. In the Business Hierarchy section, select the AML node and click Edit.
4. Add AML_SURV_BTL case type in Node Identifier and click Save.
  For example: FCC_PRECASE.V_CASE_TYPE in ('AML_SURV','AML_SURV_BTL','AML_DD','AML_TER','AML_PAT')
Make sure the Auto Assignment rules are configured to pick and assign the cases with AML_SURV_BTL case type and also Security mapping and Security batch are executed so that Users can access cases with AML_SURV_BTL case type.
For more information, see Configuring Case Allocation and Mapping Security Attributes to Organizations and Users.

Run the below sql script in ECM Atomic Schema.

update FCC_DM_DEFINITION set V_SRC_FILTER='FCC_AM_EVENTS.V_EVENT_CD =
FCC_AM_EVENT_BINDING.V_EVENT_CD
AND FCC_AM_EVENT_BINDING.V_BINDING_ACTUAL_VALUE IS NOT NULL
AND TO_CHAR(FCC_AM_EVENTS.V_EVENT_CD) = FCC_EVENT_LOOKUP.V_EVENT_CD
AND FCC_EVENT_LOOKUP.V_DATA_ORIGIN = FCC_AM_EVENTS.V_DATA_ORIGIN
AND FCC_EVENT_LOOKUP.V_EVENT_TYPE = ''AML_SURV_BTL''
AND FCC_AM_EVENTS.V_RUN_ID = ASC_EVENT_SAMPLE.RUN_ID
AND FCC_AM_EVENTS.V_EVENT_CD = ASC_EVENT_SAMPLE.EVENT_ID
AND FCC_AM_EVENTS.PRCSNG_DT = ASC_EVENT_SAMPLE.FIC_MIS_DATE
AND TRUNC(FCC_AM_EVENTS.PRCSNG_DT) = $MISDATE
AND FCC_AM_EVENTS.V_DATA_ORIGIN IN
(SELECT FCC_BATCH_DATAORIGIN.V_DATA_ORIGIN
FROM FCC_BATCH_DATAORIGIN
WHERE FCC_BATCH_DATAORIGIN.N_RUN_SKEY = $RUNSKEY)
AND NOT EXISTS (
SELECT
''X''
FROM
FCC_EVENT_BINDING
WHERE
FCC_EVENT_BINDING.N_EVENT_SKEY =
fcc_event_lookup.n_event_skey
AND FCC_EVENT_BINDING.V_BINDING_NAME =
fcc_am_event_binding.v_binding_name
AND FCC_EVENT_BINDING.V_BINDING_ACTUAL_VALUE =
fcc_am_event_binding.v_binding_actual_value
)'
where DM_ID='7503'
/
COMMIT
/

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

select * from PR2_PROCESS_TASK_PARAMETER where V_TASK_PARAMETER_VALUE LIKE '%ASC%' ; 
(Check the SOURCENAME and LOADTYPE and replace it by empty string using the below query as reference) 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_task_parameter_value LIKE '%ASC%';

OR

If OFS BD and ECM are on different schemas:

Create the Database Link in the ECM Schema to Connect to the ASC/BD Atomic Schema (Use the Database sys user to create the DB LINK)

CREATE PUBLIC DATABASE LINK <DB_LINK_NAME> CONNECT TO <BD/ASC_ATOMIC_SCHEMA> IDENTIFIED BY <password> USING '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(PORT=<PORT_NO>)(H OST=<hostname>)))(CONNECT_DATA=(SID=<SID_NAME>)))';

Run the following query after replacing ##OFS_ECM_AML_SOURCE## with DB_LINK_NAME and ##OFS_ECM_AML_LOADTYPE## as 'DBLINK' in the Config schema and commit the changes:

select * from PR2_PROCESS_TASK_PARAMETER where V_TASK_PARAMETER_VALUE LIKE '%ASC%' ; (Check the SOURCENAME and LOADTYPE and replace it by ##DB_LINK_NAME## and DBLINK using the below query as reference ) update PR2_PROCESS_TASK_PARAMETER set V_TASK_PARAMETER_VALUE = replace(replace(V_TASK_PARAMETER_VALUE, '"SOURCENAME=##OFS_ECM_AML_SOURCE##"', '"SOURCENAME=##DB_LINK_NAME##"'), '"LOADTYPE=##OFS_ECM_AML_LOADTYPE##"', '"LOADTYPE=DBLINK"') WHERE v_task_parameter_value LIKE '%ASC%';

Run the following query in the ASC BD schema to find the MIS date for the batch:

SELECT V_RUN_ID, PRCSNG_DT FROM fcc_am_events WHERE V_RUN_ID IN (SELECT RUN_ID FROM asc_event_sample) GROUP BY V_RUN_ID, PRCSNG_DT ORDER BY V_RUN_ID, PRCSNG_DT ASC;

In the ECM UI, navigate to Common Tasks > Rule Run Framework > Run.
1. Select the Oracle_ASC_Event_Processing batch, click Fire Run.
2. Select Batch mode (Create and Execute), and provide the MIS Date from the query mentioned above.

5 Pre-batch Execution Configuration