Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This section guides the user through the menu options that are available under the Distribution menu.
Some newspapers offer a previous day’s paper to new subscribers. For example, if a subscriber wants to start on a Thursday, the associate may offer the previous Sunday’s paper for free. The subscriber gets the bonus of an extra paper, and the newspaper is able to count some of its leftover Sunday papers as paid circulation. Previous delivery is available for route-delivered subscriptions only (not mail).
Before you can use the previous delivery feature, you must define the previous day (such as Sunday), and at least one day on which previous copies of a publication can be delivered (in Publication setup—see Publication in the Setup Manual).The Prev Delivery field can then be set to “y” during a new start (if there are no “exceptions”—see below). A “Previous Delivery” message will appear on the carrier’s bundle top on the delivery date, and cards for each previous delivery can also be printed, using this option.
In addition to new starts, subscribers with a restart and delivery schedule change may also be eligible for previous deliveries. Business Rules in the Customer Services section govern this.
Your newspaper may limit the previous delivery offer to subscribers with certain rates or on certain routes. You define these limitations in Circulation by indicating who should not be offered previous delivery. Exceptions to previous delivery can be made based on:
Route type
Route
Carrier
Subscriber rate code
Route type, route, and carrier exceptions are entered on the Prev Deliv Exception window (see Prev Deliv Exception in the Setup Manual). Subscriber rate code exceptions are defined with the rate codes (see Subscription Rates in the Setup Manual). If a new start, restart or delivery schedule change subscriber has a rate, route, or carrier that is excepted, the Prev Delivery field will not be open (i.e., the previous delivery cannot be offered).
When a new start, restart or delivery schedule change marked for previous delivery is entered, the delivery date for the previous delivery is immediately determined. This delivery date can be ascertained by viewing the Previous Delivery transaction that is created.
The delivery date for the previous paper depends on how you answer the Business Rule— Which date should previous deliveries be based on?, in the Route Processing section. This can be set to “entry date” or “start date”.
If the Business Rule is set to “entry date”, the previous paper will be delivered on the date the transaction is entered (unless Transaction Processing has already been completed, in which case it will be the next publishing day). If the question is set to “start date”, the previous paper will be delivered on the start date of the subscription, with the first regular paper. However, if the start date is not a valid previous delivery day, the “entry date” method will be used.
To illustrate when and how delivery dates are determined, let’s look at an example. Say the Star is set up for previous delivery as follows:
Sun
n
Sunday
Mon
y
Sunday
Tue
y
Sunday
Wed
n
Sunday
Thu
y
Sunday
Fri
y
Sunday
Sat
n
Sunday
Let’s also say the Times is set up the same way, but Business Rules for the Times is set to base the previous delivery date on the start date, while with the Star it is based on the entry date. Now, assume that on Thursday, January 6, we have the following starts (and transactions processing is not yet complete for 1/6):
Ella
Times
1/7 (Fri)
1/6 (Thu)
Start Date
Bob
Times
1/18 (Tue)
1/6 (Thu)
Start Date
Cara
Star
1/6 (Thu)
1/6 (Thu)
Entry Date
Greg
Star
1/19 (Wed)
1/6 (Thu)
Entry Date
Circulation would determine the following dates for delivery of the previous paper:
Ella. The Sunday, January 2 paper will be delivered on Friday, January 7.
Bob. The Sunday, January 16 paper will be delivered on Tuesday, January 18. Note that if Bob had started on the 19th (a Wednesday, which is not a valid delivery day), the “entry date” method would be used instead, and he would receive the January 2 paper on the 6th.
Cara. The Sunday, January 2 paper will be delivered on Thursday, January 6.
Greg. He will also get a Sunday, January 2 paper delivered on Thursday, Jan 6.
Previous delivery papers can count toward paid circulation as long as the previous paper’s publishing date is within six days of the delivery date. For example, if the previous delivery day is a Sunday, and on Sunday January 2nd we have 40 papers that are subsequently delivered later in the week, 40 copies will be added to the paid circulation for January 2nd.
If AAM has been closed for that date, however, the paid circulation will not be adjusted (see Close Day for AAM). Previous deliveries will not be separated on Circulation’s AAM reports—they will simply be counted as part of the paid circulation.
Previous deliveries create adjustments to route draw. So, if a route has two previous deliveries of the Sunday, January 2nd paper on the following Wednesday, and three on Thursday, the route’s draw for January 2nd will be adjusted by +5.
Transaction Processing will create a suspended batch of draw adjustments using the draw adjust code entered in Business Rules (Which draw adjust code should be used when updating draw for previous paper deliveries? in the Account Finance section). The draw adjust code should use a charge code that is a charge (not credit), and have Charge Account set to “n” and Adjust AAM History set to “y”.
The batch of previous delivery draw adjustments will be named “PDyymmddxx”, where “yymmdd” are the year, month and day respectively, and “xx” is a sequence number. For example, if there are two previous delivery batches for 05/17, they will be named PD00051701 and PD00051702. The draw adjustment batch must be accepted using the Route Adjust option before it can be processed (see Route Adjust).
Note: Draw adjustments made because of previous deliveries affect AAM reporting. The AAM may allow previous deliveries to count toward circulation only on certain days of the week—consult the AAM regulations for more information.
If you credit carriers for the delivery of previous delivery papers, you will need to set up a TM product for previous delivery. You can then credit the delivery carrier with TM credits by setting up a carrier credit rate for the TM product.
To align previous delivery with a TM product, you must answer the Business Rule— Which TM product should be used to credit/charge accounts for previous paper deliveries?, in the Account Finance section. When the previous delivery draw adjustment batch is accepted, Circulation will create TM draw for the product on the delivery date of the previous delivery. You can also print TM bundle tops and other documents for the previous delivery product, which may be helpful to personnel who must ship the correct number of previous deliveries to each route. It might also be useful to have the TM product printed with the publication in the publishing run.
One label will be printed for each subscriber who should receive a previous paper on the current publishing date. Previous delivery labels use the Business Rules settings in the Mail Processing section to determine formatting, such as the number of labels across one page and the width of the label.
Select Prev Delivery Labels from the Distribution menu to display the Previous Delivery Route Labels window.
Choose the product, edition, departure sequence and truck sequence for which you want to print bundle tops by selecting the appropriate Process checkbox. Note that edition will be “*” unless you have separate publishing runs at the edition level.
The Print Route Name and Print District Name checkboxes appear near the bottom of the window. This is where you indicate whether the route name and/or the district name should be printed on the label in addition to the route and district IDs.
If you want a separate route label file for each route, select the Additional Reports by Route checkbox.
Click Continue to produce the cards.
Most newspapers print bundle tops to attach to the bundles of papers they distribute to carriers. The bundle top information allows distribution personnel to count and load the bundles correctly and informs the carriers of any changes on their routes. Bundle tops are the primary means of communicating to carriers any delivery pattern changes, starts, stops, messages, complaints, and compliments about their work. You enter bundle information using this option, and then print the bundle tops using the Bundle Tops option.
You can enter distribution information for products and dates that are not in the current publishing run. Business Rules determine whether the truck sequence can be changed using this option. Business Rules also determine whether minimum bundle sizes can be used, as well as the default entries in the Print Key Bundles Only checkbox and the Separate Option field.
Note: See Enter Bundle Info for a discussion of the Advance Processing version of Enter Bundle Info.
Select Enter Bundle Info from the Distribution menu to display the Distribution Information window.
Click the Add Distribution Info icon ().
Enter distribution information in the Product through Truck Sequence fields (described below).
Click Next and complete the remaining fields.
PRODUCT
setup
Enter the product for which you are defining distribution information.
RUN DATE
date
Enter the publishing date for which you are defining distribution information.
EDITION
N/A
DEPARTURE
setup
Enter the truck departure sequence that should be used. The departure sequence is the order trucks follow on a given day departing from the dock. Examples are “Monday-Friday” and “Holiday.”
TRUCK SEQUENCE
setup
Enter the truck sequence for this product and publishing date. The truck sequence is a pattern that determines which routes are dropped by which trucks and in what order. Examples are “Daily” and “Sat-Sun”.
DEPARTURE ORDER, DROP ORDER
display
The departure order and drop order, which determine whether bundles are printed in ascending or descending order among trucks and within each truck, are displayed. These values are set up in Business Rules.
MIX NAME
setup
If you use InsertPlus and are inserting a mix in this publication, enter the mix name here, or press “*” to multi-select mixes. The insert combination code may be printed on the truck manifest and bundle tops (as governed by Business Rules) and be used to determine bundle sizes.
BUNDLE SIZE OPTION
predefined
You will need to assign a standard, minimum, and maximum size for your bundles. Indicate here whether you wish to define the bundle size by delivery method (carrier, motor, and single copy), AAM zone, AAM zone by delivery method (both AAM zone and delivery method), truck, edition, or insert mix. “Insert Mix” will be a choice only if you have InsertPlus. You can define bundle sizes for each insert combination of the mix(es) entered in Mix Name. If there will be routes with no inserts, enter a record with a mix name of “*”. Also, a sequence of “*” can be entered to specify the bundle size for all combinations of a mix that do not have an individual bundle size record.
PRINT KEY BUNDLES ONLY
predefined
Most routes will receive one odd bundle that is below or above the standard size. These are called “key” bundles. For example, if a route has 37 papers and the standard is 10, there could be 3 standard bundles and one key bundle of 7. Indicate here whether the bundle top should print only for the key bundle (always), print for all bundles (never) or print according to the route.
SEPARATE OPTION
predefined
Indicate whether hand-tie bundles tops should be printed separately at the end of the bundle run (hand-tie) or with the other bundles (none). A hand-tie bundle is a bundle below the minimum size that often must be hand-tied. If you use InsertPlus and have routes that require special handling (based on a preprint demographic defined in Business Rules), select special. Select both if you want special and hand-tie bundles to be printed at the end of the run.
ROUNDING MODEL
N/A
This field is active only for advance processing.
PRINT ROUTE LISTS PRINT ORDER
yes/no predefined
PRINT AD ZONES, PRINT INSERT LIST, PRINT INSERT MIX
—
These fields are used when generating bundle tops in InsertPlus. They are not used in Circulation.
INCLUDED PRODUCTS
setup
Specify any additional products to include on the truck manifest. Additional publications must have the same truck sequence and truck departure as the original publication.
COMBINE WITH FINAL ON
N/A
This field is active only for advance processing.
CREATE ONE FILE SET
yes/no
This field allows you to override the Business Rules settings that create separate bundle top and truck manifest files by publication and edition. When this checkbox is selected, one combined export file for all multi-pack editions is created (i.e., instead of separate files), and the remaining editions are exported as before (based on File Map setup). A Business Rule, Should the export file set for multi-pack products default to 'One File Set' in 'Enter Bundle Info'? (Route Processing section), allows you to set the default value for this checkbox.
Enter stacker information, bundle sizes, and messages for this run (see below).
Click OK to accept the bundle information.
After you have completed the above fields, you can enter stacker information on the Stacker tab.
To add stacker information, click the Modify Stacker button on the Stacker tab, complete the fields described below, and click OK.
STACKER OPTION STACKER FILE NAME
predefined setup
Identify the stacker interface option you use: • File Map—Select this option if you use a file-mapped stacker interface. Then, indicate the specific file map to use in the Stacker File Name field. • None—Select this option if you do not use a stacker interface. • A specific stacker—Any stacker equipment for which you have an Add On Activation record and for which there is a standard stacker format will appear in this combo box. Options may include Ferag, HALL, KANSA, Muller Martini, QUIP, WinLincs, etc. In the Stacker File Name field, you will need to specify a name for the stacker file that will be generated. The stacker type identified in Business Rules (What is the default count/stacker equipment? (Route Processing section)) will default in this field.
NUMBER OF CUTS NUMBER OF PAGES
integer(3)
If you are interfacing to the iDab stacker export, enter the number of bundles on a skid and the number of pages in a single newspaper (to measure thickness). Otherwise, leave these fields blank.
KEY PRODUCT CODE STANDARD PRODUCT CODE
open(1)
Enter the key and standard product codes, if desired. These are newspaper-defined one-digit codes that are used to differentiate between standard and key bundles in the stacker file.
Bundle sizes are defined on the Bundle Size tab. To begin entering bundle sizes, click Add and enter the standard, maximum, and minimum bundle sizes for each bundle size option. The “standard” you specify here is the standard size of your bundles. There will most likely be an odd-sized bundle among the standards, known as the key. The key will not be over the size specified as “maximum”. If the key is under the “minimum” size, the key bundle will be considered a “hand tie” and can be printed separately from the other bundle tops depending on Business Rules.
Bundle Size Option is taken from the main window.
Details allows you to enter a specific AAM zone, delivery method, truck, etc., depending on the bundle size option specified.
Standard is the standard bundle size.
Maximum is the maximum size of key bundles.
Minimum is the minimum size of key bundles, below which a bundle will be considered a hand-tie bundle.
Max Stack Bundle is used for stacker interfaces. It is the maximum size of a stack of newspapers coming off the stacker.
# Stacks/Bundle is the number of stacks coming off the stacker that comprise one bundle.
If you want to enter a message for all carriers or carriers of a specific draw type, click the Messages tab. Then, click Modify Messages and type the text in the appropriate field. Click OK when you have finished.
The "Copy Distribution Info Range" option can be used to copy, update, or delete multiple records depending on the date range passed for selected weekdays in the specified range.
Select the required Distribution Information from the Advance Distribution Information table and click on Copy Distribution Info Range button.
A pop-up window will be displayed to add, update, or delete records depending on the date range passed for selected weekdays in the specified range.
The truck manifest is a document produced during the publishing run that lists the drops on each truck. Drops may consist of routes, relay truck drops, or individual subscribers (“throwoffs”). The truck manifest shows how many bundles and papers go to each drop and in what order those drops will be made. This is used to help distribution personnel load trucks and the truck driver to keep track of the drops and number of bundles and papers for each drop on the truck. In addition, the truck manifest has the following features:
It is subtotalled by truck with grand totals by product.
A summary page that lists totals for the entire manifest is included at the end.
All routes that are bulked on the truck into one bundle top are listed separately, with a notation that the route is part of the truck bulk bundles.
All routes where the total draw is less than the minimum bundle size (“hand-tie” bundles) are flagged with the label defined in Business Rules.
If advance sections have been distributed for the publishing date, advance updraws or section detail can print with each drop on the manifest.
If an additional product (such as a TM product) is included with the publication on this publishing run, the product may also be printed on the truck manifest, indicating how many copies should be distributed to each route.
Business Rules in the Route Processing section determine, among other things, whether editions and TM products are printed on the truck manifest, the print order of the manifest (ascending or descending truck order), whether a blank column is included for recording the returns picked up by the driver, and the label that should appear on hand-tie bundles (so they can be identified among regular bundles).
Business Rules also govern whether truck manifest data is exported to an ASCII file (which allows you to import the manifest into word processing software and format it as you like). If so, the ASCII file will be exported to the /dti/exchange/cm directory
and be named manifest<processid>
, where <processid>
is the system ID of the process that generated the file. The advance truck manifest will be named advmanifest<processid>
. See Appendix B in the User Manual for the format of the export file.
Before printing bundle tops, you must first enter bundle size information (see Enter Bundle Info).
Select Truck Manifest from the Distribution menu to display the Truck Manifest window.
Select the product, edition, departure sequence and truck sequence for which to create the truck manifest by selecting the appropriate Process checkbox. If you use publishing groups (see A Note on Publishing Groups), the publishing group will also be listed. Note that edition will be “*” unless you have separate publishing runs at the edition level (see A Note on Editions for details).
Click Continue to produce the manifest.
Stacker machines are used by newspapers to stack papers into bundles for distribution to routes. Standard bundle sizes are entered in Circulation, and this information can be transferred to some stackers automatically.
The Stacker Interface option produces an ASCII file containing information necessary to the operation of the stacker. Circulation writes the ASCII file to in the directory /dti/exchange/cm
, using the file name entered in Enter Bundle Info (see Enter Bundle Info). Business Rules define the type of stacker for which the interface file is created. If you do not use the stacker interface, this question must be set to “None”.
Supported formats include: Ferag, Hall, iDab, Kansa, Muller Martini, Quip, Winlincs, and (using file mapping) Wamac. Another format may be defined for your site using a file map with a Usage of “Stacker” (see in the Setup Manual for more information).
Select Stacker Interface from the Distribution menu to display the Stacker Interface window.
Choose the product and edition for which you want to create the ASCII file by selecting the appropriate Process checkbox. Note that edition will be “*” unless you have separate publishing runs at the edition level (see A Note on Editions for details).
Click Continue to process and create the file. See Appendix B for the file format.
The ASCII file can then be transferred to the stacker machine.
Route labels may be required in order to deliver products to some locations, such as office buildings, nursing homes, hospitals, and schools. The labels contain the subscriber names and addresses.
Route Setup determines whether labels print for subscribers. The following table lists the possibilities.
Always
A label is printed for every subscriber.
Never
Labels are not printed for any subscriber.
Dwelling Type
If the dwelling type (in Dwelling Type Setup) specifies printing labels, then labels will be printed for all subscribers with that dwelling type.
Business Rules determine whether route labels are printed in truck-route-delivery sequence order, or truck-route-subscription ID order. If route labels are printed in delivery sequence order, the delivery (walk) sequence can be set up using Route Delivery Sequence. Route labels also use the mail label Business Rules settings (Mail Processing section) to determine formatting, such as the number of labels across one page and the width of the route label.
Select Route Labels from the Distribution menu to display the Route Labels window.
Select the product, edition, departure sequence and truck sequence for which to print route labels by selecting the appropriate Process checkbox. Note that edition will be “*” unless you have separate publishing runs at the edition level (see A Note on Editions for details).
If you want a separate route label file for each route, select the Additional Reports by Route checkbox.
Click Continue to produce the labels. For printing instructions, see the section on printing below.
Disable the print queue and load the label forms into the printer.
Configure the printer so that it cannot be interrupted by other print jobs.
When this has been done, press the spacebar to perform the forms alignment test, which checks for proper alignment of paper stock in the printer. The product name and date are printed during the test. When the number of test alignment forms specified in Alignments (in Report Configuration) have printed, form printing begins.
Note that the printer will be tied up for less time under the following conditions:
You specify that the print job is to be spooled to disk rather than printed immediately by entering “B” for background in When in the View & Print Options window.
Adequate disk space is available for a spooled file.
Once the forms have printed, a message that the printer is about to be released so that other jobs may print is displayed. Remove the special forms and reload the printer with normal paper.
A publication may have a separate publishing run for each edition (see A Note on Editions). In this situation, a version of the Daily Draw Worksheet can be run for each edition—known as the Edition Daily Draw Worksheet. This report has the same format as the Daily Draw Worksheet but is at the edition level.
Note: This option is only available to publishing runs open for a specific edition.
Select Edition Drawsheet from the Distribution menu to display the Edition Daily Draw Worksheet window.
Choose the product/delivery method/edition(s) for which you would like to run the report by selecting the Process checkbox.
Click Continue to process the report. It will have the same format as the Daily Draw Worksheet, but the edition is displayed in the heading.
Office pay status cards serve to remind carriers not to collect from subscribers who are office pay. A card is printed for an office pay, paid complimentary, or unpaid complimentary subscriber if the subscriber:
Has just started
Has had other transaction activity that changed the expiration date
Has moved to a different address
Has been assigned to a different route
Is being serviced via a changed delivery schedule
Card dimensions are defined in the Reports section of Business Rules. Because Circulation will print the product, route, delivery schedule, expire date, name, address, and telephone number, the minimum size of the status card is 9 lines (or 1½ inches). If a subscription is delivered by multiple routes, a card will be printed for each route that delivers it.
To print status cards for all office pay subscribers, go to Reports | Account | Status Cards.
Carrier collection cards alert carriers to new carrier collect subscribers. Cards are printed for carrier collect subscribers who started or switched to carrier collect within the date range entered. If a subscription is delivered by multiple routes, a card is printed for each route that delivers it.
To print collection cards for all collect subscribers, use Reports | Account | Collection Cards. Card dimensions are defined in Business Rules under the section “Reports”.
You can print these cards as often as you wish.
Select Status/Collect Cards from the Distribution menu to display the Status and Collection Cards Processing window.
Select the appropriate checkbox for the product, edition, departure sequence and truck sequence for which to print status cards. Note that edition will be “*” unless you have separate publishing runs at the edition level (see A Note on Editions for details).
Click Modify Criteria.
Complete the following fields.
PRODUCT
display
The product is displayed.
START DATE END DATE
date
Enter a start date and end date for transactions that should be included. For example, if an office pay new start falls within the dates specified here, a card will be printed for that subscriber
CARD TYPE
predefined
Enter Office Pay Status, Collection, or Both.
ADDITIONAL CARDS
yes/no
If you select this checkbox, you will have the option of entering one or more additional routes or subscription IDs. All of the available cards will be printed for the selected route(s) and/or subscription(s).
ROUTE
setup
Enter the route for which you want to produce additional cards or “*” to multi-select.
SUBSCRIPTION
open
Enter the subscription for which you want to produce additional cards or “*” to multi-select.
REPORT TYPE
predefined
Select Export or Print Cards. If you selected “Both” in CARD TYPE, then “Export” is the only option. Note: If you select “Export”, the remaining fields will be required. If you select “Print Cards”, the remaining fields will not be active.
FILE FORMAT
setup
Enter a user-defined format that has been set up in File Map.
FILE NAME
open (30)
Enter the name of the file that will be produced in the /dti/exchange/cm directory.
FILE OPTION
predefined
Select append to add this information to the existing file, or replace to replace the existing file.
Click OK and then Continue to produce the cards. See Printing Forms for information about how to load forms and configure your printer for this task.
The bundle top can include the following items (an asterisk* indicates items controlled by the Business Rules):
The start, stop, restart, and vacation pack messages include the subscriber name and address, delivery schedule, billing method, number of copies, and expiration date. Also included are general messages entered using Enter Bundle Info (see ).
Returns, complaints, etc. that were entered before the publishing run (and have not previously been printed) will be printed on the bundle tops. Messages can be printed on several consecutive days, but after the first day, a “reminder” heading will accompany them. Invoices can be flagged to print on bundle tops for a publishing run using the Invoices On Bundle option in Accounting.
The expire date prints with subscriber transaction messages.
The restart date is printed when printing stop messages.
Bundle tops should always be printed on the same side of the paper.
Bundle top messages should be printed on the same page as the other information.
The truck, standard bundle size and number of standards are displayed in large print.
A banner page is printed for each truck.
The number of starts a route must have on the next publishing day before future start messages are printed.
The day on which complaints, reminder messages, and repeat messages should be printed.
The print order for the bundle tops (ascending truck, descending truck, descending drop, edition or depot).
Whether bundle tops for relay trucks are printed in drop order or after the other bundles on the parent truck. Also, if relay bundles are bulked, whether relay parent bundle tops should reflect the combined actual draw of the relays or the bulked draw.
Sorting for bundle tops is chiefly controlled by the departure sequence and truck sequence, which can be ascending or descending, based on Business Rules. The table below is an example of the order in which bundle tops might be printed. The numbers in the right column represent routes, each of which will have one or more bundle tops printed (depending on whether they were set up to be printed for standard bundles or only keys). Notice that bundle tops for hand-tie bundles and bulk bundles are printed at the end. Truck bulk bundles (which list all bulked routes on the truck) are identified with a “B”.
A key bundle top is used for the bundle containing the odd number of papers. For example, if a route has 50 papers and the standard bundle size is 20, the route would have two bundles of 20 and one key of 10. Typically, route messages are printed only on the key bundle tops.
Some trucks have bulk bundle tops for some or all routes. This means that the papers are bulked together rather than in individual bundles. If a route has messages, they are printed on a special bundle top for the route known as a bulk key.
When a route is added to a truck sequence, it can be flagged as bulk. The Print Key Bundle Only flag is also set (which indicates whether standard and key bundle tops, or only key bundle tops, should be printed). There is also a Print Key Bundles Only field in Enter Bundle Info, which can be set to “route”, “always” or “never”. If “never” is selected, both key and standard bundles will be printed. The Print Option field in Truck Departure setup determines whether keys or standards are printed first. The following table lists the bundle tops will be printed for a route based on the bulk and Print Key Only settings.
Select Bundle Tops from the Distribution menu to display the Bundle Tops window.
Click Continue to print the bundle tops.
The Daily Draw worksheet can be used as a tool in assessing short term draw. For example, you could print the estimated draw for five days following your publishing date, and use these figures when estimating inserts and other supplies. You can also use the report to quickly scan the current draws for each route.
When the Daily Draw Worksheet prints the future draw, it uses draw figures from the same day of the previous week. For example, if your publishing day was a Wednesday and the Daily Draw Worksheet listed Thursday’s estimated draw, it would use the draw figures from the previous Thursday. Note that the future draw estimates do not take unprocessed future transactions into account.
Business Rules determine whether sorting should be done by AAM column or district and how many days in the past and future should be included. Business Rules also determine whether routes that deliver both publications in a combined publication should be reported as a single line item. If so, the sorting will be by route rather than district and no AAM percentages will be displayed.
This report can be run as many times as you wish.
Select Daily Draw Worksheet from the Distribution menu to display the Daily Draw Worksheet window.
Choose the product/delivery method/edition(s) for which you would like to run the report by selecting the Process checkbox.
Click Continue to process the report.
If you use the option to round advance draw for bulk routes, you can export rounded draw figures with this option. Both the rounded draw and original advance draw figures are exported for each truck or route group that had rounding. With this information, the export file can be imported into other software programs to perform reconciliation reporting.
Adv Reconciliation exports draw rounding information to the /dti/exchange/cm
directory. The file name will be recon<publ><mmddyyyy>
, where <publ>
is the ID of the publication and <mmddyyyy>
is the date of the export. For example, if Adv Reconciliation exported a file for the Times on the 6th of March, 2008, the name would be “reconTimes03062008”. The export file format is given in Appendix B of the User Manual.
Select Adv Reconciliation from the Distribution menu to display the Advance Reconciliation Draw window.
Choose the products and run dates for which to round draw by selecting the appropriate Process checkbox.
Click Continue to export.
Use this option to print receipts for single copy routes that show the number of papers dropped, by product. Each receipt also has a section that shows the number of returns collected. Two receipts are printed, side-by-side, for each route. A sample is shown below.
Each single copy type that will use this option must be identified in Setup. On the Single Copy Type window (Setup | Distribution | Route | Single Copy Type), there is a field, Print Receipt?, that must be set to “yes” to allow receipts to be printed.
Select Single Copy Receipts from the Distribution menu to display the Single Copy Receipts window.
Choose a product and edition by selecting the appropriate Process checkbox.
Click Continue to print the receipts.
This field will default and cannot be changed. Note: This field is replaced by the Paper Section field in the version of this program.
Select this checkbox if you want a route delivery list to be printed on the route’s bundle top. The PRINT ORDER field will become available to select the order in which the route list should be sorted. The possible choices are address, postal route, and delivery sequence order. If a TM product or other publication is delivered with the main publication, it will appear in a separate column. See for more information on route delivery lists.
Route labels should be considered forms if they are printed on special paper. If so, the Is A Form flag should be set to “y” for route labels in . When form printing occurs, a message will be displayed that control of the printer is about to be turned over for this purpose. Ask your system administrator to:
Note: Enabling/disabling printers is a security issue (see in the Setup Manual).
Before printing bundle tops, you must first enter bundle size information (see ).
Choose the product, edition, departure sequence and truck sequence for which you want to print bundle tops by selecting the appropriate Process checkbox. If you use publishing groups (see ), the publishing group will also be listed. Note that edition will be “*” unless you have separate publishing runs at the edition level (see for details).
Truck 15
23, 27, 31, 24, 26, 33, B
Truck 07
44, 52, 54, 39, 03, B
Truck 12
02, 05, 06, 07, 10, B
…Relay Truck 12a
65, 75, 71, B
Truck 22
37, 38, 34, 32, 77, B
Truck 19
17, 16, 18, 12, B
…Relay Truck 19a
25
......Relay Truck RR
48, 43, 45, 37, B
Truck 02
61, 62, 63, 66, B
Hand-tie bundles
All hand-tie bundle tops in truck and drop order
Truck Bulk
Truck-wide bundle listing bulk routes and draw
Messages for bulk
Bundle tops for all bulk routes that have messages
Bulk with key option
Bundle tops for all bulk routes set up to print keys
Insert exception
Bundle tops for routes with insert combinations that are below the minimum defined in Business Rules (InsertPlus sites only)
Route
Y
Y
One bulk label for all bulk draw on a truck (no standards). One key label for each route.
Route
N
Y
Bulk labels for all standard bulk bundles on a truck. One bulk key label for the truck.
Route
Y
N
Key bundle for each route, no standards.
Route
N
N
Standard bundles and key bundle for each route.
Always
Y
Y
One bulk label for all bulk draw on a truck (no standards). One key label for each route (no standards).
Always
N
Y
One bulk label for all bulk draw on a truck (no standards). One bulk key label for the truck.
Always
Y
N
Key bundle for each route, no standards.
Always
N
N
Standard bundles and key bundle for each route.
Never
Y
Y
Bulk labels for all standard bulk bundles on a truck. Standard bundles and key bundle for each route.
Never
N
Y
Bulk labels for all standard bulk bundles on a truck. One bulk key label for the truck.
Never
Y
N
Standard bundles and key bundle for each route.
Never
N
N
Standard bundles and key bundle for each route.
route
draw adjustments*
future starts (for next pub day)
delivery schedule messages
carrier name
invoices*
previous delivery messages
messages to carrier
carrier phone #*
number of papers to drop
delivery placement
vacation pack messages*
subscriber phone #*
number of bundles to drop
draw comparison*
TM products delivered with paper*
returns*
drop location
drop sequence
inserts and mix (InsertPlus required)*
complaints*
truck number
publishing date
route list (based on Enter Bundle Info)
account payments*
changes to expire dates
subscribers going into grace*
advance updraw*
subscriber payments*
edition
start/stop/restart messages
advance section detail*
draw changes
bonus day messages