61
Chapter 3
Importing Product Content
3-9
For information on how to set the Change Mode preference to Redlining or Authoring mode, see “Setting Business
Rule Options” on page 8-2.
Selecting a Change Order
On the Select Change Order and Mapping File step of the Import wizard, you can specify a change order to use for
the import session. In Redlining mode, a change order is required to import items, BOMs, AMLs, prices, and price
lines. In Authoring mode, a change order is optional.
Click to select a change order. The Select Change For Import window appears. This new window is another
wizard that lets you specify the change order to use for the current import session. You can search for an existing
change order or create a new ECO, MCO, SCO, or PCO, or a change order of a similar user-defined subclass.
Note
If you search for an existing change order, make sure it is in a non-released state. If you're importing prices
in Redlining mode, search the Agile PLM system to see if there is a pending PCO for the price object. If
there is already a pending PCO associated with a price, you cannot add the same price object to a different
PCO.
BOM, AML, and Price Lines Rollbacks
To preserve the integrity of BOMs, AMLs, and Price Lines imported to the Agile PLM system, the Import wizard
doesn’t allow you to import partial import data to a new revision. If a BOM, AML, or Price Line row cannot be
imported because it is invalid, the revision is rejected and the Import wizard rolls back the entire table to its original
state prior to the import session.
During BOM, AML, and Price Lines rollbacks, parent items and prices are not removed from the
Affected Items
or
Affected Prices
tabs of the specified change order. Also, changes made to Title Block, Page Two, or Page Three fields
are unaffected by rollbacks.
If a fatal error (for example, a database error) occurs while you are importing to a new revision of an item, the Import
wizard rolls back the revision. Despite the rollback, any child items automatically created during the import process
are not removed; they remain in the Agile PLM system.
If you import a BOM, AML, or Price Lines table to the latest revision and a validation error occurs, the replacement
table is rejected.
If a fatal error occurs while you are importing BOMs, AMLs, or Price Lines to the latest revision, any replacement
tables that were accepted before the error occurred cannot be rolled back. If this happens, try importing to the latest
revision again.
If there are existing redlines for a pending Change order, the Import wizard clears them before importing new
redline data from the import file. The clearing of redlines and the importing of new data are separate operations.
After the redlines are cleared, the transaction is committed, and then the import process starts. Therefore, if the
import operation fails for any reason (such as a duplicate item number), the table rolls back to its pre-redlined state.
The following table shows how import errors affect released BOMs, AMLs, and Price Lines tables:
Table 3-1: How import errors affect released BOMs, AMLs, and Price Lines
Revision
Type of Error
Result
New revision — importing a new
revision to the parent item or price
Validation error
The new revision and the related BOM, AML, or Price Lines
table rejected.
Fatal error
The new revision and the related BOM, AML, or Price Lines
table are rolled back.
Current revision — importing
changes to the current revision of the
parent item or price
Validation error
The replacement BOM, AML, or Price Lines table is rejected.
Fatal error
Any replacement BOM, AML, or Price Lines tables imported
before the fatal error cannot be rolled back.