Professional Documents
Culture Documents
MD.070 APPLICATION
EXTENSION TECHNICAL DESIGN
Genworth Unified Oracle
Voucher Sequence Numbering
Author: Sharanappa.L.K
Creation Date: Jun-12-2006
Last Updated:
Document Ref: MD-050 Voucher Sequence Numbering.
Version: 1.0
Approvals:
<Approver 1>
<Approver 2>
MD.070 Application Extension Technical Design
Document Control
Change Record
1
Reviewers
Name Position
Distribution
2
3
4
Note To Holders:
If you receive an electronic copy of this document and print it out, please write your
name on the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front
cover, for document control purposes.
Contents
Document Control...................................................................................................................ii
Technical Overview.................................................................................................................1
Approach............................................................................................................................1
Module List........................................................................................................................2
GNW Voucher Number Report- Concurrent Program Logic..........................................3
Calling Arguments...........................................................................................................3
Log Output........................................................................................................................3
Table and View Usage.....................................................................................................3
Program Logic (pseudo code)........................................................................................3
SQL Statements.................................................................................................................6
Default Data Sources........................................................................................................6
Validation Logic................................................................................................................6
Incompatibility..................................................................................................................6
Performance Considerations...........................................................................................6
Other Considerations.......................................................................................................6
Integration Issues.....................................................................................................................8
Changes Required.............................................................................................................8
Shared Components.........................................................................................................8
Alert conditions................................................................................................................8
Incompatibilities................................................................................................................8
Performance Issues...........................................................................................................9
Database Design.....................................................................................................................10
Desired Table Changes..................................................................................................10
New/Updated Seed Data.............................................................................................10
Descriptive Flexfields.....................................................................................................10
Value Sets.........................................................................................................................10
Grants/Synonyms..........................................................................................................10
Archiving.........................................................................................................................10
Database Diagram..........................................................................................................11
Tables, Indexes, Sequences...........................................................................................11
Implementation Notes...........................................................................................................12
Design Summary............................................................................................................12
Coding Summary............................................................................................................12
Testing Summary............................................................................................................12
Installation.......................................................................................................................13
Open and Closed Issues for this Deliverable....................................................................14
Open Issues......................................................................................................................14
Closed Issues...................................................................................................................14
Technical Overview
This document defines the technical components required to Implement Custom
Voucher Sequence Numbering. Oracle Payables allows users the ability to create
custom Voucher Sequence Numbering.
Approach
This custom program will be running in Three phases. In First Phase Pick all the
Necessary Information from The Ap_invoices and Po_ Vendor_sites_all and
GL_code_combination .Which is The useful for the Genarating the Custom
Voucher Number and Then store that data into Custom table
GEOR_AP_VOUCHER_SEQUENCE_TBL. In Second Phase The Voucher is
Genarating from the Custom table GEOR_AP_VOUCHER_SEQUENCE_TBL And By
the Custom Concurrent Programe all The Custom Voucher numbers are
stored in the Custom table GEOR_AP_VOUCHER_NUMBER_TBL
The Third Phase is refer to Voucher Numbering Report . This report Shows
the Invoice Number , Oracle Voucher Number and Custom Voucher Number.
And This Report will not show GAP Less Voucher Numeber. “ Invoice Date
from” and” Invoice Date to” are Parameter of the Report
All processing and validation results are presented in log file of concurrent request.
Module List
Forms
There is no Customization to the forms, which have been identified as part of this
program other than configuring of Descriptive Flexfield linked to the Operating
Unit Definition, which is a standard functionality of Oracle Applications.
Reports
GNW Voucher Number Report would be produced as part of the Custom GNW
AP Voucher Number Generation. The Details of the records processed and state of
each invoice which are validateed Invoice and show the corresponding oracle
voucher number and custom voucher number .This Report should be run after
the GNW AP Voucher Number Generation concurrent program..
Database Triggers
Calling Arguments
GNW AP Voucher Number Generation would not have any explicit parameters
Log Output
The log output would be limited to the records which were processed as part of the current run of the program
and would consists of following column Headings
1. C ompany Code.
2. Country Code.
3. Document Type.
4. Country Type.
5. Voucher Number
________________________________________________________________________________
AP_INVOICES_ALL X
AP_INVOICE_DISTRIBUTIONS_ALL X
PO_VENDOR_SITES_ALL X
GL_CODE_COMBINATIONS X
HR_LOCATIONS X
HR_ALL_ORGANIZATION_UNITS X
GEOR_AP_VOUCHER_SEQUENCE_ X X
TBL
GEOR_AP_VOUCHER_NUMBER_TB X X
L
Step2: Pick the Country Name and Document types from the Custom look ups
Step1. Get the required data elements from the cursor and looping them
(c) Check the document type(invoice type) in the lookup and with cursor element.
(d) If invoice_country and Supplier country is ITALI then country type is “D”
If invoice_country is ITALI and country exits in lookups then country type code”F”
If invoice_country is ITALI and country not exits in lookups then country type
code”I”
If invoice_country is not ITALI and country not exits in lookups then country type
Code “x ”
(d) Sequence Number genarates sequentionaly and update the in the table .
Step1: The Report shoes Invoice Number,Oracle Voucher number and Custom Voucher number
SQL Statements
1 - Data Selection
SELECT <data>
FROM <tables>
WHERE <select criteria>
AND <join conditions>
Validation Logic
Error Conditions:
No
Warning Conditions:
Incompatibility
Performance Considerations
Other Considerations
Restart Strategy
Restart procedures for the Voucher Sequence Number would follow standard
procedures.
Crash Recovery
Integration Issues
Changes Required
Within Product
Other Products
No changes required
Shared Components
INV
None
BOM
None
ENG
None
MPS/MRP
None
WIP
None
Alert conditions
No
Incompatibilities
None.
Performance Issues
None.
Database Design
This section summarized new and changed database objects and data required to
support Voucher Sequence Numbering . However, the complete database design is
documented in the Database Extensions Design document.
None
Descriptive Flexfields
NO
Value Sets
Grants/Synonyms
Yes
Archiving
No need to archive.
Database Diagram
No new tables
Implementation Notes
This document describes exactly how Voucher Sequence Numbering Programe was
developed and implemented at Genworth Unified Oracle.
Design Summary
Functional Design
Technical Design
Design Review
Final Acceptance
Coding Summary
Program Files
Testing Summary
Installation
A new set of menus (owned by XBOL) is created to call the new forms as follows:
Navigate
Sub-menu
Sub-menu
Open Issues
2 Country code
3 Invoice type
Closed Issues