GNM_SLM_AR_Interfaces_Configuration_TS

• 1. .Introduction

     1. Purpose

The document GNM_SLM_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 configuration options that support the Oracle AR interfaces: the relevant housekeeping screens. Separate documents deal with the actual AR interface and 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. .Oracle AR configuration

     1. Customer statuses

Customers setup in SLM can only have statuses that are valid in Oracle AR, so that the data in the two systems can be kept synchronised. SLM has a list of Customer statuses in a table called AR_ACCOUNT_ACTIVE_STATUSES.

The Customer statuses screen, which shows the available status codes, is accessed from this menu option: Syndication → AR Interfaces → Customer statuses

This opens an Oracle Form named rcs_aaas_010_pc.fmb

If the Prevent new requests? checkbox is ticked against a customer status then it will not be possible to enter new licence requests in SLM for Customers with that customer status. Customers in this situation are clearly highlighted in SLM.

If a new customer status is added in Oracle AR it must also be created in this screen in SLM. This is a manual process as it happens so infrequently.

.

• 1. Account statuses

Customers setup in SLM can only have account statuses that are valid in Oracle AR, so that the data in the two systems can be kept synchronised. SLM has a list of these account statuses in a table called AR_ACCOUNT_STATUSES.

The Account statuses screen, which shows the available account status codes, is accessed from this menu option: Syndication → AR Interfaces → Account statuses

This opens an Oracle Form named rcs_aast_010_pc.fmb

If the Alert in new requests? checkbox is ticked against an account status then a users get a warning if they enter a new licence request in SLM for a customer with that account status, but they will be allowed to continue.

If the Prevent new requests? checkbox is ticked against an account status then it will not be possible to enter new licence requests in SLM for Customers with that account status.

Customers in either situation are clearly highlighted in SLM.

If a new account status is added in Oracle AR it must also be created in this screen in SLM. This is a manual process as it happens so infrequently.

.

• 1. Address/contact statuses

Customer billing addresses setup in SLM can only have statuses that are valid in Oracle AR, so that the data in the two systems can be kept synchronised. SLM has a list of address/contact statuses in a table called AR_SITE_ACTIVE_STATUSES.

The Address/contact(site) statuses screen, which shows the available status codes, is accessed from this menu option: Syndication → AR Interfaces → Address/contact statuses

This opens an Oracle Form named rcs_asas_010_pc.fmb

If the Prevent new requests? checkbox is ticked against an address/contact status then it will not be possible to enter new licence requests in SLM for Customers with that address/site status. Customers in this situation are clearly highlighted in SLM.

If a new address/contact status is added in Oracle AR it must also be created in this screen in SLM. This is a manual process as it happens so infrequently.

.

• 1. Agency discount codes

Customers setup in SLM can be assigned an agency discount code that must match the codes available in Oracle AR, so that the data in the two systems can be kept synchronised. SLM has a list of Agency discount codes in a table called AR_AGENCY_DISCOUNT_CODES.

The Agency discount codes screen, which shows the available discount codes, is accessed from this menu option: Syndication → AR Interfaces → Agency discount codes

This opens an Oracle Form named rcs_aadc_010_pc.fmb

If a new agency discount code is added in Oracle AR it must also be created in this screen in SLM. This is a manual process as it happens so infrequently.

.

• 1. VAT codes

Customers setup in SLM can be assigned a VAT code that must match the VAT codes available in Oracle AR, so that the data in the two systems can be kept synchronised. SLM has a list of VAT codes in a table called VAT_CODES.

The VAT codes screen, which shows the available codes, is accessed from this menu option: Syndication → AR Interfaces → VAT codes

This opens an Oracle Form named rcs_vcod_010_pc.fmb

If a new VAT code is added in Oracle AR it must also be created in this screen in SLM. This is a manual process as it happens so infrequently.

End of Document