The Oracle Period Close Advisor provides guidance on recommended period-end procedures for E-Business Release 12.x. It is intended to be generic and does not relate to a specific organization or industry. Step-by-step best practices with tips and troubleshooting references are provided to assist you through each phase.

 

The Oracle BI Enterprise Edition turns information into intelligence and delivers it to the enterprise. Many organizations today use a broad range of different Business Intelligence tools and applications to collect information from a variety of sources, to analyze it and share with users.

 

At the beginning of our careers back in 1989 as programmers, a colleague and I decided to learn how to play golf. This was at a time when computer gaming was still in its infancy so we actually preferred spending time outdoors.

 

Those familiar with Exadata's CellCLI command line interface often find themselves wondering what sorts of cell metrics are available, and if there's an easy-to-use interface to gather this data without having to look in the manual every time.  I'm one of those guys, so I took some time and put some little shell scripts that might be able to help.

 
CRM Resources are required for a variety of purposes in Oracle E-Business Suite (R12 and 11i). Here is a simple break down of the steps required to create a complete and functioning CRM Resource for you.

 

The Payment Administrator is a collection of settings to define the various components used to create payables documents using the Payment Process Request.  There is a wide variety of processing options available and the Payment Administrator groups these together in a single place. This article will focus on two of the more common elements, the Payment Process Profile and Payment Formats.

 

In order to properly manage internal software license usage within a global company, license management, administration and support must be carefully considered. A centralized licensing infrastructure is ideal, allowing for:

 

Recently, one of my clients required that I secure several of their printers in E-Business Suite so that only certain users could access them. User specific printer security is not standard functionality in Oracle E-Business Suite 12.1.1 but with a little security-through-obscurity we met the requirement to the clients satisfaction. The requirement was a result of the inital setup which caused these printers to appear on the Printers list of values in the Concurrent Request submission screen under "Options".

 

The purpose of this post is to outline how storage works on Exadata.  We’ll look at the host-based storage on the compute nodes and storage server nodes, and then look at the cell storage characteristics, mapping these to ASM storage and finally, database storage. 

 
In this post, I'm going do to a little follow-up to the blog at:
 
 
I received quite a bit off both online and offline feedback on this post and wanted a chance to re-position my messaging a bit.