Source Code Security

Source code security is utilized by assigning codes that identify the access that is permitted on transactions that were automatically created by the program. The following illustration shows different levels of access which have been assigned to source codes:

If you are configuring your General Ledger system, fill out the Source Code Definition and Security worksheet to define your organizations source code security values.

Different offices in your organization can use programs to create transactions for the General Ledger. These programs use information to create the transaction amount, account number, description, etc. For example, the Payroll module creates labor distribution transactions (source code LB) on the basis of the employees departments, wages, and salaries. The General Ledger transactions reflect the payroll information for each employee.

In cases where module programs create the transactions, the General Ledger transactions must usually match the module data. For example, labor distribution amounts must match employee payroll totals. (You do not want to print a paycheck in the Payroll module and then record a different amount in the General Ledger.) Generally, the Business Office posts these transactions without changing them. However, if a person changes or deletes the transactions before posting, the General Ledger could easily get out of synch with the module data.

The General Ledger module allows you to restrict access to certain transaction source codes. In other words, source codes may be identified that do not allow anybody to alter or delete transactions after the module program has created them.

Each access code allows the user to view the transactions. You can use the codes to grant varying combinations of delete and change access. A security code can be applied to each source code on the system. Most source codes will carry a blank code since total access to General Ledger transactions is usually desirable. However, as illustrated in the following example, you may want to restrict access only to those source codes that are automatically created in other offices.

Example

Related Topics

Source Code

Enable Audit Trail History