COMMERCIAL IN CONFIDENCE

Oracle R12 Implementation for TSL

At

Functional Specification Document

For

Migration of Open AP Invoices

Document Number: AP002

_________________________________________________________________________________________
FSD_AP002.doc Page 1 of 14
 COMMERCIAL IN CONFIDENCE

Document Revision History

Version Revision Date Description of Changes Author(s)

1.00 06-Dec-2012 Initial Document Infosys Ltd.
2.00 24-Dec-2012 Updated after TSL review Infosys Ltd.

Distribution/Review History

Version Action Action Date Name Title

Signed Off

Name Title Version Date Signature Remarks

Related or Referenced Documents

Document name Description Owner Document Reference

_________________________________________________________________________________________
FSD_AP002.doc Page 2 of 14
 COMMERCIAL IN CONFIDENCE

Table of Contents
1 INTRODUCTION...............................................................................................................5
1.1 Document Purpose.................................................................................................... 5
1.2 Acronyms and Glossary.............................................................................................5
2 BUSINESS REQUIREMENTS..........................................................................................5
2.1 Business Requirements Overview.............................................................................5
2.2 Pre Requisites............................................................................................................5
3 APPROACH......................................................................................................................6
3.1 Overview.................................................................................................................... 6
3.2 Process Flow Diagram...............................................................................................7
3.3 Processing Logic........................................................................................................8
3.4 Responsibility, Menu Navigation and User Procedure...............................................8
3.4.1 Responsibility Details..........................................................................................8
3.4.2 Menu Navigation.................................................................................................8
3.4.3 User Procedure...................................................................................................8
4 FUNCTIONAL DESIGN DETAILS....................................................................................8
4.1 Functional Design Details for Interfaces.....................................................................8
4.1.1 Interface Overview and Description....................................................................8
4.1.2 Data File Stakeholders Details............................................................................9
4.1.3 Mapping Details and Validation...........................................................................9
4.1.4 Concurrent Program details................................................................................9
4.1.5 Launch Parameters...........................................................................................10
4.1.6 Scheduling Details............................................................................................ 10
4.1.7 Interdependencies.............................................................................................10
4.1.8 Error handling and Reporting............................................................................11
4.1.9 Audit Trial Reports............................................................................................ 11
4.1.10 Restart Mechanism...........................................................................................11
4.1.11 Backup and Recovery.......................................................................................11
4.1.12 Forms Layout....................................................................................................11
[Link] Form Parameters.......................................................................................11
[Link] Field Mapping............................................................................................ 11
[Link] Field Validations.........................................................................................11
[Link] Navigation Flow......................................................................................... 11
[Link] Data Processing Logic...............................................................................11
[Link] Messages and Error Codes.......................................................................11
4.1.13 Report Layout................................................................................................... 12
[Link] Log Output.................................................................................................12

_________________________________________________________________________________________
FSD_AP002.doc Page 3 of 14
 COMMERCIAL IN CONFIDENCE

[Link] Report parameters.....................................................................................12

[Link] Report Headings........................................................................................12
[Link] Column Headings...................................................................................... 12
[Link] Table and View Usage...............................................................................12
[Link] Program Logic............................................................................................12
[Link] Incompatibility............................................................................................12
[Link] Installation..................................................................................................12
4.1.14 JSP/OAF Layout............................................................................................... 12
[Link] Screen Overview........................................................................................12
[Link].1 Screen Name........................................................................................12
[Link].2 Screen Functionality.............................................................................12
[Link].3 Screen Layout.......................................................................................12
[Link].4 Field Descriptions................................................................................. 12
[Link].5 Validations............................................................................................ 13
[Link] Technical Architecture...............................................................................13
[Link].1 Class Files............................................................................................ 13
[Link].2 General Utilities.....................................................................................13
[Link].3 Mime Body............................................................................................13
[Link].4 Special Processing...............................................................................13
4.1.15 Performance Considerations.............................................................................13
5 DATA FLOW DIAGRAM.................................................................................................13

6 ASSUMPTIONS.............................................................................................................. 13
6.1 Business Assumptions.............................................................................................13
6.2 Oracle Application Assumptions...............................................................................13
7 ISSUES........................................................................................................................... 14
7.1 Open Issues............................................................................................................. 14
7.2 Closed Issues...........................................................................................................14
8 ACCEPTANCE CRITERIA............................................................................................. 14

9 APPENDIX...................................................................................................................... 14
9.1 Data File Format for Interfaces.................................................................................14

_________________________________________________________________________________________
FSD_AP002.doc Page 4 of 14
 COMMERCIAL IN CONFIDENCE

1 Introduction

1.1 Document Purpose

This Functional Design Document deals with Accounts Payables Transactions

Migration from Legacy System (GLOVIA) to Oracle applications.

1.2 Acronyms and Glossary

A list of definitions, acronyms and abbreviations used in documentation are given

below.

Term Definition
AP Accounts Payables
GLOVIA Legacy System for Fujitsu
NA Not Applicable
TSD Technical Specification document
TSL TEN Singapore Pte. Ltd
Oracle EBS Oracle E-Business Suite

2 Business Requirements

2.1 Business Requirements Overview

FTSL has a requirement to migrate AP open invoices from their GLOVIA system to
Oracle applications (Invoices for which payments are yet to be made). In standard
oracle application invoices are entered through AP transaction screen, as data is
huge during migration there is a need for custom migration program that reads the
data in legacy system and maps it to oracle applications. Along with open invoices
migration, the accounting data, tax data related to invoices also has to be migrated.

2.2 Pre Requisites

1. AP open invoices data to be interfaced to Oracle will be in the format provided in

appendix.
2. Customer master data for which AP Invoice data is getting interfaced should be
present in Oracle EBS.
3. Descriptive flex fields need to be setup in Oracle.
4. Configurations like Transaction Source, Currency Code, Salesperson, Payment
Terms, Receipt Method, Location Code etc needs to be setup in Oracle.

_________________________________________________________________________________________
FSD_AP002.doc Page 5 of 14
 COMMERCIAL IN CONFIDENCE

3 Approach

3.1 Overview

 This is an inbound interface to Oracle EBS. GLOVIA will extract the existing
AP supplier invoices in flat file and will be transferred to Oracle database
server. The AP supplier invoices file will be a CSV file.
 The data in the flat file will be moved to custom staging tables using a tool
(e.g. SQL Loader). The staging table will be the exact replica of the standard
interface file format from legacy system.
 A custom program will be developed to validate the data based on
predefined conditions and successfully validated records will be transferred
from staging tables to Payables Open interface tables. Custom program will
derive values for fields like Account Code, Invoice Number, Invoice Type,
Line Type etc. before transferring valid records to Oracle EBS interface
tables.
 The records which are validated by the custom program will be moved to
interface tables and status of error records will be updated in a custom
staging table.
 Standard ‘Payables Open Interface Import’ program is executed in Oracle
EBS. This program will populate AP invoices data from interface tables to
oracle AP Invoices base tables and error records will remain in the interface
tables.
 Custom program will get executed which will move error records from
custom staging tables and Oracle EBS AP Invoices interface tables to
custom error tables.

_________________________________________________________________________________________
FSD_AP002.doc Page 6 of 14
 COMMERCIAL IN CONFIDENCE

3.2 Process Flow Diagram

_________________________________________________________________________________________
FSD_AP002.doc Page 7 of 14
 COMMERCIAL IN CONFIDENCE

3.3 Processing Logic

 Data from Glovia system will be extracted into a data file. This data file will
be used by Oracle SQL Loader to process the records and upload into
staging tables.
 A custom concurrent program will validate the data in the staging tables
upload in the above step.
 In case of any error, the error records will be verified and corrected. They are
re-verified for data correctness. The process will continue until all the records
are validated.
 Once the validation is complete, the data will be uploaded to Oracle standard
interface tables
 Standard concurrent program “Payables Open Interface import” will be called
after the interface tables are populated. This program will populate the
Oracle Base table.

3.4 Responsibility, Menu Navigation and User Procedure

3.4.1 Responsibility Details

Oracle Accounts Payables Super user
Oracle Accounts Payables user

3.4.2 Menu Navigation

<<Responsibility>> - Control – Requests – Run

3.4.3 User Procedure

Step 1: Data is received from legacy system in the required format.
Step 2: Data is checked for consistency.
Step 3: If there are any discrepancies in the data, file is errored out.
Step 4: Data is loaded to staging table
Step 5: Validations are performed
Step 6: Records are than inserted into standard interface table
Step 7: Through import it is populated in the base tables
Step 8: Through some sample testing, data is confirmed for accuracy from
front end.

4 Functional Design Details

4.1 Functional Design Details for Interfaces

4.1.1 Interface Overview and Description

 This interface will insert open AP invoices information into Oracle EBS
received from legacy system which will be a flat file.

 Using any tool (e.g. SQL Loader), the data in flat files will be inserted into
custom staging table and custom program will be run to validate these
records and move to the oracle standard Payables Open interface tables.
_________________________________________________________________________________________
FSD_AP002.doc Page 8 of 14
 COMMERCIAL IN CONFIDENCE

Custom validation program will be used to derive value of certain fields

before transferring them to Oracle EBS Payables Open interface tables.

 Oracle standard ‘Payables Open Interface import’ program will pick up

records from the interface table and insert into the base tables. Errored
records will be flagged and will remain in the Payables Open interface
tables.

 Custom program will move error records from custom staging tables and
Oracle EBS interface error tables to custom error tables.
.

4.1.2 Data File Stakeholders Details

Stakeholder Activity Remarks

GLOVIA Sending data file to Oracle

Server

Oracle EBS Processes data file and imports

into Oracle EBS

4.1.3 Mapping Details and Validation

Please check the data file format for more information on mapping and
validations. [Section 9.1]

SI No Entity Name Description Data Validation Remarks

Position

4.1.4 Concurrent Program details

SI Concurrent Program Type Description

No Program name
1 XXGST_SH_DAT Host This is common program
A_LOADER: Data which will load data from
Loader Program flat file received from
legacy systems to Oracle
custom staging tables.

_________________________________________________________________________________________
FSD_AP002.doc Page 9 of 14
 COMMERCIAL IN CONFIDENCE

SI Concurrent Program Type Description

No Program name
2 XXGSTAP0021:A PLSQL Package This is the main program
P Conversion for Open AP Invoices
Program Conversion. This program
will take care of Data
Loading, Data Validation,
Interfacing validated
records to Standard Oracle
Interface tables &
launching ’Payables Open
Interface Import ‘program.
Data Loading will happen
by launching
“XXGST_SH_DATA_LOA
DER: Data Loader
Program”

4.1.5 Launch Parameters

SI Parameter Description Displayed Required Default Value

No Name (Y/N) / Value Set
Optional
1 Execution This Y Required N TBD
Mode parameter
decides
program
execution
2 Data File Data file Y Required NULL TBD
Name Name
3 File Path File Path Y Required NULL TBD
4 Control Control File Y Required NULL TBD
File Name Name
5 Transfer Transfer Y Required Y TBD
Flag Flag

Launch Parameters will be updated once Technical Design is finalized based

on confirmation on File format from FTSL.

4.1.6 Scheduling Details

The Concurrent Request is run only on demand whenever required

4.1.7 Interdependencies

None

_________________________________________________________________________________________
FSD_AP002.doc Page 10 of 14
 COMMERCIAL IN CONFIDENCE

4.1.8 Error handling and Reporting

 Oracle Interface Errors are corrected and resubmitted again by

deleting Interface table data and reprocessing staging table data.

 Errors encountered in program during validation are captured as

Report in the output..

4.1.9 Audit Trial Reports

NA

4.1.10 Restart Mechanism

If AP Migration program is terminated abruptly, it can be restarted by
resubmission of Concurrent program.

4.1.11 Backup and Recovery

NA

4.1.12 Forms Layout

NA

[Link] Form Parameters

NA

[Link] Field Mapping

NA

[Link] Field Validations

NA

[Link] Navigation Flow

NA

[Link] Data Processing Logic

NA

[Link] Messages and Error Codes

NA

4.1.13 Report Layout

_________________________________________________________________________________________
FSD_AP002.doc Page 11 of 14
 COMMERCIAL IN CONFIDENCE

[Link] Log Output

NA

[Link] Report parameters

NA

[Link] Report Headings

NA

[Link] Column Headings

NA

[Link] Table and View Usage

NA

[Link] Program Logic

NA

[Link] Incompatibility
NA

[Link] Installation
NA

4.1.14 JSP/OAF Layout

[Link] Screen Overview

NA

[Link].1 Screen Name

NA

[Link].2 Screen Functionality

NA

[Link].3 Screen Layout

NA

[Link].4 Field Descriptions

NA

[Link].5 Validations
NA
_________________________________________________________________________________________
FSD_AP002.doc Page 12 of 14
 COMMERCIAL IN CONFIDENCE

[Link] Technical Architecture

NA

[Link].1 Class Files

NA

[Link].2 General Utilities

NA

[Link].3 Mime Body

NA

[Link].4 Special Processing

NA

4.1.15 Performance Considerations

Due to smaller data volume, Payables open interface Import program will be
able to handle it successfully.

5 Data Flow Diagram

Data flow diagram will be updated in Technical Specification Documentation.

6 Assumptions

6.1 Business Assumptions

 Only Open AP Invoices are migrated to Oracle applications.

6.2 Oracle Application Assumptions

NA

7 Issues
_________________________________________________________________________________________
FSD_AP002.doc Page 13 of 14
 COMMERCIAL IN CONFIDENCE

7.1 Open Issues

No Date Issue Description Reply Remarks

Date
1 06-Dec- To Migrate AP Invoices
2012 data to Oracle EBS from
GLOVIA, what are criteria
for selecting data?
2 06-Dec- Confirmation needed on
2012 format used for Migrating
Open AP Invoices data to
Oracle EBS.[ File format is
attached in Appendix
Section 9.1]

7.2 Closed Issues

No Date Issue Issue Closed Remarks

Description Resolution
By Date

8 Acceptance Criteria

NA

9 Appendix

9.1 Data File Format for Interfaces

_________________________________________________________________________________________
FSD_AP002.doc Page 14 of 14