Posting Preferences - GLUTSPPP

All posting codes are set up through the General Ledger (GL) Posting Preferences (GLUTSPPP) utility. This utility is used in conjunction with the GL Subsystem Interface (GLUTSPSI) utility. Posting Preferences eliminate the need to enter the Posting Code during data entry time by automatically determining the appropriate code for each transaction based on the data entered on the subsystem's Default (DFLT) Posting Preferences page. The order in which the posting codes are entered on the Posting Preferences page determines the order the system will search to find the applicable posting code for a given transaction. Therefore, it is important to enter data on the page in a hierarchy from specific to general.

Posting Preferences Data Entry

Users can navigate to a ledger/subsystem/report register conveniently by using the entity list panel on the left side of the WebClient page. This list contains a ledger control allowing the user to easily select from all ledgers defined in BusinessPlus. Then, the subsystem/report register can be selected from the list below the ledger by clicking on the desired record. This will automatically load the posting preferences data on the main form of the page.

After entering/updating posting preferences data, click the Save button to store the information in the database. If changes were made to the data and not saved, the user will be prompted if they wish to save their current changes and action will be taken accordingly.

To add a new record, enter the desired information on the row with an asterisk ( * ) in the first column. To insert a row, right-click the desired row to insert before and select "Insert New Row." To delete a row, select the desired row to delete and press the delete key on the keyboard. Note that the Save button must be clicked after making ANY changes to the posting preferences data. If a change was detected and the user tries to navigate to another row or close the application, they will be prompted to save the information first before performing the desired operation.

If there were any problems saving data to the database, an error list will appear and there will be a red exclamation point beside every row containing an error. No data for the current record can be saved until these errors are fixed.

Data Entry Definitions

Attribute: A specific portion of the BusinessPlus structure which is used in analyzing the details associated with a transaction in the batch to determine which CKID code should be used.
Defined codes could be:
DIV AP or AR divisions
KEY The defined org key's short 4-character description of the org part
OBJ The defined obj code's short 4 character description of the obj group
NUMG The manager code of the current user defined in nucleus common codes
NULC The location code of the current user defined in NUCLEUS common codes
Low Value: This field allows for the entry of a specific code which relates to the BusinessPlus structure in the Attribute field. This is considered the lower bound for this Attribute value when a batch needs to determine which code to use, like with a CKID.
High Value: This field allows for the entry of a specific code which relates to the BusinessPlus structure in the Attribute field. This is considered the upper bound for this Attribute value when a batch needs to determine which code to use.
Posting Code: Enter the specific posting code (001, 002, etc.) which should be used under the defined 'If Attribute is between Low Value and High Value' conditions. Under certain circumstances it may be necessary to relate two or more 'If' conditions together. When this is the case, place the word "AND" in this field. In the last defined "If" entry place the required Posting Code. Posting preferences (GLUTSPPP) are stored in NU Common Codes (NUUPCD). The Category/Value would be GLxx/DFLT#### where GL is always GL (as the subsystem of the utility, not the ledger code), xx is the subsystem (AP, AR, CR…) and #### is a sequential number.
For example, the first record in GLUTSPPP for AR would be: GLAP/DFLT0001 where AP is the subsystem and 0001 is the first sequential number.
For PY posting preferences, the subsystem is CP, DP, or EP.
Within each GLxx/DFLT#### common code:

The ledger field is stored in the common code ledger field.
The short description has the default.
The first associated code is the attribute name.
The second associated code is the low range for the attribute.
The third associated code is the high range for the attribute.
The fourth associated code is the posting code to set it to.

A common code will be created for each line on the posting preference.

History User Interface

The History User Interface (UI) provides a simple and efficient way of saving Posting Preferences data records. To access the History UI, click the Preferences tool strip and select "History."

The History UI initially presents the user with options that describe when the software will automatically begin deleting history records. This is the "General" tab and is not specific to a ledger/subsystem/report register. These values are specific to the GLUTSPPP utility as a whole. Both a date and numeric value are required in case posting preferences data remains static over a long period of time. This enables the user to specify a date significantly in the past to prevent deleting records unintentionally when the numeric value was set to a low number. Note that there is a limit on 25 records per ledger/subsystem/report register, however specifying a date in the past could cause the system to not delete records until BOTH the date and the numeric value constraints are satisfied.

The "Records" tab contains detailed information regarding when history records were created. This information is saved on a ledger/subsystem/report register basis. If the current posting preferences data were changed, a snapshot of the current posting preferences data would be saved as a new history record after a click to the Save button.

In order to reload a history record, open the History UI and navigate to the Records tab. Select the desired history record from the tree view control and click "Apply Changes" to reload the Main Form with the history record. Note that the Record Info text box on the Main Form will reflect the history record chosen by displaying the date/time of the selected record. Likewise, the History UI Records tab will also display "(Selected)" beside the record currently displayed on the Main Form. This provides easy identification on which record is currently selected.

Note that when saving a history record the user is prompted to see if they really want to make a history record the current data used for Posting Preferences.

Tools

After defining or changing the Posting Preferences records, launch the tool to Rebuild the Posting Preferences and update the associated common codes.