Oracle Apps Notes

A collection of my random notes, primarily on Oracle Apps

Prevent users from uploading specific files in Oracle EBS

Oracle EBS provides a way to restrict the type of files which can be uploaded though the front end. This will, for example, prevent users from uploading specific file types through the Generic File Manager or from uploading XML report files (which is how I came across this feature).
The two main parts to this feature is the Attachment File Upload Restriction Default profile option and the FILE_MIME_TYPES table.
The FILE_MIME_TYPES table lists the various file types and specifies whether they are allowed to be uploaded or not. The Attachment File Upload Restriction Default profile option controls those file types which have not been explicitly allowed or disallowed in the FILE_MIME_TYPES. Attachment File Upload Restriction Default can have a value of Yes or No. If it is set to Yes, a file type can be uploaded from the front-end even if it has not been explicitly allowed or disallowed in FILE_MIME_TYPES. Setting this value to No will prevent the user from uploading any file type which has not been explicitly allowed in FILE_MIME_TYPES.
When this feature prevents users from uploading a file, they will see this message on the screen: This file type is not allowed. Please choose another file
For more details please check Metalink Note#1357849.1: Security Configuration Mechanism in the Attachments Feature in Oracle E-Business Suite.

Which Fusion Middleware components are installed in my system?

A quick note to self and everyone coming here:

To find out which Fusion Middleware components are installed in your system (and their corresponding version details), open the registry.xml file under $MW_HOME. As shown in the picture below, all installed components, their versions and installed paths are available in the file. registry_sample

What the Expression Language test button actually tests in the Fusion Application Page Composer

So you are customizing a page in Fusion Applications using the Page Composer. You come up with a nice way of using the Expression Language to hide a field dynamically based on the value of another field on the page. You type an expression in the Show Component property of the field and click on the Test button. And… Oops! It did not return the expected value. You check and double check the expression. It looks fine. You are starting to wonder whether this is a bug. But then something strikes you. You think you know what is happening. You check and confirm your hunch. You condense the lesson you learn in the picture below:

Expression Language


Get every new post delivered to your Inbox.

Join 49 other followers