Beruflich Dokumente
Kultur Dokumente
HasmanSoft
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.
SR#
Date
Author
Version
Change Reference
Reviewers
Name Naga Kishore Shaker pasha Jashwanth Anil Position
Approvers
Position
Distribution
Copy No. 1 2 3 4
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.
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.
Contents
Document Control......................................................................................................................2 Topical Essay.............................................................................................................................5 Business Requirements .............................................................................................................6 Solution Design..........................................................................................................................7 Design Approach................................................................................................................7 Functional Design...............................................................................................................9 ............................................................................................................................................11 Test Scenarios...................................................................................................................11 Assumptions:.....................................................................................................................12 Open Issues..............................................................................................................................13 Closed Issues............................................................................................................................14 Review Log..............................................................................................................................15
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.
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.
The process should be capable of creating costs of items in Oracle Inventory in the specified Organization from a third party system provided data file. The program shall validate the data provided by third party system and shall load only valid records. The program should be capable of updating the cost. The program shall capture and display the invalid records and the reasons for rejection of such records. The process shall be seamlessly automated through API.
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.
Design Approach Below diagram explains the process of interfacing costing data into Oracle.
Flow Diagram
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.
This symbol indicates the actions to be done through standard program provided by oracle.
The interface process has three phases viz. Load, Validate and Interface. Load Process: In this process the third party system provided data will be loaded into a custom table. Validate Process: In this process the third party system data will be validated and successfully validated records are moved to a staging table. If any records do not pass validation, they are flagged as error records and they are populated into error data table. Interface Process: In this process the successfully validated data is loaded into oracle database.
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.
Purpose and Usage of the Attribute The Organization in which the Item data has to be loaded / updated The Item Name for which we need to give the cost.
Data Validation If the organization code is valid then get the organization code. If it is not valid then populate an error message. If the item code is valid then get the item code. If it is not valid then populate an error message. If the cost type is valid then get the cost_type_id. If it is not valid then populate an error message.
Item Code
Cost type
A cost type is a set of costs uniquely identified by name. In Standard Costing method, Frozen is the seeded cost type.
Use_default_controls
If this Flag is enabled we cannot modify the cost controls or we cannot create user entered costs. This Flag indicates whether costs are based on a roll up of the items. This flag is enabled only for make items. This Flag is enabled for the items which are included in rollup of the cost. (Buy items). The cost element is used to get the unit cost of the item. Sub-elements can be used as smaller classifications of the cost elements. Each cost element must be associated with one or more sub-elements. This attribute is for identifying whether the given rate is for single item or lot of items. This attribute gives the rate of an Item.
Based_on_rollup
Include_in_rollup Cost-element
If flag is Y then Y else N. If the cost element is valid then get the cost element code. If it is not valid then populate an error message. If the sub element is valid then get the resource code. If it is not valid then populate an error message. If the basis is valid then get the basis code. If it is not Rate must not be null.
Sub-element
Basis Rate_or_amount
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.
Data Validations
Below validations are to be performed on the data before the data is transferred to Staging. Below are such validations that need to be performed 1. 2. 3. 4. 5. We need to check whether the Organization Code provided in the Flat file is valid or not. We need to check whether the Item Code provided in the Flat file is valid or not. We need to check whether the cost types provided in the Flat file are in the list of values. We need to check whether the cost elements provided in the Flat file are in the list of values. We need to check whether the sub elements provided in the Flat file are in the list of values.
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. Use_default_controls: If this Flag is Y we cannot create user entered costs. Based_on_rollup: This flag is Y only for make items. Include_in_rollup: This flag is Y only for buy 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.
Test Scenarios
S.No 1 2 3 4 Test Scenario Creating new costs for already existing item using standard interface program. Creating new costs for already existing item using API. Updating new costs for already existing item using standard interface program. Updating new costs for already existing item using API. Execution Parameters Expected Result Costs for the given items are successfully loaded as per the attributes provided in data file. Costs for the given items successfully loaded as per attributes provided in data file. Costs for the given items successfully updated as per attributes provided in data file. Costs for the given items successfully updated as per 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.
Assumptions:
1. If the given data is not valid, then the data is not loaded into the staging table.
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.
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.
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.
Review Date
21-112011 21-112011
Review Comments
Reviewed By
Anil, jaswanth venkatesh
Action Taken
Closed Date
23-112011 23-112011
Correction Effort
corrected corrected
Put the test scenarios and modifications in design Changes in topical essay,functional design,validations.
yes yes
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.