Concurrent Report Access Level

on Monday, June 7, 2010

If you want your users to be able to view output of reports submitted by other users, you can set following profile option at site level:

Concurrent:Report Access Level

Set the above profile to "Responsibility" When this profile is set to " Responsibility " it enables all the users (having access to the responsibility from which user submitted Program) to view the output of the program.

If above profile is set to User (Default), then only the user who has submitted the request can view the output of the submitted program.

<<Click the view image in large size>>

Assign Org ID to a Responsibility

on Tuesday, June 1, 2010

When you create a responsibility, you assign a profile option called MO:Operating Unit to the responsibility. This operating unit is the organization that you will be working in. When any user logged into this responsibility that user will be working only within this organization. Anything that is run concurrently, only looks at that organization.

To assign an org_id to a responsibility, log into System administrator or Application Developer responsibility, goto profile option & search by that responsibility name. Look for profile option MO: Operating Unit and assign desired organization to this profile.

Org_id in Apps Tables

All tables that end with _ALL have an org_id column. This denotes what org_id that data is related to. If the table does not have an org_id column then the data is available in all organizations.

APPS - RICE Components

on Sunday, May 30, 2010

The acronym, RICE, stands for Reports, Interfaces, Conversions, and Enhancements (or Extensions).

During a Oracle Applications implementation, additional configuration, design, or programming requirements are necessary to satisfy functional requirements and achieve the desired functionality. The objective during any implementation would be to keep new object development to an absolute minimum. 

RICE objects represent requirements not currently supported within the core functionality of an Oracle Application Module being implemented and thus require additional technical development to satisfy the functional requirement of a organization.

During an Implementation development of RICE components involves

1. Creation of Reports that are not available as standard reports in the oracle apps modules

2. Creation of the Interfaces to external systems.

3. Creation of Conversion programs to transfer data from a legacy system to the new system.

4. Enhancements (or extensions) to the existing system to add additional functionality to existing system without disturbing the core software functionality of the system.

A RICE object has a lifecycle throughout the project that includes approval to develop, functional design specification, technical design specification, coding, testing and implementation. The effort required to complete this development cycle can be significant.