Agile Advantage 2006 - Oracle · Agile DataLoad uses Microsoft Access to hold and transfer legacy data into the Agile Advantage database. An Agile Administrator user account with

Agile DataLoad™ 2006for Agile Advantage™

User Guide

Copyrights and TrademarksCopyright © 1995-2006 Agile Software Corporation. All rights reserved. You shall not create any derivative works of this publication nor shall any part of this publication be copied, reproduced, distributed, published, licensed, sold, stored in a retrieval system or transmitted in any form or by any means: electronic, mechanical, photocopying, or otherwise, without the prior written consent of Agile Software Corporation, 6373 San Ignacio Avenue, San Jose, California 95119-1200 U.S.A.; Telephone 408.284.4000, Facsimile 408.284.4002, or http://sme.agile.com.

The material in this manual is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this manual to assure its accuracy, Agile Software Corporation assumes no liability resulting from errors or omissions in this manual, or from the use of the information contained herein.

Agile Software Corporation reserves the right to make changes in the product design without reservation and without notification to its users.

Agile Software is a registered trademark of Agile Software Corporation.

The Agile logo, Agile Administrator, Agile Advantage, Agile Anywhere, Agile Application Server, Agile Product Record Management, Agile Program Management, Agile Product Compliance Management, Agile Standards & Compliance Management, Agile Document Management & Control, Agile Quality Management, Agile Product Sourcing, Agile Design Collaboration, Agile View & Markup, Agile Engineering Integration, Agile Enterprise Integration, Agile ChangeCAST, Agile Content Service, Agile Advantage eHub, Agile Export, Agile eXpress, Agile Advantage iFS, Agile Import, Agile Integration Server, Agile Document Scanning & Processing, AgileScript, Agile ADK, Agile Sourcing Intelligence, Agile Supplier, Agile Unwired, Agile Viewer, and MyAgile.com are trademarks of Agile Software Corporation.

Microsoft, Microsoft Windows, Microsoft Word, Microsoft Excel, and Internet Explorer are registered trademarks of Microsoft Corporation.

Oracle and Oracle 10g are registered trademarks of Oracle Corporation.

Engineering Data eXchange (EDX) for SolidWorks, Engineering Data eXchange (EDX) for Pro/ENGINEER, and Sarbanes-Oxley Compliance Pack are trademarks of Syncronus Corporation.

All other product names are trademarks, registered trademarks, or trade names of their respective owners.

Part No. TP-SBS-EN1042-2006A

April 26, 2006

CONTENTS

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vDocumentation Roadmap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Preface

Readme File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viOther Information Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi

Agile Online Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .viManual Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vi

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

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-15

iii

Agile DataLoad 2006

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17BOM History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

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

iv User Guide

Contents

Chapter 3 Loading BOM History

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Agile BOM Table Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3SOURCE 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-12

v

Agile DataLoad 2006

Changes in Final Status Validations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13

Index

vi User Guide

PREFACE

About This GuideWelcome to the Agile DataLoad 2006 User Guide.

This guide describes Agile DataLoad 2006, including the following chapters:

❑ Chapter 1, “Introduction,” introduces Agile DataLoad 2006, provides information about this release, and discusses installation.

❑ Chapter 2, “Using Agile DataLoad,” describes how to use Agile DataLoad 2006 and Microsoft Access to import customer legacy data into Agile Advantage.

❑ Chapter 3, “Loading BOM History,” describes the requirements and instructions for loading BOM History from source databases.

❑ Appendix A, “Agile DataLoad Field Configuration,” contains information about database fields, attributes, and valid values.

❑ Appendix B, “Validations,” contains information about record dependencies among the records in the SOURCE tables.

The Agile documentation includes Adobe® Acrobat® PDF files available online. Also, ask your Agile administrator if there is a Documentation folder available on your network, from which you can access the Agile documentation (PDF) files.

Note To read the PDF files, use the free Adobe® Acrobat® Reader™. For more information about Adobe Acrobat Reader, visit www.adobe.com.

Before you install, you should check for possible updates to the documentation files by visiting the Documentation section of the Support area of the Agile Web site at http://support.agilesoft.com/docs/2006/index.asp. If you do not have access, please contact [email protected] for assistance.

Documentation Roadmap

You can find a complete list of all Agile Advantage documentation from the Help menu, or by visiting the Documentation section of the Support area of the Agile Web site athttp://support.agilesoft.com/docs/2006/index.asp.

v

Agile DataLoad 2006

Readme File

The Agile readme file contains up-to-date information that may be useful to you in configuring Agile Advantage. You can view the readme file from the main Agile Installation folder.

Other Information SourcesYou can get additional help in a number of ways.

Agile Online Support

For product support or information about Agile products and services, visit the Agile Web site at http://www.agile.com.

Customers with a current Agile Support agreement (existing account required or request an account by e-mail to [email protected]) can log in to this site to access the following online services for Agile Software® products:

❑ Problem status and reporting

❑ Alerts

❑ Frequently asked questions (FAQs)

❑ Documentation

Manual ConventionsThe following table lists conventions used in the documentation, and gives an example of how each convention is applied.

Table 1: Conventions used in this manual

Convention Example

Text from the user interface (for example, field names, nodes, and menus and commands) are shown in a sans serif bold font.

Select the SmartRules node.

Click OK.

Text you need to type is shown in Courier.

Type the username Administrator.

Placeholders for variable text are shown in Italic.

Set the directory to drive:\Agile\Qadmin\.

vi User Guide

Preface

A vertical bar is used to separate a menu name from its menu command; to indicate the expansion of nodes and subnodes; and to indicate software keys.

You can generate Agile Administrator reports from the Tools | Reports menu.Expand the Change Orders | Attributes | Cover Page node.HKEY_CURRENT_USER | Software.

An environment variable is enclosed in percent (%) signs.

Change the OAS root file-system folder to %DMI_DB_ROOT%\html\.

Right-click means to press and release the right mouse button.

Right-click to see the shortcut menu.

A plus sign (+) means to hold down one key while pressing another.

To open the File menu, press Alt+F.

Shift+click means to press and hold the Shift key while clicking the mouse button.

Shift+click to select a block of items in the list.

Ctrl+click means to press and hold the Ctrl key while clicking the mouse button.

Ctrl+click to select non-contiguous items in the list.

The term “computer” generically refers to hardware for a server or workstation. Note that multiple types of server software can run on a single computer.

Import the Agile database file to replicate the database on another computer.

Table 1: Conventions used in this manual

Convention Example

vii

Agile DataLoad 2006

viii User Guide

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 oracle_resetlatestrev2005.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.

2 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.

3 oracle_resetflag2005.sql — Sets up a new internal 32-bit flag to control BOM, Rev, and Where Used.

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

5 oracle_setactive2005.sql — Resets the active object for Manufacturer searches. You need to run this script only if you load Manufacturer data.

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


6 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.

7 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.

8 oracle_averify2005.sql — Checks the Agile Advantage database integrity.

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

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

11 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.

2-49

Agile DataLoad 2006

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-50 User Guide


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-51

Agile DataLoad 2006

❑ 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-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.

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


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

Appendix A Agile DataLoad Field ConfigurationAP

PEN

DIX

A
SO
URCE

_Ite

m T

able

Tabl

e A-

1:

SOUR

CE_I

tem

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

Required

ITE

M_N

UM

BE

Rit

em.it

em_n

um

ber

A/N

75N

o du

plic

ates

allo

wed

.

CL

ASS

item

.cla

ssL

Par

ts c

lass

Doc

um

enta

tion

cl

ass

Agi

le d

efin

ed c

lass

.

SUB

CLA

SSit

em.s

ubc

lass

A/N

30

Exa

mpl

es:

Par

tD

ocu

men

t

Mu

st e

qual

an

exi

stin

g u

ser

defi

ned

su

bcla

ss fo

r th

e sp

ecif

ied

clas

s.

DE

SCR

IPT

ION

item

.des

crip

tion

A/N

100

Opt.

CLA

SS_N

OT

ES

item

.not

esA

/N10

23

DO

CSI

ZE

item

.doc

size

L2

A, B

, C, D

, E, J

Not Vis.

MO

DIF

YD

AT

Eit

em.m

odif

ydat

eD

Syst

em s

ets

to d

ata

load

dat

e.

A-3

Agile DataLoad 2006
Optional
CA

TE

GO

RY

item

.cat

egor

yL

100

Mu

st e

qual

an

exi

stin

g C

ateg

ory

for

the

spec

ifie

d cl

ass

as d

efin

ed in

th

e Li

st fo

r ca

tego

ry a

ttri

bute

.

CL

ASS

S_C

RE

AT

EU

SER

page

_tw

o.cr

eate

_use

rL

Th

e u

ser

Nam

e m

ust

be

in t

he

list

of u

sers

.

CL

ASS

_C

UR

RE

NC

Y1–

5it

em.p

age2

.cu

rren

cyX

X

CL

ASS

_DA

TE

01–0

5it

em.p

age2

.dat

eXX

D

CL

ASS

_TE

XT

01–2

5it

em.p

age2

.tex

tXX

A/N

50

Tabl

e A-

1:

SOUR

CE_I

tem

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-4 User Guide

Optional
CL

ASS

_LIS

T01

–25

item

.pag

e2.li

stX

XL

Mu

st e

qual

an

exi

stin

g L

ist v

alu

e fo

r th

e sp

ecif

ied

clas

s as

def

ined

in

the

List

for

Lis

tXX

att

ribu

te.

PR

OD

UC

T_L

INE

Sm

satt

.val

ue

LM

ult

iple

val

ues

can

be

load

ed in

th

is fi

eld

and

sepa

rate

d by

a

com

ma

(,).

Th

e va

lues

for

this

fi

eld

are

stor

ed in

th

e M

SAT

T

tabl

e.

CL

ASS

_MU

LT

ILIS

T01

– 0

3m

satt

.val

ue

L10

0M

ult

iple

val

ues

can

be

load

ed in

th

is fi

eld

and

sepa

rate

d by

a

com

ma

(,).

The

val

ues

for t

his

fiel

d ar

e st

ored

in t

he

MSA

TT

tab

le.

Mu

st e

qual

an

exi

stin

g M

ult

ilist

va

lue

for

the

spec

ified

su

bcla

ss a

s de

fin

ed in

the

Lis

t for

Mu

ltili

stX

X

attr

ibu

te.

CL

ASS

_MU

LT

ITE

XT

10it

em.p

age2

.mu

ltit

ext1

0A

/N25

6

CL

ASS

_MU

LT

ITE

XT

20it

em.p

age2

.mu

ltit

ext2

0A

/N51

2

CL

ASS

_MU

LT

ITE

XT

30 -

35

item

.pag

e2.m

ult

itex

t3X

A/N

1023

SUB

CLA

SS_

CU

RR

EN

CY

1 -

5it

em.p

age3

.cu

rren

cyX

X

Tabl

e A-

1:

SOUR

CE_I

tem

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-5

Agile DataLoad 2006
Optional
SUB

CLA

SS_D

AT

E01

-05

item

.pag

e3.d

ateX

XD

SUB

CLA

SS_L

IST

01-

25it

em.p

age3

.list

XX

LM

ust

equ

al a

n e

xist

ing

Lis

t val

ue

for

the

spec

ifie

d su

bcla

ss a

s de

fin

ed

in t

he L

ist f

or L

istX

X a

ttri

bute

.

SUB

CLA

SS_

MU

LT

ILIS

T01

-03

msa

tt.v

alu

eL

Mu

ltip

le v

alu

es c

an b

e lo

aded

in

this

fiel

d an

d se

para

ted

by a

co

mm

a (,

). T

he v

alu

es fo

r th

is fi

eld

are

stor

ed in

th

e M

SAT

T t

able

. M

ust

equ

al a

n e

xist

ing

Mu

ltili

st

valu

e fo

r th

e sp

ecifi

ed s

ubc

lass

as

defi

ned

in th

e L

ist f

or M

ult

ilist

XX

at

trib

ute

.

SUB

CLA

SS_

MU

LTIT

EX

T10

item

.pag

e3.m

ult

itex

t10

A/N

256

SUB

CLA

SS_

MU

LTIT

EX

T20

item

.pag

e3.m

ult

itex

t20

A/N

512

SUB

CLA

SS_

MU

LTIT

EX

T30

- 3

5it

em.p

age3

.mu

ltit

ext3

XA

/N10

23

TA

RG

ET

CO

STIt

em.t

arge

t co

st

Tabl

e A-

1:

SOUR

CE_I

tem

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-6 User Guide

Not Vis.
FLA

GS

item

.fla

gsA

/N32

Set

to z

ero

by A

gile

Dat

aLoa

d.

Val

ue

set

via

<db

vend

or>

_ se

tcou

nt.s

ql a

fter

com

ple

te d

ata

set

load

ed in

to A

gile

tab

les.

OB

JVE

RSI

ON

item

.obj

vers

ion

NSe

t to

zer

o by

Agi

le D

ataL

oad.

DE

LET

E_F

LAG

item

.del

ete_

flag

NSe

t to

zer

o by

Agi

le D

ataL

oad.

Tabl

e A-

1:

SOUR

CE_I

tem

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-7

Agile DataLoad 2006

SOUR

CE_C

hang

e Ta

ble

Tabl

e A-

2:

SOUR

CE_C

hang

e

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

Required

CH

AN

GE

_N

UM

BE

Rch

ange

.ch

ange

_nu

mbe

rA

/N30

No

dupl

icat

es a

llow

ed.

CLA

SSch

ange

.cla

ssL

Ch

ange

Ord

ers

clas

sC

han

ge R

equ

ests

cl

ass

Dev

iati

ons

clas

sSt

op S

hips

cla

ssM

anu

fact

ure

r Ord

ers

clas

s

Agi

le d

efin

ed c

lass

.

SUB

CL

ASS

chan

ge.s

ubc

lass

L30

EC

O, E

CR

, MC

O,

Dev

iati

on, S

top

Shi

p

(oth

er s

ee n

ote)

Mu

st e

qual

an

exi

stin

g u

ser

defi

ned

su

bcla

ss fo

r th

e sp

ecif

ied

clas

s.

STA

TU

Sch

ange

.sta

tus

A/N

Stat

us

asso

ciat

ed

wit

h a

Wor

kflo

w.

Mu

st e

qual

a v

alid

sta

tus

for

the

asso

ciat

ed w

orkf

low

. If t

he

stat

us

typ

e is

not

rele

ased

or

com

plet

e,

then

it w

ill lo

ad th

e de

fau

lt si

gnof

f an

d lo

ads

the

defa

ult

wor

kflo

w.

CR

EA

TE

_DA

TE

chan

ge.c

reat

e_d

ate

DV

alid

for

all C

han

ge c

lass

es.*

RE

LE

ASE

_DA

TE

chan

ge.r

elea

se_d

ate

DV

alid

for

all C

han

ge c

lass

es.*

DE

SCR

IPT

ION

chan

ge.d

escr

ipti

onA

/N10

23

WO

RK

FLO

W_I

Dw

orkf

low

A/N

Wor

kflo

w N

ame

Nam

e of

a V

alid

Wor

kflo

w

A-8 User Guide

Optional
CA

TE

GO

RY

chan

ge.c

ateg

ory

L10

0M

ust

equ

al a

n e

xist

ing

Cat

egor

y fo

r th

e sp

ecif

ied

clas

s as

def

ined

in

the

List

for

cate

gory

att

ribu

te.

RE

ASO

N_C

OD

Ech

ange

. rea

son

_cod

eL

2M

ust

equ

al a

n e

xist

ing

reas

on

code

as

defi

ned

in t

he

list

for

the

reas

on-c

ode

attr

ibu

te.

RE

ASO

Nch

ange

.rea

son

A/N

1023

MO

DIF

YD

AT

Ech

ange

.mod

ifyd

ate

DSy

stem

set

s to

dat

a lo

ad d

ate.

*

CL

ASS

_C

RE

AT

EU

SER

chan

ge.c

reat

e_u

ser

LT

he

use

r N

ame

mu

st b

e in

the

list

of u

sers

.

OR

IGIN

AT

OR

chan

ge.o

rigi

nat

orL

Th

e u

ser

Nam

e m

ust

be

in th

e lis

t of

use

rs.

OW

NE

Rch

ange

.ow

ner

LT

he

use

r N

ame

mu

st b

e in

the

list

of C

han

ge A

nal

ysts

for

all

Ch

ange

s ex

cept

Man

ufa

ctu

rer

Ord

ers.

For

MC

Os,

th

ey m

ust

be

Com

pon

ent

En

gin

eers

.

RE

SUM

E_D

AT

Ech

ange

.res

um

e_da

teD

Val

id fo

r O

NLY

Sto

p Sh

ips

Cha

nge

cla

ss.*

EFF

EC

TIV

E_

FRO

Mch

ange

.eff

ecti

ve_f

rom

DV

alid

for

ON

LY

Dev

iati

ons

Cha

nge

cla

ss.*

EFF

EC

TIV

E_T

Och

ange

.eff

ecti

ve_t

oD

Val

id fo

r O

NL

Y D

evia

tion

s C

han

ge c

lass

.*

Tabl

e A-

2:

SOUR

CE_C

hang

e (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-9

Agile DataLoad 2006

FIN

AL

_C

OM

PL

ET

E_

DA

TE

Ch

ange

.rel

ated

Q

CR

.ch

ange

Fin

al

Com

plet

e D

ate

Not Vis.

SUB

MIT

_DA

TE

chan

ge.s

ubm

it_d

ate

DSy

stem

gen

erat

ed, l

eave

bla

nk

un

less

sig

nof

f dat

a av

aila

ble.

*

RO

UT

E_D

AT

Ech

ange

.rou

te_d

ate

DSy

stem

gen

erat

ed, l

eave

bla

nk

un

less

sig

nof

f dat

a av

aila

ble.

*

CL

ASS

_C

UR

RE

NC

Y1–

5C

han

ge.p

age2

.cu

rren

cyX

X

Tabl

e A-

2:

SOUR

CE_C

hang

e (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-10 User Guide

Optional
CL

ASS

_DA

TE

01–

05ch

ange

.pag

e2.d

ateX

XD

*

CL

ASS

_TE

XT

01–

25ch

ange

.pag

e2.t

extX

XA

/N50

CL

ASS

_LIS

T01

–25

chan

ge.p

age2

.list

XX

LM

ust

equ

al a

n e

xist

ing

Lis

t va

lue

for

the

spec

ifie

d cl

ass

as d

efin

ed in

th

e Li

st fo

r L

istX

X a

ttri

bute

.

PR

OD

UC

T_L

INE

Sm

satt

.val

ue

LM

ult

iple

val

ues

can

be

load

ed in

th

is fi

eld

and

sepa

rate

d by

a

com

ma

(,).

The

val

ues

for

this

fi

eld

are

stor

ed in

th

e M

SAT

T

tabl

e.

CL

ASS

_M

UL

TIL

IST

01 –

03

msa

tt.v

alu

eL

100

Mu

ltip

le v

alu

es c

an b

e lo

aded

in

this

fiel

d an

d se

para

ted

by a

co

mm

a (,

). T

he v

alu

es fo

r th

is

fiel

d ar

e st

ored

in t

he

MSA

TT

ta

ble.

Mu

st e

qual

an

exi

stin

g M

ult

ilist

val

ue

for

the

spec

ifie

d su

bcla

ss a

s de

fin

ed in

the

List

for

Mu

ltili

stX

X a

ttri

bute

.

Tabl

e A-

2:

SOUR

CE_C

hang

e (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-11

Agile DataLoad 2006
Optional
CL

ASS

_M

ULT

ITE

XT

10ch

ange

.pag

e2.m

ult

itex

t10

A/N

256

CL

ASS

_M

ULT

ITE

XT

20ch

ange

.pag

e2.m

ult

itex

t10

A/N

512

CL

ASS

_M

UL

TIT

EX

T30

-

35

chan

ge.p

age2

.mu

ltit

ext1

0A

/N10

23

SUB

CLA

SS_D

AT

E01

-05

chan

ge.p

age3

.dat

eXX

D*

SUB

CL

ASS

_TE

XT

01-2

5ch

ange

.pag

e3.t

extX

XA

/N

SUB

CLA

SS_L

IST

01-2

5ch

ange

.pag

e3.li

stX

XL

Mu

st e

qual

an

exi

stin

g L

ist

valu

e fo

r th

e sp

ecif

ied

subc

lass

as

defi

ned

in t

he L

ist

for

Lis

tXX

at

trib

ute

.

SUB

CLA

SS_

MU

LT

ILIS

T01

-03

msa

tt.v

alu

eL

Mu

ltip

le v

alu

es c

an b

e lo

aded

in

this

fiel

d an

d se

para

ted

by a

co

mm

a (,

). T

he v

alu

es fo

r th

is

fiel

d ar

e st

ored

in t

he

MSA

TT

ta

ble.

Mu

st e

qual

an

exi

stin

g M

ult

ilist

val

ue

for

the

spec

ifie

d su

bcla

ss a

s de

fin

ed in

the

List

for

Mu

ltili

stX

X a

ttri

bute

.

Tabl

e A-

2:

SOUR

CE_C

hang

e (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-12 User Guide


SUB

CLA

SS_

MU

LTIT

EX

T10

chan

ge.p

age3

.mu

ltit

ext1

0A

/N25

6

SUB

CLA

SS_

MU

LTIT

EX

T20

chan

ge.p

age3

.mu

ltit

ext1

0A

/N51

2

SUB

CLA

SS_

MU

LTIT

EX

T30

- 3

5

chan

ge.p

age3

.mu

ltit

ext1

0A

/N10

23

SUB

CLA

SS_

CU

RR

EN

CY

1-5

Cha

nge

.pag

e3.c

urr

ency

XX

Not Visible - Set by Agile DataLoad

FLA

GS

chan

ge.f

lags

A/N

32Se

t to

zer

o by

Agi

le D

ataL

oad.

V

alu

e se

t vi

a <

db v

endo

r>_

setc

ount

.sql

aft

er c

ompl

ete

data

set

load

ed in

to A

gile

tab

les.

OB

JVE

RSI

ON

chan

ge.o

bjve

rsio

nN

Set

to z

ero

by A

gile

Dat

aLoa

d.

DE

LE

TE

_FL

AG

chan

ge.d

elet

e_fl

agN

Set

to z

ero

by A

gile

Dat

aLoa

d.

* D

ate

fiel

ds c

an in

clu

de t

ime

in M

S A

cces

s da

te/t

ime

form

at, s

uch

as

4/4/

99 0

5:32

:13

PM

.

Tabl

e A-

2:

SOUR

CE_C

hang

e (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-13

Agile DataLoad 2006

SOUR

CE_R

ev T

able

Tabl

e A-

3:

SOUR

CE_R

ev (R

evis

ion

Obje

ct F

ield

s)

Ch

ang

e O

rder

sC

han

ge

Req

ues

tsD

evia

tio

ns

Sto

p S

hip

sM

anu

fact

ure

r O

rder

sN

ote

s

ITE

M_N

UM

BE

RR

RR

RR

CH

AN

GE

_N

UM

BE

RR

RR

RR

RE

V_N

UM

BE

RR

OO

OO

OB

SOL

ET

E_

DA

TE

ON

/AN

/AN

/AN

/A*

EFF

EC

TIV

E_

DA

TE

RR

RR

R*

FUN

CT

ION

OO

OO

O

INC

OR

P_D

AT

EO

OO

OO

Val

idat

ion

will

giv

e a

war

nin

g if

this

fi

eld

is n

ot p

opu

late

d. F

ileL

oad

will

n

ow p

opu

late

th

is v

alu

e w

hen

lo

adin

g fi

les.

*

RE

LEA

SE_T

YP

ER

N/A

N/A

N/A

O

LO

C01

-10

OO

OO

O

DA

TE

01-2

0O

OO

OO

*

TE

XT

01-1

5O

OO

OO

LIS

T01

-25

OO

OO

O

RE

LEA

SED

NV

NV

NV

NV

NV

Bin

ary

fiel

d se

t by

Agi

le D

ataL

oad

to

ind

icat

e w

heth

er t

he r

evis

ion

is

rele

ased

or

not

.

A-14 User Guide


INC

OR

PO

RA

TE

DN

VN

VN

VN

VN

VN

ot se

t by

Agi

le D

ataL

oad.

Indi

cate

s w

het

her

th

e fi

les

for

the

revi

sion

h

ave

been

inco

rpor

ated

. Set

du

rin

g th

e Fi

leL

oad

proc

ess.

LAT

EST

_FLA

GN

VN

VN

VN

VN

VB

inar

y fi

eld

set b

y A

gile

Dat

aLoa

d to

in

dica

te w

heth

er t

he

revi

sion

is t

he

late

st fo

r th

e it

em.

KE

Y:

R=

Req

uir

ed fi

eld

O=

Opt

ion

al fi

eld

N/A

=n

ot a

pplic

able

to t

hat

cla

ss N

V=

not

vis

ible

* D

ate

fiel

ds c

an in

clu

de t

ime

in M

S A

cces

s da

te/t

ime

form

at, s

uch

as

4/4/

99 0

5:32

:13

PM

.

Tabl

e A-

3:

SOUR

CE_R

ev (R

evis

ion

Obje

ct F

ield

s) (

cont

inue

d)

Ch

ang

e O

rder

sC

han

ge

Req

ues

tsD

evia

tio

ns

Sto

p S

hip

sM

anu

fact

ure

r O

rder

sN

ote

s

A-15

Agile DataLoad 2006

SOUR

CE_B

OM T

able

Tabl

e A-

4:

SOU

RCE_

BOM

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

Required

PA

RE

NT

_N

UM

BE

Rbo

m.it

em=

sele

ct

item

.item

_nu

mbe

r fr

om

item

,bom

whe

re

item

.id=

bom

.item

A/N

Mu

st e

qual

an

exi

stin

g it

em n

um

ber.

ITE

M_N

UM

BE

Rbo

m.it

em_n

um

ber

A/N

30M

ust

equ

al a

n e

xist

ing

item

nu

mbe

r.

FIN

D_N

UM

BE

Rbo

m.f

ind_

nu

mbe

rN

5m

ax. 3

2767

If b

lan

k, A

gile

Dat

aLoa

d de

fau

lts

to”0

”.

Optional

QU

AN

TIT

Ybo

m.q

uan

tity

A/N

20If

bla

nk,

def

ault

s to

th

e va

lue

set

in

Agi

le A

dm

inis

trat

or.

DE

SCR

IPT

ION

bom

.des

crip

tion

A/N

255

NO

TE

Sbo

m.r

ef_n

otes

A/N

512

DA

TE

01–0

5bo

m.d

ateX

XD

TE

XT

01–0

5bo

m.t

extX

XA

/N50

LIS

T01

–05

bom

.list

XX

LM

ust

equ

al a

n e

xist

ing

Lis

t va

lue

for

the

spec

ifie

d cl

ass

as d

efin

ed in

th

e Li

st fo

r Li

stX

X a

ttri

bute

.

MU

LTIT

EX

T30

-

31bo

m.p

age2

.mu

ltit

ext3

XA

/N10

23

A-16 User Guide

Not Vis.
HIS

T_C

HA

NG

E_I

Nbo

m.c

han

ge_i

nA

/NSe

t by

Agi

le D

ataL

oad.

Mu

st e

qual

an

ex

isti

ng

Ch

ange

Nu

mbe

r.

HIS

T_C

HA

NG

E_O

UT

bom

.ch

ange

_ou

tA

/NSe

t by

Agi

le D

ataL

oad.

Mu

st e

qual

an

ex

isti

ng

Ch

ange

Nu

mbe

r. R

edlin

e de

lete

row

sho

uld

be

crea

ted

for

BO

M r

ows

wit

h ch

ange

_ou

t va

lue

set.

PR

IOR

_RO

Wbo

m.p

rior

_row

NSe

t to

zero

by

Agi

le D

ataL

oad.

OB

SOL

ET

E_

DA

TE

bom

.eff

ecti

ve_d

ate

DSe

t by

Agi

le D

ataL

oad

to a

ssem

bly’

s re

visi

on o

bsol

ete

date

for

spec

ific

B

OM

row

bas

ed o

n c

han

ge_o

ut

valu

e.

Tabl

e A-

4:

SOU

RCE_

BOM

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-17

Agile DataLoad 2006

SOUR

CE_M

anuf

actu

rer T

able

Tabl

e A-

5:

SOUR

CE_M

anuf

actu

rer

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

Required

NA

ME

man

ufa

ctu

rer.

nam

eA

/N30

No

dupl

icat

es a

llow

ed.

CLA

SSm

anu

fact

ure

r.cl

ass

LM

anu

fact

ure

rs c

lass

Agi

le d

efin

ed c

lass

.

SUB

CLA

SSm

anu

fact

ure

r.su

bcla

ssL

30E

xam

ple:

Man

ufa

ctu

rer

Mu

st e

qual

an

exi

stin

g u

ser

defi

ned

su

bcla

ss fo

r th

e sp

ecifi

ed c

lass

.

A-18 User Guide

Optional
STA

TU

Sm

anu

fact

ure

r.st

atu

sL

Exa

mpl

es: A

ppro

ved,

D

isqu

alif

ied,

Obs

olet

eM

ust

equ

al v

alid

Sta

tus

for

spec

ifie

d cl

ass.

AD

DR

ESS

man

ufa

ctu

rer.

addr

ess

A/N

100

CIT

Ym

anu

fact

ure

r.ci

tyA

/N50

STA

TE

man

ufa

ctu

rer.

stat

eA

/N50

CO

UN

TR

Ym

anu

fact

ure

r.co

un

try

A/N

50

PO

STA

L_C

OD

Em

anu

fact

ure

r.po

stal

_cod

eA

/N50

CO

NT

AC

Tm

anu

fact

ure

r.co

nta

ctA

/N50

EM

AIL

man

ufa

ctu

rer.

emai

lA

/N10

0

PH

ON

Em

anu

fact

ure

r.ph

one

A/N

25

FAX

man

ufa

ctu

rer.

fax

A/N

25

UR

Lm

anu

fact

ure

r.u

rlA

/N25

6

CL

ASS

_C

RE

AT

EU

SER

Man

ufa

ctu

re.h

isto

ry.u

ser?

CL

ASS

_C

UR

RE

NC

Y1-

5M

anu

fact

ure

.pag

e2.c

urr

ency

XX

CLA

SS_N

OT

ES

Man

ufa

ctu

re.p

age2

.not

es

Tabl

e A-

5:

SOUR

CE_M

anuf

actu

rer (

cont

inue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-19

Agile DataLoad 2006
Optional
CLA

SS_D

AT

E01

–05

man

ufa

ctu

rer.

page

2.da

teX

XD

CL

ASS

_TE

XT

01–2

5m

anu

fact

ure

r.pa

ge2.

text

XX

A/N

50

CL

ASS

_LIS

T01

–25

man

ufa

ctu

rer.

page

2.lis

tXX

LM

ust

equ

al a

n e

xist

ing

List

va

lue

for

the

spec

ified

cla

ss

as d

efin

ed in

the

List

for

Lis

tXX

att

ribu

te.

CL

ASS

_M

UL

TIL

IST

01 –

03

msa

tt.v

alu

eL

100

Mu

ltip

le v

alu

es c

an b

e lo

aded

in t

his

fiel

d an

d se

para

ted

by a

com

ma

(,).

T

he v

alu

es fo

r th

is fi

eld

are

stor

ed in

the

MSA

TT

tabl

e.

Mu

st e

qual

an

exi

stin

g M

ult

ilist

val

ue

for

the

spec

ified

subc

lass

as d

efin

ed

in t

he L

ist f

or M

ult

ilist

XX

at

trib

ute

.

CL

ASS

_M

ULT

ITE

XT

10m

anu

fact

ure

r.pa

ge2.

mu

ltit

ext

10A

/N25

6

CL

ASS

_M

ULT

ITE

XT

20m

anu

fact

ure

r.pa

ge2.

mu

ltit

ext

20A

/N51

2

CL

ASS

_M

ULT

ITE

XT

30 -

35

man

ufa

ctu

rer.

page

2.m

ult

ite

xt3X

A/N

1023

Tabl

e A-

5:

SOUR

CE_M

anuf

actu

rer (

cont

inue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-20 User Guide

Optional
SUB

CLA

SS_

DA

TE

01-0

5m

anu

fact

ure

r.pa

ge3.

date

XX

D

SUB

CLA

SS_

TE

XT

01-2

5m

anu

fact

ure

r.pa

ge3.

text

XX

A/N

SUB

CLA

SS_L

IST

01-2

5m

anu

fact

ure

r.pa

ge3.

listX

XL

Mu

st e

qual

an

exi

stin

g Li

st

valu

e fo

r th

e sp

ecifi

ed

subc

lass

as

defi

ned

in t

he

Lis

t for

Lis

tXX

att

ribu

te.

SUB

CLA

SS_

MU

LT

ILIS

T01

-03

msa

tt.v

alu

eL

Mu

ltip

le v

alu

es c

an b

e lo

aded

in t

his

fiel

d an

d se

para

ted

by a

com

ma

(,).

T

he v

alu

es fo

r th

is fi

eld

are

stor

ed in

the

MSA

TT

tabl

e.

Mu

st e

qual

an

exi

stin

g M

ult

ilist

val

ue

for

the

spec

ified

subc

lass

as d

efin

ed

in t

he L

ist f

or M

ult

ilist

XX

at

trib

ute

.

SUB

CLA

SS_

MU

LTIT

EX

T10

man

ufa

ctu

rer.

page

3.m

ult

ite

xt10

A/N

256

SUB

CLA

SS_

MU

LTIT

EX

T20

man

ufa

ctu

rer.

page

3.m

ult

ite

xt20

A/N

512

Tabl

e A-

5:

SOUR

CE_M

anuf

actu

rer (

cont

inue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-21

Agile DataLoad 2006

SUB

CLA

SS_

MU

LTIT

EX

T30

- 35

man

ufa

ctu

rer.

page

3.m

ult

ite

xt3X

A/N

1023

SUB

CLA

SS_

CU

RR

EN

CY

1-5

Man

ufa

ctu

re.p

age3

.cu

rren

cyX

X

Not Vis. - Set by Agile DataLoad

FLA

GS

man

ufa

ctu

rer.

flag

sA

/N32

Set

to z

ero

by A

gile

D

ataL

oad.

Val

ue

set

via

<db

ven

dor>

_set

cou

nt.

sql

afte

r co

mpl

ete

dat

a se

t lo

aded

into

Agi

le t

able

s.

OB

JVE

RSI

ON

man

ufa

ctu

rer.

objv

ersi

onN

Set

to z

ero

by A

gile

D

ataL

oad.

DE

LET

E_F

LAG

man

ufa

ctu

rer.

dele

te_f

lag

NSe

t to

zer

o by

Agi

le

Dat

aLoa

d.

Tabl

e A-

5:

SOUR

CE_M

anuf

actu

rer (

cont

inue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-22 User Guide


SOUR

CE_M

fr_P

art T

able

Tabl

e A-

6:

SOUR

CE_M

fr_Pa

rt

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

Required

PA

RT

_N

UM

BE

Rm

fr_p

art.

part

_num

ber

A/N

30N

o du

plic

ates

allo

wed

.

CLA

SSm

fr_p

art.

clas

sL

Man

ufa

ctu

rer

Par

ts

clas

sA

gile

def

ined

cla

ss.

SUB

CLA

SSm

fr_p

art.

subc

lass

L30

Exa

mpl

e:

Man

ufa

ctu

rer

Par

t

Mus

t eq

ual

an

exi

stin

g u

ser

defi

ned

su

bcla

ss fo

r th

e sp

ecif

ied

clas

s.

MA

NU

FAC

TU

RE

Rm

fr_p

art.

man

u_i

dA

/NM

ust

equ

al a

n e

xist

ing

Man

ufa

ctu

rer

Nam

e fr

om

Man

ufa

ctu

rer

obje

ct.

Optional

STA

TU

Sm

fr_p

art.

stat

us

LE

xam

ples

: Act

ive,

O

bsol

ete

Mus

t eq

ual

val

id S

tatu

s fo

r sp

ecif

ied

cla

ss.

CL

ASS

_DA

TE

01–0

5m

fr_p

art.

page

2.da

teX

XD

CL

ASS

_TE

XT

01–2

5m

fr_p

art.

page

2.te

xtX

XA

/N50

CL

ASS

_LIS

T01

–25

mfr

_par

t.pa

ge2.

listX

XL

Mus

t eq

ual

an

exi

stin

g L

ist

valu

e fo

r th

e sp

ecif

ied

clas

s as

de

fin

ed in

th

e L

ist

for

Lis

tXX

at

trib

ute

.

DE

SCR

IPT

ION

mfr

_par

t.de

scri

ptio

nA

/N10

0

A-23

Agile DataLoad 2006

CLA

SS_

CR

EA

TE

USE

RM

frpa

rt.h

isto

ry.u

ser

CLA

SS_

CU

RR

EN

CY

1-5

Mfr

part

.pag

e2.c

urr

ency

XX

CLA

SS_N

OT

ES

Mfr

part

.des

crip

tion

Tabl

e A-

6:

SOUR

CE_M

fr_Pa

rt (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-24 User Guide


Lis

tXX

att

ribu

te.

Optional

CL

ASS

_M

UL

TIL

IST

01 –

03

msa

tt.v

alu

eL

100

Mul

tipl

e va

lues

can

be

load

ed

in th

is fi

eld

and

sepa

rate

d by

a

com

ma

(,).

The

val

ues

for t

his

fiel

d ar

e st

ored

in th

e M

SAT

T

tabl

e, a

nd

mu

st e

qual

an

ex

isti

ng

Mu

ltili

st v

alu

e fo

r the

sp

ecif

ied

subc

lass

as d

efin

ed in

th

e L

ist

for

Mu

ltili

stX

X

attr

ibu

te.

CL

ASS

_M

ULT

ITE

XT

10

mfr

_par

t.pa

ge2.

m

ult

itex

t10

A/N

256

CL

ASS

_M

ULT

ITE

XT

20

mfr

_par

t.pa

ge2.

m

ult

itex

t20

A/N

512

CL

ASS

_M

ULT

ITE

XT

30 -

35

mfr

_par

t.pa

ge2.

m

ult

itex

t3X

A/N

1023

SUB

CLA

SS_

DA

TE

01-0

5m

fr_p

art.

page

3.da

teX

XD

SUB

CLA

SS_

TE

XT

01-2

5m

fr_p

art.

page

3.te

xtX

XA

/N50

SUB

CLA

SS_

LIS

T01

-25

mfr

_par

t.pa

ge3.

listX

XL

Mus

t eq

ual

an

exi

stin

g L

ist

valu

e fo

r th

e sp

ecif

ied

subc

lass

as

def

ined

in t

he

Lis

t fo

r

Tabl

e A-

6:

SOUR

CE_M

fr_Pa

rt (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-25

Agile DataLoad 2006
Optional
SUB

CLA

SS_

MU

LT

ILIS

T01

-03

msa

tt.v

alu

eL

Mul

tipl

e va

lues

can

be

load

ed

in th

is fi

eld

and

sepa

rate

d by

a

com

ma

(,).

The

val

ues

for t

his

fiel

d ar

e st

ored

in th

e M

SAT

T

tabl

e. M

ust

equ

al a

n e

xist

ing

Mul

tilis

t va

lue

for

the

spec

ifie

d su

bcla

ss a

s def

ined

in

the

Lis

t fo

r M

ult

ilist

XX

at

trib

ute

.

SUB

CLA

SS_

MU

LTIT

EX

T10

mfr

_par

t.pa

ge3.

m

ult

itex

t10

A/N

256

SUB

CLA

SS_

MU

LTIT

EX

T20

mfr

_par

t.pa

ge3.

m

ult

itex

t20

A/N

512

SUB

CLA

SS_

MU

LTIT

EX

T30

- 3

5

mfr

_par

t.pa

ge3.

m

ult

itex

t3X

A/N

1023

SUB

CLA

SS_

CU

RR

EN

CY

1-5

Mfr

part

.pag

e2.c

urr

ency

XX

TA

RG

ET

CO

STM

frpa

rt.t

arge

tcos

t

Tabl

e A-

6:

SOUR

CE_M

fr_Pa

rt (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-26 User Guide

Not Vis.
FLA

GS

mfr

_par

t.fl

ags

A/N

32Se

t to

zero

by

Agi

le D

ataL

oad.

V

alu

e se

t vi

a <

db v

endo

r>_

setc

oun

t.sq

l aft

er c

ompl

ete

data

set

load

ed in

to A

gile

ta

bles

.

OB

JVE

RSI

ON

mfr

_par

t.ob

jver

sion

NSe

t to

zero

by

Agi

le D

ataL

oad.

DE

LET

E_

FLA

Gm

fr_p

art.

dele

te_f

lag

NSe

t to

zero

by

Agi

le D

ataL

oad.

Tabl

e A-

6:

SOUR

CE_M

fr_Pa

rt (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-27

Agile DataLoad 2006

SOUR

CE_A

ppro

ved_

Mfr

Tab

le

Tabl

e A-

7:

SOU

RCE_

Appr

oved

_Mfr

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

Required

ITE

M_N

UM

BE

Rm

anu

_by.

agile

_par

tA

/NM

ust

equ

al a

n e

xist

ing

item

n

um

ber.

MFR

_PA

RT

man

u_b

y.m

anu

_par

tM

ust

equ

al a

n e

xist

ing

man

ufa

ctu

rer

part

nu

mbe

r ba

sed

on t

he

man

ufa

ctu

rer

nam

e.

MA

NU

FAC

TU

RE

RN

/AA

/NM

ust

equ

al a

n e

xist

ing

man

ufa

ctu

rer

nam

e. T

he

com

bin

atio

n o

f mfr

_par

t an

d m

anu

fact

ure

r n

ame

mu

st b

e va

lid.

PR

EFE

R_S

TA

TU

Sm

anu

_by.

pref

er_s

tatu

sL

Exa

mpl

es:

Pre

ferr

ed,

Alt

ern

ate

Mu

st e

qual

val

id S

tatu

s.

Optional

RE

F_N

OT

ES

man

u_b

y.re

f_n

otes

A/N

2000

DA

TE

01–0

5m

anu

_by.

dat

eXX

D

TE

XT

01–0

5m

anu

_by.

text

XX

A/N

50

LIS

T01

–05

man

u_b

y.lis

tXX

LM

ust

equ

al a

n e

xist

ing

Lis

t va

lue

for

the

spec

ifie

d cl

ass

as d

efin

ed in

th

e L

ist

for

Lis

tXX

att

ribu

te.

MU

LT

ITE

XT

30 -

31

man

u_b

y.m

ult

itex

t3X

A/N

2000

A-28 User Guide

Not Vis. - Set by Agile DataLoad
CH

AN

GE

_IN

man

u_b

y.ch

ange

_in

A/N

Set

to z

ero

by A

gile

Dat

aLoa

d. N

o A

ML

his

tory

is s

up

por

ted

in t

his

rele

ase.

CH

AN

GE

_OU

Tm

anu

_by.

chan

ge_o

ut

A/N

Set

to z

ero

by A

gile

Dat

aLoa

d. N

o A

ML

his

tory

is s

up

por

ted

in t

his

rele

ase.

PR

IOR

_RO

Wm

anu

_by.

pri

or_r

owN

Set

to z

ero

by A

gile

Dat

aLoa

d. N

o A

ML

his

tory

is s

up

por

ted

in t

his

rele

ase.

Tabl

e A-

7:

SOU

RCE_

Appr

oved

_Mfr

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-29

Agile DataLoad 2006

SOUR

CE_U

ser T

able

Tabl

e A-

8:

SOU

RCE_

User

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

Required

USE

RN

AM

EA

/NN

o D

up

licat

es.

FUL

LN

AM

EA

/N29

Optional

EM

AIL

_EN

CO

DE

_T

YP

EL

MIM

E,

UU

EN

CO

DE

Def

ault

MIM

E.

NO

TIF

ICA

TIO

NL

Yes

, No

CH

AN

GE

CA

STL

Yes

, No

AN

AL

YST

_SE

AR

CH

ES

LY

es, N

o

AN

AL

YST

_LIS

TL

Yes

, No

CO

MP

_EN

GR

_SE

AR

CH

ES

LY

es, N

o

CO

MP

_EN

GR

_IN

BO

XL

Yes

, No

EM

AIL

EM

AIL

_AT

TA

CH

_T

YP

EL

Agi

le, w

CM

Mu

ltip

le v

alu

es c

an b

e lo

aded

in t

his

fi

eld

and

sepa

rate

d by

a c

omm

a (,

).

CO

MM

EN

T

ESC

DE

S_A

PP

RO

VA

L

A-30 User Guide

Optional
FAX

A/N

Allo

ws

peri

ods,

das

hes

, com

mas

.

PH

ON

EA

/NA

llow

s pe

riod

s, d

ash

es, c

omm

as.

PA

GE

RA

/NA

llow

s pe

riod

s, d

ash

es, c

omm

as.

STA

RT

UP

_UR

LA

/N

RO

LE

Le.

g. R

eadO

nly

, C

reat

or,

Inco

rpor

ator

, etc

.

Mu

ltip

le v

alu

es c

an b

e lo

aded

in t

his

fi

eld

and

sepa

rate

d by

a c

omm

a (,

).

Mu

st e

qual

an

exi

stin

g R

ole

valu

e.

LO

GIN

_PA

SSW

OR

DA

/NR

equ

ired

if P

refe

ren

ces h

ave

been

set i

n

Ad

min

istr

ator

to

dis

allo

w a

bla

nk

pas

swor

d.

AP

PR

OV

AL_

PA

SSW

OR

DA

/N

DE

PA

RT

ME

NT

LM

ult

iple

val

ues

can

be

load

ed in

th

is

fiel

d an

d se

para

ted

by a

com

ma

(,).

M

ust

equ

al a

n e

xist

ing

Dep

artm

ent

valu

e.

Not

e: T

he c

urr

ent

vers

ion

of A

gile

Dat

aLoa

d do

es n

ot s

upp

ort

load

ing

Pro

gram

Man

ager

an

d P

artn

er in

form

atio

n fo

r u

ser

acco

un

ts.

Not

e: A

ll u

sers

load

ed t

hro

ugh

Agi

le D

ataL

oad

will

be

assi

gned

a fu

ll u

ser

licen

se.

Tabl

e A-

8:

SOU

RCE_

User

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

A-31

Agile DataLoad 2006

SOUR

CE_R

efDe

sig

and

SOUR

CE_R

efDe

sig_

2 Ta

bles

Th

e SO

UR

CE

_Ref

Des

ig ta

ble

is c

reat

ed w

hen

you

cre

ate

a n

ew A

cces

s da

taba

se u

sin

g D

ataL

oad.

The

tabl

e is

load

ed

duri

ng

the

Loa

d op

erat

ion

.

Th

e SO

UR

CE

_Ref

Des

ig_2

tabl

e is

als

o cr

eate

d w

hen

you

cre

ate

a n

ew A

cces

s da

taba

se u

sin

g D

ataL

oad

. Th

e ta

ble

is

load

ed d

uri

ng

the

Load

ope

rati

on. T

he

SOU

RC

E_R

efD

esig

_2 t

able

can

con

tain

row

s w

ith

the

sam

e ID

. For

a g

iven

B

OM

row

ID

, all

SOU

RC

E_R

efD

esig

_2 r

ows

wit

h t

he

sam

e ID

are

load

ed f

or t

hat

BO

M r

ow. T

her

e is

no

erro

r ch

ecki

ng

for

refe

ren

ce d

esig

nat

ors

in t

his

tab

le. R

ange

s ar

e n

ot e

xpan

ded

befo

re b

ein

g lo

aded

, so

the

ran

ges

are

han

dle

d a

ccor

din

g to

ser

ver

imp

lem

enta

tion

.

Tabl

e A-

9:

SOU

RCE_

RefD

esig

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

IDN

RE

FDE

SIG

A65

,535

Tabl

e A-

10:

SOU

RCE_

RefD

esig

_2

Att

rib

ute

Map

ped

to

List Field

Type

Size

Val

id V

alu

esN

ote

s

IDN

RE

FDE

SIG

A65

,535

A-32 User Guide


SOUR

CE_C

usto

mer

Tab

le

Tabl

e A-

11:

SOU

RCE_

Cust

omer

Att

rib

ute

Map

ped

to

List Field

Type

Size

No

tes

Required

CU

STO

ME

R_N

AM

Ecu

stom

er.c

ust

omer

_nam

eA

/N10

0

CL

ASS

cust

omer

.cla

ssL

Val

ide

valu

es: C

ust

omer

Cla

ss

Agi

le d

efin

ed c

lass

SUB

CL

ASS

cust

omer

.su

bcla

ssA

/N30

Val

ide

valu

es:

Exa

mpl

es:C

ust

omer

Mu

st e

qual

an

d ex

isti

ng

user

de

fin

ed s

ubc

lass

for

the

spec

ifie

d c

lass

CU

STO

ME

R_N

UM

BE

Rcu

stom

er.c

ust

omer

_nu

mbe

rA

/N70

No

dupl

icat

es a

llow

ed

SIT

E_I

Dcu

stom

er.s

ite_

idA

/N70

SIT

E_N

AM

Ecu

stom

er.s

ite_

nam

eA

/N70

Optional

CLA

SS_C

RE

AT

EU

SER

AD

DR

ESS

cust

omer

.ad

dre

ssA

/N10

23

CIT

Ycu

stom

er.c

ity

A/N

50

STA

TE

cust

omer

.sta

teL

CO

UN

TR

Ycu

stom

er.c

oun

try

L

A-33

Agile DataLoad 2006
Optional
PO

STA

L_C

OD

Ecu

stom

er.p

osta

l_co

de

A/N

128

PH

ON

Ecu

stom

er.p

hon

eA

/N12

8

UR

Lcu

stom

er.u

rlA

/N25

5

FAX

cust

omer

.fax

A/N

128

CO

NT

AC

Tcu

stom

er.c

onta

ctA

/N12

8

CO

NT

AC

T_E

MA

ILcu

stom

er.c

onta

ct_e

mai

lA

/N12

8

CO

NT

AC

T_P

HO

NE

cust

omer

.con

tact

_pho

ne

A/N

128

CL

ASS

_CU

RR

EN

CY

1-5

Cu

stom

er.p

age2

.cu

rren

cyX

X

CL

ASS

_DA

TE

01-0

5cu

stom

er.p

age2

.dat

eXX

D

CLA

SS_L

IST

01-2

5cu

stom

er.p

age2

.list

XX

L

CL

ASS

_MU

LT

ILIS

T01

-03

L

CL

ASS

_MU

LT

ITE

XT

10-3

5cu

stom

er.p

age2

.mu

ltit

extX

XA

/N10

23

CL

ASS

_NO

TE

Scu

stom

er.p

age2

.not

esA

/N10

23

CL

ASS

_TE

XT

01-2

5cu

stom

er.p

age2

.tex

tXX

A/N

50

SUB

CL

ASS

_DA

TE

01-0

5cu

stom

er.p

age3

.dat

eXX

D

SUB

CL

ASS

_LIS

T01

-25

cust

omer

.pag

e3.li

stX

XL

SUB

CL

ASS

_MU

LT

ILIS

T01

-03

cust

omer

.pag

e3.m

ult

ilist

XX

L

SUB

CL

ASS

_MU

LT

ITE

XT

10cu

stom

er.p

age3

.mu

ltit

ext1

0A

/N25

6

SUB

CL

ASS

_MU

LT

ITE

XT

20cu

stom

er.p

age3

.mu

ltit

ext2

0A

/N51

2

Tabl

e A-

11:

SOU

RCE_

Cust

omer

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

No

tes

A-34 User Guide


SOUR

CE_P

robl

emRe

port

Tab

le

SUB

CL

ASS

_MU

LT

ITE

XT

30-3

5cu

stom

er.p

age3

.mu

ltit

ext3

0XX

A/N

1023

SUB

CL

ASS

_TE

XT

01-2

5cu

stom

er.p

age3

.tex

tXX

A/N

50

SUB

CL

ASS

_CU

RR

EN

CY

1-5

Cu

stom

er.p

age3

.cu

rren

cyX

X

Tabl

e A-

12:

SOU

RCE_

Prob

lem

Repo

rt

Att

rib

ute

Map

ped

to

List Field

Type

Size

No

tes

NU

MB

ER

prob

lem

_rep

ort.

nu

mbe

rA

/N70

No

dupl

icat

es a

llow

ed

Required

CL

ASS

prob

lem

_rep

ort.

clas

sL

Agi

le d

efin

ed c

lass

SUB

CL

ASS

prob

lem

_rep

ort.

subc

lass

A/N

30M

ust

equ

al a

nd

exis

tin

g u

ser

def

ined

su

bcla

ss fo

r th

e sp

ecif

ied

clas

s

CU

STO

ME

R_N

AM

Ep

robl

em_r

epor

t.cu

stom

er_n

ame

A/N

100

SIT

E_N

AM

Epr

oble

m_r

epor

t.si

te_n

ame

A/N

100

ITE

M_N

UM

BE

Rpr

oble

m_r

epor

t.it

em_n

um

ber

A/N

50

CA

TE

GO

RY

prob

lem

_rep

ort.

cate

gory

L

Tabl

e A-

11:

SOU

RCE_

Cust

omer

(con

tinue

d)

Att

rib

ute

Map

ped

to

List Field

Type

Size

No

tes

A-35

Agile DataLoad 2006
Optional
ASS

IGN

_TO

prob

lem

_rep

ort.

assi

gn_t

oL

ASS

IGN

_DA

TE

prob

lem

_rep

ort.

assi

gn_d

ate

D

OR

IGIN

AT

OR

prob

lem

_rep

ort.

orig

inat

orL

DA

TE

_OR

IGIN

AT

ED

prob

lem

_rep

ort.

dat

e_or

igin

ated

D

FIN

AL_

CO

MP

LE

TE

_DA

TE

prob

lem

_rep

ort.

fin

al_c

ompl

ete_

date

D

PR

OD

UC

T_L

INE

Spr

oble

m_r

epor

t.p

rod

uct

_lin

esL

DE

SCR

IPT

ION

prob

lem

_rep

ort.

desc

ript

ion

A/N

1023

RE

SOLU

TIO

N_C

OD

Epr

oble

m_r

epor

t.re

solu

tion

_cod

eL

CLA

SS_C

RE

AT

EU

SER

CL

ASS

_CU

RR

EN

CY

1-5

Pro

blem

Rep

ort.

pag

e2.c

urr

ency

STA

TU

SP

robl

emR

epor

t.st

atu

s

RE

V_F

OU

ND

prob

lem

_rep

ort.

rev_

fou

nd

A/N

20

RE

V_F

IXE

Dpr

oble

m_r

epor

t.re

v_fi

xed

A/N

20

FAIL

UR

E_M

OD

Epr

oble

m_r

epor

t.fa

ilure

_cod

eL

Tabl

e A-

12:

SOU

RCE_

Prob

lem

Repo

rt (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

No

tes

A-36 User Guide

Optional
CL

ASS

_DA

TE

01-0

5pr

oble

m_r

epor

t.pa

ge2.

date

XX

D

CL

ASS

_LIS

T01

-25

prob

lem

_rep

ort.

page

2.lis

tXX

L

CL

ASS

_MU

LT

ILIS

T01

-03

L

CL

ASS

_MU

LT

ITE

XT

10pr

oble

m_r

epor

t.pa

ge2.

mul

tite

xtX

XA

/N25

6

CL

ASS

_MU

LT

ITE

XT

20pr

oble

m_r

epor

t.pa

ge2.

mul

tite

xtX

XA

/N51

2

CL

ASS

_MU

LT

ITE

XT

30-3

5pr

oble

m_r

epor

t.pa

ge2.

mul

tite

xtX

XA

/N10

23

CL

ASS

_NO

TE

Spr

oble

m_r

epor

t.pa

ge2.

not

esA

/N10

23

CL

ASS

_TE

XT

01-2

5pr

oble

m_r

epor

t.pa

ge2.

text

XX

A/N

50

SUB

CL

ASS

_DA

TE

01-0

5p

robl

em_r

epor

t.p

age3

.dat

eXX

D

SUB

CL

ASS

_LIS

T01

-25

prob

lem

_rep

ort.

page

3.lis

tXX

L

SUB

CL

ASS

_MU

LT

ILIS

T01

-03

L

SUB

CL

ASS

_MU

LT

ITE

XT

10pr

oble

m_r

epor

t.p

age3

.mul

tite

xtX

XA

/N

SUB

CL

ASS

_MU

LT

ITE

XT

20pr

oble

m_r

epor

t.p

age3

.mul

tite

xtX

X

SUB

CL

ASS

_MU

LT

ITE

XT

30-3

5p

robl

em_r

epor

t.p

age3

.mul

tite

xtX

X

SUB

CL

ASS

_TE

XT

01-2

5pr

oble

m_r

epor

t.pa

ge3.

text

XX

A/N

50

SUB

CL

ASS

_CU

RR

EN

CY

1-5

Pro

blem

Rep

ort.

pag

e3.c

urr

ency

WO

RK

FLO

W_I

DP

robl

emR

epor

t.w

orkf

low

Tabl

e A-

12:

SOU

RCE_

Prob

lem

Repo

rt (c

ontin

ued)

Att

rib

ute

Map

ped

to

List Field

Type

Size

No

tes

A-37

Agile DataLoad 2006

A-38 User Guide

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: Leading zeroes in the number section of a RefDesig are dropped. For example:

A01-A03 is expanded to A1, A2, A3. It does not become A01, A02, A03.

❑ Rule 8 — 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 9 — 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 10 — If neither of the RefDesigs contains a prefix, then the range is valid. For example:

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

B-10 User Guide


❑ Rule 11 — 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.

• 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.

B-11

Agile DataLoad 2006

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

❑ 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.

B-12 User Guide


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-13

Agile DataLoad 2006

B-14 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