Set Lower Limit

Use this system function to create the WHERE clause of a SQL search statement for use in a succeeding fetch when you are searching against a table that employs a ragged hierarchy.

Parameters

Grid: Input, required. The grid FC to affect.
Table: Input, required. The source from which to acquire comparison data. Set the parameter to an alphanumeric constant (<Literal>), <Null>, or an applicable object from the object list.
Alias: Input, required. The column of the table from which to acquire comparison data. Set the parameter to an alphanumeric constant (<Literal>), <Null>, or an applicable object from the object list.
Comparison Type: Input, required. The comparison operator to use. Set the parameter to the comparison operator to use (<Equal To>, <Not Equal To>, and so forth).
Comparison Value: Input, required. The comparison value to use. Set the parameter to an alphanumeric constant (<Literal>), <Blank>, <Zero>, or applicable object from the object list.
And/Or: Input, required. Indicates whether to append another WHERE clause to the SQL statement and how the new statement relates to the one before it (AND or OR). Set the parameter to <And>, <Or> or <None>.

Additional Notes

In some cases, referencing an item just by table and column (as you do with Set Selection) is insufficient. For example, in JD Edwards EnterpriseOne, some tables, especially in Financials, are structured using ragged hierarchies. A ragged hierarchy is one in which the parent attribute of one or more child attributes is not at the level immediately above the child. In short, some attributes in the hierarchy effectively have an empty parent-level attribute and descend from a grandparent attribute instead.

This table illustrates how information might appear in a ragged hierarchy:

Segment	Family	Class	Commodity
Mineral & Textile
Mineral & Textile	Mineral, Ores, & Metals
Mineral & Textile	Mineral, Ores, & Metals	Base Metals
Mineral & Textile	Mineral, Ores, & Metals	Base Metals	Titanium
Mineral & Textile	Mineral, Ores, & Metals	Precious Metals
Mineral & Textile	Mineral, Ores, & Metals	Precious Metals	Gold
Time, Jewelry, & Gem
Time, Jewelry, & Gem	Gemstone
Time, Jewelry, & Gem	Gemstone	Pearls
Time, Jewelry, & Gem	Timepiece
Time, Jewelry, & Gem	Timepiece	Watches

If you searched at the commodity level, the system would return only titanium and gold because at that level, watches and pearls are technically null values. To compensate, use the system function, Set Lower Limit, instead of Set Selection to build the WHERE clause of the SQL statement in this situation. With Set Lower Limit, you can have the grid display all records starting from the Titanium line down. With conventional filter fields it is impossible to display all the subsequent records because none of the other "class" fields are greater than or equal to Titanium. Set Lower Limit not only includes the most restrictive field (in this case Class - Titanium), but also includes each step in the hierarchy to determine if a record is actually "greater than" the lower limit record.

In general, this system function should not be used in cases where the user can affect the select. For example, QBE and filter fields are ways the user can affect the select. If the user can affect the select, then the user's select information should always be taken into consideration. This system function can be used in conjunction with Set Selection Append Flag to either append or replace the QBE or filter selection with the system function selection.