RICE Components

RICE Components

While implementing an Oracle ERP Application system to a client, to meet the client requirements a consultant needs to make changes to original Vanilla system (Unchanged Oracle ERP Implemented system). The changes made to Original Oracle ERP come under RICE components.

Notes: In information technology, vanilla (pronounced vah-NIHL-uh) is an adjective meaning plain or basic. The unfeatured version of a product is sometimes referred to as the vanilla version.

Mostly an oracle apps technical consultant will be working on RICE components.

R--Reports

I--Interfaces

C--Conversions

E--Extensions (Forms personalization)

During an implementation, development of RICE components involves:

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

2. Creation of the Interfaces to external systems and internal system

Interfaces are of two types

1) Inbound Interface

2) Outbound Interface

Inbound Interface: Transferring the data from the legacy system(in our case it is excel sheet) into the Oracle apps base tables.

Outbound Interface: Transferring the data from the Oracle apps base tables into the legacy system (It might be any of these SAP, People-soft etc).

3. Creation of Conversion programs to transfer data from a legacy system to the new system.(like upgrade  the 11i to R12 ) . Conversation is one time process.

4. Enhancements (or extensions) to the existing system to add additional functionality to existing system without disturbing the core software functionality of the system. Its creating custom code from scratch, existing objects (views, packages and java classes etc) can be used. It is having different behavior from seeded one.

RICE terminology has been introduced by Oracle Corporation and later some Oracle consultants has added their own flavor and introduced some other terminologies like FRICE and RICEW.

FRICE stands for Forms, Reports, Interfaces, Conversions and Enhancements / Extensions

RICEW stands for Reports, Interfaces, Conversions, Enhancements / Extensions and Workflows

Documenting terminology for RICE components
AIM (Applications Implementation Methodology) is documenting structure introduced by Oracle Corporation which is used throughout the life cycle of a RICE component object. Process in AIM methodology includes approval to develop, functional design specification, technical design specification, coding, testing and implementation.(like as MD50,MD70,Testing Documents)