Md050 application extensions_functional_design_080112

AIM
MD.050 APPLICATION
EXTENSIONS FUNCTIONAL
DESIGN
<Company Long Name>
<Subject>

Author: <Author>
Creation Date: August 1, 2012
Last Updated: August 1, 2012
Document Ref: <Document Reference Number>
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>

MD.050 Application Extensions Functional Design Doc Ref: <Document Reference Number>
August 1, 2012

Document Control

Change Record
4

Date Author Version Change Reference

1-Aug-12 <Author> Draft 1a No Previous Document

Reviewers

Name Position

Distribution

Copy No. Name Location

1 Library Master Project Library
2 Project Manager
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.

<Subject> Document Control iii
File Ref: md050applicationextensionsfunctionaldesign080112-120801122058-phpapp01.doc (v. DRAFT 1A )
Company Confidential - For internal use only

August 1, 2012

Contents

Document Control...................................................................................................................ii

Topical Essay...........................................................................................................................iv
Basic Business Needs......................................................................................................iv
Major Features.................................................................................................................iv
Definitions........................................................................................................................iv
User Procedures..............................................................................................................iv
Examples............................................................................................................................v
Business Rules...................................................................................................................v
Assumptions.....................................................................................................................v
Century Date Compliance...............................................................................................v
Form and Report Descriptions.............................................................................................vi
<Form Title> - Form Description..................................................................................vi
<Form Title> Form..........................................................................................................vi
Prerequisites.....................................................................................................................vi
<Zone 1 name> Zone......................................................................................................vi
<Zone 2 name> Zone......................................................................................................vi
<Report Title> - Report Description...........................................................................vii
<Report Title>.................................................................................................................vii
Report Parameters..........................................................................................................vii
Report Headings............................................................................................................vii
Column Headings.........................................................................................................viii
Concurrent Program Description........................................................................................ix
When to Run the Program.............................................................................................ix
Launch Parameters..........................................................................................................ix
Business Rules Implemented.........................................................................................ix
Log Output.......................................................................................................................ix
Restart Procedures..........................................................................................................ix
Technical Overview.................................................................................................................x

Open and Closed Issues for this Deliverable.....................................................................xi
Open Issues.......................................................................................................................xi
Closed Issues....................................................................................................................xi


August 1, 2012

Topical Essay
<Subject> allows you to...

<Subject> contains:

• <Component Name> Form
• <Component Name> concurrent program

Basic Business Needs

<Subject> provides you with the features you need to satisfy the following basic
business needs. You will be able to address the following:

• <Business need 1>
• <Business need 2>

Major Features

<Feature Name 1>

<Description of feature>

<Feature Name 2>

<Description of feature>

Definitions

<Unique Term>

<Definition>

User Procedures

In order to <do what this feature does>, you must perform the following steps:

• <Step 1>
• <Step 2>

Each of these steps is described in more detail below.

<Step 1>

<Detailed description of first step>


August 1, 2012
<Step 2>

<Detailed description of second step>

Examples

Business Rules

Assumptions

This design assumes that the following statements are true:

•
•
•

Century Date Compliance

In the past, two character date coding was an acceptable convention due to
perceived costs associated with the additional disk and memory storage
requirements of full four character date encoding. As the year 2000 approached, it
became evident that a full four character coding scheme was more appropriate.

In the context of the Application Implementation Method (AIM), the convention
Century Date or C/Date support rather than Year2000 or Y2K support is used.
Coding for any future Century Date is now considered the modern business and
technical convention.

Every applications implementation team needs to consider the impact of the century
date on their implementation project. As part of the implementation effort, all
customizations, legacy data conversions, and custom interfaces need to be reviewed
for Century Date compliance.

When designing and building application extensions, it is essential that all dates be
entered, stored, and processed using the full four digit year for compliance with
Century Date standards. In the case of custom interfaces, both the program code
and imported legacy or third-party application data must be checked for
compliance with Century Date standards.


August 1, 2012

Form and Report Descriptions
The following defines the form and report elements of <Subject> customization:

<Form Title> - Form Description

<Form Title> Form

Use this form to ...

Prerequisites

Before you can use this form you must perform the following:

• <step 1>
• <step 2>

<Zone 1 name> Zone

Use this zone to...

Field 1 (Optional, LOV source) HELP

Enter...

Field 2 (Display only) HELP

<Custom Application Name> displays ...

<Zone 2 name> Zone

Field 3 (Required, Default) EDIT ZOOM PICK HELP

Choose one of the following options:

First Option Description of first option.

Second Option Description of second option. <Custom Application
Name> displays this option as the default.


August 1, 2012

<Report Title> - Report Description
.........1.........2.........3.........4.........5.........6.........7.........8
.........1.........2.........3.........4.........5.........6.........7.........8.........9.........0.........1.........2.........3..
.........1.........2.........3.........4.........5.........6.........7.........8.........9.........0.........1.........2.........3.........4.........5.........6.........7.........8

________________________________________________________________________________
<Company Long Name> Date: 01-Jan-92
<Left Title> <Report Title> Page: 1
<Report Sub-Title>

Heading 1 Heading 2
--------- ----------

<sample data here>

*** End of Report - <Report Title> ***

________________________________________________________________________________

<Report Title>

Use the <Report Title> report to ...

Report Parameters

You run the <Report Title> report from the Standard Report Submission form.
Enter the following parameters specify the desired reporting options.

Parameter 1 (Required, Default) PICK

Select one of the following values:

Option 1 Description.

Option 2 Description

Parameter 2 (Optional)

Enter...

Report Headings

<Company Long Name>

<Custom Application Name> prints the name of the organization running the
report.


August 1, 2012
Date:

<Custom Application Name> prints the date and time that it ran the report. The
date is in DD-Mon-YY format and the time is in 24-hour format.

<Left Title>

<Custom Application Name> prints <whatever this is used for on this report>.

<Report Title>

<Custom Application Name> prints the name of the report

<Report Sub-Title>

<Custom Application Name> prints <whatever this indicates>.

Page:

<Custom Application Name> prints the page number for each page of the report.

Column Headings

Heading 1

<Custom Application Name> prints...


August 1, 2012

Concurrent Program Description
The <Component Name> concurrent program is needed to …

When to Run the Program

<Component Name> concurrent program should be run when…

Launch Parameters

Launch parameters for the <Component Name> concurrent program include:

Business Rules Implemented

The business rule implemented by <Component Name> concurrent program is…

Log Output

The log output consists of ….

Restart Procedures

Restart procedures for <Component Name> concurrent program are as follows:

•
•
•


August 1, 2012

Technical Overview

Considerations

If any Oracle Manufacturing tables change in future versions of Oracle
Manufacturing, components of this customization may also require changes to work
correctly. Evaluating the impact of such changes on custom programming is the
responsibility of the company, although additional consulting services can be
contracted to assist prior to upgrading.


August 1, 2012

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


Md050 application extensions_functional_design_080112

Recommended

More Related Content

What's hot (20)

Similar to Md050 application extensions_functional_design_080112 (20)

Recently uploaded (20)

Md050 application extensions_functional_design_080112