| |
|
|
|
4. All Present and Correct (APAC) |
| |
|
|
Client
|
British Telecom, U.K.
|
| |
|
|
Period
|
December 1999 - Febraury 2000.
|
| |
|
|
Team Size
|
Two.
|
| |
|
|
Position
|
Analyst / Programmer.
|
| |
|
|
Responsibilities
|
Design, Coding, & Testing.
|
| |
|
|
The project
|
|
| |
|
|
To ensure that all source bills are present for every SAP
allocated to a Customer's Account it was necessary to manually
check whether or not an invoice has been received for each SAP
before the bill is run which is a time consuming, and not necessarily
accurate process. The APAC system identifies on an exception basis
those accounts for which a complete set of valid invoices has not been
received. APAC can be used to take decision whether an APAC Validation
is needed for a customer, create APAC reports (both accounts and SAP),
and automate delay CFB invoices.
I was involved in designing the system using Rational Rose, coding
the APAC validation and the APAC reports which includes development of
EJB, Servlet and JSP.
|
| |
|
|
Operating System
|
MS WINDOWS NT 4.0 & IBM AIX.
|
| |
|
|
Languages
|
JAVA1.1.7 & HTML 4.0.
|
| |
|
|
Database
|
IBM DB2 5.0 & 5.7.
|
| |
|
|
Special Software
|
JSDK, JDBC, Websphere transaction server 3.0.2,
|
|
|
JSP, EJB, and Visual age 3.0.
|
| |
|
|
Work Location
|
T.C.S, Chennai, India.
|
| |
|
|