1. Implementation process
All implementations require modifications to the setup data over time. A full implementation cycle using an implementation project is recommended for larger and higher risk modifications, such as reorganizing territories, or adding a new tax regime. You can make smaller changes such as changing profile options, or a list of values by searching for the appropriate task from the Overview page and performing the task directly from there.
When setup data of an existing implementation requires modification that involves a significant number of tasks and task lists or has high risk implication in many parts of an application, maintaining those setup changes through implementation projects is advisable. Often you should perform the modifications in a test environment to mitigate risks before applying the changes to a production environment.
For maintenance of setup data, you can create an implementation project without selecting offerings or options. You can add tasks and task lists specific to the needed modification directly to the implementation project. Once the implementation project is created, functionality is exactly the same as any implementation project you create based on offerings and options. The processes for assigning users to tasks to maintain the setup data and finally to export and import the changes to the target instance is the same as implementation projects you create based on offerings and options.
Implementation Project Manager
Implementation project managers are typically responsible for the overall implementation of an Oracle Fusion application. They research and analyze the functionality of Fusion offerings and match them to the business requirements of the implementation. They also determine what setup tasks need to be performed and who will perform them to make an Oracle Fusion application ready for transactional processing.
Functional User
Functional users are representatives from various lines of business of a company and are subject matter experts in their functional areas. They are the financial administrators, procurement managers, sales operations representatives, and benefits administrators. Typically, they will be responsible for entering setup data and then verifying that the applications are working correctly for the transactional processes.
System Administrator
System administrators typically come with technical background and are responsible for software installation, systems configuration, and data migration. The export and import of setup data will usually be performed by system administrators.
An implementation project is the list of setup tasks you need to complete to implement selected offerings and options. You create a project by selecting the offerings and options you want to implement together. You manage the project as a unit throughout the implementation lifecycle. You can assign these tasks to users and track their completion using the included project management tools.
Maintaining Setup Data
You can also create an implementation project to maintain the setup of specific business processes and activities. In this case, you select specific setup task lists and tasks
Exporting and Importing
Implementation projects are also the foundation for setup export and import. You use them to identify which business objects, and consequently setup data, you will export or import and in which order.
Selecting Offerings
When creating an implementation project you see the list of offerings and options that are configured for implementation. Implementation managers specify which of those offerings and options to include in an implementation project. There are no hard and fast rules for how many offerings you should include in one implementation project. The implementation manager should decide based on how they plan to manage their implementations. For example, if you will implement and deploy different offerings at different times, then having separate implementation projects will make it easier to manage the implementation life cycles. Furthermore, the more offerings you included in an implementation project, the bigger the generated task list will be. This is because the implementation task list includes all setup tasks needed to implement all included offerings. Alternatively, segmenting into multiple implementation projects makes the process easier to manage.
The Manage Applications Implementation business process enables rapid and efficient planning, configuration, implementation, deployment, and ongoing maintenance of Oracle Fusion applications through self-service administration.
The Setup and Maintenance work area offers you the following benefits:
- Prepackaged Lists of Implementation TasksTask lists can be easily configured and extended to better fit with business requirements. Auto-generated, sequential task lists include prerequisites and address dependencies to give full visibility to end-to-end setup requirements of Oracle Fusion applications.
- Rapid StartSpecific implementations can become templates to facilitate reuse and rapid-start for comparable Oracle Fusion applications across many instances.
- Comprehensive ReportingA set of built-in reports helps to analyze, validate and audit configurations, implementations, and setup data of Oracle Fusion applications.
With Oracle Fusion Functional Setup Manager you can:
- Learn about and analyze implementation requirements.
- Configure Oracle Fusion applications to match your business needs.
- Achieve complete visibility to setup requirements through guided, sequential task lists downloadable into Excel for project planning.
- Enter setup data through easy-to-use user interfaces available directly from the task lists.
- Export and import data from one instance to another for rapid setup.
- Validate setup by reviewing setup data reports.
- Implement all Oracle Fusion applications through a standard and consistent process.
The following documentation resources are available for learning how to configure Oracle Fusion Applications.
- Functional Setup Manager Developer's Guide
- Common Implementation Guide
- Customer Data Management Implementation Guide
- Enterprise Contracts Implementation Guide
- Marketing Implementation Guide
- Sales Implementation Guide
- Fusion Accounting Hub Implementation Guide
- Financials Implementation Guide
- Compensation Management Implementation Guide
- Workforce Deployment Implementation Guide
- Workforce Development Implementation Guide
- Incentive Compensation Implementation Guide
- Procurement Implementation Guide
- P6 EPPM Administrator's Guide for an Oracle Database
- P6 EPPM Administrator's Guide for Microsoft SQL Server Database
To start an Oracle Fusion Applications implementation, you must set up one or more initial users using the super user that was created during installation and provisioning of the Oracle Fusion Applications environment, or using the initial administrator user provided by Oracle for Oracle Cloud Application Services implementations. Because Oracle Fusion Applications is secure as delivered, the process of enabling the necessary setup access for initial users requires several specialized steps when getting started with an implementation.
The following high level steps are required for starting an implementation.
- If you are not starting an Oracle Cloud Application Services implementation, sign into Oracle Identity Manager (OIM) as the OIM Administration users and provision the IT Security Manager job role with roles for user and role management. This enables the super user account, which is provisioned with the IT Security Manager job role, to create implementation users.
- For starting all implementations, sign in as the user with initial access: either the Oracle Fusion Applications installation super user or the initial Oracle Cloud Application Services administrator user.
- Perform the following security tasks:
- Synchronize users and roles in the Lightweight Directory Access Protocol (LDAP) store with HCM user management by using the Run User and Roles Synchronization Process task.
- Create an IT security manager user by using the Create Implementation Users task.
- Provision the IT security manager with the IT Security Manager role by using the Provision Roles to Implementation Users task.
- As the newly created IT security manager user, sign in to Oracle Fusion Applications and set up at least one implementation user for setting up enterprise structures.
- Create an implementation user by using the Create Implementation Users task.
- Provision the implementation user with the Application Implementation Manager job role or the Application Implementation Consultant job role by using the Provision Roles to Implementation Users task. The Application Implementation Consultant job role inherits from all product-specific application administrators and entitles the necessary View All access to all secured object.
- Optionally, create a data role for an implementation user who needs only the limited access of a product-specific Application Administrator by using the Create Data Role for Implementation Users. Then assign the resulting data role to the implementation user by using the Provision Roles to Implementation Users task.
The figure shows the task flow from provisioning the IT Security Manager job role with the user and role management entitlement to creating and provisioning implementation users for enterprise setup.
Enterprise structure
Oracle Fusion Applications have been designed to ensure your enterprise can be modeled to meet legal and management objectives. The decisions about your implementation of Oracle Fusion Applications are affected by your:
- Industry
- Business unit requirements for autonomy
- Business and accounting policies
- Business functions performed by business units and optionally, centralized in shared service centers
- Locations of facilities
Every enterprise has three fundamental structures, legal, managerial, and functional, that are used to describe its operations and provide a basis for reporting. In Oracle Fusion, these structures are implemented using the chart of accounts and organizations. Although many alternative hierarchies can be implemented and used for reporting, you are likely to have one primary structure that organizes your business into divisions, business units, and departments aligned by your strategic objectives.
Legal Structure
The figure above shows a typical group of legal entities, operating various business and functional organizations. Your ability to buy and sell, own, and employ comes from your charter in the legal system. A corporation is a distinct legal entity from its owners and managers. The corporation is owned by its shareholders, who may be individuals or other corporations. There are many other kinds of legal entities, such as sole proprietorships, partnerships, and government agencies.
A legally recognized entity can own and trade assets and employ people in the jurisdiction in which it is registered. When granted these privileges, legal entities are also assigned responsibilities to:
- Account for themselves to the public through statutory and external reporting
- Comply with legislation and regulations
- Pay income and transaction taxes
- Process value added tax (VAT) collection on behalf of the taxing authority
Many large enterprises isolate risk and optimize taxes by incorporating subsidiaries. They create legal entities to facilitate legal compliance, segregate operations, optimize taxes, complete contractual relationships, and isolate risk. Enterprises use legal entities to establish their enterprise's identity under the laws of each country in which their enterprise operates.
In the figure above, a separate card represents a series of registered companies. Each company, including the public holding company, InFusion America, must be registered in the countries where they do business. Each company consists of various divisions created for purposes of management reporting. These are shown as vertical columns on each card. For example, a group might have a separate company for each business in the United States (US), but have their United Kingdom (UK) legal entity represent all businesses in that country. The divisions are linked across the cards so that a business can appear on some or all of the cards. For example, the air quality monitoring systems business might be operated by the US, UK, and France companies. The list of business divisions is on the Business Axis. Each company's card is also horizontally striped by functional groups, such as the sales team and the finance team. This functional list is called the Functional Axis. The overall image suggests that information might, at a minimum, be tracked by company, business, division, and function in a group environment. In Oracle Fusion Applications, the legal structure is implemented using legal entities.
Management Structure
Successfully managing multiple businesses requires that you segregate them by their strategic objectives, and measure their results. Although related to your legal structure, the business organizational hierarchies do not need to be reflected directly in the legal structure of the enterprise. The management structure can include divisions, subdivisions, lines of business, strategic business units, and cost centers. In the figure above, the management structure is shown on the Business Axis. In Oracle Fusion Applications, the management structure is implemented using divisions and business units.
Functional Structure
Straddling the legal and business organizations is a functional organization structured around people and their competencies. For example, sales, manufacturing, and service teams are functional organizations. This functional structure is represented by the Functional Axis in the figure above. You reflect the efforts and expenses of your functional organizations directly on the income statement. Organizations must manage and report revenues, cost of sales, and functional expenses such as research and development (R&D) and selling, general, and administrative (SG&A) expenses. In Oracle Fusion Applications, the functional structure is implemented using departments and organizations, including sales, marketing, project, cost, and inventory organizations
job role
|
| Information Technology Management > Manage IT Security > Implement Function Security Controls. | |
All implementations require modifications to the setup data over time. A full implementation cycle using an implementation project is recommended for larger and higher risk modifications, such as reorganizing territories, or adding a new tax regime. You can make smaller changes such as changing profile options, or a list of values by searching for the appropriate task from the Overview page and performing the task directly from there.
When setup data of an existing implementation requires modification that involves a significant number of tasks and task lists or has high risk implication in many parts of an application, maintaining those setup changes through implementation projects is advisable. Often you should perform the modifications in a test environment to mitigate risks before applying the changes to a production environment.
For maintenance of setup data, you can create an implementation project without selecting offerings or options. You can add tasks and task lists specific to the needed modification directly to the implementation project. Once the implementation project is created, functionality is exactly the same as any implementation project you create based on offerings and options. The processes for assigning users to tasks to maintain the setup data and finally to export and import the changes to the target instance is the same as implementation projects you create based on offerings and options.
No comments:
Post a Comment