Then choose #EXTENSIBLE_CHARACTER_NUMERIC from the dropdown list. semantic attributes such as reuse of translatable column headers or a check table, but a suitable one does not exist yet. You often define the technical attributes of the data element in a domain, so they can be reused.Ĭreate a new data element: If you want to reuse the benefits of data elements - i.e. You can define properties such as search help and (translatable) column header, and then use the same data element in many contexts. Use an existing data element: The most powerful: A data element describes both the technical and semantic attributes of a field, such as a currency, or a customer name. For more information, see ABAP Keyword Documentation: Predefined Dictionary Types. There are 3 ways to create a field for a database table:īuilt-in type: The quickest: You specify a (pre-defined) primitive type, length, and description, but no more. First you need to understand your options: All rights reserved.In the next step, you will define the table fields. Scripts can be run to directly insert those terms into the database, making those newly added terms available in the Rules Palette for use by the configuration team.Ĭopyright © 2009, 2013, Oracle and/or its affiliates. The spreadsheet should be filled out when a new term is deemed necessary and approved and should include all of the necessary data to populate the Data Dictionary tables. If the term is changed in any way, alert the team so any existing configuration can be changed to the approved name.Īn alternate method for managing new terms is to use a spreadsheet rather than the online Data Dictionary in the Rules Palette.If a new term is approved, then the prefix can be removed and will be available for the team to use.Provide a query to run against the Data Dictionary tables that will pull any entries that have the prefix to be reviewed by the Data Dictionary owner.

When adding a new term, use an agreed-upon prefix in the definition, such as ‘FOR REVIEW-xxxxxxxxx’.

Provide the DataDictionary-CheckIn/CheckOut privilege to a small number of configuration analysts.

Special characters are supported in category names, such as dashes or underscores.

Use an uppercase letter for each word in the category name.

Ensure the category name is meaningful to the configuration team as they will be using categories to filter the Data Dictionary terms.

Minimize abbreviations when at all possible.

Use standardized naming conventions when defining categories for the Data Dictionary.

Use an uppercase letter for each word in the name.

Do not use underscores or special characters in names.

Do not use spaces between words in a name.

Ex: NewEffectiveDate NOT NewEffDateĮnsure the name is relevant to the data the field or variable is representing.

Use standardized naming conventions for fields and math variables when defining Data Dictionary terms.

Set the level of compliance for math variables in the DataDictionaryEnforcement business rule to Ignore.

Adding new terms means that the Rules Palette user will be able to name the term, define the term type, associate the term to one or more pre-defined categories and add a definition to the term. User is also able to add new categories to the Data Dictionary.

DataDictionary-CheckIn/CheckOut: user is able to add new terms to the Data Dictionary and can use the new term or existing terms in configuration.

The user is only able to select from existing terms defined in the Data Dictionary when configuring rules.

DataDictionary-View: this privilege restricts a user from adding new terms.

Only configuration team members should have access to the Data Dictionary.

Use security privileges in the Rules Palette to control access to the Data Dictionary tool.

Turn on the Data Dictionary as soon as possible.

Assign an individual as the Data Dictionary owner who will approve all terms added to the dictionary.

Establish a team to define the categories, naming conventions and definitions for Data Dictionary terms.

When starting an implementation project:.Before implementing the use of the Data Dictionary it is important to review the best practices that are listed below. Oracle® Insurance Rules Palette 9.7.0.0 E39062_01Īdhering to Data Dictionary best practices will help ensure the successful use of the tool. You are here: Data Dictionary > Data Dictionary Best Practices

Online data dictionary creator