Document Number: Revision Level: 0 Satyanarayana K Bhaskar T Pavan A

Prepared By/Submission Date:

Title:

HasmanSoft

Bom Interface MD 050

MD050 APPLICATION EXTENSIONS FUNCTIONAL DESIGN

BOM INTERFACE

Author:

Satyanarayana K Bhaskar T Pavan A

Creation Date: Last Updated: Document Ref: Version: Review:

18-Nov-2011 18-Nov-2011 1.0

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050 Document Control

Change Record
3

SR#

Date

Author

Version Change Reference

Reviewers
Name Naga Kishore G Shaker Pasha Anil Position

Approvers

Name Naga Kishore

Position

Distribution

Copy No. 1 2 3 4

Name

Location

Note To Holders:

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050

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.

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050

Contents

Document Control......................................................................................................................2 Topical Essay.............................................................................................................................5 Business Requirements .............................................................................................................6 Design Approach................................................................................................................6 Detail Design......................................................................................................................8 Test Scenarios...................................................................................................................10 Assumptions......................................................................................................................11 Open Issues..............................................................................................................................12 Closed Issues............................................................................................................................13 Review Log..............................................................................................................................14

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050 Topical Essay

A bill of materials (BOM) is a list of the parts or components that are required to build a product. The BOM provides the manufacturer's part number (MPN) and the quantity needed for each component. A bill of material is a list or Items associated with a parent Item, such as an assembly, and information about how each item relates to the parent item. A single level BOM consists of one parent Item and its immediate component Items. Multilevel BOMs are displayed by linking together single level BOMs stored in the system. A subassembly is both a parent and a component. All items in a BOM model, including the parent Item being configured, must be defined in the Item Master and enabled in the Inventory Organization where BOM Model is created A BOM Model can be shared among other Inventory Organizations by creating common bills. After a valid combination of options is selected from BOM Model, a Standard BOM is created to guide manufacturing planning and execution. Repetitive combinations of option selections can be stored and retrieved as preconfigured Items The Bills of Material Object Interface insure that your imported bills of material contain the same detail as those you enter manually in the Define Bill of Material form. The Bill of material open Interface programs allow you to import bill information into standard base tables

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050 Business Requirements

Typically, user requirements for the bom Interface will be as under 1. The program shall be seamlessly automated. 2. The program should be capable of creating new bill of materials in Oracle from a user provided data file. 3. The program shall be capable of updating new components of bill of material 4. The program should be capable of updating the attributes of components present in the bill of material 5.The program shall validate the data given by the user in the flat file 6. The program shall capture and display the invalid records and the reasons for rejection of such records Solution Design 7. The program shall be creating bom in master and child organization for items

Design Approach

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050

Below diagram explains the process of interfacing Item data into Oracle. Flow Diagram

Data file from user

Move to staging

int erf ac e

Move to interface

Load data Using control file

Validate data

Load process

validation process

Data valid ?

Standard import

interface process

Correct data

Populate error data

End

Error data report

The interface process has three phases viz. Load, Validate and Interface.

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050

Load Process: In this process the user provided data will be loaded into a custom table. Validate Process: In this process the user data will be validated and successfully validated records are moved to a custom staging table. If any records do not pass validation, they are flagged as error records and the custom error data table. In this table the errors will be records. Interface Process: In this process the successfully validated data is interfaced into oracle either using the interface program based on the choice of the users.

Detail Design
The interface process is explained in detail as below.

User Data File Specifications

Users shall provide data in a csv file format. Csv file can be generated by saving an excel data file as csv (comma separated values) format. The data file shall have values for below attributes of Items. Below table explains the purpose and usage of each Attribute that is included in the data file

Attribute

Purpose and Usage of the Attribute

Validation should be valid

Organization code Assembly Item Code

Organization in which bom should be inserted

the organization code provided

Item Name belongs to the item code should be valid and it should exsist in the items of finished good
particular organization

Item Description Display Implemented Only

Item Description of finished good Future and current, Current , display should be in the list of values All If implemented only check box is unchecked then component is on pending engineering change order(eco) Item Sequence Routing sequence i.e., operations Operation sequence no
should be in list of values defined in sequence defined in routing

Item Num Operation_Seq_Num

Component_Item

Item name for purchased item should exsist and the item type should be item and Subassembly Item

purchased item and it shoul be in the respective organization

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050

Component_Quantity This is the quantity of the if the uom is in each. The quantity should be not be Item.
null .

Auto_Request_Materia l flag

Flag to specify to send the material request automatically or not

: yield should be not null and should be grater than zero and should be less than or equal to 1 .

Component_Yeild_Fact It displays yield percentage or

Include_In_Cost_Rollup Flag to specify to include the the item with item type Flag cost of the item is rollup or purchased item is checked with include in cost rollup not Supply_Type This value specifies how the supply type provided should Items are issued to the Job, be valid and it should be in the list of values by pull or push. To send & receive unrestricted goods to subinventories. the any

Supply_Subinventory

Check_Atp flag

To check whether to perform an ATP check on the component. Default Check ATP flag is YES. The Optional field indicates whether the component is mandatory or optional

Optional flag

Mutually_Exclusive_Op Choose any number or no tions flag option on the option class bill. Default choose at least one option class bill SO_BASIS Oracle order management it should be in the list of can override the default values. quantity for the option class . Flag for Shippable Item. If this flag is not enabled the Item cannot be shipped. For example service Items need not be shipped though used in Order Management.
So_Basis should be valid and

Shippable_Item_Flag

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050

Include_On_Ship_Docs flag To check weather print the components on external shipping document. Such as pack slips and commercial invoices .Default is off. To check whether the component is required to ship the order. To check the component is required to recognize revenue before ship the order.

Required_To_Ship flag

Required_For_Revenu e flag

User Parameters
The Program shall have the below parameters based on the requirements mentioned above 1. Import Method (Values in LOV: Standard Interface) 2. Use Item Template (Values in LOV: Yes, No)

Test Scenarios
Sino 1 Test Scenario Upload Bom that do not exist in Master and Child Organizations without using templates through standard interface program Upload Bom that exist in Master but not in Child Organization without using templates through standard interface program Upload Bom that exist in both Master and Child Organizations without using templates through standard interface program Upload Bom that exist in Master but not in Child Organization using templates through standard interface program Upload Bom that exist in both Master and Child Organizations using templates through standard interface program Execution Parameters Expected Result Bom is successfully created in both Master and Child Organizations as per the attributes provided in data file Bom is successfully created in the Child Organization as per the attributes provided in data file Bom attributes are successfully updated in specified Organizations as per the attributes provided in data file Bom is successfully created in the Child Organization as per the attributes provided in data file Bom attributes are successfully updated in specified Organizations as per the attributes provided in data file

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050

Assumptions
None

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050 Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050 Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.

Bom Interface MD 050 Review Log

Review Date

SR #

Section/Page Review Reference in Doc/Code Comments under Review

Reviewe d By

Review Effort (in Min)

Action Taken

Closed Date

Correction Effort

PROPRIETARY NOTE: This contains information proprietary to Hasman Software Solutions Pvt Ltd. Any disclosure or use is expressly prohibited, except upon written permission by Hasman Software Solutions Pvt Ltd.