You are on page 1of 17

AIM

MD.050 APPLICATION
EXTENSIONS FUNCTIONAL DESIGN
Author:

Manjunath K V

Creation Date:

Feb 28, 2007

Last Updated:

Mar 02 2007

Document Ref:
Version:

1.0

Approvals:

Mr.T.Saravanan, Project Manager,


AIT
Mr. R. Venkateswaran, Vice
President Operations, Apps Info Tec
Pvt Ltd

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

Document Control
Change Record
3

Date

Author

Version

28.02.2007
02.03.2007

Manjunath K V
Manjunat h K V

Draft
1.0

Change Reference

Reviewers
Name

Position

Mr.T.Saravanan

Project Manager, AIT

Distribution
Copy No.

Name

Location

1
2

Library Master
T.Saravanan

Project Library
Project Manager

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.

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

Document Control

Page ii of 17

MD.050 Application Extensions Functional Design

Doc Ref:
Error! Reference source not found.

Contents

Document Control........................................................................................................... ii
1. Topical Essay ................................................................................................................4
1.1 Background ..........................................................................................................4
1.2 Basic Business Needs...........................................................................................4
1.3 Major Features .....................................................................................................4
1.4 Assumptions ........................................................................................................5
1.5 User Procedures : Refer Open Issues 04. ...........................................................5
2. Tea Catalog Form .........................................................................................................6
2.1 Tea Catalog Form General Description: ............................................................6
2.2 Tea Catalog Form Layout ...................................................................................7
2.3 Tea Catalog Form Fields : ...................................................................................8
2.4 Tea Catalog Form Fields Additional Information..........................................9
3 Tea Tasting Form :.......................................................................................................11
3.1 Tea Tasting Form General Description : .........................................................11
3.2
Tea Tasting Form Layout : ........................................................................12
3.3 Tea Tasting Form Fields : ..................................................................................14
3.4 Tea Tasting Form Fields Additional Information: .......................................15
4. Technical Overview....................................................................................................16
5. Open and Closed Issues for this Deliverable ...........................................................17
5.1 Open Issues ........................................................................................................17
5.2 Closed Issues......................................................................................................17

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

Document Control

Page iii of 17

1. Topical Essay

1.1 Background
J V Gokal Business Group are into the business of Tea trading in the form of Tea Bags, Tea Packets and Bulk Tea Blending. For the above purpose the raw
material Tea Lots are purchased through various Auctions held across the country at various Auction centers. Various Brokers of the Auction centers provide detailed
information about the Raw Material Tea Lots in the form of Catalog Tables either in printed format or in soft copy MS Excel format.
The Tea Departments of JVG at various operating units ascertain the quality of the Teas by tasting the Tea Samples provided by the Brokers along with the
Tea Catalogs. The Tea tasting parameters are a qualitative measure of the Raw Material Tea Lots which aids the bidding of the selected Teas during Auction.
JVG has a need to capture the entire Catalog details in Oracle Applications. In the future the captured data can be analysed to ascertain the type, kind and
quantity of Raw Material Tea lots which would be helpful in understanding current and future market trends.

1.2 Basic Business Needs


1.

To capture the Tea Catalogue Data provided by the Broker.

2.

To update the Catalogue Information after the completion of the Auction to capture the Selling Price and Buyer information for each
record.

3.

To capture the Tasting parameter values for selected catalogue records.

1.3 Major Features


Standard Oracle Application does not provide Catalogue Form or Tasting Form as required by the user.. As such the above forms are
customized to capture specific business scenerios.
The Catalog and the Tea Tasting Forms can be accessed only through Manufacturing Responsibilities and specific Data Entry
Responsibility.

MD.050 Application Extensions Functional Design

Doc Ref:
Error! Reference source not found.

1.4 Assumptions
This design assumes that the following statements are true:
Any successful Bid results in an Item Creation in Oracle Inventory module through Interfaces only if the Tasting Parameters have values.
Tasting Form can be accessed either direct or through the Catalogue Form.
Catalog Records can be inserted / updated into the Catalog Custom Table either through the Custom Catalog Form or through Data Import
in excel format.
Catalog records can be deleted only through the Custom Catalog Form.
Tasting Parameters values can be inserted / updated only through Tasting Form.

1.5 User Procedures : Refer Open Issues 03.

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

1. Topical Essay

Page 5 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

2. Tea Catalog Form


2.1 Tea Catalog Form General Description:
Sl. No
1

General Instruction

Screen Formats are defined and followed by Field details


Above every screen, there is a brief description about the
purpose of the form.

3
4

All the screens will have standard WHO Columns (Created By,
Created Date etc,)
This module will work above all SOBs and OUs

This form needs to be registered as Custom Form.

6
7

The form needs to work in query and retrieve mode as well as


input and modification mode
Query Fields Refer to Table 1A

If the field Succesful Bid is enabled then the record should not
be saved unless data is entered in the Tasting form.

Remarks

If the record is saved after succesful bid is enabled then a new


item should get created in the Item Master
Refer to Open Issue 01.
For any record Tasting form should be enabled for viewing and
10 editing purpose.
Table 1 A
Field Name
Sequence of Query Mode
Broker Code
1
Sale No
1
Sale Year
1
Garden Name
1
Grade
1
Invoice No.
1
Lot No.
1
Other fields
2
9

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

2. Tea Catalog Form

Page 6 of 17

MD.050 Application Extensions Functional Design

Doc Ref:
Error! Reference source not found.

2.2 Tea Catalog Form Layout


Purpose of the Form :
a.

To capture details from Tea Catalogs.

b. To query details about Tea Catalog entries.


c.

To modify values of existing records.

d. To delete Tea Catalog entries.

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

2. Tea Catalog Form

Page 7 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

2.3 Tea Catalog Form Fields :


Sl.N
o

Form Fields

Type

Size

1
2

AUCTION CENTER
SALE_NO

Alpha Numeric
Alpha Numeric

----5

3
4
5
6

BROKER CODE
LOT_NO
GRADE
INVOICE NO

Alpha Numeric
Alpha Numeric
Alpha Numeric
Alpha Numeric

7
8

GARDEN
CATALOGUE TYPE
CATALOGUE CATEGORY
SALE_YEAR
SEASON YEAR
AREA
F_CHEST
T_CHEST
GP_NO
GP_DT
AWR_DT
PACKING_DT
WAREHOUSE LOCATION
PACKAGES
PACKAGE TYPE
GROSS_WT / PACKAGE
NET_WT/PACKAGE
ACTUAL_WT/PACKAGE
VALUATION PRICE
SELLER
BUYER
SELLING PRICE

9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

Remarks

Description

Example

6
5
14
12

List of Values
Mandatory.
Needs to be codified by AIT;
Mandatory;Refer Open Issues 03.
Mandatory.
Mandatory.
Mandatory.

Edit
Edit
Edit
Edit

Alpha Numeric
Alpha Numeric

16
12

Mandatory ;
Mandatory.

Edit Box; Query Enabled; Mandatory;


Edit Box; Query Enabled; Optional;

Alpha Numeric
Numeric
Numeric
Alpha Numeric
Numeric
Numeric
Alpha Numeric
Date
Date
Date
Alpha Numeric
Numeric
Alphabetic
Numeric
Numeric
Numeric
Currency
Alphabetic
Alphabetic
Numeric

12
4
4
12
12
12
6

Otional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
Optional
2 Decimal Digits; Optional
2 Decimal Digits; Optional
2 Decimal Digits;Optional
6 Digits with 2 Decimal Digits; Optional

Edit Box; Query Enabled; Optional;


List of Value; Optional; Query Enabled
List of Values;Optional
Edit Box; Optional
Edit Box;Optional
Edit Box;Optional
Edit Box;Optional;
Date format ( DD/MMM/YYYY)
Date format ( DD/MMM/YYYY)
Date format ( DD/MMM/YYYY)
Edit Box; Optional;
Edt Box ;Optional
Edit Box;Optional
Edit Box; Optional
Edit Box;Optional
Edit Box; Optional
Edit Box;Optional
Edit Box;Optional
Edit Box;Optional
Edit Box;Optional

30
4
12
5
5
7
6
30
30
6

6 Digits with 2 Decimal Digits; Optional

Refer Open Issue 03.


Edit Box; Query Enabled; Mandatory;
Box; Query Enabled;
Box; Query Enabled;
Box; Query Enabled;
Box; Query Enabled;

Mandatory;
Mandatory;
Mandatory;
Mandatory;

08
ABC
000013
BP
C01941A
ATTAREEKHA
T
CT
2006
2006
A
25092
25131
687
11/8/2006
12/23/2006
11/4/2006
ITSA
40
Case
29.4
29.0
1146.0
70.00

86.00

2. Tea Catalog Form

Page 8 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

2.4 Tea Catalog Form Fields Additional Information.


Sl.N
o

Form Fields

Type

Size

SAVE
EXIT
CLEAR
TASTING

Button
Button
Button
Button

<Lot>

Tab

Tab

<Packages>

Tab

Tab

Tab

Tab

<Weight>
<GP.
Details>

Tab

Tab

<Valuation>

Tab

10

Succesful Bid

11

Date of entry

Date

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

-----

Standard Save Functionality.


Standard OK Functionality.
Standard Clear Functionality.
Shuld open Tasting Form when clicked.

Description

1
2
3
4

Tab
CheckBo
x

5
6
5
14

Remarks By AIT
Button
Button
Button
Button

Yes / No

Check Box

In case of new entry , default should be System


Date.

Date format (
DD/MMM/YYYY)

2. Tea Catalog Form

Page 9 of 17

MD.050 Application Extensions Functional Design

Doc Ref:
Error! Reference source not found.

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

2. Tea Catalog Form

Page 10 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

3 Tea Tasting Form :


3.1 Tea Tasting Form General Description :
Sl. No
1
2
3
4
5

General Instruction

Remarks

Screen Formats are defined and followed by Field details.


Above every screen, there is a brief description about the purpose of the form.
All the screens will have standard WHO Columns (Created By, Created Date
etc).
This module will work above all SOBs and OUs.
This form needs to be registered as Custom Form.

6
7

8
9
10

Sl. No
1
2
3
4
5
6

The form needs to work in query and retrieve mode as well as input and
modification mode.
Query Fields Refer to Table 1B
If the field Succesful Bid is enabled then the record should not be saved unless
data is entered in the Tasting Form and the selling price field in the Catalogue id
updated.
If the record is saved after succesful bid is enabled then a new item should get
created in the Item Master.
For any record Tasting form should be enabled for query and update mode.
Table 1 B
Field Name
Broker Code
Sale No
Garden Name
Grade
Invoice No.
Lot No.

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

Sequence of Query Mode


1
1
1
1
1
1

3 Tea Tasting Form :

Page 11 of 17

MD.050 Application Extensions Functional Design

Doc Ref:
Error! Reference source not found.

3.2 Tea Tasting Form Layout :


Purpose of the Form :
a.

To capture details from Tea Sampling for particular Catalog Entries.

b. To query details about Tea Catalog Entries.


c.

To modify values of existing records.

d. To delete Tea Tasting Entries.

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

3 Tea Tasting Form :

Page 12 of 17

MD.050 Application Extensions Functional Design

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

Doc Ref:
Error! Reference source not found.

3 Tea Tasting Form :

Page 13 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

3.3 Tea Tasting Form Fields : Refer Open Issue 04.


Sl.N
o

Fields
GRADING
CATEGORY

Category

Field Format

Size

Min

Max

Description

Critical Parameters

Alpha Numeric

16

----

----

Insertion and Retrieval Modes .

16

----

----

Insertion and Retrieval Modes .

Critical Parameters

Alpha Numeric

STANDARD /
BLEND
LEAF
APPEARANCE

Quality Parameter

Numeric

0.5

9.5

Insertion and Retrieval Modes .

LIQUOR COLOR

Quality Parameter

Numeric

0.5

9.5

Insertion and Retrieval Modes .

SIZE

Quality Parameter

Numeric

Insertion and Retrieval Modes .

INFUSION

Quality Parameter

Numeric

Insertion and Retrieval Modes .

MILK COLOR

Quality Parameter

Numeric

Insertion and Retrieval Modes .

TASTE

Quality Parameter

Numeric

Insertion and Retrieval Modes .

QUALITY

Quality Parameter

Numeric

10

FLAVOUR

Quality Parameter

Numeric

11

REMARKS

Quality Parameter

Alpha Numeric

Remarks

Insertion and Retrieval Modes


Insertion and Retrieval Modes
Insertion and Retrieval Modes

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

30

----

----

3 Tea Tasting Form :

Page 14 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

Sl.N
o

Fields

Field Format

Size

Minimum

Maximum

Remarks
Refer Open
Issue 02

Description
Query Mode only

Example

12

BROKER CODE

ABC
ATTAREEKHAT

13

GARDEN NAME

Query Mode only

14

SALE NO.

Query Mode only

01

15

INVOICE NO.

Query Mode only

12345678

16

GRADE

Query Mode only

BP

17

LOT NO.

Query Mode only

000013

3.4 Tea Tasting Form Fields Additional Information:


Sl.N
o

Fields to be present

Field Format

Catalog

Button

Save

Button

OK

Button

Cancel

Button

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

Size

Minimum

Maximum

Remarks

Description

Example

Should open Catalog


Form with relevant data.
Standard Save
Functionality.
Standard OK
Functionality.
Standard Cancel
Functionality.

3 Tea Tasting Form :

Page 15 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

4. Technical Overview
Considerations
1.

Both the Catalogue Form and the Tea Tasting Form should provide Delete Functionality similar to Oracle Applications.

2.

Query Mode and Functionality should be similar to Oracle Applications.

3.

Tabs Placements should be similar to Oracle Applications.

4.

In case of Retreival of existing records The Date of Entry and the Place of Entry should also be retrieved.

5.

In case of Updation of records date of updation need not be captured.

6.

If the Succesful Bid Check box is enabled in Catalogue then the Delete functionality for that particular record needs to be disabled.

7.

Once the Item is created in Item Master of Oracle Applications , the Successful Bid Checkbox status should not be allowed to change.
The only exception being the deletion of the Item itself from the Item Master.

8.

Tea Tasting Parameter values cannot be deleted if


a.

An Item exists in the Item master linked with this particular Tea Catalog Entry which is refered by the Tea Tasting Form.

b. The Succesful Bid Check Box is enabled in the Tea Catalog form for the particular Catalog Entry which is refered by the Tea
tasting Form.
9.

All The Query mode fields in the Tea Tasting form should retrieve the values from the appropriate fields in the Catalogue form for the
relevant record once queried.

10. The catalogue would be uploaded twice in excel format.


a.

Pre auction Update : This occurs before the Auction.

b. Post Auction Update : This occurs after the Auction . having values for Buyer, Selling Price etc..

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

4. Technical Overview

Page 16 of 17

Doc Ref:
Error! Reference source not found.

MD.050 Application Extensions Functional Design

5. Open and Closed Issues for this Deliverable


5.1 Open Issues
ID

Issue

01

The Transition Methodology


of the Catalogue and the
Tasting Data after successful
bidding for the actual creation
of an item in the Item Master
of Oracle Application needs to
be ascertained.
Broker Code - list of values
needs to be determined.
User procedures need to be
fixed.
Mandatory and Optional
Fields need to be fixed for
Tasting Parameters.

02
03
04

Resolution

Responsibility

AIT

Target Date

Impact
Date

02-Mar-2007

JVG

02-Mar-2007

AIT

04-Mar-2007

JVG

04-Mar-2007

Responsibility

Target Date

5.2 Closed Issues

ID

Issue

Error! Reference source not found.


File Ref: MD50- version 1[1].0 (v. 1.0)

Resolution

Impact
Date

5. Open and Closed Issues for this Deliverable

Page 17 of 17