Event frame templates for batch data

The migration process creates event frame templates in your AF database that define the minimum required attributes to represent a batch record, such as Batch ID, Product, Procedure Name, and Recipe. After the migration completes, the batch interfaces create event frame templates that match the interface requirements.

OSIBatchDB is a generic event frame category for batch data that contains parent templates for the other batch event frame template categories. The following categories of event frame templates derive from OSIBatchDB:

• OSIBatchMigration is used by AF Link for migrated batches.

• OSIBatch is used by event frame interfaces, such as EFGen and Batch 4.0 interfaces.

  Templates for migrated batch data	Notes
  PICampaignMigrated	This template is for migrated PI Campaigns
  PIBatchMigrated	This template is for migrated PI Batches
  PIUnitBatchMigrated	For unit batches, the name of the procedure is used for the event frame name. If the procedure name is empty, the batch ID is used instead. If the batch ID is empty, the event frame name is the string <undefined>. PI Batch Subsystem batches are migrated to event frames derived from the PIUnitBatchMigrated template. The procedure name attribute of the event frame will be empty, so in this case, the batch ID is used to create the name of the event frame. A PI Heading associated with PI Batch Database batches is not migrated, because there is no equivalent object in the AF database.
  PISubBatchMigrated_L1	Level 1 PI Subbatches are migrated to event frames that derive from the template named PISubBatchMigrated_L1.
  PISubBatchMigrated_L2	Level 2 PI Subbatches are migrated to event frames that derive from the template named PISubBatchMigrated_L2.
  PISubBatchMigrated_L3	Level 3 PI Subbatches are migrated to event frames that derive from the template named PISubBatchMigrated_L3.
  PISubBatchMigrated_L4	The template PISubBatchMigrated_L4 is used for levels 4, and deeper.

PI batch interfaces, version 4.0, or later, create event frames that derive from PICampaign, PIBatch, PIUnitBatch and PISubBatch. Due to how the templates derive, by searching against these templates attributes (Product, Recipe, BatchID, Procedure and Product), you can quickly find common event frames created by the migration process or PI batch interfaces, version 4.0.

Note: Transfer records are not migrated to AF. After the migration of batch data is initiated, PI transfer records become read-only and no new transfer records are generated.