GNM_RCS_Chart_of_Accounts_Sales_TS

• 1. .Introduction

     1. Purpose

The document GNM_RCS_Chart_of_Accounts_FS.docx is the functional specification that describes what business functions RCS supports in relation to coding of financial transactions. The Chart of Accounts itself is defined in the Finance spreadsheet found at http://spike/content/513.

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 Chart of Accounts as it is implemented in RCS/SLM for sales of licences i.e. accounts receivable. A separate document deals with all how the Chart of Accounts is implemented in RCS for accounts payable (and syndication contracts revenue).

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. .Chart of Accounts definition

A syndication housekeeping screen is used to maintain the Chart of Accounts data for licence requests processed in SLM.

• 1. Historical context

For historical reasons there are two models of the chart of accounts in RCS/SLM. The one used mainly for expenditure in RCS has always been different from that used for sales. By way of explanation here is a brief history:

• • Initially RCS was developed with a cost code that were known at the time as Impersonal Codes – these were what the old AS400 finance system operated with;

  • RCS was soon upgraded to use 6-character short codes that mapped to the Impersonal codes. The codes, such as HOMCOM (Home desk Commissions), were intended to be more intuitive for the users;

  • Then Oracle EBS was implemented and RCS’s 6-character codes were remapped to the Oracle 8-segment accounting code combinations;

  • Then SLM was developed but it was necessary to offer more control to the users that just a list of 6-character codes so a simplistic 8-segment model was defined. The focus was on as many values as possible being correctly defaulted into the screen fields;

  • Later the RCS model was completely overhauled after Finance restructured the Chart of Accounts. The 6 letter short codes were out and the full 8-segment coding was in. The code hierarchies were fully mapped from the master document, and users granted permissions on them; and

  • Syndication contracts were added after that, whereupon it was decided the full RCS model should be adopted rather than the more simplistic SLM model.

• 1. The chart of accounts screen

The screen is accessed from this menu option: Syndication → AR interface → Chart of Accounts

This menu option opens screen rcs_csrs_010_pc.fmb.

Unlike the RCS screen this is not a tab canvas, but instead the 8 segments are listed across the top of the screen, and below that are the codes that relate to the segment highlighted at the top.

Segments 1 to 6 all share the same properties, as shown above i.e.

• • Text default

  • Indicates if the code is used as the default when licencing text content

  • Images default

  • Indicates if the code is used as the default when licencing image content

  • Audio default

  • Indicates if the code is used as the default when licencing audio content

  • Video default

  • Indicates if the code is used as the default when licencing video content

.

Segment 7 is for Analysis 2 and has no specific properties, as shown below:

Segment 8 is for Project codes and has the same properties as segments 1-6, along with a 3rd party commission fee property, as show below:

• 1. .Defaults

To reduce the burden on the syndication sales executives of entering the segment values for every request special attention has been given to Analysis 2 codes and Project codes.

• 1. Default Analysis 2 codes

The Customers screen enforces a default Analysis 2 code to be set for every customer. This code is then applied to all requests/licences for that customer, but can be changed if necessary.

The screen is accessed from this menu option: Syndication → Customers

This menu option opens screen rcs_cust_010_pc.fmb, running in a mode that means appears as shown below.

• 1. Default project codes

The Default project codes screen enables the RCS/SLM Administrator to define which project code is to be used by default for sales of content published in each GNM publication.

The screen is accessed from this menu option: Syndication → AR interface → Default project codes

This menu option opens screen rcs_pbln_010_pc.fmb, running in a mode that means appears as shown below.

End of Document