33.3 Setting up Batch Execution of Rate Card

For the defined Products to become “dummy” instrument records and for these records to be Transfer Priced, a Batch process is required. The following steps describe how to create the required batch process.

Create a Batch for running the daily FTP process against standard products. This process should be scheduled to Run each day (or at any required frequency) by the Administrator after the daily FTP reference rates are loaded.

To set up batch execution of rate card:

  1. Click the Batch Maintenance option under Operations.

    Figure 33-7 Batch Maintenance screen


    The Batch Maintenance screen displays the list of batches.

  2. Click the Add icon to create a Batch for running the daily FTP process against standard products.
  3. Enter the Batch Name and description. Select the Duplicate Batch and/or Sequential Batch option(s) if required. Click Save to save Batch details.

    Figure 33-8 Batch Maintenance Fields


    This screen allows you to define the FTP Rate Card parameters.

  4. Search the created Batch using the Search criteria if required. Searched Batch is displayed. Select the Batch to add the corresponding tasks to it.

    Figure 33-9 Batch Maintenance summary page


    This screen displays all the batches.

  5. Click Add to add the first task to the Batch and enter the task description for the first Task in the Task Definition box. Select the component "RUN EXECUTABLE".

    Figure 33-10 Batch Maintenance – Task Definition


    This screen allows you to define the task details for the batch.

  6. Enter the required parameters as follows:

    Table 33-3 Fields and Descriptions from the Task Definition page

    Term Description
    Datastore Type Leave the default value of EDW.
    Datastore Name Leave the default value.
    IP Address Leave the default value.
    Executable

    Input appropriate values for the following required parameters, tpol.sh, Product dimension number, System ID number for the TP process (for example, tpol.sh,3,300052)

    tpol.sh is the executable file for the first task. It takes process id and product dimension type as the input parameters. tpol.sh internally calls a java program that takes data from the UI tables and populates the FSI_PM_GENERATED_INSTRMTS table.

    Process_id parameter usage in the tpol.sh task:

    The Process ID is used to identify the instrument table (i.e. the PM Generated Instruments table) and fires a delete on this table before processing. This process will work only for the FSI_PM_GENERATED_INSTRMTS table, as it uses an explicit request_id which is null. This column is available only in the FSI_PM_GENERATED_INSTRMTS table.

    While generating the “dummy” instrument records, the tpol.sh process picks up data from the Product Characteristic table but also joins to the process. It generates the instruments only if a TP rule is attached to the Process.
    Wait Y
    Batch Parameter Y
    The name of the executable file is tpol.sh. The following Product Dimension types are supported here:
    • 2 – General Ledger
    • 3- Common COA
    • 4- Product
  7. Click Add to add the second task to the selected Batch and enter the description for the second task on the Task Definition page. Select the component of the task as "Transfer Pricing Engine". This process will execute a TP engine Run, reading the instrument data from the FSI_PM_GENERATED_INSTRMTS table and will update the Transfer Rate column with the calculated result.

    Note:

    Users must first create a Standard TP Process for selection in this batch. The TP Process should include the “PM Generated Instruments” table under Source Selection. The calculated items should include all relevant rate calculations, such as Transfer Rate and Adjustment Rates.
  8. Enter the required parameters as follows:
    • Folder: Select the folder in which the definition of the process that has to be scheduled for execution is lying.
    • Process Type: The Process type can be Standard or Stochastic.
    • Process Name: The Process Name should be defined for process metadata value (system ID of the process) which is defined in Task 1 under Executable parameter.
    • Optional Parameters
  9. Click Add to add the third task to the selected Batch and enter the description for the third task on the Task Definition page. Select the component of the task as "Transform Data". This process will populate the FTP rate from the fsi_pm_generated_instrmts table to the FSI_M_PROD_TRANSFER_RATE table, which is the source table for Rate Card Reporting.

    Figure 33-11 Task Definition fields


    This screen allows you select Dynamic Parameters for the task.

  10. Enter the required parameter details as follows:
    • Rule Name: DT_POPULATE_PM_TRANS_RATE_T_1
    • Parameter List

    Note:

    Third step is not required anymore, as for rate card reporting, data gets picked from FSI_M_PROD_TRANSFER_RATE earlier. But now onwards, fsi_pm_generated_instrmts itself, can retain history and used for Rate Card Reporting.
  11. Define the precedence of the tasks. Task 2 should be executed after Task 1, and Task 3 should be executed after Task 2.

    Figure 33-12 Task Details pane


    This part of the Task Definition screen displays the tasks that are created.

  12. Click the Batch Execution option under Operations to execute the Batch. Select the Batch, which you want to execute using search criteria using the corresponding check-box.

    Figure 33-13 Batch Mode pane


    This screen allows you to select one or more of the listed Batches and execute them.

  13. You can also use the Schedule option if you want to schedule a Batch for later or recurring processing. Click Execute Batch. A message will be displayed: Batch Triggered Successfully.
  14. Click Ok.
  15. To view the Batch Processing Report, click the Batch Processing Report option under Operations. Expand the Execution Date.

    Figure 33-14 Batch Processing Report


    The Batch Processing Report displays the details of the processed batches.

    At this point, “dummy” instrument records will be generated, the records will be transfer priced, inclusive of both base TP Rates and any Add-on Rates defined through an Adjustment Rule, and the results will be moved into the Rate Card reporting table and will be available for reporting.