Import Redlining (Adaptive UI)

The Import Redlining (Adaptive UI) functionality allows authorized users to import Items, BOM, and AML data from third party Excel files into the PLM system using a Change Order (ECO/MCO) business process.

Change order and workflow handling

The Change Order field is populated either with the selected business process ID or with Auto Number.

If Auto Number is used, the user must select a Workflow Template, and a new business process is created automatically.

Input files

Users must provide two Excel files using the drag and drop option available in the workbench:

  • Import file: Contains Items, BOM, Reference Designators, and/or AML data.
  • Mapping file: Contains settings and field mapping information used for transformation logic.

Update mode

The update mode defines how imported data is applied:

  • Complete replace: The existing data can be fully replaced.
  • Net change: Only the differences from existing data are applied.

Template type

The template defines the structure for the BOM data in the excel file:

  • Parent child template: The parent and child templates are provided in separate columns.
  • Level template: The BOM hierarchy is defined using a level/depth column.

Import and validation process

When you click the Import button:

  • The application applies transformation logic from the mapping file.
  • The data is validated based on the rules defined in PLM Preferences for Import Redlining.
  • The transformed data is displayed in a spreadsheet view, with invalid cells highlighted in red.
  • You can correct errors and proceed by clicking Continue.

Creating the business process

When you click Continue the application generates a business process id along with the affected items and required redlining.

  • If an item listed in the Excel file does not exist in the system, the application creates the item with the revision as !INTRO.
  • Items that do not exist in the system, are attached to the business process as affected items, and a redlining is created for each of them (for the “!INTRO” revision).
  • If an item already exists, the system compares the Excel data with the latest revision stored in the PLM tables. If there are differences in item attributes, BOM, or reference designators, the item is attached to the business process as an affected item and redlining is created.
  • If the Excel file contains items of type Document, the application creates the item along with its associated document and file.
  • In all cases, the revision specified in the Excel file is considered as the Proposed Revision.
Note: 
  • If the revision specified in the Excel file already exists, the Proposed Revision field remains empty. The user must either specify the revision in the Redlining Workbench, or the system generates it during the Check Out operation.
  • For AML data, the application ignores the Effective From field (if provided) in the Excel file.

After the business process is created, the Redlining Workbench is started, where users can review the redlining data for the affected items and make changes if required.