Monday, 12 July 2021

GL: Encumbrance Posting Errors and remedies

 Encumbrance Posting Errors  :


While posting GL Encumbrance Entries make sure to check the following:


1. If the Reserve for Encumbrance Account is setup for the selected Charge account.

2. Make sure there is not security restrictions are in place for the Selected responsibility through which you initialize to post the Entries.

3. If you are using the Custom Sources makes sure they are created correctly. 

4. The Custom Encumbrance Types setup under categories and encumbrances types.

5. Last but not least look out for silly errors ;)

·         The defined Reserve for Encumbrance Account (in the Set of Books or Ledger) must exist and be valid, when used for the same balancing segment values used in the journal lines.

·         The security rules or the cross-validation rules can cause the problem.

·         The Reserve for Encumbrance account is used to automatically balance the unbalanced encumbrance journals, by the posting program.

·         The responsibility must have access to the existing account combination or to create a new one if the combination does not exist.


Suggested Solutions : 

1) to confirm which is the specific account causing the problem, set the profile option 'GL: Debug Mode' to Yes at user level and rerun the posting program.

2) check the log file for a reference to a code combination.

3) Confirm that the account combination is valid, enabled and not secured by security rules or cross-validation rules.
Adjust the rules setup or assignments to allow the usage of the combination if required.


No comments:

Post a Comment

AOL : Query to fetch responsibilities attached to a User

 Query to fetch the responsibilities attached to a FND_USER login. SELECT t.responsibility_id,        t.responsibility_name,        v.RESPON...