Previous  Next          Contents  Index  Navigation  Glossary  Library

Value Set Naming Conventions

If you plan to refer to your value set name in a WHERE clause for a validation table value set, you should use only letters, numbers, and underscores (_) in your value set name. You should not include any spaces, quotes, or other special characters in your value set name. Do not use the string $FLEX$ as part of your value set name. Note that validation tables are case-sensitive for value set names you use in validation table WHERE clauses.

Suggestion: Make your value set names contain only one case (either upper or lower case) to avoid case-sensitivity problems.

Oracle Applications includes many predefined value sets. These are primarily value sets for Standard Request Submission parameters. During an upgrade, Oracle Applications will overwrite your value sets that use the same names as Oracle Applications value sets. While Oracle Applications provides a list of reserved value set names before an upgrade so that you can rename your sets to prevent their being overwritten, you should name your value sets carefully to make upgrades easier.

Oracle Applications reserves certain naming patterns. Oracle Applications reserves the patterns of either two or three characters immediately followed by either an underscore or hyphen, as in AP_VALUE_SET or PER-Value Set.

Note that Oracle Applications products do not completely follow these guidelines for Release 11, so you will still need to check and possibly rename your value sets before upgrades. However, if you name your value sets with names we are unlikely to use, your future upgrades will be simpler. For example, you might want to give your value sets names that begin with a six-character name for your site.

         Previous  Next          Contents  Index  Navigation  Glossary  Library