Business objects MOVER ID 5.0 NCOA LINK User Manual

Page 1
Mover ID User’s Guide for NCOA
Link®
Mover ID 5.0
November 2008
Page 2
Contact information Find contact information on the Web at http://service.sap.com.
USPS information Business Objects is a non-exclusive Interface Distributor Licensee of the United
States Postal Service. The following trademarks are owned by the United States Postal Service: USPS, CASS, Standard Mail, First-Class Mail, DPV, LACSLink, NCOALink, and United States Postal Services.
2
Mover ID User’s Guide
Page 3
Contents
Preface.............................................................................................................5
Documentation.................................................................................................6
Chapter 1:
Overview........................................................................................................ 7
Overview of Mover ID ....................................................................................8
Attempted — not known: ANKLink.............................................................10
What to expect from the USPS and from Business Objects..........................11
Security requirements....................................................................................12
Get started with NCOALink..........................................................................13
Chapter 2:
Move-updating in ACE .............................................................................. 15
Install the NCOALink directories and files...................................................16
Prepare for NCOALink processing................................................................19
Enable NCOALink processing......................................................................21
Specify the locations of NCOALink files......................................................22
Enter customer and USPS licensee information............................................23
Set up NCOALink processing.......................................................................26
Enter NCOALink service provider information............................................30
Enter Processing Acknowledgement Form (PAF) information.....................32
Enter contact information for the broker or list administrator....................... 34
Memory usage ...............................................................................................36
Automatically replace old address with new.................................................42
False-positive log file ..................................................................... ...............43
Unlocking DPV .............................................................................................44
Move-update output fields.............................................................................45
Strategies for your ACE output file...............................................................47
ACE Library functions ..................................................................................49
Chapter 3:
Reports and log files................................................................................... 51
Mover ID Summary report ............................................................................52
NCOALink log files ......................................................................................58
Chapter 4:
Certification and audits.............................................................................. 67
NCOALink certification and audits...............................................................68
Appendix A:
Improving NCOALink performance.........................................................69
What hardware and OS are best for NCOALink processing?....................... 70
What caching and data format strategy is best?.............................................72
Tips ................................................................................................................74
Are there any special strategies that might help? ..........................................76
Index..............................................................................................................77
Contents
3
Page 4
4
Mover ID User’s Guide
Page 5

Preface

About this manual This manual describes ACE’s Mover ID option, which lets you move- update yo ur

data using the USPS NCOA
Link®
system. It is written for NCOA
Link
users (full service providers and limited service providers) who use ACE’s Mover ID solution. This manual does not cover everything you need to know to operate the
Link
NCOA NCOA

Conventions This document adh eres to the following docum entation conventions:

Convention Description
Bold
Italics
> in menu commands
!
system. You will need a copy of USPS publications describing
Link
.
Highlights file names, paths, and text that you should type exactly as shown. For example, “Type
Both emphasizes text and indicates text for which you should substi­tute your own data or valu es. F or e xam ple , “Type a name for your file,
.txt
and the Indicates commands that you choose from menus in the following for-
mat: Menu Name > Command Name. For example, “Choose File > New.”
Alerts you to important information and potential problems.
extension (
testfile
cd\dirs
.txt
).”
.”
Points out special cases that you should know about.
Draws your attention to tips that may be useful to you.
Preface
5
Page 6

Documentation

Complete documentation set

Access the latest documentation

Your complete ACE documentation set includes th e following:
ACE User’s Guid e ACE Job-File Reference (if you use ACE Job) ACE Library Reference (if you use ACE Library) Mover ID User’s Guide (if you purchased the Mover ID add-on option) Quick Reference for Views and Job-File Products (if you use ACE Views or
Job)
Other documents that you may need to reference are located on the SAP Service Marketplace (SMP) under Data Quality:
Quick Reference for Library Products (if you use ACE Library) System Administrator’s Guide Edjob User’s Guide Database Prep Views Quick Start Guide (if you use ACE Views)
You can access product documentation in several places:
On your computer. User’s Guides and other manuals for each product that
you have installed are available in the Documentation folder. Choose Start > Programs > Business Objects Applications > Documentation.
On the SAP Corporate Portal. Go to http://help.sap.com/ to access all the
latest product docume ntation. Follow this link, selec t the Business Objects tab, select Data Quality from the All Product s drop list, and choose ACE from the All Releases drop list.
6
Mover ID User’s Guide
Page 7
Chapter 1: Overview
What is move­updating?

Move-update with ACE’s Mover ID option

Chapter summary This chapter contains an overview of how ACE works with NCOA
“Move-updating” means checking a mailing list against the National Change of Address database to make sure your data is updat ed with cur rent ad dresses. Wh en you perform move updating, you update your records for people or businesses that have moved and have filed a Change of Address form with the United States Postal Service (USPS).
Move updating is required by the USPS on all presorted First Class mail.
To help mailing-list managers meet this requirement, the USPS offers the Mover ID for NCOA ID provides support for NCOA Remote Views, and ACE RAPID.
You can also use ANK
Link
ANK available.
You will also find an overview of what to expect from the USPS and Business Objects on issues such as security, technical support, and performance.
Link
, a system that includes move-updat ed data in dire ctories. Mover
Link
to update address data with the most current address information
Link
in ACE Job, ACE Views, ACE Library, ACE
(attempted not known) with NCOA
Link
.
Link
and
Chapter 1: Overview
7
Page 8

Overview of Mover ID

Move-update with NCOA
How ACE works with NCOA
Link
Link
The U.S. Postal Service requires move-updating on all First Class presorted mailings. To help mailers meet this requirement, the U SP S o ffers cert ain options, including NCOA
By using NCOA database with the latest move data, using a one-pass process. With NCOA
Link
.
Link
through ACE, you’re updating the addresses in your
Link
,
you can:
Improve mail deliverability. Reduce the cost and time needed to forward mail. Meet the USPS move-updating requirement for presorted First Class mail. Prepare for the possible expansion of move-update requirements.
The ACE Mover ID option supports NCOA
Link
. Mover ID is a for-sale option for
ACE Job, ACE Views, ACE Library, ACE RAPID, and ACE Remote Views. This is how Mover ID fits into ACE processing:
8
Mover ID User’s Guide
Page 9
The following diagram shows how move updating fits into ACE processing.
1. ACE performs its normal p rocessing on the addr ess data. You cannot perform
Mover ID processing without the usual ACE processing. NCOA
Link
requires
parsed, standardized address data as input.
Link
2. The software searches the NCOA
database for a record that matches your
parsed, standardized record.
3. ACE receives the move information, including the new address, if one is
available.
Link
4. ACE looks up the move record that comes back from the NCOA
database, to assign postal and other codes.
5. At your option, ACE can either retain the old address and append the new, or
replace the old address with the new.
6. ACE produces the reports and log files that you will need for USPS
compliance. The number of move-updated records also appears in the Job Summary report and in stati stics files.
Chapter 1: Overview
9
Page 10
Attempted — not known: ANK
Link
ANK move-updating solution
is part of the
Undeliverable-as-addressed mail costs the mailing industry and the USPS a lot of money each year. ACE provides NCOA problem. With ACE’s NCOA data.“ANK” stands for “Attempted — Not Known.”
Note: If you are an NCOA
Link
ANK
option to access ANK
Link
Link
Link
option, you have ac cess to the USPS’s ANK
Link
full service provider, you do not need ACE’s
as an additional solution to this
Link
data.
Link

The importance of move-updating

ANK
Link
is for NCOA
Link
end users and limited service providers
More than 40 million people and businesses move every year. To keep accurate address information for you r contact s, you must use a USPS method for recei ving your contacts’ new addresses. Not only is move-updating good business, it is required for all First-Class mailers who claim presorted or automation rates. As the USPS expands move-updating requirements and more strictly enforces the existing regulations, move updating will become increasingly important.
Normally NCOA
Link
end users and limited service providers have access to 18 months of move-update data. Users gain access to 30 additional months of move data — the ANK
Link
data by using the ANK
Link
data.
Note: These additional 30 months of data tell only that a move occurred and the date of the move. The new address is not provided.
Link
ANK
helps you make informed choices regarding a contact. If the data indicates that the customer has moved, then you can choose one of the following courses of action:
Suppress that contact from the list. Try to acquire the new address from an NCOA
Link
If you are an NCOA
full service provider, you do not need to us e the ANK
Link
full service provider.
option because you already have complete access to the full 48 months of move data (including the new addresses).
Link
Link
ANK
is a for-sale
option
Link
ANK
data ANK
Automatic ANK detection
10
Mover ID User’s Guide
Link
ACE’s ANK
Link
is a for-sale option. In order to purchase the ANK
must already own the Mover ID for NCOA
Link
option, at the end user or limited
Link
option, you
service provider level. If you’d like information about acquiring this option, contact your Business
Objects’ customer support representative.
Link
is a subset of NCOA
Link
. You can request ANK
Link
data from the USPS National Customer Support Center (NCSC) by calling 1-800-589-5766 or e­mailing ncoalink@usps.gov
. ANK
Link
data is not available from Business
Objects.
ACE detects if you’re using ANK whether you’re using ANK
Link
in ACE.
Link
data. There’s no need for you to specify
Page 11

What to expect from the USPS and from Business Objects

Move updating is a business decision for you to make

Security is your responsibility

Your move-updating system (NCOA
Link
), and the license requirements that go with it, have created a new dimension in the relationship among mailers, the USPS, and vendors. It’s important to be clear about what to expect from everyone.
The Mover ID option offers an option to replace a person’s old address with their new one. You will decide whether you will accept move upda tes r el ate d to f ami ly moves, or only individual moves. The USPS recommends that you make these choices only after careful thought about your customer relationships. Con sider the following examples:
If you are mailing checks, account statements, or other correspondence for
which you have a fiduciary responsibility, then move-updating is a serious undertaking. The USPS recommends that you verify each move by sending a double postcard, or other easy-reply pi ece, before cha nging a fina ncial rec ord to the new address.
If your business relationship is with one spouse and not the other, then move
updating must be handled carefully with respect to divorce or separation. Again, it may make sense for you to take the extra time and expense of confirming each move before permanently updating the record.
The USPS is extremely concerned about preventing any improper use of
Link
NCOA
data. From the USPS, you can learn their rules on security, access control, permitted and forbid den uses of move data, and so on . For detai ls, see t he Privacy Act of 1974, Title 39.

USPS responsibility for support

When you acquire an NCOA USPS product. The NCOA
Link
license from the USPS, you are licensing a
Link
database is developed and maintained by the USPS. Therefore, contact the USPS National Customer Support Center in Memphis at 800-589-5766 as your first line of support for NCOA problems with the NCOA

Performance In our tests, ACE runs slower with Mover ID on than with it off. Your processing

Link
system.
Link
issues or
speed depends on the computer running ACE and the percentage of input records affected by a move (more moves, slower performance).
See also “Improving NCOALink performance” on page 69.
Chapter 1: Overview
11
Page 12

Security requirements

Because of the sensitivity and confidentiality of change-of-address data, the USPS imposes strict security procedures on software vendors and users.

100 unique names and addresses

The USPS requires that your input data have a minimum of 100 unique records. ACE Job, Views, Remote Views, and RAPID checks your input file for uniqueness. These checks make verification take longer, but they are required by the USPS.
ACE Library. If you are using ACE Library, you must ensure that the 100­record requirement is met. You must also obtain a waiver from the USPS
Link
before you can purchase ACE Library’s NCOA

Password protection The USPS requires that the machine that the software and NCOA

functionality.
are installed on be password-protected.
Link
directories
12
Mover ID User’s Guide
Page 13
Get started with NCOA
Link

How to get started You’ll find all the information you need on the USPS RIBBS website. More

specifically, find the “NCOA
Link
Information Document” for an introduction. The
“End User Certification Procedures” and the “Service Provider Certification
Link
Procedures” tell you exactly what you need to do to become NCOA To access these documents, go to the RIBBS site (http://ribbs.usps.gov/
Link
NCOA
on the left side of the pa ge, and then scroll down the right side of the
-certified.
), click
page to find the documents that correspond to your provider type (end user, full service provider, or limited service provider).
Steps to becoming NCOA
Link
-certified
Before you can perform NCOA steps. These steps are described more fully in the “End User Certification
Link
processing , you must complete the foll owing
Procedures” and the “Service Provider Certification Procedures” documents.
Link
1. Complete the USPS’s NCOA
application and other required forms. After you complete the appl icati on and forms, t he USPS gives you an a uthor izat ion code, which you’ll need in step 2.
2. Purchase the Business Objects Mover ID option. For details, contact your Business Objects’ customer support representative. You must report your authorization code to Business Objects (see step 1) and state at what level you’re certifying (end user, limited service provider, or full service provider).
Link
3. Perform the NCOA
certification test using ACE’s easy test job template.
Coordinate with the USPS to process their test file. See Chapter 4 for details.
Link
4. Complete the USPS’s NCOA pay the USPS for NCOA
Link
license agreement. At this point, you also
.
Completing Step 3 of NCOA
Hash or flat file format The USPS offers NCOA
Link
application
As you complete the NCOA for the Step 3 form.
Link
application, you need to consider several items
Link
data in hash files or flat files. ACE can access either format. On the Step 3 form, you indicate whether you’d like to receive hash files, flat files, or both. For help determining which file format may be best for you, see “Improving NCOALink performance” on page 69.
Versions Be sure to indicate the correct product names and versions, as shown below.
The Step 3 form asks for your ... You enter ...
Link
NCOA NCOA
Software Product Name Mover ID.
Link
Software Product Version The latest version of Mover ID that you
have received. If you’re not sure what ver­sion that is, see “Fin din g v e rs ion nu mb ers” on page 14.
Address Matching ZIP+4 Product Name ACE.
Chapter 1: Overview
13
Page 14
The Step 3 form asks for your ... You enter ...
Address Matching ZIP+4 Product Version The latest CASS-certified version of ACE
that you have received. If you’re not sure what version that is, see “Finding version
numbers” on page 14. Delivery Point Validation Product Name ACE. Delivery Point Validation Product Version The latest CASS-certified version of ACE
that you have received. If you’re not sure
what version that is, see “Finding version
numbers” on page 14.
Finding version numbers You can see the versions of ACE, CASS-certified ACE, and Mover ID in the
following ways:
Release notes. With each ACE release, t he releas e notes lis t the ACE, CASS,
and Mover ID version numbers.
Command line options. Use the command line option pwace /rev or
pwace -rev to see what your installed versions are. Or use the command line
option pwace /lib or pwace -lib to see the installed versions for several of underlying ACE components.
Help menu. In ACE Views, choose Help > About ACE Views to see what
your installed versions are. Choose Help > Library Version to see the installed versions of the underlying components that make up ACE.
Library function. In ACE Library, call ace_get_revision to see what your
installed versions are.
Mover ID Summary. In the Mover ID Summary report header, you can see
the ACE version and the Mover ID version that you used when processing your Mover ID job.
CASS 3553 report. The CASS report shows the version of ACE that was
most recently CASS-certified.
14
Mover ID User’s Guide
Page 15
Chapter 2: Move-updating in ACE
Chapter summary This chapter walks you through the steps you’ll take in ACE to set up move-
updating with NCOA
Link
.
Chapter 2: Move -u pd a ting in AC E
15
Page 16
Install the NCOA
Link
directories and files
Hardware recommendations for NCOA
About the NCOA
Link
Link
directories
Install the NCOA
Link
directories
When move-updating with NCOA
At least 60 GB of available disk space. DVD drive. Sufficient RAM. See “Improving NCOALink performance” on page 69.
After you’ve purchased NCOA test, the USPS sends you the latest NCOA
Link
, you will need:
Link
from the USPS and passed their certification
Link
directories every month (if you’re
an end user) or every week (if you’re a limited or full service provider).
Link
The USPS requires that you use the latest NCOA you. Note that NCOA
Link
directories expire within 45 days.
Remember that unlike other directori es that you use with ACE, the NCOA directories are not provided by Business Objects. The NCOA
directories that they send to
Link
Link
directories
come straight from the USPS.
Before you can use the NCOA
Link
directories, which the USPS provid es to you on DVD, you must install them to your hard disk. The USPS recommends that you have 60 GB of free disk space.
Link
You can install the NCOA
directories using a GUI (graphical user interface)
utility, or you can install from the command line.
Install with the GUI utility 1. Insert the NCOA
2. Run the DVD installer, located at pw\ncoalink\ncoadvdver.exe or postware/
ncoalink/ncoadvdver.
For further installation details, see the online help available within the installation program (choose Help > Contents).
Link
directories DVD into your DVD drive.
16
Mover ID User’s Guide
Page 17
Install from the command line
Command-line option Description
Windows UNIX
You can use the ncoadvdver command with the following command-li ne o pt ion s to automate the installation process.
-c Run selected processes in console mode (do not use the graphical user interface)
/p:t -p:t Perform transfer. When using this option, you must also:
specify the DVD location wi th /d or -d
specify the transfer location with /t or -t
/p:u -p:u Perform unpack. When using this option, you must also:
specify the DVD location wi th /d or -d
specify the transfer location with /t or -t
/p:v -p:v Perform verification. When using this option, you must also:
specify the transfer location with /t or -t
/d -d Specify DVD location. /t -t Specify transfer location. /nos -nos Do not stop on error. (Return failure code as exit status.) /a -a Answer all warning messages with Yes.
You can combine “p” options. For example, if you want to trans­fer, unpack, and ver­ify all in the same process, enter or
-p:tuv
/p:tuv
.
After performing the “p” option specified, the program will close.
Windows example Your command line may look something like this:
ncoadvdver /p:tuv /d D:\ /t C:\pw\dirs\ncoa
UNIX example Your command line may look something like this:
ncoadvdver [-c] [-a] [-nos] [-p:(t|u|v)] [-d <path>] [-t <path>]
Install the NCOA daily delete file
Link
If you are a service provider, then every day when you perform NCOA processing, you must download the daily delete file and install it in the same directory where your NCOA
Link
directories are located.
The daily delete file contains records that are pending deletion from the
Link
NCOA
data. For example, if Jane Doe filed a change of address with the
USPS and the n didn’t move, Jane’s record would be in the daily delete file. Because the COA is stored in the NCOA
Link
directories, and they are updated
only weekly or monthly, the daily delete file is needed in th e interim, until the
Link
NCOA
directories are updated again.
If you are an end user , yo u only nee d the dai ly del ete fil e for processi ng S tage I or II files.
Link
Chapter 2: Move -u pd a ting in AC E
17
Page 18
Important points to know about the daily delete file
ACE will fail verification when NCOA
performed, and th e daily delete file isn’t installed.
ACE supports only the ASCII version of the daily delete file.Do not rename the daily delete file. It must be named dailydel.dat.ACE will issue a verification war ning if the daily delete file is more than
three days old.
Install the daily delete file To download and install this file:
Link
is enabled, a stage test is being
1. Go to http://ribbs.usps.gov/
Link
2. Click NCOA
on the left side of the page.
.
3. Click the dailydel.dat file link on the right side of the page.
4. When prompted, save the file to the same location where your NCOA
directories are stored.
Link
18
Mover ID User’s Guide
Page 19
Prepare for NCOA
Link
processing

How ACE finds move data

During NCOA addresses in the NCOA
Link
processing, ACE compares your standardized addresses with
Link
database. ACE looks for matching addresses to
determine if any move data is available for your records. If move data exists for a particular address, then ACE checks for a match of the
business, individual, o r fami ly na me, de pendin g on the “mat ch logi c” you choose. For details about match logic, see “Set up NCOALink processing” on page 26.
ACE will process only assigned records through NCOA doesn't have name or firm information, it will not be processed through
Link
NCOA

Data format T o compare your dat a with NCOA

.
of the following formats:
Discrete name fields (the first name is its own fie ld , last name is in its own
field, and so on). Use discrete name fields for the best matching results.
Name-line field (the person’s full name is in a single field). Use name-line
field for the next best matching results. Note: Name data should be in the First Middle Last name format (for example, John James Donaldson). If name data is in any other format (for example, Last First Middle), parse the data using DataRight IQ to get name components into the desired format before you perform NCOA
Link
processing.
Link
. Also, if a record
Link
data, ACE requires that your data be i n one
How ACE treats name­line data

How ACE treats multiline data?

Multiline fields (data is in an open format). Multiline fields will not yield the
best matching results. To achieve better matching results, first pars e your data using DataRight IQ.
ACE tries to match the data in the name-line field as either name or firm information. If you also have a discrete firm field that is populated, then ACE assumes that the name-line field contains name data.
When you use multiline data, ACE identifies the address information first. Then ACE examines the two line s of data before the address. ACE at te mpts to determine which line contains name information and treats the remaining line as firm data. If neither or both lines are identified as the na m e, ACE treats the first line as name and the second as firm. ACE then parses the name information and passes the parsed names and the firm data into NCOA
Link
to try to find a match.
Remember that using multiline data is not ideal. To achieve the best matching results, use discrete components.
Chapter 2: Move -u pd a ting in AC E
19
Page 20

Matching on name data

ACE Vie ws and job users: If you plan to match on people’s names, include either discrete name fields, t he name-line field, or multilin e fields in your DEF file. See the Database Pr ep manual for more information about setting up DEF files.
ACE Library users: If you plan to match on people’s names, you must define either discrete name components, the name-line component, or multiline components.
Discrete name components Name-line components Multiline components
In ACE Views or job:
PW.Pre_Name PW.First_Name PW.Mid_Name PW.Last_Name PW.Post_Name

Matching on business name data

In ACE Library:
ACE_IPre_Name ACE_IFirst_Name ACE_IMid_Name ACE_ILast_Name ACE_IPost_Name
ACE Views or job users: If you plan to match on business names, then ideally you would include the firm component (PW.Firm) in your DEF file, though you
In ACE Views or job:
PW.Name_Line
In ACE Library:
INAME
ACE_
In ACE Views or job:
PW.Line1-12
may also use name-line or multiline fields. See the Database Prep manual for more information about setting up DEF files.
ACE Library users: If you plan to match on business names, then ideally you would define the firm component (ACE_IFirm), though you may also use name­line or multiline components.
Discrete name components Name-line components Multiline components
In ACE Views or job:
PW.Firm
In ACE Library:
ACE_IFirm
In ACE Views or job:
PW.Name_Line
In ACE Library:
ACE_INAME
In ACE Views or job:
PW.Line1-12
In ACE Library:
ACE_ILINE1-12
In ACE Library:
ACE_ILINE1-12
20
Mover ID User’s Guide
Page 21
Enable NCOA
Link
processing
Enable NCOA processing in ACE Views or job file

Enable NCOALink processing in ACE Library

Link
To set up ACE so that it can perform NC OA
Link
processing, follow these steps:
1. Access the ACE Execution Options window (Views) or the Execution block (job file).
2. Turn on the Perform Mover ID NCOALink option.
By default, the Perform Mover ID NCOALink option is set to N, or not selected, meaning that ACE will not perform Mover ID processing.
To control NCOA new mode type
Option Setting
ACE_MODE_ENABLE_MOVER_ID
Link
processing in ACE Library, call ace_set_mode() with the
ACE_MODE_ENABLE_MOVER_ID
Set this to
Link
NCOA Set this to
processing. This is the default setting.
:
ACE_MID_NCOALINK
processing.
ACE_MID_OFF
to turn off NCOA
to enable
Link
Always call ace_set_mode() after calling ace_init_addr() and before calling ace_open().

Enable reports When you perform NCOA

ID Summary report. V iews and Jo b-File users, be sure to select the Create Reports option (or set it to Yes). If you’re using ACE Library, see Chapter 3 for details about creating this report.
Link
processing, you are required to gen erate the Mover
Chapter 2: Move -u pd a ting in AC E
21
Page 22
Specify the locations of NCOA
Link
files

Specify the locations in ACE Views or job file

Specify the locations in ACE Library

NCOA
Link
processin g requires t he NCOA
Link
directory from the USPS and several additional supporting files that help ACE parse names, if necessary. You must specify the locations of these files so that ACE can access them while processing your files.
1. Access the Auxiliary Files window or block.
2. Specify the files’ locations in the NCOALink Directory and Name Parsing
Files options. Use the same path that you used du ring in stalla tion. By def ault, they’re installed to pw\ncoalink. You enter only the paths here. Don’t enter the file names.
In ACE Views, you can specify the locations of these files in the ACE Defaults window in the Auxiliary Files tab.
You specify the files’ locations by calling ace_set_file() with the following values:
Use ACE_DIR_NCOALINK to specify the path to the NCOAUse ACE_DIR_NCOALINK_SUPPORT to specify the path to the Name
Link
directory.
Parsing files.

Supporting files The list below shows the supporting files, which Business Objects creates,

maintains, and provides to you:
acenpe.dat
acenpr.dat
acenpu.dat
pwcap.dct
acenp.so
(on all UNIX
acenpp.dat
acenps.dat
parsing.dct
acenp.dll
acenp.sl
(on Windows)
(on HP)
platforms except HP)
22
Mover ID User’s Guide
Page 23

Enter customer and USPS licensee information

Required information When you perform NCOA

the company performing NCOA for whom they are performing NCOA performing the processing for yourself, you are the licensee and the customer.
The required information is used in The USPS False Positive Log, which is required when you run ACE with DPV and/or LACS all licensee types: Limited Service Providers, Full Service Providers, and End Users.
ACE Views and Job-File Enter the NCOA
Link
information in the Customer & USPS Licensee Information block.This block is required for all end users, limited service providers, and full service providers performing NCOA
2
DSF
, or DPV processing).
Link
All NCOA
providers and end users must include the following required
information: Customer Company Name (to 50 chars).. =
Customer Address (to 50 chars)....... =
Customer City (to 28 chars).......... =
Customer State (2 chars)............. =
Customer ZIP (5 chars)............... =
Customer ZIP+4 (4 chars)............. =
Customer Phone (10 chars)............ =
Log File Directory (path only)....... =
Link
processing, you must provide information about
Link
processing (the licensee) and the company
Link
processing (the customer). If you’re
Link
enabled. This applies to
Link
processing (and Suite
Link
, LACS
Link
,
If one of these fields is not set, ACE issues an error telling you that the blank paramete r is re quired.
ACE Library To specify customer and licensee information, use the ace_mvid_set_info() or
ace_set_mailer_info() function with the values specified below:
ACE_MAILER_CUST_CO ACE_MAILER_CUST_ADDRESS ACE_MAILER_CUST_CITY ACE_MAILER_CUST_STATE ACE_MAILER_CUST_ZIP ACE_MAILER_CUST_ZIP4 ACE_ MAILER_LOG_FILE_PATH
NCOA
Link
PAF ID The NCOA
Link
PAF ID is an identification scheme consisting of four sub-parts:
1. Platform ID from the USPS (4 characters)
2. List Owner NAICS (6 characters)
3. List Processing Frequency (2 characters)
4. Customer/List ID (6 characters)
Chapter 2: Move -u pd a ting in AC E
23
Page 24
Customer & USPS
Use these options to enter your customer and licensee information.
licensee Information options
Views or job option Library option ID Length Description
Link
NCOA
Platform ID
Licensee Name
ACE_MID_LIC_ID ACE_MAILER_LIC_NAME
4 30
The licensee performs NCOA The Platform ID is the NCOA
identification number, assigned by the USPS.
Use ace_mvid_set_info() with ACE_MID_LIC_ID.
Use ace_set_mailer_info() with ACE_MAILER_LIC_NAME.
It’s exactly four characters long. The licensee name is the name of the NCOA
licensee, up to 30 characters. This information will appear in the PAF log and
Mover ID Summary (see Chapter 3). The platform ID and licensee name are available
on the license agreement from the USPS.
Link
processing.
Link
licensee’s
Link
List Owner NAICS ACE_MAILER_LIST_OWNER_S
IC
Use ace_set_mailer_info().
IMB Mailer ID ACE_MAILER_IMB_ID
Use ace_set_mailer_info().
Customer/List ID
Customer Company Name Customer Address Customer City Customer State Customer ZIP Customer ZIP4 Customer Phone
ACE_MAILER_LIST_OWNER_ID
Use ace_set_mailer_info().
ACE_MAILER_CUST_CO ACE_MAILER_CUST_ADDRESS ACE_MAILER_CUST_CITY ACE_MAILER_CUST_STATE ACE_MAILER_CUST_ZIP ACE_MAILER_CUST_ZIP4 ACE_MAILER_CUST_PHONE
6 Enter the North American Industry Classifica-
tion System (NAICS), which identifies what business the list owner engages in. For more information, see
http://www.census.gov/epcd/www/naics.html
.
6 or 9 The IMB Mailer ID is a unique 6-digit or 9-digit
numeric code assigned to mailers by the USPS based on their annual mail volumes. This num­ber is included in the NCOA
Link
PAF
(Process-
ing Acknowledgement Form).
6 or 8 Customer/List ID is a unique ID assigned by the
licensee to identify the list owner (customer). If the licensee does not have a naming scheme
in place for customer/lists, the 6 digits could be made up of:
First 3 digits: Customer name/identifier
Last 3 digits: List name/identifier
The Customer/List ID is required for all pro­vider types.
50 50 28 2 5 4
The customer is the person or company for whom you are performing NCOA
Link
process-
ing. Enter the customer’s address and telephone. The customer information appears in the Mo ver
ID Summary and log files (see Chapter 3).
10
Processing Frequency
24
Mover ID User’s Guide
Use ace_set_mailer_info().
ACE_MAILER_PROC_FREQ
Use ace_set_mailer_info().
2 This 2-digit number (from 1 to 52) indicates
how many times per year the list is processed with NCOA
If the list owner has other lists processed by the NCOA enter
Link
.
Link
licensee at different frequencies,
99
.
Page 25
Views or job option Library option ID Length Description
Date List Received
ACE_MAILER_DATE_RECEIVED
n/a Enter the date when the NCOA
received the list. Use the yyyy/mm/dd format.
Use ace_set_mailer_info().
If you’re an end user, you may leave this blank.
Link
licensee
List Return Date
Log File Directory
ACE_MAILER_DATE_RETURNED
Use ace_set_mailer_info().
ACE_MAILER_LOG_FILE_PATH
Use ace_set_mailer_info().
n/a Enter the date when the list will be returned to
the customer. Use the yyyy/mm/dd format. If you’re an end user, you may leave this blank.
n/a Indicate where the NCOA
Link
log files should be produced. ACE determin es the file names during processing, as the USPS requires. This directory must exist and must be writable.
It’s very important that you use the same path for all jobs. If you have multiple clients, use the same log file directory for all clients so that the log files are combined.
Chapter 2: Move -u pd a ting in AC E
25
Page 26
Set up NCOA
Link
processing

Required information Before you can perform NCOA

Link
processing, you must specify the match logi c,
mode, the number of data months, and other NCOA

Enter your information in ACE Views or job fi le

Enter your information in ACE Library

Access the Mover ID NCOALink window or block, and then fill in your information. See the table below for details.
To specify these NCOA
Link
processing and mail options, use the
ace_mvid_set_info() function with the values specified on page 26. See page 49 for more information about using this function.
NCOA
Link
processing
Use these options to enter your NCOA
and mail options
Views and job option Library option ID Description
Mode
ACE_MID_MODE
COA.
You’re processing this job to update it with the
latest address data.
Settings: COA STATS RETCODE
Stats.
You’re processing this job to analyze statistics, such as the number of records in your list that have updated addresses and the number of moves of each type. When you choose Stats, you do not get move­updated addresses.
Retcode.
purposes. When you choose Retcode (return code), and you post to the APM.RetCode or ACE_APM_RET_CODE output component, you can see the return codes, which further explain if match­ing records were found in the NCOA and why or why not. With this op tion, you do no t get move-updated addresses.
Link
processing options.
Link
processing and mail information.
Y o u’re processing this job f or informational
Link
directories,
Match Logic
26
Mover ID User’s Guide
ACE_MID_MATCH_LOGIC
Settings: B I C S R
Choose the types of moves that you want to process:
Business. Business moves only. This ignores fam-
ily and ind ividual moves.
Individual. Individual moves only. This ignores
family and business moves.
Ind & Bus. Individual and business. This ignores
family moves.
Standard. All types of moves will be processed. Residential. Individual and family moves.
Page 27
Views and job option Library option ID Description
Processing Ca tegory
ACE_MID_PROCESSING_CAT
Settings: EMP TRAIN INT DB TST MKTG TEST PROD RUN STAGE I
STAGE II SYS TEST
Specify your reason for using NCOA
Emp Train. You’re processing this file as part of
employee training.
Int Db Tst. You’re testing with a licensee-owned
database.
Mktg Test. You’re testing with external customer
lists.
Normal (Views and job file) or PROD RUN
(Library). You’re processing the mailin g list to update it before a mailing.
Stage I and Stage II. You’re testing the matching
performance against a USPS test file. The USPS scores the Stage II test file. Choose S tage I or Stag e II only if you are processing a USPS test file. See Chapter 4 for more information.
Sys Test. You’re processing this file as part of sys-
tem testing, such as loading of USPS f ile updates.
Link
:
High Match Rate Descrip­tion
Accepted COA Months
ACE_MID_HIGH_MATCH_RA TE_ DESC
Settings: A S R
ACE_MID_NUM_DATA_MONTHS
The USPS wants to distinguish between files that have a legitimate reason for a high percentage of NCOA
Link
matches and files that are fraudulently used to create mover lists. Legitimate reasons for high match rate:
ANK
Link
-processed file.
An ANK
Link
-processed file contains records for people who have moved, but you don’t yet have their new address. This option is avail­able only to full service providers.
Stage file.
If you’re performing Stage I or Stage II testing, be sure that the processing category is set to Stage also.
Return Mail File.
A “return mail file” contains
records for mail that was returned to sender.
ACE Vi ew s and Job file use rs: Choo se None or leave blank if you don’t expect a high match rate.
ACE Library users: If you don’t expect a high match rate, you can simply not call ace_mvid_set_info with ACE_MID_HIGH_MATCH_RATE_DESC.
Use this setting to make ACE ignore change-of-address data older than the specified number of months. For example, enter 12 to use change-of-address data that has a move-effective date within the last 12 months.
If you are an end user or limited service provider, enter a value from 6 to 18. If you’re a full service provider, enter a value from 6 to 48.
Processing First Class Mail Processing Periodicals Mail Processing Standard Mail Processing Package Services
Mail
ACE_MID_PROC_FIRST_CLASS ACE_MID_PROC_PER_MAIL ACE_MID_PROC_STD_MAIL ACE_MID_PKG_SRV_MAIL
Job-file and Library users:
Indicate the mail classes that you’re processing by entering processing and
Views users:
N
for those you’re not.
Select the options for those mail classes
that you are processing.
Chapter 2: Move -u pd a ting in AC E
Y
for those you’re
27
Page 28
Views and job option Library option ID Description
Processing Category
ACE_MID_PROCESSING_CAT
Settings: EMP TRAIN INT DB TST MKTG TEST PROD RUN STAGE I
STAGE II SYS TEST
Specify your reason for using NCOA
Emp Train. You’re processing this file as part of
employee training.
Int Db Tst. You’re testing with a licensee-owned
database.
Mktg Test. You’re testing with external customer
lists.
Normal (Views and job file) or PROD RUN
(Library). You’re processing the mailin g list to update it before a mailing.
Stage I and Stage II. You’re testing the matching
performance against a USPS test file. The USPS scores the Stage II test file. Choose S tage I or Stag e II only if you are processing a USPS test file. See Chapter 4 for more information.
Sys Test. You’re processing this file as part of sys-
tem testing, such as loading of USPS f ile updates.
Link
:
High Match Rate Descrip­tion
Accepted COA Months
ACE_MID_HIGH_MATCH_RA TE_ DESC
Settings: A S R
ACE_MID_NUM_DATA_MONTHS
The USPS wants to distinguish between files that have a legitimate reason for a high percentage of NCOA
Link
matches and files that are fraudulently used to create mover lists. Legitimate reasons for high match rate:
ANK
Link
-processed file.
An ANK
Link
-processed file contains records for people who have moved, but you don’t yet have their new address. This option is avail­able only to full service providers.
Stage file.
If you’re performing Stage I or Stage II testing, be sure that the processing category is set to Stage also.
Return Mail File.
A “return mail file” contains
records for mail that was returned to sender.
ACE Views and Jobfile users: Choose None or leave blank if you don’t expect a high match rate.
ACE Library users: If you don’t expect a high match rate, you can simply not call ace_mvid_set_info with ACE_MID_HIGH_MATCH_RATE_DESC.
Use this setting to make ACE ignore change-of-address data older than the specified number of months. For example, enter 12 to use change-of-address data that has a move-effective date within the last 12 months.
If you are an end user or limited service provider, enter a value from 6 to 18. If you’re a full service provider, enter a value from 6 to 48.
Processing First Class Mail Processing Periodicals Mail Processing Standard Mail Processing Package Services
Mail
28
Mover ID User’s Guide
ACE_MID_PROC_FIRST_CLASS ACE_MID_PROC_PER_MAIL ACE_MID_PROC_STD_MAIL ACE_MID_PKG_SRV_MAIL
Job-file and Library users:
Indicate the mail classes that you’re processing by entering processing and
Views users:
N
for those you’re not.
Select the options for those mail classes
that you are processing.
Y
for those you’re
Page 29
Views and job option Library option ID Description
List Name
Other Processes Used to Prepare List
ACE_MID_LIST_NAME
ACE_MID_PROCESSES_LIST
Enter the name of this list. You can name the list whatever you like, up to 30 characters.
If this list is a master house list or your only mailing list, you might consider entering your company name here.
The name you enter here will appear in the log files (see Chapter 3).
The USPS requires information about all processes used in obtaining your final data results. In particular, the USPS wants to know if you performed any USPS pro­cesses, such as CASS, DPV, RDI, and NCOA
Link
pro­cessing. If you’ve performed these processes through ACE, ACE keeps track of this information for you in the Mover ID Summary . If you’ve per formed any additional processes on this data, using software other than ACE, you must enter it here.
You can enter up to 512 characters. The text you enter here will appear in the Mover ID Summary and the
Link
NCOA
log files (see Chapter 3).
Chapter 2: Move -u pd a ting in AC E
29
Page 30
Enter NCOA
Link
service provider information

Required for service providers

Enter your information in ACE Views or job fi le

Enter your information in ACE Library

If you’re a service provider, you must provide details about the type of proc essin g being done. If you’re an end user, you can skip this section.
Access the Mover ID NCOALink Service Provider window or block, and then fill in your information. See the table below for details.
To specify service provider information, use the new ace_mvid_set_info() function with the values specified on page 30. See page 49 for more information about using this new function.

Service provider options

Views or job option Library option ID Description
Broker Involved
Not applicable. T o specify a broker, use the function
ace_mvid_set_contact_info() with the set­tings shown on page 34.
Use these options to enter your service provider information.
The broker directs business to an NCOA provider.
If a broker is involved, you must enter the broker’s contact information in the Mover ID Contact Infor­mation window or block. See page 34 for details.
If a list administrator, a broker, or both are involved in your job, you must complete a Mover ID Contact Information window or block for each of them, sepa­rately. See page 34.
Link
service
List Administrator Involved
Buyer Company Name ACE_MID_BUYER_CO If the list was processed for rent, sale, or lease, enter the
Mailing ZIP Code (job file)
Business Mail Entry Unit (BMEU) or Post Office ZIP Code (Views)
Not applicable. To specify a list administrator, use the
function ace_mvid_set_contact_info() with the settings shown on page 34.
ACE_MID_MAILING_ZIP Enter the ZIP Code of the Business Mail Entry Unit
A list administrator stores and maintains lists. List administrators are different from brokers in two ways:
List administ rators don ’ t send mo ve-updat ed files
back to the list owner.
List administrators may have an NCOALink
license.
If a list administrator, a broker, or both are involved in your job, you must complete a Mover ID Contact Information window or block for each of them, sepa­rately. See page 34.
name of the company or individual who bo ugh t the list.
(BMEU) or post office where the mail will be submit­ted for mailing.
30
Mover ID User’s Guide
Page 31
Views or job option Library option ID Description
Pre-Processes Per­formed
Pre-Process Changes With Postal Data
Pre-Process Changes With Other Data
Concurrent Processes Performed
Concurrent Process Changes With Postal Data
Concurrent Process Changes With Other Data
Post-Proc esses Per­formed
Post-Process Changes With Postal Data
Post-Process Changes With Other Data
ACE_MID_PREPROC_PERFORMED
Settings:
N
No pre-processing
Y
Yes, but with no data changes
D
Yes, with non-postal data changes
P
Yes, with postal data changes only
B
Yes, with postal and non-postal data
changes
ACE_MID_CONC_PROC_PERFORMED
Settings:
N
No concurrent-processing
Y
Yes, but with no data changes
D
Yes, with non-postal data changes
P
Yes, with postal data changes only
B
Yes, with postal and non-postal data
changes
ACE_MID_POSTPROC_PERFORMED
Settings:
N
No post-processing
Y
Yes, but with no data changes
D
Yes, with non-postal data changes
P
Yes, with postal data changes only
B
Yes, with postal and non-postal data
changes
Indicate whether you processed or will process this data before performing NCOA
If you will have processed this data before perform­ing NCOA
Link
processing, indicate whether that pre-
Link
processing.
processing included changes with postal data. If you will have processed this data before perform-
ing NCOA
Link
processing, indicate whether that pre-
processing included changes with non-postal data.
Indicate whether you processed or will process this data in some other way while performing NCOA
Link
processing. If you will have processed this data in some other
way while performing NCOA
Link
processing, indi­cate whether that pre-processing included changes with postal data.
If you will have processed this data in some other way while performing NCOA
Link
processing, indi­cate whether that pre-processing included changes with non-postal data.
Indicate whether you will process this data after per­forming NCOA
Link
processing.
If you will process this data after performing NCOALink processing, indicate whether that post­processing included changes with postal data.
If you will process this data after performing NCOALink processing, indicate whether that post­processing included changes with non-postal data.
Output Returned
Additional Notes
ACE_MID_STD_OUTPUT_RETURNED
Settings: Y N B
ACE_MID_ADDITIONAL_NOTES
Setting: A
If all required NCOALink output was returned to the client, choose Standard.
If the NCOALink output was returned to the client after other changes, choose Modify.
If the NCOALink output was returned to the client unchanged, and the required output data was also returned, choose Both.
Enter EXT REQUEST if the customer submitted a written request for an extension. If there was no request for extension, leave this blank or do not set it.
Chapter 2: Move -u pd a ting in AC E
31
Page 32

Enter Processing Acknowledgement Form (PAF) information

PAF requirements The Processing Acknowledgement Form (PAF) gives the NCOA

provider (licensee) permission from the list owner to perform NCOA processing on the list or lists from that list owner.
Each list must have its own PAF ID. You can itemize multiple lists and their PAF IDs on the back of the paper form.
Link
The USPS requires that NCOA
Have a completed PAF for a customer on file before performing NCOA
licensees:
processing on that customer’s data.
Keep a copy of the PAF on file for each of its customers.Get updated PAFs from each customer at least once a year.Assign a unique PAF ID for each list.
In addition, if a job i nvo lves both a broker and a li st admini st ra to r, you must have a paper PAF o n fi le fo r both of them.
PAFs are available from the USPS (http://ribbs.usps.gov/
), not from Business
Objects.

Transitioning from NCOA or FASTforward

The USPS has authorized the use of the NCOA from NCOA or FASTforward to NCOA
Link
Link
PAF during your transition
. According to the USPS:
Link
service
Link
Link
This process will allow existing NCOA/FASTforward and
Link
current NCOA applicants, to distribute and collect NCOA
Link
NCOA
processing, and for processing of client lists through
Licensees, as well as approved NCOA
Link
PAFs for future
the current NCOA/FASTforward licensed services. This will eliminate the need to collect multiple forms for processing.
Therefore, we [the USPS] have included a temporary alternate “Transition” Required Text Document within the Service Provider Licensee Performance Requirements. Please o btain t he most current copy of the Licensee Performance Requi rement s at
http://www.ribbs.usps.gov/files/ncoalink
.
Please be advised that NCOA and FASTforward PAF are not
Link
acceptable for authorizing NCOA
processing.
If you have any questions about transitioning, contact the USPS Move Update Support Department at 800-589-5766.

Steps There is a specific order of steps to follow in routing the PAF:

1. The list owner fills out the “List Owner” secti on , signs it, and sends it to the broker, agent, or list administrator.
2. The broker, agent, or list administrator fills out the “Broker/Agent/List Administrator” section, signs it, and sends it to the licensee.
Link
32
3. The licensee completes the “Licensee” section, signs it, and keeps it on file.
Mover ID User’s Guide
Page 33

Enter your information in ACE Views or job fi le

Access the Mover ID NCOALink PAF window or block, and then fill in your information. See the table on page 33 for details.

Enter your information in ACE Library

To specify PAF information, use the new ace_mvid_set_info() function with the values specified on page 33. See page 49 for more information about using this new function.

PAF options Use the options below to enter your PAF information.

Because you must fill in all of the client-specific information, you could save some time by creating a base job for each of your clients and reusing it on their future jobs.
Views and job option Library option I D Description
Person Signing PAF (job file) Name of the Person Signing
PAF (Views) Title of Person Signing PAF ACE_MID_PAF_SIGNER_TITLE Enter the job title of the person signing this PAF .
Date PAF Signed by Cus­tomer
PAF Type (job file) Type of PAF (Views)
ACE_MID_PAF_SIGNER_NAME Enter the name of the person signing this PAF.
You may enter up to 50 characters.
You may enter up to 50 characters.
ACE_MID_DATE_CUST_SIGNED_PAF Enter the date that the customer signed the PAF.
Use the yyyy/mm/dd date format.
ACE_MID_PAF_TYPE
Settings: I M R
Specify the reason for completing your current PAF:
Initial
or
I.
This is the first PAF you’re com­pleting to become authorized to process addresses for this particular customer.
Modified
because some information on your old one changed.
Renewal
because your old one is expiring.
or
M.
You’re completing a new PAF
or
R.
You’re completing a new PAF
Customer Parent Company (job file)
Parent Company (Views) Customer Alternate Com-
pany (job file) Alternate Company Name
(Views) Date PAF Signed by Licensee ACE_MID_DATE_LICENSEE_SIGNED_

PAF log file The PAF information that you provide (above) is stored in a log file. See Chapter

ACE_MID_PAF_PARENT_CO If the list owner’s compan y is owned by another
company (a “parent company”), enter the parent company’s name here.
ACE_MID_PAF_ALT_CO_NAME If the list owner’s company is also known by
another name, enter that alternate name here.
PAF
Enter the date that the licensee signed the PAF. (The licensee is the NCOA vider.)
Use the yyyy/mm/dd date format.
Link
service pro-
3 for details.
Chapter 2: Move -u pd a ting in AC E
33
Page 34

Enter contact information for the broker or list administrator

Required information — if there’s a broker or list administrator

Enter your information in ACE Views or job fi le

Enter your information in ACE Library

If you indicated, in the Mover ID NCOALink Service Provider window or block, that there is a broker or list administrator involved in this job, then you must provide contact information for them, as described below.
If you’re an end user, you can skip this section.
Access the Mover ID Contact Infor mation window or bloc k, and then fi ll in your information. If both a broker and a list administrator are involved, you must complete a window or bl ock for bo th of them. Li kewise, if multipl e broker s or li st administrators are involved, complete a window or block for each one. See the table below for option descriptions.
To specify contact information for a broker or list administrator, use the ace_mvid_set_contact_info() function:
Use the setting_ID values specified in the table below.
Set contact_index to a number from 1 to 100. The contact_index is a unique identifier about which contact is included. Information associated with the first contact should use conta ct_index 1, the second contact should use contact_index 2, and so on.
See your ACE Library Reference for more information about using this function.

Contact information options

Views or job option
Contact Type
Contact ID
NCOALink Contact Level
NCOALink Contact NAICS
You must provide contact information if a broker or list administrator is involved in this job. The information entered here is stored in a USPS-required log file, the broker agents / list administrators log file. See page 58.
Library setting_ID
ACE_MID_CONTACT_TYPE
Settings: Broker Listadmin
ACE_MID_CONTACT_ID
ACE_MID_CONTACT_LEVEL
ACE_MID_CONTACT_SIC
Description
Enter Broker or Listadmin. A broker directs business to the service provider; a list adminis­trator stores and maintains address lists.
Enter a unique ID number for the broker or list administrator. You assign the ID number.
Enter the degree of separation this contact is from you. For example, enter from this contact. If your contact received the list from a different broker, then enter 2 for this contact.
Enter a value from 1 to 99. Enter the broker’s or list admin istrator’ s numeric
North American Industry Classification System code, which identifies the business that they engage in. For more information, see:
http://www.census.gov/epcd/www/naics.html
1
if you received the list
NCOALink Date Signed PAF
34
Mover ID User’s Guide
ACE_MID_DATE_BROKER_SIGNED_PAF ACE_MID_DATE_ADMIN_SIGNED_PAF
Enter the date when this contact signed the P A F.
Page 35
Views or job option
Library setting_ID
Description
Contact Name Contact Address Contact City Contact State Code Contact Zip Contact Plus 4 Code Contact Telephone Num­ber
ACE_MID_CONT ACT_NAME ACE_MID_CONTACT_ADDRESS ACE_MID_CONTACT_CITY ACE_MID_CONTACT_STATE ACE_MID_CONTACT_ZIP ACE_MID_CONTACT_ZIP4 ACE_MID_CONTACT_PHONE
Enter the broker’s or list administrator’s:
namecomplete addressphone number
Chapter 2: Move -u pd a ting in AC E
35
Page 36

Memory usage

Save time Y ou can reduce the time required for NCOA

options to control memory usage:
Loa d directories into memory Cache for ZIP order processing Windows caching options (for Windows operating system, ACE Views and
jobfile only)
See “Improving NCOALink performance” on page 69 for a complete explanation
Link
processing speed and what you can do to improve it.
Link
directories into system memory before processing. Your
Link
requires large directories and supporting files.

Load directo ries into memory

of NCOA
You can load NCOA system may not be able to load the entire set of NCOA memory because NCOA However, you can control memory usage with the NCOA
To maximize performance, allocate as much memory as possible, up to 3GB. Even 200 MB can provide a large boost in performance. The amount of memory that you can allocate is limited only by the amount of memory available on your computer.
The USPS recommends that you have at least 1.5GB free while performing NCOALink processing. Ideally, there would be 3GB available.
Link
processing by using sev eral ACE
Link
files into system
Link
memory options.

Cache for ZIP order processing

To improve NCOA order, select t he Cache for ZIP Order Processing option. With this option selected, one or more segments of the NCOA
Link
processing speed when your input data is in ZIP Code
Link
data are cached on your computer. A segment of data is temporarily saved in the computer’s RAM until that segment of data has been processed. Then the next segment is loaded into RAM and the previous segment is removed from RAM.
Two ways to place data in ZIP Code order
To place your data in ZIP Code order, you have several options:
Use a program such as FirstPrep to place the data in ZIP Code order before
you process the data with ACE.
Turn on the Sort Input File by ZIP Code option in ACE’s Execution block to
place the data in ZIP Code order while you run ACE.
Turn on the Cache for ZIP Order Processing option only when processing
!
your data in ZIP Code order. Turning this option on when processing data that is not in ZIP Code order will slow performance.
Best results When you use the Cache for ZIP Order Processing option, you’ll see the greatest
speed improvements in the following situations:
Your data is concentrated geographically. For example, a 100,000-record file
that contains only Wisconsin addresses is processed much faster than a 100,000-record file that contains addresses for all 50 states.
36
Mover ID User’s Guide
Page 37
Your data file is large. Speed improves in proportion to the size of the data
file.
The Cache for ZIP Order Processing option is not an automatic performance enhancement in every situation. Take time to analyze its effects on your processing speeds.

Windows caching options

Correctly setting the Windows caching options may improve processing speed. This can help you surpass the previous 2 gi gabyte (G B) application memory limit. If you have over 2GB of memory available for processing, you may notice improvements using the Windows caching options.
These Windows caching options apply only to:
Windows operating system NCOA Suite ACE Views and Jobfile
Link
Link
directories
directories
Before you use the Windows caching options, you or your System Administrator must perform two system-level tasks. Unless you perform these two tasks first, the Windows caching options will be unusable. The two tasks are:
1. Edit the boot.ini file. See “Edit boot.ini” on page 37 for details.
2. Edit permissions so that pages can be locked into memory. See “Edit permissions” on page 38 for details.
Edit boot.ini The boot.ini file specifies how to start (or boot) the computer. The Windows
operating system (OS) does not recognize memory over a certain amount, usually 4GB. If Windows is unable to recognize all physical memory currently installed, you may need to enable PAE (Physical Address Extensions). Even with this option, other restrictions, such as motherboard and BIOS limitations, may cause Windows OS to recognize less than the total amount of installed memory. See
http://ww
w.microsoft.com/whdc/system/platform/server/PAE/PAEdrv.mspx fo r
OS restrictions and for information about PAE.
If you have never made changes to boot.ini before, we recommend that you
!
give these instructions to your System Administrator. If you accidentally delete something, it may seriously and adversely affect your computer.
1. At a command prompt, navigate to the root of the boot directory. For example, c:\boot.ini (where c is the drive where the file is located).
2. Type attrib -s -h -r boot.ini to remove the system, hidden, and read-only attributes of the boot.ini file.
3. Open the boot.ini file in a text editor and then type /pae at the end of the operating system that will process your ACE jobs. For example,
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /pae
4. Save and close the boot.ini file.
5. At the command prompt, type a ttrib +s +h +r boot.i ni to restore the system, hidden, and read-only attributes that protect the boot.ini file.
Chapter 2: Move -u pd a ting in AC E
37
Page 38
Edit permissions Follow these instructions to grant permission to lock pages in memory.
1. On the Start menu, click Run. In the Open box, type gpedit.msc.
2. In the Group Policy window, open the following folders in succession:
Computer Configuration Windows Se ttings Security Settings Local Policies User Rights Assignment

Set up ACE Views or job file

3. In the details pane, double-click Lock pages in memory.
4. In the Local Security Policy Setting window, click Add.
5. In the Select Users or Groups window, add the applicable user.
6. Reboot to make your changes take effect.
1. Access the Memory Usage window or block.
2. To load ZIP-sorted segments into RAM, turn on the Cache for ZIP Order Processing option.
38
Mover ID User’s Guide
Page 39
BEGIN Memory Usage ========================================== Windows Use Extended Memory (See NOTE)= NONE Windows Memory Window Size (# of MB). = Load RDI Dirs into System Memory (Y/N)= N Load LACSLink Dirs into Memory (Y/N). = N Load SuiteLink Dirs into Memory (Y/N) = N Load DPV Dirs into System Memory (Y/N)= N
Load DSF2 Dirs into Memory (Y/N)..... = N
NCOALink Memory (AUTO/MANUAL/N)...... = N
NCOALink Memory Allocation (# of MB). = Cache for ZIP Order Processing (Y/N). = N Insufficient Memory Action(ABORT/CONT)= ABORT END
3. At the NCOALink Memory option, choose or enter N (None), Auto, or
Manual. See the table below for details.
Setting Description
N (job file) None (Views)
If you don’t want to transfer NCOA choose this option. Your processing will be slower.
Link
files into system memory,
Auto
Recommended setting.
Link
NCOA
files into system memory. ACE determines the amount
If you select this option, ACE will load your
of memory to use based on the available memory, the size of the files, and the extent to which caching the files will improve pro­cessing time.
Manual If you select this option, ACE will load your NCOA
Link
files into system memory based on the amount you enter in the NCOALink Manual Allocation parameter. If you use the manual setting, set Allocation to 2048MB or more.
4. If you chose Manual in step 3, go to the NCOALink Manual Allocation parameter and enter the amount of memory, in megabytes (MB), that you
Link
want to dedicate to loa ding NCOA
files into memory.
5. To improve Windows caching, set the Windows memory options. See the following table for details.
Chapter 2: Move -u pd a ting in AC E
39
Page 40
Option Description
Windows Use Extended Memory (ACE job file)
Extended Memory Usage (ACE Views)
Control memory caching on the Windows operating sys­tem. If you set this option to Manual or Auto, then also set the NCOALink Memory and NCOALink Memory Alloca­tion options.
None.
ACE uses all available application memory for pro-
cessing.
Auto.
Recommended setting. ACE determines how much memory to use. Typically, this is approximately 200MB of application memory.
Manual.
If you set this option to Manual, then enter the amount of memory to u se at the Windows Memory Wind ow Size option.
Windows Memory Win­dow Size (ACE job file)
Memory Window Size (ACE Views)
If you set the Windows Use Extended Memory option to Manual, we recommend setting the Windows Memory Win­dow Size option to 200MB. This will be a good starting point for any performance testing that you do . Th e n yo u ca n modify the size as needed after further testing.

Set up ACE Library

ZIP order processing To cache for ZIP Code order processing, call:
ace_set_mode(ah, ACE_MODE_CACHE_ZIP_ORDER,TRUE);
To cache for random order processing (default), call:
ace_set_mode(ah, ACE_MODE_CACHE_ZIP_ORDER,FALSE);
These function calls control caching in ZIP or random order only. To set up caching of NCOA
Memory caching To enable memory caching in ACE Library, use ace_mvid_set_info() with
Link
directories in ACE Library, see “Memory caching” below.
ACE_MID_CACHE_MB. The setting should be auto or a number as a text string. To manually specify the maximum number of megabytes (MB) of RAM to
Link
dedicate to NCOA
Setting Description
Auto ACE loads your NCOA
directories,
Link
files into system memory. ACE determines the amount of memory to use based on the available memory, the size of the files, and the extent to which caching the files will improve processing time.
For example:
ace_mvid_set_info(ah_id, ACE_MID_CACHE_MB,"AUTO");
number as a string
ACE loads your NCOA megabytes (MB) you specify in this string.
For example:
ace_mvid_set_info(ah_id, ACE_MID_CACHE_MB, "250");
Link
files into system memory based on the number of
40
See also “ACE Library functions” on page 49.
Mover ID User’s Guide
Page 41

Insufficient memory If your computer doesn’t have enough memory available to load the NCOA

files, ACE will either stop processing the job or continue processing it without loading the files into system memory, depending on your choice at the Insufficient Memory Action parameter.
Link
The Insufficient Memory Action option applies to NCOA
Setting Description
and DPV files.
Abort Discontinue processing the entire job. This is the default setting. Cont Continue processing wit hout lo ading dir ectories in to syste m mem ory. Choose
this setting to process the job without interruption.
Link
How does this affect DPV or LACS
Link
?
When you perform DPV (Delivery Point Validation), LACS
Link
processing at the same time, the DPV and LACS into memory first, before the NCOA
Link
directories.
directories will be loaded
Link
, and NCOA
If you select the Load DPV Directories into System Memory option, be aware that caching DPV directories requires at least 768 megabytes (MB).
Link
Chapter 2: Move -u pd a ting in AC E
41
Page 42

Automatically replace old address with new

This section applies to ACE Views and Job-File only. If you’re using ACE Library, you can skip this section.
Use with caution! Normally, ACE standardizes your input data and outputs it into AP fields. If new
(forwarding) addresses are available, ACE outputs them to APM fields. If you want to replace old addr esses with new ( forwarding ) addresses, yo u can use
the Mover ID Auto Update optio n. With Mover ID Auto Update turned on, ACE posts the new (forwarding) address to AP fields, overwriting the pre-move address.
When Mover ID Auto Update is enabled, the PW fields will contain either the move-updated address or the original address, if no move-update was available.
This option might be useful if you use either of ACE’s “auto update” features: Standardize PW Fields in the Input File window or block, or Copy Input Data to Output File in the Post to Output File window or block.
Important:
Before turning on this option, read the cautionary information in the “What to
expect from the USPS and from Busi ness Objects” on page 11. If you need to keep both the old and the new address, turn off this option.
If you want to selectively post move-updated addresses, turn this option on
and add additional fields and filters as needed.
This option does not affect the style or availability of APM fields for manual posting. APM fields are listed in the Quick Reference for Views and Job-File Products.
42
Mover ID User’s Guide
Page 43

False-positive log file

The USPS requires that ACE log false-positive addresses in a log file. ACE creates a log file for each mailing list that contains a false positive record. If multiple false positives exist within one mailing list, ACE writes them all to the same log file.

Location for log files You set the location of the log file in the Log File Director y parameter in the

Customer & USPS Licensee Information block. Make sure that the location you set is writable.

Log file naming convention

For the DPV log file, ACE names the log files based on specific conventions. Each log file is named dpvl####.log, where #### is a number from 0001 t o 9 999. For example, the first log file generated is DPVL0001.log, the next one is DPVL0002.log, and so on.

Submit to USPS When a list is processed t hat produces a log file, you must submit the log file to

the USPS NCSC (National Customer Support C enter) at dsf2stop@usps.gov the subject line DPV False Positive or LACS
Link
False Positive as applicable.
with
The NCSC uses this informati on to determine whether the list can be returned to the mailer.
When the USPS has released your list that contained the locked record, you should delete the corresponding log file.
Chapter 2: Move -u pd a ting in AC E
43
Page 44

Unlocking DPV

Full and limited-service providers need to email the DPV False Positive log file to the USPS NCSC (Nation al Customer Support Center) to obtain approval and the necessary information to unlock the list (see “Submit to USPS” on page 43).
2
If you are an end user with DSF
disabled in your job setup, ACE locks DPV processing. You must contact Business Object’s Customer Assurance to obtain an unlock code following the steps below.

Retrieve code and unlock DPV

Follow these steps to retrieve the DPV unlock code from the SAP SMP (Service Marketplace):
1. Go to the SMP (http://service.sap.com/message) and create a support
message using BOJ-EIM-COR2.
2. Attach the dpvx.txt file to your message.
In Windows, the fle is located at pw\dpv. For UNIX, the file is located at postware/dpv.
Note: If the dpvx.txt file cannot be att ached t o the original message, inclu de the unlock information in the message instead.
3. SAP Support sends you a new dpvw.txt file. Replace the old file with the new
file.
4. Open your database and remove the record causing the lock.
Keep in mind that you can only use t he unlock code one time. If ACE de tects another false-positive, you will need to retrieve a new DPV
unlock code. Be
sure to remove the record that is causing the lock from the database.
44
Mover ID User’s Guide
Page 45

Move-update output fields

Pre-move and post­move data are
ACE can provide information about your addresses before and after move­updating.
available
ACE Views and Job-File users
Pre-move f ields. The data posted to these fields accurately reflects your data
before move-updating with Mover ID. These fields start with the prefix AP. For a complete list of AP fields, see your Quick Reference for Views and Job-File Products.
Post-move fields. The data posted to APM fields accurately reflects your data after move-updating with M over ID. These fie lds start with t he prefix APM. For a complete list of APM fields, see your Quick Reference for Views and Job-File Products.
ACE Library users When you use the ace_get_component function, you control which data is
returned by using the following source flags:
ACE_OLD returns the data as it was input. ACE_NE W returns the data as it was standardized by ACE. ACE_M VID returns the move-updated data.

Move-update output fields for names

Nicknames, alternate spellings, and initials
In some cases, an input name is not the name used when matching with the
Link
NCOA
directory. ACE can substitute nicknames and alternate spellings to
ensure more accurate matching.
The USPS controls which nicknames and spelling variations are allowed
For example, the input name is John Q Smith, and the name in the NCOALink directory is Jack Q Smith. ACE recognizes that Jack is a common nickname for John, and so it can recognize that the two records match (assuming that the address data also matches, of course).
Your database
John Q Smith 100 West Creek Ln Dodge WI 54625-9242
They
match!
Link
NCOA
database
Jack Q Smith
100 West Creek Ln Dodge WI 54625-9242
1492 Stratford St Mabel MN 55954-2922
old address
new address
Chapter 2: Move -u pd a ting in AC E
45
Page 46
The following output components show what name ACE used for matching with
Link
NCOA
ACE Views and job file ACE Library
.
APM.Pre_Name APM.First_Name APM.Mid_Name APM.Last_Name APM.Post_Name
ACE_APM_PRE_NAME ACE_APM_FIRST_NAME ACE_APM_MID_NAME ACE_APM_L AST_NAME ACE_APM_POST_NAME
ACE Library users: Call ace_get_component with the ACE_MVID source flag to retrieve these com­ponents showing data used for matching with
Link
NCOA
.
Parsed name lines: If your name data is stored in name lines (for example, “Dr. Paul Lionel Smith Jr.” all in one field), ACE parses it into the discrete names and uses the discrete names when looking for matches in the
Link
NCOA
directory. This ensures more accurate matching.
46
Mover ID User’s Guide
Page 47

Strategies for your ACE output file

This section applies to ACE Views and Job-File only. If you’re using ACE Library, you can skip this section.
You can use an option called Mover ID Auto Update to automatically replace the old address with the new (forwarding) address. However, the best way to control what you output and when is to manually post.
We recommend that you set up your ACE job so that your output file(s) will include both the new and the old address. Specific output options are shown below.

Clone input and append new address

The easiest way to set up your ACE output file is to clone (copy) the input file format, then append extra fields for move data. In the output records not affected by a move, most of the appended fields will be blank. The example below shows what your Job-File setu p might look like. See the Quick Reference for Views and Job-File Products for complete details about these fields.
BEGIN Create Output File =================================== ...
Copy Format of Input File (Y/N)...... = Y
Field (name,length,type,misc)........ = Move_Flag, 1, c
Field (name,length,type,misc)........ = Move_Date, 6, c
Field (name,length,type,misc)........ = Move_Type, 1, c
Field (name,length,type,misc)........ = Move_PAddr, 50, c
Field (name,length,type,misc)........ = Move_SAddr, 50, c
Field (name,length,type,misc)........ = Move_City, 28, c
Field (name,length,type,misc)........ = Move_State, 2, c
Field (name,length,type,misc)........ = Move_ZIP, 5, c
Field (name,length,type,misc)........ = Move_ZIP4, 4, c
Field (name,length,type,misc)........ = Move_DPBC, 2, c
Field (name,length,type,misc)........ = Move_CART, 4, c
END
BEGIN Post to Output File ================================== ... Copy Input Data to Output File (Y/N). = Y
Copy (source, destination)........... = APM.RetCode, Move_Flag
Copy (source, destination)........... = APM.Eff_Date, Move_Date
Copy (source, destination)........... = APM.Move_Type, Move_Type
Copy (source, destination)........... = APM.Prim_Addr, Move_PAddr
Copy (source, destination)........... = APM.Sec_Addr, Move_SAddr
Copy (source, destination)........... = APM.City, Move_City
Copy (source, destination)........... = APM.State, Move_State
Copy (source, destination)........... = APM.ZIP, Move_ZIP
Copy (source, destination)........... = APM.ZIP4, Move_ZIP4
Copy (source, destination)........... = APM.DPBC, Move_DPBC
Copy (source, destination)........... = APM.CART, Move_CART
END
Chapter 2: Move -u pd a ting in AC E
47
Page 48

Divert move records to a separate output file

Instead of cloning and appending, you can create a second output file just for move records. Two approaches are possible:
Output each record once, placing move records in the “movers” file and all
other records in the “main” file (shown below).
Output move records twice; once to the “main” database, and a second time
to the “movers” database.
Both of these approaches require that you use an output filter to determine whether a record is a move.
“Movers” file For the “movers” file, use the
filter (see “movers” file, use the clo ne­and-append approach shown on the previous page.
“Main” file option If you want to keep movers out
of your “main” file, u se the fi lter (see Each Record option to Once (see
). Populate this file as you
wish, but don’t bother posting any of the APM fields to the main file; they’ll all be blank.
“Main” file option If you want the “main” file to
include both movers and others, omit the filter on the “main” file (see Each Record option to All Filters (see use the clone-and-append approach sh own on the pr evious page.
). To populate the
), and set the Output
), and set the Output ). To populate the file,
BEGIN Output Control ======================================= Output Each Record (ONCE/ALL FILTERS) = Once ... END
“Movers” file
BEGIN Create Output File =================================== ...
Copy Format of Input File (Y/N)...... = Y
Field (name,length,type,misc)........ = Move_Flag, 1, c
... END
BEGIN Post to Output File ================================== ...
+ Output Filter...................... = alltrim(APM.RetCode) $ “A,91,92”
Copy Input Data to Output File (Y/N). = Y
Copy (source, destination)........... = APM.RetCode, Move_Flag
... END
“Main” file
BEGIN Create Output File =================================== ... END
BEGIN Post to Output File ================================== ...
+ Output Filter...................... = .not. (alltrim(APM.RetCode) $ “A,91,92”)
... END
48
Mover ID User’s Guide
Page 49

ACE Library functions

Functions To set up NCOA

ace_mvid_set_info() ace_mvid_set_contact_info() ace_set_mailer_info() ace_mvid_ncoal_header() ace_mvid_report_init() ace_mvid_report_set_data() ace_mvid_report_set_retcode_count() ace_mvid_report_open() ace_mvid_report_job_section() ace_mvid_report_file_section() ace_mvid_report_term() ace_set_mode() ace_set_file() ace_get_component()
For details about these functions, see your ACE Library Reference.
Link
processing, you’ll use the following functions:
Chapter 2: Move -u pd a ting in AC E
49
Page 50
50
Mover ID User’s Guide
Page 51
Chapter 3: Reports and log files
Chapter summary ACE produces the fo llowing move-related reports and log files:
Mover ID Summary report Customer service log (CSL) Addr ess Conv ersion Statistics (ACS) file PAF customer information log Broker agent / list administrator lo g DPV false positive log
Note: The ACE Job Summary report also shows the number and percentage of records that were move-updated. See your ACE User’s Guide for a sample of this report.
Chapter 3: Reports and log files
51
Page 52

Mover ID Summary report

The Mover ID Summary includes useful NCOA
Link
information, including your
entries about the licensee, customer, service provider, list owner, and so on.

Return code information

The Mover ID Summary always includes a brief summary of return codes, and you can choose to include more detailed return code descriptions on the report if you want. Return codes tell you if a record was affected by a move, how the
Link
NCOA
match was made, or why a match could not be made.
If and when the USPS adds return codes in the future or changes return code descriptions, those new or updated return codes will au tomatically be availabl e to you through ACE in the Mover ID Summary report, Customer Service Log (CSL), and Address Correction Statistics (ACS) file.
Setup To enable printing of th e detailed return code descriptions:
In ACE Views or Job File, select Print Return Code Descriptions in the
Report: Mover ID Summary window or block.
In ACE Library, call
ace_mvid_report_set_data(ah, ACE_RPT_SETTING_STRING_INC_RTN_CODE_DESC, (char *)”Y”);
ACE Library For more information about setting up and generating this report in ACE Library,
see your ACE Library Reference, Appendix D.
52
Mover ID User’s Guide
Page 53
Job setup and input file informatio n
The first page of this report shows how you set up the job, information about the input file, and statistics about your pre-move addresses.
Page 1 Mover ID Summary ACE [version] NCOALink Processing Summary Report Mover ID [version]
--------------------------------------------------------------------------------
Job Information ----------------------------------------------------------------
Job Name: wonder.ace Job Description: NCOA/Link Testing Job Owner: Team
Mover ID Auto-Update: No Match Logic: I - Individual
Service Provider Type: END USER ANKLink Enabled: No Directory Data Months: 48 Directory Data Format: HASH Mode (Data Returned): C - COA Processing Category: NORMAL Accepted COA Months: 18 Mail Classification: A High Match Rate Desc.: N/A
NCOALink Processing Completed: 20060531 NCOALink Log File Path: .../ace/stats List Name: ncoae001.ace Processes Used to Prepare List: NCOALink, Centroid GeoCensus, Address-Level GeoCensus, EWS, eLOT, RDI, DPV, and CASS
Customer & USPS Licensee Information
-----------------------------------------------------------­Licensee ID: E001 Licensee Name: Team List Owner SIC: 123456
Input File ---------------------------------------------------------------------
Input File Name: /ace/job/input/ncoanew.dbf
Total Input Records: 1888 Less Records Dropped by Delete Mark: 0 Less Records Dropped by Input Filter: 0 Less Records Up-To-Date Per Z4 Change: 0 Net Input Records to be Processed: 1888 Total Number of NCOALink Matches: 331 Total Number of NCOALink Return Codes: 1888 Total Moves not DPV confirmable: 266 NCOALink Match Percentage: 17.53 NCOALink Return Code Percentage: 100.00
Statistics (based on pre-move addresses) ---------------------------------------
Delivery Point Validation Summary (DPV)
No Stats Processed: Y
Vacant Processed: Y CMRA DPV DPV DPV Status Code Count Confirmed No Stat Vacant
-------------------------------- --------- --------- --------- ---------
Primary/Secondary Confirmed (Y) 80 0 13 0 Secondary Not Confirmed (S) 8 0 0 0 Secondary Missing (D) 1 0 0 0
-------------------------------- --------- --------- --------- --------­Total: 89 0 13 0 Total Not Confirmed: 410
Chapter 3: Reports and log files
53
Page 54
Statistics about all input data
The second page of the Mover ID Summary shows information about the move­updated addresses. This section is based on all input data.
Mover ID Summary ACE [version] NCOALink Processing Summary Report Mover ID [version]
-------------------------------------------------------------------------------
Address Type Summary Records %
--------------------- ---------- -----­Street 1597 84.59 PO Box 37 1.96 High Rise 24 1.27 Rural Route 179 9.48 Firm 0 0.00 General Delivery 23 1.22 Military 0 0.00 Unique 0 0.00
--------------------- ---------- -----­Total Zip+4 Codes: 1860 98.52
Statistics (based on move-updated addresses) -----------------------------------
Forwardable Moves Records %
--------------------- ---------- -----­Individual 298 15.78 Family 0 0.00 Business 0 0.00
--------------------- ---------- -----­Total Moves: 298 15.78
Address Type Summary Records % Assignment Summary Records %
--------------------- ---------- ------ --------------------- ---------- -----­Street 1589 84.16 LACS Convertible 224 11.86 PO Box 34 1.80 Addr Level Geo Codes 1581 83.74 High Rise 28 1.48 Centroid Geo Codes 291 15.41 Rural Route 171 9.06 Firm 0 0.00 RDI Matches 1760 93.22 General Delivery 24 1.27 Military 6 0.32 Unique 0 0.00
--------------------- ---------- -----­Total Zip+4 Codes: 1852 98.09
CASS Qualitative Statistical Summary (QSS)
Records % Records %
--------------------- ---------- ------ --------------------- ---------- -----­High Rise Default 46 2.44 Rural Route Default 29 1.54 High Rise Exact 5 0.26 Rural Route Exact 142 7.52 EWS Match 0 0.00 LACS Convertible 224 11.86 DPV Confirmed 137 7.26 RDI 1760 93.22
54
Mover ID User’s Guide
Page 55

Return code summary of all input data

This section shows return code information for all of your input dat a. Late r in the report, it is broken down by output file.
Page 3 Mover ID Summary ACE [version] NCOALink Processing Summary Report Mover ID [version]
--------------------------------------------------------------------------------
Delivery Point Validation Summary (DPV)
Confirmed Records % Not Confirmed Records %
--------------------- ---------- ------ --------------------- ---------- -----­Confirmed 135 7.15 Primary Not Confirmed 1704 90.25 CMRA Confirmed 2 0.11 Secondary Not Conf. 18 0.95 Secondary Missing 21 1.11
--------------------- ---------- ------ --------------------- ---------- -----­Total Confirmed: 137 7.26 Total Not Confirmed: 1743 92.32
NCOALink Return Code Summary Records %
------------------------------------------------------------ ---------- -----­ New Address Provided by NCOALink A - COA MATCH 289 15.31 91 - COA MATCH - SECONDARY NUMBER DROPPED FROM COA 4 0.21 92 - COA MATCH - SECONDARY NUMBER DROPPED FROM INPUT 5 0.26
Found COA 01 - COA MATCH - FOREIGN MOVE 4 0.21 02 - COA MATCH - MOVE LEFT NO ADDRESS 5 0.26 03 - COA MATCH - PO BOX CLOSED NO FORWARDING ADDRESS 4 0.21 05 - COA MATCH - A NEW ADDRESS CAN NOT BE PROVIDED 15 0.79 14 - COA MATCH - NEW ADDRESS WOULD NOT CONVERT 0 0.00 19 - FOUND COA - NEW ADDRESS NOT ZIP+4 OR DPV CONFIRM 5 0.26
Cannot Match COA 00 - NO COA MATCH 1514 80.19 04 - CANNOT MATCH COA - STREET ADDRESS WITH SECONDARY 0 0.00 06 - CANNOT MATCH COA - MIDDLE NAME CONFLICT 0 0.00 07 - CANNOT MATCH COA - GENDER CONFLICT 0 0.00 08 - CANNOT MATCH COA - CONFLICTING INSTRUCTIONS 0 0.00 09 - CANNOT MATCH COA - HIGHRISE DEFAULT 0 0.00 10 - CANNOT MATCH COA - RURAL DEFAULT 0 0.00 11 - CANNOT MATCH COA - INSUFFICIENT COA NAME 8 0.42 12 - CANNOT MATCH COA - MIDDLE NAME TEST FAILED 2 0.11 13 - CANNOT MATCH COA - GENDER TEST FAILED 0 0.00 15 - CANNOT MATCH COA - INDIVIDUAL NAME INSUFFICIENT 15 0.79 16 - CANNOT MATCH COA - SECONDARY NUMBER DISCREPANCY 8 0.42 17 - CANNOT MATCH COA - OTHER INSUFFICIENT NAME 8 0.42 18 - CANNOT MATCH COA - GENERAL DELIVERY 0 0.00 20 - CANNOT MATCH COA - CONFLICTING DIRECTIONS 0 0.00
From "Daily Delete" Process 66 - DAILY DELETE 2 0.11
------------------------------------------------------------ ---------- -----­Total NCOALink Return Codes: 1888 100.00
Chapter 3: Reports and log files
55
Page 56

Detailed return code descriptions

If you chose to print detailed return code descriptions, they are shown in this section of the Mover ID Summary report.
Page 4 Mover ID Summary ACE [version] NCOALink Processing Summary Report Mover ID [version]
--------------------------------------------------------------------------------
NCOALink Return Code Description
Code = Return Code Description = Explanation of Return Code Address - Y = New Address Provided
- N = New Address Not Provided How - D = Derived by data - returned in lieu of 11 digit
- S = Derived by software
+------+-------------------------------------------------------+---------+-----+ | Code | Description | Address | How | +------+-------------------------------------------------------+---------+-----+ | 00 | NO COA MATCH -MATCH WAS NOT FOUND WITH GIVEN INPUT | N | S | | | NAME, ADDRESS AND MATCHING LOGIC | | | +------+-------------------------------------------------------+---------+-----+ | 01 | COA MATCH - FOREIGN MOVE - MATCH FOUND, BUT NEW | N | D | | | ADDRESS OUTSIDE USPS DELIVERY AREA - A NEW ADDRESS | | | | | CAN NOT BE PROVIDED | | | +------+-------------------------------------------------------+---------+-----+ | 02 | COA MATCH - MOVE LEFT NO ADDRESS - MATCH FOUND, BUT | N | D | | | NEW ADDRESS WAS NOT PROVIDED TO THE USPS - A NEW | | | | | ADDRESS CAN NOT BE PROVIDED | | | +------+-------------------------------------------------------+---------+-----+ | 03 | COA MATCH - PO BOX CLOSED NO FORWARDING ADDRESS - | N | D | | | MATCH FOUND, BUT NEW ADDRESS WAS NOT PROVIDED TO THE | | | | | USPS - A NEW ADDRESS CAN NOT BE PROVIDED | | | +------+-------------------------------------------------------+---------+-----+ | 04 | CANNOT MATCH COA - A COA WAS FOUND UTILIZING THE LAST | N | D | | | NAME AND ADDRESS BUT THE INPUT DID NOT CONTAIN A | | | | | SECONDARY NUMBER AND THE COA CONTAINED A SECONDARY | | | | | NUMBER | | | +------+-------------------------------------------------------+---------+-----+ | 05 | COA MATCH - A NEW ADDRESS CAN NOT BE PROVIDED - THE | N | D | | | DPBC REPRESENTS MORE THAN ONE ADDRESS - THE NEW | | | | | ADDRESS CAN NOT BE PROVIDED | | | +------+-------------------------------------------------------+---------+-----+ | 06 | CANNOT MATCH COA - MIDDLE NAME CONFLICT - MORE THAN | N | D | | | ONE COA AND THE MIDDLE NAMES OR INITIALS ON THE COA'S | | | | | ARE DIFFERENT - NEW ADDRESS CAN NOT BE PROVIDED DUE | | | | | TO UNRESOLVED CONFLICT | | | +------+-------------------------------------------------------+---------+-----+ | 07 | CANNOT MATCH COA - GENDER CONFLICT - MORE THAN ONE | N | D | | | COA EXISTS AND THE GENDERS ON THE COA'S ARE DIFFERENT | | | | | - NEW ADDRESS CAN NOT BE PROVIDED DUE TO UNRESOLVED | | | | | CONFLICT | | | +------+-------------------------------------------------------+---------+-----+ | 08 | CANNOT MATCH COA - CONFLICTING INSTRUCTIONS - MORE | N | D | | | THAN ONE COA EXISTS WITH DIFFERENCES IN THE NEW | | | | | ADDRESS - NEW ADDRESS CAN NOT BE PROVIDED DUE TO | | | | | UNRESLOVED CONFLICT | | | +------+-------------------------------------------------------+---------+-----+ | 09 | CANNOT MATCH COA - HIGHRISE DEFAULT - FAMILY COA WITH | N | D | | | HIGH-RISE ADDRESS ZIP+4 CODED TO BUILDING DEFAULT - | | | | | INDIVIDUAL NAME INFORMATION REQUIRED FOR MATCH | | | | | MISSING OR NOT MATCH COA | | | +------+-------------------------------------------------------+---------+-----+
[report condensed for illustration purposes]
56
Mover ID User’s Guide
Page 57

Summary of each output file

Subsequent pages of the report show pre- and post- move statistics and r eturn code summaries of your data broken down for each output file.
Mover ID Summary ACE [version] NCOALink Processing Summary Report Mover ID [version]
--------------------------------------------------------------------------------
Move Update Summary Per File ---------------------------------------------------
File Name: .../ace/job/output/ncoae001.dbf Filter: n/a Records Passed by Filter: 1888
Statistics (based on pre-move addresses) ---------------------------------------
Delivery Point Validation Summary (DPV)
No Stats Processed: Y
Vacant Processed: Y CMRA DPV DPV DPV Status Code Count Confirmed No Stat Vacant
-------------------------------- --------- --------- --------- ---------
Primary/Secondary Confirmed (Y) 80 0 13 0 Secondary Not Confirmed (S) 8 0 0 0 Secondary Missing (D) 1 0 0 0
-------------------------------- --------- --------- --------- --------­Total: 89 0 13 0 Total Not Confirmed: 410
Address Type Summary Records %
--------------------- ---------- -----­Street 1597 84.59 PO Box 37 1.96 High Rise 24 1.27 Rural Route 179 9.48 Firm 0 0.00 General Delivery 23 1.22 Military 0 0.00 Unique 0 0.00
--------------------- ---------- -----­Total Zip+4 Codes: 1860 98.52
Statistics (based on move-updated addresses) -----------------------------------
Forwardable Moves Records %
--------------------- ---------- -----­Individual 298 15.78 Family 0 0.00 Business 0 0.00
--------------------- ---------- -----­Total Moves: 298 15.78
Address Type Summary Records % Assignment Summary Records %
--------------------- ---------- ------ --------------------- ---------- -----­Street 1589 84.16 LACS Convertible 224 11.86 PO Box 34 1.80 Addr Level Geo Codes 1581 83.74 High Rise 28 1.48 Centroid Geo Codes 291 15.41 Rural Route 171 9.06 Firm 0 0.00 RDI Matches 1760 93.22 General Delivery 24 1.27 Military 6 0.32 Unique 0 0.00
--------------------- ---------- -----­Total Zip+4 Codes: 1852 98.09
Chapter 3: Reports and log files
57
Page 58
NCOA
Link
log files
ACE automatically generates the USPS-required log files and names them according to USPS requir ement s. If you ’re ce rtified as an NCOA only log file that you will need is the customer service log.
ACE generates these log files in the directory that you specify in the Customer and USPS Licensee Information window or block, at the Log File Directory option. With the start of each new month, ACE starts a new log file. Each log file contains information about every NCOA client.
The USPS requires that you save these log files for five years.
Log file End
users
Customer service log
PAF customer information log

Required for...
Limited ser­vice providers
Full service providers

Link
end user, the
Link
job processed that month, for every
Description
This log file contains one record per list that you process. Each record details the results of change-of-address processing. For details, see “Customer service log (CSL) and Address Conversion Statistics (ACS) file” on page 59.
This log file contains the information that you provided for the PAF .
The log file lists each unique PAF entry. If a list is processed with the same PAF informa­tion, the information appears just once in the log file.
When contact information for the list admin­istrator has changed, then information for both the list administrator and the corre­sponding broker are written to the PAF log file.
Broker agents / list administrators log
DPV false-positive log

ACE Library’s automatic log files

58
Mover ID User’s Guide


This log file contains all of the contact infor­mation that you entered for the broker or list administrator.
The log file lists information for each broker or list administrator just once.
The USPS requires the broker / list adminis­trator log file from service providers, even in jobs that do not involve a broker or list administrator. ACE produces this log file for every job if you’re a certified service pro­vider.
For details, see “False-positive log file” on page 43.
ACE creates or updates the required log files automatically during calls to ace_findf() and ace_close().
Page 59

Log file names ACE follows the USPS file-naming scheme fo r the following log files:

Customer service log PAF customer information log Brok e r agents / list administrators log
The table below describes the naming scheme. For example, P1234A08.DAT is a PAF Log file generated in October 2008 for a licensee with the ID 1234.
Character 1 Characters 2-5 Character 6 Characters 7-8 Extension

Customer service log (CSL) and Address Conversion Statistics (ACS) file

B
Broker log
C
Customer service log
P
PAF log
The NCOA
Platform ID, exactly four characters long.
Link
-required customer service log (CSL) contains a record for each
Month
1
January
2
February
3
March
4
April
5
May
6
June
7
July
8
August
9
September
A
October
B
November
C
December
run of address conversion processes, such as NC OA
Year
08
for 2008, for
example
Link
, LACS
Link
.DAT
, ANK
Link
and DPV. The USPS requires this information in this single-file format. However, because of the large file size, it can be difficult to find specific information contained in the CSL.
The ACS file contains all the sa me information that’s in the CSL, plus additional information (such as licensee name, input database name, and Mover ID “00” matches). Unlike the CSL, the ACS file contains information about only the last run. You can name the file whatever you like, choose its format, and easily find information about your most recently processed data.
Note: When you process a job using an assignment mode of Geo or Parse, ACE does not produce the ACS file.
To generate the ACS file, perform Mover ID processing, which is available in ACE as an add-on option. You can produce the ACS file with ACE Library, Views, or Job.
Note: It is possible to generate the ACS file through ACE Library without
Link
performing NCOA
processing. However , becau se most of th e data i n th e
ACS file is about move updates, if you produce the ACS file without
Link
performi ng NCOA
processing, most of the da ta in the file will be zeroes.
The ACS file contains a single record with the following fields:
Field Length Description
LICEN_ID 5 Licensee ID (USPS assigned). LIST_SIC 7 List Owner North American Industrial Classification Sys-
tem (NAICS) code.
Chapter 3: Reports and log files
59
Page 60
Field Length Description
FREQ_PROC 4 Frequency of Processing. LIST_ID 7 List ID (Licensee assigned). PROC_CAT 10 The type of processing performed. ADD_NOTES 2 Additional notes. “A” in this field means that the cus-
tomer provided written request for a longer processing period.
PROC_PRE 2 Preprocessing performed.
NNone Y Yes, but with no data modifications D Yes, data modifications from sources other than
postal data
P Ye s, data modifications from postal data only (for
example, ZIP+4 or DPV)
B Yes, data mo dific ations fro m postal an d oth er
sources
PROC_CON 2 Concurrent processes performed.
NNone Y Yes, but with no data modifications D Yes, data modifications from sources other than
postal data
P Yes, data modifications from postal data only (for
example, ZIP+4 or DPV)
B Yes, data modifications from postal and other
sources
PROC_POST 2 Post-processes performed.
NNone Y Yes, but with no data modifications D Yes, data modifications from sources other than
postal data
P Yes, data modifications from postal data only (LAC-
Link
S
)
B Yes, data modifications from postal and other
sources.
STD_OUTPUT 2 Standard output returned.
Y All NCOA
Link
-required output returned to client
N Post-processes modified return info rmation (up dates
applied to list)
B Post-processes modified return information; how-
ever, separ ate file contain ing all requir ed outp ut data was also returned
MTCH_LOGIC 2 Matching logic applied.
S Standard (business, individual, and family matches) I Individual only B Business only C Individual and business only
60
Mover ID User’s Guide
Page 61
Field Length Description
DATA _ R E T 2 Data returne d .
C COA data returned (including footnotes and p ro cess-
ing statistics)
F Footnotes (no COA data included; may include pro-
cessing statistics)
S Statistics only (no COA data or footnotes provided)
NO_MON_REQ 3 Number of months requested. By request of list owner,
number of months for which COA data accepted.
CLASS_MAIL 2 Class of mail to be used for mailings produced from cus-
tomer mailing list. A First-Class only B Periodicals only C Standard Mail only D Package Services only E First-Class and Periodicals F First-Class and Standard Mail G First-Class and Package Services H Periodicals and Standard Mail I Periodicals and Package Services J Standard Mail and Package Services K First-Class, Periodicals, and S tand ard Mail L First-Class, Periodicals, and Package Services M First-Class, Standard Mail, and Package Services N Periodicals, Standard Mail, and Package Services O First-Class, Periodical, Standard Mail, and Package
Services LIST_REC 9 Date list received from customer. PRO_BEGIN 9 Date NCOA PRO_END 9 Date NCOA
Link
processing began.
Link
processing was complete. LIST_RET 9 Date list returned to customer. RECS_PROC 11 Total number of records processed. NCOA_QURY 11 Total number of NCOALink queries performed. RECS_MTCH 11 Total number of records matched. Results returned indi-
cate return codes A, 91, 92, 01, 02, 03, 05, 14, and 19.
RECS_REJ 11 Total number of matches rejec ted. Re sul ts disc arded
based on Move Effective Date: Retu rn cod e 00 gen erated
due to age of COA. RECS_ZIP4 11 Total number of records ZIP+4 coded. RECS_DPV 11 Total number of records DPV confirmed. SW_NAME 31 ZIP+4 software name. SW_VERSION 13 ZIP+4 software version. Z4_DIRDATE 9 ZIP+4 directory release date.
Link
NCO_SWNAME 31 NCOA
software name.
Chapter 3: Reports and log files
61
Page 62
Field Length Description
NCO_SWVER 13 NCOA NCO_DIRDAT 9 NCOA
Link
software ve rs i on .
Link
data release date. DPV_SWNAME 31 DPV software name. DPV_SWVER 13 DPV software version. DPV_DIRDAT 9 DPV data release date. ZIP4_POBOX 11 ZIP+4 match statistics. Total matched to PO box. ZIP4_HCBOX 11 ZIP+4 match statistics. Total matched to HCR exact. ZIP4_RR_DF 11 ZIP+4 match statistics. Total matched to RR default. ZIP4_FIRM 11 ZIP+4 match statistics. Total matched to firm. ZIP4_GD 11 ZIP+4 match statistics. Total matched to general delivery. ZIP4_HR_DF 11 ZIP+4 match statistics. Total matched to highrise default. ZIP4_MIL 11 ZIP+4 match statistics. Total matched to military. ZIP4_NONDE 11 ZIP+4 match statistics. Total matched to nondeliverable. ZIP4_RRBOX 11 ZIP+4 match statistics. Total matched to RR exact. ZIP4_ST 11 ZIP+4 match statistics. Total matched to street. ZIP4_HCDEF 11 ZIP+4 match statistics. Total matched to HCR default. ZIP4_HRSEC 11 ZIP+4 match statistics. Total matched to highrise exact. ZIP4_OTHER 11 ZIP+4 match statistics. Total matched to other. ZIP4_LACS 11 ZIP+4 match statistics. Total matched to positive LACS. ZIP4_EWS 11 ZIP+4 match statistics. Total matched to EWS. RETCODE_A 11 NCOA
address provided by NCOA
RETCODE_91 11 NCOA
address provided by NCOA secondary address and matched NCOA
Link
return code A. NCOA
Link
return code 91. NCOA
Link
Link
Link
match. New
. Exact match.
Link
match. New
. Input record was missing
Link
record that
had a secondary address.
RETCODE_92 11 NCOA
address provided by NCOA secondary address and matched NCOA
Link
return code 92. NCOA
Link
Link
match. New
. Input record contained
Link
record that
was missing secondary address. RETCODE_00 11 NCOA RETCODE_01 11 NCOA
Link
return code 00. No NCOA
Link
return code 01. NCOA
Link
match.
Link
match. Foreign
move. RETCODE_02 11 NCOA
Link
return code 02. NCO A
Link
match. Moved Left
No Address (MLNA). RETCODE_03 11 NCOA
Link
return code 03. NCOA
Link
match. Box Closed
No Order (BCNO). RETCODE_04 11 NCOA
Link
return code 04. No NCOA
Link
match. Family
move from street address with second ary.
62
Mover ID User’s Guide
Page 63
Field Length Description
RETCODE_05 11 NCOA
Link
return code 05. NCOA
digit delivery point barcode (DPBC) is ambiguous.
Link
RETCODE_06 11 NCOA
return code 06. No NCOA
names or initials don’t match.
RETCODE_07 11 NCOA
Link
return code 07. No NCOA
don’t match.
Link
RETCODE_08 11 NCOA
return code 08. No NCOA
flicting new addresses.
Link
RETCODE_09 11 NCOA
return code 09. No NCOA
move from highrise default.
RETCODE_10 11 NCOA
Link
return code 10. No NCOA
move from rural route or highway contract default.
Link
RETCODE_11 11 NCOA
return code 11. No NCOA
ual move, insufficient name data.
Link
RETCODE_12 11 NCOA
return code 12. No NCOA
name test failed.
RETCODE_13 11 NCOA
Link
return code 13. No NCOA
test failed.
Link
RETCODE_14 11 NCOA
return code 14. NCOA
address would not convert.
Link
RETCODE_15 11 NCOA
return code 15. No NCOA
ual name insufficient on input to match.
RETCODE_16 11 NCOA
Link
return code 16. No NCOA
ary number discrepancy.
Link
RETCODE_17 11 NCOA
return code 17. No NCOA
ent first name.
Link
RETCODE_18 11 NCOA
return code 18. No NCOA
move from General Delivery.
RETCODE_19 11 NCOA
Link
return code 19. NCOA
address not ZIP+4 codeable.
Link
RETCODE_20 11 NCOA
return code 20. No NCOA
ple response, conflicting directions.
Link
match. New 11
Link
match. Middle
Link
match. Genders
Link
match. Con-
Link
match. Family
Link
match. Family
Link
match. Individ-
Link
match. Middle
Link
match. Gender
Link
match. New
Link
match. Individ-
Link
match. Second-
Link
match. Differ-
Link
match. Family
Link
match. New
Link
match. Multi-
RETCODE_21
through
11
To be defined.
RETCODE_30 RETCODE_66 11 NCOA
Link
return code 66. No NCOA
Link
match. Input
address appears in “Daily Delete” suppression file. DPV_AA 11 DPV footnotes . ZIP+4 match. DPV_A1 11 DPV footnotes. No ZIP+4 match. DPV_M1 11 DPV footnotes. Primary number missing. DPV_M3 11 DPV footnotes. Primary number invalid. DPV_P1 11 DPV footnotes. Missing PO, RR, or HC Box number.
Chapter 3: Reports and log files
63
Page 64
Field Length Description
DPV_P3 11 DPV footnotes. Invalid PO, RR, or HC Box number. DPV_BB 11 DPV footnotes. DPV matched (all components). DPV_RR 11 DPV footnotes. DPV matched to Commercial Mail
Receiving Agency (CMRA).
DPV_CC 11 DPV footnotes. Primary number match; secondary
present but invalid.
DPV_N1 11 DPV footnotes. Primary number match. Secondary miss-
ing.
DPV_R1 11 DPV footnotes. DPV matched to CMRA. Personal Mail
Box (PMB) number not present.
ADD_MON_0
through
ADD_MON_48
11 Total number of matches made with Move Ef fective Date
(MED) correspon din g to the proce ss date . Addr esse s matched month 0 – 48.
OPER_ID 7 Operator ID. Identificatio n code for the oper ator w ho pr o-
cessed this list.
BUY_CO_NAM 31 Buyer company name. If the processed list was for rent,
sale, or lease, this is the name of the compan y (or in div id­ual) purchasing the list.
MAIL_ZIP 6 Mailing ZIP Code. ZIP Code of Bus iness Mail Entry Un it
(BMEU) or post office at which mail will be submitted
for mailing. DPV_ST_VAL 11 DPV statistics. Street (S) records validated. DPV_ST_CP 11 DPV statistics. Street (S) records validated. CMRA pre-
sented. DPV_ST_CV 11 DPV statistics. Street (S) records validated. CMRA vali-
dated. DPV_HIR_RV 11 DPV statistics. Highrise (H) records validated. DPV_HIR_CP 11 DPV statistics. Highrise (H) record s validated. CMRA
presented. DPV_HIR_CV 11 DPV statistics. Highrise (H) records validated. CMRA
validated.
64
DPV_POB_RV 11 DPV statistics. PO box (P) records validated. DPV_RR_RV 11 DPV statistics. RR/HC (R) records validated. DPV_RR_CP 11 DPV statistics. RR/HC (R) recor ds v alidated. CM RA pr e-
sented. DPV_RR_CV 11 DPV statistics. RR/HC (R) records validated. CMRA val-
idated. DPV_FRM_RV 11 DPV statistics. Firm (F) records validated. DPV_FRM_CP 11 DPV statistics. Firm (F) records validated. CMRA pre-
sented. DPV_FRM_CV 11 DPV statistics. Firm (F) records validated. CMRA vali-
dated.
Mover ID User’s Guide
Page 65
Field Length Description
DPV_GD_RV 11 DPV statistics. General delivery (G) records validated. DPV_PE_TOT 11 DPV statistics. Total primary number error. DPV_PE_ST 11 DPV statistics. Street (S) records with primary number
error.
DPV_PE_HIR 11 DPV statistics. Highrise (H) records with primary number
error.
DPV_PE_POB 11 DPV statistics. PO box (P) records with primary number
error.
DPV_PE_RR 11 DPV statistics. RR/HC (R) records with primary number
error.
DPV_PE_FRM 11 DPV statistics. Firm (F) records with primary number
error. DPV_SE_TOT 11 DPV statistics. Total secondary number error. DPV_SE_ST 11 DPV statistics. Street (S) records with secondary number
error. DPV_SE_HIR 11 DPV statistics. Highrise (H) records with secondary num-
ber error. DPV_SE_FRM 11 DPV statistics. Firm (F) records with secondary number
error. LAC_SWNAME 31 LACS LAC_SWVER 13 LACS LAC_DIRDAT 9 LACS LAC_RET_A 11 LACS LAC_RET_00 11 LACS LAC_RET_14 11 LACS
Link
software name.
Link
software version.
Link
data release date.
Link
return codes. LACS record match.
Link
return codes. No match.
Link
return codes. Found LACS record. New
address would not convert.
Link
LAC_RET_92 11 LACS
return codes. Match with secondary number
dropped on input. DPV_RET_F1 11 DPV additional return codes. Military. DPV_RET_U1 11 DPV additional return codes. Unique ZIP Code. DPV_RET_G1 11 DPV additional return codes. General delivery. DPV_RET_NL 11 DPV additional return codes. New address not DPV con-
firmable with vendor software. ANK_RET_A,
ANK_RET_00
through
11 ANK
same as NCOA
Link
return codes. ANK
Link
return code s.
Link
return codes are the
ANK_RET_20, ANK_RET_66, ANK_RET_92, ANK_RET_91
TOT_ANKMAT 11 Total records matched using ANK
Link
.
Chapter 3: Reports and log files
65
Page 66
Field Length Description
LAC_RET_09 11 LACS
Link
Return Codes. Old address highr ise default, no
new address.
Link
TOT_LACCON 11 Total records LACS
converted. MLIST_NAME 31 User given list name. LIC_NAME 31 Licensee name. INP_DB 200 Input file. CUST_CONAM 51 Customer company name. STE_SWNAME 31 SuiteLink software name. STE_SWVER 13 SuiteLink software version. STE_DIRDAT 9 SuiteLink directory date. STE_RET_A 11 SuiteLink return code “A” matches. STE_RET_00 11 SuiteLink return code “00” matches IND_MOVES 11 The number of individual moves in the job. FAM_MOVES 11 The number of family moves in the job. BUS_MOVES 11 The number of business moves in the job. DIR_FORMAT 4 Directory format (hash or flat).
Link
DIR_MONTHS 4 Number of months in the NCOA DIR_TYPE 8 Type of directory (NCOA
Link
directory (18 or 48).
or ANK
Link
).
HI_MTC_DSC 1 High match rate description (A, S, R, or bla nk). See
“High Match Ra te Description” on page 27.
66
Mover ID User’s Guide
Page 67
Chapter 4: Certification and audits
Chapter summary As an NCOA
Link
NCOA certification. These steps are described in this chapter.
user, you must also follow certain USPS procedures during your initi al
Link
licensee, you will experience periodic USPS audits. As an
Chapter 4: Certification and audits
67
Page 68
NCOA
Link
certification and audits

Refer to the USPS The information below is based on NCOA

Link
information from the USPS. If you have questions about certifica tion or audit proced ures, contact your USPS accoun t representative or the USPS National Customer Support Center in Memphis.

Certification and audit procedure

During certification, you must process a file from the USPS to prove that you adhere to the requirements of your license agreement.
An audit involves processing a test file, which the US PS provides, and creat ing an output file in a USPS-specif ie d format. This output file is called the Test Client Output File.
You send the Te st Cl ient Output File to the USPS for grading i n Stage I and S tag e II testing and also during auditing.
The USPS will send you the input file and will determ ine the output file name.

Preparing your test job Business Objects provides the following files to assist you in passing an audit:

ncoastg1.ace, the template ACE job file for NCOA ncoastg1.fmt, the format file for NCOA ncoastg1.def, the definition file for NCOA
ncoastg2.ace, the template ACE job file for NCOA ncoastg2.fmt, the format file for NCOA ncoastg2.def, the definition file for NCOA
Link
Stage I pre-testing
Link
Link
Stage II testing
Link
Link
Stage I pre-testing
Stage I pre-testing
Link
Stage II testing
Stage II testing
These files are in the tem plate subdirectory (pw\ace\template or postware/ace/ template). Copy all of them to a differen t subdirectory.
Do not edit these three files directly. Instead, make a copy of them, and edit the copy. When you receive a newer version of ACE, always use the newest version of these three files. They are installed with each new version of ACE.
When editing your copy of the template file, set up the job as usual. In particular, check all of the parameters that require a file path name, t he Mover ID NCOA
Link
blocks, and Mover ID Summary report blocks. As required, this audit job produces the Mover ID Summary report, CASS 3553 form, and an output file in USPS-specified format.
When using the ncoastg1.ace and ncoastg2.ace files, change the output file
!
name to $job_out.dat. Otherwise the default FMT and DEF files will be overwritten and won’t work with the USPS-supplied input file for the next job.
After processing the job, the auditor may ask you to display results on your computer, and to copy all of the reports and outputs back to the USPS tape or diskette. That tape or diskette normally goes back to the NCSC in Memphis for evaluation.
The audit team may also want to check out other things like how files are
Link
processed through NCOA agreement and the NCOA
. For complete information, read your license
Link
technical documentation , or check wit h your USPS
contracting officer.
68
Mover ID User’s Guide
Page 69
Appendix A: Improving NCOA
Link
performance

Overview Many factors affect ACE’s performance when running NCOA

most critical factor is the amount of disk access taking place, and there are ways to reduce it. Having lots o f memory available for cachin g data is often the most effective way of reducing disk access. Other critical factors include hard drive speed, seek time, and the sustained transfer rate. When the time spent on disk access is minimized, the performance of the CPU becomes significant.
Link
. Generally the
Appendix A: Improving NCOALink performance
69
Page 70
What hardware and OS are best for NCOA
Link
processing?

Operating systems and processors

Some people mistakenly assume that a high-priced 64-bit UNIX system with multiple processors and many gigabyte s of RAM will run an NCOA
Link
job much faster than a common single-processor 32-bit PC. The real strengths of such a UNIX system come into play when you process multiple jobs at once. However, some processors are better at diffe rent types of comp utation, and t he computat ion involved in most ACE and NCOA
Link
processing is very wel l suited to the microprocessors found in most computer s, such as t hose made by Intel a nd AMD. RISC style processors like those found in most UNIX systems are generally substantially slower for this type of computation. In fact a common PC can often run a single job through ACE and NCOA
Link
about twice as fast as a common UNIX system. If you’re looking for a cost-effective way of processing single jobs, a Windows server or a fast workstation can produce excellent results.
Most UNIX systems have multiple processors and are at their best processing several jobs at once. If you process millions of records in a single large job, you can split the job into multiple smaller jobs, each co ncurrently processing only a subset of your input file. With the system dividing the load between the multiple processors, you may see outstanding overall processing speeds.
If you’re running on a UNIX operating system, we recommend that you run on a 64-bit platform, with 64-bit software. The software will cache more when running in 64-bit mode.

Memory NCOA

your service provider level, the data format, and the release of the data from the USPS. The data may be 7 gigabytes (GB) or twice that size. Accessing any amount of data from a hard drive takes much longer than all the computation involved in an NCOA makes a tremendous difference in performance.
How much memory is enough? Having even a few hundred megabytes available for ACE to use when caching NCOA difference. One test showed a job running at several hundred thousand records per hour with 200 MB cached, when the same job ran at only one thousand records per hour without that memory available.
In general, if performance is critical, and especially if you are a Full Service Provider and you frequently run very large jobs with millions of records, you should get as much memory as you can. You may want to go as far as caching the entire NCOA with enough left for the operating system. If your typical jobs are less than a million records, you may find your performance is adequate with 2 to 4 GB of RAM available to ACE.
For reasonable performance, your computer should have at least 3 GB of RAM. This provides enough RAM to maximize processing of CASS, and DPV, and to achieve good performance with NCOA you may need additional RAM.
Link
processing uses many gigabytes of data. T he exact amount depends on
Link
lookup, so getting the necessary data into memory
Link
directory data can make a huge
Link
data set. Having 20 GB of RAM installed should allow for that,
Link.
To achieve maximum performance
70
Mover ID User’s Guide
Page 71

Data storage When ACE does need to access a hard drive for NCOA

performance becomes a critical factor in the overall performance. Hard drive access occurs either:
during the process of caching large quantities of directory data to use in the
future, or
retrieving relatively small amounts of data directly from the hard drive if it
could not be cached
Link
In any case, the hard drive you use for NCOA
data should be fully dedicated to that process, at least while your job is running. Other processes competing for the use of the same physical disk drive can greatly reduce your NCOA performance.
In the first case, the sustained tra nsfer rate of your hard drive is its most significant feature. For example, if you are going to cache 10 GB of data, that’s 10 GB of mostly linear disk access. If your hard drive can maintain a transfer rate of 50 MB per second, populating the cache will take several minutes. A low­performance hard drive, a badly fragmented hard drive, or a hard drive being accessed over a busy network or other bottleneck may not be able to deliver half that transfer rate, so the time required to cache the data could be doubled or worse.
If you will be caching large volumes of data and you have an older hard drive, you may want to consider an upgrad e. High-RPM model s are desirable, bu t so are drives featuring a large data capacity per platter, as these high capacity drives generally offer excellent transfer rates. Packing data more densely on the platters not only increases storage capacity but also increases the amount of data transferred in each revolution of the disk. To achieve even higher transfer rates you may want to explore the possibility of using a RAID system.
Link
When ACE accesses NCOA
data directly rather than from a cache, the most significant hard drive feature is the average seek time. The amount of data ACE needs to perform a single lookup is very small, but it may be distributed among several files, requiring several seeks. Each seek typically requires several milliseconds which is much longer than it takes to actually transfer the data. Thus if you’re not going to be cachi ng several GB o f dat a, su staine d t ransfer rat e is not as significant.
Link
, hard drive
Link
Appendix A: Improving NCOALink performance
71
Page 72

What caching and data format strategy is best?

Data format ACE supports both hash and flat file versions of NCOA

Link
data. If you have ample memory to cache the entire hash file data set, that format may provide the best performance. The flat file data is significantly smaller, which means a larger share can be cached in a given amount of RAM. But accessing the flat file data also involves binary searches, which are slightly more time consuming than the direct access used with the hash file format. If you have very limited memory (less than 600 MB availabl e for NCOA
Link
caching), the hash file format is likel y to provide better performance because the binary searches involved in accessing the flat file version are particularly time cons uming when the data is on a hard drive.

ZIP order caching If you are processing very large lists, you would ideally cache the entire data set,

but you may not have the vast amounts of RAM required to do that. If you have a few GB available and very large or very regional lists in ZIP Code order, either sorted by turning on the Z I P C ode sort i ng option within ACE or if yo ur input file is already in ZIP Code order, you may want to consider enabling ZIP order caching.
Link
The ZIP order caching option tells ACE to cache a portion of the NCOA
data required for similar ZIP Codes at a time, reusing that memory later to cache another portion of the data. After a segment of the data has been cached, all the addresses with the same first two digits of the ZIP Code can be processed without much additional disk access. Thus for those addresses you can achieve nearly CPU-bound performance, which may be in the millions of records per hour. Essentially, enabling this feature puts a finite limit on the amount of disk access that ACE may do for a single NCOA
Link
job. The amount of disk access is large, close to four times the size of the data set. Thus it’s possible for a job to do about 60 gigabytes of disk readi ng, but for l arg e or highly re gional j obs the result can be a substantial improvement in performance. As jobs get larger, the performance gain from using the ZIP order caching feature also increases.
72
ZIP order caching isn’t always appropriate. If your list contains only a few thousand records destined for addresses distributed throughout the country, the time saved by having that data cached may be less than the time it takes to cache it. The data ACE caches for each 2-digi t ZIP Code may be ov er 500 megabytes. If there aren't many addresses with a given 2-digit ZIP Code, turning on ZIP order caching may actually decrease performance significantly. It's impossible to identify a specific minimum number of records per 2-digit ZIP Code that you would need before ZIP order caching becomes beneficial . That threshold depe nds on the transfer rate and seek time of your hard drive, the format of the data, and many other variables.
Setting up the ZIP order option:
In ACE V iews or Jobfile, go to the M emory Usage window or b lock and
select the Cache for ZIP Order Processing option.
In ACE Library, call
ace_set_mode(ah, ACE_MODE_CACHE_ZIP_ORDER, TRUE);
Mover ID User’s Guide
Page 73

Memory usage The NCOA

control how much memory to use for caching. The optimal amount of memory depends on a great many factor s. The “Aut o” option wi ll usu ally d o a good job of deciding how much memory to use, but in some cases manually adjusting the amount can be worthwhile. In general, to get good performance when you are processing an input file with millions of records, you should dedicate as much memory to caching NCOA records in a job, the optimal amount of memory to dedicate to caching will probably be between a few hundred megabytes and two gigabytes. Within that range the difference in performance is usually fairly minor.
Link
parameters in the Memory Usage block of ACE allow you to
Link
data as possible. If you have less than a million
Appendix A: Improving NCOALink performance
73
Page 74

Tips

Many factors can increase or decrease processing speed. Some are within your control and others may be inherent to your business. Here are some to consider:
RAM You should have at least 2GB of available RAM for each process of ACE with

Input order Processing in ZIP Code order allows ACE to process many records for each

Link
NCOA
you will be running concurrently. For very large jobs, the more
memory you can dedicate to NCOA
Link
, the better.
access of a hard drive for directory data.

ZIP Code order caching

This feature is only beneficial for large jobs, and the minimum size to get that benefit will depend on your hardwar e and data. For a small j ob turning this on ca n decrease performance dramatically. If you’re in doubt, try toggling this option.

Cache size Using too little mem ory for NCOA

Link
caching can cause unnecessary random file access and time-consuming hard drive seeks. Using far too much can cause large files to be read from the disk into the cache even when only a tiny fraction of the data will ever be used.

CPU Speed If your jobs and run-time environment minimize disk access, the speed of your

CPU is the limiting factor in your performance.

Directory location It’s best to have NCOA

RAM drive. This eliminates all IO for NCOA
Link
directories on a local solid state drive or a virtual
Link
while processing the job. If you have them on a hard drive, it’s best to use a defragmented local hard drive. The hard drive should not be accessed for anything other than the NCOA
Link
data while you are running. Using a hard drive over a network or a drive that is being accessed by other processes can reduce your processing speed dramatically.

Match rate The more records you process that have forwardable moves, the slower your

processing will be. Retrieving and decoding the new addresses takes time, so updating a list regularly will improve the processing speed on that list. You can measure the impact of your match rate on y our perfo rmance by alter ing your DE F file to use a constant name for all the records, re boot i ng, and r erunni ng the job. If you tell ACE that the name is always “Nosuch Personexists” you will get no matches and you'll see faster processing. The difference in processing times is how long ACE spent dealing with NCOA
Link
matches when you first ran the job
with real data.

Input format Ideally you should provide ACE with discrete fields for the addressee’s first,

middle, and last name, as well as for the pre-name and post-name. If your input has only a name line, ACE will have to take time to parse it before doing
Link
NCOA
. If your file is in multi -line format , ACE may have to analyze multiple lines to determine which is the address line and then parse the selected line into discrete components. This will obviously slow things down.
74
Mover ID User’s Guide
Page 75

File size Large files process faster. There is overhead when processing any job, but if a j ob

includes millions of records, a few sec onds o f overh ead becomes insignificant. A few seconds per job is much more significant if you have hundreds of smaller jobs.
Appendix A: Improving NCOALink performance
75
Page 76

Are there any special strategies that might help?

In some cases there are things you can do that will help a great deal.

Software RAM drives If you process millions of records every day, but those records are contained in

many separate input files, or you need to process them in numerous separate jobs with different settings, you may not be able to benefit from caching lar ge amounts of data within ACE, even if you have ample RAM. You may be able to achieve extremely good results by caching the data externally, however.
Software RAM drives are readily available for many operating systems. These programs allow you to use some of you r syst em memory to create a virtual drive. If you have enough RAM available to create a virtual RAM drive that can accommodate the full NCOA achieve performance exceeding a million records per hour. Once the data is loaded onto the RAM drive, every ACE job that uses it can get the full benefit of caching without spending any additional time loading its internal cache.
Link
Set ACE’s NCOA
cache size to around 50 MB, an d specify th e RAM drive as the location for the data files, and if you are processing in ZIP Code order, your job will be CPU-bound. If you have RAM to spare, consider putting your ZIP4_US.DIR and other ACE directories on the RAM drive as well. That will allow you to process at CPU speeds without the need to process in ZIP Code order.
Link
data set, that may be your quickest way to

Hardware RAM drives Another possibility is using a har dware RAM dri ve for your NCOA

directory data. These drives can be installed like a hard drive, but they use memory to store data without any moving parts. Their performance is much better than a hard drive, but they are also quite expensive. Some models use Flash memory , which has t he advanta ge of being non- vola tile, so your data stay s on the drive even after re-booting the computer. Other models use conventional memory. They offer better performance than those using Flash memory, but they requiring loading the data every time the computer is booted.
Link
and other
76
Mover ID User’s Guide
Page 77

Index

A
Accepted COA Months option, 27, 28 ACE Execution Options window, 21 ACE_IFIRM, 20 ACE_IFirst_Name, 20 ACE_ILast_Name, 20 ACE_ILINE1-12, 20 ACE_IMid_Name, 20 ACE_INAME, 20 ACE_IPost_Name, 20 ACE_IPre_Name, 20 ACE_MID_CACHE_MB, 40 ACE_MODE_CACHE_ZIP_ORDER, 40 ACS file, 59 ACS file format, 59 ADD_MON_0 through ADD_MON_48, 64 ADD_NOTES, 60 Additional Notes option, 31 Address Conversion Statistics (ACS) file, 59 Address Conversion Statistics file, 59 Alternate Company Name option, 33 ANK, 10 ANK_RET_00 through ANK_RET_20, 65 ANK_RET_66, 65 ANK_RET_91, 65 ANK_RET_92, 65 ANK_RET_A, 65 ANKLink, 10 AP fields, 45 APM fields, 45 appending new address, 47 Attempted - Not Known, 10 auto update, 42 Auxiliary Files window, block, 22
B
boot.ini, 37 broker, 30
contact information, 34 Broker Involved option, 30 BUS_MOVES, 66 Business Mail Entry Unit (BMEU) or Post Office ZIP Code
, 30
option business match logic, 26 BUY_CO_NAM, 64 Buyer Company Name option, 30
C
Cache for ZIP Order Processing option, 36, 38 caching, 36, 37 CLASS_MAIL, 61 cloning input, 47 COA Mode setting, 26
Concurrent Process Changes With Other Data option, 31 Concurrent Process Changes With Postal Data option, 31 Concurrent Processes Performed option, 31 Contact Address option, 35 Contact City option, 35 Contact ID option, 34 contact information
broker or list administrator
Contact Name option, 35 Contact Plus 4 Code option, 35 Contact State Code option, 35 Contact Tax ID Number option, 35 Contact Telephone Number option, 35 Contact Type option, 34 Contact ZIP option, 35 CSL, 59 CUST_CONAM, 66 Customer & USPS Licensee Information window, block, 23 Customer Address option, 24 Customer Altern a te C ompany option, 33 Customer City option, 24 Customer Company Name option, 24 Customer Parent Company option, 33 Customer Phone option, 24 Customer service log, 59 customer service log, 58 Customer State option, 24 Customer Tax ID Number option, 24 Customer ZIP option, 24 Customer ZIP4 option, 24 Customer/List ID option, 24
, 34
D
daily delete file, 17 data format, 19 DATA_RET, 61 Date List Received option, 25 Date PAF Signed by Cu stomer option, 33 Date PAF Signed by Li censee option, 33 DEF setup, 19 Delivery Point Validation
false-positive log
memory, 41 DIR_FORMAT, 66 DIR_MONTHS, 66 DIR_TYPE, 66 directories
NCOALink discrete name fields, 19 DPV
false-positive log
memory, 41
unlocking, 44
, 43
, 16
, 43, 58
Index
77
Page 78
DPV_A1, 63 DPV_AA, 63 DPV_BB, 64 DPV_CC, 64 DPV_DIRDAT, 62 DPV_FRM_CP, 64 DPV_FRM_CV, 64 DPV_FRM_RV, 64 DPV_GD_RV, 65 DPV_HIR_CP, 64 DPV_HIR_CV, 64 DPV_HIR_RV, 64 DPV_M1, 63 DPV_M3, 63 DPV_N1, 64 DPV_P1, 63 DPV_P3, 64 DPV_PE_FRM, 65 DPV_PE_HIR, 65 DPV_PE_POB, 65 DPV_PE_RR, 65 DPV_PE_ST, 65 DPV_PE_TOT, 65 DPV_POB_RV, 64 DPV_R1, 64 DPV_RET_F1, 65 DPV_RET_G1, 65 DPV_RET_NL, 65 DPV_RET_U1, 65 DPV_RR, 64 DPV_RR_CP, 64 DPV_RR_CV, 64 DPV_RR_RV, 64 DPV_SE_FRM, 65 DPV_SE_HIR, 65 DPV_SE_ST, 65 DPV_SE_TOT, 65 DPV_ST_CP, 64 DPV_ST_CV, 64 DPV_ST_VAL, 64 DPV_SWNAME, 62 DPV_SWVER, 62
E
Emp Train processin g category, 27, 28 enabling move- u pd a ting, 21 Execution block, 21 Extended Memory Usage option, 40 extension request, 31
F
FAM_MOVES, 66 fields
, 45
AP APM, 45
format, 19 format of data, 19 FREQ_PROC, 60
H
hardware recommendations
NCOALink
HI_MTC_DSC, 66 High Match Rate Description option, 27, 28
, 16
I
IMB Mailer ID, 24 IND_MOVES, 66 individual match logic, 26 individual with bus ine ss ma tch l og ic, 26 INP_DB, 66 installing
daily delete file
NCOALink directories and files, 16 Insufficient Memory Action option, 41 Int Db Tst processing category, 27, 28
, 17
L
LAC_DIRDAT, 65 LAC_RET_00, 65 LAC_RET_09, 66 LAC_RET_14, 65 LAC_RET_92, 65 LAC_RET_A, 65 LAC_SWNAME, 65 LAC_SWVER, 65 LIC_NAME, 66 LICEN_ID, 59 licensee
NCOALink Licensee ID, 59 list administrator, 30
contact information, 34 List Administrator Involved option, 30 List ID, 60 List Name option, 29 List Owner NAICS option, 24 LIST_ID, 60 LIST_REC, 61 LIST_RET, 61 LIST_SIC, 59 locking pages in memory, 38 log file
e-mail to USPS
false positive, 43 Log File Directory option, 25 log files, 51
naming convention, 59
NCOALink, 58
, 23
, 44
M
mail class codes, 61 mail options, 26 MAIL_ZIP, 64 Mailing ZIP Code option, 30 match logic, 26 Match Logic option, 26 match rate, 27, 28 memory usage, 36 Memory Usage window, block, 38 Memory Window Si ze option, 40 Mktg Test processing category, 27, 28
78
Mover ID User’s Guide
Page 79
MLIST_NAME, 66 Mode option, 26 Mover ID
introduction
Mover ID Auto Update option, 42 Mover ID Contact Infor mation window, block, 34 Mover ID NCOALink Service Provider window, block, 30 Mover ID NCOALink window, block, 26 Mover ID Summary report, 52 move-update re quirement, 8 move-updating
diagram introduction, 7 NCOALink, 8
set up ACE, 15 MTCH_LOGIC, 60 multiline fields, 19
, 7
, 9
N
NAICS, 24, 34 NAICS code, 59 Name of the Person Signing PAF option, 33 name-line field, 19 National Customer Support Center, 11 NCO_DIRDAT, 62 NCO_SWNAME, 61 NCO_SWVER, 62 NCOA_QURY, 61 NCOALink, 8
broker, 30
customer service log, 59
daily delete file, 17
directories, 16
files, 16
hardware recommendations, 16
licensee, 23
list administrator, 30
overview, 7
service provider, 30
set up ACE, 19 NCOALink Contact NAICS option, 34 NCOALink Directory option, 22 NCOALink log files, 58 NCOALink Manual Allocation optio n , 39 NCOALink Memory option, 38, 39 NCOALink Name Parsing files, 22 NCSC, 11 NO_MON_REQ, 61 Normal processing category, 27, 28
O
OPER_ID, 64 output file, 47 Output Returned option, 31
P
PAF, 32 PAF customer information log, 58 PAF log file, 33 PAF Type option, 33 Parent Company option, 33
parsing name lines, 46 password protection, 12 Perform Mover ID NCOALink option, 21 permissions, 38 Person Signing PAF option, 33 Post-Process Changes With Other Data option, 31 Post-Process Changes With Postal Data option, 31 Post-Processes Performed option, 31 Pre-Process Changes With Other Data option, 31 Pre-Process Changes With Postal Data option, 31 Pre-Processes Performed option, 31 PRO_BEGIN, 61 PRO_END, 61 PROC_CAT, 60 PROC_CON, 60 PROC_POST, 60 PROC_PRE, 60 Processes Used to Prepare List option, 29 Processing Acknowledgement Form, 32 Processing Category option, 27, 28 Processing First Class Mail option, 27, 28 Processing Frequency option, 24 processing options, 26 Processing Package Services Mail option, 27, 28 Processing Periodicals Mail op tion, 27, 28 Processing Standard Mail option, 27, 28 PW.Firm, 20 PW.First_Name, 20 PW.Last_Name, 20 PW.Line1-12, 20 PW.Mid_Name, 20 PW.Name_Line, 2 0 PW.Post_Name, 20 PW.Pre_Name, 20
R
RECS_DPV, 61 RECS_MTCH, 61 RECS_PROC, 61 RECS_REJ, 61 RECS_ZIP4, 61 replacing old address with new, 42 reports, 51 request for extension, 31 residential match logic, 26 Retcode setting, 26 RETCODE_00, 62 RETCODE_01, 62 RETCODE_02, 62 RETCODE_03, 62 RETCODE_04, 62 RETCODE_05, 63 RETCODE_06, 63 RETCODE_07, 63 RETCODE_08, 63 RETCODE_09, 63 RETCODE_10, 63 RETCODE_11, 63 RETCODE_12, 63 RETCODE_13, 63 RETCODE_14, 63 RETCODE_15, 63
Index
79
Page 80
RETCODE_16, 63 RETCODE_17, 63 RETCODE_18, 63 RETCODE_19, 63 RETCODE_20, 63 RETCODE_21 through RETCODE_30, 63 RETCODE_66, 63 RETCODE_91, 62 RETCODE_92, 62 RETCODE_A, 62 return codes, 26, 52, 53, 55, 56, 57, 62, 63, 65
S
security, 11 service provider
NCOALink
set up ACE for move-updating, 15 Stage I processing category, 27, 28 Stage II processing category, 27, 28 Standard Industrial Classification, 34 standard match logic, 26 Standardization Style window, block, 42 Stats setting, 26 STD_OUTPUT, 60 STE_DIRDAT, 66 STE_RET_00, 66 STE_RET_A, 66 STE_SWNAME, 66 STE_SWVER, 66 SW_NAME, 61 SW_VERSION, 61 Sys Test processing categ or y, 27, 28
, 30
T
Title of Person Signing PAF option, 33
TOT_ANKMAT, 65 TOT_LACCON, 66 Type of PAF option, 33
U
unlock
DPV
, 44
unlock code
retrieving
, 44
W
web site
USPS RIBBS
Windows Memory Window Size parameter, 40 Windows Use Extended Memory parameter, 40
, 13
Z
Z4_DIRDATE, 61 ZIP Code order, 36 ZIP4_EWS, 62 ZIP4_FIRM, 62 ZIP4_GD, 62 ZIP4_HCBOX, 62 ZIP4_HCDEF, 62 ZIP4_HR_DF, 62 ZIP4_HRSEC, 62 ZIP4_LACS, 62 ZIP4_MIL, 62 ZIP4_NONDE, 62 ZIP4_OTHER, 62 ZIP4_POBOX, 62 ZIP4_RR_DF, 62 ZIP4_RRBOX, 62 ZIP4_ST, 62
80
Mover ID User’s Guide
Loading...