Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
The Utilities menu contains a variety of options that support the other areas of Circulation. The mass rerouting and address hygiene utilities, the purge programs, and the View/Print Utility are only a few of the options available.
It should be noted that many of these utilities are powerful programs that can significantly change or delete data in the Circulation system. You should use caution when running them.
Most Utilities options are run from Circulation’s older character interface. Some, however, have been ported to the new Graphical Utilities module.
This section guides the user through the menu options that are available under the Account menu.
This section guides the user through the menu options that are available under the Audience menu.
The Utilities menu contains options for maintaining system resources and history, producing custom programs and reports, and performing various setup activities.
Topics covered in this section are as listed below:
PostWare (The options on this menu are described in the document entitled Postware and Label Studio.)
The Draw Export feature allows account draw figures for a given date range to be exported to an ASCII file in the /dti/exchange/cm
directory (see Appendix B for the file format). The file will contain a single cumulative draw figure for the account. For example, if the draw export was run for 10/01 - 10/07, the total draw for each account within that seven-day period would be exported.
Select Draw Export from the Account menu to display the Account Draw Export Utility screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the publication for which you are exporting draw.
START DATE, END DATE
date
Enter the date range for which to export draw. The total draw for this date range will be exported for each account.
ROUTE TYPE
setup
Enter the route type for which to select accounts, or enter “*” to multi-select route types. Only accounts with routes of this route type will be selected.
FILE NAME
open (20)
Enter a name for the ASCII file. The file will be exported to /dti/exchange/cm.
Select Continue to export the draw figures. After processing is completed, a report will list the number of records exported and any errors that occurred during the process.
AAM reporting is done by Town of 25 and Zip code. Because home delivery routes may cross AAM zone, Town of 25 or Zip code boundaries, it is necessary to know what percentage of a route’s draw lies in each area. The percentages are set up with the route (see Distribution Point in the Setup Manual), and when the publishing run ends (or returns or adjustments are entered) the percentages are used to update AAM history. The AAM reports are based on this history.
Note: Business Rules determine whether AAM history is kept by Zip code.
For example, let’s say route 12 was 75% in Zip code 55107 and 25% in Zip code 55110. On a given day, the publishing run calculated a draw of 80 for this route. The draw would be broken down for AAM history: 60 would be allocated to Zip code 55107, and the remaining 20 to Zip code 55110.
As time passes and circulation patterns (and route boundaries) change, these percentages lose their accuracy—perhaps after a while only 50% of route 12’s subscribers live in Zip code 55107. But the same percentages are still being used for AAM reports, so 55107 figures are inflated, while 55110 figures are deflated.
You can use Compare/Update AAM % to update Town of 25 and Zip code percentages so that they reflect the current circulation. The utility will look at all subscribers on a route and, based on address information, recalculate the percentages. A report listing the new percentages is created as part of the process, and you have the option to run the utility just as a report (with no updating).
You should update AAM percentages once a month, or whenever there is a change (such as mass rerouting) that could affect the percentages. For performance reasons, AAM percentages are not updated automatically with the publishing run. Also, you may elect to print the report only in order to review the changes that will be made before updating the percentages. Always print a copy of this report for AAM audit purposes.
Select Compare/Update AAM% from the Account menu to display the Compare AAM Percent Report screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the product for which to update AAM percentages (enter “*” to multi-select products).
ROUTE TYPE
predefined
Indicate which route type should have AAM percentages updated. Route types are user-defined categories (see Route Type in the Setup Manual).
PRINT REPORT
yes/no
Indicate whether the Compare AAM Percent Report should be created.
UPDATE METHOD
predefined
Specify whether to update AAM percentages for Town of 25, Zip code, both, or neither (enter neither if you are creating the report only).
Select Continue to update percentages and produce the report.
Use this utility to automatically change the amounts you charge or credit accounts for specific recurring charges. If you charge accounts different amounts for a specific charge (such as bond deposit), you must run the utility separately for each amount.
Select Change Recur Charge from the Account menu to display the Recurring Charges Change Report screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the product for which to change recurring charges (enter “*” to multi-select products).
CHARGE CODE
setup
Enter the charge/credit code to change.
LAST DATE
date
Enter the last date that the old charge amount is valid.
OLD AMOUNT,
NEW AMOUNT
decimal (10)
If this is a flat charge, enter the old and new amounts of the charge code. Only accounts who are charged OLD AMOUNT for the charge code will be changed to NEW AMOUNT.
OLD PERCENT,
NEW PERCENT
decimal (6)
If this is a percent charge, enter the old and new percents for the charge. The same rules apply as for flat charges.
Select Continue to change the charge amount and produce the Change Recur Charge Report, which lists all accounts whose recurring charge amounts were changed.
Rate Check is a useful tool for querying or troubleshooting your account rating structure; it displays all of the rules and rule-rate links for which an account qualifies, in the correct hierarchy.
Note:
This utility is not intended for use with bill-to accounts. Use the delivery account instead; it will produce the same results as could be expected from using the bill-to account.
Select Rate Check from the Account menu to display the Account Rate Check screen.
Complete the following fields.
DATE
date
Enter a date on which to base the rate check. The account and rates will be assessed as of this date.
ACCOUNT
setup
Enter the account number of a delivery or non-delivery account. This utility is not intended for use with bill-to accounts.
PRODUCT
setup
Enter the publication or TM product for which the account’s rate should be selected.
DELIVERY ACCOUNT
yes/no
If this account is set up as both a delivery and non-delivery carrier, indicate if you want to see the delivery or non-delivery rates.
ENTITY TYPE
predefined
If this is a non-delivery carrier, indicate whether you want to display rates for individual routes or all routes in a district.
DISTRICT
setup
If the field above is set to “district”, enter the district for which rates should be displayed.
ROUTE
setup
Enter the route for which rates should be displayed.
AAM ZONE
setup
Rates can differ based on the subscriber’s AAM zone. Enter the AAM zone to include in this rate query, or enter “*” to multi-select AAM zones.
DELIVERY SCHED
setup
Rates will differ based on the subscriber’s delivery schedule. If this is a home delivery carrier, enter the delivery schedule for which to display rates, or enter “*” to multi-select delivery schedules.
DRAW TYPE
predefined
Rates will differ based on draw type. If this is a home delivery carrier, specify the draw type for which to display rates (office pay, carrier collect, paid comp, unpaid comp, samples, service, third party, TMC). Enter “*” to multi-select draw types. If this is a single copy route, “single copy” is displayed.
RATE CODE
setup
If this is a home delivery route, the rates may vary based on the subscriber’s rate code. If so, enter the subscriber rate codes for which the account’s rates should be displayed (enter “*” to multi-select rate codes).
PAPER COUNT
integer (7)
An account’s rates can differ based on the number of papers delivered on a given day. Enter the number of papers for which to display rates (leave this field set to 0 to display rates regardless of paper count).
BONUS DAY DRAW
yes/no
Indicate whether the option should find rate valid for bonus days. Leave this field set to “n” unless you are specifically looking for bonus day rates.
Select Continue to complete the rate query. The Account Rate Check report is displayed, listing each rate for which the account qualifies. All of the rules and the rule-rate link for the rate are displayed. The first rate displayed will be the highest in the hierarchy, the next one the next highest, and so on.
Draw figures by census tract can be used in both Targeted Marketing and InsertPlus. A route may cross census tract boundaries; the percentage of a route’s draw that lies within a particular census tract may be set up with the route, and periodically updated using this utility.
Update Census Tract % looks at the census tract entered for each subscriber on a route and recalculates the census tract percentages to reflect current circulation. A report listing the old and new percentages is created by the process.
Select Update Census Tract% from the Account menu to display the Census Tract % Report screen.
Select Add and enter the product for which census tract percentages should be recalculated (enter “*” to multi-select products).
Select Continue to update percentages and produce the report.
The number of households on each home delivery route includes both subscribers and non-subscribers; this figure is used in InsertPlus. Initially, the number of households is entered into the system when the route is set up. This number may grow inaccurate in time due to changed route boundaries or other causes.
Use Update # Households to recalculate the number of households on a route based on the number of addresses in the database assigned to the route. A report listing the old and new household figures is created in the process, and you may run the utility for the report only.
Select Update # Households from the Account menu to display the Household Count Report screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the product for which to update households (enter “*” to multi-select products).
UPDATE
yes/no
Indicate whether the household count for each route delivering this product should be recalculated. If you only wish to create the report, enter “n” here.
Select Continue to update households and produce the report.
The Holiday Edition option can be used on dates (such as holidays) when you will have different editions than are normally run on that day of the week. Changes in holiday editions are typically accompanied by changes in holiday draw.
For example, let’s say on Thursday you print only two editions (“City” and “Country”). This Thursday is a holiday, however, and you want to replace Thursday’s editions with the editions normally used on Sunday (“Early”, “Morning”, and “Final”). When this utility is run each route will use its Sunday edition on Thursday—the Sunday editions will print on the bundle tops, allowing personnel to correctly distribute “Early”, “Morning”, and “Final” editions to the right routes.
Note:
During route setup, each route is assigned an edition for each day of the week. Also note that alternate edition models may be used for this (see Edition Override for more information).
Select Holiday Edition from the Account menu to display the Holiday Edition screen.
Select Add and complete the following fields.
PUBLICATION
setup
Enter the publication for which to make edition changes.
PUBLISH DATE
date
Enter the publishing date on which you wish to make edition changes. This is the date of the holiday.
REPLACE DATE
date
Enter the date whose editions should replace the publish date editions. For example, if you want to replace Thursday’s edition with Sunday’s, enter Thursday’s date in PUBLISH DATE, above, and last Sunday’s date here.
Select Accept to change the editions. After the changes have been made, the main menu will appear.
You can use this utility to quickly enter adjustments to account balances (usually done when transferring balances from an old system).
Note:
All amounts entered are added to the account’s existing balance. Once you are “live” on Circulation, select this option only on instruction from the Newscycle Support Center.
Select Balances from the Account menu to display the Balances screen.
Enter the company and bill source for the accounts being adjusted, and the current date and the ending date of each aging period in the old circulation system.
When you have entered this information, more data entry fields appear so you can enter balance information for each account. The following table shows what to enter.
ACCOUNT
setup
Enter the account ID in Circulation.
TOTAL
decimal (10)
Enter the total amount this account owes.
CURRENT
decimal (10)
Enter the portion of Total currently due.
PERIOD 1 PERIOD 2 PERIOD 3
decimal (10) decimal (10) decimal (10)
Enter the portion of TOTAL due in the respective aging periods (in your old circulation system). The sum of Current, Period 1, Period 2, and Period 3 must equal Total.
When you have entered the balances for all of your accounts, press F4 to exit to the main menu.
(Export)
(Export)
(Import)
(Import)
This section guides the user through the menu options that are available under the Subscription/Address menu.
Address correction software can be used to “cleanse” your addresses (verifying that the address line, city, state, and Zip code are correct) as well as standardize the entire address line, city and state (based on your country’s postal data and rules).
Some of the benefits provided by address correction are listed below:
Corrects and standardizes address, city and state data.
Assigns Zip/Postal codes (Zip code, Zip+4, carrier route) that can provide additional pre-sort discounts for mailing.
Allows you to comply with the new, stricter rules on OCR (optical character recognition) readability.
Allows your customer service operators to verify address information on-line when entering a new start.
Makes addresses more deliverable.
Creates a higher percentage of address “matches” when you use List MatchPlus software.
For US addresses, Quadient populates eLot (Enhanced Line of Travel), DPV (Delivery Point Validation), and LACS (Locatable Address Conversion System) codes used by the USPS. Quadient will also return the DPV NO STATS setting (used for dwellings for which there is no DPV information, such as those that are vacant or being built), if the Business Rule— For US addresses, should the DPV NO STATS directory be used? is set to “Yes”.
For US addresses, Quadient uses SuiteLink to fill in the suite number for incomplete business addresses (see SuiteLink).
Different address correction software products that have been integrated with Circulation. Quadient utilizes US Postal Service (USPS) directories to cleanse and standardize US addresses in the Circulation database. Another vendor, QAS, is generally used for Australian and Canadian addresses. Two older products, Address Correction and Encoding (ACE) and CACE, the Canadian counterpart to ACE, are no longer supported. Business Rules determine the address correction software used and configuration parameters for each software product. See Address Cleansing in the Setup manual for more information.
Note: Address correction is an optional costed feature offered in Circulation.
There are two ways in which address correction software can be used for address hygiene. Batch Address Hygiene, documented below, enables you to cleanse and standardize all addresses in one or more Zip codes at one time.
The other way to perform address hygiene is when a single address is added or modified in Customer Service or iServices Subscriber. If the new or modified address does not exactly match the address in the USPS or Canada Post directories, and Business Rules are set to allow cleansing, a window will open asking you which address to keep. This is known as online address hygiene, and is described in the Customer Service chapter (see Adding an Address).
In addition, Circulation has a batch hygiene utility for the Circulation router, which will cleanse addresses used to define the router address ranges (see Router Addr Hygiene).
If your addresses are mostly in the US and you use Quadient for address correction, Batch Address Hygiene can be run to cleanse all addresses in one or more Zip codes. This option might be used when an updated directory is available, or when a group of addresses is added to Circulation (through List MatchPlus). It is a good idea to run Batch Address Hygiene at least once without updating the address database; the reports can then be studied and action taken on individual addresses you would rather not cleanse.
Note:
If your addresses are mostly in Canada or Australia and you use QAS for address correction, you cannot cleanse addresses via Batch Address Hygiene. Instead you can export addresses for cleansing outside of Circulation, and then import them. See FAQ #111 for more information.
Batch Address Hygiene has no effect on router addresses, which are stored elsewhere in the database. User Router Addr Hygiene to cleanse router address ranges.
The process of cleansing and standardizing a batch of addresses is automatic—all addresses that have the Cleanse Address field checked (flagged when adding the address) will be included. Addresses with Cleanse Address unchecked will not be processed in Batch Address Hygiene. It is therefore possible to separate out irregular addresses that you do not wish to process.
Note:
The cleansing process may take a considerable amount of time if an entire address database is being cleansed.
After the processing is completed several reports are created to document the hygiene process. Some of these reports can also be generated without updating the Circulation address database.
Select Batch Addr Hygiene from the Utilities | Subscription/Address
menu to display the Address Hygiene Batch Processing Report screen. When using Quadient, the screen lists the Quadient directory date. This is the date of the postal directories being used by Quadient. You can check this date periodically and, when a directory update occurs, run Batch Address Hygiene for your addresses.
Select Add and enter information in the fields described in the table below.
ALL ZIPS
yes/no
Indicate whether addresses in all Zip codes should be processed.
ZIP CODE
setup
UPDATE
yes/no
Indicate whether the Circulation address database should be updated. Enter “n” here if you are just running the utility for the reports.
REROUTE ADDRESSES
yes/no
If you are using Quadient and the addresses will be updated, indicate whether Batch Address Hygiene should automatically reroute addresses for home delivery routes. If you choose to reroute, the subscription will remain on its current route, but the route assigned to the address itself may change. Note that both addresses and subscriptions are assigned routes. The subscription route is used for delivering publications. The address route is used for Targeted Marketing delivery and defaults as the subscription route when there is a new subscription.
CREATE FORM 3553
yes/no
If the address will be updated, indicate whether a PS Form 3553 should be generated for all addresses being cleansed. This form is submitted to the post office to establish the number of your addresses with Zip+4, carrier route information, etc.
LIST NAME
open (19)
If you are generating a form 3553, enter a list name. This name appears on the form and is for reference.
CREATE AAS REPORT LIST NAME
yes/no open (19)
These fields are for CACE, which is no longer supported. The fields will be skipped.
DATE RANGE
yes/no
Indicate whether batch address hygiene should cleanse only addresses entered within a certain date range.
PERIOD START DATE, PERIOD END DATE
date
If DATE RANGE is set to “y”, enter the date range for address cleansing. Only addresses entered within this date range will be cleansed.
REPORT ALL DETAIL
yes/no
Indicate whether every address should be listed in the Assigned Addresses Report (one of the reports created by Batch Address Hygiene).
NTH’ING FACTOR
integer (4)
If you entered “n” in the previous field, indicate the nth’ing factor to use for displaying addresses in the Assigned Addresses Report. For instance, if you want every tenth address to be displayed, enter “10”; if you want every hundredth address to be displayed, enter “100”.
Select Continue to begin cleansing addresses. When using Quadient, during processing the screen will display the number of addresses that have been uploaded for cleansing. In addition, an e-mail is sent by Quadient to the e-mail address specified in the Business Rules when the address cleansing process starts and completes.
After processing is complete, the Summary Statistics Report will appear. The standard viewing and printing options are available for this report. The other reports are saved to spool and can be viewed via the View/Print Utility (see View/Print). These reports are described below.
Important:
If you do update the Circulation database, be sure to save the reports (set Save to “Y” in the View/Print window). Otherwi1se, the Update Audit report will not be saved, and you will have no record of which addresses were changed.
If you want to process addresses for only one ZIP Code, you can enter that ZIP in the ZIP Code field described in the table above. If you want to process multiple ZIPs, enter a “*” in the ZIP Code field, and the ZIP Code Selection screen will appear.
Note:
Although Batch Address Hygiene can be run for specific ZIP+4s, we recommend that you run it only for 5-digit ZIP Codes, as ZIP+4s frequently change. If you do enter full ZIPs+4s, formatting is important; be sure a dash is included in the ZIP (e.g., 55119-9911) and a space for Canadian Postal Codes (e.g., A0A 0A0).
Select Add and enter each Zip code that should be included, one at a time. As a shortcut, you can enter incomplete Zip codes; all Zip codes beginning with those numbers will be included. For example, in the screen below “55” is entered—all Zip codes that begin with “55” will be processed.
When all Zip codes have been entered, press F4 and then Exit to return to the Address Hygiene Batch Processing Report.
Up to five reports are created during Batch Address Hygiene processing, as listed below. When addresses are not updated, only the Assigned Address Report, the Unassigned Address Report, and the Summary Statistics report are created.
The Assigned Address Report lists addresses that were changed in address hygiene; both the new and old form of the address appear. A status code is also listed which tells which elements of the address were standardized (see Quadient status codes). Addresses where the core address elements remained unchanged will not be listed on this report, and if an nth’ing factor was used, only a fraction of the changed addresses will be listed. The core elements of an address are: the house number, house number modifier, prefix, street name, street type, suffix, unit type, unit, city, state, and Zip code.
The Unassigned Addresses Report lists addresses that address correction was not able to confidently match to any address in the postal directories. An error code is listed with each address, explaining why the address could not be assigned (ssee Quadient status codes). Note that the report contains an LAC (Locatable Address Correction) setting, under the STREET NAME column. A “Y” in LACS CODE indicates that the US address (usually a rural route) needs to be converted to a standard street address (also referred to as “911 conversion”). Address correction does not have the capacity to make the change.
The Update Audit Report is created only if the Circulation database was updated by Batch Address Hygiene. This report lists updated addresses that contained missing or incorrect elements, such as a missing Town of 25. An “FYI” column provides information about possible inconsistencies with the address.
The Summary Statistics Report summarizes the Batch Address Hygiene process, listing the total addresses read, assigned and unassigned, among other things. This is the only report that is displayed after Batch Address Hygiene processing; the other reports are saved in files and must be viewed with the View/Print utility.
The PS form 3553 can be submitted to the USPS as proof that addresses have been cleansed using CASS-certified software (necessary for automated discounts). The form 3553 may be recreated bi-monthly, after new postal directories are installed. Any time large numbers of addresses are added or modified within the database (for example, via List MatchPlus), Batch Address Hygiene should again be run on all addresses and a new form 3553 (or AAS report) created. When using Quadient, the report under the normal directory will just contain text indicating the name and location of the pdf version of the report downloaded from Quadient, which will be saved under the pdf directory. When running batch address hygiene and creating the form 3553, addresses in the database meeting the following conditions will show up in the “total addresses” count, but not in the “coded addresses” count on the 3553 (i.e., your percentages will be lowered):
Address is locked by another user.
The address does not have “US” or “CA” as the country name.
The address country is blank and publication country in Business Rules is not “US” or “CA”.
The address “cleanse” flag is set to “no”.
The address is a special address (military or foreign).
Note:
According to the USPS, submitting the form 3553 (run against the entire database) with each mailing will be sufficient to qualify for automation discounts. For example, if you created a form 3553 for your entire database of 10,000 addresses, you could use this form with a partial mailing of 4,000 addresses.
The table below shows the default file names used to save the reports.
Assigned Addresses Report
ADDRHYB1
Unassigned Addresses Report
ADDRHYB2
Update Audit Report
ADDRHYB3
Summary Statistics Report
ADDRHYB4
PS Form 3553
ADDRHYB5
Every time you run Batch Address Hygiene and use the default settings, the new reports will replace the reports previously saved. If you wish to keep a particular report saved with the default name, change its file name by selecting Utilities | System | View/Print.
An example of each of the reports can be found below.
Change codes returned by Quadient appear on the Assigned Addresses report in the STATUS field, with an “S” prefix. Likewise, error codes returned by Quadient appear in the ERROR column on the Unassigned Addresses report, with an “E” prefix. These codes can be looked up from Quadient’s website, using this URL:
Click the link labeled "known values" to view the codes.
SuiteLink is a USPS database of business addresses that is utilized by Quadient during address cleansing. The purpose of SuiteLink is to append suite information to, or correct invalid suite information for, business addresses, based on the ZIP+4.
The SuiteLink codes returned by Quadient on the Batch Address Hygiene report include:
A—SuiteLink match - secondary information exists and was assigned to this record as a result of SuiteLink processing.
00—SuiteLink no match - lookup was attempted but no matching record could be found.
blank—A SuiteLink lookup was not attempted because either (1) the address was not a high-rise default according to CASS, or (2) the address did not contain a firm.
In order to use SuiteLink, the name of the business must be in the Last Name field in the Occupant record, or else in the Other Name field when the Other Name Usage field is set to “Firm”. If the firm name passed to Quadient is blank or the address does not DPV-confirm, SuiteLink will not be called.
Newspapers that own multiple publications may have a situation where, due to delivery or market considerations, subscribers of one pub need to be shifted to another pub. Obviously, making such a switch is a time-consuming process. However, by using this option, Product Change, you can save time and minimize data entry mistakes.
Product Change switches active or temp stopped subscribers from one publication (the “from” product) to another (the “to” product), based on delivery schedule, billing method, and route/district. A different delivery schedule and billing method can be specified for the “to” product, and the appropriate transactions are created to accomplish the switch. Both route and mail delivered subscribers can be shifted to the new publication.
Note: Product Change is a powerful tool. Please read the documentation below thoroughly before running this utility.
Several different transactions may be created by Product Change, including starts, stops, and transfers. The following table describes the transactions and the role they play in the publication switch.
Perm Stop
A perm stop transaction for the “from” publication will be created for each subscriber.
Start
A start transaction for the “to” publication will be created for each subscriber (unless the subscriber already has an active or temp stopped subscription with the “to” publication). The route will be determined by consulting the router.
Temp Stop
If the subscriber is temp stopped on the “from” publication, an equivalent temp stop will be created for the “to” publication (unless the subscriber already has an active subscription with the “to” publication).
Transfer Out Transfer In
If the subscriber is office pay in both the “from” and “to” publications a transfer out will be created for the “from” publication, and a transfer in for the “to” publication.
Billing Change
If the billing method entered for the “to” publication is different than the one specified for the “from” publication, a billing change transaction will be created for the “to” publication.
Delivery Schedule Change
If the delivery schedule entered for the “to” publication is different than the one specified for the “from” publication, a delivery schedule change transaction will be created for the “to” publication.
Before running Product Change, please take the following considerations into account:
Because Product Change uses the router to determine the new route for each subscriber, you must have the router defined for the “to” product.
The router does not need to be defined for mail subscribers. If the subscriber’s label group exists for the “to” publication, they will be assigned this label group, otherwise the label group will be determined by the subscriber’s Zip Code using Zip Label Group setup.
Subscribers with future non-monetary transactions (for example, a delivery schedule change, billing change, or stop and restart with donation) will not be switched; instead, they will be written to an exception report. Subscribers with payments or available refunds will be switched, and the payment or refund will be taken into consideration in the transfer in transaction created for the “to” product.
Subscribers currently in grace will be switched, but the grace amounts will not be transferred to the “to” product. Instead, the subscribers will be written to the exception report, and the grace amounts must be manually handled (if necessary).
The subscriber’s rate will be transferred with the subscriber, unless the rate is not valid with the “to” publication. In that case, the subscriber will be rerated.
If you have the billing method for the “to” publication set to office pay, but a route does not allow office pay subscribers, these subscribers will become carrier collect.
If a subscriber already has an active or temp stopped subscription on the “to” publication, Product Change will only change the delivery schedule, based on the Product Change Setup option.
Publishing runs for both the “to” and “from” products must be closed before this utility is run.
To switch subscribers from one publication to another:
If you have occupants that subscribe to both publications, you will need to specify how their delivery schedule should be changed in Product Change Setup.
Select Product Change from the Subscription/Address menu.
Select Add and complete the following fields. We recommend that before you do the actual product change, you run this option with Report Only set to “y” so that the exception report can be viewed for possible problems.
EFFECTIVE DATE
date
Enter the date on which the product switch should take place. Transactions created by the process will have this date.
FROM PRODUCT
setup
Indicate the publication that subscribers should be switched from.
DELIVERY SCHEDULE
setup
Indicate the delivery schedule that subscribers should be switched from. Only subscribers with this delivery schedule for the “from” product will be switched.
BILLING METHOD
predefined
Indicate the billing method that subscribers should be switched from (carrier collect, office pay, paid comp, or unpaid comp). Only subscribers with this billing method for the “from” product will be switched.
TO PRODUCT
setup
Indicate the publication to which subscribers should be switched.
DELIVERY SCHEDULE
setup
Indicate the delivery schedule that subscribers should be switched to. They will have a subscription to the “to” publication delivered on days defined by this delivery schedule.
BILLING METHOD
predefined
Indicate the billing method the subscribers should have with the “to” publication.
SOURCE, SUBSOURCE
setup
Enter the source code and, if applicable, subsource code that should be used for any transactions created by this utility.
REASON CODES
setup
Enter the reason codes for the different transactions that may be created by this utility: start, permanent stop, temporary stop, delivery schedule change, billing method change, transfer out and transfer in.
SELECTION METHOD
predefined
Indicate whether subscribers should be picked for the publication switch based on district, route, or label group. Note that district and route will change route delivered subscribers only, and label group will change mail delivered subscribers only.
SELECTION
setup
Enter the district, route or label group (depending on what is entered in Selection Method) to base the switch on, or enter “*” to multi-select districts or routes. Only subscribers within these routes, districts or label groups will be selected for the product change.
REPORT ONLY
yes/no
If you set this field to “y”, the product change will not take place—only the exception report will be created. We recommend that you initially run the utility with this field set to “y”, review the exception report, and then run it again.
Select Continue to begin processing. Subscribers of the “from” product assigned to the delivery schedule, billing method and routes, districts or label groups entered will be switched to the “to” product. As part of the process, the Product Change Utility report will be created, detailing the subscribers who had their publication switched by the process. The standard view/print options are available.
Run Rerouting for the “to” product.
The Product Change Utility report lists successful product changes, processing errors, and other information about the process. The report has seven distinct reporting areas:
Successful Change. Lists subscriptions that were carrier collect in the “from” publication and are now carrier collect in the “to” publication.
Transfer. Lists subscriptions that were office pay in the “from” publication and are now office pay in the “to” publication (Transfer Out and Transfer In transactions will be created for these subscribers).
Transfer Grace. This is the same scenario as “Transfer”, but the subscriber was in grace in the “from” publication. No Transfer transactions will be created, and the grace amount must be manually entered.
Grace. Lists subscriptions that were office pay in the “from” publication and in grace and are now carrier collect in the “to” publication. The grace amount will have to be handled manually.
Refund Due. Lists subscriptions that were office pay in the “from” publication (and had a balance) and are now carrier collect in the “to” publication. An Available Refund transaction will be created when stop transaction is processed. The refunds must be entered manually.
Pending Transaction. Lists subscribers that had pending transactions and were therefore not processed.
Processing Error. Lists subscribers that were not processed because of some error (other than a pending transaction).
This option allows you to change an account’s bill source. For example, you might change an account from weekly to monthly billing because he or she has turned 18. Because accounts are organized in the system by company and bill source, Change Bill Source will also move all payments, open items, and other records for the account to the new bill source.
Note: Before running this utility, be sure that there are no open billing runs for the current or new bill source.
Select Change Bill Source from the Account menu to display the Change Bill Source screen.
Select Add and complete the following fields.
COMPANY
setup
Enter the company to which this account belongs.
ACCOUNT
setup
Enter the account number.
CURRENT BILL SOURCE
display
The current bill source for this account is displayed.
NEW BILL SOURCE
setup
Enter the new bill source that will be assigned to this account.
Select Accept to process the bill source change. You can then change another bill source or select Exit to exit to the main menu.
Newscycle Circulation and Newscycle Audience can share occupant and address data, giving Audience a richer dataset for targeted content serving and ad serving on the newspaper website, as well as campaign generation.
Circulation occupant, address and subscription data can be loaded into Audience as source data via an API, and Audience can then send back selected profiles in a flat file, which can be imported via ListMatch and used to target profiles for campaigns in Circulation. For example, profiles for frequent website readers can be imported into Circulation via LM and targeted for a campaign to sell digital subscriptions.
Audience will use the occupant ID as a unique key for storing information about the occupant, including e-mail address, addresses, and subscription info. Once interfaced, occupants can be included in target profiles, allowing certain ads and content to be displayed on the publication website when the occupant logs in. Occupants can also be selected for marketing campaigns.
Initially, you may have your existing Circulation address/occupants loaded into Audience via a flat file, with the assistance of NEWSCYLE Professional Services. In addition, if you store demographic information in Circulation and would like to interface that data to Audience, if the demographic answers have an answer type of “Character” and the Map to Audience field in Demographic setup is set to “y” (see Demographic in the Setup Manual). After the initial load and setup is complete, you can update Audience with new or modified address/occupant information using an incremental sync.
Circulation data can be sent to the Audience API via the Audience Sync option.
Note: The Audience API is a costed add-on. Add On Activation must be configured in order to access the Audience Sync and Reset Audience Sync options (see in the Setup Manual).
The Audience Sync option is used to export occupant, address, subscription, and demographic information from Circulation in a form that can be imported into Newscycle Audience. It can also be used to update incremental changes to occupant, address, subscription, and demographic information to Audience, either directly via a web service call or via export/import as done with the full export.
The file will be named audgenome.xml
and be exported to /pbs/exchange/cm/
. See Appendix B for the XML format and output examples.
The host name, URL, class path and WSDL used to communicate with the Audience web service are defined by Business Rules in the Audience section of Household Management. Business Rules also control the batch size of the web service call, whether passwords are interfaced, whether only subscribers are interfaced and, if so, which publications they are interfaced for, whether only one profile should be sent per occupant, and other settings pertaining to Audience Sync.
Select Audience Sync from the Audience menu in Graphical Utilities. The Audience Sync screen displays.
Click the Add button and enter the following fields.
SYNC TYPE
predefined
Enter Full or Incremental. A full sync will export all audience information. An incremental sync will export only audience information that has changed since the last sync.
ERROR PROFILES
predefined
Indicate "Yes," "No," or "Only" whether the sync should include error profiles.
SYNC STYLE
predefined
Indicate whether the sync should be Direct or Export. A direct sync is performed via a web service call to Audience. An export sync will export audience information to a file.
MAXIMUM PROFILES
integer
This field controls the maximum number of records exported. To export all records, leave this field blank or set it to 0.
LAST SYNC
display
The date and time of the last sync is updated whenever all profiles (Max Profiles left blank) are exported. When a subset of profiles is exported, the date and time are not updated.
Select Accept to perform the audience sync.
This option is typically used on holidays where the draw is significantly higher or lower than usual; it transfers or combines draws from another day to the holiday. Holiday draw can be run for either home delivery or single copy routes, and for actual or advance draw.
Replace draw (draw for the replace day entirely replaces draw for the holiday).
Take the maximum (the draw for each delivery schedule is compared for the two days and the maximum draw used).
Replace draw (draw for the replace day entirely replaces draw for the holiday).
Combine draw (draw for the replace day and holiday will be combined).
Take the maximum (the larger of the two draws will be used).
Note:
You should review your account rating setup before using this option. For example, carriers who do not normally deliver on Sunday may receive Sunday draw; i.e., their rate would need to have draw and credit charges specified for Sunday.
If you are running Holiday Draw for actual draw, you must run it after transactions have been processed for the final time for the holiday, but before bundle tops, manifests, etc. have been printed. Similarly, for advance draw, you must run this utility after the holiday’s advance run has been started but before any advance run documents have been printed.
Note:
Rather than using Holiday Draw to manipulate draw figures for holidays, you can use Circulation’s bonus day feature. See Bonus Day Delivery for more information.
Select Holiday Draw from the Account menu to display the Holiday Draw screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the product for which to transfer draw.
DRAW TYPE
predefined
Indicate whether holiday draw should be run for actual draw or advance draw. Advance draw is used in advance publishing, while actual draw is used in the regular publishing run.
PUBLISH DATE
date
The last publishing date for which transaction processing has been run is displayed. This will be the day to which draw will be transferred (i.e., the holiday). This option does not check against Circulation’s Holiday Calendar. Therefore, be sure to double check your holiday dates. These dates should be verified a month prior to the actual holiday.
REPLACE DATE
date
Enter the date from which to transfer draw.
SINGLE COPY METHOD
predefined
Enter the method to use to replace the draw on the publish date for single copy outlets: none, replace (use Replace Date draw totals), combine (add draw totals) or maximum (use larger draw total).
ROUTE METHOD
predefined
Enter the method used to replace the draw on the publish date for routes: none, replace (use Replace Date draw totals), maximum (use the larger draw total within each delivery schedule), or combine (copy the draw from all delivery schedules from the Replace Date that are not present on the publishing date).
Select Accept to adjust the draw. Circulation will take the draw for each route on the replace date and replace, compare or combine it with the route draw on the holiday. If there is no corresponding replace day route, it will simply add the holiday route with its draw to the holiday draw. You should then print your bundle tops and carry out the rest of the publishing run.
As an example of how Holiday Draw would work, let us look at the draw for a typical home delivery route, route 09, using the following information:
So, on a typical week, the draw is 65 Monday-Friday, 45 on Saturday, and 60 on Sunday.
But on Monday, May 23rd (the holiday), we will use the draw for the following Sunday. If we were to use a Route Method of replace, the holiday draw would be 60 (45 on the Mon-Sun schedule, and 15 on the Sun schedule). But, for this example, we use a Route Method of maximum, and the holiday draw is 80:
Delivery Schedule
Sunday
Monday (normal)
Holiday
Mon-Sun
45
45
45
Sunday
15
0
15
Mon-Fri
0
20
20
80
So, on Monday the 23rd, Holmes would deliver 80 papers rather than 65. The extra 15 newspapers will be rated using the Sunday rate code specified for their rate—this means that the rate assigned to Holmes should have an amount and charge code specified for Sunday, even though Holmes does not deliver the route on Sunday.
The Reset Audience Sync option resets the run control record used by the Audience Sync utility in case the process is interrupted.
Select Reset Audience Sync from the Audience menu in Graphical Utilities. The Reset Audience Sync screen displays.
Click the Add button and set the last sync date and time.
Click OK and then Continue to reset the run control record. A processing report will display with information about the reset (original and changed Last Sync Date and Last Sync Time).
You might, for various reasons, want to assign an account a new ID—for example, change a carrier, Jones, from “4B2” to “4B27”. Account IDs can be changed with this utility.
Select Change Account ID from the Account menu to display the Change Account ID screen.
Enter the old ID of the account you wish to change. Then enter the new account ID.
The Message field will indicate when the account ID change has been processed. Change other account IDs, or press F4 to exit to the main menu.
The Rate Change utility facilitates across-the-board changes to account rates. You can use it, for example, to add 0.05 to the draw charge for all routes in the “City” AAM zone. The utility will change the value of rate codes, which are selected by one or more parameters, including:
district
delivery schedule
account type
route
route type
account rate class
AAM zone
route rate class
draw type
rate code (selected directly)
Using the account rule/rate links, this utility finds all rate codes that meet the entered criteria. For example, if route 07 is entered as the only parameter, the utility will find all rule-rate links for which route 07 qualifies—those with a Route Rule with a route of “07” or “*”. To extend this example, if delivery schedule “DO” were entered along with route 07, only rule/rate links that had both a qualifying Route Rule and qualifying Delivery Rule would be selected.
Once rate codes are picked, the utility will determine if the rate code appears in any other rule/rate links. If the rate code appears in a rule/rate link that the selection parameters do not qualify for, the rate code will not be changed; instead it will be listed in the processing report that is displayed after the rate change is complete.
Select Rate Change from the Account menu to display the Account Rate Change Utility screen.
Select Add and complete the following fields. It is a good idea to run the utility once with Update set to “n”, verify that the correct rate codes are being selected, and then run it again with Update set to “y”.
EFFECTIVE DATE
date
Enter the date on which the rate change should take place. Account draw on or after this date will be rated with the new rate.
PRODUCT
setup
Enter the publication for which you are changing account rates.
DISTRICT,
ROUTE,
AAM ZONE,
DELIVERY SCHEDULE,
ROUTE TYPE,
ROUTE RATE CLASS,
ACCOUNT TYPE,
ACCOUNT RATE CLASS,
DRAW TYPE, RATE CODE
setup
In these fields, enter your parameters for selecting rate codes. You can enter a single entity in a field, enter “*” to multi-select entities, or leave blank. Note that Rate Code refers to the account’s rate code (i.e., you will be picking rate codes directly). If multiple entities are entered, an account rating rule will qualify if it matches any of the entities or is “*”. If a field is left blank, it will qualify for all account rating rules.
CHARGE TYPE
predefined
Indicate whether charge rate codes, credit rate codes, or both charge and credit rate codes should be changed.
UPDATE
yes/no
Indicate whether rates should be changed. If you enter “n” here, no rate change will be created, but the utility will report which rate codes were selected and if any rate codes had conflicts.
UPDATE TYPE
predefined
If Update is set to “y”, the New Rate window will open with these additional fields. Indicate whether to adjust or replace the rate codes selected.
UPDATE AMOUNT
decimal (9)
Enter the rate change amount. If Update Type is “adjust”, the existing rate will be adjusted by this amount (enter “-” to adjust a rate down). If Update Type = “replace”, this will be the new rate. The wholesale rate (what the account is charged or credited) and retail rate (what account taxes are based on) may both be changed.
Once the rate change amount is entered, select Continue to change the rates. If a rate code is to be changed, the utility will end-date the old rate code record and create a new rate code record with a start date equal to the effective date. After the rate changes are made, a processing report will display the rate codes that were changed and any rate codes that were not changed due to conflicts (i.e., some rule/rate links using the rate code were valid while others were not valid).
The Change Credit Status utility can be run in situations where you would like to change the credit status for all former subscribers on certain routes. This may be useful for promotions or for “rehabilitating” stopped subscribers with bad credit statuses. You may optionally generate tasks as part of this process.
Select Change Credit Status from the Subscription/Address menu to display the Change Credit Status screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the publication for which to select routes.
ROUTE
setup
Enter the route for which perm stopped subscribers should have a new credit status, or enter “*” to add multiple routes, one at a time, on the Route List Maintenance screen.
CREDIT STATUS
setup
Enter the credit status which should be assigned to perm stopped subscribers on the selected routes.
GENERATE TASKS
yes/no
Set this field to “y” if a task should be generated for each subscriber whose credit status was changed. The field will only open if at least one task is defined for the Change Credit Status utility (Event field set to “Report Processing” and Report field set to “Change Credit Status”).
Select Accept to change the credit statuses.
Circulation enables you to enter more than one occupant for the same address—several coworkers in one office, for example. Sometimes, however, the same address is mistakenly entered twice. Select Duplicate Address Edit to compare duplicate addresses and decide which addresses, if any, should be removed.
Business Rules determine whether Circulation accepts a duplicate address and whether a warning appears.
Note:
Two addresses are duplicates only if they have the same Zip code, street name, house number, house modifier and unit number (they can have different street suffixes, prefixes, and street types). These criteria are summarized in following table (in Dupl Addr Purge all items except occupant must be identical in order for two addresses to be considered duplicates). Also, military and foreign addresses (where all of the street address fields are blank) will be skipped. See Address for more information about addresses.
Zip code
Street suffix (for example, “North” in “30th Ave North”)
Street name
Street prefix (for example, “North” in “North 30th Ave”)
House number
Street type (for example, “Ave” in “North 30th Ave”)
House modifier (for example, “a” in “23a Portland Ave”)
Occupant name
Unit #
To help you execute your decisions more quickly on screen, duplicate addresses are printed in the Duplicate Address Report the same as they appear when you select Dupl Address Edit.
Select Dupl Address Edit from the Subscription/Address menu to display the Duplicate Address Edit screen.
Select Add. In Starting Address, enter the ID of the first address to check for duplicates. (When an address is brought into the Circulation database, either by operator entry or via conversion from an old data system, Circulation assigns it a unique numeric ID.) Also indicate whether the report should include only exact matches (exact matches must match on all of the items listed in the above table).
Note:
The first time you select this option, accept the default value of zero in Starting Address. If you need to stop checking address duplicates for one reason or another, you can continue later where you left off by entering in Starting Address the ID of the last address you checked.
Select Continue to begin the edit process. Circulation will check the database for duplicates of the first address (from Starting Address). It will then check for duplicates of the next address, moving up by address ID. If there is more than one duplicate for an address, the address will be paired with the best match. This means you may have to run Duplicate Address Edit more than once to find all duplicate addresses.
Circulation will display the first duplicate address match.
You will have four options with this set of duplicate addresses:
Keep address 1 (enter “1”)
Keep address 2 (enter “2”)
Keep both addresses (enter “n”)
Quit the edit process (enter “q”)
If both addresses have occupants, you will have the same options available for editing the occupants (except for Quit). If you delete one address but keep both occupants, the occupants will be listed together under the remaining address. Subscription information is never deleted, just reassigned to the retained occupant/address.
Continue with the edit until all addresses have been reviewed or you are ready to quit. A report will appear, listing information about the addresses you edited (the standard viewing and printing options are available).
The Circulation router is defined as a collection of address ranges. Each address range consists of two addresses—the “to” address and the “from” address. Addresses that fall in between the “to” and “from” addresses are defaulted to the specified route (see Router Utility for more information on the router).
When addresses are cleansed, it may happen that they no longer have the address elements (Zip code, street name, etc.) that fit the router. For example, if the router assigned addresses in the range of 300 Main St and 500 Main St to route 6, and 430 Main St was cleansed to 430 West Main St, the router would no longer assign it to route 6.
To prevent this from happening, the router addresses themselves can be cleansed with Router Address Hygiene. This utility cleanses both the “to” and “from” addresses, just as Batch Address Hygiene, and then compares the “to” and “from” addresses to make sure their address elements match (except for house number—the “to” and “from” addresses will, of course, have different house numbers). For example, with the router addresses mentioned above we might have:
To
300 Main St 55107
300 West Main St 55107
From
500 Main St 55107
500 East Main St 55107
In this case, the router addresses would not be updated, because the “to” and “from” address elements do not match. The four outcomes of Router Address Hygiene are listed below. Each outcome will print either on the Assigned Addresses Report or the Unassigned Addresses Report produced by the process.
Both cleansed
Yes
Yes
Assigned Address Report (if the original addresses differ from the cleansed addresses)
Both cleansed
No
No
Unassigned Address Report
1 address cleansed,
1 not cleansed
Match not done
Yes
Assigned Address Report
Nether cleansed
Match not done
No
Unassigned Address Report
Note:
Only a certain percentage of cleansed addresses will appear on the Assigned Address Report, determined by the nth’ing factor. When one address from a range is cleansed and the other is not cleansed, both addresses will always appear on the report.
As with Batch Address Hygiene, this option will only cleanse addresses if you use Quadient for address correction.
Select Router Address Hygiene from the Utilities | Subscription/Address
menu to display the Router Address Hygiene Processing Report screen.
Select Add and enter information in the fields described in the table below.
SELECT BY
predefined
Indicate whether to update router segments defined by city, Zip Code, or both.
ALL ZIPS
yes/no
If cleansing ZIP Code segments, indicate whether all ZIP Codes should be cleansed.
ZIP CODE
setup
ALL CITIES
yes/no
If cleansing city segments, indicate whether all cities should be cleansed.
CITY, COUNTY, STATE, COUNTRY
setup
If you entered “n” in the previous field, enter the city, county, state and country that should be cleansed. Enter “*” in City to multi-select cities.
UPDATE
yes/no
Indicate whether router addresses should be updated. We recommend that you first run this utility without updating addresses, and study the reports produced.
REPORT ALL DETAIL
yes/no
Indicate whether every address should be listed in the Assigned Addresses Report (one of the reports created).
NTH’ING FACTOR
integer (4)
If you entered “n” in the previous field, indicate the nth’ing factor to use for displaying addresses in the Assigned Addresses Report. For instance, if you want every tenth address to be displayed, enter “10”.
REQUIRE DUAL ASSIGNMENT
yes/no
Enter “y” if a router record should be assigned only when both the from and to addresses are assigned. Otherwise enter “n”.
Select Continue to begin processing. Router Address Hygiene will compare the ZIP Code, street name, street type, prefix and suffix of the router address to postal directories and cleanse the address if necessary. If the router address has no ZIP Code, Router Address Hygiene will instead use the city, county, state and country for comparison. If a cleansed address has a street type, city, county, or state not set up in Circulation, Circulation will add it to the database.
Three reports are produced by the process: the Assigned Address Report (the default spool name begins RTRHYB1), The Unassigned Address Report (RTRHYB2), and the Summary Statistics Report (RTRHYB3). See Batch Address Hygiene Reports for more information on the reports. These reports can be viewed and printed from the View/Print Utility.
When running the Product Change option to shift subscribers from one publication to another, some or all of your subscribers of the “from” publication might also have an active or temp stopped subscription with the “to” publication. In this case, no starts or stops will be created. However, the delivery schedule can be changed for the “to” publication. To do this, you specify the delivery schedule with this option, Product Change Setup.
Select Product Change Setup from the Subscription/Address menu to display the Product Change Delivery Schedule Setup screen.
Select Add and enter the delivery schedules for the “from” and “to” products, and the delivery schedule that subscribers should be changed to. For example, in the screen above, all of the subscribers to publication GZ who have delivery schedule DO (daily only) and also have a subscription to publication DM with delivery schedule DO, will have their DM delivery schedule changed from DO to DS (daily and Sunday).
Select Accept to enter the product setup into the database.
Enter other delivery schedules for the “to” and “from” products. You should enter records for each possible delivery schedule for the “to” publication. For example, if you are switching publication GZ subscribers with a delivery schedule of DO to publication DM, you might set up the following records for the DM delivery schedules:
DO
DO
DO
DO
DS
DS
DO
SO
DS
This utility allows you to import a file of subscribers or to extend grace periods for all subscribers in grace within a certain date range (only non-combo subscribers who are currently in grace can be extended using this option). You can extend grace a specified number of days, or have all grace end at a specified date.
Note:
Extend Grace Days does not consider the Business Rule, What is the total maximum grace days a subscriber may have? Therefore, by using this utility it is possible to extend a subscriber’s grace days beyond the maximum.
Select Extend Grace Days from the Subscription/Address menu to display the Extend Grace Days screen.
Select Add and complete the following fields.
USE IMPORT FILE?
yes/no
Indicate whether to import a file or not. Default is no.
PRODUCT
setup
Enter the product for which grace should be extended.
START DATE, END DATE
date
Enter the starting date and ending date for the grace extend. Subscribers who are currently in grace and will end grace within this date range shall be extended.
# DAYS TO EXTEND
integer (7)
Enter the number of days to extend, if you are extending everyone’s grace a certain number of days.
NEW END GRACE DATE
date
Enter the new end grace date, if you are extending everyone’s grace to a certain date.
READ OPTION
predefined
Indicate whether to commit or edit the import file. If you choose “Commit” the grace will be extended and besides changing the EndGrace transactions date an EndGraceChg transaction is created so there is a footprint with this change. If you choose “Edit”, only the processing report will be created (you can then look the report over for errors before committing).
FILE NAME
open (30)
File must be pipe delimited and stored in the exchange directory with three variable length fields: SubscriptionID, Number of Days, and New Grace Date. SubscriptionID must always be supplied in the import file. The Number of Days or the New Grace Date (but not both) must also be supplied in the import file.
SOURCE
setup
Valid Source from setup.
REASON
setup
Valid Reason from setup.
REMARKS
character (40)
Remarks, if any associated to extending the grace.
Select Accept to process the grace extends.
This option allows you to delete individual subscriptions, for example in the case where duplicate subscriptions were entered in error. Circulation will only allow you to delete a subscription if:
The subscription is permanently stopped.
All subscription activity for the subscription has been processed.
All financial activity including payments, NSFs, canceled payments and unearned revenue is at least 180 days old, based on the last publishing date.
Select Subscription Purge from the Subscription/Address menu to display the Subscription Purge screen.
Select Add and enter the account number of the subscription that should be deleted. Or, enter “*” and add multiple subscriptions on the Account List Maintenance screen.
Select Continue to delete the subscription and all subscription activity. A report will appear, listing the account number that was deleted—the standard viewing and printing options are available.
Circulation can create a report listing all duplicate addresses in the Circulation database. Using the report, you can locate problem addresses, and run Duplicate Address Edit more efficiently. The criteria for determining duplicate addresses is the same in both functions (see the table on Dupl Address Edit).
Select Duplicate Address Report from the Subscription/Address menu to display the Duplicate Address Report screen.
Select Add and enter the ID of the first address number you want included in the report in Starting Address. Also indicate whether the report should include only exact matches.
Select Continue to process the report.
Duplicate Address Purge allows you to remove all duplicate addresses after a specified address number, at one time. The address with the lowest address number is retained, and occupant and subscription information associated with duplicate addresses is automatically assigned to the remaining address. If duplicate occupants are encountered (i.e., first name, last name, and phone are a perfect match), the oldest occupant record is kept.
To qualify as duplicate addresses, two addresses must have the same:
Zip
Street
House #
House Modifier (for example, “a” in 401a Portland Ave”)
Street Prefix (“North” in “36 North Portland Ave”)
Street Suffix (“North” in “36 Portland Ave North”)
Street Type (“Ave” in “36 Portland Ave”)
Unit #
Note: Use Duplicate Address Purge only if you want to get rid of all duplicate addresses within the database. For example, if many of your addresses have rural routes, you should not use this option.
To purge duplicate addresses:
Select Dupl Address Purge from the Subscription/Address menu to display the Duplicate Address Purge screen.
Select Add. In Starting Address, enter the ID of the address where purging should begin (addresses with a lower ID number will be skipped). Also indicate whether the report should include only exact matches (exact matches must match on all of the items listed on Dupl Address Edit).
Select Continue to begin purging duplicate addresses. In this process, Circulation automatically reassigns all information associated with each address in a set of duplicates to the one retained address. For example, if the addresses whose IDs are 45, 2615, and 10045 are duplicates, only address 45 is retained in the database and all information associated with addresses 2615 and 10045 is assigned to address 45.
As part of the purge process, the Duplicate Address Purge report will be created.
Address demographics are usually answered for subscribers individually in Customer Service (for example, during a new start), or are imported via List MatchPlus. This utility, however, allows you to set the answer of an address demographic for a whole range of addresses, or change answers if they have already been assigned. You can run the utility for a range of street numbers, and entire street, or even an entire Zip code.
For example, you might have an address demographic called “Deliver TM”, which is used to select addresses for your TM products. You are expanding your alternate delivery routes, and now all addresses in Zip code 55107 can receive TM products. You can run this utility for Zip code 55107, and all addresses within that Zip code will have their “Deliver TM” answers changed from “no” to “yes”.
Select Address Demographics from the Subscription/Address menu to display the Update Address Demographics screen.
Select Add and complete the following fields.
DEMOGRAPHIC
setup
Enter the ID of the demographic for which you are changing answers. This must be an address demographic that is already set up. See Demographic in the Setup Manual for more information.
DEMOGRAPHIC ANSWER
setup
Enter the answer to which this demographic question should be set. All addresses within the range entered below will have this answer for the address demographic above.
ZIP CODE, EXT
open (5) open (4)
Enter the Zip code and (optionally) Zip code extension for this address range.
PREDIRECTIONAL
predefined
If you are entering a street name and it has a predirectional (street prefix), such as “N” in “1234 N Main St”, enter the predirectional here.
STREET NAME
open (28)
If you are changing address demographic answers for all or part of an individual street, enter the street name for this address. If the address has a PO box, enter the PO box here.
TYPE
setup
If you entered a street name, enter the street type, such as St, Rd, or Ave. Press F2 to look up valid entries.
POSTDIRECTIONAL
predefined
This field appears after Type to accommodate entry of postdirectional street directions (street suffix), such as “N” in “1234 Main St N”.
FROM HOUSE NUMBER, TO HOUSE NUMBER
open (10)
If you are changing address demographic answers for part of an individual street, enter the house number range that should be included in the change.
FROM UNIT, TO UNIT
open (8)
If you are changing address demographics for part of an individual house number (e.g., an apartment complex), enter the unit number range that should be included in the change.
SUMMARY
yes/no
Indicate whether the report that is created as part of the Address Demographic Utility process should be summarized. If you enter “n” here, the report will list all addresses changed; if you enter “y”, the report will list only the total number of addresses changed.
UPDATE
yes/no
Indicate whether Circulation should actually update the addresses selected with the demographic answer above. You may want to run this option first with UPDATE set to “n”, study the report, and then run it again with Update set to “y”.
Select Continue to run the utility. If a selected address already has the demographic answered, the answer will be changed; if the demographic is not answered, the answer will be added. When the process is finished, a report will appear, either listing the addresses changed or giving the total number of addresses changed (the summary version).
Newspapers sometimes offer bonus days to subscribers not on a 7-day delivery schedule. Bonus days are special days (typically holidays) on which the subscriber will receive the paper, even though it is not a normal delivery day for them. For example, if New Year’s Day falls on a Monday, the newspaper might still offer to deliver a special edition to subscribers with weekend-only delivery schedules. In this case, Monday, January 1st would be marked as a “holiday bonus” day.
Bonus days can be easy to managed and track in Circulation. The bonus day feature works as follows:
Using this option, bonus days are defined separately for each delivery schedule. Newscycle recommends defining bonus days for at least as far in the future as your longest subscription term. For example, if your longest term is 1 year, you should define premium days for at least the next year (and ideally for the next two years).
Run the to create the bonus day transactions for existing subscribers.
When a start or billing change is entered, the subscriber can be flagged to receive bonus days, or not. Flagging a subscriber to receive bonus days will cause a bonus day transaction to be created for each bonus day for which the subscriber qualifies. Mail and third party subscribers are not eligible for bonus days. Hybrid subscribers are eligible only on bonus days that are route-delivered. Online subscribers are eligible for bonus days only if Valid for Online is set to “y” in Bonus Days setup (described below).
You may wish to run the Bonus Day Delivery utility the day before each scheduled bonus day to update bonus day transactions with the most current route information and add bonus day transactions for subscribers who qualify, but do not already have them.
Bonus day transactions will be processed by Transaction Processing. If bonus day transactions are processed after the bonus day, a suspended draw adjustment batch will be created for the transactions. Business Rules determine the draw adjust code used with the batch. The batch must be accepted in Route Adjust.
The Route Delivery List can include bonus day papers to be delivered on the run date. Bonus day messages can also be printed on the bundle tops, depending on the bonus day reason code and Business Rules. A bonus day message will be printed if a subscriber has a bonus day transaction for that day.
Subscribers can optionally be charged a premium for the bonus day using the . This can apply both to subscribers who would not normally receive the paper on the delivery day, and subscribers who would receive the paper but are being charged a premium amount for a special edition delivered on the bonus day.
Special account rates can be set up to charge and credit home delivery carriers for bonus day papers.
Bonus days affect the account GL. Subscriber GL accounts are affected only if Bonus Day Adjustment is run.
Select Bonus Day Setup from the Subscription/Address menu in Graphical Utilities to display the Bonus Day screen.
Click the Add icon and complete the following fields.
Click OK to enter the bonus day information into the database.
To create bonus day transactions for the bonus day, run the .
Due to changes in your router, your bonus day setup, or for other reasons, you may want to update bonus day transactions for all subscribers and create new transactions for the correct days and routes. This is the purpose of the Bonus Day Delivery utility. See for more information about bonus days in general.
When a subscriber is flagged for bonus day papers as part of a new start or billing change, a bonus day transaction is created. Separate transactions are created for each bonus day, and the transactions include the delivery route valid for that delivery date (based on the router). If the subscriber permanently stops or changes delivery schedules, the bonus day transactions are removed automatically. In addition, deleting a start transaction that is flagged for bonus days will also delete the bonus day transaction.
When this utility is run, Circulation creates bonus day transactions for all subscribers who should receive a bonus paper on the specified bonus day. If a bonus day transaction already exists for a subscriber for that bonus day, a new bonus day transaction will overwrite the old one. Also, the delivery schedule can be set up to specifically include opt-out subscribers. bonus day transactions will not be created for temp-stopped subscribers.
Note:
Before running the utility, you must set up at least one reason code for bonus day transactions (Transaction Type is “BonusDay”).
If the Business Rule “Do you bill subscribers in advance for premium days?” is set to “Yes”, bonus day transactions will only be created for subscribers with rates that support premium days (i.e. are not marketing terms, balance forward rates, or rates that have Include in Bonus Day Adjustment unchecked).
Select Bonus Day Delivery from the Subscription/Address menu in Graphical Utilities to display the Bonus Day Delivery screen.
Click Add and complete the following fields.
Click OK and then Continue to run the utility.
Once processing is completed, a processing report will display any errors that occurred. The standard view/print options are available.
The bonus days set up for one year can be copied to another year, using the Copy Bonus Day Setup utility. This includes premium days as well as free bonus days.
Note:
Each bonus day will be copied to the same date in the “To” year. The only exception is February 29th on a leap year, which will be copied to March 1 if the “To” year is not a leap year. If a bonus day is on a different day from year to year (for example, Thanksgiving), you will need to delete this bonus day in the “To” year after the copy, and add it manually.
The amounts for the “From” year will be carried over to the “To” year.
In order to do the copy, the “From” year must have at least one bonus day defined, and the “To” year must not have any bonus days defined.
Select Copy Bonus Day Setup from the Subscription/Address menu in the Utilities module. The Copy Bonus Day Setup screen displays.
Click the Add button and enter the criteria for copying bonus days.
Click OK and Continue to run the utility. The bonus days will be copied to the “To” year and a processing report will display, listing the bonus dates copied (if run in Edit mode, the bonus days will not be copied, but the processing report will list the days eligible to be copied).
This utility is used to select a group of subscribers and change their delivery schedules. For example, you may want to force all weekend-only subscribers to a Fri-Sun schedule. The delivery schedule change will not change the expiration dates of these subscriptions. Rating information will be recalculated to allow these subscribers to receive more papers within the same period.
After running this utility, a report will be displayed that shows all accounts that met the criteria entered on this screen.
Notes:
You must assign a reason code that has Update Expire set to “no”.
You must create a rate file that contains the old rate and new rate. When a subscriber is selected who has the old rate, the new rate will be assigned. The file must be in /dti/exchange/cm
and be formatted as follows:
<old rate> | <new rate>
.
Select Deliv Sched Change from the Utilities | Subscription/Address
menu in Graphical Utilities to display the Delivery Schedule Change screen.
Select Add and complete the following fields.
Select OK and then Continue to change the delivery schedules.
Use Batch Transactions to accept, reject, or suspend batches created using other processes.
Note: Currently, this option can be used only for batches created with the Stop Utility.
To run this utility:
Select Subscription/Address | Batch Transactions in Graphical Utilities to display the Batch Transaction Utility window.
In the Batch field, select the batch you want to view. The following information will be displayed:
The process that created the batch (i.e., Stop Utility).
The user who created the batch.
The total number of transactions in the batch.
Delete transactions from the batch. To delete a transaction, select the Delete checkbox and click Delete Selected. You also have the option of selecting and unselecting all transactions at once.
Accept the batch by clicking Accept.
Reject and remove the batch by clicking Reject.
Suspend the batch for future review by clicking Suspend.
This utility extends all active non-combo subscriptions by route for a user-defined number of days.
Note: Extend Expire Dates will not update the wallet when Advance Bill Premium Days are used.
Select Extend Expire Dates from the Utilities | Subscription/Address
menu in Graphical Utilities to display the Extend Expire Dates screen.
Select Add and complete the following fields.
Select OK and Continue to update the expire dates.
Subscription-length pricing allows you to define rates for subscribers based on their subscription length (the number of days they have been active subscribers). For example, you may wish to give all year-long subscribers a better rate than new subscribers or gradually reduce subscription rates incrementally at 6-month, 1-year, and 2-year breakpoints. Or, you may wish to gradually transition your long-term subscribers to your highest rates.
Subscription-length pricing stores subscription length information as subscription demographics. The subscription rule in rate setup (and links in Rate Links) defines the subscription-length pricing rates. Several Business Rules in the Subscriber Accounting section control various aspects of subscription-level pricing.
This utility updates subscription lengths and creates billing changes to update rates for subscribers who have crossed over to the next subscription level. For all office-pay subscribers (including promo, reduced, and normal rates), this utility will add, change, or remove subscription-length levels based on the length of service. For subscribers on “normal” rates, it will also create billing changes to update the rates where appropriate.
Select Subscription/Address | Sub Length Pricing
in Graphical Utilities to display the Subscription Length Pricing window.
Click Add and complete the following fields.
Click OK and then Continue to run the utility.
ACS (Address Change Service) is a USPS program that provides businesses with information relating to their undeliverable mail. As part of this program, a participant can be sent a file with undeliverable customers. This includes both customers who have had a change of address (“COAs”), and customers living at invalid addresses (“nixies”).
If your newspaper is part of this program, you can use this option to import the ACS undeliverable file provided to you by the USPS into Circulation, creating temporary stops for subscribers that have moved or who live at undeliverable addresses. In order to qualify for an undeliverable file, your mail labels must have the subscription ID print in the ACS Keyline position (this can be done with Label Designer). The subscription ID of undeliverable subscribers is then passed back in the ACS file. More information about the ACS program can be found by contacting the USPS.
Import the ACS undeliverable file and match the subscription ID with a subscription in Circulation.
Create a temporary stop for all subscribers matched, unless a future temporary stop has already been entered.
Update a demographic specified by the user.
Print any errors to a processing report.
Select ACS Update from the Subscription/Address menu to display the Address Change Service Report/Update screen.
Select Add and complete the following fields.
Select Continue to import the ACS file. After processing is completed, a report will list the number of records imported and other information about the process (for example, subscribers who already had future temp stops will be listed).
The Stop Utility allows you to generate a list of subscribers and create a batch of permanent or temporary stop transactions for some or all of them. For example, you may want to generate a list of subscribers who have been temp stopped for 30 or more days due to nonpayment, and stop them permanently.
To run this utility:
Select Subscription/Address | Stop Utility
in Graphical Utilities to display the Stop Utility window.
Click Add and complete the following fields.
Click OK and then Continue to produce the report and/or create the stop transactions.
If you created transactions, you must accept the batch using the Batch Transaction Utility (below).
Subscribers on certain delivery schedules may be offered “bonus days” with their subscriptions. For example, subscribers on a Sunday-only delivery schedule may receive a paper on New Year’s Day, even though it is on a Wednesday. Bonus days are typically free, and Circulation’s bonus day functionality does not charge the subscribers. However, some newspapers do charge for bonus days. Even daily subscribers who normally receive the paper on the bonus day may be charged an extra amount, as the paper might be a special edition. In this situation, the Bonus Day Adjustment utility can be run to create subscriber payment adjustments to charge bonus day subscribers.
There are two methods for charging for bonus days in Circulation:
Defining premium days. In this method, money for premium days is deducted from subscriber payments and placed in a “wallet”, which is then deducted when the premium day occurs. Newscycle recommends using this method, because a bonus day is charged in advance and does not impact the subscriber’s expire date.
Using the “traditional” method of adjusting the subscriber’s balance directly. This causes the subscriber’s expire date to be pulled back when a bonus day occurs.
Both methods are described in greater detail below.
When using the premium day method for charging for bonus days, the amount for all bonus days occurring in a subscription period is deducted from the initial subscriber payment and put into a separate wallet for the subscriber. The premium amounts are then deducted from the wallet as the premium days are published and delivered, using negative payment adjustments created by Bonus Day Adjustments and imported by Lockbox Processing.
Note:
Premium days are not charged to subscribers with rates that have marketing terms. Also, rates with a rate type of Balance Forward are not currently supported. Subscribers with these rates will not be billed for premium amounts, and will only receive the premium day paper if it is for a day on their delivery schedule.
To use the premium day method, you must:
Answer “Yes” to the Business Rule— Do you bill subscribers in advance for premium days? (Subscriber Billing section), to “Yes”. If you leave this parameter set to “No”, bonus day adjustments are made using the “Traditional” method described below. Another Business Rule in the same section— Should premium day detail be exported in renewals?, determines whether premium day information is included when renewals are exported in the Detailed Export 2 format.
Have Include in Bonus Day Adjustment flagged for the subscriber rates that qualify for premium day charges. The field is located on the Rate Code tab in Subscriber Rates setup (in the Rate Setup Wizard, this is the prompt “Should subscribers on this rate be included in the Bonus Day Adjustment selection?”).
Define a subscriber payment adjustment code that has Update Wallet set to “y”. This code will be used by Lockbox Processing to create payment adjustments when importing a bonus day adjustment batch. The payment adjustments will deduct the subscriber’s wallet rather than the subscriber’s balance. See Sub Payment Adjustment in the Setup Manual for more information about setting up payment adjustment codes.
Map the payment adjustment code above to the AdjustmentAmount field in the “AdjmntOnly” file map (or what ever Subscriber Lockbox file map you use to import bonus day adjustments).
The premium day charge amounts are predefined in Bonus Day Setup and can be “Additional” (in addition to the subscriber’s copy rate for that day, if they receive the paper) or “Final” (total charge for the bonus day paper) based on the Adjustment Type field. Below is an example of how the adjustment types would charge two subscribers (one who would normally receive the paper on the bonus day, and one who would not).
Subscribers are charged for premium days when the premium day paper is delivered. If the subscriber received the paper (was not temp stopped, for example), the cost of the premium day will be deducted from their wallet. Charging for premium days is a four-step process:
The Bonus Day Adjustment utility is run for the premium day, as described below. This creates an export file of premium day subscribers.
The payment batch containing the premium day adjustments is accepted in Batch Payments. When accepting a batch, the adjustments cannot be modified, and no additional payments can be added. However, individual adjustments can be deleted from the batch.
Charging for Premium Days must be done in a timely manner for the most accurate accounting of the subscriber’s wallet balances. Steps 1 - 4 must be run after End Publishing Run on the Premium Day, and before Start Publishing Run on the next publishing day.
Note:
If you are running renewal notices for a future date and a premium day occurs between the current date and the renewal date, you should run the Bonus Day Adjustment utility for the premium date followed by Transaction Processing and Payment Processing for the current date in order to include correct premium amounts in the term calculations.
If any of the following activities have taken place since the last day of the period, a Historical Unearned or Grace Due should not be run.
Change in the Premium Day Calendar
Run any Premium Day processing
Note: If you are using Premium Day or a wallet of any kind, it is time sensitive.
When a premium amount is deducted from a subscriber payment and added to the wallet, it is considered Unearned Revenue, just like the rest of the subscriber’s balance. When the premium day is earned and negative payment adjustments are made, the Debit and Credit GL Account fields specified for the payment adjustment code determine the GL accounts debited and credited. Because this will be a negative payment adjustment, Debit GL Account will typically be Revenue and Credit GL Account will typically be Unearned Revenue.
With the traditional method for charging for bonus days, the subscriber’s expire date is adjusted when the Bonus Day Adjustment utility is run. Because the expire date is adjusted unpredictably by bonus days, Newscycle recommends using the premium day method described above rather than the traditional method.
When using the traditional method, the bonus amount is specified when running the Bonus Day Adjustment utility. The possible adjustment types are:
Extra charge—Charge a flat amount in addition to the daily amount already paid by the subscriber. For example, you may charge an extra 0.50 for a Labor Day bonus paper.
Total charge—Charge a flat amount, minus the amount already paid by the subscriber. For example, a total charge of 2.00 for the bonus day could include a 0.45 normal daily charge plus an additional 1.55 to bring the total charge up to 2.00. Note: This adjustment type applies only to active subscribers who would normally receive that day’s paper.
Day’s Rate—Charge a previously defined Sunday or weekday rate for the bonus paper. For example, charge the subscriber’s usual Sunday rate for a New Year’s Day bonus paper delivered on Monday.
Number of Days—Deduct a number of days from the subscription period, rather than just one day. For example, charge subscribers three days for the Christmas paper. The number of days adjustment will be converted to an amount by multiplying the value of the last day of the subscription period by the number of days entered. For example, if the value of the last day is 0.20, and 2 days are entered, the subscriber’s balance will be reduced by 0.40.
The following table shows how subscribers on different delivery schedules could be charged for a Thanksgiving Day bonus paper using the expanded features of this utility.
Prior to running the utility for the first time, you may want to set up a special subscriber payment adjustment code for bonus days; the adjustment code must have Update Expire set to “y” and Cash Adjustment set to “n”. Also note that a Business Rule, For adjustment only payments, what description should display in the transaction window? (Customer Services section), governs the description that appears for subscriber payment adjustments.
The Bonus Day Adjustment option exports a file which is then imported via Subscriber Lockbox Processing to create the payment adjustments. This is the same process used with the premium day method, but when using the traditional method the payment adjustments will adjust the subscriber’s expire date.
Bonus day adjustments are exported by running the Bonus Day Adjustment utility, as described in the procedure below.
Select Subscription/Address | Bonus Day Adjustment
in Graphical Utilities to display the Bonus Day Adjustments window.
Click Add.
Select the delivery schedules you want to view. To do this, complete the following fields:
The delivery schedules meeting the entered criteria are displayed. If using the traditional method for bonus day adjustments, complete the following fields and click the OK button within the field panel or each delivery schedule to which you want to make an adjustment. (You must click OK after entering each adjustment. If you do not click OK, the adjustment will not be made.) If you are using the premium day method, these fields will be inactive and this step can be skipped.
When you have finished entering adjustments for the affected delivery schedules, click the OK button that applies to the entire window. Then, click Continue to create the export file. The utility will export subscribers who received the bonus day, along with adjustment day or monetary figures, to an ASCII file. Once the export is done, a processing report will list the number of records exported. See Appendix B for the export file format.
Select Subscriber Payments | Lockbox Processing
in the Accounting module, and import the ASCII file created by the Bonus Day Adjustment utility. The Input File Format should be the file map you created for this purpose. The Input File Name should be the file name specified in Bonus Day Adjustment.
Once the lockbox payment adjustments are processed, accept the payment batch in Batch Payments and process them in Payment Processing. The batch will contain negative payment adjustments (either in days or amounts) for the subscribers who received the bonus day paper.
If you entered “n” in the previous field, enter the ZIP Code that should be cleansed, or enter “*” to multi-select ZIPs (see ).
If you entered “n” in the previous field, enter the ZIP Code that should be cleansed (US Zip+4 is not supported by the router). Enter “*” to multi-select Zip codes (see ).
Set up the bonus days themselves (see ).
The premium day adjustment file is imported via using a special file format for bonus day adjustments. The format should match the , which is a fixed length format with two fields: subscription ID and bonus day value.
Subscriber Payment Processing is run to process the adjustments in the lockbox batch. This deducts the premium day amount from the wallet using a negative payment adjustment. See for more information about buying premium days.
You can report the charges for a specific premium day by running the for the payment batch created for the bonus day adjustments by Lockbox Processing. Premium day charges will display as negative payment amounts.
PRODUCT
setup
Select the product for which to update expire dates. Only one product can be entered.
SOURCE
setup
Select a source code for these expire change transactions.
REASON
setup
Select a reason for these expire change transactions.
DAYS TO EXTEND
integer (3)
Enter the number of days to extend expire dates (must be a positive integer).
ALL ROUTES ROUTE
yes/no setup
Check All Routes to change delivery schedules for all routes, or enter one or more specific routes. If you click the Lookup icon to the right of the Route field, the Route List Maintenance screen will appear. Select Add and enter and individual route, then click OK. Click OK when you have finished and the window will close.
ALL DELIVERY DAYS
yes/no
If you want to extend the expire date for subscribers who received a paper on a specific publishing date, leave All Delivery Days unchecked, and the publishing date in the Delivery Date date field. For example, if the expire date should be extended for everyone who received a paper on 11/30/2009, enter “11/30/2009”.
DELIVERY DATE
date
Otherwise, check All Delivery Days to include all subscribers who meet the remaining criteria. Delivery Date will be skipped.
ALL SCHEDULES
yes/no
If you want to extend the expire date for subscribers on a specific delivery schedule, leave All Schedules unchecked, and select the delivery schedule in the Schedule field.
SCHEDULE
date
Otherwise, check All Schedules to include subscribers on all delivery schedules.
UPDATE
yes/no
If you check this field, expire change transactions will be created. Leave the field unchecked to produce only a report (transactions will not be created).
REMARKS
open (40)
This field is optional, and defaults to “DTIExpireDateExtend”. Remarks are stored with the ExpireChg transaction.
PRODUCT
setup
Enter the publication for which you are creating bonus day adjustments.
BONUS DAY DATE
date
Enter the date of the bonus day for which you are creating adjustments.
EXPORT FILE
open (20)
The Bonus Day Adjustment utility will export an ASCII file of bonus day subscribers and adjustment amounts or days. Enter the file name for this file. It will be exported to the /dti/exchange/cm
directory. See Bonus Day Adjustment Export Format for the file format.
INCLUDE ACTIVE SUBSCRIBERS
yes/no
Indicate whether subscribers who would normally receive a paper on the bonus day should be included in the export.
INCLUDE ACTIVE AUTORENEW SUBSCRIBERS,
INCLUDE ACTIVE ONLINE SUBSCRIBERS,
INCLUDE ACTIVE MAIL SUBSCRIBERS
yes/no
If including active subscribers, indicate whether auto renew, online, and/or mail subscribers should be included.
INCLUDE BONUS DAY AUTORENEW SUBSCRIBERS
yes/no
Indicate whether autorenew subscribers who normally would not receive a paper on the bonus day should be included in the export.
DELIVERY SCHEDULE
display
The selected delivery schedule is displayed.
DISTRICT
setup
Enter the district whose routes should have bonus day adjustment that will apply to this delivery schedule, or enter “*” to multi-select districts.
TYPE OF ADJUSTMENT
predefined
Select the type of bonus day adjustment that will apply to this delivery schedule. The options are Extra Charge, Total Charge, Days Rate, and Number of Days.
AMOUNT
decimal (8)
If Type Of Adjustment is “Extra Charge,” “Total Charge,” or “Number of Days,” enter the amount that subscribers should be charged for this bonus day. Note: When entering the amount for a “Number of Days” adjustment, enter the total number of days that should be deducted from the subscription period for this bonus day.
THIS DAYS RATE
predefined
If Type Of Adjustment is “Days Rate,” select the weekday whose rate should be charged for the bonus paper.
This section guides the user through the menu options that are available under the System menu.
This section guides the user through the menu options that are available under the Setup menu.
This section guides the user through the menu options that are available under the Tools menu.
Use this feature to automate the execution of certain options. For example, you can set up some publishing run processes in one batch, or run a group of reports. Most options that produce output can be included in batches (e.g., reports, account billing, the publishing run). Options that input data into the system (such as Services and Setup options, payment entry options, or Press Room Entry) cannot be included in batches.
One aim of batch processing is to reduce the time spent entering parameters for Circulation’s processing options. For example, parameters must be entered for multiple options during the publishing run (starting the run, printing bundle tops, the DM report, etc.). Since the publishing run will generally be processed with the same parameters every day, these parameters can be saved as part of a batch and run automatically.
Another advantage to batch processing is that it reduces the chance for errors due to incorrect parameters being entered. Also, it can allow a sequence of events, such as an account billing run, to proceed without needing operator intervention. A newspaper could have its account billing run set up as a batch process, and instruct a night operator to run the process before leaving at midnight. The account billing run could then process when there was no other activity on the system.
Note: Circulation does not validate prompt entries in batch processing. Therefore, you must be sure that what you enter for these prompts is valid.
Save the parameters for each option to be included in the batch by selecting Save from the option’s strip menu (see Save and Find). You may set up fields that should be prompted for when the option is run, and these prompts will appear (in alphabetical order) before you run your batch.
During the Save, be sure to check the settings in the View & Print Options Window—these settings will be used by the batch when processing the report. You will want to have either View or Save set to “y”. In File Name, you may want to change the file name extension to “<N>” (current day of month) “<D>” (current week day) or “<M>” (current month). For example if your file name is “RTL” and the batch is run on the Wednesday June 5th, the extensions would result in the following file names:
RLT.<N> would result in RLT.05
RLT.<D> would result in RLT.WED
RLT.<M> would result in RLT.JUN
Use Batch Setup to assemble the saved parameters for the options you want to include into a batch.
Enter the View/Print Utility and select Run to run the batch. Or, run the batch from a UNIX prompt (see Running a Batch from a Command Line).
After parameters for each option to be included in the batch have been saved, the batch can be set up using this option.
Select Batch Setup from the System menu to display the Batch Setup screen.
Select Add and complete the following fields.
BATCH
open (8)
Enter a name for this batch. For example, you might call a batch “Monday” if it is to be run every Monday.
DESCRIPTION
open (30)
Enter a description for this batch.
USER NAME
setup
Enter your user name. This will be the user that prints on any reports generated by the batch.
SECURITY
setup
Select Specifics to add individual options to this batch (see below).
Select Accept to complete the batch setup. The batch is now ready to run. Note that you cannot Accept this record until you define a batch input record by selecting Specifics.
After a batch has been set up, specify the options that should belong to the batch with this specific. Each option must have a previously saved file containing field parameters for that option.
Select Specifics | Batch Setup
from the Batch Setup screen to display the Batch Input Setup screen.
Select Add and complete the following fields.
BATCH
display
Circulation displays the batch name entered on the Batch Setup screen.
SEQUENCE NUMBER
integer (3)
Enter a sequence number for this option. The sequence number determines the order in which the option will be run in the batch (i.e., option 10 will run before option 20). Enter sequence numbers in increments of 10 so that you can add an item without having to re-sequence all items.
INPUT TYPE
predefined
Indicate if this batch consists of input files or batch (subbatch) files. Enter batch only if you have previously set up another batch and you want it to run as part of this batch.
INPUT FILE
open (40)
If you entered input in Input Type, enter the file name (case sensitive) under which the parameters for this option have been saved.
SUB BATCH
setup
If you enter batch in Input Type, enter the name of the batch that should be processed.
Select Accept to accept the file. You can now add other saved files to the batch, or press F4 and select Exit to return to the Batch Setup screen.
You may find it more convenient to run a batch from a command line or job scheduling software than from the View/Print Utility. To run a batch in this manner, you simply enter a batch print command at the UNIX prompt or in the job scheduler. The format for the batch print command is:
<app> -b -B /tmp/batch.log -p viewprint/initbatch -P “<batchname>”
<app>
is the application name. In most cases it will be “cm”.
-b
tells the program to skip the display of the startup banner.
-B
puts the process into background mode and sends the regular output to the file /tmp/batch.log
.
-p
specifies the program to run, in this case viewprint/initbatch
-P
specifies the name of the batch
cm -b -B /tmp/batch.log -p viewprint/initbatch -P “AAMDaily”
This would run the batch “AAMDaily”. In addition to the batch name, parameters for set fields can also be specified in the “-P” command. For example, if batch “AAMDaily” includes the Daily AAM and AAM History reports, and you have set up the batch to prompt for Start Date and End Date in both reports, you could specify them by expanding the “-P” command like this:
-P “AAMDaily:STARTDATE=01/15/2001,ENDDATE=01/31/2001”
Note: If date fields use the “today” variable, you do not need to specify them in the -P statement; the current system date will be used automatically.
PRODUCT
setup
Select the product for which you will delivery a bonus day paper.
DELIVERY SCHEDULE
setup
Select the delivery schedule that will receive the bonus day paper, or enter “*” to multi-select delivery schedules in the Delivery Schedule popup window.
BONUS DATE
date
Enter the date for the bonus day.
ALL DISTRICTS
yes/no
Bonus days may be defined for specific districts, or include all districts. Check this field if the bonus day paper will be delivered to all districts. Note: If you charge for bonus days using the “premium day” method (see Premium Day), bonus days cannot be set up for specific districts. All Districts will display as checked and District will display as“*”.
DISTRICT
setup
If the bonus day will only be delivered to specific districts, leave All Districts unchecked and specify the district here (enter “*” to multi-select districts). Only subscribers on the selected delivery schedules who are delivered by routes in these districts will receive the bonus paper for that date.
PAID CIRCULATION
yes/no
This field controls whether bonus day papers for a delivery schedule/district should be counted as paid or unpaid draw on the AAM reports. If “y” is entered here, the bonus day draw will be stored with the subscriber’s billing method (office pay, carrier collect, etc.). If “n” is entered, the bonus day draw will be stored as sample draw.
INCL OPT OUT SUBSCRIBERS
yes/no
Indicate if you want to include subscribers who have opted out of bonus days. For this field to be available, the Business Rule, What is the default reason code for bonus day transactions for subscribers who opted out of bonus day papers? (Customer Services section), must be set. The field is not available if you charge for bonus days using the “premium day” method.
PROJECTED
yes/no
If bonus days have been copied from an old year to a new year (see Copy Bonus Day Setup), the new bonus days will have Projected flagged to indicate that they are projected bonus days and need review. The bonus day can then be modified and Projected unchecked to indicate that it has been reviewed. Projected will be inactive when adding a new bonus day (rather than copying). Note: Having Projected checked does not prevent bonus day transactions from being created for a bonus day; the field is for reference purposes only.
DELIVERY METHOD
yes/no
Indicate whether subscribers who are delivered by route, mail, online subscribers, or “*” (for multi-select window) should receive this bonus day paper.
Online subscribers qualify for receiving bonus days on any day of the week if their address can be delivered by route. For example, it is possible to schedule a bonus day print delivery for online subscribers on a weekday for which they also have online access.
LABEL GROUP
setup
For a mail-delivered subscription, enter the mail label group for this subscriber.
ADJUSTMENT TYPE
predefined
This field pertains only if you charge for bonus days using the “premium day” method. Indicate whether the bonus day charge should be “Additional” (in addition to the subscriber’s copy rate for that day, if they receive the paper) or “Final” (total charge for the bonus day paper). See Premium Day for an example of premium day charges using the different adjustment types. If the bonus day is free or if you use the “traditional” method for charging bonus days, leave this field blank (Amount and Renewal Description will remain grayed out).
AMOUNT
decimal (5)
This field pertains only if you charge for bonus days using the “premium day” method. Enter the premium amount for the product, delivery schedules and delivery methods selected.
RENEWAL DESCRIPTION
open (30)
This field pertains only if you charge for bonus days using the “premium day” method. Enter the description that should print on renewal notices for the bonus day. The field will be exported with other premium information to the Detailed Export 2 format, if the Business Rule— Should premium day detail be exported in renewals? is set to “yes”.
PRODUCT, DELIVERY SCHEDULE
setup
Enter the publication and delivery schedule for which to create bonus day transactions. You may enter “*” to multi-select delivery schedules.
BONUS DATE
date
Enter the bonus date for which bonus day transactions should be created. This date must be defined as a bonus day in advance (see Bonus Day Setup).
SOURCE, REASON
setup
Enter the source and reason codes for creating the bonus day transactions. The reason code must be specifically set up for bonus days.
PRODUCT
setup
Select the product whose bonus days should be copied, or select “*” to multi-select products.
DELIVERY SCHEDULE
setup
Select the delivery schedule whose bonus days should be copied, or select “*” to multi-select delivery schedules.
FROM YEAR, TO YEAR
integer (4)
Enter the year bonus days should be copied from, and the year they should be copied to. Both years must be formatted to four digits (e.g. “2016”).
UPDATE OPTION
predefined
Indicate whether to run the copy in edit or commit mode. Edit mode will generate a processing report, but not copy the bonus days. Commit mode will copy the bonus days.
PRODUCT
setup
Select the product to which the delivery schedule change will apply.
EFFECTIVE DATE
date
Enter the date on which the delivery schedule changes will be made.
SOURCE
setup
Select a source code for these transactions.
SUB SOURCE
setup
Select a subsource, if required.
IN GRACE REASON CODE, PAID REASON CODE
setup
Select a reason for the transactions that will be created. You can use different reason codes for in-grace subscribers and paid subscribers. Note: It is recommended that you use reason codes that are set up with Update Expire=”no” in these fields. Reason codes that update the expire date can cause expire dates to move backward instead of forward.
NEW SCHEDULE
setup
Select the new delivery schedule that will be assigned.
OLD SCHEDULE
setup
Select the old delivery schedule that will be changed.
DELIVERY TYPE
setup
Select the delivery type to which these changes will apply (e.g., “carrier”, “motor”, etc.). Select “*” to multi-select.
RATE FILE
open
Enter the name of the rate file that contains the old rate and new rate. The file must be in /dti/exchange/cm and be formatted as follows: <old rate> | <new rate>.
REMARKS
open
Enter any remarks for the transactions that will be created. Remarks will be visible on the Delivery Schedule Change transaction screen in Customer Service.
READ OPTION
predefined
Select Edit to see the transactions that will be created, or Create to actually create the transactions.
PRODUCT
setup
Select the product or products for which subscription-length pricing should be updated.
RATE CHANGE DATE
date
This field is used to calculate pending (i.e., future) rate changes for renewal notices and auto payments. Enter the date through which pending rate changes should be calculated.
EXCLUDE
predefined
If applicable, select the solicitation code or codes of subscribers who should be excluded from this update.
UPDATE LEVELS
yes/no
If you select this checkbox, the relevant demographics (defined in Business Rules) will be updated with a new level and “update” date.
UPDATE RATES
yes/no
If you select this checkbox, billing changes will be created to move the updated subscribers to the appropriate rate code for their subscription level.
REVIEW DATE
date
If you are updating rates without updating levels, enter the review date. This date must match the date stored in the date demographic for the subscribers whose rates will be updated. Note: This field is used when the levels were previously updated without also updating the rates. Billing changes will be created for these subscribers as long as the date entered here matches the date in the “subscription length level change” demographic.
SOURCE
setup
Enter the source code for the billing change transactions that will be created.
PAID REASON
setup
Enter the reason code for the billing change transactions that will be created for paid subscribers.
IN GRACE REASON
setup
Enter the reason code for the billing change transactions that will be created for in-grace subscribers.
FILE NAME
open (20)
Enter the file name of your ACS file. The file must be placed in the /dti/exchange/cm directory; see Appendix B for the format.
REPORT ONLY
yes/no
ACS Update can be run in a report-only mode (no temp stops will be created and no demographics will be updated). If you only want to create the report, enter “y” here.
EFFECTIVE DATE
date
Enter the date for which to create temporary stops and update demographics.
SOURCE
setup
Enter a source code for the ACS update.
REASON
setup
Enter a reason code for the ACS update. This reason code will be used with any temporary stop transactions created by it.
OCCUPANT DEMOGRAPHIC
setup
Enter the ID of the occupant demographic that should be updated as part of this process.
DEMOGRAPHIC ANSWER
setup
Enter the answer that should be updated with the demographic. Subscribers that are matched by the update will receive this answer to the demographic question above.
PRODUCT
setup
Enter the product ID.
INCLUDE COMBOS
yes/no
Indicate with whether to include combos from the report.
SELECTION TYPE
predefined
Indicate whether this report should include a particular area, region, zone, district, route, or mail.
SELECTION
setup
Enter the area, zone, district, or route (depending on what type is entered above) to include. If you entered “mail” above, this field will be skipped.
BILLING METHOD
predefined
Specify the billing method to include in the report. Choices are office pay, carrier collect, paid complimentary, unpaid complimentary, or * (to multi-select billing methods).
DELIVERY SCHEDULE
setup
Specify the delivery schedule to include in the report or enter “*” to multi-select delivery schedules.
IN GRACE ONLY?
yes/no
Select this check box if you want to limit the search to mail subscribers who are in grace.
ALL RATE CODES RATE CODE
yes/no setup
Indicate if you want to include all rate codes in the report. If not, enter the rate code or codes (using multi-select) to include.
DELIVERY STATUS
predefined
Select active, temp stopped, or both.
DAYS STOPPED
integer (4)
Enter the minimum number of days a subscriber must be stopped to appear in the list. This field is skipped if Delivery Status is set to “active”.
PROCESS OPTION
predefined
Select Report Only to generate a list of subscriptions that meet the criteria entered in this window. Select Create Stops to create the actual stop transactions.
STOP DATE
date
Enter the date that stop transactions will be created.
SOURCE
setup
Enter the source code for the stop transactions you will create, such as “customer” or “carrier”.
SUB SOURCE
setup
If this field is active, enter a sub-source for the stops (for example, the carrier who called in the stops).
STOP REASON
setup
Enter the reason code for these stops, such as “bad check”.
RESTART DATE
date
For temporary stops, enter the restart date.
RESTART REASON
setup
For temporary stops, enter the restart reason. Not available when using Report Only.
DONATION CODE
setup
For temporary stops, optionally enter the donation code. If a donation code is entered, all days of the temp-stop period will be donated.
This option is used to accept all suspended batches of subscriber payments that are not currently in use.
Imported and system-generated batches (such as Customer Services payment batches) will only be auto-accepted if the Business Rule— Should batches that are imported or created by the system be accepted automatically? is set to “Yes.” If these batches can be auto-applied, one-time bank draft batches from Customer Services will only be applied if another Business Rule— Should payment batches containing one-time bank draft payments be auto accepted?, is set to “Yes.”
Select Subscription/Address | Auto Accept Batches
in Graphical Utilities to display the Auto Accept Batches window. Currently, only subscriber payment batches can be accepted automatically, and the Batch Type field cannot be modified.
Click Add.
Click OK to accept all open batches.
Select Check Date & Time from the System menu to display date and time information. Press Enter to exit to the main menu.
There are two methods to control the viewing and printing of reports that you create in Circulation, as shown below.
Method #1
Method #2
Select Utilities | System | View/Print to access the View/Print Utility (documented here). You may only access reports that have been saved to “spool” (disk). Reports are saved to spool if SAVE is set to “y” in the View & Print Options window.
Select View/Print from the System menu to display the View/Print Utility screen.
Strip menu options on this screen are described in the following table.
Modify
View
Background
When a report is run, you may specify (in the When field of the View & Print Options window) that it should be run as a background process. The screen will then be freed for other uses while the report is processed, but you will only be able to view it in the View/Print Utility. This option allows you to view field settings for reports that are (or were) running in the background. A selection window will open for you to multi-select the report settings to view (Enter selects, F1 accepts). If you select more than one, press the space bar to move from one viewing to the next. If you do not have any background jobs on record, this option will not appear.
Reports
Use this option to view reports that are stored in spool. A multi-select window will open for you to select reports to view. Once a report appears, use the arrow keys to scroll and press F4 to exit. If the terminal type VT100 is being used, the screen will automatically widen to display all 132 characters of a report. The screen will return to its normal size when you have finished viewing the report.
Deferred
After setting up a report, you may choose to defer it (by setting When to “Deferred” in the View & Print Options window). This option allows you to view the field settings for the report. A multi-select window will open for you to select settings to view. Press the space bar to exit or move on to the next viewing.
Input
Reports
Use this option to print reports saved to spool. A multi-select window will open for you to select report settings to print.
Range
If you want to print only a portion of a report, use this option. Choose the report to print from the multi-select window. Scroll to the first line that should be printed, and type “s” (for start). Then, go to the last line that should be printed and type “e” for end. Press F1 to print the portion you have selected.
Status
This option allows you to view the status of all printers on the computer system. Information about each print job is shown, including the queue name, the printer status, the job ID, the names of the files being printed, the user ID of the person initiating the print job, the number of pages printed, the percent of the total job printed, the number of blocks in the file, the number of copies requested, and the rank of the print job in the spooler print order. Press Enter to return to the View/Print Utility screen.
Cancel
Select this option to cancel a print job because, for example, paper has jammed the printer. Before printing can continue, the job must be cancelled and the problem fixed. You are prompted to enter the ID of the job to cancel (this can be found by selecting Status, above), or the printer ID if there is only one job running on that printer. After you enter the job ID, the job is cancelled and the View/Print Utility screen reappears.
Disable Printer
You can disable (bring off line) a printer with this option. You may want to do this to print forms, or to stop a job that was mistakenly sent. When you select this option, you are prompted for the printer to disable. The View/Print Utility screen then reappears.
Enable Printer
This option allows you to enable (bring back on line) a printer that has been disabled. Printers might be disabled because of form printing (see below), a canceled print job, or a paper jam, among other things. You should designate one person (e.g., the system administrator) to enable and disable printers, to avoid confusion. Enabling and disabling do not work on Sun systems. When you select this option, you are prompted for the printer to enable. The View/Print Utility screen then reappears.
Run
Deferred
This is where you process deferred reports. Select the report to process from the multi-select window. After processing is complete, the report can be viewed or printed by other options in the View/Print Utility.
Background
Use this option to run background reports, if the report failed to run for any reason.
Batch
Archive
Append
Archive files are spool files (reports) to which other spool files can be added. For example, you may keep all of your Subscriber Payment Journals for one month in one archive file, and then transfer the file to diskette. To append a report to an archive file, enter the archive file name in Archive File and then select the reports to acrhive in the multi-select window. The reports will be added to the archive file and the View/Print Utility screen will appear. You can then delete the reports that were appended.
Copy
Use this option to copy a report to the archive area (i.e., make it an archive file). If an archive file of the same name exists, it will be overwritten. Using the Subscriber Payment Journal example again, each month after the archive file was transferred to disk, you could copy the next Journal and thus start the file again. To copy a report, choose the report(s) to copy from a multi-select window, and then specify the name of the archive file that will be created.
Move
This is the same as Copy, above, but the report(s) selected will be removed from the report area and will exist only as an archive file. If there is already an archive file with the same name, you will be prompted whether to replace it.
Replace
This is the same as Move, above, but you will not be prompted if there is already an archive file with the same name.
Delete
Background
This option allows you to delete reports that were run as background processes. A multi-select window will open for you to specify the reports to delete.
Reports
This option allows you to delete reports from spool. You should delete unneeded reports regularly in order to conserve disk space. A multi-select window will open for you to specify the reports to delete.
Input
This option allows you to delete input files for batch processes. A multi-select window will open for you to specify the input files to delete.
Scan
This is a “refresh” option that causes Circulation to re-read the report spool area.
The Process Log is a record of all report inputs, warnings and errors that develop while running jobs. You may want to delete log files that are older than a certain date, in order to save disk space.
Select Purge Process Log from the System menu in Graphical Utilities to display the Purge Process Log screen.
Enter the cutoff date and log type.
CUTOFF DATE
date
Enter the cutoff date. Only processes that occurred on or before this date are purged. Choose a cutoff date 30-45 days prior to the current date. Process log information should be retained for at least 30 days for error tracking purposes.
LOG TYPE
predefined
Indicate what should be included in the report: info (general information about processes started and completed, etc.), warning (minor errors which do not affect data integrity), error (a more significant problem which may affect data integrity), or fatal (an error which causes some or all processing activity or printing to cease or be skipped). Enter “*” to multi-select log types.
Click OK and then Continue to begin the purge.
Select Check Disk Space from the System menu to display disk space information. Press Enter to exit to the main menu.
Select Who’s Logged In from the System menu to display a list of users logged into your system.
If there is more information than can display on one screen, press Enter to scroll down. Press Enter (or F4 and Enter) to exit to the main menu.
The Process Log contains two kinds of information:
Inputs and processing messages from any process that produces a report. This includes transaction and account bill processing, for example, as well as all of the options on the Reports menu.
Error messages from transactions. Most of these transactions are entered in Services. If a transaction does not produce an error, it will not be entered in the Process Log.
Select Process Log Report from the System menu in Graphical Utilities to display the Process Log List screen.
Click Add and complete the following fields.
START DATE END DATE
date
Enter the date range to cover in the report.
ALL LOG CLASSES LOG CLASS
yes/no predefined
To include all messages in the Process Log, check All Log Classes. Or, select the log class to include: Indicate whether the report should include info messages, warnings (minor errors that do not affect data integrity), more significant errors, or fatal errors.
ALL USERS USER NAME
yes/no open (60)
Select the user(s) whose processes would be included in the report, or check All Users to include log messages from processes run by all users.
ALL TITLES TITLE
yes/no predefined
Enter the title of the report area under which these messages were produced, or check All Titles to include all reports. Click the lookup icon to the right of the Title field to display a list of report titles. Customer Service transactions are valid but they are not included in the lookup.
FUNCTION LIST
predefined
Enter the function (such as “transfer in” or “validate truck name”) to include in the report. We recommend that you enter an asterisk (*) to include all functions.
TTY LIST
open (60)
Enter the terminal ID to include in the report (enter “*” to include all). Your terminal ID will default.
Select OK and then Continue to produce the report.
When writing a custom program or using Results (where you create ad hoc reports), it is useful to have a list of all files where a certain field is referenced. Use Find Fields to produce this list.
Select Find Fields from the System menu to display the Find Fields Report screen.
Select Add and enter a text string for which you want to search. You can press F2 to select from a list of exact field names.
Select Continue to produce the list. The list can be viewed and printed like other reports.
This option is useful when setup must be changed for a large number of routes. For example, say that the Sunday edition for all routes in a certain district must be changed from “Early” to “Final”. Instead of modifying route setup for each route individually, you can run Bulk Route Changes and change all the routes at once. The setup information that can be updated with this tool includes:
District
Edition
Depot
Service Area
Delivery Schedule
Insert Group (InsertPlus sites only)
Route Class
Route Name
Allow Office Pay Flag
Allow Carrier Collect Flag
Note:
Setup information cannot be blanked out with this option. For example, if you wanted to change the rate class for a group of routes from “super” to blank, you would have to modify the routes individually.
Select Bulk Route Changes from the Setup menu.
Select Add and complete the following fields.
PRODUCT
setup
Enter the product to which these routes belong.
ROUTE OPTION
predefined
Indicate whether bulk changes are being made to home delivery routes, single copy routes, or both.
SELECTION TYPE
predefined
Indicate whether this utility should change routes in a particular district, zone, region, or area, or an individual route.
SELECTION VALUE
setup
Enter a particular district, zone, region, area or route (depending on the selection type entered above) for which to run the utility, or enter “*” to multi-select.
EFFECTIVE DATE
date
Enter the date on which the setup changes should take effect.
DISTRICT SERVICE AREA DELIVERY SCHEDULE INSERT GROUP ROUTE CLASS ROUTE NAME SINGLE COPY LOCATION ALLOW OFFICE PAY ALLOW CARRIER COLLECT EDITION (SUN - SAT) DEPOT (SUN-SAT) DEPOT DROP ORDER
setup setup setup setup setup open (25) open (30) yes/no yes/no setup setup integer (8)
For each setup item that should be changed, enter the new value. If an item should not be changed, leave it blank. For example, if you only want to change the Sunday edition from “Early” to “Final”, enter “Final” in the first EDITION field and leave all other fields blank.
Select Continue to make the route setup changes. For each route, the utility will look for an existing record with the values entered here; if it cannot find a record with these values, it will end date the old record and create a new record using the Effective Date field as the start date.
The exceptions are delivery schedule and route name. A new delivery schedule record is created for the route if one does not already exist; however no other delivery schedule records are modified. In the case of route name, the existing record is changed to reflect the new name. After the route changes have been made, the Bulk Route Changes report will appear, listing all of the records that have been created or changed.
The performance analysis tools can be used by system administrators and others to determine the users and processes that are affecting system performance. These tools are primarily database tools; they display the total number of reads, writes, and accesses to a database either by user or by database table. There are two basic types of tools:
Reports. The Table Statistics Report, Index Statistics Report, and User Statistics Report list the number of reads, writes, and accesses to a table, index, or by a user since the database was started.
Interactive Tools. The User Statistics and Table Statistics interactive tools display the number of reads, writes, and accesses to a database within a time period (for example, the last 10 seconds), by user or table.
These tools are based on Progress VSTs (Virtual System Tables—see your Progress documentation for more information on VSTs). The tools can help you analyze system performance issues. For example, if subscriber payment processing is taking an unusually long time, you could run the Table Stats tool to see how many records are being written while it processes, and what tables are involved.
There are three reports that can be run to analyze system performance:
The User Statistics Report lists the number of reads, writes, and accesses to one or more databases by the current sessions. Each session’s user name is listed, and the sessions are listed in order of total number of accesses (with the highest users at the top of the report). The report can be run in detail mode (each database broken out separately) or in summary mode (only one line for all databases).
The Table Statistics Report lists the number of reads, writes, creates and deletes that have been made to each table in one or more databases since the database was started. The report can list tables alphabetical by table name, or in order of reads (with the tables with the most reads at the top of the report).
The Index Statistics Report lists the number of reads, writes, creates and deletes that have been made to each index in one or more databases since the database was started. The report can list tables alphabetical by index name, or in order of reads.
All of the reports have the standard view/print options.
The interactive tools give a snapshot of what is going on in the system between regular time intervals. There are two interactive tools. The User Statistics tool displays the reads, writes, and accesses for the top users within a given period of time. The Table Statistics tools displays the same thing, but for tables rather than users.
Whether users should be sorted in order of the number of database writes, reads, or accesses. With tables, the sorting can be in reads, updates, creates or deletes.
The number of users (or tables) displayed.
Whether to update the display and, if so, the time interval (in seconds) at which the display is updated.
Whether the number should be the number of reads, writes and accesses since the tool was started (cumulative) or since the display was last updated.
Once started, the tool will display the top users or tables. If run with Repeat = “y”, the screen will update every fifteen seconds (or whatever time period you entered in Every).
To exit from the interactive tools, press F4.
Circulation stores a great deal of detailed information—such as subscriber transactions, route draw detail and service messages—that may be purged from the system after a certain time period, in order to conserve disk space. How long history should be kept varies with the type of detail. For example AAM history should be kept as required by the Audit Bureau of Circulation, depending on your audit cycle.
Detailed information can be purged from the History Purge menu. The same standard process is used in all purges, as described below.
Select the appropriate option from the History Purge menu. For example, to delete AAM circulation data, select AAM Histories. Each of these options is described below.
Select Add and enter the purge fields. The fields will differ from option to option, but there will always be a Cutoff Date field. Detail information that was created on or before the date you enter here will be deleted from the system.
Select Continue to begin the purge.
A Processing Status window will display the number of records purged as it proceeds. When the purge is completed, you may be prompted to press the space bar.
You can purge historical AAM circulation figures with this option. Circulation is retained for AAM zone, AAM Zip code, and AAM Town on a daily basis. This information is used for AAM reporting, so be sure that you will not need to run AAM reports for any dates before the cutoff date. The fields for this purge are described below.
PRODUCT
setup
Enter the product for which to delete AAM history audit records. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only historical data from on or before this date will be purged. AAM must be closed through Cutoff Date for the purge to process. This can be done by via Utilities | Close Day For AAM.
AUDITS COMPLETED
yes/no
Indicate whether you have been audited for the AAM through the cutoff date. If you enter “n” in this field, no purge will take place when you select Continue.
This option enables you to purge audit trail records of address, occupant and subscription modifications, deletions and additions made on or before a specified cutoff date. The data, of course, will remain in the database—only the audit trail records will be deleted.
Note: If you plan to produce 1099s, do not purge charges for the current reporting year.
This option allows you to purge records of charges (except those for the current year or later) and credits incurred by accounts before a specified cutoff date. Purging charge records will not change account balances. The fields for this purge are described below.
PRODUCT
setup
Enter the ID of the product for which to delete account charge audit records. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only historical data on or before this date will be purged.
1099s COMPLETED
yes/no
Indicate whether you have completed the 1099 tax forms for your carriers for this year. If you enter “n” here, no purge will take place when you select Continue.
This option allows you to purge demographic answers based on an entered Demographic and Cutoff Date.
Circulation has the ability to import phone numbers on the federal Do Not Call list, or another DNC list, creating database records (see Do Not Call List for more information on DNC lists). Over time, many end-dated Do Not Call records may accumulate in the Circulation database. These records can be removed by the Do Not Call List purge utility. You must specify a cutoff date, and the DNC list to purge.
Use GL Batch to purge transactions that have been interfaced (i.e., “posted”) to the general ledger using the Accounting | Fiscal Close - GL | Export GL
option. You may delete history by specific journal codes if desired (see GL Interface Journal for more information about journal codes). The following table describes the fields for this purge.
PURGE TYPE
predefined
Indicate whether to purge GL transactions by batch or date. Note: When purging transactions by date, all posted GLBatch and GLTran records in which the GLBatch. GLTranDate is less than the entered date will be deleted.
BATCH
setup
This field is active only if you are purging by batch. Enter the ID of the batch to delete.
CUTOFF DATE
date
This field is active only if you are purging by date. Enter the cutoff date. Only transaction histories associated with batches processed on or before this date will be purged.
JOURNAL CODE
predefined
This field is active only if you are purging by date. Enter the journal code for which to delete transaction history (press F2 for a lookup of valid codes). To include all codes, enter “*”.
Customer and route messages are entered in Services, and can be dispatched or displayed at the bottom of the screen. The message purge fields are described below. Dispatch transactions are also deleted by this option.
PRODUCT
setup
Enter the product for which messages should be purged. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date for the purge. Any messages with an end date that is on or before this date will be deleted.
You can use this option to purge postal history—information about label groups, PO Zones, and mail sorting that is created by the Daily PO Report and used by the Financial PO Report. You may not purge PO history records within the current month. If you use PostWare, only some of this detail will be created, and it will not be used for PostWare reports (PostWare keeps its own history). The following table describes the fields that must be entered to do a PO history purge.
PRODUCT
setup
Enter the product for which to delete PO histories. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only PO histories of periods on or before this date will be purged.
AUDITS COMPLETED
yes/no
Indicate whether your postal audits have been completed through this date. If you enter “n” here, no purge will take place when you select Continue.
This option can be used to purge Product Address records (created by TM Processing) for a specific TM product and cutoff date. The purge fields are described in the table below.
PRODUCT
setup
Enter the product for which to delete Product Address records. Enter “*” to multi-select products. Note that only TM products are available, as these are the only products that have Product Address records.
CUTOFF DATE
date
Enter the cutoff date. All Product Address records for the selected products for dates on or before the cutoff date will be purged.
The option allows you to purge Publishing Info setup records (which define the barcodes to be used for the publication on a given issue date). See Publishing Info in the Setup manual for more information. This option is accessed on the History Purge menu in Graphical Utilities.
PRODUCT
setup
Enter the publication for which to delete Publishing Info records. Enter “*” to multi-select publications.
CUTOFF DATE
date
Enter the cutoff date. All Publishing Info records for the selected publications for dates on or before the cutoff date will be purged.
Route draw history, which is required to produce bundle tops and other distribution documents, can be purged with this option. This purge will delete only home delivery route history (single copy draw history can be deleted with Single Copy Draw). The following table describes the route draw purge fields.
PRODUCT
setup
Enter the product for which to delete route draw histories. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only route draw histories for dates on or before the cutoff date will be purged.
DRAW TYPE
predefined
Indicate whether advance draw should be purged, actual draw, or both draw types. If Draw Type is set to “advance”, advance draw for any date prior to the publishing date may be purged. If Draw Type is set to “actual” or “both”, only draw that is more than a year old may be purged.
Use Route Draw Adjust to purge the history related to returns and draw adjustments (except within the current year) done for home delivery route draw. The route draw adjust purge fields are described below.
PRODUCT
setup
Enter the product for which to delete route draw adjust histories. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only route draw adjustments for dates on or before the cutoff date will be purged.
Use Route Transactions to purge the history related to draw changes and shortage information. The route transaction purge fields are described below.
PRODUCT
setup
Enter the product for which to delete route transactions. Enter “*” to multi-select products.
TRAN TYPE
date
Enter DrawChange, OutletNote, OutletStart, OutletStop, or Shortage. Press F2 for lookup; enter “*” to multi-select transaction types.
INITIAL DATE
date
Enter the date from which the purge cutoff date will be calculated.
This option allows you to purge the draw history (except within the current year) for single copy routes. The following table describes the fields you enter to purge single copy draw.
PRODUCT
setup
Enter the product for which to delete single copy draw histories. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Single copy draw histories for dates on or before the cutoff date will be purged.
DRAW TYPE
predefined
Indicate whether advance draw should be purged, actual draw, or both draw types. If Draw Type is set to “advance”, advance draw for any date prior to the publishing date may be purged. If Draw Type is set to “actual” or “both”, only draw that is more than a year old may be purged.
Select Single Copy Draw Adjust to purge the returns and draw adjustments (except within the current year) done for single copy routes. The single copy draw adjust purge fields are described below.
PRODUCT
setup
Enter the ID of the product for which to delete single copy draw adjust histories. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only single copy draw adjust histories for dates on or before this date will be purged.
Use this option to purge subscription transaction history. This includes renewal notices, payments, starts, expires, and other transactions entered for subscribers in Services. The following table describes the subscription transaction purge fields.
Note: Purging subscription transaction history can impact future transactions and subscriber activity. Please contact Naviga Global Support before purging this information.
PRODUCT
setup
Enter the product for which to delete subscription transaction history. Enter “*” to multi-select products.
TRAN TYPE
predefined
Enter the transaction type to purge, or enter “*” to multi-select transaction types.
INITIAL DATE
date
Enter the cutoff date. Only subscription transaction history dated on or before this date (minus the number of retention days defined) will be purged. See Tran Type Publication in the Setup Manual for more information about retention days.
TM draw records are created for a TM product’s routes when the product is processed. Draw records for past dates may be deleted, however you should not delete unbilled TM draw, if you credit carriers for TM delivery. Select TM Draw and enter the product and cutoff date for the purge.
PRODUCT
setup
Enter the product for which to delete TM draw, or “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only TM draw for dates on or before this date will be purged.
Completed tasks can be deleted by the Task Purge utility. All tasks completed up to and including the cutoff date entered will be purged.
CUTOFF DATE
date
Enter the cutoff date for purging tasks. Only tasks completed as of this date will be purged.
Unearned Revenue transactions are created when processing the Unearned Revenue Report in “update” mode. These transactions are used to define the prior unearned revenue when processing the next fiscal period. Select Unearned Revenue to purge these transactions. The following table describes the unearned revenue purge fields.
PRODUCT
setup
Enter the product for which to delete unearned revenue history. Enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date. Only unearned revenue history for dates on or before this date will be purged.
This option will delete context data from the system (SessionContext and SessionTempTable tables), as of a specified cutoff date (default is two days prior). A warning is displayed if a cutoff date of less than two days prior is entered.
Note: The cutoff date should not be entered for the system date while graphical sessions are active.
Select Purge Session Data from the System menu to display the Session Context Purge screen.
Enter the cutoff date.
Select Accept to begin the purge.
Press the spacebar when the purge is complete.
Bulk Router Updates allows you to change the default route, Town of 25, or AAM zone for all router address ranges that fall within the area specified. For example, if all subscribers on Colfax Ave are now being delivered by route 15 instead of routes 4, 12, and 7, you could make one bulk change here instead of modifying several router records.
See for more information about routers.
Note:
If you run this utility by Zip code, no router records that are based on city will be updated. The reverse is also true: if you run the utility by city, no Zip code-based router records will be updated.
Select Bulk Router Updates from the Setup menu to display the Bulk Router Updates screen.
Enter router update information in the following fields.
Select Accept to make the router changes.
Although they can be modified using the Trip Delivery Seq option above, trip sequences must initially be imported into Circulation using this import utility.
Select Trip Del Seq Import from the Setup menu to display the Trip Delivery Seq Import screen.
Select Add and enter the name of the import file. The file must be located in the /dti/exchange/cm
directory. See Appendix B for the file format.
Select Continue to import the file. After the import has completed, a processing report will display the number of records read and any errors that occurred.
The Route Type Change utility can be used to change the route type for one or more routes, or all routes in one or more districts. In addition, changes can be made to:
Allow Carrier Collect and Allow Office Pay flags for the routes selected. This may cause billing changes for subscribers on the route, for example if an office pay subscriber’s route is changed to a carrier collect only route—a billing change would change the subscriber’s billing method from office pay to carrier collect.
Credit statuses for subscribers on the routes selected. If the credit status is changed, end grace transactions can be created if the subscriber’s grace period changes and the subscriber is currently in grace. You may optionally generate tasks as part of this process.
Grace periods. Grace periods may be changed because of route type changes (grace periods can be defined by route type). End grace transactions would also be created in this scenario.
Rate changes. Rate changes might be made for subscribers, based on the new route type and billing method. Billing change transactions are created for subscribers with billing method or rate changes.
Renewal notices and invoices for subscribers on the routes selected. Because of delivery method or credit status changes, you may want to reissue renewal notices or invoices to subscribers on the routes affected. A “rebill” transaction will be created for the subscriber. Renewal notices and invoices can then be generated for subscribers with rebill transactions.
Select Route Type Change from the Character Utilities | Setup menu.
Select Add and complete the following fields.
Select Continue to change the route type and create the associated transactions. You will be prompted to enter the file name for an export file. This export file, which is written to /dti/exchange/cm
, will contain details about subscriber information changed by the process (see Appendix B for the file format). As part of the process, the Route Type Change report will also appear, listing subscribers changed by the process and the information that was affected.
If rebill transactions were created, you can reprint invoices or renewal notices in Subscriber | Renewal Notices. The Print Rebills field must be set to “y” and the rebill reason must be the same as you entered here.
Trips are delivery sequences used by carriers who deliver multiple routes; addresses from all of the routes are arranged collectively in one trip sequence (see Trip in the Setup Manual for more information). Trip delivery sequences can be modified and viewed using this option. Note, however, that they cannot be added here—they must be imported using the next option, Trip Del Seq Import.
Select Trip Delivery Seq from the Setup menu to display the Trip Delivery Sequence Update screen.
Specify the trip to be modified. You must also indicate whether the delivery sequences should display in Trip Delivery Sequence or Street Address order. Then select Continue.
The addresses delivered by this trip will now display. To change the trip sequence order for an address, select Modify, highlight the address and press Enter. Select VIEW to scroll through the address list.
Newspapers may change their route IDs from time to time, to better reflect the distribution organization or for other reasons. The Route ID Change options makes route ID changes a snap. All applicable records will be changed to use the new route ID. A single route can be changed, or a group of routes can be renamed using an input file.
Note:
If you use Circulation InSight, you must do a full export to InSight after changing a route ID.
Do not use this utility when a publishing run is open, when processing a Targeted Marketing product, or using any other option that accesses route records.
Select Utilities | Setup | Route ID Change
to display the Route Change Utility screen.
Select Add and complete the following fields.
Select Continue to change the route ID. The Route Change Utility report will be displayed, listing the routes that were changed.
You can run the Truck Validation report for a particular truck sequence, product, departure sequence, and date, to ensure that:
All of your routes have been assigned a drop order with a truck.
There are no routes that have been assigned to more than one truck.
All route drops have been assigned a location (a Truck Drop Sequence record).
A route doesn’t have multiple drop orders on a truck.
A truck does not have multiple editions (if One Edition Per Truck is set to “y”).
All trucks are included in the departure sequence.
This report is useful after initial setup, and whenever you are doing significant modifications to your trucks or routes. Some problems this report might reveal are routes assigned to multiple trucks, routes that are not assigned to trucks, routes that do not appear because the drop record has an end date before this date, and routes on trucks multiple times.
Select Truck Validation from the Setup menu to display the Truck Sequence Validation Report screen.
Select Add and complete the following fields.
Select Continue to produce the report.
Before running the GMA/SAM Export, Circulation route types must be mapped to GMA “account types”; account types are exported as part of the route information.
Note: The GMA/SAM interface requires a separate license fee to use. Contact the Naviga Global Support Center for more information.
Select GMA/SAM Account Type from the Utilities | Setup
menu.
Select Add and pick a route type. Then enter the associated GMA account type (the account type is user-defined and may be up to 5 characters). More than one route type may be mapped to the same account type.
Select Accept to add the route type/account type mapping to the database.
In addition to account types, you may also specify a default circulation group to user in the export. This is done with a Business Rule— In the GMA/SAM Export, what is the default circ group? (Route Services section).
Use this option to save time when creating product records. This utility will copy the area, region, distribution zone, and district records from one publication to another. You will be prompted to enter the product to copy from (From Product) and the product to copy to (To Product), as well as start and end dates for the records that will be created.
Note:
If any of these records already exist for the To product, they will not be copied. For example, if product “DM” has Area records of “East” and “West”, and product “GZ” already has an Area record of “East”, copying product “DM” to “GZ” will result in only one Area record, “West”, being copied.
Select Copy Publ Info from the Utilities | Setup
menu to display the Copy Publication Information screen.
Select Copy and complete the following fields.
Select Accept to copy the publication information. When finished, a report will display any errors that occurred during processing.
Route delivery sequences define how a newspaper carrier should walk a route. Route lists and route labels may be printed in this order (Business Rules determine whether route labels print in truck-route-walk sequence order or truck-route-subscription ID order).
Select Route Delivery Sequence from the Setup menu to display the Route Delivery Sequence Update screen.
Select Add and complete the following fields.
Select Continue to begin the sequencing. All of the addresses on this route are displayed, along with their sequence number (which is initially zero).
Select Modify, scroll down to the first address in the sequence, and press Enter. You can then enter the sequence number for this address. We recommend that you sequence addresses by tens (10, 20, 30, etc.) so that addresses can be added into the sequence later.
Press Enter after specifying a sequence number, and select another address. When you have finished entering sequence numbers, press F4 and Exit (twice) to exit to the main menu.
This utility allows you to assign or change the walk sequence order for your mail addresses. The walk sequence indicates the order in which the postal carrier delivers addresses on a route. By placing mail in walk sequence order, you can receive certain mailing discounts.
Mail labels can be printed in walk sequence order within each PO route. Walk sequence order can also be automatically assigned.
One way to determine the walk sequence order is to print walk sequence cards (see ) and send them to the post office, where they will be put in walk sequence order and returned.
Select Postal Walk Sequence from the Setup menu to display the Postal Walk Sequence Update screen.
Specify the Zip code, postal carrier route, and sort order for which you are setting up the walk sequence.
Select Continue to begin the sequencing. Addresses with the Zip code, PO type and PO number you specified will be displayed, along with their sequence number (which is initially zero).
Select Modify, scroll down to the first address in the sequence, and press Enter. You can then enter the sequence number for this address. We recommend that you sequence addresses by tens (10, 20, 30, etc.) so that addresses can be added into the sequence later.
Press Enter after specifying a sequence number, and select another address. When you have finished entering walk sequence numbers, press F4 and select Exit (twice) to exit to the main menu.
Route Delivery Sequence Update allows you to export carrier walk sequences, modify them in an external program, and then import them back into the Circulation database. You can run this utility in “Edit” or “Commit” mode and export for a single route or all routes.
Select Utilities | Setup | Route Del Seq Update
.
Select Route Del Seq Update from the Setup menu to display the Route Delivery Sequence Import/Export screen.
Select Add and complete the following fields.
Select Continue to begin the import or export.
The One Day Rate Change utility allows sites to change an account rate for a single day; for example, to increase the carrier credit on a major holiday.
Select One Day Rate Change from the Utilities | Setup menu in Graphical Utilities.
In the top portion of the screen, highlight a rule rate link records whose rate you want to change. You can Ctrl-click to select individual rates, or Shift-click to select a range of records.
Click the Add button and complete the following fields.
Click OK. The one-day rate change will be saved but not committed, and display in the One Day Change Links area in the lower right of the screen.
Define rate codes for additional rule rate links and dates.
Click the Commit button to commit the one day changes. Changes do not take effect until they are committed. Be sure that each change is correct before performing this step. Individual changes can be modified or deleted by using the Modify and Delete buttons.
Click OK to complete the operation. After a change is committed:
The original rule rate link is end-dated to the day before the one-day rate change.
A copy of the original rule rate link is created with a start date of the day after the one-day rate change.
This tool is used to unlock or clear the lock records for various types of batches. A lock can occur when a user does not exit these programs normally.
Select Unlock/Clear Batches from the Utilities | Tools
menu.
Select the type of batch to unlock in Batch Type. Select one of the following:
Cash Batch
Clear Pmt Batch Stat (subscriber payment batch)
Draw Change Batch
Refund Batch
Returns/Adjust Batch
In batch id, enter the batch to unlock or “*” to multi-select batches.
Press F1.
Select Accept to unlock the batch(es).
Enter the security identification that indicates who will be allowed to run this batch (see in the Setup Manual for more information).
Select View/Print on the strip menu that appears when creating specific reports, and set view print settings in the View & Print Options window that appears. This method allows you to view, print, save, and archive reports, but offers fewer tools than Method #2. This method is discussed on .
Modify settings in the View & Print Options window. You might do this prior to viewing or running reports in the View/Print Utility, in order to establish default settings. The View & Print Options window also determines what other options are available. For example, if you have Print set to “n”, PRINT will not appear on the strip menu. See for more information about these fields.
Field settings for a group of reports or processes can be saved to an input file. The input files can then be added together in batches, allowing a number of options (for example, all of the churn reports) to be run with one command. See for more information about batches. This option allows you to view the field settings for input files. A multi-select window will open for you to select settings to view. Press the space bar to exit or move on to the next viewing.
Use this option to start a previously defined batch process. For example, you may want to run your publishing run as a single batch process so that it can be done overnight. Batches must be set up beforehand (See ). Select the batches to run from the multi-select window that appears. You will then be prompted if you want to continue with the processing. If the batch has prompts, they will also appear. You should be aware that some batches can take several hours to run, and stopping them may create errors in Circulation. Note that once the batch is processed, any reports saved will not immediately be added to the saved file list—you must select Scan to update the list.
Note: For information about customizing your personal view/print settings, see in the Setup Manual.
ROUTE
setup
Enter the route for which to set up or modify the walk sequence.
ALL ADDRESSES
yes/no
Enter “y” if you want to select all addresses assigned to a route.
ZIP CODE
setup
Enter the Zip code for which to modify or view the route delivery sequence. Only addresses on this route within this Zip code will be sequenced.
SORT ORDER
predefined
Indicate whether addresses should display in street address order or walk sequence order. This is for display purposes only; the actual order is always the walk sequence order.
ASSIGN
yes/no
Indicate if you want sequence numbers to be automatically assigned by 10s (e.g., 10, 20, 30, etc.).
ZIP CODE
setup
Enter the Zip code for which to set up postal walk sequences. Enter “*” to enter multiple Zip codes.
PO TYPE
predefined
Enter the PO route type. Enter an “*” to include all types or press F2 for a lookup of valid types.
PO NUMBER
open (3)
If you entered a PO route type in PO TYPE, enter the PO route number or enter “*” to include all routes.
SORT ORDER
predefined
Indicate whether addresses should be displayed on the screen in street address or walk sequence order.
ASSIGN
yes/no
Indicate if you want sequence numbers to be automatically assigned by 10s (e.g., 10, 20, 30, etc.).
OPTION
predefined
Select Export or Import.
READ OPTION
predefined
If you selected “Import” above, select Edit or Commit. “Edit” completes all of the checks and generates the same messages as “Commit”, but does not update the database.
ALL ROUTES
yes/no
If you selected “Export” above, indicate if you want to include all routes.
ROUTE
setup
If you are not including all routes, identify the single route that you want to export.
FILE NAME
open (30)
Enter the name of the file to export, or the name of the file you are importing. If you are importing, the file must exist in the default exchange directory.
DATE OF RATE CHG
date
Enter the date of the one-day rate change.
DRAW RATE CODE
setup
Select the rate code for the draw charge. This will determine the rate charged carriers who are rated by the selected rule rate link for the date above.
DRAW CHRG CODE
setup
Select the charge code corresponding to the draw rate code. This should be set up as a charge (not a credit).
CREDIT RATE CODE
setup
Select the rate code for the draw credit (if applicable). This will determine the rate credited to carriers who are rated by the selected rule rate link for the date above.
CREDIT CHRG CODE
setup
Select the charge code corresponding to the credit rate code. This should be set up as a credit.
RETURN RATE CODE
setup
Select the rate code that will apply to returns.
RETURN CHRG CODE
setup
Select the charge code corresponding to the return rate code. This should be defined as a charge (not a credit).
This section guides the user through the menu options that are available under the Export menu.
This section guides the user through the menu options that are available under the Import menu.
ZIP CODE
open (5)
If the router records being updated are based on the Zip code, enter the Zip code here. If the records are based on the city, leave this field blank.
ZIP EXTENSION
open (4)
This field pertains only to Canadian rural routes (middle digit of FSA is “0”). Enter the LDU for this rural route.
COUNTRY, STATE, COUNTY, CITY
setup setup open (25) open (28)
If the router records being updated are based on the city, enter the city (and the country, state and county where it is located) here.
STREET
open (28)
If a particular street is being updated, enter the street name here.
TOWN OF 25
setup
If you are changing the default Town of 25 for this area, enter the new Town of 25 here (otherwise leave blank).
PRODUCT, AAM ZONE, DELIVERY PLACEMENT
setup setup setup
If you are changing the default AAM zone or delivery placement for this area, enter the AAM zone or delivery placement and the product it belongs to here. Otherwise, leave these fields blank.
MAP, ROUTE, START DATE
setup setup date
If you are changing the default route for this area, enter the route and the delivery map it is associated with. Also, enter a start date for the route change to go into effect.
PRODUCT
setup
Enter the product for which routes will have route types changed.
EFFECTIVE DATE
date
Enter the date on which the changes created by this utility should be based (including changes to route setup, billing changes, and end grace changes).
DISTRICT
setup
Enter the district whose routes should have route type changes made, or enter “*” to multi-select districts. Leave this field blank if you want to select specific routes, rather than districts.
ROUTE
setup
If District is blank, indicate the routes for which route types should be changed (enter “*” to multi-select routes).
NEW ROUTE TYPE
setup
Enter the route type that should be assigned to these routes. The route type must be set up in advance.
ALLOW CARRIER COLLECT
yes/no
Indicate whether the routes selected should allow carrier collect subscribers.
ALLOW OFFICE PAY
yes/no
Indicate whether the routes selected should allow office pay subscribers.
SOURCE
setup
Enter the source code that should be used for any transactions created by this utility. For example, if you enter “routetyp” and a billing change transaction is created for a subscriber, the source code of the billing change transaction will be “routetyp”.
BILLING CHANGE REASON
setup
Enter the reason code for any billing change transactions created by the utility. For example, if a carrier collect subscriber is delivered by a route that is changed to office pay only, a billing change transaction will be created for the subscriber.
GRACE CHANGE REASON
setup
Enter the reason code for any grace change transactions created by the utility. For example, if a subscriber is in grace and her grace period changes due to a changed credit status, a grace change transaction will be created for that subscriber.
CHANGE CREDIT STATUS
yes/no
Indicate whether subscribers delivered by the routes selected should have their credit statuses changed by the utility.
CREDIT STATUS
setup
If you are changing credit statuses, enter the credit status here. All subscribers on the selected routes will now have this credit status.
CREATE REBILL TRAN
predefined
Indicate under what circumstances subscribers of the routes selected should have rebill transactions created. You can create rebill transactions for all subscribers (always), no subscribers (never), or only subscribers who have already received an invoice or renewal notice and thus need a reprint (if needed).
REBILL REASON
setup
Enter the reason code for any rebill transactions that are created.
GENERATE TASKS
yes/no
Set this field to “y” if you are changing credit statues and a task should be generated for each subscriber whose status was changed. The field will only open if at least one task is defined for the Route Type Change utility (Event field set to “Report Processing” and Report field set to “Route Type Change”).
SINGLE ROUTE
yes/no
Indicate whether you are changing the route ID for a single route. If you are changing IDs for a group of routes, set this field to “n” and enter the input file in Input File Name.
OLD ROUTE
setup (8)
If you are changing the route ID for a single route, enter the existing route ID here.
NEW ROUTE
open (8)
If you are changing the route ID for a single route, specify the new route ID here.
NAME/LOCATION
open (25)
The route name can be changed along with the ID. If you are changing the route ID for a single route, enter a name for the route (leave blank to keep the old route name).
INPUT FILE NAME
open (30)
If you are changing the route ID for a group of routes, you must create an ASCII file containing the old and new route IDs. Enter the name of the ASCII file here. The file must be in the /dti/exchange/cm
directory. See Appendix B for the file format.
PRODUCT
setup
Enter the product for which to produce the report. Only routes delivering this product will be considered.
DEPARTURE
setup
Enter the departure sequence for the report. Trucks that are in the truck sequence but not in this departure sequence will be listed.
TRUCK SEQUENCE
setup
Enter the truck sequence for which to produce the report. The drops information will be considered according to this sequence.
VALIDATION DATE
date
Enter the date on which to base the report. For example, if a drop record has an end date before this date, the drop will not show up on the report.
ONE EDITION PER TRUCK
yes/no
Indicate whether the truck sequence should be validated for edition—if so, a warning will be displayed if more than one edition of the newspaper is being dropped by a truck.
WEEKDAY
predefined
If you are validating for edition, indicate the day of week that should be validated, or enter “*” to multi-select days. Routes can have different editions on different days of the week; you may allow multiple editions on a truck on one day but not another day.
ALL TRUCKS
yes/no
If this field is set to “y”, errors for all trucks will be shown in the “Trucks Without A Truckdeparture Record” and “Duplicate TruckDropSequence Records” sections. If it is set to “n”, errors will be shown only for those trucks that have been set up in the selected truck sequence.
FROM PRODUCT
setup
Enter the product whose information you want to copy.
TO PRODUCT
setup
Enter the product to which you want to copy the information.
START DATE END DATE
date
Enter the start and end dates for the records that will be created.
The reports produced by Check Home Delivery and Check Single Copy identify missing information about home delivery and single copy routes, respectively:
No account assigned
No account assigned
No account information for account assigned
No account information for account assigned
No bill source for account
No bill source for account
No billing information for account
No billing information for account
No home delivery information
No single copy information
No publication information
No publication information
No delivery schedule assigned
No AAM percentages assigned
No delivery map assigned
No Zip code percentages assigned
No AAM percentages assigned
No drop sequence assigned
No Zip code percentages assigned
No drop instructions assigned
No drop sequence assigned
No drop location information
We recommend that these reports be run after initial route setup, and after any significant modifications to route information.
Select Check Home Delivery or Check Single Copy from the Tools menu.
Select Add and enter the product and route for which to create the report (enter “*” in Route to multi-select routes).
Select Continue to produce the report.
Use this option to rerate existing subscriptions due to a rate increase for selected rate codes. It will create a billing change transaction for all subscribers on a selected product, rate code, and delivery schedule. When the billing change is processed, the subscriber’s expire date will be adjusted back to reflect the rate increase.
Select Tools | Rerate Subscribers
to display the Rerate Subscribers window.
Click Add and complete the following fields.
PRODUCT
setup
Select the product ID.
SUBSCRIBER TYPE
predefined
Select the subscriber type: In Grace, Paid, or Both.
EFFECTIVE DATE
date
Enter the date on which the billing change transactions will be effective.
RATE CODE
setup
Select the rate code that has changed, or enter “*” to multi-select.
DELIVERY SCHEDULE
setup
Select the delivery schedule of the subscribers to be rerated, or enter “*” to multi-select.
SOURCE CODE
setup
Select the source code of the billing change transactions.
(REASON CODE) IN GRACE
setup
If the subscriber type is “In Grace” or “Both”, select the reason code to apply to the subscribers’ billing changes.
(REASON CODE) PAID
setup
If the subscriber type is “Paid” or “Both”, select the reason code to apply to the subscribers’ billing changes.
Click OK and then Continue to rerate the subscribers.
This tool re-exports a direct deposits batch.
Select Utilities | Tools | Re-Export Direct Dep
to display the Re-Export Account Direct Deposits screen.
Select Add.
Enter the company, bill source, bank, deposit date, and a description of the batch.
Press F1 and select Continue to re-export the batch.
This tool re-exports a subscriber payment batch.
Select Utilities | Tools | Re-Export SubPmt Bat
to display the Re-Export Subscriber Payment Batch screen.
Select Add.
In the Batch field, identify the subscriber payment batch to re-export.
Press F1 and select Continue to re-export the batch.
This option allows you to create a reversing batch of unbilled returns. The new batch will be created in a suspended mode.
Select Undo Draw Adj Batch from the Utilities | Tools
menu.
Select Add and complete the following fields.
BATCH
open
Select the batch for which you want to create reversing entries.
REVERSE BATCH
open
Enter a name for the new batch of reversing entries.
DRAW ADJUST
setup
Enter the draw adjust code to use for these entries.
Select Continue to create the batch.
Newspaper distribution patterns will change over time; for example, routes are often shifted to different trucks, and trucks themselves are split, combined or renamed. The Move Truck Drop utility can be useful when making distribution changes; the utility moves all of the drops of one truck to a different truck. For example, say two trucks, 22a and 22d, dropped the following routes:
Now let’s say the trucks need to be combined. All of truck 22a’s routes are moved to truck 22d using Move Truck Drop, which will result in one truck:
Select Utilities | Tools | Move Truck Drop
to display the Move Truck Drop screen.
Select Add and complete the following fields.
TRUCK SEQUENCE
setup
Enter the truck sequence within which you are moving drops.
OLD TRUCK
setup
Enter the ID of the truck that you are moving drops from.
NEW TRUCK
setup
Enter the ID of the truck that you are moving drops to.
EFFECTIVE DATE
date
Enter the date on which the drops should effectively move from the old to the new truck. This will be the end date of the drops on the old truck and the start date of the drops on the new truck.
Select Continue to move the drops. Note that all drops, including routes, relay trucks, and throwoffs will be moved. The drops will have the same drop order on the new truck as they did on the old truck. When complete, a processing report will appear, listing the number of drops that were moved.
The Change Area Code tool is useful when area codes are changed in one of your primary market areas; it allows you to quickly change all customers affected to their new area code. In order to run this tool, you must create a text file that lists the old area code, the phone extension (first three digits of the phone number), and the new area code for that extension. The fields must be comma-separated. For example, if area code 612 was changing to 651 for all phone numbers starting with “222”, “211” and “639”, you would have the following lines in your file:
612,222,651
612,211,651
612,639,651
Select Change Area Codes from the Utilities | Tools menu.
Select Add and enter the path and file name of the text file you created.
Select Continue to change the area codes. A processing report will display the number of records changed.
This menu option helps the client to to re-run direct debit files. The user need to provide the batch id to generate the files.
Select Utilities | Tools | Re-Export Direct Deb
to display the Re-Export Direct Debit screen.
Select Add.
In the BatchID field, enter the direct debit batch to re-export and press F1.
Select Continue to re-export the batch.
This tool re-exports an Interface to AP file.
Select Utilities | Tools | Re-Export AP Interfc
to display the Re-Export Interface to AP screen.
Select Add.
Enter the company, bill source, invoice date, and AP clearing account.
Enter the remaining information as needed, depending on the interface to AP being used.
Press F1 and select Continue to re-export the file.
The Subscriber Balances Export is used to export current subscription balances and other information for all subscribers except permanently stopped subscribers with a zero balance. The balance calculation used by this export is the same calculation used in the Show | Balance option in Customer Service. See Appendix B for the file format.
Select Subscriber Balances from the Export menu to display the Subscriber Balance Export screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the publication for which subscriber balances should be exported, or enter “*” to multi-select publications.
EXPORT OPTION
predefined
Select either summary or detail.
FILE NAME
open (30)
Enter a file name for the export. Subscriber balances will be exported to this file in the /dti/exchange/cm directory.
Select Continue to export subscriber balances. When the export is complete, a processing report will display, listing how many records were exported. The standard view/print options will be available.
mass2one™ Email Campaign Manager® is a popular marketing software application that offers e-mail campaign features. Circulation can export occupant information, including e-mails, to mass2one. Occupants with certain subscriber status(es) for a product you specify will be exported. Solicitation codes can be used to flag subscribers who should not be e-mailed.
Select Mass2one from the Utilities | Export
menu to display the mass2one Export screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the publication that should be exported, or enter “*” to multi-select publications. All subscriptions to the products selected will be exported. So, for example, if two products are selected and an occupant has a subscription to both, the occupant will be exported twice. Occupants with no subscriptions to the selected products will be exported with a status of “non-subscriber”.
SUBSCRIBER STATUS
predefined
Select the type of subscriber whose occupant information should be exported: Active, Temp Stopped, Former or Never. Enter “*” to multi-select.
SOLICITATION CODE
setup
Select the solicitation code that should be used to denote occupants that should not be e-mailed (for example a “NoEmail” solicitation code). Enter “*” to multi-select codes. Occupants who are assigned to one of these solicitation codes will be exported with the “Do not Email” indicator set to “yes”.
EMAIL OPTION
predefined
Indicate whether only occupants who have an e-mail address should be exported (require), only occupants who do not have an e-mail address should be exported (exclude), or all occupants should be exported regardless of e-mail address (either).
FILE NAME
open (25)
Enter the name for the export file. Occupant information will be exported to this file in the /dti/exchange/cm directory.
Select Continue to run the export. Occupant information will be exported to the /dti/exchange/cm
directory, using the file name entered by the user. See Appendix B for the file format. After the export has completed, a report will display information on the process, including the number of records exported.
Most newspapers will continue to deliver papers for a certain grace period after a subscription expires, in the hopes that a payment is forthcoming. If a payment does not arrive, the subscription will eventually be stopped and the subscriber will owe for the grace. Because the subscriber did not specifically agree to receive the grace papers, he or she is not legally bound to pay the grace, and it is typically written off by the newspaper. However, by stating up front that delivery will continue past expiration date, a newspaper can, in some states, legally require the grace amount to be paid, and so refer customers owing grace to everyone’s friend, the bill collector.
The Collectech option exports information about subscribers who owe grace to Collectech, a software system used for bill collection. As part of the export a CollectXprt transaction will be created for the subscribers, to prevent them from being exported again and to establish an export history. The export can include subscribers who:
Are active with an expired subscription, if the subscriber received grace papers but has not yet made a payment.
Are perm stopped and owe grace.
Were previously exported and have since paid.
Active, perm stopped and paid subscribers will be exported to separate Collectech files—see Appendix B for the file formats.
Select Collectech from the Export menu to display the Collectech Export screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the publication whose subscribers should be exported to Collectech, or enter “*” to multi-select publications.
EXPORT ACTIVE
yes/no
Indicate whether active subscribers (i.e., subscribers who have expired and are either in their grace period or have been turned over to carrier collect) should be exported.
PAYMENT LENGTH, PAYMENT TERM
integer (4), predefined
If active subscribers are being exported, enter the payment length and term to use. The value of the length and terms will be found, using the subscriber’s rate code, and exported. If a matching length and term has not been defined, the highest term for the subscriber’s rate code will be used. For example, if “13 week” is entered here and the value of the 13 week term is 25.00 for rate code “regular”, a subscriber with this rate code will have 25.00 exported as the collection amount, even if the subscriber has only spent a few days in grace.
START DATE, END DATE
date
Enter the date range to use in selecting active subscribers. Only subscriptions that expired within this date range will be included.
EXPIRE STOPPED
yes/no
Indicate whether perm stopped subscribers who owe grace should be exported.
REASON CODE
setup
Enter the stop reason code to use in selecting stopped subscribers, or enter “*” to multi-select reason codes. Only subscribers who perm stopped using the reason codes entered here will be included.
START DATE, END DATE
date
Enter the date range to use in selecting perm stopped subscribers. Only subscriptions that perm stopped within this date range will be included.
EXPORT PAID
yes/no
Indicate whether subscribers who were previously exported to Collectech (as active or stopped) and have since made a payment should be exported. This allows the Collectech to consider the bill as paid.
FILE NAME
open (10)
Enter the file name for the Collectech export. The Collectech files will be written to /dti/exchange/cm using this file name, plus the extensions of “active”, “stop” or “paid”, depending on which subscribers are being exported. For example, if the file name is “collect”, the files exported will be “collect.active”, “collect.stop” and/or “collect.paid”.
Select Continue to export information about active, stopped and paid subscribers to Collectech. When the export is complete, a processing report will display the number of records that were exported to each file.
This option allows you to locate subscriber and account payments and refunds using the credit card number. For example, if a non-subscriber finds a charge on his credit card statement and wants to know what the charge was for, you can use the credit card number to locate the payment since no subscription ID is available.
Select Tools | Find CC Transactions to display the Find Credit Card Transactions window.
Click Add and complete the following fields.
START DATE END DATE
date
Enter the date range to cover.
CARD NUMBER
open
Enter the credit card number to search.
PAYMENTS REFUNDS
yes/no
You can search for payments, refunds, or both.
TYPE
setup
Indicate they type of transactions you want to search: subscriber, account, or both.
AMOUNT
decimal
Enter the amount of the transaction, if known.
INCLUDE TIP
yes/no
Select this checkbox if the entered amount includes a tip.
Click OK and then Continue to locate the credit card transactions. There is no printed report.
The Subscriber Activity Export will find all subscribers with a certain type of transaction (start, billing change, stop, etc.) within a given date range and export occupant, address and subscription information to an ASCII file. The export format is user-defined, and must be set up in advance in File Map.
For example, all billing changes for the current month could be exported, including the subscriber’s current billing method and renewal delivery method, and then imported into a subscriber billing software program. The billing software could use this information to turn on or off renewal notice distribution, or switch from carrier delivery to e-bill.
Select Subscriber Activity from the Export menu to display the Subscriber Activity Export screen.
Select Add and complete the following fields.
PRODUCT
setup
Enter the publication for which subscriber activity should be exported, or enter “*” to multi-select publications.
TRAN TYPE
predefined
Select the transaction type to be exported (press F2 for a listing of transaction types).
SOURCE, REASON
setup
Transactions can be selected based on the source and reason codes entered. Enter the source and reason codes to use, or enter “*” to multi-select codes.
START DATE END DATE
date
Enter the date range to use in selecting transactions.
DATE TYPE
predefined
Indicate how transactions should be selected for the date range above: based on the create, process, publish or transaction date. The create date is the date the transaction is created on; the process date is the date it is processed by Transaction Processing; the publish date is the publishing date on which the transaction goes into effect; and the transaction date is the actual date entered with the transaction.
PROCESS OPTION
predefined
Indicate if you want processed transactions, unprocessed transactions, or both kinds of transactions to be included in the report.
FILE FORMAT
setup
Enter the ID of the subscriber activity export format that should be used. This must be defined in advance in File Map.
FILE NAME
open (30)
Enter the file name for the export. Subscriber activity will be exported to this file in the /dti/exchange/cm directory. The file name may default from the file format.
FILE OPTION
predefined
Indicate whether to replace the file above, if it exists, or append it. If set to “append”, the export will append the new activity to the existing file. This could allow, for example, multiple transaction types to be exported to the same file.
GENERATE TASKS
yes/no
TASK
setup
Select the task that should be generated.
CREATE CONTACTS
yes/no
Indicate whether contacts should be created.
CONTACT DATE
date
Enter the date of the contact.
CONTACT TYPE
setup
Enter the type of contact to be created (e.g., email, letter, phone call).
SOURCE
setup
Identify the source of the contact.
REASON
setup
Identify the reason for the contact.
Select Continue to export subscriber activity. When the export is complete, a processing report will display the number of records that were exported.
The Draw Impact Export is used to export information about transactions that affect draw (such as starts, stops, restarts, move-outs, move-ins, and delivery schedule changes). For each transaction listed, the export will include the draw impact to Daily Online, Daily Print, Sunday Online, and Sunday Print counts.
Select Utilities | Export | Draw Impact
to display the Draw Impact Export screen.
Select Add and complete the following fields.
Select Continue to export the information. See Appendix B for the export format.
This option is used to extract addresses for which the Cleanse Address? flag is set to “n”. The file map used for this export (“CleanseFlagExp” usage) may contain any other address elements to help the user determine whether individual addresses should or should not be cleansed.
The exported file must be updated outside of Circulation. Afterward, use import option () to import the updated addresses back into Circulation.
Select Update Cleanse Flag from the Utilities | Export menu to display the Update Cleanse Flag Exp screen.
Select Add and complete the following fields.
Select Continue to export the addresses.
Subscribe Extract Export is used to integrate the Subscribe and Circulation applications. The Subscribe application uses the Circulation APIs to create transactions like new subscriptions, payments, or billing changes. The data from these transactions is stored in the Circulation databases. The Subscribe Extracts are used to import this data into the Subscribe databases.
The files associated with Subscribe Extract Export are mentioned below.
Select Utilities | Export | Subscribe Extract
to display the Subscribe Extract Export screen.
Select Add and complete the following fields.
Select Continue to export the information.
Use this option to export addresses that require mass cleansing. Before you use this option, you must define a file map with the “AddressExport” file map usage (see Appendix B).
Select Export | Addresses
to display the QAS Address Export window.
Click Add and complete the fields in the table below.
Click OK and then Continue to export the addresses.
This option allows billing changes to be imported in order to update a subscriber’s renewal delivery method, rate code, auto renew credit card, or auto renew bank draft information. For example, this tool can be useful in cases where a renewal delivery method (such as eBill) is tracked by another system. The import format is user-defined, and must be set up in advance using File Map (“SubTranImprt” usage). See Appendix B for a list of data elements that can be included.
Select Billing Change from the Import menu to display the Billing Change Import screen.
Select Add and complete the following fields.
Select Continue to do the import. This will create unprocessed billing change transactions for the subscribers in the file. When the import is complete a processing report will be displayed, listing how many records were exported and any errors that occurred.
This option allows you to export subscription information to an external file. The export format is user-defined, and must be set up in advance in File Map using the “SubscrExprt” file mapping usage.
Select Subscriber Info from the Export menu to display the Subscriber Export screen.
Select Add and complete the following fields.
Select Continue to export the data.
Rewards programs are promotional offers, such as Air Miles, that give consumers credits for purchasing a product (see Reward Program in the Setup Manual). Circulation can give customers rewards based on subscription purchases, but because rewards programs are managed in a different application, it is necessary to export rewards information periodically.
Select Rewards from the Utilities | Export
menu to display the Reward Transaction Export screen.
Select Add and complete the following fields.
Select Accept to export rewards information. See Appenndix B for the file format. A processing report will list details about the export and any errors that occurred.
The Comboizer tool can assist you in implementing and managing combo subscriptions. The Comboizer can be used to convert a subscriber’s existing individual subscriptions to a combo subscription. Two different methods can be used to convert subscriptions:
Single subscription method. If the subscriber has a single subscription (for example, a hybrid subscription that is online during the week and route-delivered Saturday and Sunday), separate subscriptions are created under one combo. With this method, a publication and delivery schedule are specified.
Only subscriptions with that product and delivery schedule that match the primary subscription of the combo are selected—these are changed to combo subscriptions via a combo change transaction. New subscriptions are created for the other components of the combo.
Multiple subscription method. If the subscriber has multiple subscriptions that meet the criteria for a combo, they are married together into a combo subscription via combo change transactions.
The subscriber must have active subscriptions for all components of the combo in order to qualify for this method. Currently, running the Comboizer is the only way to combine existing subscriptions into a combo (this cannot be done in Customer Service).
Note:
At Cloud sites, the Comboizer must be run by Newscycle Support. At on premise sites, security access must be granted by Newscycle in order to use the tool. Please contact the Naviga Global Support Center to activate this feature.
The Comboizer is run for a specific combo and (for single subscriptions) a product and delivery schedule. Optionally, you can use an import file containing subscriber rate codes, and only subscriptions with those rate codes will be considered.
The tool can be run in update or non-update mode. If run in update mode, combo transactions (combo change and combo start) are created, and the subscription is rerated. Transfer out and transfer in transactions are also created to transfer the subscriber’s balance to the combo subscription. The rate code to assign to the combo subscription can also be specified in the import file, or you can have Circulation rating determine the rate.
Note:
You may need to set up new Rule Rate Links to link the appropriate rate codes to subscription rules for the reason and source codes used by the Comboizer. If specifying rates in the import file, be sure those rate codes are linked to a subscription rule that is valid for the reason code and source codes used.
Follow the procedure below to run the Comboizer tool, once you have security access.
Select Comboizer from the Tools menu in the Graphical Utilities module. The Comboizer Tool screen displays.
Click Add and enter the criteria for running the tool. The fields are described in the table below.
Click OK and then Continue to run the Comboizer.
If run in update mode, combo change and combo start transactions are created using the Effective Date entered as the transaction date. These transactions will be processed when Transaction Processing is run for the transaction date.
The Comboizer Tool report displays, listing the number of subscriptions selected and other details from the process.
Please note the following when running the Comboizer tool:
Transactions created by the Comboizer tool include: combo change (to change a non-combo subscription to a combo), and combo start and expire (for new combo subscriptions created when running in “single subscription” mode). If there is a balance on the subscription, the combo change transaction creates transfer out and transfer in transactions when it is processed.
When the subscription has a balance, the transfer out transactions will split the balance to keep all of the combo subscriptions with the same expire date, as with a regular combo change transaction. If using the “multiple subscriptions” method, each active subscription balance is split into the combo subscriptions. This results in two transfer out transactions but four transfer in transactions. In this scenario, Transaction Processing must be run twice: once to process the combo change, and once to process the remaining transfer transactions.
Subscribers with the following pending transactions will not be selected (they will, however, be listed on the Comboizer Tool report): stop, payment, delivery schedule change, billing change, move in, move out, temporary address, transfer, reroute or delivery reassignment, grace writeoff, placement, combo change.
You should not run Transaction Processing while the Comboizer is running in update mode.
When run with the “single subscription” method, if the delivery schedule that is being split is a hybrid delivery schedule, the Comboizer should be run before final Transaction Processing or after End Publishing Run, not during or between the two.
When run with the “single subscription” method, if a subscriber already has a second subscription that matches a subscription that would be created by the Comboizer, the Comboizer will still create a new subscription. For example, when running for a combo that is route-delivered and online, if the route-delivered subscription is primary and a subscriber already has both a route-delivered subscription and an online subscription, a second online subscription will be generated as part of the combo.
When changing an existing subscription to a combo subscription, auto renew information, delivery information, grace days, balances, and other subscription information is retained. However, the subscription is rerated.
Marketing terms and balance forward billing are not currently supported with combos.
Subscribers with multiple copies are skipped by the Comboizer.
Below are examples of how the Comboizer would process different types of subscriptions. In the first two examples, assume the combo “TribC” is used, which has a primary product mix of product Trib, delivery schedule DS, and delivery method “Route”. “TribC” also contains a product mix with product Trib, delivery schedule DS, and delivery method “Online.”
Trib subscribers who are route-delivered with a delivery schedule of “DS” are given access to the online version of the Trib. To create combo subscriptions reflecting this, the Comboizer is run with the following parameters:
Existing Combo Type = “Single Subscription”
Product = “Trib”
Delivery Schedule = “DS”
Combo = “TribC”
Use Rate Input File is unchecked
All route-delivered subscriptions for product Trib, delivery schedule “DS” are considered. If a subscription qualifies (e.g. it has no pending stops, payments etc.) the following transactions are created:
Combo change for the current route-delivered subscription, changing it to a combo.
Combo start to start a new online subscription, with an associated expire change.
For subscriptions with a balance, transfer out/in transactions are created to transfer the balance to the combo subscriptions.
Circulation rating is used to determine the rate of the new combo subscriptions.
Trib subscribers who are route-delivered but also have online access have two independent subscriptions to the Trib, one with a delivery method of “Route” and the other “Online”. These subscriptions are married together under combo “TribC” by running the Comboizer with the following parameters:
Existing Combo Type = “Multiple Subscriptions”
Product = “Trib”
Delivery Schedule = “DS”. Only “DS” subscribers are picked up. If other delivery schedules also have multiple subscriptions, combos should be set up for them, and the Comboizer run for each different combo.
Combo = “TribC”
Use Rate Input File is unchecked
Subscribers who have both a route-delivered and online subscription to the Trib with the delivery schedule “DS” are considered. If a subscription qualifies, the following transactions are created:
Combo change for both current subscriptions, changing them to combo subscriptions.
For subscriptions with a balance, transfer out/in transactions are created to transfer the balance to the combo subscriptions.
Circulation rating is used to determine the rate of the new combo subscriptions.
Subscribers who receive a route-delivered paper on Sunday and have access to the online version on other days of the week have a single hybrid subscription to the Trib with delivery schedule “Hybrid” and the rate code “DSHybrid”. To create combo subscriptions for these subscribers with the same rate, the Comboizer is run with the following parameters:
Existing Combo Type = “Single Subscription”
Product = “Trib”
Delivery Schedule = “Hybrid”
Combo = “TribH” (like “TribC” but primary product mix is for delivery schedule “Hybrid”)
Use Rate Input File is checked, and a file name is specified. The file contains the line: DSHybrid,DSHybrid
Subscribers who have a Trib subscription with delivery schedule “Hybrid” and the rate “DSHybrid” are considered. If a subscription qualifies the following transactions are created:
Combo change for the current subscription, changing it to a combo subscription with a delivery method of “Route.”
Combo start to start a new online subscription, with an associated expire change.
For subscriptions with a balance, transfer out/in transactions are created to transfer the balance to the combo subscriptions.
The combo subscriptions retain the “DSHybrid” rate.
After addresses have been exported using the and updated outside of Circulation, use this option to import them back into Circulation. A file map for this import (“CleanseFlagImp” usage) must be set up in advance.
Select Update Cleanse Flag from the Utilities | Import
menu to display the Update Cleanse Flag Import screen.
Select ADD and complete the following fields.
Select Continue to import the addresses.
Indicate whether tasks should be created. In order to create tasks, a task type and event must be defined for the report in .
ALL ZIPS?
yes/no
Indicate if all Zip codes should be included in the export.
ZIP CODE
open
Enter the Zip code to include or “*” to multi-select Zip codes. This field is active only if ALL ZIPS? is set to “n”.
FILE FORMAT
setup
Enter the ID of the update cleanse export format that should be used. This must be defined in advance in FILE MAP with a usage of “CleanseFlagExp”.
FILE NAME
open (30)
Enter the file name for the export. The addresses will be exported to this file in the /dti/exchange/cm directory. The file name may default from the file format.
FILE OPTION
predefined
Indicate whether to replace the file above, if it exists, or append it. If set to “append”, the export will append the new activity to the existing file.
address_demo.txt
This file displays all demographics with the DemographicType "Address."
address_master.txt
This file exports all of the address IDs available in the Circulation database.
auto_renew.txt
This file displays details of all the active auto-renewal subscriptions.
autorenew_ccexpire.txt
This file provides information on AutoRenew Subscriptions that started with a Promo Rate Code and will expire in the next 14 days, after which the rate will be increased.
autorenew_ccstart.txt
This file contains information on the AutoRenew Subscriptions that started today on AutoPay Type "Credit Card" and on Promo RateCode.
bill_change.txt
This file contains information on all "BillingChg" Transactions. BillingChange includes changes to billing method and address, switching from autopay to non-autopay and vice versa, rate changes, and so on.
campaign_extractMG2.txt
This file sends information on the campaigns and offers available in the NCS Circ, such as the Campaign ID, start and end dates, and other details.
campaign_PropertiesExtractsMG2.txt
This file displays Campaign properties like CampaignPropertyID and CampaignPropertyValue.
campaign_ZipExtractsMG2.txt
This file includes information on which Campaign IDs apply to particular Zip Codes.
carrier.txt
This file contains information on the carriers that were modified or created after the export start date.
carrier_distribpoint.txt
This file displays the details of Routes/DistribPoints of all the carriers
complaints.txt
This file contains information on the complaints.
deadlines.txt
This file exports information on paper delivery deadlines and redelivery cutoff times for products on the associated routes.
delsched.txt
This file contains all the Delivery Schedule (DelivSched) Transactions.
demographics_subscribe.txt
This file contains all of the Subscription demographics intended for Subscribe (DemoGraphic.AudienceCategory - "Subscribe").
endgrace_date.txt
This file displays information about subscriptions that are in the grace period.
expire_date.txt
This file contains information about subscriptions that are due to expire within the export date range.
future_trans.txt
This file extracts vacation details for all future vacations (Temp Stops) and vacations that have already started (the vacation's end date has not yet been reached).
future_trans_full.txt
This file contains the Transactions that will become effective in the future. Transactions included are: 1stInvoice, 1stRenewal, 2ndInvoice, 2ndRenewal, 3rdInvoice, 3rdRenewal, 4thRenewal, AutoRenew, BillingChg, DelivSched, EndGrace, EndGraceChg, Expire, ExpireChnge, GraceAccrual, GraceEnd, GraceExport, GraceOwed, GracePaid, GraceWOff, MoveIn, MoveOut, Note, ReBill, Refund, RefundXfr, Renewal, Reroute, Restart, Start, Stop, TempAddrEnd, TempAddress, TransferIn, TransferOut
mailsubscription.txt
This file displays all the subscriptions that are mail-delivered.
merchandise.txt
This file extracts information on merchandise (items such as books and mugs) associated with three transaction types: DelivSched, BillingChg, and Start.
non_subs.txt
This file sends information on occupants who are present in the system but have not subscribed or whose subscriptions are no longer active.
notes.txt
This file contains all the Note Transactions.
occupant_demo.txt
This file displays all demographics with the DemographicType "Occupant."
occupant_email.txt
This file exports the email addresses of all the occupants. It displays data such as OccupantID, Email Address, Start Date, End Date, Primary (Yes/No), etc.
occupant_name.txt
This file exports the Occupant Names such as First Name, Last Name, Middle Names of the occupants.
occupant_phone.txt
This file exports the Phone Numbers of all the occupants. It displays data such as OccupantID, Phone Numbers, Phone Type, Create Date, Create Time, Primary (Yes/No), etc.
occupantsolicitation.txt
This file contains all of the Occupant Solicitations. Occupants may request not to be solicited by phone, mail, or other methods.
payments.txt
This file extracts information for transactions with a transaction type of "Payment" or "AutoRenew."
pymtdecline.txt
This file contains information on payments that have been declined or failed.
rate_codes.txt
This file gives the details of all active rate codes, their rate terms and lengths, start and end dates, etc.
renewals.txt
This file displays the subscriptions that are due for renewal.
restarts.txt
This file sends information about subscriptions that have been restarted after a temporary stop or vacation.
route_draw.txt
This file contains the number of copies/draws delivered on a certain route.
route_subscription.txt
This file contains Route and Distribution Point information for all carriers.
router.txt
This file contains information on all Routes and their related RouteIDs. In NCS, a Route is a collection of address ranges. A default route exists for each address range.
starts.txt
This file contains information about newly started subscriptions.
stops.txt
This file contains information on subscriptions that have been stopped (either temporarily or permanently).
submaster.txt
This file displays the details of all the subscriptions. Note: Trial details of a subscription (Trial_Term, Trial_Length, Trial_StartDate, and Trial_EndDate) are included in the Sub_master.txt file.
subscription_demo.txt
This file displays all demographics with the DemographicType "Subscription."
version.txt
This file contains meta data about the Extract run, such as the database name, export version, release version, number of export files created, etc.
EXPORT PATH
predefined
Enter the full path for the file to be exported.
EXPORT START DATE
date
Enter the start date for which you want to export information.
EXPORT VERSION
predefined
Enter the export version, e.g., 01, 02, etc.
RUN SUBCON FILES
yes/no
Enter "Yes" to export the SubCon extracts or "No" to exclude the SubCon extracts.
RUN DISCOVERY FILES
yes/no
Enter "Yes" to export the Discovery extracts or "No" to exclude the Discovery extracts.
PUBLICATION
setup
Enter the publication or publications for which the subscribe extract is to be exported.
DATABASE NAME
setup
Enter the circulation database from which the subscribe extract is to be exported.
FILE MAP
setup
Select the Address Export file map you want to use for the export. This must be defined in advance in File Map setup.
FILE NAME
open (30)
The default file name defined in File Map setup will appear, but can be changed. You can also select from a list of file name tokens (shown below) by clicking the lookup icon.
ALL ADDRESSES
yes/no
Leave this field checked to export all the addresses in the database.
USE QAS SELECTION
yes/no
If you do not select All Addresses, this field opens. It pertains only if you use QAS for address cleansing. Check Use QAS Selection to export addresses based on the QAS status: • Forced addresses—Addresses that have a delivery point ID (DPID) of 0 and a cleanse score that is not blank. • Uncleansed addresses—Addresses that have a delivery point ID (DPID) of 0 and cleanse score that is blank. • Both.
ALL COUNTRIES, COUNTRY
yes/no setup
Leave All Countries checked to export addresses for all countries. To export addresses for a specific country, uncheck All Countries and select the country in the Country field.
PRODUCT
setup
Enter the product ID.
FILE FORMAT
setup
Enter the ID of the subscriber export format that should be used. This must be defined in advance in File Map.
FILE NAME
open (30)
Enter the export file name. This file must be in the /dti/exchange/cm directory. The file name may default from the file format.
Field
Type
What to enter
PRODUCT
setup
Enter the publication for which rewards should be exported, or enter “*” to multi-select publications.
START DATE, END DATE
date
Enter the date range for which to export rewards information. Only rewards with a processing date within this date range will be exported.
REWARD PROGRAM
setup
Select the rewards program that you are interfacing.
PROVIDER CODE, SPONSER CODE, LOCATION CODE
open (4)
Enter the provider code, sponsor code, and location code for the rewards being interfaced, if applicable. These values will default from Business Rules.
EXISTING COMBO TYPE
predefined
Indicate whether the Comboizer should create combo subscriptions from a single subscription or combine multiple subscriptions.
PRODUCT DELIVERY SCHEDULE
setup
If you are using the “single subscription” method (as specified in Existing Combo Type), select the publication and delivery schedule that combo subscriptions should be created for. Only subscriptions to this publication/delivery schedule combination will be considered.
COMBO
setup
Select the combo that subscriptions should be created for. In order to qualify for the combo, the subscriber must have a subscription to the combo’s primary product mix (product, delivery method, and delivery schedule). If using the “single subscription” method, only combos that include the specified publication can be selected.
EFFECTIVE DATE
date
Enter the date on which the combo subscriptions should be created. This will be the transaction date of the combo change and combo start transactions. The current publishing date defaults.
SOURCE REASON
setup
Select the source and reason code that should be used for the combo change transactions. Only valid combo change reason codes can be selected. The source and reason code will also be used to determine the rate for the combo subscription. Note that the expire date for the primary publication will be retained, if the reason code has Update Expire set to “n” in setup. There will be either a positive or negative discount created, depending on whether the combo rate is more expensive or less expensive than the original non-combo rate.
USE INPUT RATE FILE FILE NAME
yes/no open (30)
If only subscriptions with certain rate codes should be processed by the Comboizer, check User Input Rate File and enter the file name in the File Name field. If Use Input Rate File is unchecked, the Comboizer will select all matching subscriptions.
The file must be placed in the /pbs/exchange/[defaultdir]
directory. The format contains two fields in quotes separated by a comma: the old rate code and the new rate code. If Circulation rating should determine the new rate, set the new rate code field to “*”.
An example of the file contents might be:
dmDOMOTOR,DM+GZdig-NORMAL
DMDSMOTOR,*
DMDSHD,DMGZRte
UPDATE
yes/no
Indicate whether combo subscriptions should be created by the tool. If this field is not checked, only a report will display. Newscycle recommends running the Comboizer first with Update unchecked and reviewing the Comboizer Tool report before running in update mode.
READ OPTION
predefined
Indicate whether the import should be run in commit mode (addresses imported into Circulation) or edit mode (no addresses imported—the file is simply read and any errors displayed). We recommend running this option in edit mode first to confirm that there will be no errors during the import.
FILE FORMAT
setup
Enter the ID of the update cleanse import format that should be used. This must be defined in advance in File Map with a usage of “CleanseFlagImp”.
FILE NAME
open (30)
Enter the file name for the import. The addresses will be imported from this file in the /dti/exchange/cm
directory. The file name may default from the file format.
Use this utility to import address additions, changes, and deletions. All of the imported data will be validated just as if the addresses were being added or modified manually. If Business Rules are set not to parse addresses, detailed information such as house number, street name, predirectional, street type, etc., will not be validated.
After importing the address data, an audit report will be created that displays the number of records added, changed and deleted along with any errors encountered. Error messages are written to the log.
File mapping is used to define the format of the import file (see Appendix B).
Note: If you cleanse addresses, run Batch Address Hygiene after importing addresses to cleanse them. The Address Information import only validates address elements, such as street type.
Select Import | Address Information
to display the Address Import window.
Click Add and complete the following fields.
READ OPTION
predefined
Indicate whether the import should be run in commit mode (transactions imported into Circulation) or edit mode (no transactions imported—the file is simply read and any errors displayed).
TOWN OF 25
setup
If you selected commit above, select the town of 25 to which these addresses belong.
FILE FORMAT
setup
Select a File Map format to use for this address import.
FILE NAME
open (30)
Enter the name of the address file being imported. The file must be in the /dti/exchange/cm
directory.
Click OK and then Continue to import address information.
PRODUCT
setup
Enter the product or products for which to view draw impact.
START DATE, END DATE
dates
Enter the date range for which you want to export information.
EXCLUDE DELIVERY SCHEDULE
yes/no
If applicable, specify which delivery schedule(s) you want to exclude from the export.
INCLUDE LAST YEAR
yes/no
If you select “y” in this field, the export will be run a second time for the same date range of the previous year.
EXPORT FILE NAME
predefined
Enter the full path and file name of the file to be exported.
READ OPTION
predefined
Indicate whether the import should be run in commit mode (transactions imported into Circulation) or edit mode (no transactions imported—the file is simply read and any errors displayed). We recommend running this option in edit mode first to confirm that there will be no errors during the import.
TRAN TYPE
predefined
Enter the transaction type to be exported. Currently, “Billing Change” is the only choice.
SOURCE, SUBSOURCE REASON
setup
If the import is being run in commit mode, enter the source, subsource (if applicable) and reason code for the billing change transaction.
TRAN DATE
date
If the import is being run in commit mode, enter the transaction date for the billing changes. If a transaction date is contained in the file, the file’s transaction date will override this date.
FILE FORMAT
setup
Enter the ID of the subscriber transaction import format that should be used. This must be defined in advance in File Map.
FILE NAME
open (30)
Enter the import file name. This file must be in the /dti/exchange/cm
directory. The file name may default from the file format.
Communication history is a record of the newsletters, alerts, and other communications sent to an occupant. Communication history can be generated by Targeted Marketing when selecting customers opting into a communication (see Processing), or imported into Circulation from an outside source using this option. For example, if you currently manage a newsletter e-mail list in another application but want the ability to view which newsletters and alerts were sent to an occupant in Customer Service, you can import that history into Circulation.
Note:
In order to import communication history for a customer, the customer must have opted in to the communication item using the communication method and detail (e-mail, phone or address) contained in the import file. Also, the customer’s occupant ID must be contained in the import file.
The import format is defined by file mapping. You must define a file map with a usage of “CommHistImport” (see Appendix B for a list of elements).
In Graphical Utilities, select Communication Hist from the Import menu. The Communication History Import screen displays.
Click Add and enter criteria for the import in the fields described in the table below.
READ OPTION
predefined
Indicate whether to read or commit the import file. The communication history records will only be imported if the read option is “Commit”. A report is generated in both cases.
FILE FORMAT
setup
Select the file format to use for the import. This must be defined in file mapping with the “CommHistImport” usage.
FILE NAME
open (30)
Specify the name of the file to import. The file name may default from the file map, but can be changed. The file should be in the /dti/exchange/cm
directory (or your [defaultdir] directory, if other than “cm”).
DELIVERY DATE
date
The delivery date can be specified in the file format, using the DeliveryDate element in the file map. If the file map does not contain this element, this field opens, and you must enter the delivery date for the communication history here. This is typically the date on which the newsletter or other communication was sent to the customer.
Click OK and Continue to read the file. If Read Option is “Commit”, communication history records will be imported and can be viewed in Customer Service.
The Communication History Import processing report displays the number of records validated or imported.
Circulation has the ability to import data from a telemarketing system or other source. Starts, stops, restarts, moves, delivery schedule changes, payments, complaints, billing changes and combo changes can all be imported. Solicitation codes can also be updated. After the import, Circulation in turn creates an export file, detailing records that were rejected or have warnings.
Subscriber Activity reads in a file from /dti/exchange/cm/secure
, and creates subscriber transactions using the guidelines described in the following table. A separate section of Business Rules, Import Sub Activity (see Import Sub Activity in the Setup Manual) allows you to configure some aspects of the import.
All transactions
If the Circulation Occupant ID, Address ID, or Subscription ID is supplied by the interface file, the address, occupant, or subscription in Circulation must match the information in the file. If no Occupant ID, Address ID, or Subscription ID is supplied, Subscriber Activity will attempt to match a Circulation address based on address data in the file. All address elements must match, except for the unit designator (Apt, #, Room, etc.). If the file contains a name, the occupant first and last name in the file must exactly match the occupant first and last name in Circulation for the subscriber matched. If no Occupant ID, Address ID, or Subscription ID is supplied, Subscriber Activity will attempt to match a Circulation address based on address data in the file. All address elements must match, except for the unit designator (Apt, #, Room, etc.). If the file contains a name, the occupant first and last name in the file must exactly match the occupant first and last name in Circulation for the subscriber matched.
Start
If this is a mail delivery start, the occupant cannot have an address that the router determines should be route delivered. If this is a route delivery start, the occupant must have an address that is route delivered, as determined by the router. When creating a new start, Subscriber Activity will create a new occupant record if there is no matching occupant at that address in Circulation. It will then assign the subscription to a label group (based on the Zip code) or a route (based on the router). It will also determine the subscription rate, occupant type, credit status, AAM zone, unlisted phone number flag, and send invoice and send renewal flags, if this information is not supplied by the interface file.
Stop
The occupant must have an active subscription, and no pending stop transactions.
Restart
The occupant must have a subscription that is temp stopped on the record’s transaction date (cannot be perm stopped or active), and cannot have a restart between the temp stop date and the record’s transaction date.
Delivery Schedule Change
The occupant must have an active subscription. There cannot be a pending delivery schedule change transaction for the subscriber. Business Rules can be set to require the delivery schedule in the file to contain a higher number of delivery days than the subscriber’s current delivery schedule. For example, a delivery schedule change that upgrades a subscription from Mon-Fri to 7-day would be accepted, but a delivery schedule change that downgrades a subscription from Mon-Fri to Sat-Sun would be rejected. When creating the delivery schedule change, Subscriber Activity will determine the new subscription rate, if not supplied by the interface file.
Move
The occupant must have an active subscription, and no pending stop transactions.
Payments
The occupant must have a subscription (it does not have to be active). Cash, check, credit card or bank draft payments can be interfaced. Business Rules determine the number of days that are added to the payment date when importing cash or check payments.
Billing Changes
The occupant must have an active subscription.
Combo Changes
Combo changes are supported for both non-combo to combo subscription changes and combo to combo subscription changes.
Complaints
An occupant or address must be supplied. The occupant does not need to be a subscriber.
Demographic Answers
An occupant or address must be supplied. The occupant does not need to be a subscriber.
Solicitation Update
Up to two solicitation codes can be included in the file. If they are, the occupant matched in Circulation w ill be updated with the solicitation code(s).
Select Subscriber Activity from the Import menu to display the Subscriber Activity Import screen.
Select Add and complete the following fields.
FILENAME
open (25)
Enter the name of the import file. The import file can have any name, but must be located in the /dti/exchange/cm directory.
BANK
setup
Enter the bank for cash, check or bank draft payments being interfaced.
READ OPTION
predefined
Indicate whether the import should be run in Edit only or Commit mode. Commit will create transactions and update solicitation codes. Edit only will not update any information, but it will validate the data in the interface file and display warnings and errors on an error report. When first implementing the interface, we recommend running the interface in Edit only mode before committing.
CREATE EXPORT FILE
yes/no
Indicate whether an output file should be exported to the /dti/exchange/cm directory. The output file lists the status of each imported record.
AUTO ACCEPT
yes/no
Indicate if you want all open batches to be accepted automatically. Transaction Security controls whether the default answer can be changed.
SUSPEND ALL STARTS
yes/no
Set this field to “y” if all new starts should be suspended.
ALLOW START FOR EXISTING SUBSCRIPTION
yes/no
Set this field to “y” if new starts are allowed for addresses that already receive a subscription. Set this field to “n” if starts are not allowed for addresses with existing subscriptions.
Select Continue to run the interface. If the read option is Commit, transactions will be created in Circulation, solicitation codes will be updated, and an output file will be exported. If the read option is Edit only, the data will only be validated. In both cases, a report will be displayed after processing is complete. If Create Export File is set to “y”, an output file will be also be created in the /dti/exchange/cm/secure
directory, listing the status of each imported record. The standard view/print options are available.
For the format of the import and output files, see Appendix B. For descriptions of the reject codes, see Subscriber Activity Import | Reject Codes.
Rewards are exported to the rewards management application via the Rewards Export. To insure that the records were interfaced correctly, a response file may be sent back from the rewards application. The response file determines whether a reward was accepted or rejected. Once a response has been received for a reward record, the reward will be considered completed rather than pending. Importing responses is optional.
Select Reward Response from the Utilities | Import
menu to display the Reward Response Import screen.
Select Add and complete the following fields.
READ OPTION
predefined
Indicate whether to Edit or Commit the import file. Reward records will be updated only if the read option is “Commit”. If “Edit” is selected, a report will appear, but no records will be updated.
REWARD PROGRAM
setup
Select the rewards program that you are interfacing.
IMPORT FORMAT
predefined
Select the format for the rewards import.
FILE NAME
open (16)
Enter the name of the response file being imported. The file must be placed in the /dti/exchange/cm directory.
Select Continue to import rewards file. See Appendix B for the format. A processing report will list details about the import and any errors that occurred.
This utility loads authentication control history from a flat file. Authentication history is used to track subscriber digital access, for AAM and other purposes. This utility can be used as an alternative to iServices Authentication.
Select Import | Auth Import
to display the Authentication Import window.
In the File Format field, enter the name of the file map created for this option. The “AuthImport” file mapping usage is used for this import. See Appendix B for the possible data elements.
In the File Name field, enter the name of the file to import. This file must exist in the /dti/exchange/cm
folder.
Select Edit to view the records to be imported or Commit to import the records.
Click OK to run the utility.
Note:
If the AuthControl data element is not included in the specified file, you will be prompted to enter a valid authentication control ID before continuing with the import.
The Federal Trade Commission administers a national Do Not Call (DNC) list for telemarketing. Most telemarketers are forbidden from calling consumers that place their phone numbers on the list.
The Do Not Call List utility assists newspapers in complying with federal DNC lists. The utility will allow full DNC lists or changes to DNC lists to be imported. State lists may also be imported, provided they are in the same format as the federal DNC list. Federal DNC lists can be downloaded from http://telemarketing.donotcall.gov. The list can be in flat text or XML format—choose flat text for use with Circulation.
When a list is imported, phone numbers contained on the list are flagged as Do Not Call numbers. The Do Not Call setting can be used as a selection parameter in Targeted Marketing (which is the method most often used to generate telemarketing lists) and viewed for a specific occupant in the Occupant Phone window in Customer Service. Old DNC records can be deleted via the Do Not Call List purge utility.
Select Do Not Call List from the Utilities | Import
menu to display the Do Not Call Import screen.
Select Add and complete the following fields.
LIST
setup
Specify the list (e.g., “federal”, “Minnesota”) that is being imported. This must be defined in advance (see Do Note Call List in the Setup Manual).
LIST TYPE
predefined
Indicate whether this is a full list or a list containing changes only.
EFFECTIVE DATE
date
Enter the date on which this list becomes effective.
ALL AREA CODES, AREA CODE
yes/no, integer (3)
Indicate whether the phone numbers for all area codes should be read in and, if not, enter the area code that should be read (enter “*” to multi-select area codes).
FILE FORMAT
setup
Select the file map to use for this import.
INPUT FILE NAME
open (30)
Enter the file name of the DNC list file sent by the government. The file must be placed in the /dti/exchange/cm
directory.
For the full list, each record in the file should contain only the occupant’s area code and phone number, separated by a comma. For example: 788,7643087.
Select Continue to run the import. The phone numbers in the DNC list will be read and compared to Circulation’s Do Not Call records. If no record exists for a phone number, it will be added; if one does exist, the record’s start date will be updated with the effective date entered at run time. If importing a full DNC list, after the import all phone numbers not contained in the file will have their Do Not Call records end dated (the end date will be the day prior to the effective date).
This utility uses a file map to import Note Transactions into Customer Services for selected subscriptions. The file format of this import is determined by file mapping (NoteImport usage). See Appendix B for a list of data elements available for this format.
Note: Product was not included in the file map as it is assumed by the SubscriptionID. The Note transaction’s is Permanent? automatically defaults to No. Remarks can be up to 2000 characters.
Create an ASCII file containing the desired data elements.
Note: SubscriptionID and Remarks are required data elements.
Select Import | Note Transaction
to display the Note Transaction Import window.
Click Add and complete the following fields.
Read Option
predefined
Indicate whether to commit or edit the note transactions in the ASCII file. If you choose “Commit” the Note transactions will be created. If you choose “Edit”, only the processing report will be created (you can then look the report over for errors before committing).
File Format
setup
Select the file format to use for the import. At least one format for the Note Import usage must be defined in the File Map setup (see Appendix B).
File Name
open (30)
Dependent on File Format. Will populate if File Format has a default.
Tran Date
date
Pre-populates with current run date.
Source
setup
Valid Source from setup. If Source is included in the import file, the value from the import file is used regardless of what is entered during run-time.
Reason
setup
Valid Reason from setup. If Reason is included in the import file, the value from the import file is used regardless of what is entered during run-time.
Click OK and then Continue to import the Notes transactions. A Note transaction will be created in Customer Services for each SubscriptionID in the import file. A processing report will display the number of records created along with any error and/or informational messages related to the import of the data elements.