TeamcenterKnowledge

Developing requirements > Unstructured (flat file) import

Importing a new requirement specification for the unstructured document

To create a new requirement specification containing requirement objects defined by the identifiers in the unstructured document, you import the unstructured document as a new import. After the import, the requirement specification object name is set to the name of the unstructured document. You have the option of importing the unstructured document with or without trace links.

If the import fails with an error, the entire import transaction is rolled back and the import operation is aborted.

The following occurs in Teamcenter after the import is successfully completed:

  • A new requirement structure is created in Teamcenter. The requirement specification or specification subtype is set to the unstructured document name and contains the imported items. The imported items are created from the valid identifiers for the requirement information such as requirement and paragraph revisions that are specified in the unstructured document. The rules you define in the flat file configuration files validate the identifier tags and control their behavior.

  • The requirement structure is imported as a precise structure.

  • A dataset is created containing the contents of the unstructured document and is associated with the requirement specification. Any Word or Excel macros in the unstructured document are preserved in the dataset.

    Note: If you have previewed the unstructured document before the import, the unstructured document name and the dataset name has the text -Preview appended to the original name.

    The dataset is linked to the requirement objects contained in the requirement specification.

    Example: The ReqSpec100 dataset and its linked requirement information displayed in the Impact Analysis view.

  • External and internal trace links are created in Teamcenter that are defined in the unstructured document. The rules you define in the flat file configuration files determine the trace link behavior.

  • The body text of the requirement objects is set to the URL of the dataset.

    Note: When importing an unstructured document, the formatting for body text may not be preserved.

Related Topics

  • Previewing the import file for accuracy and errors

Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.plm00038/id1676009 · retrieved Fri Jul 10 2026 00:00:00 GMT+0000 (Coordinated Universal Time)