Agile Advantage - Oracle Help Center

Agile Advantage
™
ChangeCAST User Guide
v2006 SP4
Part No. E12872-01
August 2008
Agile Advantage 2006
Copyright © 1995, 2008, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement
containing restrictions on use and disclosure and are protected by intellectual
property laws. Except as expressly permitted in your license agreement or allowed
by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish or display any part, in any form, or
by any means. Reverse engineering, disassembly, or decompilation of this software,
unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not
warranted to be error-free. If you find any errors, please report them to us in
writing.
If this software or related documentation is delivered to the U.S. Government or
anyone licensing it on behalf of the U.S. Government, the following notice is
applicable:
U.S. GOVERNMENT RIGHTS
Programs, software, databases, and related documentation and technical data
delivered to U.S. Government customers are "commercial computer software" or
"commercial technical data" pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such, the use,
duplication, disclosure, modification, and adaptation shall be subject to the
restrictions and license terms set forth in the applicable Government contract, and,
to the extent applicable by the terms of the Government contract, the additional
rights set forth in FAR 52.227-19, Commercial Computer Software License
(December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA
94065.
This software is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous
applications, including applications which may create a risk of personal injury. If
you use this software in dangerous applications, then you shall be responsible to
take all appropriate fail-safe, backup, redundancy and other measures to ensure the
safe use of this software. Oracle Corporation and its affiliates disclaim any liability
for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other
names may be trademarks of their respective owners.
This software and documentation may provide access to or information on
content, products and services from third parties. Oracle Corporation and its
affiliates are not responsible for and expressly disclaim all warranties of any kind
with respect to third party content, products and services. Oracle Corporation and
its affiliates will not be responsible for any loss, costs, or damages incurred due to
your access to or use of third party content, products or services.
Agile Advantage 2006
C ONTENTS
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i
TTY Access to Oracle Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i
Readme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Agile Training Aids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii
Accessibility of Code Examples in Documentation . . . . . . . . . . . . . . . . . . . . . . . . . ii
Accessibility of Links to External Web Sites in Documentation . . . . . . . . . . . . . . . ii
Chapter 1
Introducing Agile ChangeCAST
Some Important Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
General Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Agile ChangeCAST Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
What’s New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Guidelines for Using Agile ChangeCAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Starting Agile ChangeCAST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Minimizing On Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Logging In As a Different User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
The Agile ChangeCAST Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Title Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Profile Library Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Profile Library Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Profile Library Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Transfer Log Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Transfer Log Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Transfer Control Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Agile ChangeCAST Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Where to Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Chapter 2
Working with Profiles
About Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
iii
Agile Advantage 2006
Adding and Importing Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a New Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Importing a Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auditing and Validating the Imported Profiles. . . . . . . . . . . . . . . . . . . . . . .
Copying Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Renaming Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Distributing Profile Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3
2-2
2-2
2-2
2-4
2-6
2-6
2-7
2-7
Defining Attributes and Field Mappings
Guidelines for Defining Attributes and Field Mappings. . . . . . . . . . . . . . . . . . . . . . . 3-1
Differentiating Documents from Parts and MCOs from ECOs . . . . . . . . . . . . . . . . . 3-2
Defining ERP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
The Attributes Table Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Attribute Text Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
The Attributes Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Attributes Table Dialog Box Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Adding Individual Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Modifying Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Removing Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Appending Attributes from a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Importing Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Exporting Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Verifying Attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Specifying and Verifying Agile-to-ERP Field Mappings . . . . . . . . . . . . . . . . . . . . . . . 3-7
Guidelines for Mapping Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Mapping Manufacturer or AML Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
A Note about BOM Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
The Field Mappings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Mapped Fields Table Columns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Field Mappings Dialog Box Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Creating Field Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Mapping to Null . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Mapping to System Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Specifying a Map Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Importing or Adding Field Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Exporting Field Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Managing Mapped Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Reordering Mapped Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Producing Agile ChangeCAST Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
iv
User Guide
Contents
Profile Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Producing an Agile Tables Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Printing Agile ChangeCAST Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Chapter 4
Formatting and Transferring Agile Data Files
About Agile ChangeCAST Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Formatting Agile ChangeCAST Transfer Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Reviewing and Modifying Transfer Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Reviewing and Editing Protocol Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Reviewing and Editing Notification Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Reviewing and Editing Schedule Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Connection Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Enabling and Disabling Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Starting and Stopping Agile ChangeCAST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Viewing and Printing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
The Transfer Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
The Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Retransferring Change Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Forcing Unscheduled Transfers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Backing Up Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Suggestions for Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Error Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Appendix A
Sample AGX File
Index
v
Agile Advantage 2006
vi
User Guide
Preface
The Agile Advantage documentation set includes Adobe® Acrobat™ PDF files. The
Oracle Technology Network (OTN) Web site (http://www.oracle.com/
technology/documentation/agile.html) contains the latest versions of the Agile
Advantage PDF files. You can view or download these manuals from the Web site,
or you can ask your Agile administrator if there is an Agile Advantage
Documentation folder available on your network from which you can access the
Agile Advantage documentation (PDF) files.
Note
To read the PDF files, you must use the free Adobe Acrobat Reader™
version 7.0 or later. This program can be downloaded from the Adobe
Web site (http://www.adobe.com).
If you need additional assistance or information, please contact Customer Support
(http://www.oracle.com/agile/support.html) for assistance.
Note
Before calling Agile Support about a problem with an Oracle|Agile
Advantage manual, please have the full part number, which is located on
the title page.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support
Services within the United States of America 24 hours a day, 7 days a week. For
TTY support, call 800.446.2398. Outside the United States, call +1.407.458.2479.
Readme
Any last-minute information about Agile Advantage can be found in the Readme
file on the Oracle Technology Network (OTN) Web site (http://www.oracle.com/
technology/documentation/agile.html).
i
Agile Advantage 2006
Agile Training Aids
Go to the Oracle University Web page (http://www.oracle.com/education/chooser/
selectcountry_new.html) for more information on Agile Training offerings.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document.
The conventions for writing code require that closing braces should appear on an
otherwise empty line; however, some screen readers may not always read a line of
text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or
organizations that Oracle does not own or control. Oracle neither evaluates nor
makes any representations regarding the accessibility of these Web sites.
ii
iii
Agile Advantage 2006
iv
v
Agile Advantage 2006
vi
C HAPTER 1
Introducing Agile
ChangeCAST
This chapter gives an overview of how Agile ChangeCAST transfers data from
Agile Advantage to target ERP (Enterprise Resource Planning) systems and
explains how to set up and start Agile ChangeCAST.
It includes these topics:
❑ Some Important Definitions
❑ Overview
❑ What’s New
❑ Guidelines for Using Agile ChangeCAST
❑ Starting Agile ChangeCAST
❑ The Agile ChangeCAST Window
❑ Where to Go From Here
❑ Where to Go From Here
Note: Installation instructions are included in the Agile Advantage Installation
and Maintenance Guide or the Agile Advantage Upgrade Guide.
Some Important Definitions
Understanding the following terms will help you understand and use Agile
ChangeCAST and related files:
1-1
Agile ChangeCAST 2006
General Terms
Table 1-1: General terms
Term
Definition
Profile
A collection of settings used by ChangeCAST to process
and deliver the transfer file to the ERP system. Profiles
define many aspects of data transfer from Agile to a single
target ERP system, including transfer file structure
definition, transfer settings, scheduling information, data
mapping, and directory/file locations.
Profile library
Up to 32 profiles together in a single file with extension
.agx (for ChangeCAST 8.1 and later) or .agc (for previous
releases).
Field
An individual piece of information; an attribute or column
of a table.
Row
A grouping of fields or a record in a table that represents a
data element.
Table
An organized collection of records.
Attributes
A list of ERP table-field elements that can be mapped;
every profile contains a set of attributes.
Mapping
The pairing of ERP attributes with Agile fields, system
nulls, system variables (also known as system flags), or the
result of a conditional expression.
ChangeCAST connect state
Whether ChangeCAST is automatically transferring
change orders for enabled profiles; the possible states are
Paused and Resumed, controlled by buttons in the main
ChangeCAST window.
Transfer flag
An internal setting that tells ChangeCAST whether a
change order has been successfully transferred.
Agile ChangeCAST Components
These components are required for Agile ChangeCAST:
Table 1-2: Components
Term
Definition
ChangeCAST Service
A service that launches the ChangeCAST application,
ChangeCAST.exe
1-2
User Guide
Chapter 1
Introducing Agile ChangeCAST
Table 1-2: Components
Term
Definition
ChangeCAST.exe
An application used to configure and transfer files of Agile
data to a host ERP (Enterprise Resource Planning) system
StartChangeCAST.exe
An application that starts the ChangeCAST Service
File Types
Table 1-3: Agile ChangeCAST files
Term
Definition
Mapping file (.map)
An ASCII (text) file containing the mappings of Agile fields
to ERP fields.
Exported ChangeCAST
attribute file (.aga)
An ASCII text file containing a list of ERP tables and fields
that are mappable for a single ChangeCAST profile.
Profile library (.agx or .agc) A file that contains all aspects of one or more profiles. AGX
files (for the current ChangeCAST) are text files. AGC files
(the format for pre-8.1 releases of ChangeCAST) are
binary files.
Backup (.bak)
Backup of the Profile library.
Transfer file (.agl, by
default)
A formatted ASCII file, output from ChangeCAST, which
is used to transfer change order information from Agile to
a host ERP system. There is at least one transfer file for
every change order processed by ChangeCAST. Transfer
files adhere to the settings defined in corresponding
profiles.
Temporary (.agl.tmp)
Temporary files created during processing.
Transfer log
(TransferLog.txt)
A log file that tracks the status of ChangeCAST’s connect
state and transfer attempts.
Error log (ErrorLog.txt)
A log file that tracks ChangeCAST mapping, condition
syntax, and other problems encountered during
validations and audits.
1-3
Agile ChangeCAST 2006
Overview
Agile ChangeCAST works with ERP-specific profiles to update your enterprise
resource planning (ERP) systems with the latest Item, Bill of Material (BOM), and
Manufacturer information from Agile. Figure 1-1 illustrates how Agile
ChangeCAST coordinates the flow of information from the Agile Advantage
database to the ERP system:
1
Profiles are created within Agile ChangeCAST. They control:
• The format of and naming convention for Agile ChangeCAST transfer files
• The destination of Agile ChangeCAST transfer files
• Whom to alert in case of errors (Notification)
• How often Agile ChangeCAST polls for change orders and transfers them
(Schedule)
2
Profile libraries (sets of profiles) can contain up to 32 profiles. The active profile
library is named ChangeCAST.agx, although it can be renamed for distribution.
Only one profile library can be active at a time.
3
Agile users create Items (such as Parts and Documents) and release them by
creating and releasing change orders.
4
Agile ChangeCAST looks for released or implemented change orders.
5
When Agile ChangeCAST locates a released or implemented change order, it
creates a transfer file for each enabled profile, according to the format settings
for those profiles, and sends them to the destinations stored in the profiles —
one file or a set of files per released or implemented change order.
6
When the application adapter at the host ERP site receives the transfer file, it
validates the data and sends the data to the host ERP’s database.
1-4
User Guide
Chapter 1
Introducing Agile ChangeCAST
Figure 1-1: The ChangeCAST cycle
1. Profile
Library
Agile Advantage
Agile Database
(Items, BOMs,
change orders)
2. Agile
ChangeCAST
Profiles
AGILE
SERVER
Agile
ChangeCAST
Application
4. Transfer
File
3. Released or
Implemented change
orders
HOST
ERP
SERVER
5. Application
Adapter
7. ERP Host
Database(s)
What’s New
Please note the following information about Agile ChangeCAST 2006:
❑
Agile ChangeCAST 2006 does not support transfer of the new Agile objects:
CARs (corrective action requests), Issues, Customers, Problem Reports.
❑
If an object supported by ChangeCAST has been related with any of the new
Agile objects, Agile ChangeCAST 2006 ignores those relationships, even if the
user has, for example, assigned the new Quality roles.
❑
Agile ChangeCAST 2006 connects only with an Agile Advantage 2006 eHub.
❑
Agile ChangeCAST 2006 supports the transferring of compliance data from the
Item Compliance and Manufacturer Parts Compliance tabs.
The following features were added to Agile ChangeCAST starting with Release 8.1:
❑
Faster performance – ChangeCAST transfers Changes significantly faster than
previous releases. ChangeCAST can transfer an ECO up to 1000 times faster!
What used to take hours now takes only minutes.
1-5
Agile ChangeCAST 2006
❑
New profile library – ChangeCAST 8.5 profiles are stored in AGX files, which
are text files. Profiles from pre-8.1 releases of ChangeCAST were stored in AGC
files. The default profile library is called ChangeCAST.agx. You can still use
AGC files with ChangeCAST 8.5 after ChangeCAST converts them to AGX
format.
❑
Converter tool – You can import all former .AGC profile libraries and convert
them into the new .AGX profile format. A 3-step wizard lets you import
profiles.
❑
Easy-to-use Mapping tool – The Field Mappings dialog box has been enhanced.
It now provides more information, an easy way to map ERP fields to system
flags, and dynamic selection of mapped fields.
❑
Automatic “Apply BOM Row Settings” – You no longer need to select the table
with BOM information. ChangeCAST now handles this for you.
❑
Transfer option enhancements – Changes to the Protocol and Files tabs of the
Transfer Options dialog box make this part of ChangeCAST easier to use.
❑
Import and export of mappings – You can now import and export mappings
from and to other ChangeCAST systems. The mapping window supports
import of .map files, which are text files that are created by exporting
ChangeCAST mappings.
❑
Differentiation of parts/documents and ECOs/MCOs – You can now have
ChangeCAST distinguish documents from parts, and MCOs from ECOs. If you
choose this option, you can map documents separately from parts, and you can
map MCOs separately from ECOs.
Guidelines for Using Agile ChangeCAST
For information about installing ChangeCAST see the Agile Advantage 2006
Installation and Maintenance Guide or the Agile Advantage 2006 Upgrade Guide.
To upgrade ChangeCAST on a system that has a pre-8.1 version of ChangeCAST:
1
Make sure ChangeCAST Release 7 or later is installed.
See the Agile Advantage 2006 Installation and Maintenance Guide for directions.
2
1-6
Install Agile ChangeCAST 2006 on the computer that contains the earlier
release of ChangeCAST.
User Guide
Chapter 1
3
Introducing Agile ChangeCAST
Be sure you have appropriate Read and Discover privileges and that the Agile
administrator has set your Agile ChangeCAST Access property to Yes in the
Users node in Agile Administrator.
Note
By default, the Administrator role does not include privileges
necessary to perform Change Analyst tasks. The Change Analyst role
should include the following privileges for each type of object: Read,
Create, Discover, Reports, Global Groups, Global Search, Modify,
Send, and Specify Output Columns.
4
You must have the Full Use user license of Agile Product Record Management
to run a session of ChangeCAST. Contact your Agile administrator if you don’t
have the required license.
5
Your Agile administrator must modify your profile to enable you to run
ChangeCAST. Contact your Agile administrator if you are unable to use
ChangeCAST.
6
Start ChangeCAST, as described in “Starting Agile ChangeCAST” on page 1-8.
The Agile eHub service must be running on the Agile server.
7
If you are upgrading from a previous release of ChangeCAST, check that
profiles and settings are correct. If necessary, build ChangeCAST profiles, or use
profiles provided by a ChangeCAST implementer. Create or modify field
mappings if necessary.
Note
If you modify a profile completed by an implementer, it is a good
idea to have the implementer validate your changes, if possible.
For information about importing and using existing profiles, see Chapter 2,
“Working with Profiles.” For information about creating, modifying, and
verifying field mappings, see Chapter 3, “Defining Attributes and Field
Mappings.”
8
Configure and verify ChangeCAST transfer settings, including a polling
schedule.
For information, see Chapter 4, “Formatting and Transferring Agile
Data Files.”
9
Enable the profiles and start ChangeCAST (see Chapter 4).
Here are some issues you should be aware of when using ChangeCAST:
❑
Fields on the Page Three tab cannot be mapped and transferred using
ChangeCAST.
1-7
Agile ChangeCAST 2006
❑
The year is always stored in 4-digit format. Check that macros accommodate
this format. Any 2-digit years are automatically changed to 4-digit format.
❑
If there is MCO-specific data that you want transferred, you must map those
fields.
❑
Only one ChangeCAST session may be running per eHub cluster.
Caution!
If your company is using ChangeCAST, in most cases all users should not
unrelease change orders in Agile Advantage. For best results, the
Unrelease privilege should not be granted to any users in Agile
Administrator, to avoid having a change order unreleased after it has
been transferred by ChangeCAST. Unreleased change orders are not
automatically resent through ChangeCAST.
Starting Agile ChangeCAST
To start Agile ChangeCAST, choose Start in the taskbar, then choose Programs | Agile
Advantage 2006 | Agile ChangeCAST 2006. You are prompted to log in with your Agile
username and password.
If you have appropriate privileges set in Agile Administrator, the ChangeCAST
window appears, as shown in Figure 1-2 on page 1-10. The first time you launch
ChangeCAST, its connection state is Paused (the Pause button is grayed and the
Resume button is available).
Minimizing On Launch
You can use the Minimized On Launch setting in the Options dialog box to determine
how ChangeCAST behaves when launched (choose Options from the Edit menu to
display that dialog box).
The following table summarizes launch behavior for different Minimized On
Launch settings and ChangeCAST connection states.
Table 1-4: Launch behavior summary
Minimize
On Launch
Last
Connect State
Not checked
Paused
1-8
Launch Behavior
When you launch ChangeCAST, you are prompted to
log in. The ChangeCAST window opens and the
connection state is Paused.
User Guide
Chapter 1
Introducing Agile ChangeCAST
Table 1-4: Launch behavior summary
Minimize
On Launch
Last
Connect State
Not checked
Resumed
When you launch ChangeCAST, you are prompted to
log in. The ChangeCAST window opens, and the
connection state is Resumed. (ChangeCAST starts
connecting and transferring change orders for each
enabled profile according to the schedule settings.)
Checked
Paused
When you launch ChangeCAST, ChangeCAST
automatically logs in as the previous user and appears
as an icon in the system tray. The icon indicates the
connection state is Paused.
Checked
Resumed
When you launch ChangeCAST, ChangeCAST
automatically logs in as the previous user and appears
as an icon in the system tray. The icon indicates that the
connection state is Resumed and ChangeCAST is
processing change orders according to schedule
settings.
Note: With these settings, ChangeCAST can process
change orders before a user has logged in to Windows.
This option allows ChangeCAST to process ECOs after
the computer has restarted, without intervention. If the
Agile server is not running, ChangeCAST will wait for
it to start.
Launch Behavior
To maximize Agile ChangeCAST when it is minimized, click the icon in the system
tray. You’ll be prompted to enter your password before the ChangeCAST window
opens.
When ChangeCAST has been properly configured, you can start it by clicking the
Resume button. For details, see “Starting and Stopping Agile ChangeCAST” on
page 4-11.
Logging In As a Different User
If another person has been using Agile ChangeCAST and you want to log in as a
different user:
❑
If the ChangeCAST window is open, choose Log In As A Different User from the
ChangeCAST File menu.
❑
If ChangeCAST is minimized to the system tray, right-click the icon in the
system tray and choose Login As A Different User from the shortcut menu.
1-9
Agile ChangeCAST 2006
The Agile ChangeCAST Window
When you launch ChangeCAST, the ChangeCAST window appears.
Figure 1-2: The ChangeCAST window
Title bar
Menu bar
Toolbar
Profile
Library
buttons
Profile
Library
table
Transfer
Control
buttons
Transfer
Log
table
Status
bar
The ChangeCAST window has these main features, described in the following
sections:
❑
Title bar
❑
Menu bar
❑
Toolbar
❑
Profile Library table, which displays all the profiles in the profile library
(ChangeCAST.agx) and their current transfer status
❑
Transfer Log table, which shows status messages from the last few data transfers
❑
Status bar
❑
Profile library buttons
❑
Transfer control buttons
1-10
User Guide
Chapter 1
Introducing Agile ChangeCAST
Title Bar
The title bar at the top of the Agile ChangeCAST window contains the application
name; the title bar at the top of most dialog boxes contains the name of the
currently selected profile.
Menu Bar
The Agile ChangeCAST menu bar includes the following menus.
Table 1-5: ChangeCAST menu options
Menu
Actions
File
Minimize application window, log in as a different user, exit.
Edit
Set launch options, enable differentiation between parts/documents and
ECOs/MCOs.
View
Display and clear the Transfer and Error logs.
Profile
Add, rename, copy, import, remove, and audit profiles.
Mapping
Create, modify, import, and export Agile-to-ERP field mappings and
attributes.
Format
Define the format of transfer files.
Transfer
Define the destination, transfer type, email notification, file format,
application adapter post-processor, and schedule for Agile-to-ERP data
transfers.
Reports
Produce a variety of reports for the current profile, all profiles in the library,
or the Agile tables; reports are created as .txt files.
Help
Display online documentation and ChangeCAST version and copyright
information.
Toolbar
The Agile ChangeCAST toolbar offers these shortcuts for menu commands:
1-11
Agile ChangeCAST 2006
Table 1-6: Toolbar buttons
Button
Actions
Opens the Add Profile dialog box for adding new profiles.
Add Profile
Opens Windows Notepad and displays the Transfer log file (for all
profiles).
View Log File
Displays the Field Mappings dialog box for the current profile so you
can create, modify, add, import, or export Agile-to-ERP field
mappings.
Edit Mapping
Displays the File Format dialog box for the current profile so you can
define or modify its transfer file format.
Format Options
Displays the Transfer Options dialog box for the current profile so
you can enter or modify its transfer file destination, email error
notification list, file naming scheme, and transfer schedule.
Transfer Options
Validates mappings for the selected profile, including checks for valid
attributes and syntax; errors are written to the ChangeCAST Error
Log.
Audit
Profile Library Table
The Profile Library table is used to manage Agile ChangeCAST profiles. It displays
all profiles that have been created or imported into the profile library file,
ChangeCAST.agx.
The profile library can contain up to 32 profiles. The profiles are processed in the
order shown in the list.
1-12
User Guide
Chapter 1
Introducing Agile ChangeCAST
Profile Library Fields
The Profile Library table contains these fields:
Table 1-7: Profile Library fields
Field
Description
Profile
The name given to the current profile
Description
An optional note describing the current profile
Enabled
Whether the profile is active (Enabled) or not (Disabled)
Last CO
The number of the last change order transferred, for example
EC23-2200
Last Transfer File
The name of the transfer file for the last change order transferred
— for example, AG000023.agl
Status
The transfer status of the last transfer attempted, whether
successful (Success) or not (Failed)
Date/Time
The date and time the last transfer was attempted (the Status field
was updated)
Profile Library Buttons
These buttons are located to the right of the Profile Library table and help you
manage the profiles listed in it:
Table 1-8: Profile Library buttons
Button
Action
Enable
Activates the current profile and changes the Enabled field to Yes,
after first auditing the mappings
Disable
Deactivates the current profile and changes the Enabled field to
No
Move Up
Moves the current profile up one row in the Profile Library table
(profiles are processed in the order shown in the table, top to
bottom)
Move Down
Moves the current profile down one row in the Profile Library
table
Import
Displays the Import Profile dialog box so you can import a profile
from another profile library file (*.agx or *.agc)
1-13
Agile ChangeCAST 2006
Transfer Log Table
The ChangeCAST Transfer Log table contains the last several lines from the
Transfer log file, with the most recent transaction listed at the bottom of the view.
To view the entire Transfer log, click View Log.
Transfer Log Contents
Each logged transfer transaction contains these fields:
Table 1-9: Contents of each logged transaction
Field
Description
Date/Time
The date and time of the current transfer attempt (log entry)
Change #
The number of the current change order, for example EC23-2200
Filename
The name of the transfer file for the last change order transferred,
for example AG000023.agl
Transfer Status
Comments indicating whether the transfer was successful or not
and additional information about the transfer, if appropriate
Destination
The FTP site or local directory where the file was to have been
transferred
Status
The transfer status of the last change order transferred, whether
successful (Success) or not (Failed)
Other event information also appears in the Transfer log. For more information,
see “Viewing and Printing Log Files” on page 4-12.
Transfer Control Buttons
These buttons, located to the right of the Transfer log, control transfers:
Table 1-10: Transfer control buttons
Button
Action
Pause
Stops the ChangeCAST polling schedule and transfer of change
orders for all enabled profiles
Resume
Starts the ChangeCAST polling schedule
Transfer Now
Processes and transfers all change orders that have been released
and not transferred for all enabled profiles; this is not dependent
on the connection state or current schedule
1-14
User Guide
Chapter 1
Introducing Agile ChangeCAST
Table 1-10: Transfer control buttons
Button
Action
View Log
Opens Windows Notepad and displays the entire Transfer log
Agile ChangeCAST Status Bar
The status bar at the bottom of the Agile ChangeCAST window displays the current
ChangeCAST state (Paused, Resumed, or Processing), the name of the current
logged-in user, and the name of the Agile server host computer.
Where to Go From Here
With Agile ChangeCAST running, you are ready to create new profiles or load and
verify existing profiles.
Chapter 2 describes how to import and manage profiles. Chapter 3 describes how
to define and modify field attributes and mappings. Chapter 4 describes how to set
and verify file transfer settings.
1-15
Agile ChangeCAST 2006
1-16
User Guide
C HAPTER 2
Working with Profiles
Profiles configure virtually all areas of Agile ChangeCAST performance.
This chapter contains the following topics, which describe how to create and
manage Agile ChangeCAST profiles:
❑ About Profiles
❑ Adding and Importing Profiles
❑ Copying Profiles
❑ Renaming Profiles
❑ Removing Profiles
❑ Distributing Profile Libraries
About Profiles
An Agile ChangeCAST profile is a group of settings that define many aspects of data
transfer from Agile Advantage to a single target ERP system. These aspects include
transfer file structure, transfer file delivery, scheduling information, email
notification lists, and data mapping. Profiles are used in the creation of transfer
files.
2-1
Agile ChangeCAST 2006
When you launch Agile ChangeCAST, a list of all available profiles appears in the
upper table of the ChangeCAST window. When you first install ChangeCAST, the
profile table is blank, and Agile ChangeCAST prompts you to create a default
profile. You can create and import up to 32 profiles. All the profiles together make
up a profile library. Only one profile library can be active at a time. The default
profile library is ChangeCAST.agx, located in the same directory as
ChangeCAST.exe. For other important definitions needed to work with Agile
ChangeCAST, see page 1-1.
Adding and Importing Profiles
You can create a profile in the Agile ChangeCAST profile library by adding a new
profile or importing one from another profile library. Once a profile has been
created, you can copy, rename, or remove it.
Before you can use a profile, you need to: set up its Attributes table, complete a set
of Agile-to-ERP field mappings, enter transfer destination and schedule
information, and set up a list of users to notify in case of transfer problems. For
instructions, see Chapter 3 and Chapter 4.
Note
You will not find Save or Open commands on the File menu. The profile
library is saved automatically when you change the connection state to
Resume, when you click OK in a dialog box, after each transfer, or when
you exit ChangeCAST.
Adding a New Profile
To add a new profile, choose Add Profile from the Profile menu, or click the Add Profile
toolbar button. Then enter appropriate information in the Add Profile dialog box
and all dialog boxes accessible from it. Finally, click OK to save the new profile to the
profile library.
Note
Creating a new profile from scratch is a detailed process. The completed
profile must exactly match the format requirements of the target ERP
system.
Importing a Profile
For best results, import source files (other profile library files) should be stored in
a separate subdirectory, such as Profiles, located under the ChangeCAST program
directory.
2-2
User Guide
Chapter 2
Caution!
Working with Profiles
Be careful not to overwrite any files in the Agile ChangeCAST program
directory when bringing in source files.
To import a profile from a ChangeCAST profile library (.agx or .agc file):
1
Choose Import from the Profile menu. The Import Profile wizard appears.
2
Select the type of profile library from which to import, then click Next.
3
Use the Open dialog box to select the target .agx or .agc file, then click Open. Step
2 of the wizard appears.
4
Select the profiles to import from the profile library. To select all profiles, click
Select All. To deselect all profiles, click Deselect All.
5
After selecting the profiles to import, click Next. Step 3 of the wizard appears.
6
Specify the Change Order Transfer Setup option that you want. The choices are:
Keep transfer state settings, Set all change orders as transferred, Set all change orders as NOT
transferred.
7
Under Profile Library Options, specify whether you want to add the new profiles to
the active profile library or completely overwrite the active profile library. If you
overwrite the active one, Agile ChangeCAST creates a backup copy in the
ChangeCAST program directory. Click Finish to import the profiles.
8
The imported profile names are checked for uniqueness. If a duplicate is found
in the profile library, you are prompted to enter a new name or to skip that
profile.
Figure 2-1: Profile Uniqueness Test
By default, the new profile is disabled.
Note
When you import a profile, you’ll need to edit the mappings and set
transfer options (Transfer | Protocol, Transfer | Notification, and Transfer |
Schedule) before you can enable the profile.
2-3
Agile ChangeCAST 2006
Auditing and Validating the Imported Profiles
After you import a profile, it must be audited and validated to verify its integrity.
To audit a profile:
1
Select the profile that was imported in the previous section.
2
Choose Profile | Audit. The audit function reviews the profile and compares all
Agile mapped fields to designated ERP tables. Most newly imported profiles fail
the audit and return an Error Log dialog box, as in the following figure. This is
normal.
Figure 2-2: Audit errors
To pass the audit, the profile must go through a validation step with the Edit
Mappings function. Click OK to close the Error Log, and proceed to the next
step.
3
Choose Mapping | Edit Mappings. The Field Mappings window appears and displays
all Agile to ERP field mappings for the selected profile.
• If the Field Mappings dialog box appears with no errors or alert prompts, give
the mappings a cursory review and click OK. Clicking OK validates the
mappings. Proceed to Step 4, below.
• If your profile contains conditional mappings, you may receive the following
messages before the Field Mappings dialog box appears. This is normal.
The Mapping Analysis message states which mapped line number needs to
undergo an additional validation step. Note the mapping number and click OK.
2-4
User Guide
Chapter 2
Working with Profiles
The Conditional Mappings message follows, stating that some ERP tables are
not mapped properly to related Agile tables. Click OK to continue.
4
When the Field Mappings dialog box appears, in the Mapped Fields pane, select
the mapping line number that was displayed in the Mapping Analysis message
earlier, then click the Edit Mapping button. The Map Condition dialog box
appears.
Figure 2-3:
Map Condition dialog box
No information changes are required. Click OK.
The Agile Table Type dialog box appears. No information changes are required.
Click OK. When you click OK, the condition goes through an automated system
validation.
Figure 2-4:
Agile Table Type dialog box
At this point, you should be back at the Field Mappings dialog box. Click OK to
close the dialog box, and proceed to the next step.
2-5
Agile ChangeCAST 2006
5
You can now re-audit the profile. Choose Profile | Audit. The Audit function
reviews the profile again and should confirm that the profile is responding
normally and that all mapped tables are valid. If they are, you should receive the
following message:
Figure 2-5: Profile Audit
If the audit returns no errors, your profiles are in good shape. If you receive
additional audit errors, perform Steps 2 through 5 again until all conditional
rows are validated. If you continue to receive errors, contact Agile Support.
Copying Profiles
You can create a new profile by copying one that already exists in your profile
library. The copy contains the Format settings and Mappings of the original profile.
The name and Transfer settings must be entered by the user.
To copy a profile:
1
Choose Copy from the Profile menu.
The Copy Profile dialog box appears.
2
Use the drop-down list to select a source profile from your profile library. The
currently selected profile appears by default.
3
Enter a new name for the selected profile. The currently selected profile name
appears by default.
4
Enter a new description or edit the current description. The description of the
currently selected profile appears by default.
5
Click OK to add a profile with the new name and description.
Note
The new profile name is checked for uniqueness. If a duplicate is found,
you must enter a different name.
Renaming Profiles
You can rename the currently selected profile or change the profile description.
2-6
User Guide
Chapter 2
Working with Profiles
To rename a profile:
1
Either select a profile in the Profile Library table of the ChangeCAST window
and choose Rename from the Profile menu, or double-click a profile in the Profile
Library table.
The Rename Profile dialog box opens with the selected profile loaded.
2
Enter a new name for the profile. The name of the selected profile appears by
default.
3
Enter a new description, or edit the current description. The description of the
selected profile appears by default.
4
Click OK to apply the new name and description to the selected profile.
Note
The new profile name is checked for uniqueness. If a duplicate is found,
you can enter a different name.
Removing Profiles
If necessary, you can remove a profile from the profile library.
To remove a profile:
1
Select a profile in the Profile Library table of the Agile ChangeCAST window
and choose Remove from the Profile menu.
2
You are prompted to remove the profile or cancel the operation.
Click OK to permanently remove the selected profile.
Note
When you delete a profile, the transfer flags are cleared, a process that can
take several minutes. It is very important that you wait while Agile
ChangeCAST completes this process.
Distributing Profile Libraries
Sometimes it is appropriate to create a profile library on one computer and
distribute it to Agile ChangeCAST users working at other sites. ChangeCAST
always uses ChangeCAST.agx as the active profile library.
Note
Agile ChangeCAST 8.1 and later profile libraries are not supported on
releases of Agile ChangeCAST prior to Release 8.1.
2-7
Agile ChangeCAST 2006
To distribute a profile library:
1
Exit Agile ChangeCAST completely (don’t minimize).
2
Copy the profile library (ChangeCAST.agx) you want to distribute and give it
another name, such as NewLibrary.agx.
3
Distribute it to the target ChangeCAST site or sites.
When it reaches the target site, someone should:
1
Copy it to the ChangeCAST\Profiles directory.
2
Import the new profiles, deciding whether to:
• Replace the current version of ChangeCAST.agx with the new profile library,
or
• Import profiles from the new profile library into the existing profile library
Follow the instructions for importing profiles on page 2-2.
3 Verify Transfer settings.
2-8
User Guide
C HAPTER 3
Defining Attributes and
Field Mappings
Before you can use a profile to transfer Agile Advantage data, you must map
fields in the Agile Advantage database to fields in the target ERP system.
This chapter describes how to set up Agile ChangeCAST attributes and
Agile-to-ERP field mappings. Together, these settings define which Agile
Advantage data is passed to which fields in the target ERP system.
Topics include:
❑ Guidelines for Defining Attributes and Field Mappings
❑ Differentiating Documents from Parts and MCOs from ECOs
❑ Defining ERP Attributes
❑ Specifying and Verifying Agile-to-ERP Field Mappings
❑ Producing Agile ChangeCAST Reports
Note: Even if you obtain a profile library from another source, you’ll need to
verify that its mappings and settings are correct. To do that, prepare
Mappings reports (see page 3-17).
Guidelines for Defining Attributes and Field Mappings
Note
The terms ERP attribute and ERP field are used interchangeably.
3-1
Agile ChangeCAST 2006
To define ERP attributes and field mappings for each profile in your Agile ChangeCAST profile
library, follow these basic steps:
1
Select a profile in the Profile Library table of the Agile ChangeCAST window
(described on page 1-10).
2
Decide whether you want Agile ChangeCAST to distinguish documents from
parts, and MCOs from ECOs (see “Differentiating Documents from Parts and
MCOs from ECOs” below).
3
Define ERP attributes to identify the fields in the target or host ERP system that
could be chosen to receive data from the Agile Advantage system (see page 3-3).
4
Print Agile Table and Attributes reports to assist in mapping Agile Advantage
fields to fields in the target ERP system (see page 3-17).
5
Use the Agile fields and ERP attributes to create a set of Agile-to-ERP field
mappings (described on page 3-7).
6
Print a Mappings report to verify that the mappings are correct (page 3-17).
7
Modify the mappings as necessary until they are correct.
Once the mappings have been created, you can define transfer settings and start
using Agile ChangeCAST, as discussed in Chapter 4.
Caution!
While working with attributes and mappings, it is a good idea to use the
Profiles directory to hold attribute and other files that you have exported
or intend to import or open. Be careful not to overwrite files in the top
level ChangeCAST program directory, especially ChangeCAST.agx.
Differentiating Documents from Parts and MCOs from ECOs
By default, Agile ChangeCAST treats documents as parts, and MCOs as ECOs.
Therefore, documents and parts are mapped to the same ERP table, and MCOs and
ECOs are mapped to the same ERP table.
If you want Agile ChangeCAST to distinguish documents from parts, and MCOs
from ECOs, use the Enable differentiation between Agile Classes setting (in the Options
dialog box). With this setting, you can map documents separately from parts, and
you can map MCOs separately from ECOs.
3-2
User Guide
Chapter 3
Caution!
Defining Attributes and Field Mappings
If you are upgrading from a previous release of Agile ChangeCAST,
before you can use Enable differentiation between Agile Classes, you must
create new ERP tables and attributes, and re-map documents and MCOs.
Also, if you are using an application adapter, it may require modifications
to support this mode.
To access this option:
1
Choose Edit | Options.
2
Check the Enable differentiation between Agile Classes box.
3
Click OK.
If this option is not checked, Agile ChangeCAST treats documents as parts and
MCOs as ECOs. This reflects the behavior in previous releases of Agile
ChangeCAST.
Defining ERP Attributes
Before you can complete a ChangeCAST profile definition, you need to define
attributes for the target ERP database. These describe the ERP database fields that
can be mapped to receive data from Agile.
You can use the Attributes Table dialog box to define attributes for the target ERP
system by entering them manually or by opening or importing a ChangeCAST
(.aga) attribute file. For more information, see “The Attributes Table Dialog Box”
below.
After you define a set of attributes, you can print and review an Attributes report
(described on page 3-17). Modify the attribute definitions if necessary.
It is recommended that you include all of the fields available for the target ERP
system. This makes it easier to add mappings that were not used in your initial Agile
ChangeCAST implementation.
The Attributes Table Dialog Box
To display the Attributes Table dialog box, select a profile in the Profile Library
table and choose Edit Attributes from the Mapping menu.
3-3
Agile ChangeCAST 2006
Figure 3-1: Attributes Table dialog box
Attribute Text Boxes
You can edit, view, or create new attributes individually with the text boxes at the
top of the Attributes Table dialog box. The following fields appear for the row
selected in the table at the bottom of the dialog box.
Table 3-1: Fields for each row in selected table
Field
Description
Table Name
Name of the ERP table containing the ERP field that may be
targeted to receive data
Table Description
Descriptive text used to define the ERP Table name
Field Name
Name of the target field in the ERP table
Field Description
Descriptive text used to define the field name
Field Length
The maximum length (characters) allowed for data sent to the
target ERP field
Field Type
The type of data: numeric, date, or text
The Attributes Table
The Attributes table, in the lower part of the dialog box, contains ERP table names,
table descriptions, field names, field descriptions, and field lengths for the loaded
ERP attributes.
3-4
User Guide
Chapter 3
Defining Attributes and Field Mappings
The Attributes table must exist before you can map Agile Advantage fields to the
ERP system. After loading or directly defining these target attributes, you can use
the Field Mappings dialog box to configure the actual Agile-to-ERP field mappings.
You can load attributes from an exported Agile ChangeCAST attribute file (*.aga).
Attributes Table Dialog Box Buttons
The following buttons act on the Attributes table:
Table 3-2: Buttons for Attributes table
Button
Action
Add
Adds the data in the attribute text boxes to the Attributes table as a new row.
Modify
Replaces the selected row with edited data from the attribute text boxes.
Remove
Deletes the selected row.
Import
Replaces all existing attributes with the contents of the selected attribute file
(*.aga).
Export
Saves the current Attribute table rows as an attribute file (*.aga).
Add from file Adds attributes in the selected attribute file (*.aga) to the list of existing
attributes.
Adding Individual Attributes
To create an attribute directly in the Attributes Table dialog box:
1
Enter the attribute data in the text boxes.
2
Click the Add button to add the new attribute to the Attributes table.
Note
The Add button is available only if the table name/field name combination
you enter is different from all others in the Attributes table. If you change
the table name or field name, the attribute is added. If you change the
table description or field description, the attribute is modified.
Modifying Attributes
To modify an existing attribute in the Attributes Table dialog box:
1
Select an attribute in the Attributes table.
Its fields appear in the text boxes at the top of the Attributes Table dialog box.
3-5
Agile ChangeCAST 2006
2
Edit the attribute data in the text boxes.
3
Click the Modify button to enter the changes in the Attributes table.
Note
You cannot modify an attribute’s ERP table or attribute name if the
attribute is currently used in a mapping. You can modify the descriptions
and field length.
Removing Attributes
To remove an attribute in the Attributes Table dialog box:
1
Select an attribute in the Attributes table.
2
Click the Remove button to delete the attribute from the table.
Note
You cannot remove an attribute if it is currently used in a mapping.
Appending Attributes from a File
To append attributes from an attribute file to the bottom of the current Attributes table in the
Attributes Table dialog box:
1
Click the Add from file button in the Attributes Table dialog box.
2
Select the attribute file (*.aga) that contains the attributes you want to add.
3
Click Open.
The attributes in the selected file appear following those in the current table.
Importing Attributes
To select a new attribute file (*.aga) and replace all the existing attributes in the Attributes Table
dialog box:
1
Click Import in the Attributes Table dialog box.
2
Choose an attribute file to import and click Open.
Caution!
When you import an attribute file and replace all existing attributes, you
also reset and remove all existing mappings for the profile.
Exporting Attributes
You can export all of the attributes in the current Attributes table to an .aga text file.
3-6
User Guide
Chapter 3
Defining Attributes and Field Mappings
It isn’t necessary to export attributes, since the attribute information contained in
the table is included in the current profile. However, exported .aga files can be used
for reference, and might be requested by your Agile Support representative to help
with troubleshooting. These files can be copied to other Agile servers and used as
source files for importing Agile ChangeCAST attribute sets.
To export attributes in the Attributes Table dialog box:
1
Click the Export button.
2
Specify the name and location of the Agile ChangeCAST attribute file (*.aga),
and click Save.
Verifying Attributes
When you have finished loading or entering field attributes, you can verify that all
necessary ERP fields are included in the Attributes table and their data is entered
correctly.
To verify attribute definitions, print and review an Attributes report. For
instructions, see page 3-17.
If you need to add or modify an entry, follow the steps on page 3-5. When the
attribute data is complete, you can map Agile Advantage fields to the ERP fields.
Specifying and Verifying Agile-to-ERP Field Mappings
ChangeCAST profiles contain mappings of fields in your Agile Advantage database
to corresponding fields in an ERP system. Agile ChangeCAST uses these mappings
when it creates files that transfer information from an Agile Advantage database to
an ERP database.
This section describes how to create, modify, and verify field mappings for a
ChangeCAST profile.
Guidelines for Mapping Fields
To create, modify, and verify field mappings in Agile ChangeCAST, follow these basic steps:
1
Before you begin to map Agile Advantage database fields to fields in the target
ERP system, it is a good idea to complete the following tasks:
• Produce a report of Agile Advantage data tables and fields (described on
page 3-17).
3-7
Agile ChangeCAST 2006
• Complete a set of ERP attribute entries for each profile (page 3-3).
• Produce an Attributes report for each profile (page 3-17).
2
Open the ChangeCAST Field Mappings dialog box (page 3-9) and use it to map
Agile Advantage fields to equivalent ERP fields.
3
Produce a Mappings report and use it to verify the mappings (page 3-17).
4
Modify any incorrect mappings in Agile ChangeCAST and produce additional
Mappings reports until the mappings are complete.
Note
If you are using profiles created by someone else, perform steps 3 and 4
to verify that the mappings are complete and correct.
Mapping Manufacturer or AML Fields
The following considerations apply if you are mapping fields from Agile
Advantage:
❑
You must be sure the fields are set to Visible in Agile Administrator, in the
Manufacturer or Manufacturer Part | Attributes node, and also in the Parts Class |
Attributes | Manufacturer node.
❑
All Agile Manufacturer fields must be mapped to a single ERP table, separate
from other BOM item data.
❑
The multilist fields of Manufacturers and Manufacturer Parts cannot be
mapped.
❑
Pending changes cannot be mixed in a single table with AML, and BOM fields
cannot be included in the same table when AML fields are mapped.
Note
Fields in the Page Three tab (an optional tab that your administrator may
have set up) cannot be mapped. Make sure that all fields that must be
transferred are on Page Two or on other tabs, where they can be mapped.
A Note about BOM Tables
If you have an ERP table with BOM information, Agile ChangeCAST sets it as a
BOM table even if this table was not marked as a BOM table by pre-8.1 releases of
ChangeCAST. This means that different information will be transferred by Agile
ChangeCAST. If you want the information transferred to be the same as with
previous releases, choose Mappings | Edit Mappings and replace the target with 0 (zero).
3-8
User Guide
Chapter 3
Defining Attributes and Field Mappings
The Field Mappings Dialog Box
You use the Field Mappings dialog box to create Agile ChangeCAST field
mappings.
To display the Field Mappings dialog box:
1
Select a profile in the Agile ChangeCAST window.
2
Choose Mapping | Edit Mappings, or click the Edit Mapping button on the
ChangeCAST toolbar.
You can also choose Profile | Add to display the Add Profile dialog box, then click
the Field Mappings button in the Add Profile dialog box.
Figure 3-2: Field Mappings dialog box
Mapped ERP attributes are boldface. Click one to
see the mapping under Mapped Fields.
Clicking a row selects the corresponding Agile and
ERP fields above.
3-9
Agile ChangeCAST 2006
The Field Mappings dialog box has these main parts:
Table 3-3: Field Mappings dialog box components
Tree or Table
Description
Agile Fields tree
Appears in the upper left portion of the dialog box and lists
available Agile data tables and fields, grouped by table names. An
Agile field can be used in multiple mappings. The field’s ID
number is shown in parentheses. The ID is what is used for the
actual mapping by Agile ChangeCAST.
Target ERP Fields tree
Appears in the upper right portion of the dialog box and lists all
of the ERP tables/fields configured in the Attributes Table dialog
box. This tree hierarchy is grouped by table names in the ERP
system. An ERP field may be mapped only once.
A table name in parentheses following an ERP table name
indicates that the ERP table has attributes that are mapped to a
field of the Agile table noted in parentheses.
An asterisk following an ERP attribute indicates that the
attribute is mapped to a field that belongs to an Agile table (for
example, a BOM table).
Mapped Fields table
Appears in the lower portion of the dialog box; lists each ERP
field and what is mapped to it, displayed as a row in the table.
Row order determines processing order, top to bottom.
Mapped Fields Table Columns
The Mapped Fields table contains these columns:
❑
The No. column, the leftmost column in the table, numbers each mapping. Each
mapping occupies one row. The order of processing is top to bottom, and the
number in the Order column signifies that order.
❑
The ERP Attribute column contains the ERP target table and field.
Note
❑
Individual ERP fields are grouped by ERP table name in the Mapped
Fields table. The order of the entries in the Mapped Fields table is a direct
reflection of the resulting transfer file. Mapping order is critical to the
successful loading of data into the ERP. See page 3-16 for information on
reordering the Mapped Fields table.
The Agile Attribute column contains the Agile Advantage field and/or Map
Condition expression defining the value to be transmitted.
3-10
User Guide
Chapter 3
Defining Attributes and Field Mappings
Field Mappings Dialog Box Buttons
The Import button lets you import mappings from .MAP files (text files), replacing
all existing mappings. The Add button lets you add mappings from a mapping file.
For details, see “Importing or Adding Field Mappings” on page 3-14.
The buttons to the right side of the Mapped Fields table apply to the selected
mapping.
Table 3-4: Mapped fields buttons
Button
Action
Unmap
Removes the selected mapping from the table.
Caution! Unmap removes the selected mapping row. There is no undo for
this action! If you remove a mapping and want to retrieve it, recreate it with
the mapping tools at the top of the dialog box, or click Cancel to close the
Field Mapping dialog box and lose any modifications that you have made.
Move Up
Moves the selected mapping up in the list within the appropriate table.
Move Down
Moves the selected mapping down in the list within the appropriate table.
Edit Mapping
Displays the Map Condition dialog box for the selected mapping. If no
condition is configured, you can create a condition. If a condition already
exists, you can edit the existing condition.
Reorder
Tables
Displays a dialog box where you can specify the output order of the
mapped tables.
Creating Field Mappings
To map an Agile field to an ERP field:
1
Expand the source Agile Fields tree, and select the source Agile Advantage field.
2
Expand the Target ERP Fields tree, and select the target ERP field.
3
Click the Map button. The mapping appears in the Mapped Fields table.
Mapping to Null
If you want an ERP field to be passed the system NULL character, map the field to
NULL. This is often used to convey a default setting.
3-11
Agile ChangeCAST 2006
To map an ERP field to null:
1
Expand the Target ERP Fields tree, and select the target ERP field.
2
Click the Map To Null button.
When you map a field to null, the field is listed in the Mapped Fields table.
SYS_NULL appears in the Expression column in the Mapped Fields table as a
placeholder for an Agile Advantage field or mapping condition.
Mapping to System Variables
The Map Special button lets you map ERP fields to system variables, or system flags,
such as SYS_ACD. This button is unavailable if the selected ERP field has been
mapped.
To map an ERP field to a system variable:
1
Expand the Target ERP Fields tree, and select the target ERP field.
2
Click Map Special.
3
In the System Flags list, select the flag to which you want to map the target ERP
field.
4
Click Map.
5
If there is only one system flag and the table has not been set as a “BOM table”
or as an “AML table,” the Agile Table Type dialog box appears so that you can
assign an Agile table to the ERP table that contains the ERP field. Select an Agile
table from the drop-down list.
Specifying a Map Condition
Instead of setting up a simple mapping or mapping to null, you can specify a set of
conditions to control a field’s mapping.
Map conditions are formulas that can examine and manipulate Agile field data and,
based on the results, either use the data or change the data sent from the Agile field
mapped in the Field Mappings dialog box.
Map conditions are constructed with Agile ChangeCAST macro functions.
To specify a map condition for a new mapping:
1
Expand the Target ERP Fields tree, and select the target ERP field.
2
Click the Map Condition button.
3-12
User Guide
Chapter 3
Defining Attributes and Field Mappings
The Map Condition dialog box appears. You can enter a formula for
manipulating data which will be sent from the mapped field.
For example, the formula =IF(ISBLANK([Parts.General Items
Attributes.Rev:1014]),”Invalid”,”Valid”) returns Invalid if no
revision has been supplied. You can also change the form of the transmitted
data through the use of functions. For more information, see “The Map
Condition Dialog Box,” below.
3
When you close the Map Condition dialog box, the mapping appears in the
Mapped Fields table.
To edit a map condition for any existing mapping, double-click the mapping row
in the table or select the mapping row and click the Edit Mapping button.
The Map Condition Dialog Box
Figure 3-3: Map Condition dialog box
The Map Condition dialog box includes these boxes, lists, and buttons:
Table 3-5: Map Condition dialog box components
UI Feature
Action
Target Field
Displays the name of the ERP table/field to which this condition will
apply.
System Flags list
Lets you select a system flag for use in the condition formula (refer to
Agile ChangeCAST Macro Reference documentation topics for
explanations of the system variables).
Insert Flag button Inserts the selected system flag, or variable, into the Expression field.
3-13
Agile ChangeCAST 2006
Table 3-5: Map Condition dialog box components
UI Feature
Action
Agile Fields list
Allows you to select an available Agile source field.
Insert Field
Inserts the selected field name into the Expression field.
button
Function List
Allows you to select macro functions for use in the condition formula
(refer to Agile ChangeCAST Macro Reference topics for explanations
of the functions and their syntax).
Insert Function
Inserts the selected function (and placeholders) into the Expression
field at the cursor location.
button
Expression field
Used to construct the condition formula that will be used to calculate
the value for the target field; contains the fields and functions that you
insert with the Insert Flag, Insert Field, and Insert Function buttons,
including constants and system variables.
Test Expression
button
Checks the syntax of the statement in the Expression field and generates
a sample of the value returned by the condition formula.
Test Result field
Contains the result of running the test.
Editing Condition Formulas
You can edit the formula in the Expression field by inserting fields and functions at
the cursor location. You can also cut (Ctrl+X), copy (Ctrl+C), and paste (Ctrl+V)
selected text or type it directly.
Conditions are verified when the profile is enabled, when you click OK, or you click
the Test Expression button in the Map Condition dialog box. Detected errors are
written to the Error log, accessible from the ChangeCAST View menu. When you
are done with all mappings, you can click the Audit button in the ChangeCAST
toolbar to test for syntax errors. See “Toolbar” on page 1-11 for an illustration of
the Audit button. For more information about the Error log, see page 4-13.
Importing or Adding Field Mappings
You can import and add field mappings from mapping (.MAP) files generated with
other Agile ChangeCAST 8.1 or later systems.
3-14
User Guide
Chapter 3
Defining Attributes and Field Mappings
Figure 3-4: Sample .MAP file
The Import button imports field mappings, replacing all existing mappings. The Add
button imports field mappings, adding the imported mappings to the existing
mappings.
To import field mappings in the Field Mappings dialog box, replacing any existing mappings:
1
Click the Import button.
2
Agile ChangeCAST warns you that existing mappings will be replaced. Click Yes
to continue with the operation.
The Open dialog box appears.
3
Locate the .map file to import and click Open.
The imported mappings appear in the Mapped Fields table.
To add field mappings in the Field Mappings dialog box:
1
Click the Add button.
The Open dialog box appears.
2
Locate the .map file that contains the mappings you want to add, and click Open.
The mappings appear in the Mapped Fields table after any existing mappings.
Note
If there are conflicts (for example, one ERP field is mapped to more than
one Agile field), an error message appears, an entry is written in the Error
log, and the offending fields are mapped to the SYS_NULL system
variable.
Exporting Field Mappings
You can export field mappings to use with other Agile ChangeCAST profiles.
3-15
Agile ChangeCAST 2006
To export field mappings:
1
In the ChangeCAST window, select the profile that contains the mappings that
you want to export.
2
Choose Mapping | Edit Mappings.
3
Click the Export button. The Save As dialog box opens.
4
Specify a filename and location for the mapping file. The file will have a .MAP
extension.
5
Click the Save button.
The new mapping file is saved. It can now be imported into other Agile
ChangeCAST profiles.
Managing Mapped Fields
The Mapped Fields table, in the lower portion of the Field Mappings dialog box,
lists existing Agile-to-ERP field mappings.
If you select a mapping row in the table, you can use the buttons on the right side
of the Mapped Fields table to manipulate the mapping. For a description of the
buttons, see “Field Mappings Dialog Box Buttons” on page 3-11.
Reordering Mapped Fields
Mapped fields are processed and output from top to bottom according to their row
position in the Mapped Fields table on the Field Mappings dialog box. Fields are
grouped by their ERP table name.
To adjust the processing order of mapped fields at the table level:
1
Click the Reorder Tables button on the Field Mappings dialog box.
2
Select a table and click Move Up or Move Down to change the position of the table.
3
When you are done, click OK.
To reorder field mappings directly:
1
Select the mapping in the Mapped Fields table.
2
Use the Move Up or Move Down buttons to change the position of the field within
the same table list.
3
When you are done, click OK.
3-16
User Guide
Chapter 3
Defining Attributes and Field Mappings
Producing Agile ChangeCAST Reports
ChangeCAST Profile reports can help you verify attribute definitions, mappings,
and other profile settings. The Agile Tables report lists Agile Advantage tables and
fields, so you can match them with appropriate fields in ERP tables.
Profile Reports
You can produce several kinds of reports for the profile currently selected in the
Agile ChangeCAST window or for all profiles in the profile library.
To produce an Agile ChangeCAST Profile report:
1
Open the Reports menu.
2
Choose Current Profile to prepare a report for the selected profile, or choose All
Profiles to prepare a report for all profiles in the library.
3
Choose the type of report:
• Attributes to list current ERP field attributes
• Mappings to list current Agile-to-ERP field mappings
• Settings to list current transfer file format settings
• Transfer Options to list target destination and communication settings
A Save As dialog box appears and prompts you to save the report as a text file
with extension .txt.
4
Specify a destination for the report, and enter a name.
5
Click Save to save the report to the specified destination and display its contents
in Windows Notepad.
Producing an Agile Tables Report
You can produce a list of Agile Advantage data tables and their fields to help you
map Agile data fields to fields in the target ERP database.
To produce an Agile Tables report:
1
Choose Reports | Agile Tables.
A Save As dialog box appears and prompts you to save the report as a text file
with extension .txt.
3-17
Agile ChangeCAST 2006
2
Specify a destination for the report, and accept the default name or enter a
different name.
3
Click Save to save the report to the specified destination and display its contents
in Windows Notepad.
Printing Agile ChangeCAST Reports
To print an Agile ChangeCAST report saved as a text file, open it in Notepad,
WordPad, or another text editor or word processor outside of ChangeCAST and
print it from there. Then you can use the report to help you change or verify Agile
ChangeCAST settings.
3-18
User Guide
C HAPTER 4
Formatting and
Transferring Agile
Data Files
This chapter introduces Agile ChangeCAST transfer file formatting and
describes how to verify and modify transfer destination and schedule
settings. It also describes how to perform transfers, check logs, and correct
transfer problems.
It includes these topics:
❑ About Agile ChangeCAST Transfers
❑ Formatting Agile ChangeCAST Transfer Files
❑ Reviewing and Modifying Transfer Settings
❑ Enabling and Disabling Profiles
❑ Starting and Stopping Agile ChangeCAST
❑ Viewing and Printing Log Files
❑ Retransferring Change Orders
❑ Forcing Unscheduled Transfers
❑ Backing Up Files
❑ Suggestions for Troubleshooting
4-1
Agile ChangeCAST 2006
About Agile ChangeCAST Transfers
When it is in the Resumed connection state, Agile ChangeCAST periodically checks
the Agile database and looks for change orders that have been released since the last
time Agile ChangeCAST polled the Agile Advantage database.
If any are found, all enabled profiles translate the change order information into
properly formatted transfer files and store the files at the specified locations. The
files can then be processed by a local application adapter or transferred by FTP to
an ERP host or hosts for processing.
Agile ChangeCAST can synchronize up to 32 different ERP systems with the data
in the Agile system, as illustrated in Figure 4-1.
Figure 4-1: Agile ChangeCAST
Agile Database
ChangeCAST
Polls the Agile database for change orders
and notices a change has been released. Works
with up to 32 profiles.
ERP Profile
Creates a transfer file and
copies it to the ERP.
ERP Profile
Creates a transfer file and
copies it to the ERP.
...
ERP Profile
Creates a transfer file and
copies it to the ERP.
PC
01
01
Application Adapter
Reads the transfer file and
updates ERP tables.
ERP System #1
HOST
Application Adapter
Reads the transfer file and
updates ERP tables.
ERP System #2
01
Application Adapter
Reads the transfer file and
updates ERP tables.
ERP System #32
The following sections introduce Agile ChangeCAST transfer files and describe
how to specify the source, destination, and polling schedule for transfer files.
4-2
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
Formatting Agile ChangeCAST Transfer Files
Transfer files are ASCII text files that relay information from Agile Advantage to a
target ERP system. Their default extension is .agl. They can have many format
variations, depending on what is required by the application adapter that verifies
and loads information into the ERP database (see Figure 4-1).
Caution!
This information is intended only as an overview. Unless you are
involved in creating transfer files to suit specific application adapters, you
should not change any transfer file format settings. Incorrect settings can
result in transfer files that are not readable by the target ERP system.
To set the format of Agile ChangeCAST transfer files:
1
Select a profile in the Profile Library table in the upper half of the ChangeCAST
window.
2
Choose a command from the Format menu, depending on the type of settings
you want to review or modify:
• File Structure — Basic elements of the file structure, such as data/layout
sections and orientation (horizontal or vertical)
• Delimiters — Whether fields are delimited or fixed length, and which
characters to use as delimiters
• Data Format — Format options for reference designators, time and date
formats, text data conversions
• BOM/AML Settings — Options for how BOM rows are output
3
In the File Format dialog box, change appropriate settings and apply them.
4
Produce and print a Settings report so you can verify the settings and change
them if necessary. See “Profile Reports” on page 3-17.
For specific information, see the Agile ChangeCAST 2006 Integration Developer
Guide.
Reviewing and Modifying Transfer Settings
You can use the Agile ChangeCAST Transfer menu and Transfer Settings dialog box to
review and change a number of settings related to data transfer:
❑
Protocol — How transfer files are transferred (FTP or local copy) with
appropriate destination settings
4-3
Agile ChangeCAST 2006
❑
Notification — Whom to notify through email in case of transfer problems
❑
Schedule — When and how often to poll for change order releases and perform
transfers
❑
Connection — To set the reconnection time if connection fails and the number of
reconnection attempts
Files — Transfer file naming conventions and other transfer file details
❑
❑
Application Adapter — Starts a local application adapter (not available if files are
FTP’d to another location)
Caution!
You are most likely to change the Protocol, Notification, and Schedule
settings. Only those who are closely involved in implementing Agile
ChangeCAST and related application adapters should need to change the
Files and Application Adapter settings; as with Format settings, incorrect
Files and Application Adapters settings can result in serious transfer
problems.
The following sections describe how to review Protocol, Notification, and Schedule
settings and change them if necessary.
Reviewing and Editing Protocol Settings
You can use the Protocol tab of the Transfer Settings dialog box to configure file transfer
protocol options, including whether to use FTP (File Transfer Protocol) and
various FTP options.
If Use FTP is checked, the numbered files in the outgoing directory are transmitted
in numerical order to the FTP target path specified on the Protocol tab.
❑
If the FTP process is successful, the file is transferred but a copy remains in the
outgoing directory.
❑
If the FTP process is not successful, an email indicating that there was an error
is sent to addresses listed on the Notification tab, and the profile status becomes
Disabled. The file is not transferred. If the profile is re-enabled, the next time a
transfer occurs, either on schedule or with the Transfer Now button or command,
a new file is generated and transferred.
To display the Protocol tab, do one of the following:
Select a profile in the Agile ChangeCAST window and choose Protocol from the
Transfer menu. Use the Transfer Settings dialog box.
4-4
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
Figure 4-2: ChangeCAST Protocol Settings
You can review the following Protocol settings and change them if necessary:
Table 4-1: Protocol Options
Setting
Action
Output Directory
The local directory in which all transfer files are created and
archived (whether using FTP or not) for this profile.
Use Default Output Directory When checked, applies the same Output Directory
For All Profiles
information to all profiles; if not checked, settings apply only
to the currently selected profile. Note: If all profiles use the
same FTP path, filenames — set on the Files tab (page 4-3)
— must be different or processing will halt.
Currently Using Default
Directory From Profile
The name of the profile that is currently using this default
directory. Available only if Use Default Output Directory For All
Profiles is checked.
Set current profile as default Sets the output directory of the currently selected profile as
the default for all profiles. Available only if Use Default Output
Directory For All Profiles is checked.
Use FTP
When checked, transfers data using FTP.
FTP Host Name
The IP address or DNS NAME (host alias) of the host system.
FTP User Name
Your FTP host login name.
FTP Password
Your FTP host password.
4-5
Agile ChangeCAST 2006
Table 4-1: Protocol Options
Setting
Action
Confirm Password
A second entry of what you typed for FTP Password; the
password entered must be exactly the same as the one entered
previously, both the spelling and case.
FTP Target Path
The destination directory where files can be accessed by the
application adapter for the host ERP system (if UNIX host,
must use “/” as appears on target server). You can enter a dot
( . ) to specify the current path.
FTP Port
The host system FTP port (Port 21 is the default).
Transfer Mode
The FTP transfer mode, either Binary or ASCII; use the
default, ASCII.
Verify FTP Connection
Tests the FTP parameters you entered by relaying a dummy
file to the target then deleting it; if there are any problems
contacting the FTP Host, an error message appears.
Reviewing and Editing Notification Settings
You can use the Notification tab of the Transfer Settings dialog box to set up a list of
users to notify by email in case of processing or transfer errors. ChangeCAST does
not detect failures of application adapters to process a transfer file once it has been
delivered. Notification can be different for each profile and must be defined for
each profile.
To display the Notification tab, do one of the following:
Select a profile in the Agile ChangeCAST window and choose Notification from the
Transfer menu. Use the Transfer Settings dialog box.
You can review the following Notification settings and change them if necessary:
Table 4-2: Notification options
List
Action
All Users
Lists eligible users, and is obtained from Agile
Administrator; restart ChangeCAST to update the list.
Users To Notify
Users selected to receive an email in the event of an error; if
none are listed, no one is notified.
4-6
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
Figure 4-3: Agile ChangeCAST Notification Settings
You can:
❑
Use the
button to move the selected user from the All Users list to the Users
To Notify list.
❑
Use the
button to remove the selected user from the User To Notify list and add
it back to the All Users list.
❑
Shift+click or Ctrl+click to select more than one user.
Note
If users were added to Agile Administrator while ChangeCAST was
running, you can restart Agile ChangeCAST to discover new users.
Reviewing and Editing Schedule Settings
You can use the Schedule tab of the Transfer Settings dialog box to specify how often
to poll the Agile database and transfer released change orders.
To display the Schedule tab, do one of the following:
Select a profile in the ChangeCAST window and choose Schedule from the Transfer
menu. Use the Transfer Settings dialog box.
4-7
Agile ChangeCAST 2006
Figure 4-4: Agile ChangeCAST Schedule Settings
You can review the following Schedule settings and change them if necessary:
Table 4-3: Schedule Options
Setting
Action
Use Same Schedule For All
Profiles
If checked, uses the same schedule for all profiles; if not
checked, the current Schedule settings apply only to the
selected profile.
Once A Day
Automatically runs the transfer once a day at the designated
start time.
Every x Hours y Minutes
The default; specifies the time interval between transfers,
calculated from the Starting At time:
• If previous transfer processing is not finished, the next
transfer does not begin until the next scheduled time
arrives.
• The minimum time is 0 hours, 5 minutes; the maximum
time for each field is 11 hours and 59 minutes.
• The default is 1 hour, 0 minutes.
4-8
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
Table 4-3: Schedule Options
Setting
Action
Starting At
Specifies an absolute time to start checking for released
change orders:
• This option must be set.
• The default starting time is 8:00 AM.
Ending At
Specifies an absolute time to stop checking for released
change orders, for example, to stop the schedule for regular
backups or maintenance:
• The default time is 10:00 PM.
Days
Specifies the days to process change orders according to the
hourly schedule; Monday through Friday are selected by
default.
The Agile ChangeCAST Service uses the Starting At and Ending At times to
determine whether to process change orders:
❑
If the Resume button is clicked, but the current time is between the End and Start
times (down time), no change orders will be processed until the Start time is
reached.
❑
If the Pause button is clicked, then the Agile ChangeCAST Service is stopped
regardless of the schedule until it is started (Resumed).
❑
For multiple profile processing, processing proceeds profile by profile.
Note
You can use the Transfer Now command to override schedule settings and
force ChangeCAST to poll for change orders. For details, see “Forcing
Unscheduled Transfers” on page 4-15.
Connection Settings
You can use the Connection tab of the Transfer Settings dialog box to specify the
connection to the server:
To display the Connection tab, do the following:
Select a profile in the ChangeCAST window and choose Connection from the Transfer
menu. Use the Transfer Settings dialog box.
4-9
Agile ChangeCAST 2006
Figure 4-5: Agile Transfer Settings Connection Tab
Note
The Server Name, Server Port, Login Name and the Login Password are
not implemented in Agile Advantage 2006.
You can review the following Connection settings and change them if necessary:
Table 4-4: Connection Settings
Setting
Action
If connection fails, attempt to
re-connect after () minute(s)
Specifies the time required to reconnect to the server in
minutes. The default time is 3.
Number of reconnection
attempts
Specifies the number of reconnection attempts to the
server. The default time is 3.
Enabling and Disabling Profiles
By default, new profiles are disabled. When you have created or imported a profile
and verified all settings for it, you can enable it.
4-10
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
To enable a profile:
1
Select it in the Profile Library table in the upper part of the Agile ChangeCAST
window.
2
Click the Enable button.
The Transfer ECOs dialog box appears (Figure 4-6).
Figure 4-6:
The Transfer ECOs Dialog Box
3
Choose Transfer ECOs released prior to profile change(s) to transfer all change orders
with transfer flags set to Not Transferred. Choose Transfer ECOs from this point
forward to ignore all change orders released before the profile was enabled.
4
Click OK.
If settings are valid, the profile is enabled. Otherwise, an error message appears, an
entry is written to the Error log, and the profile remains disabled.
To disable a profile, select it and click the Disable button.
Note
If an FTP transfer fails, Agile ChangeCAST automatically disables the
profile and sends an email notification to all users listed in the
Notification dialog box (page 4-6). You can check the Transfer log for
details, fix the error, and enable the profile again.
Starting and Stopping Agile ChangeCAST
When Agile ChangeCAST has been properly configured, you can start it by clicking
the Resume button.
Note
For information about launching ChangeCAST and opening the Agile
ChangeCAST window, see “Starting Agile ChangeCAST” on page 1-8.
After you start Agile ChangeCAST, it runs as a service. It polls the Agile database
for newly released or implemented change orders at the scheduled polling interval.
4-11
Agile ChangeCAST 2006
Note
You can minimize the Agile ChangeCAST window by clicking the
Minimize button in the upper right corner of the window:
To restore it to its original size, click the ChangeCAST icon in the Windows
system tray.
If Agile ChangeCAST finds a released or implemented change order, it does the
following:
❑
Uses all enabled profiles to create ASCII transfer files that describe the change
order.
❑
Relays the transfer files to a specified location—either a local drive or, using
FTP, to a host ERP system. At this point, an ERP-specific application adapter
can load the information into the ERP tables.
To stop Agile ChangeCAST polling, click the Pause button. Polling for released or
implemented change orders stops and doesn’t begin again until you click the
Resume button.
Viewing and Printing Log Files
As Agile ChangeCAST runs, its activities register in log files, so you can check a
variety of information about how Agile ChangeCAST is working:
❑
TransferLog.txt, the Transfer log, documents the generation of transfer files
plus transfer attempts and successes.
❑
ErrorLog.txt, the Error log, documents condition syntax errors and other error
conditions that aren’t related to transfer files or transfer attempts.
When you click View Log, the log files appear in Windows Notepad. You can search
and perform other activities available through the Notepad menus.
To print a log file, choose Start | Programs | Accessories | Notepad (or WordPad) to open
a text editor. Then, open a ChangeCAST log file (*.log) from the directory where
ChangeCAST is installed (by default, C:\Program Files\Agile
Advantage\ChangeCAST). Finally, print the file the usual way, with File | Print.
Note
4-12
When you open a log file outside of ChangeCAST, you can print it as
usual, but text editors are not able to print when ChangeCAST launches
them automatically.
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
The Transfer Log
The ChangeCAST Transfer log file (TransferLog.txt) shows which transfer files
have been sent to the specified destination and whether their transfer was
successful. The Transfer log accumulates information; when you open it, you see
everything that occurred since you installed Agile ChangeCAST or since a
ChangeCAST user cleared the Transfer Log (with View | Clear Transfer Log). The last
several lines of the Transfer log for the selected profile appear in the Transfer Log
table of the Agile ChangeCAST window.
For a description of the Transfer Log table and its fields, see “Transfer Log Table”
on page 1-14.
To view the Transfer log, do one of the following:
❑
Click the View Log toolbar button.
❑
Click View Log in the Agile ChangeCAST window.
❑
Choose Transfer Log from the View menu.
To delete existing information in the Transfer log, choose Clear Transfer Log from the
View menu. When this option is selected, you are prompted to archive the log. If you
choose Yes, the Save As dialog appears, allowing you to enter the name of an archive
file to which the current log will be saved. The existing log is cleared. If you select
Cancel, the existing log is not archived and is cleared.
If you clear the log without archiving it, the information is not recoverable. It is
good practice to save archives and name them with the date of the archive as a
backup procedure.
The Error Log
The Agile ChangeCAST error log (ErrorLog.txt) lists errors resulting from audits
that are not related to file transfers. For example, it includes syntax expression
errors in mapping conditions.
The Error log file is used to record connection attempts and/or failures, i.e. at what
time and how many times do attempts and/or failures happen.
The Error log contains a date/time stamp followed by a narrative description of the
error.
To view the Error log, choose Error Log from the View menu.
4-13
Agile ChangeCAST 2006
To delete existing information from the Error log, choose Clear Error Log from the
View menu. When you choose this command, you are prompted to archive the log.
If you choose Yes, the Save As dialog appears, allowing you to enter the name of an
archive file to which the current log will be saved. The existing log is cleared. If you
select Cancel, the existing log is not archived and is cleared.
If you clear the log without archiving it, the information is not recoverable. It is
good practice to save archives and name them with the date of the archive as a
backup procedure.
Retransferring Change Orders
By default, Agile ChangeCAST transfers data from all Released or Implemented
change orders, along with their Affected Items and BOMs, to an ERP system. Once
data from a change order is transferred, the change order’s transfer flag is set to
“Transferred” to notify Agile ChangeCAST to skip the change order the next time
it polls the database. You can set the transfer flag manually so ChangeCAST ignores
specific change orders, or retransfers specific change orders.
To change a transfer flag setting:
1
Choose Set Transfer Flags from the Transfer menu.
The Set Transferred Flag dialog box appears (Figure 4-7).
Figure 4-7:
2
Set Transferred Flag dialog box
Enter a search condition using the fields at the top of the dialog box, and choose
Search.
4-14
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
A list appears. It includes all change orders with Released or Complete Status
Type that match the search condition.
3
Select one or more change orders from the list. You can use the Select All and
Deselect All buttons.
4
Select the appropriate Set Transferred Flag radio button. Select Transferred to stop
all selected change orders from being sent to the ERP system, or select Not
Transferred to allow selected change orders to be sent to the ERP system the next
time Agile ChangeCAST polls the Agile Advantage database.
5
Click Apply to use the selected setting.
Forcing Unscheduled Transfers
Usually, transfers are performed according to the schedule defined on the Schedule
tab. If appropriate, though, you can force Agile ChangeCAST to look for newly
released or implemented change orders and untransferred change orders
immediately, without waiting for the next polling time.
To force a transfer, choose Transfer Now from the Transfer menu, or click the Transfer
Now button in the Agile ChangeCAST window. This command is available whether
the connection state is Paused or Resumed.
Backing Up Files
Once Agile ChangeCAST is installed and operational on your server, there are
several files and folders contained within the main ChangeCAST directory that
should be backed up regularly. These files and folders contain all transfer histories,
error histories, output histories, and ERP profiles. If there is a server problem, you
will be able to recover more quickly if you have backups.
Folders:
❑
Out — contains a record of all transferred Change/Item data.
❑
Profiles — contains a record of all ERP profiles.
Files:
❑
ChangeCAST.agx — contains all available ERP profile maps.
❑
ErrorLog.txt — contains all errors logged by each profile.
❑
Services.log — contains a list of all profile transaction histories.
4-15
Agile ChangeCAST 2006
❑
TransferLog.txt — contains the full transfer history for each active profile.
Each of the files and folders listed above is updated daily and automatically by
ChangeCAST. If an Agile ChangeCAST problem occurs, Agile Support may ask for
copies of these files for review. Agile administrators should become familiar with
these files and folders and know how to access and read them.
If your company backs up the Oracle Database and Agile Advantage iFS directories
on a daily basis, these files should be included in the daily backup process.
Suggestions for Troubleshooting
Here are a few guidelines on error recovery and troubleshooting in case a transfer
failure or other error occurs. For information on backing up your Agile
ChangeCAST system and migrating legacy ChangeCAST data, see the Agile
Advantage 2006 Upgrade Guide.
Error Recovery
If a transfer fails, create a corrected change order and release it in Agile Advantage.
ChangeCAST will process the new information and send it to the application
adapter. If not all errors in the change order are corrected, the application adapter
will stop again, requiring a second correction, and so on.
Check the Transfer log and Error log described on page 4-12. If the application
adapter for the ERP system has a log file, check it as well. The next section describes
other ways to trace the source of an error.
Troubleshooting
Determining the root cause of a change order error must be done in a systematic
way. You’ll need to compare old Agile part and BOM configurations with current
part and BOM configuration in the target ERP system and the transfer file. Because
each of these components is a key factor in the successful transfer of data from Agile
Advantage to the target system, each must be considered when the processing of a
change order fails.
Consider these areas when troubleshooting:
4-16
User Guide
Chapter 4
Formatting and Transferring Agile Data Files
❑
Does the shared data of the prior revision of the part or BOM in Agile
Advantage look exactly like the current revision of the part or BOM on the
target system? Identify all differences and similarities. Identify which system is
correct, and make appropriate changes to the incorrect database to ensure that
data will be updated with the next attempt.
❑
In Agile Advantage, are there effective dates on all affected items? Take
corrective action if necessary.
❑
In Agile Advantage, are there new revisions on all affected items? Take
corrective action if necessary.
❑
In Agile Advantage, have all affected items been placed on the Affected Items tab?
Take corrective action if necessary.
❑
In Agile Advantage, are all required fields filled in? Take corrective action if
necessary. This may require the Agile administrator to make changes to ensure
that this problem does not reoccur.
❑
Does the transfer file correctly reflect any changes to parts and old versus new
BOM configurations? Check the Agile ChangeCAST profile.
❑
Does the transfer file have the correct mapping of data? Check the ChangeCAST
profile.
❑
Does Agile ChangeCAST generate the file in the correct format? Check the
ChangeCAST profile.
❑
Does the transfer file use correct conversion logic for dates, nulls, CR/LF, and
so on? Check the ChangeCAST profile.
❑
Have commands to add, modify, and delete parts or BOMs been disabled, or
has access been changed on the host system? See the target ERP system or
database administrator.
4-17
Agile ChangeCAST 2006
4-18
User Guide
A PPENDIX A
Sample AGX File
This appendix shows the contents of a small sample profile library (.AGX)
file.
Profile library (.AGX) files are text files. You can view them in Windows Notepad.
The following sample file includes one attribute and one mapping.
Caution!
Users should not edit the profile library file directly.
[AGILESESSION]
[HOSTNAME=]
[USERNAME=test]
[SHAREDSETTINGS]
[LASTCOTYPESEARCHED=All Change Orders]
[LASTCOFIELDSEARCHED=Cover Page.Number]
[LASTCOOPERATORUSED=Starts With]
[LASTCOVALUESEARCHED=b]
[PROFILENAME1=]
[OUTPUTDIR=D:\\Agile\\ChangeCAST\\Out\\]
[PROFILENAME2=]
[FILEPREFIX=]
[FILENUMBER=00003105]
[FILEEXTENSION=.AGL]
[USEFILESETTINGS=FALSE]
[USEPATHSETTINGS=FALSE]
[USESHAREDSCHEDULE=TRUE]
[PROFILE]
[NAME=DEV Profile]
[DESCRIPTION=DEV profile]
A-1
Agile ChangeCAST 2006
[NO=0]
[ENABLED=FALSE]
[LASTCHANGEORDER=]
[LASTTRANSFERFILENAME=]
[LASTTRANSFERSTATUS=]
[LASTDATETIME=]
[FILEFORMAT]
[TEXTORIENTATION=1]
[PREFIXLABEL=#]
[LAYOUTLABEL=Layout]
[DATALABEL=Data]
[TABLEHEADERS=TRUE]
[FIELDNAMES=TRUE]
[BLANKLINES=TRUE]
[EMPTYTABLES=FALSE]
[COINFO=FALSE]
[DELIMITATIONTYPE=0]
[TEXTDELIMITER=\[None\]]
[FIELDDELIMITER=,]
[LINEDELIMETER=CR/LF]
[USEDELIMETER=TRUE]
[DATEFORMAT=dd-MMM-yyyy]
[TIMEFORMAT=HH:mm:ss]
[SQLNULL=##]
[QUOTESQLNULL=FALSE]
[CONVERTCRLFINTEXT=TRUE]
[CRLFMAP=\[Space\]]
[CONVERTQUOTESINTEXT=FALSE]
[CONVERTQUOTESINTEXTMAP=0]
[REFDESIGINDIVIDUAL=TRUE]
[ONELINEPERRECORD=TRUE]
[WRAPREFDES=FALSE]
[DELTABOM=TRUE]
[OUTPUTEFFDATE=TRUE]
[EFFDATEASTEXT=FALSE]
[EFFDATETEXT=00-000-0000]
[TRANSFERSETTINGS]
[USEEXTENSION=TRUE]
[USETABLEPREFIX=FALSE]
[EXTENSION=.AGL]
[OUTPUTDIR=D:\\Agile\\ChangeCAST\\Out\\]
[PREFIX=]
[NUMBER=00003105]
[USEFTP=TRUE]
[FTPINFO]
[FTPHOSTNAME=test]
A-2
User Guide
Appendix A
Sample AGX File
[FTPUSERNAME=test]
[FTPPASSWORD=:{Eã]
[FTPTARGETPATH=//home]
[FTPPORT=21]
[FTPBINARY=FALSE]
[FTPATTEMPTS=0]
[IVAINFO]
[IVADIR=]
[CALLIVAPOSTPROCESSOR=FALSE]
[IVAPOSTPROCESSOR=]
[IVAFTPHOSTNAME=]
[IVAFTPUSERNAME=]
[IVAFTPTARGETPATH=]
[IVAFTPPORT=21]
[IVALASTFILENAME=00003104.AGL]
[SCHEDULE]
[ONCEADAY=FALSE]
[EVERYHR=1]
[EVERYMIN=0]
[STARTTIMEHRMIN=8]
[ENDTIMEHRMIN=22]
[DAY=62]
[NOTIFY]
[USER=Administrator]
[ERPINFO]
[ERPTABLE]
[TABLENAME=ag_system_items_interface]
[TABLEDESCRIPTION=ag_system_items_interface]
[TABLEALIAS=ag_system_items_interface]
[ISSPECIALTABLE=FALSE]
[SPECIALTABLENAME=]
[SPECIALTABLEID=]
[ERPATTRIBUTE]
[ATTRIBUTENAME=ITEM_NUMBER]
[ATTRIBUTEDESCRIPTION=Item Number]
[ATTRIBUTELENGTH=40]
[ATTRIBUTETYPE=Text]
[ISSPECIALATTRIBUTE=FALSE]
[ISMAPPED=TRUE]
[MAPPINGINFO]
[MAPPING]
[ISFLAG=FALSE]
[ISCONDITIONAL=FALSE]
[AGILEOBJECTNAME=Marketing Part]
[AGILEPAGENAME=General Item Attributes]
[AGILEATTRIBUTENAME=Part Number]
A-3
Agile ChangeCAST 2006
[AGILEOBJECTID=10000:20095]
[AGILEPAGEID=0]
[AGILEATTRIBUTEID=1001]
[MAPPINGID=10000:20095.0.1001]
[EXPRESSION=Marketing Part.General Item
Attributes.Mahi Part Number]
[TARGET]
[TARGETTABLE=ag_system_items_interface]
[TARGETFIELD=ITEM_NUMBER]
[NO=0]
[TARGET=ag_system_items_interface.ITEM_NUMBER]
A-4
User Guide
I NDEX
Symbols
.aga files 1-3
.agc files 1-3
.agl files 1-3, 4-3
.agx files 1-3
.map files 1-3
A
Add Profile button 1-11
adding attributes 3-5
adding profiles 2-2
Agile Tables report 3-17
appending attributes 3-6
application adapters 1-4
archive directory 4-5
attribute files 1-3, 3-3
editing 3-5
exporting 3-6
importing (appending) 3-6
attributes
adding 3-5
appending 3-6
deleting 3-6
exporting 3-6
importing 3-6
modifying 3-5
verifying 3-7
Attributes report 3-17
Attributes Table dialog box 3-3
Audit
button 1-12
Error log 4-13
log 1-12
syntax errors 3-14
B
backing up files 4-15
BOM row settings
8.1 vs. previous releases 3-8
buttons
Add Profile 1-11
Audit 1-12
Field Mapping 1-11
File Format 1-11
Insert Field 3-14
Insert Function 3-14
Pause 1-14
Resume 1-14
Test 3-14
Transfer Options 1-11
View Log File 1-11
C
change analyst 1-7
change orders
retransferring with ChangeCAST 4-14
unreleased (warning) 1-8
ChangeCAST
architecture drawing 1-4
attributes 3-3
components 1-2
definitions 1-1
file types 1-3
installation 1-6
launching 1-8
logging in 1-9
main window 1-10
menu bar 1-11
overview 1-4
profiles 1-4, 2-1
retransferring change orders 4-14
setting up 1-6
starting 1-14
Index-1
Agile ChangeCAST Advantage 2006
starting and stopping 4-11
status bar 1-15
stopping 1-14
title bar 1-11
ChangeCAST reports 3-17
ChangeCAST transfers
log 4-13
retransferring 4-14
unscheduled 4-15
ChangeCAST.agx 1-4, 1-10, 2-2, 2-7, 3-2
ChangeCAST.exe 1-2
ChangeCAST81.agx 1-12
components 1-2
concepts 1-1
condition formulas 3-14
conditions, specifying 3-12
copying profiles 2-6
creating field mappings 3-11
creating profiles 2-2
D
data migration 1-6
defining attributes 3-3
definitions 1-1
deleting attributes 3-6
deleting profiles 2-7
disabling profiles 4-10
documents
differentiating from parts 3-2
E
e-mail error notification 4-6
Enable differentiation between Agile
classes 3-2
enabling profiles 4-10
ERP system attributes 3-3
error handling 4-6
Error log 4-13
error recovery 4-16
exporting
attributes 3-6
field mappings 3-15
Index-2
F
failure notification 4-6
Field Mapping button 1-11
field mappings 3-7
creating 3-11
creating and modifying 3-7
exporting 3-15
importing 3-15
Field Mappings dialog box 3-9
File Format button 1-11
File Format dialog box 4-3
files
attribute 3-3
ChangeCAST 1-3
transfer 4-3
formatting transfer files 4-3
formulas, condition 3-14
G
guidelines
field mappings 3-7
setting up ChangeCAST 1-6
I
importing
attributes 3-6
field mappings 3-15
profiles 2-2
Insert Field button 3-14
Insert Function button 3-14
installation 1-6
installing ChangeCAST 1-6
Integration Developer’s Guide
when needed 4-4
L
launching ChangeCAST 1-8
log files 4-12
Error 4-13
Transfer 4-13
logging in as a different user 1-9
logging into ChangeCAST 1-9
User Guide
Index
M
Manufacturer Parts 3-8
Manufacturers data 3-8
Map Condition button 3-12
Map Condition dialog box 3-13
map conditions, specifying 3-12
map conditions, testing 3-14
Map To Null button 3-11
Mapped Fields table 3-10, 3-16
mapped fields, reordering 3-16
mapping
differentiating ECOs and MCOs 3-2
differentiating parts and documents
3-2
mapping Agile and ERP fields 3-7
mapping files 1-3
mappings
creating 3-11
exporting 3-15
guidelines 3-7
importing 3-15
Mappings report 3-17
MCOs
differentiating from ECOs 3-2
menu bar, ChangeCAST 1-11
migrating data 1-6
modifying attributes 3-5
MPN 3-8
N
notification settings 4-6
null, mapping to 3-11
O
Out folder 4-15
outgoing directory 4-5
overview
ChangeCAST 1-4
P
Page Three fields 1-7
Parts 3-8
Pause button 1-14
printing
log files 4-12
reports 3-18
privileges 1-7
profile library 1-4
Profile Library table 1-12
Profile reports 3-17
profiles 1-3, 1-4
adding and importing 2-2
copying 2-6
deleting 2-7
disabling 4-10
enabling 4-10
introducing 2-1
mapping fields 3-7
renaming 2-6
Profiles folder 4-15
R
removing profiles 2-7
renaming profiles 2-6
reordering
mapped fields 3-16
tables 3-16
reports
Agile Tables 3-17
Current Profile and All Profiles 3-17
printing 3-18
producing 3-17
resetting transfer flags 4-14
Resume button 1-14
S
setting the transfer flag 4-14
setting up ChangeCAST 1-6
Settings report 3-17
specifying map conditions 3-12
StartChangeCAST.exe 1-2
starting ChangeCAST 1-14, 4-11
status
of transfer 4-13
status bar, ChangeCAST 1-15
stopping ChangeCAST 1-14, 4-11
Index-3
Agile ChangeCAST Advantage 2006
system maintenance
backing up files 4-15
T
tables, reordering 3-16
Test button 3-14
toolbar buttons 1-11
transfer files 1-3, 4-3
transfer flags 1-2, 4-14
Transfer log 4-13
Transfer Now command 4-15
Transfer Options button 1-11
Transfer Options report 3-17
transfer settings
notification 4-6
transfer status 4-13
transfers
immediate or "on demand" 4-15
troubleshooting 4-16
U
unreleased change orders (warning) 1-8
V
verifying attributes 3-7
View Log File button 1-11
viewing log files 4-12
W
window, ChangeCAST 1-10
Index-4
User Guide
Download PDF
Similar pages