GNM_RCS_Interface_Reports_TS

• 1. .Introduction

     1. Purpose

The document GNM_RCS_System_Interfaces_FS.docx is the functional specification that describes what business functions RCS supports in relation to its interfaces with other GNM systems as well as any external integration.

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 Reports available for the payables interfaces. Separate documents deal with all other inter-system interfaces that pass data between RCS/SLM and other systems.

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. .Interface reports

     1. Unpaid transactions report

        1. Requesting the report

The report is run from this menu option: Housekeeping → Interface reports → Unpaid AP transactions report

This menu option opens screen rcs_reports_070_pc.fmb.

• 1. Report process

The software that is executed to produce the report is a package procedure called:

rcs_stra_010.run_report

This report lists all payment instructions where RCS has not received any information about a payment being made.

• 1. Report output

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

Contributor, Payee, Staff?, Joined staff, Left staff, Invoice no, Net, Currency, RCS trx id, PRN, CRN, ARN, Request, Royalty, Cost centre, Product, N/C, Sent as, File/Msg, Sent to AP

.

• 1. Payment mismatch reports

     1. Requesting the report

The report is run from this menu option: Housekeeping → Interface reports → Payment mismatch report

This menu option opens screen rcs_reports_090_pc.fmb.

The user can choose either or both of the Oracle payment mismatches or Payroll payment mismatches reports. By pressing the “Next” button they can enter further options including an optional Cost Centre (with LOV available as shown below) and the Period they want to report on.

Pressing “Finish” saves the request to the REPORT_REQUESTS table. The request is picked up by an asynchronous database job that processes the request and emails the report to the requestor.

• 1. Report process

The software that is executed to produce the report is a package procedure.

For the Oracle AP payment mismatches:

rcs_stra_020.run_report

For the Oracle Payroll payment mismatches:

rcs_stra_030.run_report

Each report lists all payment instructions where the amount paid was not equal to the amount on the instruction, taking into account the fact that VAT may have been added in Oracle, and also allowing a tolerance of plus or minus one penny.

• 1. Report output

The report output files list the data in comma separated values (csv) format and are emailed to the requestor of the report. The files contain these columns:

For the Oracle AP payment mismatches:

Sent as, File/Msg, Payee, Contributor, Invoice no, Net, Currency, Paid on, Paid amount, Paid currency, RCS trx id, PRN, CRN, ARN, Cost centre, Product

For the Oracle Payroll payment mismatches:

File, Payee, Contributor, Invoice no, Net, Currency, Paid on, Paid amount, Paid currency, RCS trx id, PRN, CRN, ARN, Cost centre, Product

End of Document