Client MOTOROLA Functional Specification Item Conversion Upgrade 10.7 to11.5.

Author Creation !ate %ast Updated

: : :

.!eepi"a #5$Apr$#005 #5$Apr$#005

%ast Updated &' : (ersion : !raft 1

Approvals:

Name

Title

Date

Functional Specifications

Document Control

Change Record
Date Author Version Change Reference

Reviewers
Name osition

)age$ #

Functional Specifications

Distri!ution

Cop" No#

Name

Location

Contents
Approvals:............................................................................................1 Document Control.............................................................................................2 Topical Essay....................................................................................................4 Basic Business Needs........................................................................................5 Ma or !eatures..................................................................................................." #tem Conversion:........................................................................................." Assumptions......................................................................................................$ %re&re'uisites.....................................................................................................$ De(initions.........................................................................................................) *ser %rocedures.................................................................................................+ E,amples.........................................................................................................1Business rules..................................................................................................11 Tec.nical /vervie0........................................................................................12 Navi1ation 2o1ic.............................................................................................13 Conversion Description...................................................................................14

)age$ *

Functional Specifications

4ource5Tar1et Application #nte1ration......................................................14 Data !eed !ormat5Mappin1 ......................................................................15 Data Trans(ormation .................................................................................15 Data Trans(er Mec.anism.........................................................................15 #nter(ace 2o1ic..........................................................................................15 !re'uency5 6un Time................................................................................1" 6esponse time............................................................................................1" 2aunc. %arameters....................................................................................1" 2o1 /utput................................................................................................1" 6estart %rocedures ...................................................................................1" Error 7andlin15Mana1ement56ecovery....................................................1$ 8or9(lo0 %rocess De(inition..........................................................................1$ /pen5Closed #ssues.........................................................................................1+ Closed issues.............................................................................................1+

Topical Essay
+he purpose of this delivera,le is to document the functional specifications for the conversion of items and their components from the 10.7 to 11.5.7. -e can import items from an' source into .racle Inventor' and .racle /ngineering using Item .pen interface. -ith this interface 0e can convert inventor' items from another inventor' s'stem1 migrates assem,l' and component items from a legac' manufacturing s'stem1 convert purchased items from custom purchasing s'stem and can import data from )roduct 2anage !ata 2anagement )ac"age.

)age$ 3

Functional Specifications

Basic Business Needs

+his !ata Conversion document provides the features 'ou need to satisf' the follo0ing ,asic ,usiness needs. -hen 0e import an item 0e should ensure that all the items that are imported are validated 4ou 0ill ,e a,le to address the follo0ing ,usiness re5uirements: Convert over from source to .racle 11i all the Items1 attri,utes1 components and all other related information. +he !ata Securit' and Control should ,e maintained at the time of +ransfer of data from source to destination. 2apping all the source columns 0ith the destination columns. e5uired Columns are included or defaulted. Control levels are reflected in item attri,ute values.

)age$ 5

Functional Specifications Status control settings for status attri,utes are maintained. Interdependences ,et0een item attri,ute values are maintained. /rror 2essages should ,e stored in a detailed manner and in the )roper +a,les.

Major Features
$tem Conversion:
+his conversion 0ill transfer all the items and their components from 10.7 6source7 to .racle 11i. +he Item open interface can process this conversion. -hen 'ou import items from an e8ternal s'stem through Item Interface1 0e can create ne0 items in 2aster organi9ation1 update the e8isting items and assign the e8isting items to other organi9ations. -e can specif' values for all the attri,utes or 0e can :ust specif' fe0 attri,utes and let the remainder default or null. +he Item open Interface insures that 'our imported items contain the same detail as creating and updating of Item Information.

)age$ ;

Functional Specifications +he Item open Interface lets 'ou import 'our items from e8ternal s'stem into .racle Inventor'. 4ou can also update the item information if there are an' updates in the e8ternal s'stem1 ,' identif'ing that particular item record. As'nchronous )rocessing of Items: It means that1 'ou can process multiple items simultaneousl' using the Item open interface.

!etailed and translata,le error 2essages: If 'our import fails1 the Item open Interface 0ill report detailed and translata,le error messages. +he error message 0ill identif' the severit' of the error and scope 0ith 0hich the error affects other record that 'ou have tried to import in this ,usiness o,:ect.

Assumptions
+his Functional specification document assumes that the follo0ing setup statements are true: 1. Inventor' setup complete. #. -e 0ill use the .racle Item Import Interface.

Pre-requisites
1. Inventor' setup complete. #. See pre$re5uisites for the .racle Item Import Interface.

)age$ 7

Functional Specifications *. Standard operations and alternates has to ,e specified.

Definitions
1. $nventor" Organi%ation: A ph'sical or logical 0arehouse<location to manage inventor'. An organi9ation that trac"s inventor' transactions and ,alances1 and<or that manufactures or distri,utes products. #. $nventor" item: Items 'ou stoc" in inventor'. 4ou control inventor' for inventor' items ,' 5uantit' and value. +'picall'1 the inventor' item remains an asset until 'ou consume it. 4ou recogni9e the cost of an inventor' item as an e8pense 0hen 'ou consume it or sell it. 4ou generall' value the inventor' for an item ,' multipl'ing the item standard cost ,' the 5uantit' on hand. *. $tem: An'thing 'ou ma"e1 purchase1 or sell1 including components1 su,assem,lies1 finished products1 or supplies. .racle 2anufacturing also uses items to represent planning items that 'ou can forecast1 standard lines that 'ou can include on invoices1 and option classes 'ou can use to group options in model and option class ,ills.

)age$ =

Functional Specifications 3. $tem attri!ute: Specific characteristics of an item1 such as order cost1 item status1 revision control1 C.>S account1 etc.

ser Procedures
+he user procedures for the ,usiness process are as follo0s: ?A

)age$ @

Functional Specifications

E!amples
?A

)age$ 10

Functional Specifications

Business rules
&usiness logic help to model the ,usiness. It includes all constraints and considerations that the ,usiness needs to maintain and process data successfull'. +his implies that certain rules must ,e imposed on incoming data 6,usiness o,:ects7 to ensure its validit' 0ithin the conte8t of the ,usiness. All Item1 Item Components and its Attri,utes 0ill ,e transferred over from 10.7 to .racle 11i. It is still to ,e determined 0hat Inventor' items 0ill ,e mapped to 0hat organi9ations. +his should happen after C )1. /ver'thing 0ill ,e a straight conversion. +he ,usiness plans to time to the implementation dates and /C.s 0ith the conversion from legac' to .racle Applications.

)age$ 11

Functional Specifications

Tec"nical #$er$ie%
-e ta"e the data into a flat file. From there the data is stored into staging ta,le. Aere 0e do the validations and error out the records1 0hich do not suit1 to our .racle Inventor'. +he error records are processed again and ma"e suita,le changes to them1 0ithout modif'ing the original information 6,' mapping or through some other procedures7. +hen data is loaded into interface ta,le from 0hich 0e import the items to out .racle Inventor' through BImport ItemC program. +he ta,les involved in Item Import process are: 2+%DS4S+/2DI+/2SDI?+/ FAC/ : Stores definition of items information temporaril' ,efore loading the data into .racle Inventor' 2+%DS4S+/2DI+/2SD& 2+%DS4S+/2DI+/2SD+% : Stores definition for Inventor' Items : Stores translated description columns for items.

)age$ 1#

Functional Specifications

Na$i&ation 'o&ic
To import items: 1. ?avigate to the Import Item 0indo0. #. Indicate 0hether to import the items ,elonging to all the or onl' current organi9ation.

)age$ 1*

Functional Specifications

Con$ersion Description
+he Item conversion is a one time conversion of Items and its components from legac' data,ase to the .racle Application data,ase for setup.
&ource'Target Application $ntegration Application $ntegration &cope

Name

&ource Application

&ource Application Version

&ource latform

Target Application .racle Applications 11i 611.5.77

Target latform

(re)uenc"

(ile si%e

* of tr+

Item Conversion

10.7

1 time

)age$ 13

Functional Specifications ESource<+arget Application

Data (eed (ormat'Mapping ,Data (eed (ormat-

e5uirements<!ependenciesF

Column

osition .(rom'To/ $

Ma+ length

Validation .LOV/

Data t"pe

Re)uired

.rgani9ation code Segment1

(archar#6*7

4es

30

(archar#6307

4es

Data Mapping
0ow does it map to Oracle 1R 2 .Ta!le3Column/ 2aps directl' 0ith .rgani9ation I! in interface ta,le 2aps directl' 0ith segment1 in interface ta,le

Column in data feed

Value

Remar4s

.rgani9ation code

Segment1

Item ta,le fields 0ill map directl' over from Source to .racle 11i.

Data Transformation
?one

Data Transfer Mechanism

+e8t or !at File Control File Staging +a,le Interface +a,le &ase +a,le

$nterface Logic
-e are transferring the data from the flat file to the staging ta,le using a Control file. -hen the data has ,een received into the staging ta,le1 0e have to do the re5uired validations on that data and transfer the data from staging ta,le to interface ta,le ,' use of )%<SG% Scripts. &' running Item Import )rogram1 0e import the items from Interface ta,le to ,ase ta,le.

)age$ 15

Functional Specifications

(re)uenc"' Run Time

.ne +ime )rocess

Response time

Launch arameters
+he t'pical launch parameters for this interface are:

&e)uence

arameter Name

arameter Description

Re)uired2 .5es'No/

Default Value

Value &et

Comments

Log Output
+he log output consists of 6Choose from or add to list7: +iming statistics $ ?<A

(olume statistics $ ?<A /rror messages for records 0hich are not loaded. ?um,er of records loaded in .racle ?um,er of records re:ected.

Restart rocedures
estart procedures for Item interface failed are as follo0s

)age$ 1;

Functional Specifications

1rror 0andling'Management'Recover"
In case of an' e8ceptions1 Chec" from the mtlDs'stemDerrors and trace the error In case error correction is needed1 choose from the follo0ing list In case1 alerts need to ,e sent1 list

&ecurit" Considerations

(or)flo% Process Definition

+he -or"flo0 /ngine manages all automated aspects of a 0or"flo0 process for each item. +he engine is implemented in serverHside )%<SG% and should ,e activated 0henever a call to a 0or"flo0 procedure or function is made. Since the engine is em,edded inside .racle =1 if the -or"flo0 server goes do0n for an' reason1 .racle = should ,e a,le to manage the recover' and transactional integrit' of an' 0or"flo0 transactions that 0ere running at the time of the failure. Additionall'1 -or"flo0 /ngines should ,e set up as ,ac"ground tas"s to perform activities that are too costl' to e8ecute in real time. It should manage1 the state of all activities for an item1 and in particular1 determines 0hich ne0 activit' to transition to 0henever a prere5uisite activit' completes. It 0ill automaticall' e8ecutes function activities 6e8ecution is either immediate or deferred to a ,ac"ground engine7 and sends notifications. It maintains a histor' of an activit'Cs status. It must detect error conditions and e8ecute error processes.

)age$ 17

Functional Specifications +he state of a 0or"flo0 item should ,e defined ,' the various states of all activities that are part of the process for that item.

Create )rocess Start )rocess Complete Activit' Assign Activit' Aandle /rror Suspend )rocess esume )rocess A,ort )rocess

)age$ 1=

Functional Specifications

#pen*Closed +ssues
Open issues
Num $ssue description Resolution Owner

Closed issues

Num

$ssue description

Resolution

Owner

)age$ 1@