Skip Headers

Agile Product Lifecycle Management Import/Export Guide Release 9.3.3 E39290-01 |
| Contents

Previous | Next |

# 11 Exporting Data

This chapter describes the Export Wizard and how to use this tool to export object classes and file formats that you can export plus and downloading files and viewing the exported files.

## 11.1 The Export Wizard

Agile PLM provides an easy to use Export Wizard that supports extracting data from selected objects and exporting the data. You can launch the Export Wizard from either the Web client or Java client. Exporting data is an easy process. After downloading the export file to your desktop, you can either e-mail or FTP the file to a supply chain partner, or import it into another application.

## 11.2 Export Roles and Privileges

To use the Export Wizard, you must have the Export privilege. The Export privilege is included with the following supported roles.

- (Restricted) Material Provider

- Change Analyst

- Compliance Manager

- Content Manager

- Item Content Manager

- Price Administrator

- Price Manager

- Product Content Read Only

- Sourcing Administrator

Note: These roles and privileges are assigned by your PLM System Administrator. The Export type privilege provides the Applied to field/property to control (enable/disable) exporting attachments. The available option for the Applied to field is Attachments. See Exporting Attachments on page 145 for more information.

## 11.3 Object Classes that You Can Export

This table lists the types of objects that the Export Wizard will export.

Base Class | Class
--- | ---
Items Items | Documents
Parts
Manufacturers | Manufacturers
Manufacturer Parts | Manufacturer Parts
Prices Prices | Historical Quotes
Published Prices
Changes Changes Changes Changes Changes Changes Changes | Change Orders (ECOs)
Change Requests (ECRs)
Deviations
Manufacturer Orders (MCOs)
Price Change Orders (PCOs)
Site Change Orders (SCOs)
Stop Ships
Declarations Declarations Declarations Declarations Declarations Declarations Declarations Declarations | Homogeneous Material Declarations
Part Declarations
IPC 1752-1 Declarations*
IPC 1752-2 Declarations*
JGPSSI Declarations*
Substance Declarations
Supplier Declarations of Conformance
Discussions | Discussions
Part Groups Part Groups | Commodities
Part Families
Programs | Activities (only for Root Programs)
Product Service Requests Product Service Requests | Non-Conformance Reports
Problem Reports
Quality Change Requests Quality Change Requests | Audits
Corrective and Preventive Actions
Specifications | Specifications
Substances Substances Substances Substances | Materials
Subparts
Substance Groups
substances
Suppliers | suppliers
Users | users
User Groups User Groups | Functional Teams
Users groups

* This Declaration class provides special export and import commands that enable suppliers to integrate data with other Agile PLM systems, or complete the compliance request form in other clients, such as Microsoft Excel or Adobe Reader. See Using Special Export and Import Commands to Complete Declarations on page 90.

## 11.4 Export File Formats

You can export Agile PLM data to Microsoft Excel, comma-delimited text file (CSV), aXML, or PDX package formats. The following table lists the objects that can be exported for each format.

Object | Excel/CSV | PDX | aXML
--- | --- | --- | ---
Items | Yes | Yes | Yes
Manufacturers | Yes | Yes | Yes
Manufacturer Parts | Yes | Yes | Yes
Changes | Yes | Yes | Yes
Prices | Yes | NA | Yes
Declarations | Yes | NA | Yes
Part Groups | Yes | NA | Yes
Specifications | Yes | NA | Yes
Substances | Yes | NA | Yes
Programs | Yes | NA | NA
Product Service Requests | Yes | NA | Yes
Quality Change Requests | Yes | NA | Yes
Suppliers | Yes | NA | Yes
Discussions | Yes | NA | Yes
Users | Yes | NA | Yes
User Groups | Yes | NA | Yes

In addition to text data, the PDX and aXML packages can also contain attachment files and redlines. PDX packages can be viewed or imported only with PDX-enabled applications. Agile provides a free PDX viewer called Agile eXpress to view these files.

Note: CSV files created by the Export Wizard contain additional header information that is not imported using the PLM Import Wizard. To import data from these files into Agile PLM, make sure you set the header row correctly in the Import Wizard's Delimited Text File Configuration dialog box.

### 11.4.1 Guidelines for Exporting to Microsoft Excel Files and Text Files

When you export data to a Microsoft Excel file, you end up with a single worksheet. When you export data to a text (CSV) file, you end up with a file of comma-delimited data. You can open both file types in Microsoft Excel and view the data in a tabular format.

Use these guidelines when exporting data to Microsoft Excel or text files using the Web Client:

- You can export a single object or multiple objects. Each object tab is a separate delimited text output, placed one after the other in the text file. If you export multiple objects, they are added to the export file one after the other.

- You can export only the information that appears on the tabs of the included objects. So, for example, if you export a single part with a BOM, the resulting file includes information on the part's BOM tab, but it does not include actual BOM items.

- You cannot add the following objects:

  - deleted objects

  - objects for which you do not have the necessary privileges

  - objects that are already in the export file

- You can export Attachments tab information to a text file, but you cannot export the actual attachments. Only PDX and aXML files support actual attachments.

- You can export the Sites tabs of items and the Where Used tab of items, manufacturers, and manufacturer parts.

- If you select the Manufacturers Tab when filtering items and you select a number of levels to be exported with the BOM, your export file will include the AML information for the selected number of levels of the BOM.

- If you include both BOM and AML data in your export file, the AML data is interlaced with the BOM data in the resulting file.

- Regardless of its position in a BOM hierarchy, you can export an Item in Level Template format as shown below.

a. In Web Client, select an Item, for example a part.

b. Select Actions>Microsoft Excel> Export to Excel (or Download Template).

The Excel file containing Title Block, BOM, and Manufacturers Tab data is exported.

Note: Export does not support the Pending Change Where Used tab option. For example, if you create an Item with data in the Item's Where Used and Pending Change Where Used table rows, only the values in the Where Used table are exported.

### 11.4.2 Guidelines for Exporting to aXML and PDX Packages

Agile Extensible Markup Language (aXML) format is an XML representation of Agile PLM's business schema. aXML contains all product content managed in Agile PLM.

Product Data Exchange (PDX) packages contain product content, such as item or change details, plus BOM data, manufacturer information, drawings, and other attached files. They differ from Agile package objects in that they are XML-based documents that conform to the PDX 1.0 standard. PDX packages are based on an industry-standard format for encoding structured data in an XML format. This standard provides an application-independent way to describe product content.

You can use aXML and PDX packages to send data from one Agile system to another. In addition, you can download them to your desktops and then e-mail, or FTP these packages. For PDX packages, you can import them into a PDX-enabled application, such as Agile eXpress.

For more information about PDX, including a link to the DTD, see following Web page:`http://webstds.ipc.org/2571/2571.htm`

There is no encryption for exported data and information in each aXML or PDX package is not secure. A user's privileges determines the data the user can export and users can view the contents in exported files. Login, Discovery, and Read privileges can be set in Agile Administrator to protect partners' information from access by unauthorized users.

Note: In Web Client, you can create, but you can not view aXML or PDX packages.

Use these guidelines when you export data to aXML or PDX packages using Web Client:

- You must have the Export privilege to export data to aXML or PDX packages.

- You cannot add deleted objects, objects for which you don't have appropriate privileges, or objects that are already added to the Objects To Extract table.

- Web Client supports direct access to latest released revisions of items. It also lets you access back revisions or pending revisions.

- If you export Change objects, you can use a custom filter to export redline changes to BOMs and AMLs of affected items. See Exporting Redline BOMs and AMLs for Affected Items on page 144.

- PDX packages include Sites and Where Used tab information, but they are exported as additional attributes, without their own element tags like <sites> or <whereUsed>.

- If you select PDX export, the Compliance tab of items and manufacturer parts is not exported. This is only applicable to aXML files.

- Agile eXpress does not support the Sites tab of items or the Where Used tab of items, manufacturers, or manufacturer parts. This is only applicable to PDX packages.

Note: Export does not support the Pending Change Where Used tab option. For example, if you create an Item with data in the Item's Where Used and Pending Change Where Used table rows, only the values in the Where Used table are exported.

## 11.5 Starting the Export Wizard

You can start the Export Wizard from either Web Client or Java Client using one of the following methods:

### 11.5.1 Java Client

- Open an object to export, and then choose Tools > Export.

### 11.5.2 Web Client

1. Choose Tools and Settings> Export.

2. Open an object to export, and then choose Actions > Export.

3. Search and select one or more objects on the Search Results page, and then choose More > Export.

4. Select and copy objects under My Bookmarks and Recently Visited in left pane and paste them to the Export dialog.

   Note: Although you can select any object from search results, the Export Wizard does not support all object types.

## 11.6 Navigating the Export Wizard Steps

Export Wizard steps are explained in the following example. Most of these steps are optional and you can choose to download the export file at any step without completing the remaining steps.

To export data to a file:

1. Start the Export Wizard. For options, see Starting the Export Wizard on page 138.

   The Select Objects to Export page appears. If you started the Export wizard from Actions > Export or after selecting objects in search results, you will notice some objects are already listed on this page.

   Figure 11-1 Export Wizard's Select Objects to Export page

2. In the Format field, use the drop-down list to specify whether you want to export to a PDX package, an aXML, an Excel (XLS), a Text (CSV), a Simple text (CSV), or a Simple excel (XLS) file.

3. In the Site field, select the site you want to export the data. To export data to all sites, select All.

   Note: The Site field is only available if your Agile system includes the Sites server license.

4. If you don't need to add any more objects to the list, proceed to step 6. To add more objects, click Add.

   The Search palette appears.

5. Search to locate the required objects.

6. Double click the object or drag and drop it into the Select Objects to Export dialog.

7. Adjust values in the Revision column (if necessary).

8. When you have found and added all objects for inclusion in the export file, click Next to display the Select Content Filters page.

9. Filters let you specify which information is added to the export file. For details about filters, see Specifying Filters.

   - To use predefined filters, select Predefined filter and then select the filters you want to use from the drop-down lists. To see the details of the filters, click Details.

   - To define a custom filter for this operation, select Create Custom filter; the Wizard will step you through filter definitions for each object type in the file.

10. Click Next to proceed from the Select Content Filters step.

11. If you selected Customize, on each Filter page, select the information to include in the file, and click Next to proceed to the Specify Export Properties page.

12. Enter the file type and description, and then click Export (If you are exporting to a text file, header information appears at the top of the file.).

13. When everything is complete, click Export to compile and download the export file. If you are exporting to a text file, the encoding type of the exported file is set according to your current user login profile setting. You can use Web Client or Java Client to view or modify currency settings.

    - In Web Client, click Settings > User Profile > Preferences > Edit.

    - In Java Client, click Settings > Current User > Preferences.

14. Click Close to close the File Download window.

    Note: When exporting objects in aXML format, either from the object's actions menu or global export, you can save exported files with the .axml.zip extension. To save them without the .axml.zip extension, change the Save As Type option to All Files in the Save As dialog, and then click Save. This will save the file in the .aXML format.

15. Click Cancel to close the Export Wizard.

## 11.7 Selecting Content Filters

Filters let you specify which information is added to the export file. In Web Client, you can use saved filters, defined by your Agile administrator, or you can create custom filters. In Web Client, you can create user predefined filters and use them during export.

### 11.7.1 Using Saved Filters

When you select Use predefined filter in Select Content Filters step of the Export Wizard, you can select from lists of defined filters for all supported object types. These filters are defined by the PLM administrator using the Java Client. For more information, refer to the "Agile Content Service Settings" chapter in the Agile PLM Administrator Guide.

To see the details about the selected filter, click the corresponding Details button. If you select the Use predefined filter option, but you do not select filters to use, the Export Wizard uses the default customized filters. See Working with System Default Filters on page 142.

For items and changes, only filters for the superclasses (Item and Change) are included in the Export filter lists. Filters defined specifically for classes-for example, part, document, ECO, and MCO-are not included in the Export filter lists. For example, if your export file includes an ECO and an ECR, the Change filter that you select, will apply to both objects. Similarly, if your export file includes a part and a document, the Item filter that you select will apply to both objects.

### 11.7.2 Specifying Filters When Exporting Attachments

Filters for exporting attachments are specified in Java Client, and described in Exporting Object Attachments on page 145. For aXML and PDX, when the Attachments tab is included in the Viewable Tabs list of Agile PLM's Create Filter dialog, the dialog's Attachments Options selection is enabled, and you can select Tab Only, or Tab and Files. If you select Tab and Files, you can provide a comma-separated list of file extensions to be included in the export output file. Filtering exports by file type gives you the option to exclude certain file types such as CAD diagrams when exporting BOM type data to your suppliers. See the illustration in Creating Custom Filters on page 140.

### 11.7.3 Creating Custom Filters

Custom filters enable specifying export tabs for the type of object that you have selected for export. If you have the necessary Export privileges, you can create a custom filter in Step 2 of Web Client's Export Wizard, provided the PLM Admin has configured these privileges in the Java Client. For example, if you select the PDX, or aXML format in step1, then in step3, you can select Attachments, or Attachment Files, and specify the File Extensions as shown in the following illustration. You can also set the option to customize your filter for exporting Redline Content.

Figure 11-2 Specifying file extensions to export data

Note: You cannot save this type filter for futures use. You can only use it in the current export action.

### 11.7.4 Working with BOM Filters

When you choose to include BOM information in the export file, you must specify the level of BOM information by selecting from the following options:

- Tab Only (saved filters, set by the Administrator) or BOM Tab (custom filters) - For all formats, it includes the information in the BOM tab itself, with only references to the items on the BOM tab (first level only). If this BOM option is the only one selected, the BOM items themselves are not included.

- Tab and Items

  - Tab and Items, All Levels (saved filters, set by the Administrator) or BOM Items, All Levels (custom filters) - For PDX and aXML formats, includes all items in all levels of the BOM. For Excel and CSV format, includes references to the items on all levels of the BOM tab, but does not include the items themselves.

  - Tab and Items, BOM Level (saved filters, set by the Administrator) or BOM Items, BOM Level (custom filters) - For PDX and aXML formats, includes the items on the specified level (1, 2, ..., last) of the BOM. Does not include child components of subassemblies. For Excel and CSV format, includes references to the items on the specified level of the BOM tab, but does not include the items themselves.

### 11.7.5 Working with System Default Filters

The System Default filters are the same as those that are used if you choose Customize and then proceed through each filter step without changing the settings.

If you create an export file without specifying the content filters to use, the Export Wizard follows these guidelines:

- If you download the export file in step 1 of the Wizard, the content to be exported is filtered according to System Default filters.

- If you download the export file in step 2 of the Wizard, content is filtered according to the selection made in step 2. In this case, if you select Customize, but you don't then proceed through the steps that define those filters, Export uses the System Default filters. If you select Predefined filter, but you do not select filters to use, the Export Wizard uses the System Default filters.

If you use the System Default filters, the export file contains the following information:

- Items - Title Block, Page Two, Page Three, Compliance, Suppliers, BOM tab (and all levels of BOM items), Manufacturers, Item Prices, Sites, Attachments (and attached files, if the export format is PDX or aXML)

- Manufacturer parts - General Info, Page Two, Page Three, Attachments (and attached files, if the export format is PDX or aXML)

- Manufacturers - General Info, Page Two, Page Three, and Attachments (and attached files, if the export format is PDX or aXML)

- Changes - Cover Page, Page Two, Page Three, Affected Items, Attachments (and attached files, if the export format is PDX or aXML)

- Prices - General Info, Page Two, Page Three, Price Lines, Attachments (and attached files, if the export format is PDX or aXML)

- Substance - General Info, Page Two, Page Three, Composition, Attachments (and attached files, if the export format is PDX or aXML)

- Declaration - Cover Page, Items, Page Two, Page Three, Item Bill of Substances, Manufacturer Parts, Manufacturer Part Bill of Substances, Part Groups, Part Group Bill of Substances, Compliance, Attachments (and attached files, if the export format is PDX or aXML)

- Specifications - General Info, Page Two, Page Three, Substances, Attachments (and attached files, if the export format is PDX or aXML)

- Part Groups - General Info tab, Page Two, Page Three, Parts, Compliance, Suppliers, Attachments (and attached files, if the export format is PDX or aXML)

- Program - General Info, Dependencies Dependent Upon, Team, Dependencies Required For, Discussion, Action Items, Page Two, Schedule, Page Three

- Product Service Requests - Relationships, Affected Items, Attachments (and attached files, if the export format is PDX or aXML), Related PSR, Page Three, Cover page, Page Two

- Quality Change Requests - PSR Item, Relationships, Cover page, Affected Items, Page Two, Attachments (and attached files, if the export format is PDX or aXML), Page Three

- Discussions - Discussion, Page Two, Page Three

- Users - General Info tab, Page Two, Preferences, User Group

- User Groups - General Info tab, Page Two, Users, Page Three

## 11.8 Exporting PLM Objects

The following paragraphs document exporting the respective supported file formats for these objects.

### 11.8.1 Exporting PSR, QCR, and Supplier Objects

Once you have selected the object type, the procedures and options to export the selected PLM object are essentially the same. The supported tables and components are:

- Product Service Requests - Cover Page/Page 1, Page Two, Page Three, Affected Items, Related PSR, Relationships, Attachments, and History. Supported file formats are: CSV/Excel and aXML

- Quality Change Requests - Cover Page/Page 1, Page Two, Page Three, Affected Items, Relationships, Attachments, and History. Supported file formats are: CSV/Excel and aXML

- Suppliers - General Information, Page Two, Page Three, Contact Users, RFX Routing, Manufacturers, Commodities, PSRs, Relationships, Attachments, and History. Supported formats are: CSV/Excel and aXML

To export PSR, QCR, or Supplier objects:

1. Choose and open the target object (PSR, QCR, or Supplier).

2. Choose Actions > Export for the target object.

3. In Select Objects to Export, select the applicable file type from Export to (aXML, Text (CSV), or Excel) > Next.

4. In Select Content Filters, select the applicable filter. Click Next.

5. In Specify Export Properties step, specify Type and provide the applicable description. This is optional.

6. Click Export to complete the process.

### 11.8.2 Exporting Redline BOMs and AMLs for Affected Items

If you choose the PDX or aXML export formats, an additional filtering option called Redline Changes Only is available when you export Change objects. This option indicates that only changed BOM elements should be included in the redline section of the affected items of the changes. Unchanged elements will not be included. The exported PDX or aXML file could then be used to communicate BOM and AML changes to supply chain partners.

This feature is targeted for ERP adaptors that process deltas. Agile Content Service (ACS) can be used to send the exported PDX or aXML file to an ERP adaptor.

To export redline BOMs and AMLs:

1. Open a Change object (such as an ECO).

2. Choose Actions > Export.

3. Choose PDX as the export format. Click Next.

4. On the Filters page of the Export Wizard, click Create Custom filter. Click Next.

5. On the Filter Changes page, make sure both the Affected Items Tab > Affected Items and the Redline Changes Only boxes are checked.

   Figure 11-3 Export Wizard's Select Change content to export

6. Click Next to set additional settings.

7. Click Export to complete the process.

### 11.8.3 Exporting Relationships Tables of Objects

You can export relationship tables containing Item, Change, Manufacturer, Manufacturer Part, and Part Group objects as CSV/Excel or aXML files. For the aXML file format, there are two additional tags ControlObjStatus and EffectObjStatus to represent the relationship rule. The exported aXML files can be imported back into the same or another system.

For information on Relationships tables, refer to Getting Started with Agile PLM. For procedures, see Export Wizard Steps.

### 11.8.4 Exporting Multiple Revisions of the Same Item

Export will output multiple revisions of the same item in the order of their respective revision release dates. Pending revisions will appear first in the output file. They are followed by the released revisions from earlier releases to the most recent.

### 11.8.5 Exporting Object Attachments

The Export privilege alone does not enable you to export PLM data to PDX or aXML file formats. To export attachment tab data to these formats, the PLM Admin, when configuring the privileges for the user, must select the Attachments option in an Export privilege mask's Applied to field. The default out of the box privileges are shown in the following figure.

Figure 11-4 Default out of the box Export privileges

The Attachments option is already selected for the default (Restricted) Export and Export Privileges. PLM administrators can remove or select the Attachments option for these privileges and any new privileges that they create. For information and procedures to assign roles and privileges, refer to the PLM Administrator Guide.

Figure 11-5 Managing user Export privileges

### 11.8.6 Exporting User Groups and Users Objects

Classes and subclasses in User Group are:

- Functional Teams class and Functional Team subclass

- User groups class and User Group subclass

Classes and subclasses in Users are:

- users class and user subclass

Note: You can additional information about these classes and subclasses in Agile PLM Administrator Guide.

You can export these objects using the Export Wizard. When exporting users class data, the Export function displays Functional Teams and User Groups data in the User Groups / Functional Teams page.

Figure 11-6 Exporting user group and functional team data

Similarly, when exporting User groups class data, the Export function displays the Functional Teams data.

Note: The Functional Teams class does not provide the information in Actions menu's Where Used tab. However, you can export this data using the Export button in the Where Used tab.

### 11.8.7 Exporting Reference Objects Relationships Data

Exporting the Relationships data for Reference Objects (Agile to Agile) is similar to exporting the Relationships Table of PLM objects. For more information, see Exporting Relationships Tables of Objects (on page 145) and Exporting Multiple Revisions of the Same Item on page 145.

### 11.8.8 Setting the Maximum Number of Objects to Export

This value is the maximum number of objects that you can export. The default is "0" and indicates there are no limits and all objects in the BOM are exported. The maximum number is set by your PLM Admin or a user with Admin privileges and serves to minimize excessive utilization of system resources caused by exporting large numbers of objects. For more information on Preferences and the number of objects that you can export, refer to the Agile PLM Administrator Guide.

To set the Maximum number of objects to export:

1. In Java client, select Admin > Server Settings > Preferences.

   Figure 11-7 Preferences dialog's General Information page

2. In General Information page, locate the Maximum number of objects to export and change the default value of "0" or an existing setting to the required value.

   Note: The maximum number that is set above is used when an export is executed. An estimate of the number of objects in the export request and the associated BOM items (if requested) is compared to the maximum that was set. If the estimated number of objects exceeds the maximum value, then export is terminated and an error message is displayed.

## 11.9 Specifying Headers

On the Specify Export Properties page of the Export Wizard, you can specify optional header information that describes the export file. Enter values in the Type and Description fields. The Creator field is filled automatically with your name.

## 11.10 Downloading Files

You can choose to download the export file at any step of the Export Wizard without completing the remaining steps. If you did not specify filtering information before downloading the export file, see Working with System Default Filters on page 142 System Default Filters for information on the default filters that are used.

To download the export file:

1. In the Export Wizard, click Export.

2. Click Save to save the file to your computer.

Browser's Save dialog appears.

## 11.11 Viewing Exported Files

If you export a text file, you can view it in a spreadsheet program, like Microsoft Excel, or in any text editor. If you export a PDX package, you can view it using Agile eXpress or another PDX-enabled application.

You can download the free Agile eXpress viewer from the following Web site:`http://www.oracle.com/technetwork/apps-tech/index-097651.html`