Resolving 'Object Not Found in Excel Sheet' During CMT Bulk Import in SIMATIC PCS 7

The error 'object not found in Excel sheet' during Control Module Type (CMT) bulk instance import in SIMATIC PCS 7 occurs when constituent function blocks inside the CMT template were created using copy-and-paste from existing charts instead of being dragged directly from the Block Catalog. Pasted blocks retain hidden internal instance identifiers, broken COMOS GUIDs, or obsolete type pointers that corrupt the XML export schema. To resolve the error, delete the pasted blocks from the CMT, re-insert both custom and APL blocks fresh from the SIMATIC Manager Block Catalog, re-export the CMT Excel template to regenerate clean XML headers, and execute the import.

Architecture of Control Module Types (CMT) and XML Schema Generation

Control Module Types (CMT) introduced in SIMATIC PCS 7 V8.0 provide object-oriented template engineering, replacing legacy Process Tag Types (PTT). A CMT defines an automation typical—including function blocks, internal signals, parameters, and messages—within the Master Data Library.

When an engineer exports a CMT to Microsoft Excel or COMOS for bulk data engineering, the CMT generator creates a structured XML/Excel workbook where each constituent block is mapped to a dedicated tab using its catalog type signature. If the underlying block interfaces contain invalid pointers, the parser aborts during instance instantiation.

Root Cause: Catalog Placement vs Copy-Paste Corruption

When constructing a new CMT (such as combining a custom analog block IN_ANa with standard APL blocks):

Copy-Paste Hazard: Copying blocks from an existing CFC chart or legacy PTT carries over chart-specific metadata, internal instance GUIDs, and runtime group associations. When exported, the CMT compiler writes invalid block type tags into the hidden XML definition tables.
Parser Failure: During Excel bulk import, the importer attempts to match rows in the data sheet against the template schema. Failing to resolve the internal GUID against the catalog type name, it halts with error: object not found in Excel sheet named: <BlockName> In library sheet <SheetName>.

Differences Between Process Tag Types (PTT) and Modern CMTs

Unlike legacy PTTs which relied on the Import/Export Assistant (IEA) and simple text replacements:

CMTs enforce strict structural synchronization. A single CMT can contain optional sub-blocks and control modules.
CMTs maintain a continuous synchronization link between the Master Data Library template and all placed instances in the plant hierarchy. Corrupted template definitions compromise instance synchronization across the entire multiproject.

Step-by-Step CMT Construction and Bulk Import Workflow

Follow this procedure to create clean, importable CMTs:

Clean the CMT Template:
- In the Master Data Library, open the CMT chart.
- Delete any blocks that were inserted via copy-and-paste.
Insert Blocks Fresh from Catalog:
- Open the Block Catalog tab in CFC (Libraries > Master Data Library or APL).
- Drag your custom block IN_ANa directly onto the chart canvas.
- Drag all necessary APL blocks (Pcs7AnIn, MonAnL) directly from the catalog.
Define Control Module Attributes:
- In the CMT editor, assign block parameters, signals, and messages to the CMT interface.
Re-Export Excel Template:
- Select Plant Hierarchy > Export to Excel... (or use Advanced Engineering Tools).
- Populate tag names, I/O addresses, and setpoint values for all new instances.
Import Instances: Execute Plant Hierarchy > Import from Excel...; verify zero errors.

Comparison of Bulk Engineering Approaches in PCS 7

The table below contrasts bulk engineering methods in SIMATIC PCS 7:

| Engineering Feature | Control Module Types (CMT) | Process Tag Types (PTT) | Copy-Paste CFC Charts |
|---|---|---|---|---|
| Template Management | Master Data Library (Central) | IEA File / Templates | None (Ad-hoc) |
| Data Exchange Tool | Modern Excel / COMOS / Plant Automation Accelerator | Import/Export Assistant (IEA) | Manual editing |
| Instance Synchronization| Automatic delta sync (Sync CMT) | Re-import required | Manual re-copying |
| Optional Sub-Elements | Supported (Variants/Options) | Not supported | Not applicable |
| Catalog Integrity Check| Strict (Requires fresh catalog placement) | Moderate | None (High error risk) |

Verification

Verify clean CMT instance generation:

Open the Plant Hierarchy in SIMATIC Manager.
Execute the Excel import of 10 test instances.
Verify that the import log reports 10 instances successfully created, 0 Errors, 0 Warnings.
Open one of the generated CFC charts; verify that block interconnections, parameters, and symbols populate correctly.
Compile CFC charts; verify error-free compilation and valid AS execution.

Limitations and Operational Precautions

Observe the following safeguards when working with CMTs:

Catalog Version Consistency: Ensure the custom block IN_ANa is formally installed in the Master Data Library block catalog before dragging into CMTs.
Do Not Rename Excel Tabs: Never modify the internal sheet names generated by the CMT export wizard, as tab names encode structural hierarchy pointers.
Synchronization Timing: Synchronizing CMT changes across hundreds of plant instances consumes substantial compiler resources; execute large updates during scheduled maintenance.

Engineer FAQ

Why does copy-pasting blocks inside a CMT corrupt the Excel import?

Copying blocks carries over hidden internal instance identifiers and runtime group bindings from the source chart. The CMT Excel generator requires clean, uninstantiated catalog type definitions to generate valid XML schemas.

Can custom user blocks be used inside Control Module Types?

Yes, custom function blocks (such as IN_ANa) can be used inside CMTs provided they are placed directly from the Master Data Library Block Catalog and have their I/O attributes defined.

What tool synchronizes changes made to a CMT across all plant instances?

In SIMATIC Manager, right-clicking the Master Data Library chart folder and selecting 'Plant Hierarchy > Synchronize...' propagates CMT modifications across all instances.