3.2.7 Vendor Allocation Batch

This topic provides information about the Vendor Allocation Batch process.

Vendor Allocation Batch is currently run as two sub-batches.

• Batch 1:

  After the completion of user allocation batch, user will be assigned at strategy level.

  This batch will consider only those records from the above set of records where user id belongs to any of the vendor user group and fetch all the relevant details for these accounts and persist the data.

  Job Name: obcr-vendor-account-assign-batch

  Dependent Batch/Job: User Assignment

  Multi-threaded: Yes

  Multi-stream: Yes

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

  Table 3-42 Mandatory Headers

  Parameter Name	Value	Mandatory	Description
  appld	CRVNDRMGMT	Yes	The application ID of the host service.

  Specify following parameters while executing this batch:

  Table 3-43 Parameters

  Parameter Name	Value	Mandatory	Description
  runDate	01102023	Yes	It must be in ddmmyyyy format.
  branchCode	DMO	Yes	Branch code of the project.
  userId	ADMINUSER1	Yes	User id of the user.

• Batch 2:

  This batch will consider records from strategy assign history table where user id belongs to any of the vendor user group and check whether this account and user combination exists in vendor assign table. If record exists in vendor assign table then delete from this table and move it to vendor account assign history table.

  Job Name: obcr-vendor-account-history-batch

  Dependent Batch/Job: obcr-vendor-account-facts

  Multi-threaded: Yes

  Multi-stream: Yes

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

  Table 3-44 Mandatory Headers

  Parameter Name	Value	Mandatory	Description
  appld	CRVNDRMGMT	Yes	The application ID of the host service.

  Specify following parameters while executing this batch:

  Table 3-45 Parameters

  Parameter Name	Value	Mandatory	Description
  runDate	01102023	Yes	It must be in ddmmyyyy format.
  branchCode	DMO	Yes	Branch code of the project.
  userId	ADMINUSER1	Yes	User id of the user.

Success/Failure Details:

User can verify the record level status in the following tables in CR_VNDRMGMT schema.

• DM_VENDOR_ACCOUNT_ASSIGN_DRIVER
• DM_VENDOR_ACCOUNT_ASSIGN_HISTORY_DRIVER