agile advantage - oracle cloud · 2008-11-18 · agile advantage 2006 4 user guide stage 5: using...

Agile Advantage™

DataLoad Guide

August 2008

v2006 SP4

Part No. E12871-01

Agile Advantage 2006

Copyright © 1995, 2008, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.

CONTENTS

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iTTY Access to Oracle Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .iReadme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiAgile Training Aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiAccessibility of Code Examples in Documentation . . . . . . . . . . . . . . . . . . . . . . . . . iiAccessibility of Links to External Web Sites in Documentation . . . . . . . . . . . . . . . ii

Chapter 1 Introduction

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Installing Agile DataLoad 2006 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Installing Agile DataLoad with Microsoft Access 2000 . . . . . . . . . . . . . . . . . . . . 1-3Database Conversion for Microsoft Access 2000 . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Enabling Data Loading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Chapter 2 Using Agile DataLoad

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Agile DataLoad Process Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Stage 1: Exporting Legacy Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Stage 2: Configuring the Agile Advantage Database . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Stage 3: Creating the Microsoft Access Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Stage 4: Importing Data Into Microsoft Access Tables . . . . . . . . . . . . . . . . . . . . . . . 2-15Table Populating Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17BOM History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

3


Stage 5: Using the Data Mapper Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Step 1: Database Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Data Mapper Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Step 2: Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Drag and Drop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Automap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Field Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Table Map. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Mapping Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Overwriting Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Step 3: Copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Step 4: Modular Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Generating Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Importing BOMs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Import BOM Table Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

Stage 6: Configuring the List Attribute Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Stage 7: Validating the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34Step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34Step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Viewing Validation Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Stage 8: Loading Data into Agile Advantage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40Step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40Step 2 (Loading) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41Step 3 (Loading) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42Rollback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Revising and Reloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44Notes on Loading Order. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45Running SQL Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48

Stage 9: Importing at the Customer’s Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49

Chapter 3 Loading BOM History

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Agile BOM Table Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

4 User Guide

Contents

SOURCE Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6Preparing the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Loading without BOM History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12SmartRules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Appendix A Agile DataLoad Field Configuration

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2Table Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Appendix B Agile DataLoad Field Configuration

SOURCE_Item Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3SOURCE_Change Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8SOURCE_Rev Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14SOURCE_BOM Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-16SOURCE_Manufacturer Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-18SOURCE_Mfr_Part Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23SOURCE_Approved_Mfr Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-28SOURCE_User Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-30SOURCE_RefDesig and SOURCE_RefDesig_2 Tables . . . . . . . . . . . . . . . . . . . . . . . A-32SOURCE_Customer Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-33SOURCE_ProblemReport Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-35

Appendix C Validations

Agile Administrator Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2Special Characters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3Referential Integrity Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3Rules and Validations for Reference Designators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9

Single Reference Designator Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9Reference Designator Range Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9Validations for Reference Designators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-11

Customer Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12Problem Report Validations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12Changes in Final Status Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13

Index

5


6 User Guide

Preface

The Agile Advantage documentation set includes Adobe® Acrobat™ PDF files. The Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/documentation/agile.html) contains the latest versions of the Agile Advantage PDF files. You can view or download these manuals from the Web site, or you can ask your Agile administrator if there is an Agile Advantage Documentation folder available on your network from which you can access the Agile Advantage documentation (PDF) files.

Note To read the PDF files, you must use the free Adobe Acrobat Reader™ version 7.0 or later. This program can be downloaded from the Adobe Web site (http://www.adobe.com).

If you need additional assistance or information, please contact Customer Support (http://www.oracle.com/agile/support.html) for assistance.

Note Before calling Agile Support about a problem with an Oracle|Agile Advantage manual, please have the full part number, which is located on the title page.

TTY Access to Oracle Support Services

Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, 7 days a week. For TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.

Readme

Any last-minute information about Agile Advantage can be found in the Readme file on the Oracle Technology Network (OTN) Web site (http://www.oracle.com/technology/documentation/agile.html).

i

http://www.oracle.com/technology/documentation/agile.html


http://www.oracle.com/agile/support.html



http://www.oracle.com/agile/support.html

http://www.adobe.com




Agile Training Aids

Go to the Oracle University Web page (http://www.oracle.com/education/chooser/selectcountry_new.html) for more information on Agile Training offerings.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

ii

http://www.oracle.com/education/chooser/selectcountry_new.html


iv


vi

CHAPTER 1Introduction

This chapter introduces Agile DataLoad 2006 and discusses how to install it. The following subjects are discussed:❑ Overview❑ Requirements❑ Prerequisites❑

1-1

Agile DataLoad 2006

OverviewImplementing Agile Advantage includes the process of getting data and physical files from existing legacy systems and transferring this information electronically into the Agile Advantage database and file system. Agile Advantage requires certain information to be transferred to set up the relationships between Items, BOMs, Manufacturers, and Change objects. The process of loading information usually requires several iterations.

Agile DataLoad 2006 is a tool used to get all the metadata into the Agile database by means of intermediate Microsoft Access tables. Another tool, Agile FileLoad 2006, is used to load files. Together, Agile DataLoad and Agile FileLoad ensure that the integrity of the Agile Advantage database is maintained.

Note For more information about Agile FileLoad, refer to the Agile Advantage 2006 Installation and Maintenance Guide.

Agile DataLoad 2006 is for use by Agile Certified Professionals only.

RequirementsThe following requirements must be met to use Agile DataLoad 2006:

❑ DataLoad must be installed on either Microsoft Windows 2000 Professional Service Pack 4, Microsoft Windows XP Professional (Service Pack 2), or Microsoft Windows Server 2003 Standard Edition (Service Pack 1).

Note Agile Advantage is not certified or tested on Microsoft Windows Server 2003 x64 Editions.

❑ Microsoft Access 2000 or 2003 must be installed before or after you install Agile DataLoad 2006.

Agile DataLoad uses Microsoft Access to hold and transfer legacy data into the Agile Advantage database.

❑ An Agile Administrator user account with Administrator privileges to load legacy data into the Agile Advantage database.

❑ A full Agile Advantage user license to log in to Agile DataLoad 2006.

1-2 User Guide

Chapter 1 Introduction

PrerequisitesYou need a clear understanding of the Agile Advantage 2006 Windows client and Agile Administrator 2006, and how information is organized and manipulated in those products, to perform the Agile DataLoad migrations.

You also need some experience using Microsoft Access. You use Microsoft Access database tables to create properly formatted tables for the legacy data, and to revise and reload any legacy data that may be rejected from loads to Agile Advantage.

Installing Agile DataLoad 2006

DataLoad is installed using the Agile Advantage installation program. If you have a serial number that is authorized to use Agile DataLoad, the component is available in the list of Agile DataLoad components during installation.

Installing Agile DataLoad with Microsoft Access 2000

Using Agile DataLoad 2006 with Microsoft Access 2000 also requires Microsoft DAO 3.6. DAO 3.6 is installed automatically when you install Agile DataLoad. If it does not install automatically or if you have difficulties starting Agile DataLoad 2006 after installation, contact Agile Customer Support.

Database Conversion for Microsoft Access 2000

If you are creating a database with Agile DataLoad for use with Microsoft Access 2000, an additional procedure is required.

Important First, you must create the database with Agile DataLoad 2006, as described in the next chapter. Then, you must open the database with Microsoft Access 2000, select the Convert option, and then save it as a new file. Once you have completed this process, you can no longer open the database with Microsoft Access 97.

1-3

Agile DataLoad 2006

Enabling Data Loading

Agile DataLoad 2006 can be used to configure the tables for loading data and to perform validations on the data. However, the option to actually load the data is disabled by default; the Load Configured Access Database item in the main window is grayed.

To enable the data loading feature of DataLoad, use the command line utility agrn.exe. This utility is installed automatically with Agile DataLoad 2006.

To enable data loading:

1 Open a Command Prompt window.

2 Navigate to the folder containing the DataLoad program files.

3 Type the following command, and press Enter:

agrn anywhereisright

4 Type exit and press Enter to close the Command Prompt window.

To disable the Load Configured Access Database item, follow these same steps, except type the command agrn off.

1-4 User Guide

CHAPTER 2Using Agile DataLoad

The instructions in this chapter are for qualified Agile Advantage system implementation specialists who need to load legacy data from existing customer applications into the Agile Advantage database.The following topics are included:❑ Overview❑ Agile DataLoad Process Outline❑ Stage 1: Exporting Legacy Data❑ Stage 2: Configuring the Agile Advantage Database❑ Stage 3: Creating the Microsoft Access Tables❑ Stage 4: Importing Data Into Microsoft Access Tables❑ Stage 5: Using the Data Mapper Wizard❑ Stage 6: Configuring the List Attribute Values❑ Stage 7: Validating the Data❑ Stage 8: Loading Data into Agile Advantage❑ Stage 9: Importing at the Customer’s Site❑ Checklist

2-1

Agile DataLoad 2006

OverviewAgile DataLoad 2006 helps you prepare properly formatted Microsoft Access transitional import data source tables. After you populate the Microsoft Access tables with your legacy data, Agile DataLoad uses them to load the Agile Advantage database.

The Microsoft Access tables represent the structure of the Agile Advantage objects, as shown in the following table:

Table 2-1: Microsoft Access table structure

Microsoft Access Agile Advantage

SOURCE_User User metadata

SOURCE_Item All Parts and Documents and their metadata

SOURCE_Change All Part and Document Changes and their metadata

SOURCE_Rev All Part and Document Revisions and their metadata

SOURCE_BOM All BOM configurations and their metadata

SOURCE_RefDesig RefDesig data in single-row format

SOURCE_RefDesig_2 RefDesig_2 in BOM ID validation data

SOURCE_Manufacturer All Manufacturer metadata

SOURCE_Mfr_Part All Manufacturer Part metadata

SOURCE_Approved_Mfr Approved Manufacturer list for Manufacturer Part metadata

SOURCE_Customer All Customer metadata

SOURCE_ProblemReport All Problem Report metadata

SOURCE_Supplier All Supplier metadata

SOURCE_Contact All Contact metadata

2-2 User Guide


Agile DataLoad Process OutlineThe following figures illustrate the Agile DataLoad process during the first pass and subsequent passes.

Figure 2-1: First Agile DataLoad pass

2-3

Agile DataLoad 2006

Figure 2-2: Subsequent Agile DataLoad passes

2-4 User Guide


The stages of the process, shown in Figure 2-1 and Figure 2-2, are outlined below and explained in detail in the sections that follow.

Stage 1: Exporting Legacy Data (page 2-6). Export the legacy data from your existing ERP system or similar source. You can use a comma-delimited format, or a format delimited by some other character such as the pipe or vertical bar ( | ). Choose a delimiter that is not used in the data. You can also choose fixed width, although a fixed-width format can result in large files. Edit the legacy data export files for proper form and content prior to importing them into Microsoft Access tables. Typically, the customer is responsible for providing legacy data extracts in an agreed-upon format.

Stage 2: Configuring the Agile Advantage Database (page 2-7). Use Agile Administrator to establish settings that configure the Agile Advantage database. These settings include whether a field is required or not, a field’s maximum length or data type, Page 2 and Page 3 design, and list and multilist field names (but not values). After completing this stage, the Agile Advantage database is partly configured; the remainder of the configuration occurs in Stage 5.

Stage 3: Creating the Microsoft Access Tables (page 2-8). In DataLoad, select Agile Advantage fields to be populated with legacy data. Then, Agile DataLoad creates three sets of empty Microsoft Access transitional source tables to use for importing the legacy data.

Stage 4: Importing Data Into Microsoft Access Tables (page 2-15). In this stage, make sure the source files and data are properly formatted to be placed in the SOURCE tables. You then map fields and populate the skeleton Microsoft Access tables with the exported legacy data.

Stage 5: Using the Data Mapper Wizard (page 2-17). The Data Map Wizard converts data from the user-created intermediary tables to the SOURCE tables, and from intermediary fields to SOURCE fields for each table.

Stage 6: Configuring the List Attribute Values (page 2-28). To finish configuring the Agile Advantage database, specify what values are available in the list and multilist fields. This stage is necessary to ensure that list values are available for Agile DataLoad to use. For example, if Unit of Measure is mapped to List01 in Agile Advantage, and there is a value in the extracted data for unit of measure that was not in the configured list, then Agile DataLoad flags this value as an error. Agile DataLoad can provide a report of distinct values for lists, multilists, table attribute values, and user-defined subclasses unique to the legacy system.

2-5

Agile DataLoad 2006

Stage 7: Validating the Data (page 2-33). Specify the validations you want and whether you want to include data from the Agile Advantage database in the validation process. Validating the data before loading the Microsoft Access tables greatly increases the success rate for the loading process, and should always be performed during the data load process.

Stage 8: Loading Data into Agile Advantage (page 2-40). Import the Microsoft Access legacy data tables into Agile Advantage using Agile DataLoad. Error tables are generated and added to the Microsoft Access database during import. Then revise data in the Microsoft Access error tables, if necessary, and update the Agile Administrator values. Reimport the error tables. If additional errors are generated, revise and reimport. Repeat until all legacy data has been loaded to your satisfaction. Finally, run SQL scripts to set up the database and verify its integrity.

Stage 9: Importing at the Customer’s Site (page 2-49). If necessary, export the database from Agile Advantage, and import it at the customer’s site.

Detailed discussion of these stages makes up the remainder of this chapter. There is a checklist at the end of the chapter to help you keep track of the steps.

Stage 1: Exporting Legacy DataUse Agile DataLoad to populate Microsoft Access skeleton data tables with legacy data contained in comma-delimited or fixed-width text files. Use the ERPGuidelines.doc file (available in the Alliance Resource Center) for information on specifying the format for data extracts.

❑ To create the comma-delimited legacy data files, open the database or spreadsheet application currently used to hold legacy data (such as Microsoft Excel, for example), and export the existing data in comma-delimited text format. Follow the instructions in the documentation for that application. It is usually helpful to include field names.

❑ Review the exported files and edit them in an agreed-upon format. In most implementations, the customer is responsible for generating the legacy extracts, as the customer often has staff knowledgeable about the legacy system.

Note If description fields contain commas, it may be preferable to use another character, such as the pipe or vertical bar ( | ), as the delimiter. If carriage return (CR) or line feed (LF) characters exist in the data to be loaded, you may want to replace them with special characters that can be found and replaced after completing the load using SQL.

2-6 User Guide


Stage 2: Configuring the Agile Advantage DatabaseBefore you can use Agile DataLoad to load the Microsoft Access SOURCE tables, you must use Agile Administrator to configure the Agile Advantage database. The attribute properties you specify at this time include attribute names, whether the attribute is required or not, the attribute’s maximum length or data type, the Page 2 and Page 3 design, and List attribute names (but not values, which are established in Stage 5). Refer to “Defining Attributes” in Chapter 5 of the Agile Administrator 2006 User Guide.

Note If you are creating a new Agile Advantage database, use the AutoUpdate2006.exe tool (located under your <Agile Home>\tools directory) to first import your 2005 database and then update it to 2006. Follow the procedures in the Agile Advantage 2006 Installation and Maintenance Guide. This tool establishes the structure of the Agile Advantage database. After the database is created, you can use Agile Administrator to create appropriate list values, design Page 2, and so on.

Many times databases are configured based on input expectations. The legacy data may not contain all the data that is required. You will need to set these fields to Not Required in order to successfully load the database.

Refer to the Agile Administrator 2006 User Guide for details about configuration.

2-7

Agile DataLoad 2006

Stage 3: Creating the Microsoft Access TablesNow you are ready to start Agile DataLoad to create and configure Microsoft Access data tables. Within this stage, there are several steps with their corresponding dialog boxes.

Step 11 From the Windows desktop, choose Start | Programs | Agile Advantage 2006 |

Agile DataLoad 2006. The Step 1 (Configuring) dialog box appears.

Figure 2-3: Agile DataLoad - Configure New Database (Step 1)

2 Choose Configure new Access Database. Click Next.

2-8 User Guide


Step 2

The Step 2 (Configuring) dialog box appears.


1 Type a name for your Microsoft Access database file. For example, use <company name>#.mdb as the name (replace # with the revision pass number, if you are doing multiple DataLoad passes).

Note New DataLoad files are created in Access 97 format. When you open the file in Access 2000, you will be prompted to convert the file to Access 2000 format.

2 Type a description and any notes that are relevant. For example, provide the Agile DataLoad pass and date in the Description field. Provide any special changes incorporated for this pass in the Notes field. This information is useful if you are performing successive passes.

3 Click Next.

2-9

Agile DataLoad 2006

Step 3

The Step 3 (Configuring) dialog box appears.


The Step 3 dialog box lists tables for each of the Agile Advantage classes and their required fields, and contains a button for selecting optional fields. The required fields appear when you select a table from the Tables list to the left.

Agile DataLoad reads the server values for required and optional fields. If a field is required, even for a single subclass, it is required for the whole table. Required fields must have a value during the Load process, even if they are not set to Required in Agile Administrator.

1 Select each Agile Advantage class table from the Tables list on the left. A list of the required fields for each table appears on the right.

Note The legacy data must contain fields and data for each required field.

2 To identify the optional fields needed to load legacy data, click Select Optional Fields, or double-click a class table name. The Select Optional Fields window appears.

2-10 User Guide


Figure 2-6: Select Optional Fields

Important You must make sure that Agile Advantage target classes and subclasses exist for all legacy data fields that are to be imported into the Agile Advantage database. For more information about optional and required fields, refer to Appendix A, “Agile DataLoad Field Configuration.”

3 Click Select All when you want to create empty columns for all fields.

4 Click Next after you have selected the optional fields needed for each source table.

Step 4

The Step 4 dialog box appears.

2-11

Agile DataLoad 2006


To create the skeleton Microsoft Access data tables for your legacy data:

1 In the Step 4 dialog box, click View Configuration to review the fields that are placed in the skeleton source tables, based on your selections in Step 3 (Configuring). If you need to make any changes, you can close the Configuration Information dialog box and click Back to revise the information.

Figure 2-8: Configuration Information Dialog Box

2 To populate the description table with attribute values and names from the Agile Advantage server, check Populate Description (DESC_Admin) table. You are prompted to enter a username and password. You can use this table to see what

2-12 User Guide


attribute names the Agile Advantage user will see for each attribute type. Checking this option also makes several reports available (refer to “Reports” on page 2-16).

3 Check Open Database with MS Access to view the database once it has been created.

Note If you are using Microsoft Access 2000 or 2003, you are prompted to convert and rename the file.

4 Click Finish. Microsoft Access starts. Your skeleton tables appear in a Microsoft Access Database window. Agile DataLoad moves to the background on your desktop and waits for you to finish populating the data tables.

Figure 2-9: Access Database View

The Microsoft Access Database window shows skeleton tables for each of the Agile Advantage classes. Each class has a source table and an error table, and there is a DESC_ADMIN table.

2-13

Agile DataLoad 2006

Table 2-2: Tables For Each Class

Tables Description

SOURCE_BOMSOURCE_ChangeSOURCE_Item SOURCE_RevSOURCE_ManufacturerSOURCE_Approved_MfrSOURCE_Mfr_PartSOURCE_RefDesigSOURCE_RefDesig_2SOURCE_User SOURCE_CustomerSOURCE_ProblemReport

Source tables: At this point in the process, only column headers appear in these tables. They are empty “skeletons” waiting for you to populate the rows with legacy data. These tables are where you place the legacy data for loading into the Agile Advantage database.

ERROR_BOM ERROR_ChangeERROR_Item ERROR_RevERROR_ManufacturerERROR_Approved_MfrERROR_Mfr_Part ERROR_User ERROR_CustomerERROR_ProblemReport

Error tables: Any errors generated while loading a SOURCE_<tablename> are logged in the corresponding ERROR_<tablename>. These tables are also empty skeletons; however, you do not populate them. Later, when you load your populated SOURCE tables, DataLoad writes the rejected lines of data to these ERROR tables. The error reason is logged in the ERROR_DESCRIPTION field, and the appropriate action may be taken to fix the error. Typical fixes range from making required changes in Agile Administrator, to programmatically fixing the data, to excluding the data from DataLoad. Once you have revised the rejected rows, you can use DataLoad to reload the data directly from these tables.

DESC_Admin Description table: This table contains the Agile Advantage database field mapping descriptions. They may help you determine the appropriate Agile Advantage fields to target for legacy data fields. If you did not check the Populate Description Table checkbox in Step 5 (page 2-11), only the attribute IDs and generic names appear in this table.

DATA MAPPER ERROR LOG If a mapping is invalid during an Automap, Field Map or Table Map, errors are logged to the Data Mapper Error Log table.

VALID REFDESIG PREFIXES Reference Designators: If selected, these can be used to populate the reference designator field.

VALIDATION_ERRORS This table contains validation error data.

2-14 User Guide


Stage 4: Importing Data Into Microsoft Access TablesUse the Microsoft Access external data import feature to import your legacy data, class by class or file by file, from your comma-delimited legacy data files into the Microsoft Access skeleton data tables. If your data is in Excel files, export the data to delimited text files before importing into Microsoft Access. See “Stage 1: Exporting Legacy Data” on page 2-6.

To import data into Microsoft Access:

1 Examine the skeleton SOURCE tables created in the previous Stage, and the legacy data export files from Stage 1.

Consider how the legacy data will fit into the fields in each table. Make sure the legacy data is correctly formatted for import into the Microsoft Access target tables. Refer to Appendix A, “Agile DataLoad Field Configuration,” for detailed information about allowed legacy field content and types.

2 In Microsoft Access, choose File | Get External Data | Import.

3 Follow the steps in the Microsoft Access Import Text Wizard to load the legacy data files into Microsoft Access.

• Select the format of the data (comma-delimited or fixed width).

• If the first row of your legacy data contains field names, select that option.

4 Refer to Appendix B for information about how to validate record dependencies before uploading Microsoft Access tables to the Agile Advantage database.

Table Populating Hints

Some methods that may make it easier to import legacy data into Microsoft Access:

Note See Appendix B, “Validations,” for additional information on accepted rules for fields and values.

❑ Create customer tables first, then use the Data Mapper Wizard to load the source tables into the customer tables.

2-15

Agile DataLoad 2006

❑ The skeleton table data types are set by DataLoad. Data type mismatches between the target skeleton table and the legacy data source file results in type conversion errors. If your raw legacy table fields do not have the same types, you must convert them when you populate the skeleton tables. Integer data must go into integer type fields, date data must go into date type fields, text to text, and so on.

❑ If a Microsoft Access database has not been compiled correctly then Microsoft Access displays the error message:

Microsoft Access has converted the code in your database to your current version of Visual Basic to improve the performance of this db.

To avoid this error, make sure your databases are fully compiled before you import them into Microsoft Access.

❑ When you load the populated source tables into Agile Advantage, Microsoft Access creates error tables that list import problems row by row. Use those tables to solve legacy data problems and reimport the error tables, as explained in “Revising and Reloading” on page 2-44.

❑ Required fields must contain data, and the data must be in the proper form for the field data type. You can use the DESC table to check the field mappings, or you can look at the attribute values in Agile Administrator if you need to determine what data needs to be in the required fields. The validation process detects required field faults. The data for list fields, character fields, and sub-character fields must match exactly.

❑ You may find that unique date or serial numerical values have yet to be obtained from the original legacy database. If this is the case, you may find it easier to reconfigure the original legacy database export files, and start over.

Reports

If you checked the Populate Description (DESC_Admin) Table checkbox, several reports are available. These reports include All Classes, Change Orders, Change Requests, Deviations, Documentation, Manufacturer Orders, and others. These reports can be used to generate documentation of the implementation. Click the Reports tab in Microsoft Access to use these reports.

In addition, validation reports are generated following the validation process. Refer to “Viewing Validation Reports” on page 2-39.

2-16 User Guide


Revision History

It is important to understand how Agile Advantage stores revision history information. The obsolete date for a given revision is entered on the record for that revision. It should reflect the release date of the next revision.

In the records shown above, the Effective_Date in the Rev 01 record is the date that Rev 00 became obsolete. If this is the case, you can use the data as derived by the customer. You may need to manipulate the data in the Microsoft Access tables to make it conform to the Agile convention before loading the data into Agile Advantage.

Note This is a change from previous instructions about Obsolete_Date.

BOM History

At this time, Agile DataLoad supports loading BOM history records. If you need to perform this task, refer to Chapter 3, “Loading BOM History.”

Stage 5: Using the Data Mapper WizardThe Data Mapper wizard performs four key functions:

❑ Copies data between tables within a given Microsoft Access database

❑ Displays eHub attribute values for the corresponding fields

❑ Performs basic data cleanup operations

❑ Allows you to create an email message that is automatically sent when the Validation or Load process has finished, with the option of appending the operation results (Validation or Load) to the message

Table 2-3: Revision history example

Part Rev Effective_Date Obsolete_Date Change

1003 00 09-AUG-2005 24-NOV-2005 DCN3010

1003 01 24-NOV-2005 DCN3011

2-17

Agile DataLoad 2006

Step 1: Database Selection

The first step in the Data Mapper Wizard is to select which Microsoft Access database you wish to manipulate. In addition to displaying the selections available, the wizard lets you open the database in Microsoft Access, edit the notes for the database file, or add additional databases to the list. Click Next.

Figure 2-10: Agile DataLoad - Data Mapper (Step 1)


2-18 User Guide


The user interface consists of three panes:

❑ The Copy From pane displays all tables from which data can be copied.

❑ The Copy To pane displays all tables to which data can be copied.

❑ The Properties pane displays information about the current selection.


The Copy From pane contains user specific tables created by the user. The Copy To pane contains the SOURCE_ tables. In addition, the Copy From pane displays all QueryDefs (queries) defined in the database. All three areas are described in the following steps.

Data Mapper Options

Several options for modifying database tables are available in the Options section of the Data Mapper Options window.

2-19

Agile DataLoad 2006

Figure 2-13: Agile DataLoad Data Mapper Options

All settings are universal and apply to all tables accessed by the Data Mapper wizard:

❑ Confirm Unmaps: If checked, you are prompted for confirmation before a node is unmapped.

❑ Confirm Overwrites: This applies when you run an Automap, Load Field Map or Load Table Map. If checked, you are prompted for confirmation before overwriting current, conflicting mappings.

❑ Maximum number of records to display: This specifies how many records to display when you select the pop-up menu command Show Data for a table node.

❑ Show All Tables: By default, the Copy From pane contains the user-specific tables and the Copy To pane contains the SOURCE_ tables. The Show All Tables option displays all tables (except system and hidden) in both the Copy From and Copy To panes, allowing you to control which tables are copied.

A benefit of this option is that it allows users to export their SOURCE_table data to linked tables, or copy data from and to any linked table, such as from a linked text file to a linked Excel file. You can copy data from any file format to any other format. Linking a table requires walking through a short Microsoft Access wizard, but the procedure is straightforward and simple. Microsoft Access currently supports the following formats for linked tables:

• Microsoft Access

• dBase III

• dBase IV

• dBase V

• Microsoft Excel

2-20 User Guide


• Microsoft Exchange

• HTML

• Outlook

• Paradox

• Text files

• ODBC databases

Note You should further investigate linking to or from ODBC databases and copying data between them to be fully aware of all the implications. Normal tables appear with the Unlinked icon, and linked tables appear with the Linked icon. When a field or a table is mapped in the Show All Tables view, the other pane is disabled to prevent inconsistent or unintuitive mappings.

Step 2: Mapping

Before data can be copied between tables, you must map the database tables. You can do this in several ways.

Drag and Drop

Each table node contains subnodes for all fields in that table, and you can drag and drop these fields to map them. Once a field is mapped, no drag operations are allowed on that field until it has first been explicitly unmapped.

Automap

The Automap option, which automatically maps source and target fields with the same name, is available through the Map tables window, which appears when you drag and drop a table node onto another table node.

2-21

Agile DataLoad 2006

Figure 2-14: Map Tables

Field Map

A Field Map is a list of mapped field names that ignores the names of the two mapped tables. This window allows you to load a Field Map between any two tables. You can save the map using this window, or you can right click a table node, which displays a shortcut menu containing a Save Field Map command.

Table Map

A Table Map is the set of all Field Maps for all mapped tables, and you can load and save it by right-clicking the Tables node and choosing Save Table Map.

A shortcut menu that appears when you right click the Tables node, a table node, or a field node also allows you to unmap that node. Unmapping a field node unmaps just that field node; unmapping a table node unmaps all mapped fields in the table. Unmapping the Tables node unmaps all tables. You can also unmap table and field nodes by clicking Delete.

Mapping Constraints

Several restrictions apply regardless of how fields are mapped. If you attempt an invalid mapping operation, the item you drag is not highlighted, and the mapping does not succeed. If a mapping is invalid during an Automap, Field Map, or Table Map, errors are logged to the Data Mapper Error Log table.

The following constraints apply:

❑ Neither field can be currently mapped.

❑ Both fields must have the same data types (dbMemo, dbText, dbDate, and so on). Field lengths for dbText fields will not be matched.

2-22 User Guide


❑ Cross-table mapping is not supported. If at least one field in a Copy From table is mapped to a field in a Copy To table, the two tables are considered mapped together, and neither can be mapped to another table.

❑ Fields from a same table cannot be mapped together.

Note When unmapping a field that was previously mapped, the view does not automatically repaint. To refresh the view, select another field in the window or condense and then re-expand the branch.

Overwriting Maps

If running an Automap, Field Map or Table Map conflicts with current field mappings, the following window appears, allowing you to decide which mappings to overwrite.

Figure 2-15: Overwrite Mappings Dialog Box

If loading a Table Map conflicts with current table mappings, a message box appears informing you that loading the Table Map will overwrite current mappings.

2-23

Agile DataLoad 2006

Step 3: Copying

Once your mappings are created, click Copy to start the Copy process. Before the copy process executes, Data Mapper prompts you to empty the destination tables. If you are performing only one copy from the source table to the destination table, you should click Yes. However, if you are going to perform more than one copy, click No, as this will wipe out all previous data transfers.

Alternatively, you can choose the Batch Copy command. The Batch Copy window allows you to select an unlimited number of Table Maps that are loaded and copied sequentially, and allows you to copy data from multiple tables to a single destination table.

If an email is created with the email command, the Batch Copy window provides the option of sending that email when the process finishes.

Note During a Batch Copy process, the Copy To tables are not reset, regardless of the Options setting. Additionally, any mapping conflicts are overwritten, regardless of the Options setting.

Step 4: Modular Cleanup

The Data Mapper provides two procedures for cleaning up invalid data.

Generating Changes

The first procedure scans the SOURCE_Rev table for all rows lacking a Change Number, generates new Changes for these rows in the SOURCE_Change table, and inserts the corresponding new change number in the SOURCE_Rev table rows. Additional values for these generated Changes can be set through the Generated Changes Settings command, as shown in the following window.

2-24 User Guide


Figure 2-16: Cleanup Settings Window

Prefix and Start Number generate both parts of the change number. All generated change numbers have the same prefix, and the start number is incremented for each new generated Change. Max Items per Change specifies the maximum number of revision rows that can have the same change number before a new Change is generated. Normal practice suggests that the number be 200 or less to keep from creating changes with very large affected items lists.

The Effective Date value for the SOURCE_Rev row is overwritten by the Effective Date value, because this value must be consistent with the Change release date.

Change Record Default Values lets you set values for all fields required by the Load API. Each of these fields must have a value. When all new Changes have been generated, a message box informs you of how many Changes were generated.

If a Change is loaded with an inprocess status, Agile DataLoad loads the default signoff and workflow for the Item. This can then be modified by the customer to add reviewers or change workflow steps.

Importing BOMs

When you select “Import BOMs,” the first dialog box displays a list of all tables in the database that are not created by Agile DataLoad, such as all the tables created by the user.

When you click OK, Agile DataLoad checks that the import table contains the following fields:

2-25

Agile DataLoad 2006

❑ PARENT_NUMBER

❑ ITEM_NUMBER

❑ FIND_NUMBER

❑ QUANTITY

❑ REFDESIG

If any of these fields are missing, then an error message is displayed, and you must select another table.

If SOURCE_BOM was somehow corrupted and any of the fields NOTES, ID, or QUANTITY are missing, they are silently recreated. If PARENT_NUMBER, ITEM_NUMBER or FIND_NUMBER is missing from SOURCE_BOM, then an error message is displayed and the Import process is canceled.

DataLoad scans the Valid RefDesig Prefixes table for a list of all valid prefixes. This table is created by Agile DataLoad when a new database is created and contains just two fields:

❑ PREFIX — A valid prefix.

❑ DESCRIPTION — This is for any notes the user may want to add. The value of this field is never used by Agile DataLoad.

If this table is empty or if it does not exist, all prefixes in the import table are considered valid.

If the Valid RefDesig Prefixes table has one or more entries, only the prefixes specified in this table will be considered valid when you import data from the import table.

Import BOM Table Format

As stated above, the Import BOM table is validated and must contain the following fields:

❑ PARENT_NUMBER

❑ ITEM_NUMBER

❑ FIND_NUMBER

❑ QUANTITY

❑ REFDESIG

2-26 User Guide


The import process scans Import BOM for any rows containing identical PARENT_NUMBER, ITEM_NUMBER, and FIND_NUMBER triplets and concatenates the REFDESIG value for each such row.

For example, the information in Table 2-4 would be concatenated into the information in Table 2-5.

This concatenation is done in memory and does not modify any of the Microsoft Access tables.

The concatenated REFDESIG value is then parsed for valid and invalid RefDesigs. If the Valid RefDesig Prefixes table exists and was not empty, any RefDesig in the concatenated REFDESIG value whose prefix did not match one of the values in the Valid RefDesig Prefixes table is considered invalid.

Once the parsing is done, the Quantity (of valid RefDesigs) is computed. A unique ID is generated and the row PARENT_NUMBER, ITEM_NUMBER, FIND_NUMBER, QUANTITY, ID is created in SOURCE_BOM.The corresponding row for ID and REFDESIG is created in SOURCE_RefDesig. Any invalid RefDesigs found when the concatenated REFDESIG value is parsed and added to the NOTES field of the newly created SOURCE_BOM row.

It is possible to import values from the import table for fields other than just PARENT_NUMBER, ITEM_NUMBER, FIND_NUMBER,QUANTITY, or REFDESIG.

Table 2-4: Import BOM Source Table

PARENT_NUMBER ITEM_NUMBER FIND_NUMBER REFDESIG

P001 P002 0 R1

P001 P002 0 R2

P001 P002 0 resistors

Table 2-5: Import BOM Results Table

PARENT_NUMBER ITEM_NUMBER FIND_NUMBER REFDESIG

P001 P002 0 R1, R2, resistors

2-27

Agile DataLoad 2006

For each unique data triplet, PARENT_NUMBER, ITEM_NUMBER, and FIND_NUMBER, in the import table, values for all other fields are read from the first row. If these fields exist in SOURCE_BOM, their values are added when the new row is created. Because it is not possible to concatenate values for these other fields, only the values for the first few are copied.

For instance, the information in Table 2-6 is imported into SOURCE_BOM as the data shown in Table 2-7 and into the SOURCE_RefDesig table as the data shown in Table 2-8.

Duplicate RefDesigs in the import table are not added to the NOTES field. Only one instance of each RefDesig is inserted into SOURCE_RefDesig.

Stage 6: Configuring the List Attribute ValuesUse Agile Administrator to configure the Agile Advantage database using the values for list and multilist fields.

Agile DataLoad processes your Microsoft Access source table data one row at a time. While processing a row of data from any one of the source tables, Agile DataLoad does not load a row of data into the Agile Advantage database if that row contains a field value that is not included in the list or multilist for the corresponding field name in the Agile Advantage database.

Table 2-6: Legacy Source Table

PARENT_NUMBER

ITEM_NUMBER

FIND_NUMBER REFDESIG TEXT02 DATE03

P001 P002 0 R1 Ted

P001 P002 0 R2 Simon 10/10/00

P001 P002 0 resistors

Table 2-7: SOURCE_BOM Table

PARENT_NUMBER

ITEM_NUMBER

FIND_NUMBER QUANTITY ID NOTES TEXT02 DATE03

P001 P002 0 2 37 resistors Ted

Table 2-8: SOURCE_RefDesig Table

ID REFDESIG

37 r1-r2

2-28 User Guide


For example, if the Part’s Page Two List01 field is being used for “Unit of Measure” and the Agile Administrator list includes “EA,” but the legacy data has the value “EACH,” this row will not be loaded. Instead, it is written to the error table with the error message: “Invalid list value” (although data in the error row allows the user to precisely identify the corresponding row in the SOURCE_ table.

Therefore, in this stage, all distinct values from all list and multilist fields in the source tables are copied into the appropriate fields in Agile Administrator. If values already exist for list and multilist fields in Agile Administrator, you have to resolve the differences before pasting the values into Agile Administrator.

Agile DataLoad also validates field length, case, and format based on settings in Agile Administrator. It also checks duplicate items and other relational dependencies.

Step 1

You can use Agile DataLoad to extract a file containing field names and all unique list values in your populated Microsoft Access source tables. You can then open that file in a text editor and copy and paste list values into the corresponding fields in Agile Administrator.

Note The Load process loads all attributes (whether they are visible or not), but the Validation process only takes visible attributes into account.

To extract list values and perform the update:

1 Start Agile DataLoad.

2 Select Create Selection Lists File on the Step 1 window.

2-29

Agile DataLoad 2006

Figure 2-17: Agile DataLoad Wizard - Create Selection Lists File (Step 1)

The screen title changes to Step 1 (Selection Lists).Click Next. The Step 2 (Selection Lists) window appears.

Step 2


1 Select the database from the Filename field. You can use the buttons to Add, Remove, or Open a database.

2 Click Next. The Step 3 (Selection Lists) window appears.

2-30 User Guide


Step 3


1 Type a name in the Output Selections List File field. Browse to locate an existing text file to hold the lists values, or to place the file in a specific folder. If you type a file name, the file is created in the Agile DataLoad program folder.

Note These actions affect only the Agile DataLoad list for this window. The database is not created or deleted by these actions.

2 Click Create. Agile DataLoad begins extracting selection list values from the tables in your Microsoft Access database. A progress indicator informs you of extraction progress. If the values are already in the Agile Advantage database, they are marked in the output file with an asterisk (*).

3 Click View File when the extraction process is complete. The extracted selection lists file opens in Windows Notepad.

2-31

Agile DataLoad 2006

Figure 2-20: Selection List Report

Note Server values for a field appear only if at least one row in the database contains a value for that field. Invalid list (or multilist) values are marked with an asterisk. Do not include the asterisk when you cut and paste these values in Step 4.

To create a list without the asterisk, copy the values to a blank document in Microsoft Word, edit the data, then paste the data into Agile Administrator.

4 Cut and paste list values from the text file into the corresponding fields in Agile Administrator.

2-32 User Guide


Figure 2-21: Agile Administrator Changes

5 Close Agile Administrator, and continue with the next stage.

Stage 7: Validating the DataAgile DataLoad’s Validate function lets you test the integrity of the Microsoft Access source tables before loading data into the Agile Advantage database. You can then correct problems in the data and Agile Administrator settings prior to loading the data.

The validations include Referential Integrity checks to verify that there are no duplicate Item Numbers and Administrator settings checks, such as confirming that the CHANGE_NUMBER values do not contain spaces if the field is configured in Agile Administrator with no spaces. You can elect to verify only the local Microsoft Access database, or verify both the Microsoft Access tables and the Agile Advantage database.

Note You should always validate the data before loading to ensure that the data receives the highest level of testing and verification. You do not need to validate the database if it is blank.

2-33

Agile DataLoad 2006

Step 11 Start Agile DataLoad.

2 Select Validate configured Access database. Click Next.

Figure 2-22: Agile DataLoad Wizard - Validate Configured Database (Step 1)

Step 2

In Step 2, you have the option to log in to the Agile Advantage server. If you do not log in, only the Include only local Access Database radio button is enabled in the Step 3 window, and in Step 2 you will not be able to click the Administrator Settings checks checkbox.

2-34 User Guide



1 Check the Login to Agile Advantage eHub checkbox if you want the validation to include both Agile Advantage and Microsoft Access data. If you are logging on, enter the username and password in the appropriate fields. You must have Administrator rights to use the Validate feature.

2 Check the validations you want to perform: Referential Integrity or Administrator Settings. For details about the validations performed, refer to Appendix B, “Validations.”

Referential Integrity checks confirms that there are no duplicate values in fields that must be unique and that fields that must contain data do, in fact, contain data It also performs other data checks.

Administrator Settings checks tests that requirements established in Agile Administrator are met. This is available only if you check the Login to Agile Advantage eHub checkbox.

3 Click Next.

Step 3

Specify the scope of the validation to check only the Microsoft Access database or to include the Agile Advantage database.

2-35

Agile DataLoad 2006


1 Select either of the two database choices: Include both Agile Advantage Database and local Access Database, or Include only local Access Database. You cannot select the first option unless you checked the Login to Agile Advantage eHub box in Step 2.

In most cases, when there is data already loaded in the Agile Advantage database, you should validate both the Agile Advantage and the Microsoft Access databases. For example, if the SOURCE_BOM table refers to Item Numbers that are not in the Microsoft Access table, errors might be reported if you choose to include only the local Microsoft Access database. However, if you include both the Agile Advantage and Microsoft Access tables, and the Item Numbers are in the Agile Advantage database, no errors are reported.

The Validation checkboxes in this window, combined with the settings selected in Step 2, provide a total of five possible validation sets:

• Referential integrity checks against the Microsoft Access database only

• Referential integrity checks against the Microsoft Access database and the Agile Advantage database

• Administrator settings checks only

• Referential integrity checks against the Microsoft Access database and Administrator settings checks

2-36 User Guide


• Referential integrity checks against the Microsoft Access database and the Agile Advantage database, plus Administrator settings checks

2 Click Next.

2-37

Agile DataLoad 2006

Step 4

In this step select the Microsoft Access database to validate, specify the tables to include, and begin validation.


Note If an email was created in the Data Mapper, the E-mail checkbox is enabled. This allows the user to indicate if they want to automatically send email when the Validation process has finished.

1 Select a database in the File Name list.

If the database you want does not appear, click Add. To view the contents of a database in Microsoft Access, select it and click Open.

2 Check the box next to each table you want to include in the validation.

3 Click Start Validation.

When you click Start Validation, you are asked if you want to delete the existing records in the VALIDATION_ERRORS table. New errors found during the current session will then be written to the table.

4 When the validation is finished, the number of errors appears, and you are asked if you want to open the source Microsoft Access database. Click Yes, and open the VALIDATION_ERRORS table to view the Error Description information.

2-38 User Guide


Validation may be run on a table-by-table basis. This is preferable for the initial validation because it limits the types of errors displayed in any one pass. It is best to follow the load order as shown in “Notes on Loading Order” on page 2-45.

See Appendix B for descriptions of specific validations.

Viewing Validation Reports

If errors were logged during the Validation procedure, the Reports button is enabled on the dialog box, shown in Step 4.

Reports are Access reports stored in the database when it is created through Agile DataLoad. Databases created with older DataLoad versions (prior to Agile Anywhere 7) or imported through the Add Table feature do not provide access to these reports. Reports display all information in the VALIDATION_ERRORS table.

You are prompted to display the report in one of six different sorting methods, as shown in the following figure.

Figure 2-26: Validation Reports Selection

Notes Validation reports are available only for databases created with this version of Agile DataLoad.

The Microsoft Access database must be open in order to view any generated validation reports.

2-39

Agile DataLoad 2006

Stage 8: Loading Data into Agile AdvantageOnce you have fixed any errors found in the validation process, you are ready to load the legacy data into the Agile Advantage database.

Note DataLoad checks each record size before attempting to load it. If the record exceeds the maximum length it is flagged as an error. Each record is limited to a total of 16,384 characters. For BOM records, this includes any associated Reference Designators.

If you are working with an Agile Advantage database that contains data (such as Items, BOMs, and Changes), and you do not want to append to that data, then you need to truncate those data tables first with a truncate script. Scripts for Oracle can be found in the Alliance Resource Center (ARC) at: http://arc.agile.com

Step 11 Start DataLoad. The Step 1 window appears. Make sure that all Agile Advantage

sessions are closed at this time.

Figure 2-27: Agile DataLoad Wizard - Loading (Step 1)

2 Select Load configured Access database.

Note If the Load configured Access database option is grayed, refer to “Enabling Data Loading” on page 1-4.

2-40 User Guide


3 Click Next. The Step 2 window appears.

Step 2 (Loading)


1 Select an error response option. You may choose to have data loading stop at a certain number of errors or have the process continue until finished. Either way, errors are accrued in Microsoft Access tables for later correction.

2 Type your Agile Advantage login ID and Password. If you check Remember Password, remember to uncheck it when you leave the Agile DataLoad computer.

You must have an Agile Advantage account with Administrator privileges to use DataLoad to load legacy data into the Agile Advantage database. Also, you must have a full Agile Advantage user license to log in to Agile DataLoad.

3 Click Next. The Step 3 (Loading) window appears.

2-41

Agile DataLoad 2006

Step 3 (Loading)


The database filename and description that you entered appears as a choice in the list at the top of the window. Note that you can use the Open, Add, and Remove buttons to add or remove a Microsoft Access database, or to open it in Microsoft Access.

1 Make sure that Load From: Source Tables is selected.

2 Click your database filename, and select the table to be loaded first.

Agile DataLoad manages the order for you if you select all the source tables. For loading individual tables, refer to “Notes on Loading Order” on page 2-45. Note that if you do not choose to load all tables at once, you must load the tables in the right order.

3 Click Start Load. The loading process begins. A progress indicator appears.

If you click Stop, the loading process stops. Data that has already been processed is loaded into the Agile Advantage database.

4 When the loading process is complete, a message window appears if any data was rejected.

2-42 User Guide


Figure 2-30: Agile DataLoad Errors Encountered Dialog

5 Click Yes if you want to start Microsoft Access and edit the error tables at this time. If you click No, you can see how many records (rows) have been loaded from each table in the Step 3 (Loading) window by selecting Error Tables in the Load From section.

Rollback

If necessary, you can remove data loaded during the current Agile DataLoad session from the Agile Advantage database. To do so, click the Rollback button on the Step 3 (Loading) window. The Rollback Stack window appears. Click Rollback Last to roll back the last transaction (a transaction can be one table or part of a table loaded in one session). Click Rollback All to roll back all transactions in the current session. As soon as you exit DataLoad, all rollback information is lost.

Figure 2-31: Transaction Rollback Stack dialog

Note The SOURCE_User table cannot be rolled back.

2-43

Agile DataLoad 2006

Revising and Reloading

You can correct the errors identified in the Microsoft Access error tables and reload those tables.

1 Open the first error table in Microsoft Access.

Figure 2-32: ERROR_Item Table

2 Correct all of the error tables, based on the descriptions in the Error_Description column.

3 Return to the Step 3 window (page 2-42). Click Load From: Error Tables, select the error tables, and click Start Load. The loading progress indicator appears. Any remaining errors are written to the error tables, and successfully loaded rows will disappear.

4 Revise the error tables again, and reload. Continue this process until all data loads successfully and no more errors appear in the error tables.

Note If there are many errors, it is best to go back and modify the original programs that created the SOURCE data. Then use a script to clean out the database and restart the process from the beginning.

2-44 User Guide


Notes on Loading Order

The order in which the Microsoft Access source tables are processed is important. Data is not properly loaded into the Agile Advantage database unless you process the tables in the proper sequence. However, not following the order does not corrupt the Agile Advantage database. Instead, errors are logged, and the rejected data is written to the Microsoft Access error tables, from which you can reload the data in the proper sequence.

In general:

❑ Agile DataLoad manages the loading order for you if you select and load all of the available tables on the Step 3 (Loading) window.

❑ Tables must be loaded in the order shown below.

Figure 2-33: Table Loading Order

Change

ItemUser

Manufacturer

Revision

Approved_Mfr

BOM and Ref Desig

Mfr_Parts

or

Customer ProblemReport

or

Supplier

Contact

or

or

2-45

Agile DataLoad 2006

Table 2-9: Dependencies

Order Source Table Dependencies

1 USER The SOURCE_User table must be loaded before the SOURCE_Change table. During the loading process, the SOURCE_Change table Owner field values are checked for existing users in the Agile Advantage database. If none are found, the row is rejected and written to the ERROR table.

Note: All users loaded through Agile DataLoad will be assigned a full user license.

2 ITEM The SOURCE_Item table must be processed before the SOURCE_Rev, SOURCE_BOM, SOURCE_Refdesig, or SOURCE_Approved_Mfr tables.

The SOURCE_Item table may be processed before or after the SOURCE_Change table. Every Agile DataLoad project will have a SOURCE_Item table.

3 CHANGE The SOURCE_Change table must be processed before the SOURCE_Rev table.

The SOURCE_Change table may be processed before or after the SOURCE_Item table, but should always be processed after the SOURCE_User table. Any Agile DataLoad project with Released Items will have a SOURCE_Change source table.

4 REVISION The SOURCE_Rev table must be processed after the ITEM and CHANGE source tables.

Although not required, the SOURCE_Rev source table should be processed before the BOM source table. DataLoad will not load the Item/Revisions that identify Item_Number or Change_Number that do not yet exist in the database; they are logged as errors and sent to the appropriate Microsoft Access error table.

Change_Orders, complete with a Change Status information (e.g., PENDING, CCB, RELEASED) must exist in the Agile Advantage database so that certain rules can be checked and enforced when the SOURCE_Rev table is processed by Agile DataLoad. One such rule is that you can not add an Item with a PRELIMINARY status to Agile if the Change_Order identified for that Item/Revision has a RELEASED or IMPLEMENTED status.

2-46 User Guide


5 BOM The SOURCE_BOM table cannot be processed until after the SOURCE_Item table has been loaded.

The SOURCE_BOM table must be processed before the Refdesig table (this is done automatically). Agile DataLoad will not load those entries into the internal Agile BOM table that refer to a Parent_Number or an Item_Number that does not yet exist in the Agile database; they are logged as errors and sent to the appropriate Microsoft Access error table.

6 REFDESIG The Refdesig table can not be processed without an accompanying SOURCE_BOM table. Loading the Refdesig table is not an option; it is loaded automatically along with the SOURCE_BOM table.

Agile DataLoad will not load those entries into an internal Agile REFDESIG table that refer to a BOM ID/Item_Number that does not yet exist in the BOM table in the Agile database; they are logged as errors and sent to the appropriate Microsoft Access error table.

7 MANUFACTURER The SOURCE_Manufacturer table must be loaded before the SOURCE_Mfr_Part and SOURCE_Approved_Mfr tables.

This table alone, or with the other manufacturer source tables, can be processed at any time since there are no dependencies between them and the other source tables.

8 MFR_PART The SOURCE_Mfr_Part source table cannot be processed until after the SOURCE_Manufacturer table.

The SOURCE_Mfr_Part table must be processed before the SOURCE_Approved_mfr table. Agile DataLoad will not load entries into the internal Agile MANU_PARTS table that refer to a manufacturer that does not yet exist in the Agile database; they are logged as errors and sent to the appropriate Microsoft Access error table.

9 APPROVED_MFR The SOURCE_Approved_Mfr table can not be processed until after the SOURCE_Item, SOURCE_Manufacturer and SOURCE_Mfr_Part tables have been loaded.

Agile DataLoad will not load those entries into the internal SOURCE_Approved_Mfr table that refer to an Item_Number or Mfr_part that does not yet exist in the Agile database; they are logged as errors and sent to the appropriate Microsoft Access error table.

10 CUSTOMER The SOURCE_Customer table must be processed before the SOURCE_ProblemReport table.



2-47

Agile DataLoad 2006

Running SQL Scripts

After Agile DataLoad is complete and all errors are resolved, you must log in to SQL Plus using the user name agile and the password tartan.

Important Stop the Agile Advantage eHub services before you run the validation scripts. Restart them after you have run all of the validation scripts. If you do not you may experience a problem with BOM data being trapped in the Agile Advantage eHub cache.

Run the following scripts:

1 1. Oracle_resetlatestrev2006.sql: Clears all revision record latest_flag settings and correctly sets the latest_flag field by release_date, ignoring all non-ECO and non-MCO records for Agile Advantage 2006.

2 oracle_resetflag2006.sql — Sets up a new internal 32-bit flag to control BOM, Rev, and Where Used for Agile Advantage 2006.

3 oracle_setactive2006.sql — Resets the active object for Manufacturer searches. You need to run this script only if you load Manufacturer data for Agile Advantage 2006.

11 PROBLEMREPORTS The SOURCE_ProblemReport table cannot be processed until after the SOURCE_Item and SOURCE_Customer tables have been loaded. Agile DataLoad will not load those entries into the internal SOURCE_ProblemReport table that refer to an Item_Number or Customer that does not yet exist in the Agile database; they are logged as errors and sent to the appropriate Microsoft Access error table.

12 CONTACT The SOURCE_Contact table does not have any prerequisites.

13 SUPPLIER The SOURCE_Supplier table does not have any prerequisites. Contact information must be added via the Agile Advantage Windows or Web clients and Manufacturer Parts must be added via Agile Import 2006.



2-48 User Guide


4 oracle_setoldLCP2005.sql, oracle_setoldLCP2006.sql, oracle_setoldrevnumber2005.sql and oracle_setoldrevnumber2006.sql — Agile DataLoad does not update the old rev number and old release type fields during the load process. If multiple revisions are loaded for items, these two scripts must be run after the completion of the Agile DataLoad process. They should be run prior to the execution of the Averify script for Agile Advantage 2006.

5 oracle_averify2006.sql — Checks the Agile Advantage 2006 database integrity.

6 oracle_rollbackreset.sql — Resets the rollback segment of the Agile Advantage database.

7 oracle_rollbackset.sql — Sets the rollback segment of the Agile Advantage database.

Note These scripts are located on the Agile Advantage folder in the <Agile Home>\Tools folder.

Stage 9: Importing at the Customer’s SiteOnce the Agile Advantage database has been set up and populated with legacy data, you can export it, and then use the appropriate database utilities to import data at the customer’s site. Refer to the Agile Advantage 2006 Installation and Maintenance Guide.

ChecklistThe following checklist helps you keep track of the stages and steps of the DataLoad process. Be sure to refer to the corresponding sections of this chapter for details. You may want to photocopy this list so you can reuse it.

Stage 1: Exporting Legacy Data❑ Export legacy data in comma-delimited text format.

❑ Edit legacy data export file for form and content.

Stage 2: Configuring the Agile Advantage Database❑ Use the Agile Advantage installer to install an Agile Advantage starter database.

❑ Refer to the Agile Advantage 2006 Installation and Maintenance Guide for details on installing an Agile Advantage starter database.

2-49

Agile DataLoad 2006

Stage 3: Creating the Microsoft Access Tables❑ Configure the new Microsoft Access database file.

❑ If adding optional fields to source tables:

• Specify the source of reference designators.

• Select optional fields to be added to tables.

❑ Complete creation of skeleton Microsoft Access data tables for classes.

Note Each class has a source table and an error table, and there is also a description table.

Stage 4: Importing Data Into Microsoft Access❑ View skeleton tables and determine how legacy data will fit into them.

❑ Run the Microsoft Access Import Text Wizard to load legacy data into Microsoft Access.

❑ Validate record dependencies.

❑ Populate source tables with legacy data if not done in Import.

Stage 5: Using the Data Map Wizard❑ Load the data extracts in Microsoft Access into user-created intermediary

tables.

❑ Start the Data Mapping Wizard in Agile DataLoad, selecting the Microsoft Access table to run against.

❑ Map the source and destination tables for importing data.

❑ Copy the mapping data from the source Microsoft Access tables.

❑ Validate the Microsoft Access tables for import into the Agile Advantage database.

Stage 6: Configuring List Attribute Values❑ Extract list values from Microsoft Access source tables.

❑ Paste the list values into corresponding fields in Agile Administrator.

Stage 7: Validating❑ Run the validations to test the data prior to loading it into Agile Advantage.

2-50 User Guide


❑ Fix any errors found by the validation.

Stage 8: Loading Data into Agile Advantage❑ Start DataLoad and load the source tables.

❑ If you are working with an Agile Advantage database that already has data in it, and you aren’t appending the data, download a truncate script and truncate the data tables.

Note Source tables must be loaded in the order shown in “Notes on Loading Order” on page 2-45.

❑ Revise errors identified in the Microsoft Access error tables.

❑ Reload the revised tables.

❑ Run the required SQL scripts.

Stage 9: Importing at the Customer’s Site❑ Verify that the Agile Advantage database has been set up and populated with

legacy data.

❑ Export the database.

❑ Using database-specific import tools at the customer site, import the database into the customer’s system.

2-51

Agile DataLoad 2006

2-52 User Guide

CHAPTER 3gLoading BOM History

The instructions in this chapter are for qualified Agile system implementation specialists who need to load BOM histories from existing source databases.The following topics are included:❑ Requirements❑ Agile BOM Table Structure❑ SOURCE Data Structures❑ Preparing the Data❑ Summary

Agile DataLoad 2006 supports the loading of historical BOM records if certain conditions are met. It is possible to use Agile DataLoad to load BOM history if you can provide the right type of data and you carefully consider the issues and follow the steps in this chapter.

If the SOURCE_BOM table has complete and accurate data for the CHANGE_IN and CHANGE_OUT fields, then Agile DataLoad will automatically load the BOM History during its normal load sequence. No special steps are required.

However, prior to attempting to load the BOM history, you should explore all other options. If other options are not acceptable, you must then review the source tables to ensure that the necessary data is available. If the data in the source tables is not available or in the correct format, it will not be possible to successfully load BOM history.

3-1

Agile DataLoad 2006

RequirementsTo correctly load BOM history, the following requirements must be met:

❑ Agile Advantage BOM configuration is change driven. Every row in the Agile Advantage BOM table must have a change associated with that row.

❑ If change information is unavailable in the legacy data, it must be created. To create the change information, complete parent item revision information is required.

❑ The parent Item revision information must allow each parent Item revision to be unambiguously associated with a valid legacy Change or a Change must be created to support the data load.

❑ Full BOM records for each revision of an assembly.

❑ Complete BOMs for each revision of a parent item.

❑ Information for each BOM component showing which revision, or change, added or removed the component from the parent item.

❑ Assembly revision information for each full set of BOM records, including obsolete dates.

❑ CHANGE_IN and CHANGE_OUT numbers for each BOM record.

Note The CHANGE_IN and CHANGE_OUT numbers may be either provided or derived based on legacy data information or change creation code.If the data cannot be provided to meet these requirements, then you have to examine the source files to determine if it is possible to derive the required data. Obviously, this is more difficult, but if you can extract the proper data, then the BOM history can be successfully created.

Note The BOM component effective date information normally available from ERP systems does not typically satisfy the requirements listed above. Effective dates from an ERP system reflect the manufacturing reality of when a BOM component change actually occurred, and not related to the change order controlling that change, or the date that the change order was approved.

Furthermore, changed components that were on the same change order often have different manufacturing effective dates recorded for them due to the actual timing of inventory exhaustion or shipment receipt. It is extremely difficult, if not impossible, to develop accurate BOM history from ERP effectivity dates.

3-2 User Guide


The resulting BOM history is only as good as the source data. Any ambiguity in determining the correct revision order or in determining the correct controlling change results in inaccurate historical information. Make sure you fully understand the issues involved in loading revision and change history before attempting to load BOM history.

Agile BOM Table StructureThis section describes the correct table structure needed to successfully load BOM history. Table 3-4 supplies sample information about the required fields.

Note Only fields important to the discussion of BOM history are listed.

Table 3-1: Agile Advantage BOM Table Structure

Name Null? Type Notes

ID Not Null

NUMBER(10) Unique ID for each record set by Agile Advantage.

ITEM NUMBER(10) ITEM.ID—unique ID for each item number in the ITEM table; represents Parent.

ITEM_NUMBER VARCHAR2(75) Child number (actual child number, not ID value).

CHANGE_IN NUMBER(10) CHANGE.ID—unique ID for each change number in the CHANGE table; represents the change that added the component to the BOM. It is set to 0 if the component was added to a preliminary BOM in the BOM edit window.

CHANGE_OUT NUMBER(10) CHANGE.ID—unique ID for each change number in the CHANGE table; represents the change that removed the component from the BOM. It is set to 0 if the component has not been removed from the BOM (still an active BOM record).

3-3

Agile DataLoad 2006

In two cases, CHANGE_IN can equal CHANGE_OUT.

❑ Both fields equal 0: This represents a BOM row that was added to a preliminary BOM and has not been removed.

❑ Both fields do not equal 0: This case represents a redline in the redline view window. In this case, PRIOR_BOM points to the BOM row that was deleted from the BOM.

To examine these premises in depth, we will look at some example BOMs in the Agile Advantage Windows Client. Figure 3-1 displays the first revision of a simple BOM.

PRIOR_BOM NUMBER(10) The BOM row (BOM.ID) that the current row is replacing. PRIOR_BOM is set to 0 for all BOM rows added. And when a new BOM is created using Save As, PRIOR_BOM is used to create the redlines in the redline view window of the change.

DL_CHANGE_IN TEXT The Change Number that will be loaded to the CHANGE table. DataLoad translates this to the assigned ID and correctly populates CHANGE_IN (above)

DL_CHANGE_OUT TEXT The Change Number that will be loaded to the CHANGE table. DataLoad translates this to the assigned ID and correctly populates CHANGE_OUT (above).

Table 3-1: Agile Advantage BOM Table Structure

Name Null? Type Notes

3-4 User Guide


Figure 3-1: First Revision of a Simple BOM

Table 3-2 lists records that the relationship between P0001 and the children P0002, P0003 and P0004. P0001’s ID number is 503 in the Agile Advantage table.

Notice that in Table 3-2, CHANGE_IN is set to 0 because the user created the BOM on the preliminary item first and then released it with a Change, instead of creating a preliminary Item, redlining the Item on a Change to add components, and then releasing it. If the latter had been done, the table would display records as shown in Table 3-3, where 508 is the ID for the change number.

When child P0002 is redlined off the BOM in the next revision, the Agile Advantage Windows client displays the following new BOM.

Table 3-2: Sample BOM Table

ID ITEM ITEM_NUMBER CHANGE_IN CHANGE_OUT PRIOR_BOM

511 503 P0002 0 0 0

552 503 P0003 0 0 0

557 503 P0004 0 0 0



511 503 P0002 508 0 0

552 503 P0003 508 0 0

557 503 P0004 508 0 0

3-5

Agile DataLoad 2006

Figure 3-2: Revised BOM

At the table level, the BOM records are modified to reflect the change, with 708 as the ID for the Change, as shown in Table 3-4.

Note In Table 3-4, the value in the CHANGE_IN field the last row is equal to the value in the CHANGE_OUT field because this row represents the redline.

Entries in the PRIOR_BOM field are required to create the redlines on the change orders. However, you do not have to load the PRIOR_BOM information when loading BOM history. DataLoad determines the PRIOR_BOM from the Revision Table. It matches the revision that removes the row with the revision that originated the row and create the redline.

SOURCE Data StructuresThis selection includes examples of the SOURCE_ITEM, SOURCE_CHANGE, SOURCE_REV, and SOURCE_BOM table data for loading BOM history. These examples reflect how the data must look prior to successful loading and may or may



511 503 P0002 0 708 0

552 503 P0003 0 0 0

557 503 P0004 0 0 0

711 503 P0002 708 708 511

3-6 User Guide


not reflect the actual legacy data provided. With knowledge of the goal, you should be able to evaluate the source data and determine if you can derive all the needed information.

The next four tables represent a sample load for a BOM history. Only fields important to the discussion of BOM history are listed.

The SOURCE_ITEM table is cross-referenced with the SOURCE_CHANGE table to create the data required for the SOURCE_REV table.

The SOURCE_CHANGE table must have released or implemented Changes for the records to be valid in loading the BOM history.

Use the following procedure when assigning affected Items to Implemented Changes. That is, to load Changes whose status is implemented, but have associated affected items in the SOURCE_BOM and SOURCE_REV tables:

1 In Administrator, create a new Role with the following Privilege Criteria: Cover Page. Status Equal To Default Change orders.Implemented.

2 Assign this role to the DataLoad user.

3 Load data through DataLoad.

4 Delete this role when DataLoad is complete, so future changes with a Status of Implemented can’t be changed.

Table 3-5: SOURCE_ITEM Table

ITEM_NUMBER CLASS SUBCLASS DESCRIPTION

1000 Parts Part TEST ASSEMBLY

1001 Parts Part TEST COMPONENT

1002 Parts Part COMP 2



Table 3-6: SOURCE_CHANGE Table

CHANGE_NUMBER CLASS SUBCLASS STATUS RELEASE_

DATE DESCRIPTION

ECO100 Change Orders

ECO Released 1/1/99 First Change

ECO200 Change Orders

ECO Released 2/1/99 Second Change

3-7

Agile DataLoad 2006

The OBSOLETE_DATE field in the SOURCE_REV table must reflect the obsolete date for the current revision record. Thus, for Part 1000, rev 000 is obsolete on 2/1/99. It is essential to load OBSOLETE_DATE information for assembly parts or the BOM tab will reflect start dates for each BOM revision, but no stop dates.

This is not how Agile DataLoad has loaded obsolete date in the past. The software was changed to allow the loading of the OBSOLETE_DATE on the line made obsolete. Previously the OBSOLETE_DATE was the obsolete date for the previous revision, not the current revision record.

If you have the latest BOM record for the SOURCE_BOM table, it should have a NULL in the DL_CHANGE_OUT field to indicate that it is the latest BOM record. All historical BOM records must have DL_CHANGE_IN and DL_CHANGE_OUT values that match the SOURCE_CHANGE records and the parent SOURCE_REV records.

Table 3-7: SOURCE_REV Table

ITEM_NUMBER

REV_NUMBER

CHANGE_NUMBER

RELEASE_TYPE

EFFECTIVE_DATE

INCORP_DATE

OBSOLETE_DATE

1000 000 ECO100 Production 1/1/99 1/5/99 2/1/99

1001 000 ECO100 Production 1/1/99 1/5/99

1002 000 ECO100 Production 1/1/99 1/5/99

1003 000 ECO100 Production 1/1/99 1/5/99

1004 000 ECO100 Production 1/1/99 1/5/99

1000 001 ECO200 Production 2/1/99 2/5/99

Table 3-8: SOURCE_BOM Table

PARENT_NUMBER

ITEM_NUMBER

FIND_NUMBER

HIST_CHANGE_IN

HIST_CHANGE_OUT QUANTITY

1000 1001 1 ECO100 ECO200 1

1000 1002 2 ECO100 ECO200 2

1000 1003 3 ECO100 ECO200 1

1000 1001 2 ECO200 1

1000 1002 2 ECO200 1

1000 1004 3 ECO200 1

3-8 User Guide


The results of this data set, after a successful Agile DataLoad pass, makes the resulting data set available for use in the Agile Advantage Windows client, as shown in the following figures.

Figure 3-3: BOM Assembly 1000, Revision 000

Figure 3-4 illustrates the Change ECO100 redline, which releases Assembly 1000 to revision 000.

Figure 3-4: Change ECO100 Redline

3-9

Agile DataLoad 2006

Figure 3-5: New BOM Assembly 1000, Revision 001

Figure 3-6: Change EC0200 Redline

Figure 3-6 illustrates the Change ECO200 redline, which releases Assembly 1000 to revision 001.

The BOM table level results are seen below.

Table 3-9: BOM Table Level Results

ID ITEM ITEM_NUMBER

CHANGE_IN

CHANGE_OUT

PRIOR_BOM

DL_CHANGE_IN

DL_CHANGE_OUT

815 776 1001 797 799 0 ECO100 ECO200

820 776 1002 797 799 0 ECO100 ECO200

821 776 1003 797 799 0 ECO100 ECO200

822 776 1001 799 0 0 ECO200

3-10 User Guide


The original records are those with CHANGE_IN and CHANGE_OUT populated. DataLoad will determine the ID values for the Changes and correctly populate the CHANGE_IN and CHANGE_OUT fields in the database. Agile DataLoad determines and populates the PRIOR_BOM field. If a part is removed from a BOM, an additional row must be created where CHANGEOUT equals CHANGEIN.

Preparing the DataThere are two different procedures for loading BOM history:

❑ Load a full BOM for each revision where the DL_CHANGE_IN equals the Change for the revision, and DL_CHANGE_OUT equals the Change for the next revision. Each row should have DL_OBSOLETE_DATE equal to the release date of the Change for the next revision. Add a second row for each revision where Change_out equals Change_in to remove the previous revision. The current revision does not have a DL_CHANGE_OUT or DL_OBSOLETE_DATE. This is the easiest way to load BOM history; however, it redlines out the entire BOM at each revision.

❑ For each BOM load the initial revision with the initiating Change. Match each successive revision and adjust DL_CHANGE_OUT and DL_OBSOLETE_DATE to reflect the revision that removed the BOM row or changed the BOM row.

• A change would require that the original BOM row be given a DL_CHANGE_OUT equal to the Change that modified the row, and the modified row would be added with that row as DL_CHANGE_IN.

823 776 1002 799 0 0 ECO200

824 776 1004 799 0 0 ECO200

836 776 1001 799 799 815 ECO200

852 776 1002 799 799 820 ECO200

868 776 1003 799 799 821 ECO200

Table 3-9: BOM Table Level Results

ID ITEM ITEM_NUMBER

CHANGE_IN

CHANGE_OUT

PRIOR_BOM

DL_CHANGE_IN

DL_CHANGE_OUT

3-11

Agile DataLoad 2006

• A removal of the row requires that DL_CHANGE_OUT be set to the removing Change, and that the DL_OBSOLTE_DATE be set to the release date of the Change. An additional row is added where Change_out equals Change_in to remove the part.

• An addition creates a new row with DL_CHANGE_IN set to the Change that added the row.

• The current revision will be all rows for the BOM that have no DL_CHANGE_OUT.

This method produces redlines and shows the successive changes in the revisions; however it requires the development of the matching software to develop the proper BOM rows. This is not currently standardized.

Loading without BOM History

If the DL_CHANGE_IN and DL_CHANGE_OUT fields are left blank, no BOM history is loaded and no errors appear for BOM history.

SmartRules

When loading BOM history records using Agile DataLoad, you must set the DuplicateItemNumbers on BOM SmartRule to Allow to load the BOM records.

SummaryWhen attempting to load BOM history, evaluate the legacy data to ensure that the following is provided in the data or can be derived from it:

❑ Full BOM records for each revision of an assembly

❑ Assembly revision information for each full set of BOM records, including obsolete dates

❑ CHANGE_IN and CHANGE_OUT change numbers for each BOM record

3-12 User Guide

APPENDIX AAgile DataLoad

Field Configuration

This appendix contains detailed information about Agile Advantage database fields, attributes, and their valid values. These tables show how DataLoad configures Microsoft Access database source skeleton tables with the Agile Advantage fields that you select, based on current Agile Administrator settings.The following tables are included:❑ SOURCE_Item Table❑ SOURCE_Change Table❑ SOURCE_Rev Table❑ SOURCE_BOM Table❑ SOURCE_Manufacturer Table❑ SOURCE_Mfr_Part Table❑ SOURCE_Approved_Mfr Table❑ SOURCE_User Table❑ SOURCE_RefDesig and SOURCE_RefDesig_2 Tables❑ SOURCE_Customer Table❑ SOURCE_ProblemReport Table

A-1

Agile DataLoad 2006

OverviewUse these tables to determine which optional and required fields to select when using Agile DataLoad to configure Microsoft Access database skeleton source tables. These tables also show what legacy data can be imported, and how it must be formed for import.

In addition to listing possible field selections for each of the Microsoft Access Source tables, the tables provide information for each field to describe the following:

❑ If the field is required

❑ Recommended values for field (when appropriate)

❑ Rules that DataLoad enforces when processing the field and row

❑ Error conditions and messages

❑ What other Agile Advantage database (table) fields are derived from the source field

❑ What Agile Advantage database (table) fields are written to with the data in the source field

Note Agile DataLoad will not load values for field attributes that are not set to Visible.

Agile DataLoad checks the entire row in the source table for errors before writing to the Agile Advantage database. If any error is identified the entire row is not processed, and Agile DataLoad writes the row to the appropriate error table for the source table being processed. Agile DataLoad then continues processing the next row of the source table.

Table Key

Table Symbol Description

A Alphabetical

N Numeric

A/N Alphanumeric

D Date

L List (also marked with in List column)

A-2 User Guide

Appendix A Agile DataLoad Field Configuration

Not Vis. Not Visible - Set by Agile DataLoad*

Opt. Optional

* Rows marked Not Visible - Set by Agile DataLoad or Not Vis. indicate fields that are not visible or selectable from within Agile DataLoad, but for which Agile database values are set automatically. Agile DataLoad will not load values for attributes that are not set to Visible.

Table Key

Table Symbol Description

A-3

Agile DataLoad 2006

A-4 User Guide

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-3

APPENDIX ASO

Tab

plicates allowed.

efined class.

qual an existing user d subclass for the specified

sets to data load date.

URCE_Item Table

le A-1: SOURCE_Item

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values Notes

Req

uir

ed

ITEM_NUMBER item.item_number A/N 75 No du

CLASS item.class L Parts classDocumentation class

Agile d

SUBCLASS item.subclass A/N 30 Examples:

PartDocument

Must edefineclass.

DESCRIPTION item.description A/N 100

Op

t. CLASS_NOTES item.notes A/N 1023

DOCSIZE item.docsize L 2 A, B, C, D, E, J

No

t V

is. MODIFYDATE item.modifydate D System

Ag

ile DataL

oad

2006

A-4

User G

uide

qual an existing Category specified class as defined in t for category attribute.

er Name must be in the list s.

Table A-1: SOURCE_Item (continued)
O
pti

on

al

CATEGORY item.category L 100 Must efor thethe Lis

CLASSS_CREATEUSER

page_two.create_user L The usof user

CLASS_CURRENCY1–5

item.page2.currencyXX

CLASS_DATE01–05 item.page2.dateXX D

CLASS_TEXT01–25 item.page2.textXX A/N 50

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-5

equal an existing List value e specified class as defined in

ist for ListXX attribute.

iple values can be loaded in ield and separated by a

a (,). The values for this are stored in the MSATT .


a (,). The values for this field ored in the MSATT table. equal an existing Multilist for the specified subclass as ed in the List for MultilistXX ute.


s

Op

tio

nal

CLASS_LIST01–25 item.page2.listXX L Mustfor ththe L

PRODUCT_LINES msatt.value L Multthis fcommfield table

CLASS_MULTILIST01 – 03

msatt.value L 100 Multthis fcommare stMustvaluedefinattrib

CLASS_MULTITEXT10

item.page2.multitext10 A/N 256

CLASS_MULTITEXT20


CLASS_MULTITEXT30 - 35

item.page2.multitext3X A/N 1023

SUBCLASS_CURRENCY1 - 5

item.page3.currencyXX

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values Note

Ag

ile DataL

oad

2006

A-6

User G

uide

qual an existing List value specified subclass as defined List for ListXX attribute.

le values can be loaded in ld and separated by a a (,). The values for this field red in the MSATT table. qual an existing Multilist or the specified subclass as d in the List for MultilistXX te.

O
pti

on

al

SUBCLASS_DATE01-05

item.page3.dateXX D

SUBCLASS_LIST01-25

item.page3.listXX L Must efor thein the

SUBCLASS_MULTILIST01-03

msatt.value L Multipthis fiecommare stoMust evalue fdefineattribu

SUBCLASS_MULTITEXT10




SUBCLASS_MULTITEXT30 - 35

item.page3.multitext3X A/N 1023

TARGETCOST Item.target cost

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-7

zero by Agile DataLoad. set via <dbvendor>_ t.sql after complete data set into Agile tables.

zero by Agile DataLoad.


N
ot

Vis

.

FLAGS item.flags A/N 32 Set to Value setcounloaded

OBJVERSION item.objversion N Set to

DELETE_FLAG item.delete_flag N Set to

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ag

ile DataL

oad

2006

A-8

User G

uide

SOTab

s

uplicates allowed.

defined class.

equal an existing user ed subclass for the specified

equal a valid status for the iated workflow. If the status is not released or complete, it will load the default signoff oads the default workflow.

for all Change classes.*

for all Change classes.*

e of a Valid Workflow

URCE_Change Tablele A-2: SOURCE_Change

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values Note

Req

uir

ed

CHANGE_NUMBER

change.change_number A/N 30 No d

CLASS change.class L Change Orders classChange Requests

classDeviations classStop Ships classManufacturer Orders class

Agile

SUBCLASS change.subclass L 30 ECO, ECR, MCO, Deviation, Stop Ship

(other see note)

Mustdefinclass.

STATUS change.status A/N Status associated with a Workflow.

Mustassoctype then and l

CREATE_DATE change.create_date D Valid

RELEASE_DATE change.release_date D Valid

DESCRIPTION change.description A/N 1023

WORKFLOW_ID workflow A/N Workflow Name Nam

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-9

equal an existing Category e specified class as defined in ist for category attribute.

equal an existing reason as defined in the list for the n-code attribute.

m sets to data load date.*

ser Name must be in the list ers.

ser Name must be in the list ers.

ser Name must be in the list ange Analysts for all ges except Manufacturer rs. For MCOs, they must be ponent Engineers.

for ONLY Stop Ships ge class.*

for ONLY Deviations ge class.*

for ONLY Deviations ge class.*

Table A-2: SOURCE_Change (continued)

s

Op

tio

nal

CATEGORY change.category L 100 Mustfor ththe L

REASON_CODE change. reason_code L 2 Mustcodereaso

REASON change.reason A/N 1023

MODIFYDATE change.modifydate D Syste

CLASS_CREATEUSER

change.create_user L The uof us

ORIGINATOR change.originator L The uof us

OWNER change.owner L The uof ChChanOrdeCom

RESUME_DATE change.resume_date D ValidChan

EFFECTIVE_FROM

change.effective_from D ValidChan

EFFECTIVE_TO change.effective_to D ValidChan

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values Note

Ag

ile DataL

oad

2006

A-10

User G

uide

m generated, leave blank s signoff data available.*

m generated, leave blank s signoff data available.*


s

FINAL_COMPLETE_DATE

Change.related QCR.change Final Complete Date

No

t V

is. SUBMIT_DATE change.submit_date D Syste

unles

ROUTE_DATE change.route_date D Systeunles

CLASS_CURRENCY1–5

Change.page2.currencyXX

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values Note

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-11

qual an existing List value specified class as defined in t for ListXX attribute.

le values can be loaded in ld and separated by a a (,). The values for this e stored in the MSATT

le values can be loaded in ld and separated by a a (,). The values for this e stored in the MSATT

ust equal an existing ist value for the specified ss as defined in the List for istXX attribute.


Op

tio

nal

CLASS_DATE01–05

change.page2.dateXX D *

CLASS_TEXT01–25

change.page2.textXX A/N 50

CLASS_LIST01–25 change.page2.listXX L Must efor thethe Lis

PRODUCT_LINES msatt.value L Multipthis fiecommfield artable.


msatt.value L 100 Multipthis fiecommfield artable. MMultilsubclaMultil

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ag

ile DataL

oad

2006

A-12

User G

uide

equal an existing List value e specified subclass as ed in the List for ListXX ute.


a (,). The values for this are stored in the MSATT . Must equal an existing ilist value for the specified ass as defined in the List for ilistXX attribute.


s

Op

tio

nal

CLASS_MULTITEXT10

change.page2.multitext10 A/N 256

CLASS_MULTITEXT20




SUBCLASS_DATE01-05

change.page3.dateXX D *

SUBCLASS_TEXT01-25

change.page3.textXX A/N

SUBCLASS_LIST01-25

change.page3.listXX L Mustfor thdefinattrib


msatt.value L Multthis fcommfield tableMultsubclMult

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values Note

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-13

zero by Agile DataLoad. e set via <db vendor>_ nt.sql after complete data set d into Agile tables.



*


s







SUBCLASS_CURRENCY1-5

Change.page3.currencyXX

No

t V

isib

le -

Set

by

Ag

ile D

ataL

oad FLAGS change.flags A/N 32 Set to

Valusetcouloade

OBJVERSION change.objversion N Set to

DELETE_FLAG change.delete_flag N Set to

Date fields can include time in MS Access date/time format, such as 4/4/99 05:32:13 PM.

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values Note

Ag

ile DataL

oad

2006

A-14

User G

uide

SOTab

IT

CN

R

OD

EFD

FU

IN on will give a warning if this ot populated. FileLoad will ulate this value when

files.*

R

LO

D

T

LI

R ield set by Agile DataLoad to whether the revision is or not.

URCE_Rev Tablele A-3: SOURCE_Rev (Revision Object Fields)

Change Orders

Change Requests Deviations Stop Ships Manufacturer

Orders Notes

EM_NUMBER R R R R R

HANGE_UMBER

R R R R R

EV_NUMBER R O O O O

BSOLETE_ATE

O N/A N/A N/A N/A *

FECTIVE_ATE

R R R R R *

NCTION O O O O O

CORP_DATE O O O O O Validatifield is nnow poploading

ELEASE_TYPE R N/A N/A N/A O

C01-10 O O O O O

ATE01-20 O O O O O *

EXT01-15 O O O O O

ST01-25 O O O O O

ELEASED NV NV NV NV NV Binary findicatereleased

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-15

IN y Agile DataLoad. Indicates the files for the revision n incorporated. Set during oad process.

LA ield set by Agile DataLoad to whether the revision is the r the item.

K

*

Table A-3: SOURCE_Rev (Revision Object Fields) (continued)

CORPORATED NV NV NV NV NV Not set bwhetherhave beethe FileL

TEST_FLAG NV NV NV NV NV Binary findicatelatest fo

EY: R=Required field O=Optional field N/A=not applicable to that class NV=not visible

Date fields can include time in MS Access date/time format, such as 4/4/99 05:32:13 PM.

Change Orders

Change Requests Deviations Stop Ships Manufacturer

Orders Notes

Ag

ile DataL

oad

2006

A-16

User G

uide

SO

Tab

ual an existing item number.

ual an existing item number.

Agile DataLoad defaults

defaults to the value set in ministrator.

ual an existing List value for fied class as defined in the istXX attribute.

URCE_BOM Table

le A-4: SOURCE_BOM

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Req

uir

ed

PARENT_NUMBER

bom.item=select item.item_number from item,bom where item.id=bom.item

A/N Must eq

ITEM_NUMBER bom.item_number A/N 30 Must eq

FIND_NUMBER bom.find_number N 5 max. 32767 If blank,to”0”.

Op

tio

nal

QUANTITY bom.quantity A/N 20 If blank,Agile Ad

DESCRIPTION bom.description A/N 255

NOTES bom.ref_notes A/N 512

DATE01–05 bom.dateXX D

TEXT01–05 bom.textXX A/N 50

LIST01–05 bom.listXX L Must eqthe speciList for L

MULTITEXT30 - 31

bom.page2.multitext3X A/N 1023

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-17

aLoad. Must equal an e Number.

aLoad. Must equal an e Number. Redline ld be created for change_out value

gile DataLoad.

taLoad to assembly’s te date for specific d on change_out

Table A-4: SOURCE_BOM (continued)
N
ot

Vis

.

HIST_CHANGE_IN

bom.change_in A/N Set by Agile Datexisting Chang

HIST_CHANGE_OUT

bom.change_out A/N Set by Agile Datexisting Changdelete row shouBOM rows withset.

PRIOR_ROW bom.prior_row N Set to zero by A

OBSOLETE_DATE

bom.effective_date D Set by Agile Darevision obsoleBOM row basevalue.

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ag

ile DataL

oad

2006

A-18

User G

uide

SO

Tab

Notes

No duplicates allowed.

Agile defined class.

Must equal an existing user defined subclass for the specified class.

URCE_Manufacturer Table

le A-5: SOURCE_Manufacturer

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values

Req

uir

ed

NAME manufacturer.name A/N 30

CLASS manufacturer.class L Manufacturers class

SUBCLASS manufacturer.subclass L 30 Example:

Manufacturer

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-19

Must equal valid Status for specified class.

Table A-5: SOURCE_Manufacturer (continued)

Notes

Op

tio

nal

STATUS manufacturer.status L Examples: Approved, Disqualified, Obsolete

ADDRESS manufacturer.address A/N 100

CITY manufacturer.city A/N 50

STATE manufacturer.state A/N 50

COUNTRY manufacturer.country A/N 50

POSTAL_CODE manufacturer.postal_code A/N 50

CONTACT manufacturer.contact A/N 50

EMAIL manufacturer.email A/N 100

PHONE manufacturer.phone A/N 25

FAX manufacturer.fax A/N 25

URL manufacturer.url A/N 256

CLASS_CREATEUSER

Manufacture.history.user?

CLASS_CURRENCY1-5

Manufacture.page2.currencyXX

CLASS_NOTES Manufacture.page2.notes

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values

Ag

ile DataL

oad

2006

A-20

User G

uide

Must equal an existing List value for the specified class as defined in the List for ListXX attribute.

Multiple values can be loaded in this field and separated by a comma (,). The values for this field are stored in the MSATT table. Must equal an existing Multilist value for the specified subclass as defined in the List for MultilistXX attribute.


Notes

Op

tio

nal

CLASS_DATE01–05

manufacturer.page2.dateXX D

CLASS_TEXT01–25

manufacturer.page2.textXX A/N 50

CLASS_LIST01–25

manufacturer.page2.listXX L


msatt.value L 100

CLASS_MULTITEXT10

manufacturer.page2.multitext10

A/N 256

CLASS_MULTITEXT20


A/N 512


manufacturer.page2.multitext3X

A/N 1023

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-21

Must equal an existing List value for the specified subclass as defined in the List for ListXX attribute.

Multiple values can be loaded in this field and separated by a comma (,). The values for this field are stored in the MSATT table. Must equal an existing Multilist value for the specified subclass as defined in the List for MultilistXX attribute.


Notes

Op

tio

nal

SUBCLASS_DATE01-05

manufacturer.page3.dateXX D

SUBCLASS_TEXT01-25

manufacturer.page3.textXX A/N

SUBCLASS_LIST01-25

manufacturer.page3.listXX L


msatt.value L



A/N 256



A/N 512

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values

Ag

ile DataL

oad

2006

A-22

User G

uide

Set to zero by Agile DataLoad. Value set via <db vendor>_setcount.sql after complete data set loaded into Agile tables.

Set to zero by Agile DataLoad.

Set to zero by Agile DataLoad.


Notes


manufacturer.page3.multitext3X

A/N 1023


Manufacture.page3.currencyXX

No

t V

is. -

Set

by

Ag

ile D

ataL

oad FLAGS manufacturer.flags A/N 32

OBJVERSION manufacturer.objversion N

DELETE_FLAG manufacturer.delete_flag N

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-23

SO

Tab

plicates allowed.

efined class.

qual an existing user d subclass for the ed class.

qual an existing facturer Name from facturer object.

qual valid Status for ed class.

qual an existing List or the specified class as d in the List for ListXX te.

URCE_Mfr_Part Table

le A-6: SOURCE_Mfr_Part

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Req

uir

ed

PART_NUMBER

mfr_part.part_number A/N 30 No du

CLASS mfr_part.class L Manufacturer Parts class

Agile d

SUBCLASS mfr_part.subclass L 30 Example:

Manufacturer Part

Must edefinespecifi

MANUFACTURER

mfr_part.manu_id A/N Must eManuManu

Op

tio

nal

STATUS mfr_part.status L Examples: Active, Obsolete

Must especifi

CLASS_DATE01–05

mfr_part.page2.dateXX D

CLASS_TEXT01–25

mfr_part.page2.textXX A/N 50

CLASS_LIST01–25

mfr_part.page2.listXX L Must evalue fdefineattribu

DESCRIPTION mfr_part.description A/N 100

Ag

ile DataL

oad

2006

A-24

User G

uide

Table A-6: SOURCE_Mfr_Part (continued)

CLASS_CREATEUSER

Mfrpart.history.user

CLASS_CURRENCY1-5

Mfrpart.page2.currencyXX

CLASS_NOTES Mfrpart.description

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-25

ultiple values can be loaded this field and separated by a mma (,). The values for this ld are stored in the MSATT le, and must equal an

isting Multilist value for the cified subclass as defined in List for MultilistXX ribute.

ust equal an existing List lue for the specified subclass defined in the List for tXX attribute.


tes

Op

tio

nal


msatt.value L 100 Min cofietabexspetheatt

CLASS_MULTITEXT10

mfr_part.page2. multitext10

A/N 256

CLASS_MULTITEXT20


A/N 512


mfr_part.page2. multitext3X

A/N 1023

SUBCLASS_DATE01-05

mfr_part.page3.dateXX D

SUBCLASS_TEXT01-25

mfr_part.page3.textXX A/N 50

SUBCLASS_LIST01-25

mfr_part.page3.listXX L Mvaas Lis

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values No

Ag

ile DataL

oad

2006

A-26

User G

uide

ultiple values can be loaded this field and separated by a mma (,). The values for this ld are stored in the MSATT le. Must equal an existing

ultilist value for the cified subclass as defined in List for MultilistXX ribute.


tes

Op

tio

nal


msatt.value L Min cofietabMspetheatt



A/N 256



A/N 512


mfr_part.page3. multitext3X

A/N 1023


Mfrpart.page2.currencyXX

TARGETCOST Mfrpart.targetcost

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values No

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-27

t to zero by Agile DataLoad. lue set via <db vendor>_ count.sql after complete ta set loaded into Agile les.

t to zero by Agile DataLoad.

t to zero by Agile DataLoad.


tes

No

t V

is.

FLAGS mfr_part.flags A/N 32 SeVasetdatab

OBJVERSION mfr_part.objversion N Se

DELETE_FLAG

mfr_part.delete_flag N Se

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Valid Values No

Ag

ile DataL

oad

2006

A-28

User G

uide

SO

Tab

qual an existing item r.

qual an existing cturer part number based

manufacturer name.

qual an existing cturer name. The ation of mfr_part and cturer name must be valid.

qual valid Status.

qual an existing List value specified class as defined in for ListXX attribute.

URCE_Approved_Mfr Table

le A-7: SOURCE_Approved_Mfr

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Req

uir

ed

ITEM_NUMBER manu_by.agile_part A/N Must enumbe

MFR_PART manu_by.manu_part Must emanufaon the

MANUFACTURER N/A A/N Must emanufacombinmanufa

PREFER_STATUS manu_by.prefer_status L Examples: Preferred, Alternate

Must e

Op

tio

nal

REF_NOTES manu_by.ref_notes A/N 2000

DATE01–05 manu_by.dateXX D

TEXT01–05 manu_by.textXX A/N 50

LIST01–05 manu_by.listXX L Must efor thethe List

MULTITEXT30 - 31 manu_by.multitext3X A/N 2000

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-29

ero by Agile DataLoad. No istory is supported in this



Table A-7: SOURCE_Approved_Mfr (continued)
N
ot

Vis

. - S

et b

y A

gile

Dat

aLo

ad CHANGE_IN manu_by.change_in A/N Set to zAML hrelease.

CHANGE_OUT manu_by.change_out A/N Set to zAML hrelease.

PRIOR_ROW manu_by.prior_row N Set to zAML hrelease.

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ag

ile DataL

oad

2006

A-30

User G

uide

SO

Tab

tes.

ME.

lues can be loaded in this parated by a comma (,).

URCE_User Table

le A-8: SOURCE_User

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Req

uir

ed USERNAME A/N No Duplica

FULLNAME A/N 29

Op

tio

nal

EMAIL_ENCODE_TYPE

L MIME, UUENCODE

Default MI

NOTIFICATION L Yes, No

CHANGECAST L Yes, No

ANALYST_SEARCHES

L Yes, No

ANALYST_LIST L Yes, No

COMP_ENGR_SEARCHES

L Yes, No

COMP_ENGR_INBOX

L Yes, No

EMAIL

EMAIL_ATTACH_TYPE

L Agile, wCM Multiple vafield and se

COMMENT

ESCDES_APPROVAL

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-31

ods, dashes, commas.



lues can be loaded in this parated by a comma (,). an existing Role value.

Preferences have been set in tor to disallow a blank

lues can be loaded in this parated by a comma (,). an existing Department

N rtner information for user ac

N

Table A-8: SOURCE_User (continued)
O
pti

on

al

FAX A/N Allows peri

PHONE A/N Allows peri

PAGER A/N Allows peri

STARTUP_URL A/N

ROLE L e.g. ReadOnly, Creator, Incorporator, etc.

Multiple vafield and seMust equal

LOGIN_PASSWORD A/N Required ifAdministrapassword.

APPROVAL_PASSWORD

A/N

DEPARTMENT L Multiple vafield and seMust equalvalue.

ote: The current version of Agile DataLoad does not support loading Program Manager and Pacounts.

ote: All users loaded through Agile DataLoad will be assigned a full user license.

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz


Ag

ile DataL

oad

2006

A-32

User G

uide

SOTh oad. The table is loaded du

Th g DataLoad. The table is loa he same ID. For a given BO w. There is no error ch ed, so the ranges are ha

Tab

A

ID

R

Tab

A

ID

R

URCE_RefDesig and SOURCE_RefDesig_2 Tablese SOURCE_RefDesig table is created when you create a new Access database using DataLring the Load operation.

e SOURCE_RefDesig_2 table is also created when you create a new Access database usinded during the Load operation. The SOURCE_RefDesig_2 table can contain rows with tM row ID, all SOURCE_RefDesig_2 rows with the same ID are loaded for that BOM ro

ecking for reference designators in this table. Ranges are not expanded before being loadndled according to server implementation.

le A-9: SOURCE_RefDesig

ttribute Mapped to

Lis

t F

ield

Typ

e

Siz


N

EFDESIG A 65,535

le A-10: SOURCE_RefDesig_2

ttribute Mapped to

Lis

t F

ield

Typ

e

Siz


N

EFDESIG A 65,535

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-33

SO

Tab

es

de values: Customer Class

e defined class

de values: mples:Customer

st equal and existing user ned subclass for the ified class

duplicates allowed

URCE_Customer Table

le A-11: SOURCE_Customer

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Not

Req

uir

ed

CUSTOMER_NAME customer.customer_name A/N 100

CLASS customer.class L Vali

Agil

SUBCLASS customer.subclass A/N 30 ValiExa

Mudefispec

CUSTOMER_NUMBER customer.customer_number A/N 70 No

SITE_ID customer.site_id A/N 70

SITE_NAME customer.site_name A/N 70

Op

tio

nal

CLASS_CREATEUSER

ADDRESS customer.address A/N 1023

CITY customer.city A/N 50

STATE customer.state L

COUNTRY customer.country L

Ag

ile DataL

oad

2006

A-34

User G

uide

Table A-11: SOURCE_Customer (continued)

es

Op

tio

nal

POSTAL_CODE customer.postal_code A/N 128

PHONE customer.phone A/N 128

URL customer.url A/N 255

FAX customer.fax A/N 128

CONTACT customer.contact A/N 128

CONTACT_EMAIL customer.contact_email A/N 128

CONTACT_PHONE customer.contact_phone A/N 128

CLASS_CURRENCY1-5 Customer.page2.currencyXX

CLASS_DATE01-05 customer.page2.dateXX D

CLASS_LIST01-25 customer.page2.listXX L

CLASS_MULTILIST01-03 L

CLASS_MULTITEXT10-35 customer.page2.multitextXX A/N 1023

CLASS_NOTES customer.page2.notes A/N 1023

CLASS_TEXT01-25 customer.page2.textXX A/N 50

SUBCLASS_DATE01-05 customer.page3.dateXX D

SUBCLASS_LIST01-25 customer.page3.listXX L

SUBCLASS_MULTILIST01-03 customer.page3.multilistXX L

SUBCLASS_MULTITEXT10 customer.page3.multitext10 A/N 256

SUBCLASS_MULTITEXT20 customer.page3.multitext20 A/N 512

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Not

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-35

Table A-11: SOURCE_Customer (continued)

es

SUBCLASS_MULTITEXT30-35 customer.page3.multitext30XX A/N 1023

SUBCLASS_TEXT01-25 customer.page3.textXX A/N 50

SUBCLASS_CURRENCY1-5 Customer.page3.currencyXX

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e Not

Ag

ile DataL

oad

2006

A-36

User G

uide

SO

Tab

otes

o duplicates allowed

gile defined class

ust equal and existing user efined subclass for the pecified class

URCE_ProblemReport Table

le A-12: SOURCE_ProblemReport

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e N

NUMBER problem_report.number A/N 70 N

Req

uir

ed

CLASS problem_report.class L A

SUBCLASS problem_report.subclass A/N 30 Mds

CUSTOMER_NAME problem_report.customer_name A/N 100

SITE_NAME problem_report.site_name A/N 100

ITEM_NUMBER problem_report.item_number A/N 50

CATEGORY problem_report.category L

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-37

Table A-12: SOURCE_ProblemReport (continued)

otes

Op

tio

nal

ASSIGN_TO problem_report.assign_to L

ASSIGN_DATE problem_report.assign_date D

ORIGINATOR problem_report.originator L

DATE_ORIGINATED problem_report.date_originated D

FINAL_COMPLETE_DATE problem_report.final_complete_date D

PRODUCT_LINES problem_report.product_lines L

DESCRIPTION problem_report.description A/N 1023

RESOLUTION_CODE problem_report.resolution_code L

CLASS_CREATEUSER

CLASS_CURRENCY1-5 ProblemReport.page2.currency

STATUS ProblemReport.status

REV_FOUND problem_report.rev_found A/N 20

REV_FIXED problem_report.rev_fixed A/N 20

FAILURE_MODE problem_report.failure_code L

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e N

Ag

ile DataL

oad

2006

A-38

User G

uide

Table A-12: SOURCE_ProblemReport (continued)

otes

Op

tio

nal

CLASS_DATE01-05 problem_report.page2.dateXX D

CLASS_LIST01-25 problem_report.page2.listXX L

CLASS_MULTILIST01-03 L

CLASS_MULTITEXT10 problem_report.page2.multitextXX A/N 256

CLASS_MULTITEXT20 problem_report.page2.multitextXX A/N 512

CLASS_MULTITEXT30-35 problem_report.page2.multitextXX A/N 1023

CLASS_NOTES problem_report.page2.notes A/N 1023

CLASS_TEXT01-25 problem_report.page2.textXX A/N 50

SUBCLASS_DATE01-05 problem_report.page3.dateXX D

SUBCLASS_LIST01-25 problem_report.page3.listXX L

SUBCLASS_MULTILIST01-03 L

SUBCLASS_MULTITEXT10 problem_report.page3.multitextXX A/N

SUBCLASS_MULTITEXT20 problem_report.page3.multitextXX

SUBCLASS_MULTITEXT30-35 problem_report.page3.multitextXX

SUBCLASS_TEXT01-25 problem_report.page3.textXX A/N 50

SUBCLASS_CURRENCY1-5 ProblemReport.page3.currency

WORKFLOW_ID ProblemReport.workflow

Attribute Mapped to

Lis

t F

ield

Typ

e

Siz

e N

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-39

S

A Notes

C Agile Defined Classes

S Must equal an existing user defined subclass for the specified class

SM

No duplicates allowed

SM

CC

MU

OURCE_Supplier Table

ttribute Mapped to

Type

Size

Valid Value

Req'red

Not Visible

LASS ORGANIZATION.CLASS

L suppliers Yes

UBCLASS ORGANIZATION.SUBCLASSORGANIZATION.ORG_SUPPLIER_TYPE

L BrokerComponent ManufacturerContract ManufacturerDistributorManufacturer Representative

Yes

UPPLIER_NUBER

ORGANIZATION.ORG_NUMBER

A/N

128 Yes

UPPLIER_NAE

ORGANIZATION.ORG_NAME

A/N

128 Yes

ORP_URRENCY

ORGANIZATION.ORG_CUR-RENCY_CODE

L Yes

AX_SERS

ORGANIZATION.ORG_MAX_USERS

N Yes

Ag

ile DataL

oad

2006

A-40

User G

uide

A

C

C

CD

If create date is empty, data load will use current date instead

CU

If create user is empty, data load will use it's login user instead

D

D

F

G A cascade level list, separated by a bar

MD

DDRESS ORGANIZATION.ORG_ADDRESS

A/N

1023

ITY ORGANIZATION.ORG_CITY

A/N

128

OUNTRY ORGANIZATION.COUNTRY

L

REATE_ATE

ITEM_HISTORY.TIMESTAMP

D

REATE_SER

ITEM_HISTORY.USER_IDPAGE_TWO.CREATE_USER

L

ESCRIPTION ORGANIZATION.ORG_SHORT_NAME

A/N

128

UNS ORGANIZATION.ORG_SUPPLIER_ID

A/N

128

AX ORGANIZATION.ORG_FAX

A/N

128

EOGRAPHY ORGANIZATION.GEOGRAPHY

L

AX_LICENSE_USERS

ORGANIZATION.ORG_MAX_SUPER_SUPPLIER_USERS

N

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-41

M_

P

P

R

S

U

W

P-

P Must equal an existing List value for the specified class asdefined in the List for ListXXattribute

AX_POWERUSERS

ORGANIZATION.ORG_POWER_LICENSES

N

HONE ORGANIZATION.ORG_PHONE

A/N

128

OSTCODE ORGANIZATION.ORG_POSTAL_CODE

A/N

128

EGION ORGANIZATION.ORG_REGION

L

TATUS ORGANIZATION.ORG_STATUS

L

RL ORGANIZATION.ORG_URL

A/N

150

EB_ENABLED ORGANIZATION.ORG_WEB_FLAG

L

2_DATE0115

PAGE_TWO.DATE01-15 D

2_LIST01-25 PAGE_TWO.LIST01-15

L

Ag

ile DataL

oad

2006

A-42

User G

uide

PE

Money consisted of value and currency separated by a semicolon

P0

Multi-list separated bya semicolon.

PT1

P

PN

P

P

P Must equal an existing List value for the specified class asdefined in the List for ListXXattribute

2_MONY01-10

PAGE_TWO.MONEYVALUE20-29+PAGE_TWO.MONEYCUR-RENCY20-29

M

2_MULTILIST1-03

PAGE_TWO.MULTILIST01-03

L

2_MULTITEX

0, 20,30-45

AGILE_FLEX.TEXT A/N

2_NOTES AGILE_FLEX.TEXT A/N

2_UMERIC01-10

PAGE_TWO.NUMBER01-10

N

2_TEXT01-25 PAGE_TWO.TEXT01-25

A/N

3_DATE31-45 PAGE_THREE.DATE31-45

D

3_LIST31-55 PAGE_LIST31-55 L

Ap

pen

dix A

Ag

ile DataL

oad

Field

Co

nfig

uratio

n

A

-43

PM

Money consisted of value and currency separated by a semicolon

P3

Multi-list separated bya semicolon.

PT,7

P

P3

3_ONEY30-39

PAGE_THREE.MONEYVALUE30-39+PAGE_THREE.MONEY-CURRENCY30-39

M

3_MULTILIST1-33

PAGE_THREE.MULTILIST31-33

L

3_MULTITEX41-45,50,600,80-89

AGILE_FLEX.TEXT A/N

3_NOTES AGILE_FLEX.TEXT A/N

4000

3_NUMERIC1-40

PAGE_THREE.NUMERIC31-40

N

Ag

ile DataL

oad

2006

A-44

User G

uide

APPENDIX BValidations

This appendix lists the validations performed during the Validation stage. See “Stage 7: Validating the Data” on page 2-33.The following sections are included:❑ Agile Administrator Validations❑ Special Characters❑ Referential Integrity Validations❑ Rules and Validations for Reference Designators❑ Customer Validations❑ Problem Report Validations❑ Changes in Final Status Validations

B-1

Agile DataLoad 2006

Agile Administrator ValidationsThe following rules apply during validation of Agile Administrator settings:

❑ For each table, all required columns must exist. If an attribute is required for a single subclass, that column must exist in the table (although not necessarily have a value). Critical errors that cause Validation to stop are the following:

• If the CLASS column is missing for Item, Change, Mfr, Mfr_Part tables.

• If the Key1, Key2, or Key3 columns are missing (specific to each table).

For each table the Key1, Key2, and Key3 fields are as follows: SOURCE_Item (Item_Number), SOURCE_Change (Change_Number), SOURCE_Manufacturer (Name), SOURCE_Mfr_Part (Part_Number, Manufacturer), SOURCE_BOM (Parent_Number, Item_Number, Find_Number), SOURCE_Rev (Item_Number, Rev_Number, Change_Number), SOURCE_Approved_Mfr (Mfr_Part, Manufacturer, Item_Number), SOURCE_Customer (Customer_Number, Site_Id, ), SOURCE_ProblemReport (Number).

❑ Required attributes must have a value. Whether an attribute is required is specific to each class / subclass. If the class is invalid, the rest of the row is not processed. class and subclass are always required fields. If the subclass is invalid, subclass attributes are not processed.

Table B-1: Administrator Validations

Data Type Validations

TEXT fields Validate against Administrator settings for Allow Spaces Case, Format, Max Length, and Required.

DATE fields Validate against Administrator settings for Required.

LIST fields Validate against Administrator settings to ensure that there is a value in the list for every unique value in the SOURCE table and Required.

MULTILIST fields Validate against Administrator settings to ensure that there is a value in the list for every unique value in the SOURCE table and Required.

B-2 User Guide

Appendix B Validations

Special CharactersDuring validation, certain SQL queries match values between tables. If these values contain special characters, the SQL query becomes invalid and an error message appears.

Note The error occurs only with certain fields during validation. The Load process handles all characters without causing errors. Other fields, such as Page 2 or 3, are also unaffected by special characters during Validation and Load. However, as a general rule, you should avoid using special characters in any fields to minimize the potential for errors.

Enter is considered two characters (CR/LF), and should be noted when loading data into fields such as Descriptions.

Special characters (characters that are not supported in an SQL query such as @, #, $, &, or %) are not supported in the following fields, listed per table:

❑ SOURCE_Item : ITEM_NUMBER

❑ SOURCE_Change : CHANGE_NUMBER

❑ SOURCE_Manufacturer : NAME

❑ SOURCE_Mfr_Part : MANUFACTURER, PART_NUMBER

❑ SOURCE_BOM : PARENT_NUMBER, ITEM_NUMBER, FIND_NUMBER

❑ SOURCE_Rev : ITEM_NUMBER, CHANGE_NUMBER, REV_NUMBER

❑ SOURCE_Approved_Mfr : MANUFACTURER, MFR_PART, ITEM_NUMBER

❑ SOURCE_Customer : CUSTOMER_NUMBER, SITE_ID

❑ SOURCE_ProblemReports : ITEM_NUMBER, CUSTOMER_NAME, SITE_NAME

❑ SOURCE_Supplier : SUPPLIER_NUMBER

❑ SOURCE_Contact : CONTACT_NAME

Referential Integrity ValidationsThe following validations are performed for referential integrity:

❑ All fields required for loading must exist in the tables, even if they are not set to Required in Administrator. If a field is missing, Validation stops.

B-3

Agile DataLoad 2006

❑ Fields required for load and which do not have a value are logged as errors.

❑ The DuplicateRefDes SmartRule is not validated.

Table B-2: Referential Integrity Validations

Table Validations

SOURCE_Item Validate that there are no duplicate ITEM_NUMBER entries in the SOURCE_Item and Agile ITEM tables. (ERROR)

Validate that all the columns representing the required fields (ITEM_NUMBER, CLASS, SUBCLASS, and DESCRIPTION) for the Load Process are present and have a value. (ERROR).

SOURCE_Rev Validate that there are no duplicate ITEM_NUMBER + REV combinations on the SOURCE_Rev and Agile REV tables for ECOs. (ERROR)

Validate that for all unique ITEM_NUMBER entries on the SOURCE_Rev table there is an entry in the SOURCE_Item or Agile ITEM table. (ERROR)

Validate that there is no more than one revision of an ITEM_NUMBER for the same CHANGE_NUMBER. (ERROR.)

Validate that the field value for SOURCE_Rev.EFFECTIVE_DATE is greater than or equal to the SOURCE_Change.RELEASE_DATE. (This excludes any blank revs that correspond to Change Requests, MCOs, Deviations and Stop Ships). (ERROR)

Validate that for all unique CHANGE_NUMBER entries on the SOURCE_Rev and Agile REV tables there is an entry in the SOURCE_Change or Agile CHANGE tables. (ERROR)

Validate that all the columns required for the Load process (ITEM_NUMBER, REV_NUMBER, CHANGE_NUMBER, RELEASE_TYPE, EFFECTIVE_DATE) are present and have a value. (ERROR)

B-4 User Guide


SOURCE_Change If the Administrator Settings validation is not run, check whether RELEASE_DATE must have a value, using the same rules as in Administrator Settings for each type of change.

Validate that RELEASE_DATE has a value for these situations:

ECO: Released, ImplementedECR: Released, ClosedMCO: Released, First Article CompleteStopShip: Released, ResumedDeviation: Released, Expired

RELEASE_DATE must not have a value for these situations:

ECO: Pending, Submitted, CCB, Hold, CanceledECR: Pending, Submitted, CCB, Hold, CanceledMCO: Pending, Submitted, CCB, Hold, CanceledStopShip: Pending, Submitted, CCB, Hold, CanceledDeviation: Pending, Submitted, CCB, Hold, Canceled

(ERROR).

Validate that there are no duplicate CHANGE_NUMBER entries in the SOURCE_Change and Agile CHANGE tables. (ERROR)

Validate that all the columns representing the required fields (CHANGE_NUMBER, CLASS, SUBCLASS, STATUS, RELEASE_DATE, and DESCRIPTION) for the Load process are present and have a value. (ERROR)

Validate that RELEASE_DATE is later than CREATE_DATE (ERROR). These are not necessarily required fields, so no error is logged if either field is missing or empty.

Validate that EFFECTIVE_TO is later than EFFECTIVE_FROM (ERROR). These are not necessarily required fields, so no error is logged if either field is missing or empty.


Table Validations

B-5

Agile DataLoad 2006

SOURCE_BOM Validate that PARENT_NUMBER is different from ITEM_NUMBER (recursive BOM). (ERROR)

Validate, according to Smart Rule settings in Administrator (Allow, Warning, or Error), that there are no duplicate ITEM_NUMBER entries in the SOURCE_BOM and Agile BOM tables.

Validate that for all unique ITEM_NUMBER and PARENT_NUMBER entries on the SOURCE_BOM table there is an entry in the SOURCE_Item or Agile Item tables. (ERROR)

Validate that all the columns representing the required fields (PARENT_NUMBER, ITEM_NUMBER and FIND_NUMBER) for the Load Process are present and have a value. (ERROR)

Validate the following Smart Rules according to settings in Administrator (checked only during local Referential Integrity checks): DuplicateFindNumbers, ItemsReleasedFirst, EffectivityDateOrder, EffectivityGap, EffectivityOverlap, DuplicateItemNumber.

SOURCE_RefDesig Errors are logged for all rows with an ID value that do not have a corresponding entry in the SOURCE_BOM table. Errors are logged for all invalid Reference Designators. Unlike the Reference Designator check in the Data Mapper (5.11), Validation does not check the Valid RefDesig Prefixes table for the list of valid prefixes, so any Reference Designator starting with a set of Alpha characters will be valid. A valid Reference Designator is a prefix and number, with an optional suffix. Duplicate Reference Designators are imported without being flagged as errors. Refer to “Rules and Validations for Reference Designators” on page B-9.

SOURCE_RefDesig_2 Errors are logged for BOM rows with an ID value that does not match in either SOURCE_RefDesig or SOURCE_RefDesig_2. Warnings are logged for ID values in SOURCE_RefDesig_2 that do not match those in SOURCE_BOM.

SOURCE_Mfr Validate that there are no duplicate NAME entries in the SOURCE_Mfr and Agile MANUFACTURERS tables. (ERROR)

Validate that all the columns representing the required fields (NAME, CLASS, and SUBCLASS) for the Load process are present and have a value. (ERROR)


Table Validations

B-6 User Guide


SOURCE_Mfr_Part Validate that there are no duplicate PART_NUMBER + MANUFACTURER entries in the SOURCE_Mfr_Part and Agile MANU_PARTS tables. (ERROR)

Validate that the field value for SOURCE_Mfr_Part.MANUFACTURER is not null. (ERROR)

Validate that for every unique value in the SOURCE_Mfr_Part.MANUFACTURER field, there is a corresponding value in the SOURCE_Mfr or Agile MFR table. (ERROR)

Validate that the SOURCE_Mfr_Part.PART_NUMBER field is not null. (ERROR)

Validate that all the columns representing the required fields (MANUFACTURER, NAME, CLASS and SUBCLASS) for the Load process are present and have a value. (ERROR)

SOURCE_Approved_Mfr

Validate that for all unique ITEM_NUMBER entries on the SOURCE_Approved_Mfr table there is an entry in the SOURCE_Item or Agile ITEM table. (ERROR)

Validate that all Manufacturer Numbers (Mfr/MfrPart combinations) exist on the SOURCE_Mfr_Part or Agile MANU_PARTS table. (ERROR)

Validate that there are no duplicate rows on the SOURCE_Approved_Mfr table. (ERROR)

Validate, according to Smart Rule settings in Administrator (Allow, Warning, or Error), that there is not more than one Item with the same Manufacturer Number.

Validate that all the columns representing the required fields (MANUFACTURER, MFR_PART, and ITEM_NUMBER) for the Load process are present and have a value. (ERROR)

Validate the MultipleItemsPerManufPart Smart Rule per settings in Administrator (checked only during local Referential Integrity checks).


Table Validations

B-7

Agile DataLoad 2006

SOURCE_Customer Validate that there are not multiple rows with the same Customer_Number and Site_Id.

Validate that there are not multiple rows with the same Customer_Number and different Customer_Names.

Validate that there are not multiple rows with the same Customer_Name and different Customer_Numbers.

Validate that there are not multiple rows with the same Customer_Number and Site_Id but different Site_Names.

Validate that there are not multiple rows with the same Customer_Number and Site_Name but different Site_Ids.

SOURCE_ProblemReport

Validate that there are not multiple rows with the same Number.

Validate that the Item_Number exists.

Validate that the Customer_Name exists.

Validate that the Site_Name exists.

SOURCE_Supplier Validate that there are not multiple rows with the same SUPPLIER_NUMBER and SUPPLIER_NAME.

Validate that the SUPPLIER_NUMBER exists.

Validate that the SUPPLIER_NAME exists.

SOURCE_Contact Validate that there are not multiple rows with the same CONTACT_NAME.

Validate that the CONTACT_NAME exists.


Table Validations

B-8 User Guide


Rules and Validations for Reference DesignatorsThis section describes the modifications and additions to the Reference Designators (RefDesigs) implemented by Agile DataLoad.

Single Reference Designator Rules

These are the rules for single Reference Designators.

❑ Rule 1 — A single RefDesig must not exceed the maximum length defined in Agile Administrator.

❑ Rule 2 — A RefDesig consists of any combination of alphanumerical characters, uppercase or lowercase. Punctuation characters or special characters are not allowed in a single RefDesig. The RefDesig comparison is case-sensitive. For example:

• A1b is valid.

• A1b is different from A1B.

• 7 is valid.

• P is valid.

• *5 is invalid.

• F+5 is invalid.

Reference Designator Range Rules

These are the rules for Reference Designators that cover a range of two or more.

❑ Rule 3 — A RefDesig range is indicated by two RefDesigs that are separated by a hyphen. There can be empty spaces surrounding the hyphen. For example:

• A1-A10 is valid.

• A1 - A10 is valid.

❑ Rule 4 — If a range is invalid (for example, it does not qualify for expansion), it isn’t a valid single RefDesig either. For example:

• A1-A10 is a valid range.

• A1-A10a is neither a range nor a valid single RefDesig.

B-9

Agile DataLoad 2006

❑ Rule 5 — Both of the RefDesigs in a range must end in a number, or a number followed by the same suffix. For example:


• A1a-A10a is valid.

• A1-A10a is invalid.

• A1a-A10c is invalid.

❑ Rule 6 — The number of the second RefDesig in a range must be greater than the number of the first RefDesig. For example:


• A10-A10 is invalid.

• A10-A8 is invalid.

❑ Rule 7 — If both RefDesigs in a range contain prefixes, the prefixes can be any combination of alphanumerical characters ending in a character, and the prefixes must be identical. The RefDesig comparison is case-sensitive.

For example:

• A23B6-A23B8 is valid.

• A23B6-A24B8 is invalid.

• A23B6-A23b8 is invalid.

❑ Rule 8 — If the first RefDesig in a range contains a prefix, the second RefDesig in the range is expanded as though its prefix was identical to that of the first RefDesig. For example:

A3b6-9 is expanded to A3b6, A3b7, A3b8, A3b9.

❑ Rule 9 — If neither of the RefDesigs contains a prefix, then the range is valid. For example:

210-213 is expanded to 210, 211, 212, 213.

❑ Rule 10 — Single RefDesigs or ranges of RefDesigs, can be separated by a whitespace or a comma. If there is no comma present, any number of whitespaces is acceptable. If there is a comma, any number of whitespaces can appear on either side of the comma, but two commas will be flagged as an error. For example:

• B1 B10 is valid.

B-10 User Guide


• B1,B10 is valid.

• B1-B10 C1-C10 is valid.

• B1-B10,C1-C10 is valid.

Validations for Reference Designators

These are the validations for single and ranged Reference Designators.

❑ Validation 1 — RefDesigs that are invalid, according to the rules above, are flagged as errors.

❑ Validation 2 — Flags for duplicate RefDesigs are designated by the SmartRule setting.

❑ Validation 3 — Mismatches between the value of QUANTITY and the actual number of valid RefDesigs are flagged as a warning.

❑ Validation 4 — ID values in the SOURCE_BOM table that have no match in the SOURCE_RefDesig table are flagged as errors.

❑ Validation 5 — ID values in the SOURCE_RefDesig table that have no match in the SOURCE_BOM table are flagged as warnings.

❑ Validation 6 — Duplicate ID values in the SOURCE_BOM table are flagged as errors.

❑ Validation 7 — Duplicate ID values in the SOURCE_RefDesig table are flagged as errors.

❑ Validation 8 — Rows in the SOURCE_RefDesig table with missing values for ID or REFDESIG are flagged as warnings.

Note Records must not exceed 16,384 characters. If you add 3,000 to 4,000 reference resignators to a given record, you will probably exceed the overall length limit and receive the corresponding error message in the VALIDATION_ERRORS table.

Customer ValidationsThe following errors occur for Customer objects:

❑ Rows have the same Customer ID, but different Customer Name

❑ Rows have the same Customer Name, but different Customer ID

❑ Rows have the same Customer ID and Site ID, but different Site Name

B-11

Agile DataLoad 2006

❑ Rows have the same Customer ID and Site Name, but different Site IDs

❑ Rows have the same Customer ID and Site ID

❑ Customer ID or Customer Name already exists with a different value on the server

❑ Site ID already exists for the customer on the server

Problem Report ValidationsThe following errors occur for Problem Report objects:

❑ Rows have duplicate PR numbers

❑ Rows have an unmatched Item Number

❑ Rows have an unmatched Customer Name

❑ Rows have an unmatched Site Name

❑ PR number already exists on the server

❑ Item Number does not exist locally or on the server

❑ Customer Name does not exist locally or on the server

Note Agile DataLoad checks the PR item revision if the item (and rev) appear in the Access tables, but it cannot obtain information about revs for items that exist on the server.

Agile DataLoad validates whether or not a given PR item already exists on the server, but it cannot return information about whether or not the revision exists.

Changes in Final Status ValidationsErrors occur for Changes in a Final status if the following validations do not succeed:

❑ A record must have a Release Date and a Final Complete Date

❑ Release Date must be equal to or less than the Final Complete Date

❑ If there is an Effective Date, it must be equal to or greater than the Release Date and equal to or less than the Final Complete Date

B-12 User Guide

INDEX

AAdd Button 2-30, 2-38, 2-42Administrator Settings Checks 2-35Administrator Validations (table) B-2agrn.exe 1-4

BBOM History

BOM Table Structure 3-3Data Preparation 3-11SmartRules 3-12SOURCE Data Structures 3-7Summary 3-12

BOM History Records 2-17

CConfigure New Microsoft Access DB

button 2-8Create Button 2-31Create Selection Lists File 2-29

DDataLoad

Automap 2-21Configuring the Agile Database 2-7Data Mapping Wizard 2-15Enabling Data Loading 1-4Field Map 2-22Prerequisites 1-3Reports 2-13Table Key for Fields A-2Table Map 2-22

EError Tables 2-6, 2-14, 2-16, 2-43, 2-44

IInstallation 1-3

Microsoft Access 2000 1-3

LLegacy Data 2-6List Values 2-29, 2-31Lists 2-5, 2-28Load From

Error Tables 2-44Source Tables 2-42

Log on to Agile Server Checkbox 2-35

MMicrosoft Access

Database Conversion 1-3Database Validation 2-33Delimiters 2-6Loading a Preconfigured Database

2-40Start Load 2-44

Multilists 2-5, 2-28

OObsolete Dates 2-17Open Button 2-30, 2-38, 2-42Open Database with MS Access button

2-13Oracle Data Manager 2-7Output to this file Text Box 2-31

PPopulate Description Tables with Attribute

Names 2-13

RRecommended Values for Fields A-2Reference Designator

Rules B-9Referential Integrity Checks 2-35

Index-1

Agile DataLoad 2006

Referential Integrity Validations (table) B-4

Remember Password 2-41Remove Button 2-30, 2-38, 2-42Required and Optional Fields A-2Requirements 3-2Revision History 2-17Rollback 2-43Row by Row Processing 2-16, 2-28, A-2Rules (Processing) A-2

SSelect Optional Fields 2-10Skeleton Tables 2-6, 2-13SOURCE_Approved_Mfr table A-28SOURCE_BOM table A-16, A-32, A-33,

A-35SOURCE_Change table A-8SOURCE_Item table A-3SOURCE_Manufacturer table A-18SOURCE_Mfr_Part table A-23SOURCE_User Table A-30Start Load Button 2-42Stop Button 2-42

TTable Fields Derived From Source A-2

VValid Change Status Values (table) A-14Validation 2-6VALIDATION_ERRORS table 2-14View Configuration 2-12View File Button 2-31

Index-2 User Guide