AIM

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

Author:

<Author>

Creation Date:

January 13, 2006

Last Updated:

January 13, 2006

Document Ref:

<Document Reference Number>

Version:

DRAFT 1A

Approvals:
<Approver 1>
<Approver 2>

please write your name on the equivalent of the cover page. for document control purposes. <Subject> File Ref: 264025148.MD.doc (v. please write your name on the front cover. If you receive a hard copy of this document. DRAFT 1A ) Open and Closed Issues for this Deliverable Company Confidential . Name Location 1 2 3 4 Library Master Project Library Project Manager Note To Holders: If you receive an electronic copy of this document and print it out. 2006 Document Control Change Record 1 Date Author 13-Jan-06 Versio n Change Reference <Autho r> Draft 1a No Previous Documen t Reviewers Name Position Distribution Copy No.For internal use only . for document control purposes.050 Application Extensions Functional Design Doc Ref: <Document Reference Number> January 13.

..................doc (v...................4 Report Parameters....... 3 <Zone 1 name> Zone.............................................................................................................2 Assumptions..................................................................................................................................................3 Prerequisites........................................................................................................4 <Subject> File Ref: 264025148.............................4 Report Headings..........................1 Examples................................................................ 2006 Contents Document Control...................................................................3 <Report Title> .MD.................. DRAFT 1A ) Open and Closed Issues for this Deliverable Company Confidential .......................................................................................ii Topical Essay......................................................................................................................................................2 Century Date Compliance............................................................................................................................................................................................................................................................................ 1 User Procedures............................................................Report Description...................................1 Major Features.050 Application Extensions Functional Design Doc Ref: <Document Reference Number> January 13.........2 Form and Report Descriptions.........................................3 <Form Title> ....................................................................................3 <Form Title> Form............................................................For internal use only ....4 <Report Title>......Form Description.................................................................3 <Zone 2 name> Zone.........................................................1 Basic Business Needs...........................................1 Definitions....................2 Business Rules..........................

..................................................................MD...............6 Business Rules Implemented........6 Log Output................................................8 Open Issues.....6 When to Run the Program................. DRAFT 1A ) Open and Closed Issues for this Deliverable Company Confidential ............050 Application Extensions Functional Design Doc Ref: <Document Reference Number> January 13..................................................................6 Technical Overview........................................For internal use only ........................................7 Open and Closed Issues for this Deliverable...................................................8 <Subject> File Ref: 264025148............................6 Restart Procedures.........................................................................................................................doc (v..............5 Concurrent Program Description......................................................................................................................................................................................................................................... 2006 Column Headings.................. 8 Closed Issues.............................6 Launch Parameters.......................................

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

both the program code and imported legacy or third-party application data must be checked for compliance with Century Date standards. legacy data conversions. In the case of custom interfaces. and processed using the full four digit year for compliance with Century Date standards. In the context of the Application Implementation Method (AIM).<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. the convention Century Date or C/Date support rather than Year2000 or Y2K support is used. As part of the implementation effort. When designing and building application extensions. As the year 2000 approached. stored. and custom interfaces need to be reviewed for Century Date compliance. it became evident that a full four character coding scheme was more appropriate. . all customizations. 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. 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. it is essential that all dates be entered.

Field 1 HELP (Optional. Default) Choose one of the following options: File Ref: 264025148.. Second Option Description of second option. 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 2 HELP (Display only) <Custom Application Name> displays . <Zone 2 name> Zone Field 3 EDIT ZOOM PICK HELP (Required. <Custom Application Name> displays this option as the default. LOV source) Enter. ) Company Confidential . (v.Doc Ref: Form and Report Descriptions The following defines the form and report elements of <Subject> customization: <Form Title> .doc First Option Description of first option.Form Description <Form Title> Form Use this form to ..For internal use only Open and Closed Issues for this Deliverable ..

................1...6..Doc Ref: <Report Title> ........1......7...0..... Option 2 Description Parameter 2 (Optional) Enter..4..................3....2.2......6... Enter the following parameters specify the desired reporting options. Default) PICK Select one of the following values: Option 1 Description...6..........................7.........5...3...6......3.4............2.......... .......Report Description .<Report Title> *** ________________________________________________________________________________ <Report Title> Use the <Report Title> report to ......For internal use only Open and Closed Issues for this Deliverable .............................1...5.......7.3..........................5. File Ref: 264025148....4......3.8......2........... Report Headings <Company Long Name> <Custom Application Name> prints the name of the organization running the report..7....1.. Report Parameters You run the <Report Title> report from the Standard Report Submission form............... ) Company Confidential ..4........9.......8.2.............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 ......8 ...doc (v............ Parameter 1 (Required.................5.1...0........9......

. <Report Title> <Custom Application Name> prints the name of the report <Report Sub-Title> <Custom Application Name> prints <whatever this indicates>. <Left Title> <Custom Application Name> prints <whatever this is used for on this report>.. The date is in DD-Mon-YY format and the time is in 24-hour format. File Ref: 264025148. Column Headings Heading 1 <Custom Application Name> prints. ) Company Confidential .Doc Ref: Date: <Custom Application Name> prints the date and time that it ran the report.doc (v. Page: <Custom Application Name> prints the page number for each page of the report.For internal use only Open and Closed Issues for this Deliverable .

Restart Procedures Restart procedures for <Component Name> concurrent program are as follows:    File Ref: 264025148.Doc Ref: 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 …. ) Company Confidential .doc (v.For internal use only Open and Closed Issues for this Deliverable .

File Ref: 264025148. components of this customization may also require changes to work correctly. although additional consulting services can be contracted to assist prior to upgrading.For internal use only Open and Closed Issues for this Deliverable . Evaluating the impact of such changes on custom programming is the responsibility of the company. ) Company Confidential .Doc Ref: Technical Overview Considerations If any Oracle Manufacturing tables change in future versions of Oracle Manufacturing.doc (v.

For internal use only Open and Closed Issues for this Deliverable . ) Company Confidential .Doc Ref: Open and Closed Issues for this Deliverable Open Issues ID Issue Resolution Responsibility Target Date Impact Date Responsibility Target Date Impact Date Closed Issues ID Issue File Ref: 264025148.doc Resolution (v.