RICE/CEMLI Terminology

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, making any field visible/enabled/disabled/mandatory/non mandatory comes under Personalization.



>> There are many guidelines and risks related to RICE/CEMLI components, but that's for some other day, here I'll restrict myself to overview of these terminologies.

Note: This above information is courtesy  of http://abhayappssolution.blogspot.ie

--

Alerts in Oracle Applications

Alerts are basically used automate the system maintenance, provide reports in the format chosen, for database activity/Business Requirement as it occurs..

few scenarios:

- A database event which was supposed to be monitored for instance insert into some table(event based alert).

- A SQL statement which provides specific information (event based alert).

- The frequency we want the report of a SQL statement(periodic alert)

Responsibility Name: Alert Manager

Pre-requisites:

Navigation: Alert Manager --> System --> Options

-- Electronic Account Mail setup

-- Oracle Alert Mailbox 

Navigation: Alert Manager --> System --> Installations

-- Setup if there are any CUSTOM application where the Alert needs to be created.

Types of Alerts: Event based and Periodic

-- Both types of alerts are defined by SQL statement specified in the SQL section.

Periodic Alert: Navigate to alert form and select the periodic Alert option and then below tasks to be performed.

- Application Name : Application name that owns the alert

- Alert Name : Name of the alert(up to 50 chars) with some meaningful description(up to 240 chars) and check the enabled field.

- Frequency : Select the frequency of the alert,below are the available options.

On Demand

On Day of the month

On Day of the week

Every N calendar Days

Every Day

Every Other Day

Every N Business Days

Every Business Day

Every Other Business Day

Also Start time and end time, number of times in 24 hours and end date if not required after some date.

- SQL : Enter a SQL Statement that retrieves all the alert information, that can used for actions to be planned.The statement should have INTO clause and one 

output field.

Example: Input field    :INPUT_NAME

     Output field   &OUTPUT_NAME

Oracle Alert does not support pl/sql statements, but we have a provision to create the database function and use in the SQL statement.

Example: SELECT PACKAGE.FUNCTION_NAME(:INPUT_VALUE) INTO &OUTPUT_VALUE FROM DUAL;

IMPORT Option: Rather than creating a SQL statement, we can also import from file and can use in the application.

Event Alert: Navigate to alert form and select the Event Alert option and then below tasks to be performed.

- Application Name : Application name that owns the alert

- Alert Name : Name of the alert(up to 50 chars) with some meaningful description(up to 240 chars) and check the enabled field

- Specify the event table name (application be different that the table resides) but privileges should be present.

- Check the insert/update, when the alert has to be fired.

- SQL : Enter a SQL Statement that retrieves all the alert information, that can used for actions to be planned.The statement should have INTO clause and one 

output field.

Example: Input field    :INPUT_NAME

     Output field   &OUTPUT_NAME

Oracle Alert does not support pl/sql statements, but we have a provision to create the database function and use in the SQL statement.

Also make sure there is a condition based on the event table in the SQL, by using :ROWID condition.

Example:

SELECT user_name INTO &NEWUSER FROM fnd_user WHERE rowid = :ROWID;

The SQL statement should be verified, run then it should be saved in the alert.

- Alert Details: Provide the input,output and installation/user id details.

- Action: Create the action Name and click on the action details.

Action type can be set as Message,SQL Statement script and operating system script.

and provide the details for the message details like To list and message data.

- Action sets: Once the alert actions are created, those alert actions can be included in the action sets.

Oracle Inventory --- Purchasing Category:

Oracle Inventory – Purchasing Category: Purchasing category is nothing but an Oracle Inventory category which is attached to a category set mapped to Purchasing functional area. Following setup steps need to be performed to setup a Purchasing category.

Step-1: Define "Item Category" flexfield structure

Responsibility: "Inventory Superuser" or similar
Navigate to: Setup -> Flexfields -> Key -> Segments
Query for Application "Inventory" and Flexfield Title "Item Categories".

There is already one seeded structure for the purchasing category as "PO_ITEM_CATEGORY" but if you want to define a custom one for your business please create it by entering the Structure code, title and description. Add the required category segments to the structure.

Step-2: Define Item Categories

Navigate to: Setup -> Items -> Categories -> Category Codes.
Enter the structure name and click on the "Find" button.
Define the Item category codes and description in the "Categories" form.

Step-3: Define Category Set

Navigate to: Setup -> Items -> Categories -> Category Sets
Enter the category set name, description, flex structure (the one you have setup in the Step-1), Controlled at and Default Category values.
Add the category codes defined in the previous step to the details section of the "Category Sets" form.

Step-4: Assign the category set to the functional area

Navigate to: Setup -> Items -> Categories -> Default Category Sets
Assign the category set name defined in the Step-3 to the "Purchasing" functional area.

Now the purchasing category setup is complete.

--

Oracle Apps Technical and Oracle Fusion Technical Real Time Training

Dear  "Friend",

Thank you for showing interest in the "Oracle Apps Technical with Oracle Fusion Tools" conducted by Orafusion Technologies.

We believe that you would like to evaluate the program rigorously before joining. We are starting Regular and Corporate session on "Oracle Apps Technical with Oracle Fusion Tools "with 100% Placement Assistance. It will be held at the Orafusion Technologies centre in Hyderabad.

The details of the session are as follows

Demo Date: 6^th  May

Time: 7:00 Am – 8:30 Am

Regular Session: 8^th  May 2013.

Real Time Training: 10 ^Th   May 2013.

            Prerequisite: Graduation

          Highlights: Oracle Apps Technical with Oracle Fusion Tools Regular and Real Time Training, Experience, Interview Support, Certification & Daily Job updates till Placement & Chapter wise Presentations (PPTs) & Chapter wise Hands On (MS Word Docs) & Exams on FAQs & Job Placement mainly in USA and rest of the world.

Founded and Conducting by Real Time Faculty having Experience in a CMMI Level 5 Company, Hyderabad.

This special session will give you a chance to interact with the faculty and also experience the technology first hand.

There are limited seats (10) available for the program. If you wish to register for the session please contact on " Mob: 9502657526".

Venue: "Suit #7-1-3961 Beside Venkateshwara Swami Temple, Community Hall Road, B.K.Guda Park Lane .S.R.Nagar, Hyderabad)

Fwd: Ugadi Greetings...

To Dear & Near...

With A Hope That You Attain Success And Bliss with Every flavour On the Day Of Ugadi!

With delicious teepi, chedu, karam, pulupu & uppu ugadi pachadi....

Wishing You A Happy And Prosperous Ugadi…!

Cheers

--

Excel Output From BI Publisher or XML Publisher is Trimming Leading Zeros in Excel Template

To implement the solution, execute the following steps:

1. In the rtf template, use the "Insert -> Symbol" function to insert a very small
0xA0 (NO-BREAK SPACE) character (font size 1 or 2pt) in front of the number string field.

2. One can also try:
<fo:bidi-override direction="ltr" unicode-bidi="bidi-override"> <?format-number:INVOICE_NUMBER;'09999999'?> </fo:bidi-override>"

3. Another option:
During XML template design, Instead of the using the tag < ?TAG_NAME ? >
use  ="<?TAG_NAME?>". It wraps the value with double quotes. Now Excel treat value as character and doesn't trim the leading zeors of value.
Note: space between < and ? and tag name is not requried.

4. Retest for the issue 

For more information search in metalink [ID 417811.1]

--

How to get Trace File path in backend in oracle apps

How to get Trace File
When you enable SQL trace in a session for the first time, the Oracle server process handling that session will create a trace file in the directory on the database server designated by the user_dump_dest initialization parameter. As the server is called by the application to perform database operations, the server process will append to the trace file. 

Query:

------------

select name,value from V$PARAMETER where name = 'user_dump_dest';

--