fsd ats custom form v1.0

8/8/2019 Fsd Ats Custom Form v1.0

1/17

FSD_CPGF_View_Serial_Numbers_V1.0.doc Page 1 of 17

Functional Specification Document

ATS Custom Form

Oracle R12 Re-Implementation

Submitted to

By

Infosys Technologies Ltd.

Module Code/C & I No Last Updated On


2/17


Document Tracking Information

Document Revision History

Version Date Description Author

1.0 12/10/2008 Base Version Infosys

Referenced Documents

Document Name Description

Reviewers

Name Position Date


3/17


TABLE OF CONTENTS

1. INTRODUCTION ............................................................................................................................... 41.1 DOCUMENT PURPOSE ................................................................................................................. 41.2 ACRONYMS AND GLOSSARY ....................................................................................................... 4

2. FUNCTIONAL DESIGN .................................................................................................................... 52.1 OVERVIEW................................................................................................................................. 52.2 PROCESS FLOW DIAGRAM .......................................................................................................... 52.3 PROCESSING LOGIC .................................................................................................................... 62.4 IMPACT ON OTHERCUSTOM MODULES ..................................................................................... 112.5 EXCLUSIONS ............................................................................................................................ 12

3. ENTITY RELATIONSHIP .............................................................................................................. 133.1 ERDIAGRAM........................................................................................................................... 133.2 CUSTOM OBJECTS .................................................................................................................... 133.3 TABLE &VIEW USAGE ............................................................................................................. 13

4.

TECHNICAL OVERVIEW ............ .............. ............. ............. ............. ............. ............. .............. ..... 14

4.1 MAPPING DETAILS &KEY VALIDATION.................................................................................... 144.2 FORMS..................................................................................................................................... 144.3 CONCURRENT PROGRAM .......................................................................................................... 144.4 WORKFLOW............................................................................................................................. 144.5 REPORT ................................................................................................................................... 144.6 XMLPUBLISHER..................................................................................................................... 15

5. ORACLE SETUPS............................................................................................................................ 165.1 FLEX FIELDS LIST .................................................................................................................... 165.2 MESSAGE DETAILS................................................................................................................... 165.3 VALUE SETS ............................................................................................................................ 165.4 PROFILE OPTIONS..................................................................................................................... 165.5 LOOKUP DETAILS..................................................................................................................... 165.6 OTHERCONFIGURATIONDETAILS............................................................................................. 16

6. INTEGRATION & DEPENDENCY ................................................................................................ 167. ASSUMPTIONS ................................................................................................................................ 167.1 BUSINESS ASSUMPTIONS .......................................................................................................... 167.2 ORACLE APPLICATION ASSUMPTIONS ....................................................................................... 16

8. ISSUES .............................................................................................................................................. 168.1 OPEN ISSUES............................................................................................................................ 168.2 CLOSED ISSUES ........................................................................................................................ 16

9. SIGN OFF ......................................................................................................................................... 1710. APPENDIX ....................................................................................................................................... 17

10.1 DATA FILE FORMAT ................................................................................................................. 1710.2 SAMPLE CODE/OBJECTNAME FROM 10.7.................................................................................. 17


4/17


1.Introduction

1.1 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.2 Acronyms and Glossary

Term Definition

FRD Fridley


5/17


2.Functional Design

2.1 OverviewThe 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 correctcritical components for the WIP job. The form also prints the report for the quality anddocumentation purpose.

Entire set consists of three forms and three reports.

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

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

2.2 Process Flow Diagram


6/17


2.3 Processing Logic

Define Item Types:

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

2. 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). Checkscannable flag where applicable.


7/17


3. Station transaction:

Input Parameters:

Serial Number: Enter the serial number for a particular WIP jobModel 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 inthe WIP job and are also present in the station items list checked with scannable flag.


8/17


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.


9/17


The second report prints the label:


10/17


4. Scan Components:Scan all components. Scanning the wrong component gives an error. Once all components

are scanned Print button gets activated.

5. Print the Component report:Push the print button. It would submit a concurrent request and would print the following

report.


11/17


The report printed is as follows:

It provides with the list of the components scanned for a particular serial numberwith the user and the station number.

6. Enter a new serial and repeat.


12/17


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.4 Impact on Other Custom Modules

None

2.5 Exclusions

None


13/17


3.Entity Relationship

3.1 ER Diagram

3.2 Custom Objects

Tables

Column Name Type Size Required Validation

Views

3.3 Table & View Usage

S No Table/View Name Select Insert Update


14/17


4.Technical Overview

4.1 Mapping Details & Key Validation

4.2 Forms

Purpose/Description

Layout

4.3 Concurrent Program

Purpose/Description

Parameters

Parameter

Name

Type Validation/Comments

4.4 Workflow

Purpose/Description

Process Diagram

4.5 Report

Purpose/Description

Layout

Parameters


15/17


Parameter

Name


4.6 XML Publisher

Purpose/Description

Template Layout

Parameters

Parameter

Name



16/17


5.Oracle Setups

5.1 Flex Fields List

5.2 Message Details

5.3 Value Sets

5.4 Profile Options

5.5 Lookup Details

5.6 Other Configuration Details

6.Integration & Dependency

7.Assumptions

7.1 Business Assumptions

7.2 Oracle Application Assumptions

8.Issues

8.1 Open Issues

S No Issue Resolution

8.2 Closed Issues



17/17

FSD CPGF View Serial Numbers V1.0.doc Page 17 of 17


9.Sign Off

S No Name Position Date Sign Off /

Mail

29/12/2008

10. Appendix

10.1Data File Format

10.2Sample Code/Object Name from 10.7 OA00073.