Restrictions in the usage of Oracle Apps value sets


  1. Restrictions on Value Sets :
    1. Table Validated Value Sets :
      • You cannot use table-validated id value sets for accounting flexfield and most other key flexfields.
      • You cannot use :$FLEX$, :$PROFILES$ or :BLOCK.FIELD reference in table name, value and id of table validated value sets. They are supported only in the where clause, description and additional columns.
      • You cannot use DISTINCT clause in any of the column fields or in the WHERE clause of a table validate value set.
      • In an id value set, the value can be non-unique but id should be unique. In a non-id value set, value should be unique.
      • The data-type of the columns selected for the table-validated value set must be of type NUMBER, DATE or VARCHAR2.
      • Support for SQL expression in columns of Table Validated value sets will be obsolete in future release.
    2. Translatable Independent and Translatable Dependent Valuesets :
      • The Numbers Only and Uppercase Only option cannot be used.
      • Flexfield value security is not available.
      • Must have "Char" format type.
    3. Special/Pair valuesets :
      • Special/Pair value sets are user-exit value sets (i.e., they can be validated by C engine only). PL/SQL APIs will not be able to validate them.
  2. You cannot have reserved words for segment names. These names are used (with space replaced by _) while creating the view definition. Also, you cannot have the same segment name within the same flexfield.
  3. Restrictions on Accounting Flexfield :
    • All segments in Accounting Flexfield must be "required". Also, all segments must be "displayed".
    • Accounting Flexfield only supports Independent, Dependent and Table Validation value sets (table validation cannot have any additional WHERE clauses).
    • Accounting Flexfield uses value sets that have a format type of Character. For example, 100 is less than 99.
    • Accounting flexfield requires consecutive segment numbers starting with 1 (such as 1, 2, 3).
    • If you are redefining the Accounting Flexfield for Oracle General Ledger (this key flexfield is used by most of the Oracle Applications products), you must not use any columns other than those named SEGMENT1 through SEGMENT30.
  1. The maximum size you specify for a value set is bytes, not characters.
  2. If you are upgrading from Release 10, the value for your context name is copied to the context code and context name in Release 11. The name and description are translatable, and will appear in the customer's chosen language.The context code is not translatable.
  3. REFERENCE FIELD and CONTEXT of the DFF should not be using the same column.
  4. Security Rules : If a security rule has to be enforced on a particular segment of a flexfield, or for a particular valueset, make sure that the following things have been taken care of:
    1. Make sure that the Security Enabled flag is enabled for your segment.
    2. Make sure that the valueset has either Hierarcical/ Non Hierarcical Security enabled.
    3. Make sure the Security Rule has been assigned to the correct responsibilty.
  1. Features to be de-supported in future releases:
    1. If validation is set at server-side, you cannot use :BLOCK.FIELD in any value set definiton or any default value of segments. Also,:BLOCK.FIELD is present for backward compatibility only. They will be obsoleted in future releases.
    2. Starting with Release 11, SQL*Report (RPT) is no longer supported.
    3. Format types Date and Date-Time and :BLOCK.FIELD references are given for backward compatibility only. These will not be supported in Release 12.
at 5:47:00 PM
Labels: , , , , , ,