Processing

Applies to Single Copy versions 3.6 and higher

Sales data from Scan-based Trading Partners must be added to the Syncronex Single Copy system so that SBT analysis can take place. This is most commonly done through the import of SBT data files from the trading partners. Sales data can also be added manually through the Maintain Sales option if necessary.

The import files must contain data in a tabular format, with consistent rows and columns, for the process to import the data successfully.  Each row in an import file must contain, at a minimum, an account, a publication, a sale date, and a sale quantity.  A simple spreadsheet (converted to a Comma Separated Value or CSV file) is all the system needs to import the sales data.  For example:

When converted into a CSV file, the data will look like this:

Account,Publication,Date,Qty Sold,Unit Cost,Amount
1000,P01,5/28/2012,3,1.00,3.00
1000,P02,5/28/2012,1,0.75,0.75
1000,P01,5/29/2012,4,1.00,4.00
1000,P02,5/29/2012,3,0.75,2.25
2000,P01,5/28/2012,5,1.00,5.00
2000,P02,5/28/2012,4,0.75,3.00

Using configuration and mapping, Syncronex can support several different formats, including Nexxus and iControl.  See the articles under Configuration for more information.

The Scan-based Trading Import process is a background process that extracts the data from the uploaded file and adds it to the Syncronex system.

• The import process processes all uploaded files that have been marked as ready for processing.  This includes new files that have been uploaded and not yet processed as well as files that have previously processed with errors and that are being reprocessed.
• The import process begins by attempting to parse the uploaded files.  During parsing, the process uses the import configuration files to determine where the data is located in the files.  If there are any problems in the configuration file, or if the file cannot be parsed according to the settings found in the configuration file, the file will be marked as having a parsing error.
• If parsing is successful, the import process moves on to the mapping cycle.  During mapping, the process attempts to map the account, publication, and sale date in the import file to the correct account, publication, and pub date in the Single Copy system.  If the file cannot be mapped, the file will be marked as having a mapping error.
• If mapping is successful, the import process for that file is complete.

During the upload process, the system attempts to determine the correct publication date based on the sale date that is provided in the import file.  The system looks at the sale date, and assigns the sale to the most current publication date that for which a publication match is found.  Consider some examples:

• Suppose that you are using publication mapping, and pub P01 is mapped to the publication code GAZT in the Single Copy system.  GAZT is a daily title.  If a sale is received for 6/1, then the sale will be applied to the 6/1 publication.
• In a case where P02 is mapped to the publication code TGLO in the Single Copy system, with TGLO being a Sunday-only title, if a sale is received for 6/1 (a Friday), the sale will be applied to the 5/27 publication (the previous Sunday).
• Suppose that you are using bar codes to map the publications.  In the case of a newspaper like USA Today, each day of the week has a different bar code.  Let's assume that Monday has a bar code of 50055, Tuesday has a bar code of 50056 and Wednesday has a bar code of 50057.  If a sale is received dated 5/30 (a Wednesday) with a bar code of 50055, the sale will be applied to 5/28 (a Monday) because the Monday bar code was received.