12.1.4.2 Scheduling Replicating Portfolio Actions

In addition to using the “Roll Portfolio” and “Re-balance Portfolio” button options in the Replicating Portfolio UI or the “Merge Portfolio” option, users have the ability to batch and schedule these functions through a Simplified Batch or ICC Batch process.

There are three seeded tasks listed under the Transform Data task type for scheduling these actions:

• Roll_Portfolio
• Rebalance_Portfolio
• Merge_Portfolio

To open the Simplified Batch process screen, from the LHS menu, select Common Object Maintenance, select Operations, and then select Simplified Batch to open the Simplified Batch process page. This page is the gateway for defining the batch processes for behavior pattern batch process and related functionality.

The following screen shot illustrates these tasks selected within a Simplified Batch process.

The following parameters are required for each task:

Roll Portfolio

• Run ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Process ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Execution ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Run Surrogate Key: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Pattern Code: for example, '70001'
• Application ID: for example, 'TP' (this is a static value)
• FTP User: for example, 'TP USER 1'

  These parameters would appear as follows in the simplified batch parameter input block:

  '','','','','70001','TP','TP USER 1'

  When executing from the Run Rule Framework, the user does not have to pass the Run ID, Process ID, Execution ID, and Run Surrogate Key, as the framework itself passes these values along with the Batch ID and MISDATE. The parameters would appear as follows:

  "70001","TP","TP USER 1"

Re-balance Portfolio

• Run ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Process ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Execution ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Run Surrogate Key: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Pattern Code: for example, '70001'

  Re-balance type: for example, '1' (plug to volatile) or '2' (rebalance core strips)

• FTP User: for example, 'TP USER 1'
• Application ID: for example, 'TP' (this is a static value)

  These parameters would appear as follows in the simplified batch parameter input block:

  '','','','', '70001', '1', 'TP USER 1', 'TP'

  When executing from the Run Rule Framework, the user does not have to pass the Run ID, Process ID, Execution ID, and Run Surrogate Key, as the framework itself passes these values along with the Batch ID and MISDATE. The parameters would appear as follows:

  "70001","1","TP USER 1","TP"

Merge Portfolio

• Run ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Process ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Execution ID: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Run Surrogate Key: when running via ICC batch and Simplified batch process, this parameter can be passed as ''
• Pattern Code: for example, '70001'
• FTP User: for example, 'TP USER 1'
• Application ID: for example, 'TP' (this is a static value)

  When to merge (roll versus rebalance): when running via ICC batch and Simplified batch process, this parameter should always be 'N'

  Maturity date identifying maturing strips to be merged on roll : when running via ICC batch and Simplified batch process, this parameter should always be ''

  These parameters would appear as follows in the simplified batch parameter input block:

  '','','','','70001', 'TP USER 1', 'TP', 'N', ''

  When executing from the Run Rule Framework, the user does not have to pass the Run ID, Process ID, Execution ID, and Run Surrogate Key, as the framework itself passes these values along with the Batch ID and MISDATE. The parameters would appear as follows:

  "70001","TP USER 1","TP","N",""