Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« May 2014 | Main | July 2014 »

June 26, 2014

A Vendors Guide for Understanding BI Deployments - Business v/s IT

Coming back from a recent onsite assignment, I realized how difficult it was being a BI implementation vendor. More so in a world where the Business and IT teams of the same organization view and evaluate the same BI application/platform using different yardsticks.

So what is it that makes these two different views so important to understand in order to develop a solid, easy to use and balanced BI platform which enables an organization to move forward intelligently and without hiccups?

In my experience the need for and value added by BI implementations is looked at differently by Business and IT against the following


1. Solution Architecture: Business executives require a solution which is easy to translate for the users and requires minimal overhead. IT on the other hand would be primarily concerned with the safety of the data and robustness of the solution

2. Data Access: Business users are more interested in the time taken for retrieving data and are looking for a solution which would provide them with answers in a matter of seconds. IT is more inclined to look at the solution more from the point of data security ensuring that no sensitive information is being tapped into apart from what is required as part of the Business requirements

3. Self Service and Flexibility: Business expects the BI solution to be one self-service one - where they can perform the required operations (say generating a report) without any help. IT on the other hand want the platform to be flexible enough to cater to the future needs of the organization

4. Modes of Delivery: In today's global business landscape executives are on the move most of the time and hence prefer critical reports to be delivered on their smartphones and tablets. With the concept of Bring Your Own Device gaining momentum in the West the IT Department prefers limiting the different devices that can be connected to the official network to aid the integration with the enterprise security model

5. Solution Benefits: Consumable reports for Business users at all levels helping in the decision making process is the expectation from the Business side whereas IT is more focused on the impact of the data volumes and the ease with which the solution integrates with the existing infrastructure and data sources

6. Long Term View: From the Business perspective a sustainable and flexible solution is important which helps in cutting the cost and time associated to user training which maybe required after iterative design changes. IT on the other hand thinks more about the number of vendors it would have to manage and the scalability of the solution

Though the priorities of these two sides are often at odds with each other both Business and IT provide a valuable perspective to BI deployments. As a vendor, understanding both the sides and facilitating collaboration is the best opportunity for long-term growth and success.

 


 

June 19, 2014

More on Oracle Project Manufacturing - A complete solution for Project Manufacturing based industries (Project Procurement)

Guest Post by 
Srushti Gogate, Senior Associate Consultant, Infosys Limited


In the earlier blog we have got ourselves acquainted with the project based procurement for Inventory items using PJM. In this one, we shall throw some light on the below:

1. Inter and Intra project transfers.

2. Track customer orders for specific projects in combination with Oracle Order Management
Inter and Intra project transfers

Project transfers basically involve transfer of inventory material either within the project i.e. between different tasks of the same project or between two different projects. This is basically similar to sub-inventory transfers performed in Inventory the only addition being PJM facilitates transfer of material/inventory against projects.

Project transfers are typically used when common material purchased in bulk lying in the inventory needs to be used for specific projects as and when required. It is also used in case there exists excess material against a project which can be utilized for another project having similar requirement. PJM thus enables transfer of the material at a specific project locator to another project avoiding the need to purchase extra material.

PJ also facilitates mass transfers which allows users to transfer all the items from one project to the other. Either the on hand of all items can be transferred or all items of a specific item category from one project to the other.
Mentioned below are the steps to be followed for project transfers using PJM
1. Enter item that needs to be transferred, choose the sub inventory in which the on hand exists.
2. Enter the project locator at which the material is located (Row, Rack, Bin, From Project and Task Number)
3. Enter the To Project and task i.e. the project and task on which the material is to be transferred.
4. Save the transaction
5. This will increase the on hand for the item against the To Project and reduce the on hand of the From Project
6. Run cost collection manager to collect cost against project and then run transaction import.
7. This will result in cost getting collected against the respective projects.
Now that we have a fair idea about the integration of Oracle Projects with Inventory and Purchasing module enabled by PJM, we will look at the integration with Order management facilitated by PJM.

Track customer orders for specific projects in combination with Oracle Order Management

There does not exist a very tight integration between Oracle Projects and Order Management. PJM simply enables users to track customer orders against specific projects. This can be achieved by referencing the Sales Order Lines with project and task reference. This reference flows to the child shipment lines as well.

The billing however needs to be done either based on sales order lines or from Oracle Project Billing. Customization needs to be done in case the users need to achieve Sales Order based Project Billing.

PJM supports drop shipment where the PR/POs are created from Sales Orders with Project and task reference flowing from the Sales order lines. The project costs will be collected after PO receipt and then standard Order Management or oracle project billing functionality can be used for invoicing.

Order Management can also be used in order to process Project RMAs. Whenever a RMA line is created by entering Sales Order line, the project and task reference also flows into the RMA line. After this the RMA receipt is done for which the same project and task default into the project locator.



Thus this section tells us how PJM enables user to perform project transfers  for Inventory items and track the customer orders against the project in conjunction with Order Management module

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter