1. Batch Execution Guide
  2. Batch Execution Details
  3. User Allocation Batch

3.6 User Allocation Batch

This batch will assign accounts and their respective tasks to users. Based on group basis at product processor level, different types of user assignments are done as mentioned below:
  • Customer: All the strategies & their respective tasks of all the accounts of a customer will be assigned to a single collector.
  • Accounts: All the strategies & their respective tasks of an account will be assigned to a collector.
  • Ignoring product processor group basis (at Segment Maintenance): Strategies & their respective tasks will be assigned to different collectors based on collector skill-set.

Use Allocation batch is run in 4 sub-batches.

  • Batch 1:
    Function Description:
    1. Batch will consider all accounts where segmentation is not yet done and filter the accounts based on group basis i.e either Account or Customer.
    2. For Accounts where group basis is Customer and account’s primary party having other accounts already assigned in collections then assign same user to this account.
    3. For Accounts where group basis is Account OR group basis is Customer where primary party of the account do not have any existing account in collections, assignment code will be stamped based on the assignment rules and priority defined.

    Job Name: obcr-account-assignment-batch

    Setup Prerequisites

    Following is the prerequisite for the setup:
    1. New Accounts available in the system with segmentation done.
    2. Re-segmentation of the existing accounts in done.

    Dependent Batch/Job: Segmentation Batch

    Multi-threaded: Yes

    Multi-stream: Yes

    URI : <protocol>:// obcr-user-management-services/jobLauncher/runBatch/

    Table 3-15 Mandatory Headers

    Parameter Name Value Mandatory Description
    userld ADMINUSER1 Yes User Id of the requesting user.
    appld CRUSERMGMT Yes The application ID of the host service.
    branchCode DMO Yes Branch Code of the requesting user.
    entityId DEFAULTENTITY Yes Entity ID of the request.
    Accept Application/json Yes Content Type of the request.

    Specify following parameters while executing this batch:

    Table 3-16 Parameters

    Parameter Name Value Mandatory Description
    runDate 01102023 Yes It must be in ddmmyyyy format.
    branchCode DMO Yes The branch code of requesting branch.
    userId ADMINUSER1 Yes The user id of the user triggering the batch.
    overrideDate 2023-10-01 No It must be in yyyy-mm-dd format. It is required to run the batch for a specific day.
  • Batch 2:
    Functional Description:
    1. Batch will consider all the accounts from batch 1 on which account assignment code was stamped.
    2. Based on the assignment method specified in the assignment code (i.e round robin method), users are assigned for these accounts.

    Job Name: obcr-account-assign-batch

    Setup Prerequisites:

    Batch 1 which is obcr-account-assignment-batch must be completed before this batch.

    Dependent Batch/Job: obcr-account-assignment-batch

    Multi-threaded: Yes

    Multi-stream: Yes

    URI : <protocol>:// obcr-user-management-services/jobLauncher/runBatch/

    Table 3-17 Mandatory Headers

    Parameter Name Value Mandatory Description
    userld ADMINUSER1 Yes User Id of the requesting user.
    appld CRUSERMGMT Yes The application ID of the host service.
    branchCode DMO Yes Branch Code of the requesting user.
    entityId DEFAULTENTITY Yes Entity ID of the request.
    Accept Application/json Yes Content Type of the request.

    Specify following parameters while executing this batch:

    Table 3-18 Parameters

    Parameter Name Value Mandatory Description
    runDate 01102023 Yes It must be in ddmmyyyy format.
    branchCode DMO Yes The branch code of requesting branch.
    userId ADMINUSER1 Yes The user ID of the user triggering the batch.
    overrideDate 2023-10-01 No It must be in yyyy-mm-dd format. It is required to run the batch for a specific day.
  • Batch 3:

    This batch will assign strategy level users to all accounts where ignore group basis is maintained as ‘No’ for a segment and stamp assignment code maintained at the segment level for all accounts where ignore group basis is ‘Yes’.

    Functional Description:
    1. This batch will consider all accounts where new segment is added or deleted during segmentation batch.
    2. For all accounts where segment ignore group basis in ‘No’ , assign the account level user already assigned in batch 2 above for all strategies of that segment.

      For all accounts where segment ignore group basis in ‘Yes’ , stamp the assignment code against each strategy as defined in the segment maintenance.

    Job Name: obcr-strategy-assignment-batch

    Setup Prerequisites:

    Following is the prerequisite for the setup:
    1. Batch 1 & Batch 2 must be completed before this batch.
    2. Data is available in output tables of segmentation batch.

    Dependent Batch/Job: obcr-account-assign-batch

    Multi-threaded: Yes

    Multi-stream: Yes

    Table 3-19 Mandatory Headers

    Parameter Name Value Mandatory Description
    userld ADMINUSER1 Yes User Id of the requesting user.
    appld CRUSERMGMT Yes The application ID of the host service.
    branchCode DMO Yes Branch Code of the requesting user.
    entityId DEFAULTENTITY Yes Entity ID of the request.
    Accept Application/json Yes Content Type of the request.

    Specify following parameters while executing this batch:

    Table 3-20 Parameters

    Parameter Name Value Mandatory Description
    runDate 01102023 Yes It must be in ddmmyyyy format.
    branchCode DMO Yes The branch code of requesting branch.
    userId ADMINUSER1 Yes The user ID of the user triggering the batch.
    overrideDate 2023-10-01 No It must be in yyyy-mm-dd format. It is required to run the batch for a specific day.
  • Batch 4:
    Functional Description:
    1. Batch will consider all the accounts from batch 3 on which account assignment code was stamped.
    2. Based on the assignment method specified in the assignment code (i.e round robin method), users are assigned at strategy level.

    Job Name: obcr-strategy-assign-batch

    Setup Prerequisites:

    Batch 1, Batch 2 & Batch 3 must be completed before this batch.

    Dependent Batch/Job: obcr-strategy-assignment-batch

    Multi-threaded: Yes

    Multi-stream: Yes

    Table 3-21 Mandatory Headers

    Parameter Name Value Mandatory Description
    userld ADMINUSER1 Yes User Id of the requesting user.
    appld CRUSERMGMT Yes The application ID of the host service.
    branchCode DMO Yes Branch Code of the requesting user.
    entityId DEFAULTENTITY Yes Entity ID of the Request.
    Accept Application/json Yes Content Type of the request.

    Specify following parameters while executing this batch:

    Table 3-22 Parameters

    Parameter Name Value Mandatory Description
    runDate 01102023 Yes It must be in ddmmyyyy format.
    branchCode DMO Yes The branch code of requesting branch.
    userId ADMINUSER1 Yes The user ID of the user triggering the batch.
    overrideDate 2023-10-01 No It must be in yyyy-mm-dd format. It is required to run the batch for a specific day.

Success/Failure Details:

  • User can verify the record level status in the following tables in CR_USERMGMT schema.
    • DM_ACCOUNT_ALLOCATION_DRIVER
    • DM_ACCOUNT_ASSIGN_DRIVER
    • DM_STRATEGY_ASSIGNMENT_DRIVER
    • DM_STRATEGY_ASSIGN_DRIVER
  • For a successful processing of a record, the below condition should be satisfied.

    ERROR_CODE = ‘Success’ and PROCESS_RESULT = ‘1’

Parent topic: Batch Execution Details