The unique identifier of the (what type of record is this). This default to blank but is required for all records, must be unique (what must it be unique by), and must be <= 25 characters.Linked and must be <= 50 characters. If a duplicate value is entered, he message "Duplicate Account Classes are not allowed" will be displayed on Save. This value is always editable. 

Database Field: ERPx_####GLAccountClass.OOOO

The name associated with the (ID Field Name) ID. This is required for all records but does not need to be unique (what must it be unique by) (and defaults from or is calculated by). 

Linked ClassName 

Identifies the Category associated with the Account Class. This is a single-select standard lookup that is required. If missing, the message "Category is required." is displayed on Save. This defaults as blank and is always editable.

This lookup contains the values in the GLAccountClassCategory Enumeration Class.

Database Field: ERPx_#####GLAccountClass.#####.GLAccountClassCategoryEN

A Yes/No field used to identify if the record is Inactive. If set to 'Yes' then the record is "Inactive" and will not be included in look-ups for

other master files. If set to 'No' then the record is "Active" and can be freely used

. 'No'

 values display as blank in the grid

. This value is always editable.

Database Field:

ERPx_

GLAccountClass.

IsInactive 

A single-select standard lookup to select (describe what is being selected). This defaults to (Default Value) and is (always, never, or conditionally) required. If not assigned, the message "(what message is displayed)" will be displayed. This field is (always, never, or conditionally) enabled. Linked Database Field: ERPx_#####.#####.

This lookup contains all the values in the (EnumerationClassName) Enumeration Class. 

A (single-select standard, single select load on demand, or multi-select) lookup to select (describe what is being selected). This defaults to (Default Value) and is (always, never, or conditionally) required. If not assigned, the message "(what message is displayed)" will be displayed. This field is (always, never, or conditionally) enabled. Linked Database Field: ERPx_#####.#####

This lookup contains a blank value, the current assigned value, and a list of all the 'Active' (what does it include).

The [Describe what the field shows] (formatted as …(if applicable)). This is only populated for (what is it populated for...) and (defaults from or is calculated by…). This column has a grand total at the bottom. The values comes from the (Enumeration Class) Enumeration. Linked Database Field: ERPx_#####.#####.

A (text box or non-editable text box) (formatted as …(if applicable)) to... . This is only populated for (what is it populated for...) and (defaults from or is calculated by…). This is (always, never, or conditionally) required and must be <= (how many) characters. (This column has a grand total at the bottom). Linked Database Field: ERPx_#####.#####.

A Yes/No lookup to identify whether or not the feature is turned on. The value defaults to "Yes" but can be changed at anytime. 

A value of "Yes" means that...

Identifies the sort order of the GL Account Class. This is a text box that is not required. If missing, the system will assume the Sort to be "10". If entered, this field must be a whole number. It defaults as blank and is always editable.

Sorting Rules:

• The Sort column for each Category begins with 10 and always increments in multiples of 10. To insert a Account Class in between two other Account Classes, users may enter Sort values that are in between the multiples of 10. For example, users may enter a Sort value of "25" if they wish to add an Account Class in between the Account Classes with a Sort value of "20" and Sort value of "30" in the same Category. In this case, on Save, the Account class with a Sort value of "25" will be assigned a Sort value of "30" and the existing Account Class with a Sort value of "30" will be assigned a Sort value of "40".
• If a new Account Class is added with the same Sort value as an existing Account Class in the same Category, the system will order the Account Class in ascending order based on the AccountClassSK. For example, if the "Asset" Category has three existing Account Classes ("Cash" with a Sort value of "10", "Inventory" with a Sort value of "20", and "Other Assets" with a Sort value of "30") and a new "Short Term Investments" Account Class (with a Sort value of "20") is added in the "Asset" Category, then the system will assign "Short Term Investments" a Sort value of "30" since the AccountClassSK of "Short Term Investments" is higher than the AccountClassSK of the existing "Inventory" Account Class. This would result in "Other Assets" being assigned a Sort of "40".
• If an Account Class is deleted, all Sort values for the Category will automatically re-number. For example, if the Account Class with a Sort value of "20" is deleted, then the Account Class with the Sort value of "30" will be assigned a Sort value of "20". The Account Class with the Sort value of "40" will be assigned a Sort value of "30" and so forth.

Database Field: ERPx_GLAccountClass.Sort