Master Index Wizard Field Properties and Name Restrictions

When you create fields in the object structure of the master index application, you can specify several properties for each field, such as whether the field is required, whether the field will appear as a drop-down menu on the MIDM, whether the field will be used in a blocking query, and so on. There are also some restrictions for how fields can be named and how the properties are defined.

The following topics provide information about the naming restrictions and about the field properties of the wizard.

Master Index Wizard Field Name Restrictions
Master Index Wizard General Field Properties
Master Index Wizard MIDM Field Properties

Master Index Wizard Field Name Restrictions

When you name the fields in your object structure, be sure to keep the following guidelines in mind to avoid errors when compiling or running the master index application.

Oracle Java CAPS Master Index automatically creates a field for each object named objectId, where object is the name of an object or sub-object. You cannot create fields with those names. For example, you cannot create a field named “AddressId” if there is an Address object in the object structure.
If you enter a field name longer than 20 characters, a warning dialog box appears. While most databases can handle names up to at least 30 characters, Oracle Java CAPS Master Index appends text to the end of fields defined for phonetic encoding or standardization. For fields that will be parsed, normalized, or phonetically encoded, make sure the name of the original field does not exceed 20 characters. Any other field can have a name up to 30 characters long. For information about the names of the fields automatically created by the wizard, see Oracle Java CAPS Master Index Processing Reference.
In field names, do not use characters or names restricted by Java, XML, or the database platform being used.

Master Index Wizard General Field Properties

The following table lists and describes the properties you can define on the General Properties page of the wizard.

Property	Description
Data Type	The master index data type of the field. The following data types are supported: string - Contains a string of characters. date - Contains a date value. float - Contains a floating point integer. int - Contains an integer. char - Contains a single character. boolean - Contains either `true` or `false`.
Match Type	The type of matching to be performed against the field, if the field is to be used for match weight generation. You must define at least one field for matching or no weights will be generated. The match types you specify here define the structure of mefa.xml, including the match string. The match types in mefa.xml might differ from the wizard match types. See Oracle Java CAPS Master Index Configuration Reference for information about the available options for this field and how the wizard match types correlate to mefa.xml types.
Blocking	An indicator of whether the field will be used in the blocking query. Specify `true` to add the field to the blocking query; specify `false` to omit it from the blocking query.
Key Type	An indicator of whether the field is used to identify unique objects. For example, a business index might store several addresses for each business. Each address is assigned an address type and each business can only have one address of each type. Specify `true` if the field is a unique record identifier, or `false` if it is not. Key type fields should also be required fields (see below), unless a combination of fields are specified as key types for an object. Note - It is recommended that each child object contain a key type field, but this is not required. If child objects do not contain one or more key type fields, each enterprise object might accumulate a very large number of child objects depending on the survivor strategy used.
Updateable	An indicator of whether the field can be updated from the MIDM and external system messages. Specify `true` if the field can be updated or `false` if it cannot.
Required	An indicator of whether the field is required in order to save an enterprise object to the database. Specify `true` if the field is required or `false` if it is not. If only one key type field is defined for an object, that field should be required.
Size	The number of characters allowed in each field. This determines the number of characters allowed in the database columns and defines the maximum number of characters that can be entered into each field on the MIDM.
Pattern	The required data pattern for the field. For more information about possible values and using Java patterns, see “Patterns” in the class list for `java.util.regex` in the Javadocs provided with Java. You might want to define patterns for date, telephone, or SSN fields. Note that for the MIDM, the pattern is further restricted by the value entered for the input mask described in the previous table. If no input mask is specified, all regex patterns are supported.
Code Module	The identification code for the drop-down list that appears for this field in the MIDM. Note - This value must match an entry in the code column of the sbyn_common_header database table and, by default, an entry for the code you enter is created in the Code List database script. You can further customize code lists in the script after completing the wizard.
User Code	The processing code for the drop-down list that appears for the fields defined by the Constrained By property. For more information, see the description of the Constrained By property below. Note - This must match an entry in the code_list column of the sbyn_user_code database table.
Constrained By	The name of the field that contains the corresponding User Code value (described above). The User Code and Constrained By properties are used in conjunction to fulfill two purposes. The first purpose is to define a drop-down list for the field that contains the User Code value. The second purpose is to validate the field that contains the Constrained By value against definitions for the field with the User Code value. For example, if you store non-unique IDs such as credit card numbers or insurance policy numbers, you could create a field named ID Type that has a User Code value of CREDCARD, which is also defined as a code in the sbyn_user_code table. This gives the ID Type field a drop-down list based on the definitions for CREDCARD in the sbyn_user_code table. You could then create a field named ID that would be constrained by the formats defined for the ID Type field. Any IDs you enter would be validated against the value of the ID Type field.

Master Index Wizard MIDM Field Properties

The following table lists and describes the field properties you can define on the MIDM Field Properties page of the wizard.

Property	Description
Display Name	The name of the field as it will appear on the MIDM.
Input Mask	A mask used by the GUI to add punctuation to a field. For example, if users enter the date in the format MMDDYYYY, you can add an input mask to display the dates as MM/DD/YYYY. Use the value mask (described below) to strip the punctuation from the value before storing it in the database. To define an input mask, enter a character type for each character in the field and place any necessary punctuation between the character types. For example, the input mask for the above date format is DD/DD/DDDD. D – indicates a numeric character. L – indicates an alphabetic character. A – indicates an alphanumeric character. Note that the value you enter can further restrict the data pattern for the field (this is the Pattern field property described in Master Index Wizard General Field Properties). The following character types can be used.
Value Mask	A mask used by the index to strip any extra characters that were added by the input mask (see above). This mask ensures that data is stored in the database in the correct format. To specify a value mask, type the same value as is entered for the input mask, but type an “x” in place of each punctuation mark. For example, if an SSN field has an input mask of DDD-DD-DDDD, specify a value mask of DDDxDDxDDDD to strip the dashes before storing the SSN. A value mask is not required for date fields.
Search Screen	An indicator of whether the field appears on the search windows of the MIDM. Specify `true` to display the field or `false` to hide it.
Required	An indicator of whether the field must be populated on the search windows of the MIDM when performing a search. This property can only be modified if the Search Screen property is set to `true` (see above). Specify `true` to make the field required or specify `false` to make it optional. You can also specify `oneof` to create a group of fields of which at least one must be populated to perform a search. (Be sure to specify `oneof` for each field in the group.) Tip - If a field is required for a search, the field should also be required for creating a record (by specifying true for the Required property on the Properties page). Otherwise, searches performed from the MIDM could result in no matches even though possible matches exist.
Search Result	An indicator of whether the field appears on the search results windows of the MIDM. Specify `true` to display the field, or `false` to hide it.
Report	An indicator of whether the field appears on the reports generated from the MIDM. Specify `true` to display the field on the reports; otherwise specify `false`.

Skip Navigation Links
Exit Print View
	Oracle Java CAPS Master Index User's Guide Java CAPS Documentation