GNM_SLM_Order_Reports_TS

• 1. .Introduction

     1. Purpose

The document GNM_SLM_Orders_FS.docx is the functional specification that describes what features RCS has in relation to syndication requests and orders.

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 Orders reports in SLM. Other documents describe how requests / orders are entered and subsequently processed, including the issuing of letters and licences. The Customer requests report is also documented separately.

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. .Sales summary report

The Sales summary reports is a summary of sales made in a user-selected financial period.

• 1. Requesting the report

The report, also known as the Syndication monthly sales report, is run from this menu option: Syndication → Sales summary report

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

The user can only enter the financial year to be reported on.

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_100.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:

Publication, Format, Sale type, Nat. a/c, Apr-13, May-13, Jun-13, Jul-13, Aug-13, Sep-13, Oct-13, Nov-13, Dec-13, Jan-14, Feb-14, Mar-14

The last 12 columns reflect the sales totals in the 12 periods within the requested financial year.

• 1. .Delayed royalties report

The delayed royalties report lists royalty payments not yet been paid to the original contributor(s).

• 1. Requesting the report

The report is run from this menu option: Syndication → Delayed royalties report

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

The user can only enter to Cost centre code to report on or leave it blank to report on all cost centres they have access to.

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_orfe_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:

Cost centre, Product, Payee, Order, Royalty, Invoice no, Due date, Description, Net, Currency, Created by

End of Document