PROCESSIT 7.4 R1
For Oracle Fusion Middleware 11g

GL Security Settings

©2025 Copyright ReadSoft AG (publ). All rights reserved. The contents of this document are subject to change without notice. ReadSoft is a registered trademark of ReadSoft AB. Other product and company names herein may be the trademarks or registered trademarks of their respective owners.
Questions or comments about this document may be emailed to documentation@readsoft.com.

ReadSoft AB (Head office) | Södra Kyrkogatan 4 | SE-252 23 Helsingborg | Sweden | Phone: +46 42 490 21 00 | Fax: +46 42 490 21 20
ReadSoft AG | Falkstrasse 5 | 60487 Frankfurt | Germany | Phone: +49 69 1539402-0 | Fax: +49 69 1539402-13
info@readsoft.com | www.readsoft.com

GL Security SettingsGL Security PurposeConfiguring GL security rulesConfiguration notes for Oracle E-Business Suite versionAccounting using GL Security Rules

GL Security Settings

GL Security Purpose

GL Security Rules can be enabled to force account coders to select the appropriate ERP Accounts Payable responsibility during invoice accounting.

Configuring GL security rules

GL security is based on users selecting responsibilities while performing accounting tasks. It is configured via configuration parameter.

  • Enable GL Security Rules must be se to Y to enable GL Security Rules and have account coders select an Responsibility.
  • Security Rules Application specifies which application's responsibilities should be used. The default is Account Payables, with the value SQLAP.
  • Responsibility Required For Coder determines if you must select a repsonsibility to submit an invoice for approval. If enabled when set to Y, users must supply a responsibility. If disabled, when set to N, the default responsibility Running Accounts Payable Import is used.

Configuration notes for Oracle E-Business Suite version

In Oracle E-Business Suite 11i, the responsibilities are based on MO : Operating Unit.

In Oracle E-Business Suite R12, they are based on a composite of MO : Operating Unit and MO : Security Profile.

To make use of MO : Security Profile’ in R12 must create a Security Profile and associate all desired Organizational Units with that Security Profile.

Associate the named Security Profile you create with MO : Security Profile system value at responsibility level, and the Run the Request.

Accounting using GL Security Rules

When GL Security Rules are enabled, account coders must select a responsibility before submitting an invoice for approval. The responsibility is selected in the Task Details window main menu. The option is only available when GL Security Rules are enabled.

The responsibilities available in the selection list are those assigned to the task owner, not the user currently logged in. If you are handling invoices for other users as administrator or via shared worklist, you can still only select responsibilities for the user that the task is assigned to. The responsibilities are those assigned to the task owner in the configured application.

The available choices are also filtered by the organizations that the task owner is associated with, and also depend on the setting og Security Rules Application.

If a responsibility is required during accounting, and not responsibility for the current task owner is found, they can select <empty> from the drop down list to use the default responsibility for running accounts payable import.

If the account coder does not select the correct AP responsibility, an error message is shown when the account coder clicks Submit.