GNM_SLM_Sales_Contracts_Term_Sheets_TS

• 1. .Introduction

     1. Purpose

The document GNM_SLM_Sales_Contracts_FS.docx is the functional specification that describes what business functions SLM supports in relation to syndication redistribution contracts.

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 term sheets generated for redistribution contracts. The contract entry and the on-going contract processing are covered in separate documents.

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 contracts term sheets

     1. Templates

The redistribution contract term sheets are based on a template that defines all of the clauses into which data can be substituted. The template is described more fully in the relevant syndication contract configuration document and so is not repeated here.

• 1. Report output

The term sheet is produced by an Oracle Report called rcs_scon_010.rdf

This report can be invoked by the user from any of the Syndication contract screens. When generated from the screen the contract appears in a new browser window as a PDF document.

The Oracle report can also be invoked by Oracle’s event driven processing technique, described more fully in the core technical documentation. In this instance a database job identifies contracts that are ready to be issued and publishes them. An email meta data file is written after the report is produced, which Fingerpost software processes to generate the outbound email attaching the generated PDF. The attachment is also loaded into the database for future reference during this process.

An example of a generated term sheet is given below, including the covering letter issued in the PDF. The 2nd page is deliberately blank (not shown) so that if the customer prints the contract double-sided then the letter will remain separate from the contract.

The report is complex, but uses techniques already described in the software techniques documentation, and so this is not repeated here.

The customer is asked to sign and return the document, whereupon GNM will countersign it, save it in the database, and issue a copy to the customer again.

Documents can be dropped into a folder on the server, and, provided the document name starts with a relevant RCS (including SLM) unique reference, they are loaded into the database and stored against that reference.

End of Document