SA Parm

The PARM_ID filed is probably the most common field within ARI since it is used to link the other data structures back to metadata references. PARM_ID is simply a number (up to 10 digits long) prefixed with the word PNUM. The number is generated by an Oracle sequence. An example: PARM2342

Reference to the realm containing this parameter.

Name used within the physical realm containing the parameter. For an Oracle table or view this would be the column name. For a function this would be an input or output parameter. For actions with sequenced parameters, this would be a number indicating what order the parameters are inputted in. For all other types, this name is user-defined.

Used to avoid having active parameter and deactivated parameters with the same PHYSICAL_NAME cause a unique key violation.

References the underlying parameter type.

Indicates whether the parameter is a key parameter for referencing the realm. For a table this is a part of the primary key, for a PL/SQL function this is an input parameter, and so on. In order to resolve a given parameter, it is necessary to have values for all of the realm input parameters for the realm containing that particular parameter. Those values can then be fed to a function or used as key values in a SQL query to retrieve the desired parameter value.

Indicates whether the parameter is currently valid. Because of the complex interrelationships between parameters, exceptions, events, rules, etc., ARI uses an abandon in place strategy for dealing with obsolete data. Rather than deleting a parameter (or event or exception), ARI simply marks it as being no longer active. An inactive parameter is no longer available through the GUI. A parameter is deactivated when it is changed (the old version is deactivated and a new version takes its place) or when its realm is deactivated.

Name displayed in the GUI. If the name of the parameter is changed in the GUI, this is the value that gets altered, not PHYSICAL_NAME.

For functions and actions, this indicates whether this parameter will have a constant value, which is stored in OVERRIDE_VALUE. For all other realm types, this is N.

For functions and actions, contains the value of a constant parameter.

Points to the parameter ID that provides the currency mapping for this parameter.

Some parameter values can be expanded by looking up values in the appropriated decode table. For example, STORE.STORE can be replaced by STORE.NAME by using the STORE.STORE key value to reference the underlying name field in the STORE table.

Indicates whether the parameter type can be used as an input for a lookup function. Only one parameter per parameter type may have this set to Y.

Indicates whether the parameter type can be used to drive a group lookup in the Users/Groups function. Only one parameter per parameter type may have this set to Y.

For actions, indicates whether or not the action parameter is used for an error return value.

For actions, indicates whether or not the action parameter is used for a user inputted message.

For actions, indicates whether or not the action parameter is used for the current user.

For actions, holds the ID of the column being selected in an LOV query of valid values for the action parameter. For example, the column would hold ORDER_NO if the action needs a submitted order number.

For actions, holds the ID of the decode column being selected in an LOV query. For example, BUYER_NAME would be the decode column for the BUYER_NO column.

For actions, holds the ID of the table for the column being selected in an LOV query of valid values for the action parameter. For example, the column would hold ORDHEAD if the action needs a submitted order number.

For actions, holds the condition of the column being selected in an LOV query of valid values for the action parameter. For example, the column would hold ORDER_STATUS=7 if the action needs a submitted order number.

ID of the parameter that a lookup parameter will derive its value from.