Is there an equivalent to the AIMBR.100 Application Setup template?
OUM contains an Application Setup Document template associated with task DS.030 Define Application Setups, which is comparable to the AIM BR.100. The template is product agnostic and can be tailored to address any applicationproduct. The guidance for tailoring the generic template is included in the Yellow Notes included in the template itself.
If you don’t see the Yellow Notes, select Tools->Options from the MS Word menu, select the View tab, and Select Hidden Text for viewing. Similar templates for documenting setup information and parameters are also provided for the following tasks:RA.040 Define Business Data StructuresDS.010 Define Business Data Structure Setups
Is there an equivalent to the AIM RD.020 Business Process Baseline template?-
There are no equivalent Process Questionnaires in OUM. In OUM, the client's future business processes and associated configuration decisions are discussed during preparation of the RD.011 Future Process Model.
Saturday, December 31, 2011
Wednesday, December 28, 2011
Oracle iSetup -- Templates Table
General Foundation----> This Selection Set is used to migrate AOL Foundation set ups.
Product Foundation----> This Selection Set is used to migrate Foundation set up needed before migrating any other setup data for other products.
Organization Structure--->This Selection Set is used to migrate the Organization Structure setup
All Profile Options----> This Selection Set is used to migrate all exportable profile options.
Employees----> This Selection Set is used to migrate Employees data.
Financials Setup----> This Selection Set is used to migrate Financials setup.
General Ledger Daily Rates----> This Selection Set is used to migrate General Ledger Daily Rates setup.
Suppliers----> This Selection Set is used to migrate Suppliers setup.
Discrete Mfg. and Distribution----> This Selection Set is used to migrate the Discrete Manufacturing and Distribution setups.
Financials Operating Unit Level Setup----> This Selection Set is used to migrate operating unit level setups in Oracle Payables, Oracle Receivable and Cash Management modules.
Payroll Element----> This Selection Set is used to migrate HRMS Payroll Elements.
Australian Leave Liability----> This Selection Set is used to migrate Australian leave liability setup.
Profitability Manager Setups---->This Selection Set is used to migrate Profitability Manager setups.
Transfer Pricing Setups---->This Selection Set is used to migrate Transfer Pricing Setups.
Projects Setup----> This Selection Set is used to migrate Projects setup.
Personalizations----> This Selection Set is used to migrate Personalizations
XML Publisher----> This Selection Set is used to migrate XML Publisher Metadata, Templates, Translations, XML Sample and Schema
Workflow Business Event System Objects----> This Selection Set is used to migrate Workflow Business Event System Objects Definitions
Workflow Definitions----> This Selection Set is used to migrate Workflow Definitions.
Lease Management Setups----> This Selection Set is used to migrate Lease Management Setups.
Oracle iSetup-- Introduction
Oracle iSetup, a data migration and reporting tool, is a part of the Oracle E-Business
Suite.
This tool consists of the Migrator and the Reporter:
• The Migrator helps you to migrate data from one instance of the Oracle E-Business Suite to
another. Following are the steps to migrate data:
• Extract select data from an Oracle E-Business Suite instance.
• Transform select attributes of the extracted data objects as per your requirements.
• Load data to the target Oracle E-Business Suite instance.
The Reporter helps to generate reports:
• Generate reports on the extracted data.
• Compare two sets of extracted data to identify differences.
Note: Transforming the attributes is an optional step.
There are many scenarios where Oracle iSetup can be used. Following are some of these:
Migrate Data
The CRP instance is configured and ready for test by the quality team. Then now:
1. Migrate select configuration to the test instance.
2. After testing, modify the configuration in the CRP instance.
3. Migrate the configuration to the production instance.
Suite.
This tool consists of the Migrator and the Reporter:
• The Migrator helps you to migrate data from one instance of the Oracle E-Business Suite to
another. Following are the steps to migrate data:
• Extract select data from an Oracle E-Business Suite instance.
• Transform select attributes of the extracted data objects as per your requirements.
• Load data to the target Oracle E-Business Suite instance.
The Reporter helps to generate reports:
• Generate reports on the extracted data.
• Compare two sets of extracted data to identify differences.
Note: Transforming the attributes is an optional step.
There are many scenarios where Oracle iSetup can be used. Following are some of these:
Migrate Data
The CRP instance is configured and ready for test by the quality team. Then now:
1. Migrate select configuration to the test instance.
2. After testing, modify the configuration in the CRP instance.
3. Migrate the configuration to the production instance.
Saturday, December 24, 2011
Oracle Unified Methodology
Oracle®Unified Method (OUM) is to support the entire Enterprise IT lifecycle, including support for the successful implementation of every Oracle product.
We can tailor OUM to support our specific project situation. With its ready-made templates, guidelines, and scalable work breakdown structure, OUM provides the programmatic tools that is used to manage the risks associated with our project
OUM includes three Focus Areas – Manage, Envision, and Implement.
OUM's Manage Focus Area provides a framework in which all types of projects can be planned, estimated, controlled, and completed in a consistent manner.
OUM’s Envision Focus Area deals with development and maintenance of enterprise level IT strategy, architecture, and governance. Envision also assists in the transition from enterprise-level planning and strategy activities to the identification and initiation of specific projects.
The Implement Focus Area provides a framework to develop and implement Oracle-based business solutions with precise development and rapid deployment.
We can tailor OUM to support our specific project situation. With its ready-made templates, guidelines, and scalable work breakdown structure, OUM provides the programmatic tools that is used to manage the risks associated with our project
OUM includes three Focus Areas – Manage, Envision, and Implement.
OUM's Manage Focus Area provides a framework in which all types of projects can be planned, estimated, controlled, and completed in a consistent manner.
OUM’s Envision Focus Area deals with development and maintenance of enterprise level IT strategy, architecture, and governance. Envision also assists in the transition from enterprise-level planning and strategy activities to the identification and initiation of specific projects.
The Implement Focus Area provides a framework to develop and implement Oracle-based business solutions with precise development and rapid deployment.
Oracle Unified Methodology- IMPLEMENT FOCUS AREA
IMPLEMENT FOCUS AREA --PHASES
OUM organizes the delivery of software implementation projects along several phases - indicators of the progress of the project. Each of these phases culminates in an anchor point milestone. These milestones, adopted as phase gates by the Unified Process and by Oracle Unified Method, were taken directly from the Spiral Model Anchor Point Milestones that were initially developed in a series of workshops by the USC Center for Software Engineering and its government and industrial affiliates. For further reading on milestones, see "Anchoring the Software Process."The milestones serve to establish exit criteria for each phase and provide an opportunity to evaluate the project's progress and the readiness of the project to commit resources to begin the subsequent phase.
The five Oracle Unified Method phases:
[A] Inception Phase
[B] Elaboration Phase
[C] Construction Phase
[D] Transition Phase
[E] Production Phase
Oracle Unified Methodology - Implementation Focus - Phases
OUM organizes the delivery of software implementation projects along several phases - indicators of the progress of the project. Each of these phases culminates in an anchor point milestone. These milestones, adopted as phase gates by the Unified Process and by Oracle Unified Method, were taken directly from the Spiral Model Anchor Point Milestones that were initially developed in a series of workshops by the USC Center for Software Engineering and its government and industrial affiliates. For further reading on milestones, see "Anchoring the Software Process."The milestones serve to establish exit criteria for each phase and provide an opportunity to evaluate the project's progress and the readiness of the project to commit resources to begin the subsequent phase.
The five Oracle Unified Method phases:
[A] Inception Phase
[B] Elaboration Phase
[C] Construction Phase
[D] Transition Phase
[E] Production Phase
Oracle Unified Methodology - Implementation Focus - Phases
Friday, December 23, 2011
News For Oracle Support User
News For Oracle Support User,
Over the coming months, My Oracle Support user interface (UI) will be upgraded to help provide faster, more streamlined access to support information and services.Built on Oracle’s own Application Development Framework (ADF), benefits of the redesigned UI will include:
The Oracle ADF-based UI will replace the current HTML and Flash versions. All HTML users will be migrated to the new interface in late January 2012; Flash users will be transitioned approximately 90 days later.
My Oracle Support; the existing website addresses will automatically redirect to the new interface.
Over the coming months, My Oracle Support user interface (UI) will be upgraded to help provide faster, more streamlined access to support information and services.Built on Oracle’s own Application Development Framework (ADF), benefits of the redesigned UI will include:
- Streamlined, three-step process for initiating new Service Requests (SRs)
- Single, consistent workflow for both hardware and software incidents
- Enhanced personalization and filtering within the user interface
- New accessibility features (enabling screen readers, large fonts, etc.)
The Oracle ADF-based UI will replace the current HTML and Flash versions. All HTML users will be migrated to the new interface in late January 2012; Flash users will be transitioned approximately 90 days later.
My Oracle Support; the existing website addresses will automatically redirect to the new interface.
Thursday, November 3, 2011
ERP Implementation Lesson Learnt
ERP implementation failures inflict a great deal of pain on organizations. Whether it’s implementation cost overruns, software that doesn’t support the business, or lack of employee acceptance, ERP failures entail very negative consequences. So why do over 65% of enterprise software implementations fail?
Analysis:
Our experience helping clients clean up projects they or their software vendors have failed to manage, along with our expert witness support to ERP lawsuits, has taught us quite a bit about the reasons for ERP failure. Below are five trends we see in most troubled enterprise software implementations:
Lack of software fit. The first stumbling block for many failed implementations is a severe misalignment between software functionality and business needs. There are hundreds of enterprise software options in the marketplace, so it is important to navigate carefully and find the product with the right fit. Too many failed implementations neglected to engage in an effective ERP software selection process.
Unrealistic implementation expectations. Enterprise software sales reps often understate the level of resources required to make the implementation successful, so many companies fail to budget adequate time, money, resources, and external consulting support to make the project successful. In addition, failed implementations often neglect to include key activities in their implementation project plan, such as organizational change management, business process and workflow definition, and thorough conference room pilots.
Lack of executive buy-in and support. Executive buy-in involves more than signing the checks and delegating the implementation to a project team. It involves defining clear implementation objectives, establishing project governance, and making tough decisions when needed. This is arguably the most important, because it directly affects the other four failure points.
Propensity to customize software rather than leverage standard functionality. Nearly every failed implementation I have seen suffers from this problem, and it is often because of a failure to select the right software in the first place (see #1 above). The more you customize the software, the longer it’s going to take to implement, the more it’s going to cost, and the more risk you introduce into the project. It’s typically not realistic to completely abstain from customization, but changes to the software should be devoted only to key areas of competitive advantage or differentiators. If you aren’t able to limit customization to those areas, then you should either find another ERP software solution or back up and rethink your strategy.
Lack of ERP implementation expertise. Implementations are tough and a team with tested battle wounds is going to dramatically increase your likelihood of success. As we often tell our clients, the fastest and cheapest way to implement enterprise software is to do it right the first time. Failed implementations are more likely to have inexperienced team members who don’t know enough to know what they don’t know.
Conclusion
If you see one or more of these patterns emerging during your implementation, then you are putting your organization at severe risk. On the other hand, If your implementation project team is able to avoid these five common pitfalls, you will be well on your way to a successful ERP implementation.
Good one which i read......................by Eric Kimberling post
Analysis:
Our experience helping clients clean up projects they or their software vendors have failed to manage, along with our expert witness support to ERP lawsuits, has taught us quite a bit about the reasons for ERP failure. Below are five trends we see in most troubled enterprise software implementations:
Lack of software fit. The first stumbling block for many failed implementations is a severe misalignment between software functionality and business needs. There are hundreds of enterprise software options in the marketplace, so it is important to navigate carefully and find the product with the right fit. Too many failed implementations neglected to engage in an effective ERP software selection process.
Unrealistic implementation expectations. Enterprise software sales reps often understate the level of resources required to make the implementation successful, so many companies fail to budget adequate time, money, resources, and external consulting support to make the project successful. In addition, failed implementations often neglect to include key activities in their implementation project plan, such as organizational change management, business process and workflow definition, and thorough conference room pilots.
Lack of executive buy-in and support. Executive buy-in involves more than signing the checks and delegating the implementation to a project team. It involves defining clear implementation objectives, establishing project governance, and making tough decisions when needed. This is arguably the most important, because it directly affects the other four failure points.
Propensity to customize software rather than leverage standard functionality. Nearly every failed implementation I have seen suffers from this problem, and it is often because of a failure to select the right software in the first place (see #1 above). The more you customize the software, the longer it’s going to take to implement, the more it’s going to cost, and the more risk you introduce into the project. It’s typically not realistic to completely abstain from customization, but changes to the software should be devoted only to key areas of competitive advantage or differentiators. If you aren’t able to limit customization to those areas, then you should either find another ERP software solution or back up and rethink your strategy.
Lack of ERP implementation expertise. Implementations are tough and a team with tested battle wounds is going to dramatically increase your likelihood of success. As we often tell our clients, the fastest and cheapest way to implement enterprise software is to do it right the first time. Failed implementations are more likely to have inexperienced team members who don’t know enough to know what they don’t know.
Conclusion
If you see one or more of these patterns emerging during your implementation, then you are putting your organization at severe risk. On the other hand, If your implementation project team is able to avoid these five common pitfalls, you will be well on your way to a successful ERP implementation.
Good one which i read......................by Eric Kimberling post
Know about Oracle Application Testing Suite (ATS)
• Automates complex Oracle EBusiness Suite transactions for both functional testing and
load testing
• Supports automation of both Web and Oracle Forms application interfaces and protocols
• Provides custom test cases to validate application content
• Enables parameterization of test scripts for data-driven testing
• Simulates loads of hundreds to tens of thousands of concurrent users while minimizing
hardware requirements
• Gathers critical infrastructure performance metrics to identify bottlenecks under load
• Provides an intuitive Webbased console to configure and run load tests and share real-time
results with distributed users
• EBS Test Starter Kit with sample test scripts provided for EBS R12 and 11i
ORACLE FUNCTIONAL TESTING
KEY FEATURES
• Automates testing of Web, SOA and Oracle packaged applications
• Integrated scripting platform for automated functional testing and load testing
• Intuitive GUI-based visual scripting interface to create test scripts
• Powerful Java-based code view built on Eclipse IDE to extend scripts
• Enables data-driven tests to drive your automated Web transactions
• Provides built-in test cases to validate application content
• Includes custom testing accelerators for Oracle E-Business Suite, Siebel and ADF applications
• Enables Web Services testing for SOA applications
• Enables Oracle Database testing with synthetic scripts which can be generatedfrom Real
Application Testing’s Database Replay
• Enables automatic generation of load test scripts from Real User Experience Insight
• Support for Adobe® FLEX® testing
KEY BENEFITS
• Cuts testing time in half, eliminating weeks from a project’s testing schedule.
• Reduces the amount of manual testing required for each release
• Lets you focus on testing your application rather than developing test scripts
• Eliminates the need to learn multiple tools and scripting languages for different types of tests
• Improves application quality by allowingfor increased test coverage and more extensive
validation
load testing
• Supports automation of both Web and Oracle Forms application interfaces and protocols
• Provides custom test cases to validate application content
• Enables parameterization of test scripts for data-driven testing
• Simulates loads of hundreds to tens of thousands of concurrent users while minimizing
hardware requirements
• Gathers critical infrastructure performance metrics to identify bottlenecks under load
• Provides an intuitive Webbased console to configure and run load tests and share real-time
results with distributed users
• EBS Test Starter Kit with sample test scripts provided for EBS R12 and 11i
ORACLE FUNCTIONAL TESTING
KEY FEATURES
• Automates testing of Web, SOA and Oracle packaged applications
• Integrated scripting platform for automated functional testing and load testing
• Intuitive GUI-based visual scripting interface to create test scripts
• Powerful Java-based code view built on Eclipse IDE to extend scripts
• Enables data-driven tests to drive your automated Web transactions
• Provides built-in test cases to validate application content
• Includes custom testing accelerators for Oracle E-Business Suite, Siebel and ADF applications
• Enables Web Services testing for SOA applications
• Enables Oracle Database testing with synthetic scripts which can be generatedfrom Real
Application Testing’s Database Replay
• Enables automatic generation of load test scripts from Real User Experience Insight
• Support for Adobe® FLEX® testing
KEY BENEFITS
• Cuts testing time in half, eliminating weeks from a project’s testing schedule.
• Reduces the amount of manual testing required for each release
• Lets you focus on testing your application rather than developing test scripts
• Eliminates the need to learn multiple tools and scripting languages for different types of tests
• Improves application quality by allowingfor increased test coverage and more extensive
validation
Subscribe to:
Posts (Atom)
