Oracle E-Business Suite Diagnostics Overview


  • Oracle E-Business Suite Diagnostics is a free tool provided by Oracle to ease the gathering and analyzing of information from your E-Business Suite specific to a existing issue or setup
  • Formatted output displays the information gathered, the findings of the analysis and appropriate actions to take if necessary
  • This tool is easy to use and is designed for both the functional and technical user

Oracle E-Business Suite Diagnostics are designed to improve:

  • Problem Avoidance – resolving configuration and data issues that would cause processes to fail
  • Self Service Resolution – resolving problems without the need to contact Oracle Support
  • Reduction in Resolution Time – minimizing the time spent to resolve an issue by increasing support engineer efficiency

Key items to note:

  • E-Business Suite Diagnostics do not alter the data or setup in your system
  • E-Business Suite Diagnostics are organized into one of the following groups:
  • Setup Diagnostic tests are designed to assist in resolving product setup issues
  • Activity Diagnostic tests gather information about data and configuration relevant to a particular functionality / issue, examine that information, provide feedback, and suggest appropriate actions
  • Data Collection tests gather information relevant to a particular product / functionality / issue
  • Functional Categories typically align with the product menu structure and include both activity and data collection tests
  • E-Business Suite Diagnostics are designed to run in Oracle Diagnostics and are available via the E-Business Suite Diagnostics Patch

Release 11i and Release 12 both use the Role-based Access Control (RBAC) security model.
For a basic understanding of RBAC and how it relates to diagnostics, please click here

New to Release 12.0.6 security:

  • user must have a diagnostics role assigned – 3 seeded roles are delivered that can be used without additional setup
  • the ‘Application Diagnostics’ responsibility is used to execute tests in the diagnostic framework

Additionally, output logs from previously executed tests can only be reviewed by the user who executed them or the system administrator.

More information is available on Metalink / Oracle MySupport

How to find the source code of a seeded HRMS formula function


To  look at the source code a formula function i.e. if you want to determine
the logic used to return the value concerned you can do the following

1. Establish the defintion name held in the table FF_FUNCTIONS

For example if you are interested in the function called
CALCULATE_CONTINUOUS_SERVICE

SELECT DEFINITION FROM FF_FUNCTIONS WHERE NAME = ‘CALCULATE_CONTINUOUS_SERVICE’

This will return the package.procedure

In this case it returns
pqp_service_history_calc_pkg.calcualate_continuous_service

2.Establish the file name held on the service for this package

SELECT TEXT FROM USER_SOURCE WHERE NAME = ‘PQP_SERVICE_HISTORY_CALC_PKG’
AND TEXT LIKE ‘%$Header%’

This will return the file name

In this case this is

pqshpcal.pkb

3.Access the package body code from the server and identify the procedure
concerned

In this case you can search code until locate function

calcualate_continuous_service

 

Oracle 11g – Replacing Sensitive Data Using the Data Masking Pack


This tutorial shows you how to identify sensitive data, select appropriate mask formats for the sensitive fields, apply the mask and then replace the sensitive fields in the production version.

Time to Complete — Approximately 1 hour

Topics

This tutorial covers the following topics:  — for Full Access for tutorials, – use this url — http://www.oracle.com/technology/obe/11gr1_db/security/datamask/datamask.htm#o

Managing the Data Masking Format Library

Identifying Sensitive Data for Masking

Creating Data Masking Definitions for Your Application Schema

Exporting Mask Definitions to XML

Importing Data Masking Definitions

Creating and Applying a User-Defined Mask