Search This Blog

Saturday, November 22, 2014

R12 VS FUSION


Component
Oracle e-Business Suite
Oracle Fusion Applications
Database
Oracle Database 10g
Oracle Database 11g
Application Server
Oracle application
server
10.1.2 (Forms)

Oracle Application
server
10.1.3 (OC4J)
Oracle WebLogic
User Interface
Forms, JSPs
Oracle ADF + ADF
Java Server Faces
Portal
Oracle Portal
Oracle Webcenter
Data Model
Oracle eBS
Data Model
Oracle eBS Data Model +
Siebel + PoepleSoft
(Trees, Data Effectivity,
person Model)
Attachments/Imaging
BLOBs
UCM/Stellant
Workflow/Approval
PL/SQL
BPEL
Reports
Reports (11i),
Discoverer
BI Publisher
Analytics
Discoverer
OBIEE
Financial Reporting
Financial Statement Generator
Hyperion
Integration
AIA
AIA + BPEL +
More web services
XML Gateway
XML Gateway
BPEL, B2B Adapter
Oracle Fusion Middleware Components: 
Its technology framework includes the following Oracle Fusion Middleware components -
1.Oracle WebLogic Server- Java application server that helps to deploy multiple applications in a robust and scalable environment.
2.Oracle WebLogic Communication Services- provides click-to-dial functionality through contextual Actions which further helps users with information and actions.
3.Oracle Identity Management- automatically manages user access and provides services and interfaces for third party application developments.
4.Oracle WebCenter- combines user interface technologies for building social applications.
5.Oracle Business Intelligence-offers a complete to generates and delivers analyses for fusion application.
6.Oracle SOA Suite-a comprehensive software for building and deploying service-oriented architecture.
7.Oracle Application Development Framework- a java framework to simplify application development by minimizing code writing
8.Oracle JDeveloper- for building service-oriented applications using industry standards 

Service-Oriented Architecture (SOA): 

Oracle Fusion Application are based on SOA-Services oriented Architecture.
This is a significant technology change adapted by Oracle. SOA Suite, a middleware component of Oracle Fusion Middleware, provides infrastructure component for designing, deploying and managing SOA composite applications. Various services can be created, managed and helps to put together multiple technology components into one SOA composite application.

Wednesday, November 12, 2014

Overview on OBIEE11g Security Setup

overview on OBIEE11g Security Setup

OBIEE security consists of 2 parts:
Security Infrastructure setup (Done from WLS Console and EM)
Here we define the Application roles and assign them privileges(that is associate Application role to a Application Policy) Application Role is created based on our security need and is used for grouping users, so that a group security policy can be defined.
Data and Object security setup (Done from the rpd file)
To restrict users from seeing tables/columns or filtering the data they see, we need to have the object and data security in place. This is done from rpd file. This is the most important step in security implementation

Let’s see the steps involved in security implementation.


Security Infra setup
 
We will define a user and a group in web logic server
 
 
Log on to web logic server(WLS) console (URL http://localhost_ip:7001/console) 
 
 
This is the home page of WLS console
 
 
Click on Security Realms
 
 
In Security realms page click on “myrealm”
 
 
Go to “Users and Groups” tab>”Groups”>New and add a new WLS group called DieselModelViewers_WLS
 
 
Go to “Users and Groups” tab>”User”>New and add a new user called diesel_user
 
;
 
Associate the diesel_user to DieselModelViewers_WLS group
 
Next log on to Enterprise Manager (URL http://localhost_ip:7001/em)
 
 
Navigate to Business Intelligence > coreapplication > Business Intelligence Instance >Security>Application Role
 
 
Create a new Application role to be used for our data and object security by clicking on new.
 
 
Call the Application Role and DieselModelViewers
 
The  click on 
 
 
Associate this application role with the WLS group DieselModelViewers_WLS created earlier
 
 
Object and Data Security Setup
 
 
Log in to the rpd and click Manage>Identity
 
 
Go to the Application Roles tab, check that the newly created Application role “DieselModelViewer” is visible
 
 
Click on Permissions button
 
We can now define a new data filter for the DieselModelViewers group, click on 
 
Define a new security filter for the above application role as shown above.
 
Data security is done, next lets see object security.
 
 
We want to hide the presentation table WB_TEST from members of DieselModelViewers application role, like diesel_user. Double click on WB_TEST table and the above window opens up, click on permissionsDeny permission to DieselModelViewers by clicking NoAccess.This will restrict diesel_user from seeing WB_TEST table in his subject area.
 
Next log in to Answers/Analysis page.
 
Lets check a report that has all fuel types, since an admin user can see all fuel types we will choose to see it from weblogic user
 
 
As we see , here the report is not restricted based on fuel type.
 
Lets login using the diesel_user
 
 
Try to access the subject area (noe we can only access subject area, but cant create a report because of BIConsumer privilege
 
 
We dont see the WB_TEST Presentation table due to object security
 
 
We also don’t see the fuel types, other than DIESEL, due to data security
 
 
The nqquery.log shows that DIESEL filter is added on to the select statement, which confirms that data security is working.
 

Friday, November 7, 2014

OBIEE - Week First day and last day

If we need to get week start date from a particular table,just use the below code:
TIMESTAMPADD(SQL_TSI_DAY,- DAYOFWEEK(MIN(“Dim – Date”.” Date Column”)) + 1, MIN(“Dim – Date”.” Date Column”))

For Week End Date,follow the below code:
TIMESTAMPADD(SQL_TSI_DAY, 7-DAYOFWEEK(MAX(“Dim – Date”.” Date Column”)), MAX(“Dim – Date”.”Date Column”))
DAYOFWEEK returns an integer in the range of 1 to 7. A value of 1 represents the Monday.

OBIEE -Month Start Date and Month End Date


Use the below code:
Month Start Date:
TIMESTAMPADD(SQL_TSI_DAY, -DAYOFMONTH(MIN(“Dim – Date”.”Date Column “))+1, MIN(“Dim – Date”.”Date Column”))
Here DAYOFMONTH returns an integer in the range of 1 to 31. This integer represent the count of days since beginning of the month.
Month End Date:
TIMESTAMPADD(SQL_TSI_DAY,DAYOFMONTH(MAX(“Dim – Date”.”Date Column”)) * -1 ,TIMESTAMPADD(SQL_TSI_MONTH, 1, MAX(“Dim – Date”.” Date Column”)))
From  right to left the first TIMESTAMPADD returns next month.The second TIMESTAMPADD returns the date from current month.

Wednesday, July 16, 2014

Developement Project Management stages and details

Project Start-up

Software Development Process Flow – Project Start-up
The Project Start-up step incorporates the following stages:
Entry Criteria
The Development Agreement/Proposal is received.
Tasks
Software estimation
Project Initiation and preparation/update
Project Management Plan (PMP)
Inspection of PMP
Phase-end Review
Validation and Verification
Approved Project Budget Sheet
Reviewed PMP
Project details made available using the Time Sheet System
Exit Criteria
Approval and release of Project Management Plan
Approved Project Budget Sheet
Phase Deliverables
Approval and release of Project Management Plan


Software Development Process Flow – Requirement Analysis
This step incorporates the following stages:
Entry Criteria
The Project Management Plan is made available to the client.
Tasks
Prepare Software Requirements Specifications (SRS).
Define Acceptance Criteria & prepare Acceptance Plan.
Provide the Phase-end Review.
Inspect the Software Requirements Specifications (SRS) Document.
Validation and Verification
In this stage, the SRS is completely reviewed and fine-tuned according to client requirements.
Exit Criteria
In this stage, the agreed SRS is made available to the client along with the Acceptance Plan.
Phase Deliverables
SRS
 
Software Development Process Flow – High-level Design
This step incorporates the following stages:
Entry Criteria
Agreed Software Requirement Specifications are available.
Project Management Plan is available.
Tasks
Prepare High-level Design (HLD).
Examine the HLD.
Initiate the Phase-end Review.
Validation and Verification
Review of High-level Design is validated, verified, and incorporated.
Exit Criteria
High-level Design documentation is made available.
Phase Deliverables
High-level Design document is delivered to the client with all feedbacks effectively incorporated.
Software Development Process Flow – Low-level Design
This step incorporates the following stages:
Entry Criteria
Project Management Plan is available.
HLD document is available.
Tasks
Prepare Program Specifications.
Provide a Structured Walk through.
Prepare the Test Plan and Test Cases.
Provide a Structured Walk through the Phase-end Review.
Validation and Verification
Review Test Plan.
Review Program Specification.
Review Unit Test Cases.
Review Functional Test Cases.
Review Acceptance Test Cases.
Exit Criteria
Program Specifications are released.
Unit Test Cases are released.
Functional Test Cases are released.
Acceptance Test Cases are released.
Phase Deliverables
Program Specifications
Unit Test Cases and Test Data
Functional Test Cases and Test Data
=============================

Software Development Process Flow – Testing
This step incorporates the following stages:
Entry Criteria
Project Management Plan is available.
Successfully Unit Tested Code is available.
High Level Design, Low Level Design, and Unit Test Cases are available.
Tasks
Conduct testing.
Prepare user documents.
Inspection of user documents.
Provide Phase-end Review.
Validation and Verification
Review functional test results.
Review User Documentation.
Exit Criteria
Tested System is released.
User Documentation is completed.
Phase Deliverables
Test results

Sunday, July 6, 2014

Upgrade or reimplementation or Implementation initiation

Whatever your Oracle Financials project, be it an R12 Upgrade , an R12 reimplementation, or a fresh greenfield Implementation.  It is important that you select the right partner and this starts with the RFI, RFQ, RFP & RFT documents.
So what are they ?
  • RFI - Request for Information
  • RFQ - Request for Quotation
  • RFP - Request for Proposal
  • RFT - Request for Tender
RFI – Request for Information
This document is the starting point in the procurement process.  You have identified a wide list of suppliers that you think can provide the product or services you require and need to qualify them through to the next stage of the procurement process. The purpose is simply to understand and qualify the potential suppliers, not the specific solutions.  As this is the initial document it does not need to be a long one. Aim for 5-6 pages.
 
The RFI should include:
  • Company background and overview
  • High level explanation of
    • Requirements giving rise to the RFI ( ie. Products or services giving rise to the RFI )
    • Current systems and issues
    • Where you want to be once the project has been completed. 
RFI Should not include
  • Details of other suppliers the RFI has been submitted to. 
What the customer wants from RFI Response
What the supplier wants from an RFI
  • To gain a general understanding of the competition in the market.
  • Provide enough information for pre-qualification by procurement department.
  • Provide the basis of short listed vendors for the next phase.
  • Supplier references.
  • To Qualify you as a customer.
  • Understanding of your business, its current issues and what you want to achieve from the project.
  • Specifics on what products and technology the customer is interested in.
  • Estimate of project budget.
 A sample RFI Template document for free download can be found here.