How to view ESS Jobs Submitted by other users

Q: How to view ESS Jobs Submitted by other users?

Ans: Assign “ESS Monitor Role” to user, then user will be able to see all jobs submitted by other users.

https://community.oracle.com/thread/3719674

Monitor current and future scheduled ESS jobs (Doc ID 1590255.1)

GL setups in Oracle Fusion

GL setups in Oracle Fusion: We will share the detail steps to for GL setups in Oracle Fusion. There are lot of steps involved in the Fusion GL setups. We need to perform many activities to GL setups in oracle fusion. I will try to explain some of the key activities for GL setups in Oracle Fusion. One of the major step included in the oracle fusion GL setup is Chart of Account Structure creations. In this post , we will try to create the chart of account structure for GL setup in oracle fusion. Please find below the complete detail about GL setups in Oracle Fusion.

List of Activities for GL setups in Oracle Fusion

1.     Overview of the Oracle Fusion Application

2.     Oracle fusion Application Home Page Feature

3.     Overview of the Functional setup Manager in Oracle fusion Financials

4.     How to Use functional Setup Manager

5.     Feature of Functional setup Manager

6.     How to Create Implementation Project in Functional setup Manager

7.     Implementation Project Task assignments to the Users

8.     Creating User/Roles Access for Financial Implementation

9.     Introduction of Organization Structure in Oracle Fusion

10. Implementation Example Scenario for Sample Organization

11. Create Legal Entity Address

12. Creating Legal Entity in Oracle Fusion

13. Creating Chart of Account Value Sets

14. Creating Chart of Accounts Structure

15. Creating Chart of Accounts Structure Instances

16. Creating Chart of Account Value Set Values

17. Creating Accounting Calendar for Ledger

18. Defining Currency Conversion Rate Type

19. Creating Subledger Accounting Methods

20. Creating Ledger in Oracle Fusion Financials

21. Creating Ledger

22. Assigning Legal Entity to Ledger

23. Maintaining Primary Ledger Information

24. Assigning Balancing Segment Values to Legal Entities

25. Creating Secondary Ledger in Oracle Fusion Financials

26. Creating Accounting Calendar for Secondary Ledger

27. Defining Specify Ledger Options for Secondary Ledger

28. Creating Primary to Secondary Ledger Mapping

29. Define Accounting Configurations

30. Creating Access in Oracle Fusion for Using General Ledger

31. Providing Data Access to access the Ledger Data in General Ledger

32. Opening First GL Period in Oracle Fusion

33. Open/Close Manage GL Period in Oracle Fusion

34. Creating Journal Sequence in Oracle fusion

35. Creating Journal Sources for External Source

36. Creating Journals Auto Post Criteria Set

37. Creating Auto Journal Reversal Criteria Sets

38. Configuring Revaluations in Oracle Fusion

39. How to Create the Budget in Oracle Fusion

40. Upload Budget in Oracle Fusion

41. Inquiry and View the GL Account Balances in Oracle Fusion

42. Creating New GL Account Combination in Oracle Fusion

43. Maintain Daily Rates in Oracle Fusion

44. Creating Manual Journals in Oracle Fusion

45. How to View the Created Journals

46. Open/Close GL Periods in Oracle Fusion

47. Manually Reversing Journals in Oracle Fusion

48. Creating GL Journals through Spreadsheet

49. Schedule Run Auto Post program to automatically post GL and Subledger journals in General Ledger.

50. Auto Reverse Journals

51. Translation in Oracle Fusion

52. Implement Journal Approval Process in Oracle Fusion

53. BPM Setup of oracle Fusion journal approval workflow

54. Creating Manual GL Journal for Testing Approval Process

to be continue...

ORACLE UNIFIED METHOD (OUM) – BASICS AND DOWNLOAD

 

Since retirement for Oracle legacy methods, there was lot of queries on OUM vs AIM , therefore this post will help reader to know more about new method.

The OUM aka Oracle Unified Method supports the entire Enterprise IT Life cycle, including support for the successful implementation of every Oracle product.

It is a robust, technology agnostic methodology Oracle Methods …

• Based on industry standards and field experience
• Highly scalable to support project or program specific requirements
• Iteratively developed through a continuous, evolutionary process

OUM Principal

This is based out of five main principles

1. Business: Focus on the business and assure stake holder acceptance and delivery of the development’s efforts.
2. Architecture: Define architecture before resources are committed for development and implementation.
3. Adaptability: Encourages adaptability for scalable delivery across small and large projects possessing disparate resources and skill levels.
4. Implementation: Provides rapid implementation techniques to ensure business solutions in short time frames
5. Standards: Leverage the Unified Modeling Language and the Unified Software Development Process

OUM is able to…

Support the complete range of Oracle technology projects including

• Service-Oriented Architecture (SOA)
• Enterprise Integration
• Custom Software
• Enterprise Performance Management (EPM)
• Business Intelligence (BI)
• Enterprise 2.0
• Enterprise Application Implementation
• Software Upgrade

Currently Oracle Consulting using this methods, tools support a complete range of technology engagements.

In Summary… OUM structure

• is a comprehensive set of method materials that is applicable to any type of information technology project.
• is a plan-based method – that includes overview material on various approaches and standards.
• It includes base guidelines for focus areas, views, phases, activities, processes and tasks, as well as work product descriptions.

OUM basically have focus areas and there underline phases and processes , in summary

OUM FOCUS AREAS

These 3 Focus Areas provide a frameworks for enterprise level planning, project and program management and implementing .

1. Envision Focus Area deals with development and maintenance of enterprise level IT strategy, architecture, and governance. This also assists in the transition from enterprise-level planning and strategy activities to the identification and initiation of specific projects.
2. Manage Focus Area provides a framework in which all types of projects can be planned, estimated, controlled, and completed in a consistent manner.
3. Implement Focus Area This focus Area provides a framework to develop and implement Oracle-based business solutions .

Next let take a quick overview for Implement Focus area which got replacement of old methods like AIM Foundation, AIM for Business Flows, Compass, Results Roadmap, etc.

Understanding OUM’s Implement Focus

This focus area typically based out of milestone based approach.Typical Milestone are:

• Life cycle objective milestone
• Life cycle architecture milestone
• Initial operation capability milestone
• System in production milestone
• Sign-off milestone

As mention earlier this comprises of 5 phases and 14 processes, details as follows:

OUM Project Phases

The Workflows within an OUM project are categorized into five phases: Inception, Elaboration, Construction,Transition, and Production. These phases are described below:

(A) Phase I: Inception :As the first phases in the project life cycle.Major goal of this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project. Kick off’s, review , high-level business requirements along with initial project plan is being targeted in this phase only.

(B) Phase II: Elaboration :This is the second phases in the project life cycle, where major focus would be to develop the detailed requirements models, partition the solution, develop functional prototyping, and baseline the architecture of the system.

(C) Phase III: Construction :As the third phases in the project life cycle, Construction focuses on design, implementation, and testing of functions to develop a complete system.

(D) Phase IV: Transition :This typically consist from installation onto the production system through the UAT and launch of the live application, open and ready for business.

(E) Phase V: Production : The goal of the Production phase is to operate the newly developed system, assess the success of the system, and support the users. This includes: monitoring the system; acting appropriately to ensure continued operation; measuring system performance; operating and maintaining supporting systems; responding to help requests, error reports and feature requests by users; and managing the applicable change control process so that defects and new features are prioritized and assigned to future releases.

 OUM Process – Typically OUM process defined as “A discipline or sub-project that defines a set of tasks related by subject matter, required skills, and common dependencies”. A process usually spans several phases in an approach.

All OUM tasks are also organized into processes that group related tasks together. Project team members are assigned to these groupings according to their specialization and background. OUM includes the following 14 processes

1. BUSINESS REQUIREMENTS [RD] – Objective of the Business Requirements process is to identify, refine, and prioritize the business requirements for the proposed system
2. REQUIREMENTS ANALYSIS [RA]– Objective of the Requirements Analysis process is to further analyze the requirements identified during the Business Requirements process as the basis for analysis and design.
3. ANALYSIS [AN]– Objective of the Analysis process is to analyze, refine, and structure the system requirements via the Analysis Model.
4. DESIGN [DS] – Objective of the Design process is to translate requirements into a system design that meets all functional and supplemental requirements.
5. IMPLEMENTATION [IM] – Objective of the Implementation process is to develop the final system, through a number of iterative steps.
6. TESTING [TE]– The Testing process is an integrated approach to testing the quality and conformance of all elements of the new system.
7. PERFORMANCE MANAGEMENT [PT]– Objective of the Performance Management process is to define, construct, and execute an effective approach to managing performance throughout the project life cycle.
8. TECHNICAL ARCHITECTURE [TA]– Objective of the Technical Architecture process is to design an information system architecture that realizes the business vision.
9. DATA ACQUISITION AND CONVERSION [CV]– Objective of the Data Acquisition and Conversion process is to convert all legacy data necessary for the operation of the new system.
10. DOCUMENTATION [DO]– Objective of the Documentation process is to develop documentation that augments product manuals with information about custom software and business procedures.
11. ORGANIZATIONAL CHANGE MANAGEMENT [OCM]– Objective of the Organizational Change Management process is to identify the human and organizational challenges of the project in order to mitigate risk.
12. TRAINING [TR]– Objective of the Training process is to adequately train the project team to begin the project and train the users to run the new system.
13. TRANSITION [TS]– Objective of the Transition process is to install the system and go production.
14. OPERATIONS AND SUPPORT [PS]– Objective of the Operations and Support process is to monitor and respond to system problems to fix errors and performance problems and plan enhancements.

Oracle A.I.M. Methodology Documentation and their uses

 

Enhance your project documentation process with Oracle Applications Implementation Methodology (AIM)

Introduction
Having supported many software implementations including those of ERP systems, its found that the project documentation is one area which requires significant improvement. Often just finding the project documentation is difficult enough and once this frustrating process is completed you find that the documentation is inadequate. This makes it very difficult to support such implementations and any new users of such software have to rely on learning from previous users whose availability is often in question. Although poor documentation can be attributed to poor project management, in many instances the documentation is not done simply due to the effort involved and the lack of awareness as to which tools are available to facilitate the process. This article highlights how Oracle AIM advantage simplifies the documentation process and can also be used as a tool to effectively manage Oracle Applications project implementations.

AIM Overview
In my communications with a number of Oracle Applications implementer’s, its surprising to find that there is very little awareness surrounding AIM and it is very rarely used for implementations. However, I have personally found it to be very useful in managing and documenting the Oracle Applications projects. Its also believed it compares favorably and in many instances betters project management tools being used for other ERP system implementations.

AIM consists of a project management methodology together with the underlying documentation templates that support the tasks you perform within this methodology. This combination of a methodology together with documentation templates makes AIM a powerful tool for assisting implementation participants in running and managing projects successfully. The methodology can be used for any other software implementations but obviously the true value of AIM will be only be realized when it is used in conjunction with the Oracle specific document templates.

The Methodology and Structure
The methodology used is similar to traditional software project management methodologies. There are six phases within the project, these are…

1. Definition – establish the business objectives and related requirements. Define the project work plan
2. Operations Analysis – analyze the operations and determine fit between organizational requirements and standard application functionality.
3. Design – develop detailed designs for the optimal solutions to meet the future business requirements.
4. Build – physical software system build and testing
5. Transition – developying the finished solutions into the organization
6. Production – go LIVE!

Within these phases are the various processes – see the listed processes in below figure…

The Oracle Application Implementation Methodology (AIM) is a proven approach for implementatino of Oracle Applications across business domains. This approach has been developed by oracle in constants collaboration within its partner network.

“AIM provides tools needed to effectively and efficiently plan, conduct, and control project steps to successfully implement new business systems.”

Application Implementation Method is a proven approach for all the activities required to implement oracle applications.

There are ELEVEN PROCESSES of AIM implementation, which are as follows…

1.Business Process Architecture [BP]

This phase outlines:
+ Existing Business Practices
+ Catalog change practices
+ Leading practices
+ Future practices

• BP.010 Define Business and Process Strategy
• BP.020 Catalog and Analyze Potential Changes
• BP.030 Determine Data Gathering Requirements
• BP.040 Develop Current Process Model
• BP.050 Review Leading Practices
• BP.060 Develop High-Level Process Vision
• BP.070 Develop High-Level Process Design
• BP.080 Develop Future Process Model
• BP.090 Document Business Procedure

---

2. Business Requirement Definition [RD]

This phase explains about the initial baseline questionnaire and gathering of requirements.

• RD.010 Identify Current Financial and Operating Structure
• RD.020 Conduct Current Business Baseline
• RD.030 Establish Process and Mapping Summary
• RD.040 Gather Business Volumes and Metrics
• RD.050 Gather Business Requirements
• RD.060 Determine Audit and Control Requirements
• RD.070 Identify Business Availability Requirements
• RD.080 Identify Reporting and Information Access Requirements

---

3. Business Requirement Mapping [BR]

In this phase the requirements of business are matched with the standard functionality of the oracle applications.

• BR.010 Analyze High-Level Gaps
• BR.020 Prepare mapping environment
• BR.030 Map Business requirements
• BR.040 Map Business Data
• BR.050 Conduct Integration Fit Analysis
• BR.060 Create Information Model
• BR.070 Create Reporting Fit Analysis
• BR.080 Test Business Solutions
• BR.090 Confirm Integrated Business Solutions
• BR.100 Define Applications Setup
• BR.110 Define security Profiles

---

4. Application and Technical Architecture [TA]
This outlines the infrastructure requirements to implement oracle applications.

• TA.010 Define Architecture Requirements and Strategy
• TA.020 Identify Current Technical Architecture
• TA.030 Develop Preliminary Conceptual Architecture
• TA.040 Define Application Architecture
• TA.050 Define System Availability Strategy
• TA.060 Define Reporting and Information Access Strategy
• TA.070 Revise Conceptual Architecture
• TA.080 Define Application Security Architecture
• TA.090 Define Application and Database Server Architecture
• TA.100 Define and Propose Architecture Subsystems
• TA.110 Define System Capacity Plan
• TA.120 Define Platform and Network Architecture
• TA.130 Define Application Deployment Plan
• TA.140 Assess Performance Risks
• TA.150 Define System Management Procedures

---

5. Build and Module Design [MD]
This phase emphasizes the development of new functionality (customization) required by the client. It mainly details how to design the required forms, database and reports.

• MD.010 Define Application Extension Strategy
• MD.020 Define and estimate application extensions
• MD.030 Define design standards
• MD.040 Define Build Standards
• MD.050 Create Application extensions functional design
• MD.060 Design Database extensions
• MD.070 Create Application extensions technical design
• MD.080 Review functional and Technical designs
• MD.090 Prepare Development environment
• MD.100 Create Database extensions
• MD.110 Create Application extension modules
• MD.120 Create Installation routines

---

6. Data Conversion [CV]
Data Conversion is the process of converting or transferring the data from legacy system to oracle applications. Ex. Transferring customer records from the legacy to the Customer Master.

• CV.010 Define data conversion requirements and strategy
• CV.020 Define Conversion standards
• CV.030 Prepare conversion environment
• CV.040 Perform conversion data mapping
• CV.050 Define manual conversion procedures
• CV.060 Design conversion programs
• CV.070 Prepare conversion test plans
• CV.080 Develop conversion programs
• CV.090 Perform conversion unit tests
• CV.100 Perform conversion business objects
• CV.110 Perform conversion validation tests
• CV.120 Install conversion programs
• CV.130 Convert and verify data

---

7. Documentation [DO]
Documentation prepared per module that includes user guides and implementation manuals.

• DO.010 Define documentation requirements and strategy
• DO.020 Define Documentation standards and procedures
• DO.030 Prepare glossary
• DO.040 Prepare documentation environment
• DO.050 Produce documentation prototypes and templates
• DO.060 Publish user reference manual
• DO.070 Publish user guide
• DO.080 Publish technical reference manual
• DO.090 Publish system management guide

---

8. Business System Testing [TE]
A process of validating the setup’s and functionality by QA(functional consultant) to certify status.

• TE.010 Define testing requirements and strategy
• TE.020 Develop unit test script
• TE.030 Develop link test script
• TE.040 Develop system test script
• TE.050 Develop systems integration test script
• TE.060 Prepare testing environments
• TE.070 Perform unit test
• TE.080 Perform link test
• TE.090 perform installation test
• TE.100 Prepare key users for testing
• TE.110 Perform system test
• TE.120 Perform systems integration test
  TE.130 Perform Acceptance test

---

9. Performance Testing [PT]
Performance testing is the evaluation of transactions saving time, transaction retrieval times, workflow background process, database performance, etc

• PT.010 – Define Performance Testing Strategy
• PT.020 – Identify Performance Test Scenarios
• PT.030 – Identify Performance Test Transaction
• PT.040 – Create Performance Test Scripts
• PT.050 – Design Performance Test Transaction Programs
• PT.060 – Design Performance Test Data
• PT.070 – Design Test Database Load Programs
• PT.080 – Create Performance Test Transaction Programs
• PT.090 – Create Test Database Load Programs
• PT.100 – Construct Performance Test Database
• PT.110 – Prepare Performance Test Environment
• PT.120 – Execute Performance Test

---

10. Adoption and Learning [AP]
This phase explains the removal of the legacy system and oracle application roll out enterprise wide.

• AP.010 – Define Executive Project Strategy
• AP.020 – Conduct Initial Project Team Orientation
• AP.030 – Develop Project Team Learning Plan
• AP.040 – Prepare Project Team Learning Environment
• AP.050 – Conduct Project Team Learning Events
• AP.060 – Develop Business Unit Managers’ Readiness Plan
• AP.070 – Develop Project Readiness Roadmap
• AP.080 – Develop and Execute Communication Campaign
• AP.090 – Develop Managers’ Readiness Plan
• AP.100 – Identify Business Process Impact on Organization
• AP.110 – Align Human Performance Support Systems
• AP.120 – Align Information Technology Groups
• AP.130 – Conduct User Learning Needs Analysis
• AP.140 – Develop User Learning Plan
• AP.150 – Develop User Learningware
• AP.160 – Prepare User Learning Environment
• AP.170 – Conduct User Learning Events
• AP.180 – Conduct Effectiveness Assessment

---

11. Production Migration [PM]
The process of “decommissioning” of legacy system and the usage(adoption) of oracle application system.

• PM.010 – Define Transition Strategy
• PM.020 – Design Production Support Infrastructure
• PM.030 – Develop Transition and Contingency Plan
• PM.040 – Prepare Production Environment
• PM.050 – Set Up Applications
• PM.060 – Implement Production Support Infrastructure
• PM.070 – Verify Production Readiness
• PM.080 – Begin Production
• PM.090 – Measure System Performance
• PM.100 – Maintain System
• PM.110 – Refine Production System
• PM.120 – Decommission Former Systems
• PM.130 – Propose Future Business Direction
• PM.140 – Propose Future Technical Direction