QAD 2017 Enterprise Edition > User Guides > Financials > Setting Up General Ledger > COA GL Account Restriction
  
COA GL Account Restriction
Large corporations with many entities and with many general ledger accounts in a shared set may need to restrict an account and cost center to a particular entity. For example, a general ledger expense account may be shared across a domain, but it is used to record expenses incurred by one entity in that domain. Therefore, other entities should not be able to post to this account.
By default, an account applies in all the entities with the same GL shared set. GL Account Restriction Maintain enables you to restrict an account to a single or multiple entities. If you attempt to post to a restricted account, the system checks if the account is allowed in the corresponding entity. If not, the posting is prevented. Similarly, GL lookups only retrieve GLs that are available for the target entity. Any GL account that you manually input is also validated when you save your work to check whether the account is available in the target entity.
Note: For menus at domain level, the validation checks whether the account is allowed in at least one entity in that domain. For menus at entity level, the validation checks whether the account is allowed in that entity.
Important: When you enter a GL account for an operational program, the account is validated. However, for menus that generate operational transactions, such as PO Receipts, no check is performed because there are scenarios where the GL or entity is changed without user interaction.
For example, a sales order is to be shipped from Site A and validated for the entity to which Site A belongs. However, during the shipping process, the site is changed to Site B, which belongs to another entity. The shipping process does not require you to re-enter the GL account. Therefore, there is no additional validation at shipping to check whether the GL account is allowed for Site B’s entity. This scenario results in an error in Operational Transaction Post (25.13.7). In this case, you can correct the unposted GL transactions or change the GL restriction by entity settings.