Developing an Application Express (ApEx) application for them to enable them to load and manage many different types of marketing campaign.
This is being developed in version 3.1.1 of ApEx and PL/SQL.

A security cleared contract designing and developing the 'Bowman Information Portal' to display complex information on Tri-Service Bowman communications equipment from many disparate sources.
Originally coded in Application Express 2.2, but recoded in 3.1 when it became available to us. Since installed on my laptop, thus available for demonstration, using Oracle 11g and ApEx 3.1.1 and non-restricted test data.
This requirement included:
 The development of over 25 ApEx reports linking to each other via hyperlinks where required. Most were recoded to make use of the Interactive Reports which became available in 3.1.
 One report showed data on individual parts and displayed images of the equipment in question.
 Two showed data accuracy reports with percentages of invalid and blank stock numbers and drill downs to detailed reports. One showed the numbers of invalid or blank items and the other the associated quantities.
 The provision of a PDF report coded in Oracle Reports to duplicate and populate an existing Army form, this was called via a link from a record on one of the reports decribed above.
 The provision of Administration functions which included:
 The ability to upload data from sixteen user supplied flat files using Oracle External Table and populate other Oracle tables using processed data from them.
 The creation and management of Administration Users, using Oracle Internet Directory (OID), Single Sign On (SSO) and Discoverer Users.
 The ability to upload documents, e.g. Word, Excel or PDF docs, on an ad-hoc basis which would then be available for users to open or download.
 The facility to add, remove and change menu items which provide links to external documents, applications and websites.
 The ability to upload images from a PC and associate them with appropriate string descriptions held in one of the tables.
 The creation and editing of Contacts, Glossary and FAQ entries.

Attention was paid to ensuring the performance of the code and ease of use via validations and help text.
A Technical Specification, Users Guide and Installation Guide were produced as well as input back into the Functional Specification.
I was solely responsible for the coding of the project reporting to the Project Manager and liaising with users and the tester.

Following the successful completion of the Bowman Information Portal, I was tasked with producing a simple 'template' application which incorporated
a number of the elements from Bowman but also included more complex User handling, allowing for 3 levels of users, Administrators, Superusers and Users.
It also had the facility for individual users to select a different look for the site using colours and logos from the three services plus a tri-service colour scheme

Responsible for the design and implementation of an automatic Dunning system. It ran each working day and identified bookings, which fitted the defined Dunning criteria taking account of weekends and bank holidays. The users needed to be able to view and query this data and to exclude individual bookings from the Dunning process if desired. The Dunning reports had to be distributed to individual agents within each Dunning period and also to send a summary email to a contact within Carnival UK.
The data was extracted using code stored in a Pl/Sql package. I chose to use Oracle Application Express (formerly HTMLDB) for the user application, and Oracle Reports, running on Oracle Application Server, to create and distribute the reports. The distribution mechanism used XML files containing Reports variables.
The ApEx application allowed users to query Dunning records by different Dunning periods, Brand, Status or whether the booking was cancelled. Searching on individual account code or booking reference was also possible. To cater for weekends and bank holidays the Dunning period would be automatically extended and this was shown on a non-updateable field. For those with administrative access extra buttons were shown to allow access to the ‘Administer Bank Holidays’ and ‘Administer Phones & Buckets’ functions.
Another application was produced in ApEx to enable the UAT staff to enter meaningful test data easily and to multiply it up to cover several different scenarios.

Abacus: A system for the rapid application of cheque payments to Polar (the reservations system) bookings.
Responsible to the production of a Pl/Sql package to provide validation and password handling functions and procedures which were then called by a Delphi front-end written by a colleague. One of the validation functions used an existing web service to check the amounts for a particular booking by utilising an XML message.

SPS: The SPS system allows for cheque payment application to Polar.
Responsible for the creation SPS interfaces. These use unix scripts, a PL/Sql package plus SQL*Loader and appropriate Oracle objects to achieve the following:
Polling for a Polar file and loading into SPS tables, if validation is passed.
Renaming and forwarding of this file via ftp to NTL who handle the requesting of payments from the agents.
Receiving of the NTL file showing amounts paid and those records in dispute.
Validation of the NTL file data and updating of SPS tables when a form button is pressed.
Creation of file to ftp back to Polar including additional ‘Recovery’ records when a form button is pressed.

Oracle Financials:Amended Cheque and Remittance printing report. Modified PO Approval Workflow. Various bugfix and reports modifications