Professional Documents
Culture Documents
Echnical Esign Ocument: BPL Category - Personalization
Echnical Esign Ocument: BPL Category - Personalization
Echnical Esign Ocument: BPL Category - Personalization
Approvals:
Name Signature
Mr. Prakash R
Document Control
Change Record
4
Reviewers
Name Position
Ma
Malcolm Project Manager
Saravanan SB Technical Lead
Distribution
1
2
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
Specifications.............................................................................................. 1
Dataflow Diagram*................................................................................1
TRIGGER*.............................................................................................. 1
PL/SQL Programs*..................................................................................1
PO Header*............................................................................................ 1
Screen Shots*........................................................................................ 3
Request Group*.....................................................................................7
Module List............................................................................................ 7
Layout................................................................................................... 7
Incompatibility.......................................................................................7
Other Considerations.............................................................................7
Design Summary...................................................................................8
Coding Summary...................................................................................8
Testing Summary...................................................................................8
Open and Closed Issues for this Deliverable...............................................9
Open Issues........................................................................................... 9
Closed Issues......................................................................................... 9
Preface
Functional Design Documents primary purpose is to describe the functional aspects of one or
more components of an ERP system, typically, a Customization (Report, Alert, Workflow etc.).
Technical Overview
C-DOT has a requirement of collecting information while creating SR, if the applicant
comes under BPL category then the RTI fee will be zero. At the time of collecting
information, the system should check whether the applicant category as BPL and
attachment of BPL certificate, then the system should store the information about RTI Fee
will be ZERO. The following fields to be capture at header level DFF in Tele service.
a) Category
b) BPL Certificate
c) RTI Fee
Approach
C-DOT to capture the following fields while creating RTI SR.
Subject: Collecting relevant BPL category information during RTI SR creation process.
a) Category
b) BPL Certificate
c) RTI Fee
Specifications
Dataflow Diagram*
TRIGGER*
PL/SQL Programs*
PO Header*
Navigation:Application DeveloperFlexfieldDescriptiveSegments
Application: Service
Title: Additional Information
Prompt: Context Value
Segment:
Value Set:
Screen Shots*
Descriptive Flexfield Segments:
Request Group*
Module List
Teleservice
Layout
Incompatibility
Other Considerations
Restart Strategy
Crash Recovery
Design Summary
Functional Design
Technical Design
Design Review
Final Acceptance
Technical design was approved by technical lead and ERP Manager and
released for development.
Coding Summary
Development was done on development instance (CDOT DEV) to work with
Release 12.1.3 of Oracle Applications. All coding follows the standards
defined in the Build Standards document for CDOT.
Program Files
Testing Summary
The Report will be tested in CDOT Dev environment before being moved to
production.
Open Issues
Closed Issues