Load Rule Logic from File - GLUTRILR
Rule logic definitions, also known as GL Rules, may be entered using GLUPRU or by using this utility which will load user-defined comma-delimited files containing rule logic data into the database. The user will be prompted for the file containing the rule logic data. This file must have a record length of 512 bytes. The user will also be prompted for the rule logic file definition (ie,. The format of the comma-delimited file). "DEFAULT" may be entered to use the following default comma-delimited format.
File Upload ConfigurationNote: Field names correspond to those on the GLUPRU page (glr_rule_dtl).
Excel Column | GLUPRU Column Desc. | Additional Information |
|---|---|---|
A | Rule Ledger(glr_ledger) | A two-character Ledger Code within which the Organization Part has been defined. |
B | Rule COA Element(glr_org_part) | The organization part that can be a - four-character short description for the Org Key- Key Part - Object Group being defined- OBTY- *OBT- #OBT may be used to identify object type (RV, XP, AS, etc)- #S1-#S8 may be used for Org.Key select codes- #M1-#M8 may be used for Org.Key miscellaneous codes |
C | Rule Code Value(glr_part_code) | Part Code - The actual code defined for the given Org.Key, Part, Select Code, Misc Code, Object, Object Type, or Group in Column B. |
D | Ledger(glr_gr) | A two-character code used to define which ledger is associated with the "Part Code" in Column C. If this is left blank, then the Ledger code in Column A is assumed. |
E | COA Element(glr_attr) | Org. Code - The four-character short description for the Part Code which as a specific relationship to the "Organization Part" in Column B. OBTY, *OBT, or #OBT may be used to identify object type (RV, XP, AS, etc). #S1-#S2 may be used for Org.Key select codes. #M1-#M8 may be used for Org.Key miscellaneous codes. |
F | Relational Operator(glr_relop) | Defines the relationship between the "Org. Code" in Column E and the "Part Code" in Column G which may be associated with the given "Organization Part" in Column B. Valid relational operators are: "=", "<", ">", "<>", ">=", "<=", or "==". Note that "==" is the same as "=", but may be used to define defaults for new Org. Keys and Object Codes. |
G | Value(glr_val) | The actual code defined for the given Org.Key, Part, Select Code, Misc Code, Object, Object Type, or Group in Column E. Ranges (two values separated by a "-") that are entered in this column will automatically be split into two entries, with the second entry having the opposite Relational Operator (Column F) from the first. |
H | Logical Operator(glr_logop) | This field is optional and is used when there exists a dual relationship between multiple "Org. Codes" (Column E) and their "Part Codes" (Column G). For example, when the Function can only be "ADMN" when the Division is "SD," the logical operator would be "AND." Valid logical operators are "AND" or "OR." |
I | Priority(glr_pri) | Up to 8-characters which identifies the order in which the defined logic should be reviewed. Optionally, a user-defined common code (the first 6-characters of the GLRL common code), which contains the file definition, may be entered. See the description of the GLRL/xxxxxxyy common code for information on how to setup the user-defined definition. If you use the default file layout, field defaults may be defined via the common code GLRL/DEFAUL00. If you use a custom layout, the common code GLRL/xxxxxx00 may be used. See the common code descriptions for information on setting up these common codes. |
A report will always be produced, which shows all entries that are being loaded in the database and identifies any problems with the data that might need to be fixed once the data has been loaded. The process also supports a test mode, in which only the report is produced, and no entries are written to the database. This is the best way to catch and correct any exceptions before actually loading the rule logic into the database.