Applications‎ > ‎

Miscellaneous Invoices

Overview


BT/Infonet Miscellaneous Invoices and Management System (MIMAS) was designed as an Oracle Financials 11.5.7 Application Foundation application. For Infonet, a key operational requirement was to invoice their affiliate network and intercompany business units, to integrate the Accounts Receivable and Accounts Payable transactions to BT's intercompany application and to integrate the accounting transactions with the General Ledger.

MIMAS was developed by the Infonet team consisting of myself, lead business analyst, accounting lead, two Oracle Forms and Reports developers, a technical writer and other staff as necessary. I designed the application and the underlying relational data model, I developed the backend PL/SQL dynamic accounting procedure and many of the online data validation triggers, and I managed the development, testing, setup, data migration, documentation and production rollout. MIMAS took about 6 months to develop and was in use for less than one year.
MIMAS Key Requirements
  • Automate Intercompany Invoices and Accruals
  • Convenient, familiar online data entry
  • Leverage Oracle Financials infrastructure, security
  • Provide standardized accounting templates
  • Maintain standardized invoicing items
  • Interface AR and AP to the intercompany/settlement application
  • Interface accounting journals to the core Financial system (Oracle EBS 11i)
  • Provide ad-hoc reporting

Sample Reference Data Maintenance


The entire set of application reference data had corresponding online maintenance screens. Overall, there were over 25 maintenance screens, defining all aspects of the application: GFRs, Entities, Entity Contacts, TCAs, OUCs, Projects, Countries, Tax Codes, Intercompany Periods, Transaction Types, Entity Types, Line Types, Accounting Types, etc. These are a few of the online maintenance screens.


Accounting Templates


Accounting Templates defined the General Ledger journal lines and the individual segment values. The Accounting Templates maintenance forms defined the journal, journal lines and the segment construction rules. The dynamic accounting generator (custom PL/SQL procedure) would build the proper journal lines usign this definition. Depending on the type of service offered and relationship between home and away entities, the accounting templates would consist of simple two line DR Receivable and CR Transfer Out or be as complex as 6 line journal transaction!


Online Invoice


A key requirement was to enter the transactions via the Oracle EBS environment. The users were familiar with Oracle. MIMAS supported direct entry of invoices or cloning invoices from an invoice transaction library. Here is an example of an invoice with the resulting dynamically constructed accounting.


Sales Invoice Report


MIMAS included as set of standard reports, run from Oracle's concurrent manager. The reports included reference data listing, transaction header/line detail, accounting detail and interface status. Here's an example of the sales invoice report.


One of the design goals was for MIMAS to be adopted as a BT core application and used throughout BT Americas and possible other BT countries. Unfortunatly, this goal was never realized. Attempts were made to leverage Oracle EBS R12 EGIS Intercompany module; however, that effort failed due to the complexity of integrating the transactions. As a result, today, intercompany transactions are processed manually using MS Excel worksheets.