Posting Mappings - GLUTSPPM

All posting mappings are set up through the Posting Mappings (GLUTSPPM) screen. This screen is used in conjunction with GLUTSPSI. Posting mappings eliminate the need to enter the Mapping Code during data entry time by automatically determining the appropriate code for each transaction based on the data entered on the Default Posting Mappings page. The order in which the posting codes are entered on the Posting Mappings page determines the order the system will search to find the applicable posting mapping 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-hand side. 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 mappings data on the main section 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 codes'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 CKID code to use.
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 CKID code to use.
Mapping Code: Enter the specific mapping 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 Mapping.

History User Interface

The History User Interface (UI) provides a simple and efficient way of saving Posting Mapping data records. To access the History UI, select "Preferences," then 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 GLUTSPPM utility as a whole. Both a date and numeric value are required in case posting mappings 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 mappings data were changed for the JT ledger, a snapshot of the current posting mappings data would be saved as a new history record after a click to the Save button.

In order to reload a history record, open up 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 Mappings.