Name matching in subbatch phases

In a typical batch structure, several levels of subbatches may exist for the various parts of the batch process.

Common naming structures

A common structure which can be created via the EVT interface is Batch > Unit Batch > SubBatch > SubBatch, where:

• the first-level SubBatch denotes the operation, and

• the second-level SubBatch indicates the phase.

In some cases, the name of the phase subbatch in the PI Batch Database will take the form Batch > Unit Batch > Operation (Phase), where:

• Operation is the name of the parent operation subbatch, and

• Phase is the name of the phase, enclosed in parentheses.

RtReports phase name matching

RtReports automatically removes the operation name and parentheses from the second-level subbatch name in the PI Batch Database record before applying the name match. This only applies to second-level subbatch templates (the fourth level in the data template hierarchy). If no parentheses are present in the PI Batch Database record for the phase, the name matching is the same as any other data template object.

For example, if a batch had the name BatchABC123 > UnitBatchXYZ > MyOperation > MyOperation(Phase123), only Phase123 should be entered in the Name field for the subbatch template.

This Operation > (Phase) PI Batch Database naming convention for phase subbatches requires that when you create the corresponding RtReports subbatch template for the phase subbatch, you properly match the phase name. To do this, specify only the Phase name in the Name field of the subbatch template. Leave out the Operation name and the parentheses.

Note: If you do not want the Operation name removed before applying the subbatch name matching, set the ParsePhaseName parameter in the web.config file on the RtReports server to False. For more information about configuring the web.config file, see RtReports server defaults.