You are on page 1of 2

RICE/CEMLI Terminology

In my Oracle career I often hear confusion over RICE/CEMLI terminologies, what they stands for ? what is the
meaning of...blah blah blah....so with the help of my very good friend Charan, I have decided to write my take on this.
AIM (Applications Implementation Methodology) => During packaged ERP(enterprise resource planning)
implementations, Clients often have additional requirements apart from the existing (standard) business process, for
which they need to create/change theVanila system (Unchanged ERP Implemented system) processes, and its these
changes that come under RICE/RICEW components. AIM is the methodology/standards/published guidelines, which
Oracle suggests it's Clients to follow while developing
RICE/RICEW components for their business requirements.
RICE stands for Reports, Interfaces, Conversions, Enhancements / Extensions
----> Sometimes extended to FRICE > F for Forms
------OR
RICEW > W for Workflow.
------Forms/Reports/Workflows : Create/Change existing forms/reports/workflows available in ERP system to meet the
Clients business requirements.
Interfaces : Linking (Programs) between other systems to ERP system in order to synchronize the Data.They can be
Manual, Batch or Real-Time. Interfaces can be either outbound or inbound. An outbound interface reads data from
Oracle Apps tables and usually creates output files in the third party tool specified format. An inbound interface reads
data from flat files (usually) and calls Oracle APIs to upload data into Oracle Apps.
Conversion : It is converting the data structure and data design of legacy system data to satisfy the customer’s
business rules before importing it into Oracle .It is like a one time run of an inbound interface except that the amount
of data processed during conversion could be potentially huge since all the required data from the legacy system
would be transferred to Oracle.
Enhancements/Extensions : Please see below.
>> In R12 RICE components have been extended to CEMLI components.
-------CEMLI Stands for Configurations/Customization, Extension, Modification, Localization, and Integration.
Configurations : Configure the existing, pre-built application features according to your client's
requirement.Changing setups and profile values can be the example of configurations.
Customization : Customization means altering/changing the standard objects or creation of custom object to meet
client's business need. It may be Extensions or Modifications.
Extensions : Extension means creating custom code from scratch, existing objects (views, packages and java
classes etc) can be used. It is having different behaviour from seeded one.
Modifications : Modifications is enhancing/changing the existing code to meet the client's requirements. It is the
modification of seeded behaviour.
Localization : It is to define the different legislative support provided by oracle Applications based on
country/region/language requirements.
Integration : It can be Data Integration or Application Integration, options for these two are Open Interface tables,
APIs, EAI(Enterprise Application Integration Tools), BPEL, AQ, EDI etc.
>> Apart from these there is one more term and that is Personalization.
Personalization : Tailoring the layout or visibility of page content to meet client requirements is Personalization.

Changing the user interface (UI) look-and-feel. but that’s for some other day. . here I’ll restrict myself to overview of these terminologies. >> There are many guidelines and risks related to RICE/CEMLI components. making any field visible/enabled/disabled/mandatory/non mandatory comes under Personalization.