Hi Chathurika,

It is not advised to use an account which has Manual Voucher Entries in to a Posting Control which requires the GL Account to a mandatory “Ledger” Account. The Ledger lock is applied to ensure that Reconciliation of such Account Details is Easy/Controlled when Reports are involved (For Ex - Customer Ledger Open Items) .

You can recommend the following,

1. To use a New Account with the Same Accounting Type/Account Group with relevant Number Series
2. If Customer insists on using the same account then Make the Change from a New Month and ensure that the Previous Month Details of the Account are logged. Further have a audit note informing that the account Detail will be used for a Report Reconciliation from a Particular month only

Thank You

Best Regards

Ramessh Kanna

In addition to what Ramessh explained above, I would add that current balance of this account (effect of manual vouchers) should be zero (at each most detailed level - all code parts, currency amounts, parallel amounts and quantity). Otherwise it will impact later reconciliations. 

Hi, 

A user cannot make the change after an account has been used. 

Assuming some table change is considered the most important consideration is - based on the account and the account usage does the usage require a ledger account or not. 

For example assume account 12345. Assume this is used by posting type IP2.   In IFS speak this is AR Trade (used as AR Trade). In no possible way should that account ever be set as a non ledger account. No SQL table update should be used to set that account from ledger to non ledger.  If the account “was” used by a posting type in IFS that requires a ledger account extra caution needs to be considered. Even if the account is no longer used by IP2 (for example) changing the ledger flag can / will cause issues going forward unless “other” steps are performed. 

Best suggestion, locate all posting types that use that account (run posting control report and search the PDF for the related account.   Get the posting type.  Temporarily create a new posting control for that a non-ledger account such as 5000 (use an old date or date far in the future) and save. If the save is successful, that posting types does not require a ledger account, else if IFS produces an error that the account must be ledger account then that posting type does require a ledger account.  

Assuming all posting control for the given account has been tested / does not require a ledger account, and the account was never used in the various posting types that require a ledger account,  then the account can possibly be set to non ledger account. A user can’t do that. 

By far the safest / recommended process is create a new account.   But assuming all the rules are followed, many people have changed an account from ledger to non ledger. I’ve done this countless times.  But you “must” follow the rules, as if you don’t it can create a mess.  A user can not make this change. 

Best regards, 

Thomas

Hi, 

Received additional explanation. The intent is to move a non ledger account to ledger account so that the given account can be re-used as the GP3 account. 

Hi,

OK – Far better understanding of need. 

Yes, this can be fixed.   To move this to a GP3 posting control, they will need top move the balance out in all code parts.  See balance analysis and select all display options life to date (period does not matter)

You would do something like the below to get the balance.  This would select a given account, and the current year (all periods).

Then move the balances to a different account.   Update GL and do same query to make sure 100% certain balance is really zero. 

Then change the flag.

Best regards,

Thomas