Anda di halaman 1dari 17

c c cc

c c c

c
c
Functional Specification Document

ATS Custom Form


c
c
Oracle R12 Re-Implementation
c
c

c c
Submitted toc
c

c
c
c
c
c
½
c

c
c
Infos s Technologies Ltd.c
c
c
c
ccc c
c c cc
c c
c
c
c c

c c c
 
   c c cccccccc  cccc
c c cc
c c c
Document Tracking Information
c
c
Document Revision Histor
c
Version Datecc Descriptioncc Authorc
1.0 12/10/2008 Base Version Infosys
c c c c
c c c c
c c c c
c
c
Referenced Documents
c
Document Namecc Descriptionc
c c
c c
c c
c c
c
c
Reviewers
c
Namec Positionc Datec

c c c
c c c
c c c
c
c

c c c
 
   c c cccccccc  cccc
c c cc
c c c
TA½LE OF CONTENTS

1.c INTRODUCTION............................................................................................................................... 4c
1.1c DOCUMENT PURPOSE ................................................................................................................. 4c
1.2c ACRONYMS AND GLOSSARY ....................................................................................................... 4c
2.c FUNCTIONAL DESIGN .................................................................................................................... 5c
2.1c OVERVIEW ................................................................................................................................. 5c
2.2c PROCESS FLOW DIAGRAM .......................................................................................................... 5c
2.3c PROCESSING LOGIC .................................................................................................................... 6c
2.4c IMPACT ON OTHER CUSTOM MODULES ..................................................................................... 11c
2.5c EXCLUSIONS ............................................................................................................................ 12c
è.c ENTITY RELATIONSHIP .............................................................................................................. 1èc
3.1c ER DIAGRAM ........................................................................................................................... 13c
3.2c CUSTOM OBJECTS .................................................................................................................... 13c
3.3c TABLE & VIEW USAGE ............................................................................................................. 13c
4.c TECHNICAL OVERVIEW.............................................................................................................. 14c
4.1c MAPPING DETAILS & KEY VALIDATION .................................................................................... 14c
4.2c FORMS ..................................................................................................................................... 14c
4.3c CONCURRENT PROGRAM .......................................................................................................... 14c
4.4c WORKFLOW ............................................................................................................................. 14c
4.5c REPORT ................................................................................................................................... 14c
4.6c XML PUBLISHER ..................................................................................................................... 15c
5.c ORACLE SETUPS............................................................................................................................ 16c
5.1c FLEX FIELDS LIST .................................................................................................................... 16c
5.2c MESSAGE DETAILS ................................................................................................................... 16c
5.3c VALUE SETS ............................................................................................................................ 16c
5.4c PROFILE OPTIONS..................................................................................................................... 16c
5.5c LOOKUP DETAILS ..................................................................................................................... 16c
5.6c OTHER CONFIGURATION DETAILS ............................................................................................. 16c
6.c INTEGRATION & DEPENDENCY ................................................................................................ 16c
7.c ASSUMPTIONS................................................................................................................................ 16c
!.1c BUSINESS ASSUMPTIONS .......................................................................................................... 16c
!.2c ORACLE APPLICATION ASSUMPTIONS ....................................................................................... 16c
Ñ.c ISSUES .............................................................................................................................................. 16c
8.1c OPEN ISSUES ............................................................................................................................ 16c
8.2c CLOSED ISSUES ........................................................................................................................ 16c
å.c SIGN OFF ......................................................................................................................................... 17c
10.c APPENDIX ....................................................................................................................................... 17c
10.1c DATA FILE FORMAT ................................................................................................................. 1!c
10.2c SAMPLE CODE/OBJECT NAME FROM 10.! .................................................................................. 1!c

c c c
 
   c c cccccccc  cccc
c c cc
c c c
1.cIntroduction
1.1c Document Purpose

The purpose of this document is to provide a functional overview of the functionality that
would be available through the ATS Custom Form.
This Report displays the critical components added to a WIP job at a particular station.

1.2c Acron ms and Glossar

Term Definition
FRD Fridley

c c c
 
   c c cccccccc  cccc
c c cc
c c c

2.cFunctional Design
c
2.1c Overview
The purpose of this form is to ensure that the right critical components are added to the
assembly. Thus this form provides a check for the user at a particular station to pick correct
critical components for the WIP job. The form also prints the report for the quality and
documentation purpose.

Entire set consists of three forms and three reports.


Forms:
1.c Item Types form: Registers the applicable item types
2.c Station Items form: Inserts critical components at a particular station.
3.c Station Transaction form: Used by user for scanning components.

Reports:
1.c Item List: Lists all critical components for a serialized WIP.
2.c Label: Provides assembly information
3.c Assembly line verification report: Shows scanned critical components.

2.2c Process Flow Diagram

c c c
 
   c c cccccccc  cccc
c c cc
c c c
2.èc Processing Logic

Define Item Types:

1.c Define the item types and provide its description in the Item Types form.

2.c Attach Items to stations.

Attach the items to the stations, where one item can be attached to the multiple stations.
Also provide its item type from the LOV (which pops from the item type form). Check
scannable flag where applicable.

c c c
 
   c c cccccccc  c ccc
c c cc
c c c
3.c Station transaction:

Input Parameters:

Serial Number: Enter the serial number for a particular WIP job
Model Number: Automatically displayed.
WIP Number: Automatically Displayed.
User: Enter user name from the LOV.
Station: Enter the applicable station from LOV.
Printer Name: Enter the destination printer.

The µItem list¶ button now gets activated. Click on this button which would submits two
concurrent requests and populates the item number list. These items are the components in
the WIP job and are also present in the station items list checked with scannable flag.

c c c
 
   c c cccccccc  cccc
c c cc
c c c
The reports for the two concurrent requests are as below:

List of Items that are in WIP components list for the serial number entered and which are
also present in the Station Item list both scannable and non-scannable.

c c c
 
   c c cccccccc  c!ccc
c c cc
c c c
The second report prints the label:

c c c
 
   c c cccccccc  c"ccc
c c cc
c c c
4.c Scan Components:
Scan all components. Scanning the wrong component gives an error. Once all components
are scanned µPrint¶ button gets activated.

5.c Print the Component report:


Push the print button. It would submit a concurrent request and would print the following
report.

c c c
 
   c c cccccccc  cccc
c c cc
c c c
The report printed is as follows:
It provides with the list of the components scanned for a particular serial number
with the user and the station number.

c c cc
6.c Enter a new serial and repeat.

c c c
 
   c c cccccccc  cccc
c c cc
c c c
Additional Functionality:

Not Scanned button: when pressed shows a list of all items yet to be scanned.

Routing Button: routes the component to be scanned to some other station.

2.4c Impact on Other Custom Modules

None

2.5c Exclusions

Nonec

c c c
 
   c c cccccccc  cccc
c c cc
c c c
è.cEntit Relationship
c
è.1c ER Diagram

<ER Diagram listing all tables its primary key, foreign key, unique constraints & mapping
between these tables>

è.2c Custom Objects


c
Tables
c
c ccc<TA½LE_NAME>
Column Name T pe Size Required Validation

Viewsc
c
è.èc Table & View Usage

S No Table/View Name Select Insert Update

c c c
 
   c c cccccccc  cccc
c c cc
c c c

4.cTechnical Overview
4.1c Mapping Details & Ke Validation
c
<Mapping Details between legacy/source & destination tables for interfaces>c
c
4.2c Forms
c
Purpose/Description

<Brief purpose/description regarding form functionality>c


c
La out

<Layout of the Form>c


c
4.èc Concurrent Program
c
Purpose/Description

<Brief purpose/description regarding concurrent program functionality>


c
Parameters

Parameter T pe Validation/Comments
Name

c
c
4.4c Workflow
c
Purpose/Description

<Brief purpose/description regarding workflow process/customization>


c
Process Diagram

<Workflow process diagram>c


c
4.5c Report
c
Purpose/Description
c
<Brief purpose/description regarding Report Functionality>c
c
La out

<Report Layout>
c
Parameters
c c c
 
   c c cccccccc  cccc
c c cc
c c c

Parameter T pe Validation/Comments
Name

4.6c XML Publisher

Purpose/Description
c
<Brief purpose/description regarding Report Functionality>c

Template La out

<XML publisher Template Layout>

Parameters

Parameter T pe Validation/Comments
Name

c c c
 
   c c cccccccc  cccc
c c cc
c c c
5.cOracle Setups
5.1c Flex Fields List
c
c
5.2c Message Details
c
c
5.èc Value Sets
c
c
5.4c Profile Options
c
c
5.5c Lookup Details
c
c
5.6c Other Configuration Details
c
c

6.cIntegration & Dependenc


7.cAssumptions
c
7.1c ½usiness Assumptions
c
c
7.2c Oracle Application Assumptions
c

Ñ.cIssues
c
Ñ.1c Open Issues
c
c
S No Issue Resolution

c
c
Ñ.2c Closed Issues
c
c
S No Issue Resolution

c c c
 
   c c cccccccc  c ccc
c c cc
c c c
S No Issue Resolution

å.cSign Off
c
S No Name Position Date Sign Off /
Mail
29/12/2008

10.c Appendix
c
10.1cData File Format
c
10.2cSample Code/Object Name from 10.7 ± OA0007è.
c
c

c c c
 
   c c cccccccc  cccc