Document Number: Revision Level:

XXXXXX 1 bhaskar

Prepared By/Submission Date:

Title:

HasmanSoft

Bom Interface MD 050

MD050 APPLICATION EXTENSIONS FUNCTIONAL DESIGN

BOM INTERFACE

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

Bhaskar 17-Nov-2011 17-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 Position

Approvers

Name Naga Kishore

Position

Distribution

Copy No. 1 2 3 4

Name Library Master

Location Project Library

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 Solution Design..........................................................................................................................7 Design Approach................................................................................................................7 Detail Design......................................................................................................................8 Test Scenarios.....................................................................................................................9 Assumptions......................................................................................................................10 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 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 pre-configured Items

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. 2. 3. 4. 5. 6. 7. The process should be capable of creating new bom in Oracle Inventory in the specified Organization from a user provided data file. The process should be capable of updating any given attributes of existing Items in Oracle Inventory in the specified Organization from a user provided data file. The process shall be seamlessly automated. The process shall provide choice to users whether the data has to be imported into Oracle using Interface The process shall provide choice to users whether the Items shall be interfaced using Item Templates. The program shall validate the data provided by users and shall interface only valid records. The program shall capture and display the invalid records and the reasons for rejection of such records.

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 Solution Design

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

The interface process has three phases viz. Load, Validate and Interface. 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 or using API based on the choice of the users.

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

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 Item Code Item Description Primary UOM Display Implemented Only Item Num Operation_Seq_Num Component_Item Component_Quantity Auto_Request_Material flag Component_Yeild_Factor Include_In_Cost_Rollup Flag Supply_Type Item Sequence

Purpose and Usage of the Attribute Item Name belongs to the items of finished good Item Description of finished good Primary Unit Of Measure

Routing i.e., operations sequence Item name for purchased item This is the quantity of the Item. Flag to specify to send the material request automatically or not It displays yield percentage Flag to specify to include the cost of the item is rollup or not This value specifies how the Items are issued to the Job, by pull or push. Sub inventory defined for items should exsist in one of these sub inventorys

SUPPLY_SUBINVENT ORY

Check_Atp flag Optional flag Mutually_Exclusive_Options flag SO_BASIS Shippable_Item_Flag

Atp flag is used to check the quantity to not go to negative balance

Flag for Shippable Item. If this flag is not enabled the Item cannot be

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

shipped. For example service Items need not be shipped though used in Order Management. Include_On_Ship_Docs flag Required_To_Ship flag Required_For_Revenue flag

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

Data Validations
Below validations are to be performed on the data before the data is transferred to Staging. (some of these validations can be avoided if the Items are imported using templates) Item Level Validation This validation is performed to ensure the individual attribute values provided in the data file are valid. Below are such validations that need to be performed 1. 2. 3. 4. 5. 6. The Item Code that was provided is valid The primary UOM and Pricing UOM that were provided in the data file are valid The data file contains valid User Item type and Item Status The Supply Type value is valid Default buyer and Planner values are valid The Code combinations for COGS and Sales Account are valid.

Logical Validation This validation is performed to ensure the attribute values provided in the data file are valid with respect to other values in the same record. 1. 2. 3. 4. Item should be exist in organization , Item should be finished good and it should be Bom Allowed checked Stockable & Transactable flags are setup only for Inventory Items Inventory Asset value flag can be enabled only when the Item is Stockable and Transactable

Test Scenarios
S.No 1 Test Scenario Upload Bom that do not exist in Master and Child Organizations without using templates through Execution Parameters Expected Result Bom is successfully created in both Master and Child Organizations as per the attributes

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

S.No 2 Test Scenario 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 do not exist in Master and Child Organizations without using templates through API Upload Bom that exist in Master but not in Child Organization without using templates through API Upload Bom that exist in both Master and Child Organizations without using templates through API Upload Bom that do not exist in Master and Child Organizations 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 Upload Bom that do not exist in Master and Child Organizations using templates through API Upload Bom that exist in Master but not in Child Organization using templates through API Upload Bom that exist in both Master and Child Organizations using templates through API Execution Parameters Expected Result 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 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 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 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

10

11

12

Assumptions

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

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.