Why Process Object View Import Blocks Fails to Create New Function Blocks in CFC

The Process Object View (POV) 'Import Blocks' function fails with 'The block no longer exists in the project' because it is architecturally designed only to modify parameters, comments, and messages of existing block instances, not to instantiate new blocks in CFC charts from CSV rows. To mass-instantiate function blocks or control modules across charts, engineers must use Control Module Types (CMT) with the Technological List Editor, the Import/Export Assistant (IEA), or Plant Automation Accelerator (PAA).

Functional Scope of Process Object View Import Operations

In SIMATIC PCS 7, the Process Object View (POV) is an engineering tool embedded in SIMATIC Manager that consolidates project data into tabular, spreadsheet-like views across hierarchy folders. It provides dedicated tabs for Charts, Blocks, Parameters, Signals, Messages, Picture Objects, and Archive Tags.

The Export/Import functionality in Process Object View operates under strict tabular update semantics:
* Export: Generates a CSV or text file containing object properties (such as block comments, operating parameters, I/O interconnections, alarm limits, and message texts) for existing blocks present in the charts.
* Import: Parses the imported CSV file, searches the target project for matching block instances using their unique chart path and block name, and updates modified parameter values.

Crucially, the POV block import parser requires an existing target block instance in the Step 7 database. It contains no programmatic logic to allocate new block numbers, instantiate CFC chart structures, or initialize internal run sequence tables.

Root Cause of the Block Does Not Exist Import Error

When an engineer deletes existing block rows from an exported CSV and manually enters definitions for new blocks intending to generate them across charts, the import operation aborts with:
Cannot import the attributes of the blocks. --The block no longer exists in the project

This occurs because:
1. Identifier Matching Phase: The POV import engine queries the Step 7 database cross-reference table for the chart name and block instance specified in columns 1 and 2 of the CSV.
2. Missing Object Instance: Because the block has never been placed on the designated CFC chart, the query returns null.
3. Strict Parameter Validation: Rather than creating a missing block, the import parser treats the missing database entry as an orphaned or deleted block reference, throwing a fatal import attribute error.

Supported Engineering Workflows for Mass Block Instantiation

To instantiate blocks or control loops across multiple charts efficiently without manual drag-and-drop, use one of the supported PCS 7 bulk-engineering mechanisms:

Method 1: Control Module Types (CMT) and Technological List Editor (Modern PCS 7)

In the Master Data Library, create a Control Module Type (CMT) containing the required function blocks (e.g., VlvL, MotL, or custom blocks) and standard interconnections.
In the Plant View, use the Technological List Editor (or duplicate CM instances) to generate dozens or hundreds of instances across hierarchy folders.
Synchronize the instances using Options -> Plant Types -> Synchronize with CMT.

Method 2: Import/Export Assistant (IEA) with Process Tag Types (PTT)

Create a Process Tag Type (PTT) in the Master Data Library containing the target function block.
Create an Import/Export File (IEF) template defining variable parameters (names, comments, I/O addresses).
Populate an Import/Export File (IEA CSV file) with new tag instances.
Run the Import/Export Assistant in SIMATIC Manager. The IEA automatically generates new CFC charts, instantiates blocks, and assigns parameters.

Method 3: Plant Automation Accelerator (PAA)

For large-scale greenfield engineering, define instrumentation and control templates in Siemens PAA.
Export the technological hierarchy to PCS 7 via XML exchange. PCS 7 automatically generates all charts and instantiated blocks.

Verification

In SIMATIC Manager, verify that new CFC charts or block instances are generated under the appropriate Plant Hierarchy folders.
Open Process Object View -> Blocks tab. Confirm that the newly created blocks appear in the tabular list.
Perform a test CSV export from POV, modify a parameter (such as a high alarm limit or block comment), and re-import. Confirm that the parameter update imports successfully with zero errors.

Limitations and Operational Precautions

Modifying CSV files in external spreadsheet editors (e.g., Microsoft Excel) can corrupt regional delimiters (commas vs. semicolons) or strip leading zeros from I/O addresses. Always verify CSV formatting in a plain-text editor before importing.
Legacy Import/Export Assistant (IEA) should not be mixed with Control Module Types (CMT) within the same plant hierarchy.
Mass-creating blocks requires recompiling the affected AS charts. Always perform compilation and consistency checks before downloading to the controller.

Engineer FAQ

Can Process Object View create new CFC charts?
No. Process Object View cannot create new CFC charts or new block instances. It is strictly an attribute and parameter editor for pre-existing objects.
Why does POV allow modifying existing blocks but not adding new ones?
Instantiating a function block requires assigning run sequence positions, allocating internal instance DB numbers, and linking system OBs. These tasks are handled by the CFC compiler engine and CMT wizards, not the tabular POV editor.
Can I copy and paste blocks across charts inside POV?
No. Blocks must be copied and pasted directly within CFC charts or instantiated using CMT/PTT duplication mechanisms.

Technical References

SIMATIC PCS 7 Process Object View Configuration Manual (A5E41356253-AA).
SIMATIC PCS 7 Engineering System - Bulk Engineering with CMT and IEA.
Siemens Industry Online Support Entry ID 109801081: Efficient Mass Engineering in SIMATIC PCS 7.