Oracle Unified Methodology (OUM)

The Oracle Unified Method (OUM) is Oracle's methodology for implementing its products, designed to support the entire IT lifecycle, from inception to production

The Oracle Unified Method (OUM) breaks down the project life cycle into five distinct phases, each designed to guide teams through planning, building, and deploying Oracle solutions—whether on-premises or in the cloud. Here's a deep dive into each phase:

1. Inception Phase

Goal: Define the project scope and secure stakeholder buy-in.

• Identify business drivers and high-level requirements.
• Establish project objectives, constraints, and risks.
• Develop initial project plans and estimates.
• Conduct stakeholder analysis and engagement.
• Deliverables: Project Charter, Initial Risk Register, High-Level Requirements Document.

2. Elaboration Phase

Goal: Refine requirements and design the solution architecture.

• Analyze and prioritize detailed business requirements.
• Define the solution architecture and validate feasibility.
• Plan iterations and refine the project schedule.
• Identify gaps between business needs and Oracle solution capabilities.
• Deliverables: Functional Requirements Document, Architecture Blueprint, Iteration Plan.

3. Construction Phase

Goal: Build and configure the solution.

• Configure Oracle applications based on finalized requirements.
• Develop custom components (if needed).
• Conduct unit and integration testing.
• Prepare training materials and user documentation.
• Deliverables: Configuration Workbook, Technical Design Documents, Test Scripts.

4. Transition Phase

Goal: Deploy the solution and prepare for go-live.

• Execute data migration and cutover activities.
• Conduct user acceptance testing (UAT).
• Train end users and support staff.
• Finalize support and maintenance plans.
• Deliverables: Cutover Plan, UAT Results, Training Completion Reports.

 5. Production Phase

Goal: Operate and support the live system.

• Monitor system performance and user adoption.
• Provide ongoing support and issue resolution.
• Capture lessons learned and improvement opportunities.
• Plan for future enhancements or releases.
• Deliverables: SLA Agreements, Support Logs, Post-Implementation Review.

Core Documentation in OUM Implementation Phase

📄 Document Name	📝 Purpose / Description
Project Management Plan	Defines scope, schedule, resources, and governance.
Work Breakdown Structure (WBS)	Breaks down tasks and deliverables into manageable units.
Requirements Traceability Matrix (RTM)	Maps business requirements to system functionality.
Configuration Workbook	Captures all application setup and configuration details.
Functional Design Document (FDD)	Describes how business requirements will be met functionally.
Technical Design Document (TDD)	Details customizations, integrations, and technical components.
Test Strategy & Test Plan	Outlines testing approach, scope, and responsibilities.
Test Scripts / Test Cases	Step-by-step instructions for validating system functionality.
Issue and Risk Log	Tracks project risks, issues, and mitigation strategies.
Training Plan & Materials	Prepares users for go-live with manuals and training sessions.
Cutover Plan	Details steps for transitioning from legacy systems to Oracle.
Deployment Checklist	Ensures all go-live activities are completed and verified.
Post-Implementation Support Plan	Defines support structure and escalation paths after go-live.

AME Concept in Oracle Apps R12

Let's take a closer look at the 5 key terminology used in AME concepts:

1. Attribute

2. Conditions

3. Approver Group

4. Action Types

5. Rule

Let us understand each terminology in detail.

Attribute: Attribute refers to a column name extracted from a transaction.

Examples of attributes:

Requisition Total, Item Category, Transaction requestor Person ID, Invoice Amount... So.On.

Condition: Using attributes,  if Condition are created.

If Requisition total > $1000 

Approval Group: when additional approver are required for particular conditions and to specify a dynamic SQL query for Additional approval groups are created.

Action Types : Action types helps to understand the type of approval hierarchy followed for example: Supervisory Level or Approval - Group Chain of authority.

Rule: Rule are created with combination of  Condition and Action type. For Example, if the following condition is true (If Requisition total > $1000) then following action type ( Follow Supervisory Level Hierarchy)

How to diagnose the performance issue in oracle apps R12.

1.  Trace - We run the trace based on particular activity. We require to generate trace based on particular activity like concurrent report, or form which is leading to time consumption. Trace can be run at the below level

- Trace can be run at respective Form Level

- Trace need to be enabled at Concurrent Define window.

- Trace fetching based on Request ID

Once trace file is generated. Reveiw the trace file to find out at which level there performance issue for a Particular SQL ID as is mentioned below.
                            ·         Parsing
                            ·         Fetching
                            ·         Execution

2. AWR Report: AWR Report will be run every 1 hour as scheduled by DBA team. For this report we will be able to find out Top 10 SQL ID which is causing performance issue. Based on SQL ID, we will generated

3. SQLT Report:  For particular SQL ID we have to generate SQLT Report.  Which will help us to identify the number indexes created on particular table or Query which is causing for SQL Execution issue.

Oracle Enterprise Management (OEM)

From Oracle Enterprise Management (OEM) window we will be able to find the load on the server. As per the graph below, Blue indicates high load on the server.

`

Blocking Queries:

select to_char(a.LOGON_TIME,'DDMonYY HH24:MM'),a.sid, a.serial#,c.NAME, a.STATUS,a.ACTION from V$SESSION a ,DBA_BLOCKERS b,AUDIT_ACTIONS c

where a.sid = b.holding_session and a.command = c.action;

select /*+ rule */ 'SID '||a.sid||' is blocking the sessions '||b.sid from v$lock a, v$lock b where a.block=1 and b.request >0;

SELECT c.owner, c.object_name, c.object_type, b.SID, b.serial#, b.status, b.osuser, b.machine

                 FROM  v$locked_object a, v$session b,  dba_objects c

                 WHERE b.SID = a.session_id AND a.object_id = c.object_id  AND b.sid in ( select holding_session from DBA_BLOCKERS ) ;

  

SELECT c.owner, c.object_name, c.object_type, b.SID, b.serial#, b.status,b.osuser, b.machine FROM  v$locked_object a, v$session b,  dba_objects c

WHERE b.SID = a.session_id AND a.object_id = c.object_id AND b.sid in ( select holding_session from DBA_BLOCKERS ) ;

SELECT c.owner, c.object_name, c.object_type, b.SID, b.serial#, b.status, b.osuser, b.machine FROM  v$locked_object a, v$session b,  dba_objects c

WHERE b.SID = a.session_id AND a.object_id = c.object_id  AND b.sid in ( select holding_session from DBA_BLOCKERS ) ;

SELECT session_id  FROM DBA_LOCKS WHERE BLOCKING_OTHERS = 'Blocking';

select * from DBA_WAITERS;

select * from dba_blockers;

select * from v$lock where block=1;

SELECT DECODE (request, 0, 'Holder: ', 'Waiter: ') || sid sess,inst_id,id1, id2,lmode,request, TYPE

FROM gv$LOCK  WHERE (id1, id2, TYPE) IN (SELECT id1, id2, TYPE FROM gv$LOCK WHERE request > 0)

ORDER BY id1, request;

SELECT 'alter system kill session ''' || s.sid || ',' || s.SERIAL# || ','||'@'||''|| i.instance_number || ''';' a,'ps -ef |grep LOCAL=NO|grep ' || p.SPID SPID,

'kill -9 ' || p.SPID,s.status FROM gv$session s, gv$process p,gv$instance i WHERE ( (p.addr(+) = s.paddr) AND (p.inst_id(+) = s.inst_id)) AND s.sid = &sid;

SELECT DISTINCT S1.USERNAME || '@' || S1.MACHINE

|| ' ( INST=' || S1.INST_ID || ' SID=' || S1.SID || ' ) IS BLOCKING '

|| S2.USERNAME || '@' || S2.MACHINE || ' ( INST=' || S1.INST_ID || ' SID=' || S2.SID || ' ) OBJ_ID:' ||L1.ID1||' OBJ_NAME:'||O.OBJECT_NAME

AS BLOCKING_STATUS

FROM GV$LOCK L1, GV$SESSION S1, GV$LOCK L2, GV$SESSION S2,DBA_OBJECTS O

WHERE S1.SID=L1.SID AND S2.SID=L2.SID

AND S1.INST_ID=L1.INST_ID AND S2.INST_ID=L2.INST_ID

AND L1.ID1=OBJECT_ID

AND L1.ID1=O.OBJECT_ID

AND L1.BLOCK > 0 AND L2.REQUEST > 0

AND L1.ID1 = L2.ID1 AND L1.ID2 = L2.ID2;

    SELECT

   l1.sid || ' is blocking ' || l2.sid blocking_sessions

FROM

   gv$lock l1, gv$lock l2

WHERE

   l1.block = 1 AND

   l2.request > 0 AND

   l1.id1 = l2.id1 AND

   l1.id2 = l2.id2;