Agile Product Lifecycle Management Import/Export User Guide Release 9.3.6 E71157-01 |
|
![]() Previous |
![]() Next |
This chapter includes the following:
Overview
About Agile Import Wizard
Before Using the Import Wizard
Privileges Required to Use the Import Wizard
Recommended Sequence to Import Data
Guidelines for Importing Large Import Files
Starting the Import Wizard
Import Wizard Steps
The Import component of the Agile Import/Export application enables selecting and importing data from external systems into different PLM solutions. This chapter provides the necessary referential and procedural information to perform the supported import-related tasks.
Importing data into the PLM databases is performed using the Agile Import Wizard. This tool and the supported data formats in different PLM solutions are described in this section of the guide.
The supported formats:
Excel workbooks (XLS and XLSX)
Delimited text files (TXT)
Product Data Exchange Packages (PDX)
Agile XML (or aXML) files
Objects that you can import for different PLM solutions are listed below. For more information and procedures, see Chapter 2, "Preparing and Selecting Source Data."
Objects that you can import into the PC solution are:
Item
Manufacturer
Manufacturer Part
Part Group
Objects that you can import into the PCM solution are:
Sourcing Projects
Quote histories
Published prices
Suppliers
Supplier RFQ responses
Currency conversion tables
Objects that you can import to PQM solution are:
CustomersProduct Service RequestsQuality Change Requests
Please review the following before using the Import Wizard.
To import data into the Agile PLM system, you must have the appropriate Agile PLM privileges. For information on privileges, see "Privileges Required to Use the Import Wizard."
To create PDX packages, use the Agile Content Service (ACS), the Export function in Agile Web Client, or Agile Integration Services.
Note: Creating PDX packages is similar to creating aXML files. |
To view PDX packages, use Agile eXpress. You can download Agile eXpress from the following Website, or extract the Agile PDX package into the XML file which you can view using any XML viewer:
http://www.oracle.com/technology/software/products/agile/index.html
To create aXML files, you can use the Export function in Agile Web Client, Agile Content Service (ACS), Agile Integration Services (AIS), or the Export aXML command from the Actions menu of a declaration. You can view aXML files in any XML viewer, including Internet Explorer.
Make sure the Agile PLM system has the necessary disk space to accommodate importing large PDX packages and aXML files.
If you are importing data from text files, check your source data to make sure that it is properly formatted. Do not skip this step. The little time spent here will save you far more time in the end.
To import Agile data, you must have Create, Discover, Read, and Modify privileges for each type of Agile object that you are importing. You must also have the ability to create and modify change orders and discover and read them. You need the Change orders to redline BOMs, AMLs, and published prices. In addition, you must also have the Import privilege.
If you have questions about privileges, contact your Agile PLM administrator or refer to the Agile PLM Administrator Guide.
To launch Import, you must have the My User Profile role, and the Import privilege.
Although you can import objects in any given order, it is more instinctive to import the parent object before importing data for the children.
If you are importing product content, import your data according to the following recommended sequence:
Manufacturers
Items
Manufacturer parts
Bills of material (BOMs)
Approved manufacturers lists (AMLs)
Part Groups
Note: If you are importing data from aXML or PDX packages, you can import these objects in one session. |
When you import data according to this recommended sequence, the parent items, manufacturers, and manufacturer parts will exist and will be populated with data when you reach steps 4, 5, and 6 in "Sequence for Importing Product Content." If you do not follow the recommended sequence, the Import Wizard will create objects referenced in the import data. You can go back to a previous step in the sequence (for example, importing Items) to import data to objects that you created with the Import Wizard.
A price object references an item or manufacturer part, supplier, and customer. Therefore, you must import these objects before importing the price objects.
Product service requests reference customers and suppliers. Therefore, you must import customers and suppliers before importing Product service requests:
Customers
Suppliers
Product service requests
Quality change requests reference customers and suppliers. Therefore, you must import customers and suppliers before importing Quality change requests:
Customers
Suppliers
Quality change requests
Manufacturers referenced by a supplier's manufacturer offerings must already exist before the offerings are imported. Therefore, you must import manufacturers before importing supplier manufacturer offerings.
If you are importing Product Governance & Compliance data, Oracle recommends the following import sequence.
Substances
Specifications
Declarations
You can import the following data at any time in any sequence:
Attachments
Projects
Suppliers and supplier commodity offerings. See "Sequence for Importing Supplier Manufacturer Offerings."
Supplier RFQ Responses
Currency Exchange Rates
Agile Import Server supports aXML files and PDX packages which can contain thousands of objects. For example, you can import hundreds of items from a PDX package, where each item can contain several hundred BOM components. Due to the potential for such large source files, the timing to invoke the import session is important.
For example, if you are importing large amounts of data during a single import session, it is recommended that you perform the session during non-business hours-evenings or during the weekend-when system usage is low.
How much data is considered a large amount? This is a function of your Agile PLM system and the size of your database. Use your best judgment. If you plan to import a large amount of data, do it after hours.
After the import session is finished, you can view the log file in a browser or save it to a file.
Note: For faster results, uncheck the Log Transformations preference before importing a large file. For more information, see Chapter 3, "Setting Import Preferences." |
The Import Wizard provides a simple process for importing data into the Agile PLM system.
To start the Import Wizard do as follows:
In Web Client, select the Tools and Settings icon > Import
In Java Client's Tools menu, select the Import icon.
The Import Wizard opens and prompts you for the import file.
To import an RFQ response or items, BOMs, and AMLs for a Sourcing Project, you can start the Import Wizard from an RFQ or a Sourcing Project. For more information, see Chapter 6, "Importing Supplier and System Data" and Chapter 7, "Importing Data into a Sourcing Project."
To import an item using the level template, select Item > Actions > Microsoft Excel > Import from Excel. See "Importing Data from Microsoft Excel Files."
Note: You can also start the Import Wizard by clicking the Import button on the Attachments tab of a package. For more information, see "Importing Attachments from an Agile Package." |
When you import data into the PLM, the Import Wizard displays the following steps to guide you through the process:
File Selection - To specify the import source
Specify File Content - To specify the content to import from the options below:
Select Content Options - To select a mapping and data transformation method. If you are importing Item or Price content specify whether or not a Change Order is required for modifications
If you are importing items or prices in Redlining mode, specify a Change Order for the import session. Also specify how fields in the import data should be mapped to Agile fields.
The Transformation Definition File is an optional step, it specifies how to modify the import data for the target Agile PLM system by replacing, prefixing, or suffixing certain fields.
Note: Depending on the selected option above, review the mapping if you selected Mapping File, or specify mapping if you selected Define attribute mapping. |
Specify Attribute Mapping - To specify and review attribute mapping definition.
Review Import Definition - To review the summary of your import definition. You can validate your definition to view import issues that exist.