6 Performing Batch Run

This section provides the details of the ECM batch run.

The ECM application batch run comprises of the following processes:
  • Start ECM batch
  • Load events, evented, and business data to Consolidation area
  • Correlation
  • Scoring
  • Promote to case
  • Create a case
  • End ECM batch

Note:

You must configure your own batches and default OOB must not be run as it is a sample run.

Starting a Batch Run

Note:

For executing a batch, you cannot start two batches simultaneously for the same processing group.
To start the batch run, follow these steps:
  1. Navigate to Enterprise Case Management Application.
  2. Go to the Common Tasks section. Select the Rule Run Framework.
  3. Click Run. The Run window is displayed with the available Processes.

    Figure 6-1 Application List

    This image shows the Application List.
  4. Go to the List section. Select an application for example (Oracle_BD_Event_Processing). The list of processes for the selected application is displayed.

    Figure 6-2 List of Processes screen

    This image shows the List of Processes screen.
  5. Navigate to Process Summary Page and search for BD_ECM_Start_E2E_Batch.
  6. Select the batch BD_ECM_Start_E2E_Batch and click Edit.

    Figure 6-3 Process screen

    This image shows the process screen.

    The Process Definition page is displayed.

    Figure 6-4 Process Definition page


    This image shows the Process Definition page.

  7. Click Component. The Component Selector window is displayed.
  8. Under the Tasks In ROOT section, right-click on the required batch, and then click Add Parameters. The Parameters window is displayed.

    Figure 6-5 Parameters

    This image shows the Parameters.

    The following are default parameters: "MAN","","ALL","START","DLY".

    • MAN:is the group name. Modify the name of the group as mentioned in FCC_PROCESS- ING_GROUP table. For example: E2E BATCH ALLSOURCE
    • "" Source Batch for Correlation
    • ALL: is the component that can be modified if required
    • START: is used to start the batch
    • DLY: is Data Origin

    The following is an example of a parameter:

    "E2E BATCH ALL SOURCE","","ALL","START","IND"

  9. Modify the parameters and click OK.

Ending a Batch Run

To end the batch run, follow these steps:
  1. Navigate to the Process Summary page and search for End Batch, for example: BD_ECM_End_E2E.

    Figure 6-6 Process

    This image shows the Process.
  2. Select the batch, and click Edit. The Process Definition page is displayed.
  3. Click Component. The Component Selector window is displayed.
  4. Under the Tasks In ROOT section, right-click on the required batch, and then click Add Parameters. The Parameters window is displayed.
    The following are default parameters: "","","ALL","END",""
    • Source Batch for Correlation
    • ALL: is component. Modify the component if required
    • END: is used to end the batch
  5. Modify the parameters and clickOK.

Executing a Batch Run

Note:

If you have 10 days of data, then the ECM batch has to be executed from day-01 onwards.
To access and execute the batch run, follow these steps:
  1. Navigate to Enterprise Case Management Application.
  2. Go to the Common task section. Select the Run Rule Framework.
  3. Click Run. The Run window is displayed with the available Processes.
  4. Select the Application process from the Run definition page list that is to be executed and click Fire Run. The Fire Run window is displayed.

    Figure 6-7 Fire Run window

    This image shows the Fire Run window.
  5. Enter details as described in the following table:

    Table 6-1 Adding Fire Run Details

    Fields Description
    Request Type

    Select Request Type based on the following options:

    • Single: If the batch must be executed once.
    • Multiple:If the batch must be executed multiple times at different intervals.
    Batch

    Select Batch. It has the following options:

    • Create
    • Create &Execute

    From these options, select Create & Execute
    Wait

    Select Wait. It has the following options:

    • Yes: This executes the batch after a certain duration. Enter the duration as required.
    • No: This executes the batch immediately.
    Filters
    Enter the filter details.

    Note:

    • $MISDATE option can be used to execute the run for that particular day. The format for it to enter the filter details is: to_date(<ACTIVITY_TABLE_NAME>.<ACTIVITY_DT_COL>)=$MISDATE
    • For the $MISDATE option:
      • For either Date or Timestamp datatypes, to_date is mandatory for the filter.
      • Activity Table Name and Activity Column Name should be in the capital.
  6. Click OK to run the batch. The message: Batch Execution is in progress is displayed.
  7. Click Close.

    Note:

    If batch execution fails, then see the batch details in Batch Monitor. For more information on Batch Monitor, see the Oracle Financial Services Analytical Applications Infrastructure User Guide.
  8. Once the batch is triggered, the following processes get executed:
    1. Start ECM batch, select the required process code. For example, BD_ECM_Start_E2E_Batch. For more information on starting the batch, see Starting a Batch Run.
    2. Load events, evented, and business data to the Consolidation area, select the required process code. For example, BD_Load_From_LA_To_CA. For more information on using this connector, see Loading Data
    3. Perform correlation on loaded events and select the required process code. For example, BD_Correlation. For more information on using correlation, see Configuring Correlation.
    4. Perform scoring on correlated events and select the required process code. For example, BD_SCORING. For more information on using scoring, see Scoring.
    5. Determine to promote correlated events to a case and select the required process code. For example,BD_Promote_To_Case_Decision. For more information on using promote to case, see Promoting to Case (PTC).
    6. Create a case event and select the required process code. For example,BD_Create_Case.
    7. End ECM batch and select the required process code. For example, BD_ECM_End_E2E_Batch. For more information on running the batch, see Ending a Batch Run.

      Table 6-2 Application Run Processes

      Process Name OBD OCS OKYC OTBAML OSTDO Third-party
      Start ECM batch

      BD_EC-

      M_Start_ E2E_Batc h

      		 ECM_Sta rt_E2E_B atch_- For_CS ECM Start E2E Batch For KYC

      TBAML_EC-

      M_Start_E2E

      _Batch

      STDO_EC-

      M_Start_E2E_B atch

      		 ECM Start E2E Batch
      To load events, evented, and business data to Consolidation area

      BD_-

      Load_- From_LA

      _To_CA

      Load_- From_CS

      _To_CA

      		 Load_- From_OK YC_To_C A

      TBAML_-

      Load_- From_LA_To

      _CA

      		 STDO_Load_- From_LA_To_C A

      Load_- From_LA_To

      _CA
      Perform correla- tion on loaded events BD_Cor- relation Correla- tion Correla- tion TBAML_Cor- relation STDO_Correla- tion Correlation
      Perform scoring on correlated events BD_SCO RING Scor- ing_OCS Scor- ing_OKYC TBAM- L_SCORING STDO_SCOR- ING Scoring
      Decision topromote correlated events to a case

      BD_Pro- mote_To

      _Case_- Decision

      Pro- mote_To

      _Case_- Deci- sion_OC S

      		 Pro- mote_To_ Case_De- cis- ion_OKYC TBAML_Pro- mote_To_- Case_Decisio n STDO_Pro- mote_To_- Case_Decision Pro- mote_To_- Case_Decisio n
      Create a case

      BD_Cre- ate_Case

      		 Create_- Case Create_- Case TBAML_Cre- ate_Case STDO_Create_- Case

      Create_Case
      End ECM batch

      BD_EC-

      M_End_E 2E_Batch

      		 ECM_En d_E2E_B atch_- For_CS

      ECM_End

      _E2E_Bat ch_- For_KYC

      TBAML_EC-

      M_End_E2E_ Batch

      STDO_EC-

      M_End_E2E_Ba tch

      		 ECM_End_E2 E_Batch

Batch Performance Recommendations

This section provides some tips to improve batch performance.

  • If any performance bottlenecks are coming up in the following tasks, try modifying to the data movement operation to Merge Insert (MI) instead of Delete Insert (DI).
  • Oracle Behavior Detection to CA Account Address - BD_ACCT_ADDR
  • Oracle Behavior Detection to CA Account - BD_ACCT
  • Oracle Behavior Detection to CA Customers - BD_CUST
  • Oracle Behavior Detection to CA Customers Phone - BD_CUST_PHON
Sample Query: Process BD_ACCT_ADDR
UPDATE pr2_process_task_parameter
 SET V_TASK_PARAMETER_VALUE = replace(V_TASK_PARAMETER_VALUE,
 'DATAMOVEMENTOPERATION=DI',
 'DATAMOVEMENTOPERATION=MI')
 WHERE V_PROCESS_ID IN (SELECT V_PROCESS_ID
 FROM pr2_process_b t
 WHERE t.v_process_name = 'BD_ACCT_ADDR'
  • The parallel hint degree can be modified as per system configuration. Oracle provides parallel (2) as part of the product. The degree can be modified using the following sample query.
    Sample Query: Modify parallel (2) to parallel (8)
    update fcc_dm_definition
set
    V_CREATE_SELECT_HINT = replace(V_CREATE_SELECT_HINT,'(2)','(8)'),
    V_INSERT_HINT = replace(V_INSERT_HINT,'(2)','(8)'),
    V_INSERT_SELECT_HINT = replace(V_INSERT_SELECT_HINT,'(2)','(8)'),
    V_MERGE_HINT = replace(V_MERGE_HINT,'(2)','(8)')
WHERE  dm_id in (SELECT dm_id FROM fcc_dm_definition where

  • Increase the index cache to 100000, based on the task or table identified.

    For example:

    • alter sequence CM_ACCT_ADDR_SEQ cache 100000;
    • alter sequence cm_bd_party_party_rlshp_skey cache 100000;
    • alter sequence CM_CUST_PHONS_SEQ cache 100000;
    • alter sequence CM_CUST_ADDR_SEQ cache 100000;
    • alter sequence CM_CUST_EMAIL_ADDR_SEQ cache 100000;

    Note:

    In the case of a server restart, the sequence will be skipped based on the cache mentioned.