GNM_SLM_Customer_Report_TS

• 1. .Introduction

     1. Purpose

The document GNM_SLM_Customer_Management_FS.docx is the functional specification that describes what features RCS has in relation to syndication customers.

This document is one of a set of technical specifications that provide details of how those functions are implemented in RCS.

• 1. Scope

This document focusses on the Customer requests report in SLM. Other documents describe how customer data is maintained as how to search for a customer.

This document is intended as a high-level technical document outlining how the relevant business functions are implemented in terms of software modules.

Importantly, this document does not aim to provide the level of detail that would be required in a programming specification in areas such as program structure, detailed business rules, data integrity, validation, locking considerations, data security, and calls to/from other software modules, performance considerations, and so forth.

For details of program logic and coding, the reader should refer to the program files themselves.

• 1. .Customer requests report

This report lists customers and their requests over a specified period.

• 1. Requesting the report

The report is run from this menu option: Syndication → Customer requests report

This menu option opens screen rcs_reports_240_pc.fmb which allows the user to control what should be included in the report.

The user can enter the Customer and Publication or leave them blank to report on all of them.

The format can also be selected as well as the range of financial periods to report on.

Finally the report can be restricted to show only those requests that resulted in licences being issued.

On pressing “Finish” a request for this report is saved to the REPORT_REQUESTS table, and this is processed later asynchronously by a database job.

• 1. Execution

This report output file is produced by a database job that processes new report requests. The database job executes this package procedure:

reports.process_outstanding_requests

The above packaged procedure executes another package procedure to produce the report:

rcs_ordr_010.run_report

In turn this packaged procedure writes two files to the fip folders (Fingerpost), one being the csv output for the report itself, and the other containing meta data for an email. Fingerpost tools (asynchronously again) find these files and generate an email to the requestor attaching the report.

• 1. Report output

The report output file lists the data in comma separated values (csv) format, which are emailed to the requestor of the report. The file contains these columns:

Customer, Order, Publication, Published on, Book, Section, Page, Spot/Perm, Format, Contributor, Headline/Caption, Licence date, Status, Contact details, Cancellation reason, On hold?, Hold reason, Notes, Linked to content?, Purchase order, Customer product, Circulation, Page count, RRP, RRP currency, Usage, No of words wanted, Print?, Scope, Print status, Internet?, Scope, Photocopy?, Scope, Archive?, Scope, CDROM?, Scope, DVD?, Scope, Film?, Scope, TV?, Transmissions, Scope, Radio?, Transmissions, Scope, Drama?, Scope, Other rights, Territory, Exclusive, Copyright notice, Internet expires, Internet renewal sent?, Prior approval needed?, Prior approval given, Legal check?, Fee notes, Service fee, Licence fee, Revenue split, Invoice raised?, Invoice raised on, Sent to AR?, Sent to AR on, Created by, Created on, Modified by, Modified on

End of Document