TECHNICAL DESIGN DOCUMENT

BPL CATEGORY - PERSONALIZATION

Author: Shyam Sundar M

Creation Date: Feb 01, 2017
Last Updated: Feb 01, 2017
Document Ref: N/A
Version: 1.0

Approvals:

Name Signature

Mr. Rajiv Bhasin

Mr. Prakash R

Copy Number _____

BCT
 Technical Design

Document Control

Change Record
4

Date Author Versio Change Reference

n

Feb 01, Shyam Sundar M 1.0 No Previous Document

2017

Reviewers

Name Position
Ma
Malcolm Project Manager
Saravanan SB Technical Lead

Distribution

Copy Name Location

No.

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.

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 2 of 12

 Technical Design

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

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 3 of 12

 Technical Design

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.).

Requirement Description C-DOT Solution Solution Description Remark

Id # Function / Type s
Oracle
Function

R.TSR.02 If the applicant comes under RTI / Person Oracle-Tele service-

BPL category then RTI fee Oracle Tele alizatio Personalization
will be Zero. Field with BPL service n
details is required and
scanned copy of BPL
certificate need to be
attached. RTI application
may come as a transferred
application from some other
organization and RTI fee will
not be given to C-DOT..

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 4 of 12

 Technical Design

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.

Fields to be captured for approval workflow:

a) Category
b) BPL Certificate
c) RTI Fee

Specifications

Dataflow Diagram*

TRIGGER*

PL/SQL Programs*

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 5 of 12

 Technical Design

PO Header*

Navigation:Application DeveloperFlexfieldDescriptiveSegments

Descriptive Flexfield Segments:

Application: Service
Title: Additional Information
Prompt: Context Value

Context Field values:

Code: Name: Description:

Global Data Elements Global Data Elements Global Data Element
Description
Category Applicant Category Applicant Category

Segments Summary (Additional Information)-Applicant Category

Number Name Window Column Value Set

Prompt
1 Category Category EXTERNAL_ATTRIBUTE_1 XXCDOT_SERVICE_CATEGORY

2 BPL BPL EXTERNAL_ATTRIBUTE_2 XXCDOT_BPL_ATTACHMENT

Certificate Certificate
Attached Attached

3 RTI Fee RTI Fee EXTERNAL_ATTRIBUTE_3

4 RTI Relates RTI Relates EXTERNAL_ATTRIBUTE_4

to to

5 Valid upto Valid upto EXTERNAL_ATTRIBUTE_5

6 Remarks Remarks EXTERNAL_ATTRIBUTE_6

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 6 of 12

 Technical Design

Segment:

Name Default Type Default Value

BPL Certificate Attached SQL Statement select meaning from
fnd_lookup_values where
lookup_type =
'XXCDOT_BPL_CATE_VALIDTE' and
lookup_code = :
$FLEX$.XXCDOT_SERVICE_CATEGORY
RTI Fee SQL Statement select tag from fnd_lookup_values
where lookup_type =
'XXCDOT_BPL_CATE_VALIDTE' and
lookup_code = :
$FLEX$.XXCDOT_SERVICE_CATEGORY

Value Set:

Value Set Name List Security Format Maximu Validatio

Type Type Type m Size n Type
XXCDOT_SERVICE_CATEGORY List Of No Security Char 20 Independen
Values t
XXCDOT_BPL_ATTACHMENT List Of No Security Char 5 Independen
Values t

Screen Shots*
Descriptive Flexfield Segments:

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 7 of 12

 Technical Design

Click Segments Button for Additional Information:

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 8 of 12

 Technical Design

Value Set (XXCDOT_SERVICE_CATEGORY)

Value Set (XXCDOT_BPL_ATTACHMENT)

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 9 of 12

 Technical Design

Request Group*

Module List
Teleservice

Layout

Incompatibility

Other Considerations

Restart Strategy

Crash Recovery

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 10 of 12

 Technical Design

Design Summary

Functional Design

Functional Design Approval

Functional design was approved by Global ERP Support Manager.

Technical Design

Design Review

Technical design was reviewed by technical lead.

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

The files required for this customization are as follows:

File Description Coded By

Testing Summary
The Report will be tested in CDOT Dev environment before being moved to
production.

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 11 of 12

 Technical Design

Open and Closed Issues for this Deliverable

Open Issues

ID Issue Resolution Responsibility Target Date Impact

Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact

Date

MD-070- C-DOT Quotation Comparative Statement Report Ver. 1.1 Page 12 of 12