Common Elements Used in Securing ChartFields

Field or Control	Description
Blank ChartField Values	ChartField Security rules are not enforced for blank values in ChartFields. If a row contains a blank value for a secured ChartField, access will be granted unless a different ChartField contains a value that is unauthorized.
Build Process	The process that builds the ChartField Security rules into a flattened table.
Component	A grouping of pages that are functionally related.
Distribution Code	A code that represents a combination of default ChartField values typically applied to a transaction distribution. Distribution Code security can be enabled or disabled by component. Distribution Code security behaves the same way as ChartField Security by controlling the list of values an end user is authorized to access. Distribution Code security is independent of ChartField Security with the exception of the Validation process when rules are built. The Validation process tests for conflicts between the equivalent ChartFields of the distribution code and any existing ChartField rules assigned to the user.
Inquiry	Pages used to support online queries of data.
Override Secured Prompt List	The configuration of security rules permits the user to bypass secured prompt lists for ChartFields.
Partial Access	You can set the Partial Access option to Deny Access or Grant Access. For example, for a transaction containing multiple rows of ChartFields (such as in Journal Entry), some rows contain authorized values of ChartFields and some do not. In this case, a user has partial access. Also, if one of the ChartFields in a row contains an authorized value but another ChartField value in the same row is not authorized, then the partial access option applies. That is, the user has access to Department 41000 but not to Program 6700. See Security Options - ChartField Security Page.
Security Method	The method you select for controlling security: user, role, or permission list.
Source Product	A way to partition the security values by product. For example, an accounts payable clerk can have different security setups in Payables and General Ledger.