Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
A route’s delivery can be suspended for a period of time. For example, bad weather might prevent some routes from being delivered on a given day. When a route is suspended, it will not appear on distribution reports, and its draw will not be included in AAM reporting. Subscribers on suspended routes will be temporarily stopped for the number of days the route is suspended. The carrier may or may not be charged/credited for the draw on the suspended days.
Note: The Suspend transactions created by the Suspend Route utility are processed only during non-final Transaction Processing runs.
The following setup must be in place before using this option:
At least one reason code each must be set up for the Suspend and Unsuspend transaction types in Reason setup. These will be used as the reasons for the route’s suspension and reinstatement.
The Suspend reason code must also be set up for the transaction type of Stop, and the Unsuspend reason code must also be set up for the transaction type of Restart. For example, if you define a reason code of “SUSPEND” for the transaction type of Suspend, you must also define a reason code of “SUSPEND” for the transaction type of Stop. Similarly, if you define a reason code of “UNSUSPEND” for the transaction type of Unsuspend, you must also define a reason code of “UNSUSPEND” for the transaction type of Restart.
For the Stop and Restart reason codes, the Update Draw, Print On Bundle, and Print Code On Bundle fields all must be set to “n.” This is required because the temporary stops and restarts created by the suspend and unsuspend processes should not affect the draw and are not printed on bundle tops (bundle tops are not produced for a route while it is suspended).
Business Rules must be set up to handle special circumstances, such as perm-stopping a subscriber on a suspended route. See Suspends in Customer Service for information.
Select Suspend Route from the Utilities menu.
Click Add and complete the following fields.
SUSPEND/UNSUSPEND INFORMATION
TRANSACTION TYPE
predefined
Indicate whether you are suspending or unsuspending (reinstating) routes.
SELECTION TYPE
predefined
Indicate whether routes should be selected for suspension/reinstatement by district, route, or account.
PRODUCT
open (8)
Enter the publication for which you are suspending or reinstating routes.
SELECTION
setup
Depending on what you entered in Selection Type, enter the district, route, or account that should be suspended or reinstated. You can also multi-select. If you select districts, all routes in the selected districts will be suspended or reinstated. If you select accounts, all routes associated with the accounts will be affected.
ROUTE TYPE
predefined
Indicate whether single copy or home delivery routes will be suspended or reinstated.
SOURCE
setup
Enter the source code for the suspension or reinstatement.
REMARKS
unlimited
Enter any remarks pertinent to the suspension or reinstatement.
SUSPEND
SUSPEND DATE
date
Enter the date on which the routes will be suspended.
ROUTE REASON
setup
Enter the reason code for the suspension. The reason code must be a Suspend reason code.
CHARGE/CREDIT ACCOUNT?
yes/no
If you are suspending home delivery routes, indicate whether carriers should be charged/credited for the draw on the suspended day. Single copy routes will never be charged or credited for a suspended day.
ROUTE DRAW TYPE
predefined
If you selected Charge/Credit Account, indicate the draw types for which carriers should be charged/credited on the suspended day, or multi-select draw types. The valid draw types are carrier collect, office pay, paid comp, unpaid comp, service, and sample.
SUBSCRIPTION REASON
setup
Enter the reason code for the temporary stop transactions that will be created by the system for subscribers on the routes selected. The reason code must be a Stop reason code.
UNSUSPEND
UNSUSPEND DATE
date
Enter the date on which the routes will be reinstated.
REASON
setup
Enter the reason code for the reinstatement. The reason code must be an Unsuspend reason code.
SUBSCRIPTION REASON
setup
Enter the reason code for the restart transactions that will be created by the system for subscribers on the routes selected. The reason code must be a Restart reason code.
Click OK and then Continue to complete the suspension (or reinstatement). A Suspend transaction will be created for the route. This transaction, when processed during non-final Transaction Processing, will create temporary stops for subscribers on the route. Once processing is complete, a report will display details about the process.
Note: If a route has subscribers delivered by other routes (e.g., different weekday and weekend routes), the route cannot be suspended unless the other route(s) delivering to its subscribers are also selected for suspension. Likewise, a route cannot be reinstated unless all other routes delivering to its subscribers are selected for reinstatement.
Once delivery can be resumed, routes are reinstated using the Suspend Route option with a Transaction Type of “Unsuspend.” An Unsuspend transaction will be created for each route that is reinstated. When processed by Transaction Processing, the Unsuspend will create restarts for the subscribers on the route.
For example, if a route is suspended on the 6th and reinstated on the 9th, subscribers on the route will have a temporary stop dated the 6th and a restart dated the 9th. This means that the route was suspended on the 6th, 7th, and 8th, and the subscribers will have their expire dates extended by three days.
If a route is suspended, a draw of zero will be shown for the suspended days and a suspend message will be displayed in the Route Service window. The route will also have a Suspend transaction. If this transaction is for a future date, it can be deleted, which would cancel the suspension.
When the route is reinstated, the suspend message will no longer appear, and the route will have an Unsuspend transaction. Again, future Unsuspend transactions can be deleted, which would cancel the reinstatement.
If a subscriber is on a suspended route, a message will be displayed in the Customer Service window. The subscriber will also have a Suspend transaction; this is the temp stop, but it is called “suspend” to distinguish it from ordinary temp stops.
When the route is reinstated, the suspend message will no longer appear, and the subscriber will have an Unsuspend transaction, which is the restart.
Notes:
If a start or restart is entered for a subscriber on a suspended route, it will be processed normally, but a temp stop (Suspend) will be created for the same date.
If a stop is entered for a subscriber on a suspended route, a restart (Unsuspend) transaction will be created when the stop is processed, so the subscriber will be unsuspended but stopped. The Business Rule, What is the reason code to use when a suspended subscription is restarted to process a stop? (Customer Services section), identifies the reason code to use for these Unsuspend transactions. This must be a Restart reason code defined with the Update Draw and Print On Bundle fields both set to “n.”
The temp stop (Suspend) and restart (Unsuspend) transactions are processed when they are created; therefore, they cannot be modified or deleted. However, if the subscriber really does want to temp stop, the Restart field in the temp stop can be set to “n” so that another temp stop will be created when the route is reinstated. This is an alternative way to enter a stop for the subscriber. The Business Rule, What is the reason code for the temp stop created when an unsuspend subscription is overridden? (Customer Services section), identifies the reason code to use for these temp stops. This must be a Stop reason code with the Update Draw and Print On Bundle fields both set to “n.”
If a component of a combo subscription is suspended, and the combo has Must Stop Together checked in Combo setup, Suspend Route will use the Business Rule—For combo subscriptions, should the suspend route process override the combo's setup for 'must stop together?’ to determine how to handle the rest of the combo. If the Business Rule is set to “No,” the other components of the combo will also be suspended.
As mentioned, suspended routes will not appear on any reports (bundle tops, truck manifest, AAM reports, etc.). Subscription messages for the route will be retained, however.
When the route is reinstated, all of the subscription messages that have accumulated over the suspended period will appear on the route’s bundle top.
If an account is to be charged/credited for some or all of the draw on suspended days, draw records will be kept for the draw types that should be billed. The draw, however, will be given a draw type of “suspend,” so that it will be ignored by most Circulation options.
Billing, however, will pick up suspended draw and bill it. It will be billed at the normal rate. If an account will not be charged/credited for suspended draw, no draw records will be kept.
The Utilities menu contains options to suspend routes, export routes, and draw information to an inserting system. The utility options are listed below.
Circulation has the ability to interface draw and truck information to the BURT inserting software package. The Burt Export option writes four fixed-length ASCII files to the /dti/exchange/cm directory. These files can then be imported into the BURT system. The export now includes zip pure records for each zip code the route is linked to for sites that export alternate zone information.
Note:
The Burt Export is a licensed add-on feature. You must license and activate the “Burt Export” or “BurtPlus” add-on records before you can use it. Contact the Newscycle Support Center for assistance.
The Burt Export does not export insert or mix information. This means that the inserts must be scheduled and the mixes must be created in BURT.
The Burt format version used (version 4 or version 7).
Whether routes with zero draw for the draw date are included in the export.
Whether the class of sale should be “HD” for home delivery routes and “SC” for single copy routes, or the first two characters of the route’s route type or single copy type.
Whether carrier routes or ad zones should be exported as Burt “ad routes”. If ad zones are exported, a special ad zone map must be defined to identify the “ad route” ad zones.
Whether the truck departure sequence is exported as the in the Sequence Offset field, and whether the Route Sequence field is populated.
Whether mail subscribers are included in the export. If so, a carrier route and an ad route record will be exported for each edition within a Zip code or ad zone (based on the ad zone type selected) and include the draw for all mail subscribers receiving the edition in that Zip or zone. If using ad zones, they must be defined by Zip code; mail subscribers with Zip codes that are not assigned to an ad zone will be grouped under the ad zone “MAIL”. The route ID exported will be “Z” plus the Zip code. The trucks exported will be “ML” plus the ad zone or Zip code. The class of sale for mail draw is also specified in Business Rules. Note that mail draw will not be exported if the ad zone type is “Truck”.
Whether the Burt Product Type can vary by route. If so, “Routes” will be an option in the Home Delivery Product Type and Single Copy Product Type fields. If the “Route” option is selected, the Burt product type exported for the route will be based on route setup (for actual or pending draw, the Burt Type field on the Route Setup tab, and for advance draw, the Burt Part field on the Sections tab). If a product type is not defined for a route, the product type specified in the Home Delivery Indicator field will be exported.
The file extension used for the Burt files (can be product ID, draw date, or both).
The entry and presort discount codes exported, if any.
Draw by Carrier Route (CR)
Draw by Ad Route (AR)
Draw by Ad Route Checksum (ARC)
File Name Index (FN)
Carrier Route Detail (BurtPlus add-on only)
Carrier Messages (BurtPlus add-on only)
See Appendix B for the formats.
Select Burt Export from the Utilities | Export menu.
Click Add and complete the following fields.
PRODUCT
setup
Enter the publication for which to export draw and truck information to BURT.
DRAW DATE
date
Enter the date for which draw information should be exported.
DRAW TYPE
predefined
Indicate whether actual, advance, or pending draw should be exported. If draw has already been exported for this product, date, and draw type, you will be prompted as to whether the existing file should be overwritten.
SECTION
setup
If running the export for a draw type of “Advance,” specify the section whose draw numbers should be exported (if advance publishing is run by section). If advance publishing is across all sections, enter “*” here.
DEPARTURE SEQUENCE
setup
Enter the truck departure sequence that should be used to determine the trucks to be exported.
TRUCK SEQUENCE
setup
Enter the truck sequence that should be used to determine the routes to be exported.
HOME DELIVERY PRODUCT TYPE, SINGLE COPY PRODUCT TYPE
predefined
BURT has a Product Type field, which indicates whether a route is shipped complete or in parts that are assembled outside of the mail room. In these two fields, indicate whether your home delivery routes and single copy routes leave the mail room as completes or parts. If the Business Rule, Does the route indicator vary by route for Burt Export? (Route Services section) is set to “yes”, you will also be able to enter route in these fields. Selecting route will export the Burt product type entered for the route in Route Setup or, if not defined, the product type specified in the fields below.
HOME DELIVERY INDICATOR, SINGLE COPY INDICATOR
open
If you selected “Route” in either of the product type fields above, enter the Burt product type to export for routes that do not have a product type specified in Route Setup. Note that if the Override field, below, is checked, this will be the product type exported for all home delivery and/or single copy routes.
OVERRIDE ROUTE INDICATOR
yes/no
The product type for a route may be specified in Route Setup. If Home Delivery Product Type or Single Copy Product Type is set to “Route”, indicate whether the route’s predefined product type should be exported, or whether the home delivery/single copy indicators entered above should be exported for all routes.
ROUTING SCHEDULE
open (6)
The BURT system uses the concept of a routing schedule (or “delivery schedule”) to identify how the inserting should be carried out on a given day of the week. Potentially, seven different routing schedule could be used. For example, the same departure sequence and truck sequence might be used for the Times on Tuesday and Wednesday, but in certain cases two Circulation Management “trucks” might be loaded onto the same physical truck on Tuesday. To differentiate the different load arrangements, Tuesday and Wednesday could be assigned separate routing schedules. In this field, enter the routing schedule for the export date (for example “TMSSAT” for “Times Saturday”).
AD ZONE TYPE
predefined
BURT has an “ad zone” field. Indicate whether the route’s truck, Zip code or ad zone should be exported in the ad zone field. Ad zone will only be a valid option if you have InsertPlus.
Click OK and then Continue to perform the export. After the export has completed, a processing report will list the number of records exported and any errors that occurred during the process; the standard viewing and printing options will be available.
This option exports a draw forecast file to be used by an external forecasting application. The export is for a specified time period and uses file mapping (“DrwForecastExprt
” usage). The export file includes single copy draw, returns, and draw adjustments for a selected product and date range. Past and future draw dates can be included in the file.
Note: This option exports only single copy draw. Home delivery draw is not included. Also, only replacement draw is exported. This export does not create additions and subtractions.
Select Draw Forecast from the Utilities | Export menu to display the Draw Forecast Export window.
Click Add and complete the following fields.
PRODUCT
setup
Specify the publication whose draw, returns and draw adjustments should be exported.
START DATE END DATE
date
Enter the date range for which to export the information.
ROUTE TYPE
setup
Select the type of route to include in the export: home delivery, single copy, or both.
DRAW TYPE
predefined
Select Advance, Pending, or Actual draw.
PROJECT ACTUAL DRAW WHEN NO DRAW FOUND
yes/no
When no pending or advance draw exists for a given weekday, actual draw can be used instead. For example, if you are running advance draw for a week, but advance draw exists for only one day, select this checkbox if the remaining days should be populated with actual draw.
EXPORT DAYS WITH NO DRAW
yes/no
When this checkbox is selected, data will be exported for all days selected, in order to keep the format of the export file consistent each time it is run. If this option is not selected, only days with draw will be exported, and it will be possible for the number of days to vary among exported records.
EXPORT CHANGED DRAW ONLY
yes/no
When this checkbox is selected, only those days of the week with draw that differs from the previous week will be exported. For example, if Wednesday’s draw is the same as it was last week, it will not be exported. If this option is not selected, all draw will be exported.
DRAW OPTION
predefined
This field is available only when Export Changed Draw Only (above) is selected. Indicate whether All Dates In Range or Changed Dates Only should be exported. For example, if the export is run for one week, and only one day’s draw differs from the previous week, you have the option to export only that date or all dates in the entered date range.
EXPORT BY DRAW CLASS?
yes/no
Indicate whether draw, returns, and draw adjustments should be sorted by draw class in the export file.
EXPORT BY DELIVERY SCHEDULE ID?
yes/no
Indicate whether draw, returns, and draw adjustments should be sorted by Subscriber’s delivery schedule in the export file.
FILE FORMAT
setup
Select a file format to use (set up using File Map).
FILE NAME
open (20)
Enter the name of the file to be exported.
FILE OPTION
predefined
Select append to add new figures to an existing file or replace to replace an existing file.
TRUCK SEQUENCE
setup
If the selected file map (File Format field) contains the truck ID element, specify the truck sequence ID to use in this export.
Click OK and then Continue to run the export. The file will be exported to the default exchange directory. A processing report will list the number of records exported and any errors that occurred during the process.
Use this import utility to import single copy draw changes from an ASCII file. For example, if you track NIE draw in a different system, you could export draw changes for NIE routes to a file and import them into Circulation.
This option creates a suspended batch of draw changes. The draw changes will replace (rather than adjust) the route’s draw for each day of the week beginning with the start date. A reversal date for the draw change may be specified in the ASCII file, or may be left blank (no reversal date). All of the draw dates interfaced must be unpublished, and only draw changes for single copy routes can be imported.
Create an ASCII file containing the draw change information. The file format is defined in File Mapping.
Select Utilities | Import | Single Copy Draw to display the Single Copy Draw Import window.
Click Add and complete the following fields.
READ OPTION
predefined
Indicate whether to edit or commit this information. Select commit to import draw records. Select edit to view a report showing the number of records processed (and errors)—you must then run this option a gain and set this field to commit. A batch, description, source and reason are only needed when this field is set to commit.
BATCH
open (8)
Specify an ID for the draw change batch that will be created.
DESCRIPTION
open (30)
Enter a description of this batch.
SOURCE
setup
Enter the source code for the draw change batch (such as “NIE”).
REASON
setup
Enter a reason code for the draw change batch.
OVERRIDE SETUP
yes/no
This checkbox is available only in “commit” mode. Select this checkbox if draw changes should be made for single copy routes that are set up not to allow them (i.e., draw changes = “no” in Route Setup). Notes: The availability of this checkbox is controlled by the “AllowDrwChgOvrd” Transaction Security item.
PRODUCT
setup
Enter the product ID or leave the field blank to use an imported value.
EFFECTIVE DATE
date
Enter the date on which these draw changes will be active or leave the field blank to use an imported value.
REVERSAL DATE
date
Enter the date on which these draw changes should be reversed or leave the field blank to use an imported value.
ADJUST/REPLACE
predefined
Indicate whether these draw changes should adjust existing draw or replace it.
FILE FORMAT
predefined
Enter the name of the file map to use for this import.
FILE NAME
open (30)
Enter the name of the import file in the /dti/exchange/cm
directory.
Click OK and then Continue to import the draw changes. The draw changes will be imported, and a suspended batch created (the batch can be accepted using Batch Draw Change). A processing report will display the number of records exported and any errors.
Dock (chute) assignments for trucks can be imported from an external file, via Truck Dock Import. The option imports a file that is comma or pipe delimited for a specified effective date and truck departure, and contains two fields. The first field is the truck ID and the second is the dock number.
Create an ASCII file containing the dock assignments, in the format described above.
Select Utilities | Import | Truck Dock Import to display the Truck Dock Import screen.
Click Add and complete the following fields.
FILE NAME
open (30)
Enter the name of the import file in the /dti/exchange/cm directory.
DELIMITER
predefined
Indicate whether the delimiter used is a comma or a pipe symbol (|).
EFFECTIVE DATE
date
Specify the date on which the dock assignments will take effect.
TRUCK DEPARTURE
setup
Select the truck departure for which the dock assignments are being imported.
READ OPTION
predefined
Indicate whether the file should be processed in edit or commit mode. Edit mode will only read the records and report any errors. Commit mode will create the dock assignments. NEWSYCLE recommends running this option in edit mode before importing the actual dock assignments in commit mode.
Click OK and then Continue to import the dock assignments. A processing report will display the number of records exported and any errors.
In addition to Burt, you can also export route and truck information to GMA’s SAM application, which is used in insert packaging. This allows circulation data to be transferred automatically to the GMA inserter. This export can be run for publications or TM products.
Note:
The GMA/SAM Export is a licensed add-on feature. You must license and activate the “GMA/SAM Export” add-on record before you can use it. Contact the Newscycle Support Center for assistance.
The GMA/SAM Export will not export InsertPlus insert or mix information. Inserts must be entered and mixes created in SAM. InsertPlus ad zones, however, may be exported.
Before running the export, Circulation route types must be mapped to GMA “account types”; account types are exported as part of the route information. This is done using the GMA/SAM Account Type option on the Setup menu in Utilities. Currently, this option is available only in Circulation’s character interface.
Several Business Rules in the Route Services section control various aspects of the SAM Export, including what is exported in the Zone Group, Content Code, and Plant Code fields, and whether mail draw is exported.
Select GMA/SAM Export from the Utilities | Export menu to display the GMA/SAM Export window.
Click Add and complete the following fields.
PRODUCT
setup
Specify the publication or TM product whose route information should be exported. Note that draw must be created during TM processing prior to running this export for a TM product. Mail numbers will not be exported for TM products (only publications).
DRAW DATE
date
Enter the date for which route information should be exported.
DRAW TYPE
predefined
Indicate whether actual, pending, or advance draw should be exported.
DEPARTURE SEQUENCE
setup
Select the truck departure sequence that should be used in the export. Only trucks in this sequence will be selected.
TRUCK SEQUENCE
setup
Select the truck sequence that should be used in the export. Only routes dropped by this truck sequence will be selected.
ACCOUNT GROUP TYPE
predefined
Indicate the entities that should be exported as account groups and zones. The choices are ad zone, Zip code, truck, parent truck, district, distribution zone and carrier ID.
ZONE TYPE
predefined
Indicate the entities that should be exported as zone types. The choices are ad zone, Zip code, truck, district, and distribution zone.
INCLUDE DRAW BATCH
open
This field allows you to include a suspended draw change batch (or batches) in the SAM export file, so that multiple export files can be generated for different draw scenarios. When the export is run, a message is written to the process log indicating which batches were included in the export.
CIRC GROUP
open (10)
Enter the circulation group ID that should be exported. This may default from Business Rules.
EXPORT FILE NAME
open (30)
Specify the file name for the SAM export file. This will be the name of the draw file; the global file will have this name with “GLBL.txt
” appended to it.
EXPORT MESSAGES
yes/no
Select this checkbox if you want messages records (1 through 6) to be exported. Messages will not be exported if this checkbox is not selected.
Click OK and then Continue to run the export. The files will be exported to the /dti/exchange/cm
directory. See Appendix B for the file format. A processing report will then list the number of records exported and any errors that occurred during the process.
Use this import utility to import drop times from an ASCII file. File layouts for this import are defined in File Map. At a minimum, you must include the truck ID, drop time and drop number in your file map, although you may include all of the required fields. Any fields that are not included in the file map will be prompted for at run time.
Select Utilities | Import | Drop Time to display the Drop Time 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).
FILE FORMAT
setup
Select a File Map format to use for this import. The file name may default from the file map.
PRODUCT
setup
Select the product.
RUN DATE
date
Enter the run date.
DEPARTURE
setup
Select the truck departure order.
TRUCK SEQUENCE
setup
Select the truck sequence.
DELIVERY DATE
date
Enter the delivery date.
FILE NAME
open (30)
Enter the name of the file being imported; it must be in the /dti/exchange/cm
directory.
Click OK and then Continue.
Many larger newspapers employ sophisticated inserting systems that have their own software applications. In order to insert the correct preprints in the papers for each route, these applications need the route draws. They also need to be updated when routes change trucks, or when ad zone boundaries change. The Insert Draw and Insert Base options export this data to an ASCII file, where it can be imported into an inserting system.
The draw export contains route draw figures, while the base export contains truck, ad zone, edition, preprint demographic, and other information for the route. The draw export will most likely be run daily. The base export may be run on a periodic basis, but if it is, you should wait to add new routes or make changes to existing routes until just before running the export.
Using this process, Circulation and the inserting application will always have the same information and you will not, for example, be importing draw into the inserting system for a route that doesn’t exist there yet.
The base export can be run for up to seven days, beginning with a user-defined start date. It can be run for both publications and TM products. In the case of a TM product, all routes belonging to its delivery publication will be exported. For each day, only one Zip code and AAM zone will be exported. If a route belongs to more than one, the Zip or AAM zone with the highest percentage will be used. The distribution ad zone (the ad zone belonging to the ad zone map that is assigned to the product on that day) will be exported, along with up to seven selling ad zones. A selling ad zone will be included only if it is assigned to an ad zone map on that day of the week. See the InsertPlus manual for more information about ad zones.
Note: If you do not have InsertPlus, the ad zone fields will be blank in the export.
The base records will be sorted in the export file by date, truck departure order, and the route’s drop order within each truck.
Select Insert Base from the Utilities | Export menu.
Click Add and complete the following fields.
PRODUCT
setup
Enter the publication or TM product for which base information should be exported.
START DATE, END DATE
date
Enter the date range for the base export. Route information will be exported for the days in the date range. If a publication does not publish on a given day of the week, no records will be exported for that date. Note that the export can be run for a maximum of seven days.
DEPARTURE
setup x 7
For each day of the date range, enter the truck departure sequence that should be used for sorting purposes.
TRUCK SEQUENCE
setup x 7
For each day of the date range, enter the truck sequence that should be used. This determines the truck to which a route is assigned and its drop order within the truck.
Click OK and then Continue to begin the export. The base data will be exported to /dti/exchange/cm
, and the file will be named <ProductID><Month><Day><Year> BASE
. For example, if route information for the Times is exported starting on 10/02/09, the file will be named times100209BASE
. See Appendix B for the format of this file. Once the export has completed, the Insert Base Export report will list the number of records exported, and other information about the process.
The draw export is run for a user-defined date, and can export actual or advance draw information. Only routes that are active and have draw for the publication entered will be included in the export.
Select Insert Draw from the Utilities | Export menu.
Select Add and complete the following fields.
PRODUCT
setup
Select the publication for which draw should be exported.
DRAW TYPE
predefined
Indicate whether to export actual or advance draw figures.
SECTION
setup
If you are exporting advance draw and you keep advance draw by section (a Business Rules consideration), enter the section whose draw figures should be exported. Otherwise, this field will be skipped.
DRAW DATE
date
Enter the date for which draw figures should be exported. If there are no draw records for this date and the type entered above, you will be prompted to enter a different date. Actual draw, for example, cannot be exported for more than seven publishing days in the future because it is kept for only seven days beyond the current publishing date.
Select OK and then Continue to begin the export. The draw will be exported to /dti/exchange/cm
, and the file will be named <ProductID><Month><Day><Year> <Draw Type>
. For example, if actual draw for the Times is exported on 10/02/06, the file will be named Times100206ACT
. If advance is exported rather than actual, the file would be Times100206ADV
. And, if a section is entered, the first three letters appended to the file name (for example Times100206ADVCOM
). See Appendix B for the format of this file. Once the export has completed, the Insert Draw Export report will list the number of records exported, and other information about the process.
This option allows you to select single copy draw class records based on product and draw class, and change the maximum return percentage permanently, or for a date range.
Select Max Return from the Utilities menu to display the Max Return Percentage window.
Click Add and complete the following fields.
Click OK and then Continue to change the percentages. A processing report will be displayed.
The Reseq Drop Order utility resequences the drop order of selected trucks and can also be used to remove end-dated truck records.
Select Reseq Drop Order from the Utilities menu to display the Resequence Drop Order window.
Click Add and complete the following fields.
Click OK and then Continue to run the utility.
Use this utility to record start and end times of each truck, as well as the drop time for each drop on a truck.
Select Utilities | Drop Time Entry to display the Drop Time Entry window.
Click Add and complete the following fields to define which trucks are displayed in the Truck Time table.
Click OK. Trucks that should have had deliveries for the run date entered are displayed in the Truck Time table.
Select a row in the Truck Time table and click Modify.
Complete the fields described below.
Click OK.
Select a row in the Truck Time table and click Drop Time. The Drop Time Entry window, which shows all of the deliveries for the truck in drop order, is displayed.
Select a row in the Drop Time table and click Modify.
Enter the drop date and time in the Delivery Date and Delivery Time fields.
Click OK.
Click Close when you have finished entering drop times.
The Truck Validation Sequence report lists potential problems in a truck sequence, such as routes that have more than one drop assigned, routes that are not assigned to a truck, and so on.
You can run the Truck Sequence 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 Utilities | Truck Validation to display the Truck Sequence Validation Report window.
Click Add and complete the following fields.
Click OK and then Continue to produce the report.
Note: The Router Import option is a licensed add-on feature. You must license and activate the “Router Import” add-on record before you can use it.
This option imports router changes from an external file in the RouteSmart format. To export Circulation route information, you generate the Route Delivery List report with a report type of “Export.”
Export Circulation’s route information to a file that can be read by RouteSmart. The Route Delivery List report, which is run as an export using a predefined “RouteSmart” file map, accomplishes this.
Import the file into RouteSmart and make the necessary route-boundary modifications. Then, export the route information from RouteSmart. Be sure to export all of the addresses for each route that was changed.
Using the new Route Import option, import all of the route information back into Circulation.
Run the Route Reassignment option to create reroute transactions for subscribers who are now on different routes.
To use this option, you will need to create a new file map with a usage of “RouterImport”. The data elements that can be used with this file map include AAM Zone ID, Address ID, New Route ID, Old Route ID, Product ID, and Record Identifier. All elements except AAM Zone ID and Record Identifier are required.
Note: If a route was changed in RouteSmart, all addresses on that route should be exported from RouteSmart and re-imported into Circulation so that the router is rebuilt completely. The Router Import utility will not append routes; it will replace them completely.
Select Utilities | Import | Router in Route Service to display the Router Import window.
Click Add.
Complete the following fields:
Read Option—Select Edit to produce a report of the router changes that would have been made if Commit were selected. Select Commit when you are ready to update the database with these changes.
When run in “Commit” mode, the Router Import will
make a backup copy of the current router tables (i.e., Router, RouterRoute, RouterPublication, and RouteAddress) in the default exchange directory,
delete all of the router-related records for both the old and new contained in the input file,
build a new set of router-related records for the “new” routes contained in the input file, and
produce a report of the new router segments that were created.
File Format—Select the file map that you created for this import.
File Name—The file name will default from File Map setup, but it can be changed. The file must be located in the default exchange directory.
4 Click OK to run the import.
The Truck Check report displays routes with draw that are not assigned to a truck for a selected truck sequence(s), with an option to create tasks. This information can be useful to ensure that all routes with draw will be included in the distribution documents.
Select Utilities | Truck Check to display the Truck Check window.
Click Add and complete the following fields.
Click OK and then Continue to produce the report.
When a route with draw is found, but not assigned to a truck, a task will be created if:
The Create Task checkbox is selected, and
A task is set up in the Tasks module for the Truck Check report (i.e., An Event of “Report Processing” and “Truck Check” selected as the Report).
Delivery deadlines can be defined for home delivery routes as part of Route setup (see ). The deadline indicates the time of day by which the route should be delivered. Deadlines can be viewed in Customer Service and Route Service (see ), and display when entering a complaint if the deadline has not yet been met.
You may want to override the normal delivery deadlines from time to time, for example if the weather is delaying delivery. This can be easily accomplished with this option, the Delivery Deadline Utility.
Select Deadline Override from the Utilities menu to display the Delivery Override window.
Click Add and complete the following fields.
Click OK and then Continue to override the deadlines. The utility creates Delivery Deadline Override records, which will be retained in the system for a certain number of days, as defined in Business Rules (How many days do you want to retain delivery deadline override records?). Once the overrides have processed, the Delivery Deadline Utility report will be displayed, listing the routes whose deadlines were overridden and other information about the process. The standard view/print options are available.
TRUCK SEQUENCE
setup
Enter truck sequence containing the drops to be resequenced.
REMOVE END DATED RECORDS
yes/no
Select this checkbox if end-dated drops should be deleted.
RESEQUENCE ALL TRUCKS TRUCK
yes/no setup
Indicate which trucks should be resequenced. Either specify the trucks in the Truck field or select Resequence All Trucks.
MAX CHARACTERS
open
Enter the maximum number of characters that can be used in a drop sequence number. For example, entering “3” in this field indicates that drops can be numbered up to 990 using multiples of 10 (e.g., 10, 20, 30, up to 990). If it is not possible to use multiples of 10 and remain within the 3-character limit, then a smaller multiple (between 1 and 9) will be used instead.
DEPARTURE ORDER, TRUCK, and DESCRIPTION
display
The truck’s departure order, ID, and description are displayed.
DEPARTURE DATE and DEPARTURE TIME
date
Enter the date and time of the truck’s departure. Enter the time in 24-hour
format (e.g., 23:30
).
COMPLETE DATE and COMPLETE TIME
date
Enter the date and time that the truck completed its route. Enter the time in 24-hour
format (e.g., 00:45
).
DEPARTURE
setup
Enter the departure whose departure orders will be resequenced.
REMOVE END DATED RECORDS
yes/no
Select this checkbox if end-dated departure IDs should be deleted.
MAX CHARACTERS
open
Enter the maximum number of characters that can be used in a departure order number. For example, entering “3” in this field indicates that departure order can be numbered up to 990 using multiples of 10 (e.g., 10, 20, 30, up to 990). If it is not possible to use multiples of 10 and remain within the 3-character limit, then a smaller multiple (between 1 and 9) will be used instead.
PRODUCT
setup
Specify the product or enter “*” to multi-select.
TRUCK DEPARTURE
setup
Specify the truck departure or enter “*” to multi-select.
TRUCK SEQUENCE
setup
Specify the truck sequence or enter “*” to multi-select.
CHECK BY EDITION EDITION
yes/no setup
If you want to limit this utility to a specific edition, select Check By Edition and specify the Edition.
WEEK DAYS
predefined
Optionally, specify the day of the week.
START DATE
date
Enter the date at which you want to start locating unassigned routes.
DRAW METHOD
predefined
Select the draw method: Actual, Advance, or Both.
CREATE TASK
check box
Select this check box if you want to create tasks to alert users to assign these routes.
PRODUCT
setup
Enter the product ID.
SELECTION TYPE
predefined
Indicate whether this report should include a particular edition, district, zip, route, truck, single copy type.
TRUCK SEQUENCE
setup
If you entered “truck” in Selection Type, select a truck sequence here.
SELECTION
setup
Enter the specific edition, district, zip, etc. (depending on what type is entered in Selection Type) to include. If you entered “mail” above, this field will be skipped.
ZIP EXTENSION
open
If you are using a Zip code as the selection, enter the Zip extension here.
DRAW CLASS
setup
Select the draw class for which you want to change the maximum return percentages.
START DATE
date
Enter the date on which the maximum return percentages should be changed.
END DATE
date
Enter the date on which the percentages should be changed back.
MAX RETURN PERCENT (SUN-SAT)
decimal (6)
Enter the maximum return percentage for these draw classes for each day of the week.
PRODUCT
setup
Select the product to determine which trucks are displayed in the Truck Time table.
RUN DATE
date
Enter the run date.
DEPARTURE and TRUCK SEQUENCE
setup
If only one departure and truck sequence exist for the entered product and run date, they will be populated automatically, and these fields will be skipped. Otherwise, you must enter the departure and truck sequence.
DEPARTURE DATE, COMPLETE DATE, and DELIVERY DATE
date
Optionally, you can use these fields to establish default dates for the Truck Time table.
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
Indicate whether you want all trucks to appear on the report.
PRODUCT
setup
Enter the publication whose deadlines are being overridden.
OVERRIDE DATE
date
Enter the date on which the override will take place. The override will only be effective on this date.
ENTITY TYPE
predefined
Indicate whether overrides are being entered for routes based on area, region, zone, district, route, depot, truck, edition, or Zip code
TRUCK SEQUENCE
setup
If the entity type above is “truck”, enter the truck sequence that should be used when selecting routes from the trucks entered. Otherwise, this field will be skipped.
ENTITY
setup
Enter the entity for which deadlines are being overridden. For example, if the entity type is “edition”, you would enter an edition here. Enter “*” to multi-select entities.
OVERRIDE TYPE
predefined
Indicate whether the override will be an Adjust, Override, or Delete. An Override will set a new delivery deadline for this date for the routes selected. An Adjust is used when you need to add time to an override deadline already entered. A Delete will remove an override, which means the deadlines defined in route setup will be in force again on that date.
OVERRIDE TIME
integer (4)
Enter the time, in military format, for the deadline. If this is an adjust, rather than an override, enter the number of hours and minutes that the deadline should be extended.
REMARKS
open (30)
Enter any remarks pertinent to the deadline override. Remarks entered here will appear on the Delivery Deadlines screen in Route and Customer Services.
The Draw Change Lockout utility is used to lock out additional draw changes for a selected date, product, single copy type, route, etc. If draw changes are locked, then additional draw changes cannot be entered in Route Service, iServices Distribution, or imported from a file, depending on the particular usage defined.
Select Utilities | Draw Change Lockout to display the Draw Change Lockout window. All active draw change lockouts are shown in the upper portion of the window.
Click the Add icon () and complete the following fields:
PRODUCT
setup
Specify the product to which this lockout applies.
ALL EDITIONS EDITION
yes/no setup
Specify the edition to which this lockout applies, or select All Editions.
ALL SINGLE COPY TYPES SINGLE COPY TYPE
yes/no setup
Specify the single copy type to which this lockout applies, or select All Single Copy Types.
ALL ROUTES ROUTE
yes/no setup
Specify the route to which this lockout applies, or select All Routes.
ALL ACCOUNTS ACCOUNT
yes/no setup
Specify the account to which this lockout applies, or select All Accounts. If you select an account, then all routes associated with that account will be locked out.
ALL DRAW CLASSES DRAW CLASS
yes/no setup
Specify the draw class to which this lockout applies, or select All Draw Classes.
ALL USAGES USAGE
yes/no predefined
Specify the usage (external, internal, or import) to which this lockout applies, or select All Usages. • External refers to iServices Distribution and the Distribution API. • Internal refers to the Route Service module.
• Import refers to any import of draw changes.
DRAW START DATE DRAW END DATE
date date
Specify the date range of the draw affected by this lockout.
LOCKOUT START DATE LOCKOUT START TIME
date time
Specify the date and time at which this lockout takes effect. The start time is optional.
LOCKOUT END DATE LOCKOUT END TIME
date time
Specify the date and time at which this lockout is no longer in effect. These fields can be left blank.
Click OK to save the lockout information, or Add Another to add more lockout entries.