Disable user during Month-end closing

apndy

Active Member
During month-end closing, to prevent user do transaction in JDE. we disable JDE ID of non-finanicial department. User always complain about it. They need to view some information in JDE. I want whether you have this issue in your company. Are there any good solution? Please help. thank you very much.
 
Create and assign a read-only role and remove all other roles and security (at the user level) that allow add/change/delete.
 
At month end create a snapshot/copy environment.
Update all relevant user role to have only access to this environment, and remove prod access.
After month end, swap them back.

Peter's suggestion of creating a read only role that is swapped in and out is the best idea, as the users won't be confused by being able to enter transactions that later disappear.
 
And don't forget to clear the security caches to have your changes take effect immediately.
 
This sounds nuts to me. Its what companies used to do way back when (days of calculators and abacuses). Modern systems (Like JDE) allow transactions to be processed for current period while Finance closes the previous period. To do otherwise can be business crippling in today's environment.
 
Greetings, and happy Friday!. Separate "Financial Dates" environments can be set up so that only those with access to the financial dates environment can update the prior period. Essentially, this is set up by having a separate company master apply to the financial dates environment. The financial dates environment can therefore have the company master values set to 2/28/2015, as an example, while the rest of the organization is moving along in March. So it's an environment-level setting, not a user-level setting. Hope that helps.
 
Thank you very much,

Create a public ID, a Read-only role. user can login JDE with this read-only user. Is it ok? please advise.
 
apndy,

Creating a public read-only ID is fine for users who only need read-only. BUT IT IS NOT NECESSARY to disable non-financial users during a close! If you have to do this your company is not setup correctly. IT IS WRONG! Due your due diligence and find out why.

I would advise you to find out why your company does not want transactions created. Like Larry Jones said "JDE allows transactions to be processed for the current period while Finance closes the previous period. To do otherwise can be business crippling in today's environment." If the closing company/calendar (F0010) is set correctly there should be no issues with non-financial transactions. They will go into the (new) current period while the Financial folks are closing the previous period.

Now if the accounting department is very large and you need to keep some of them out of the General ledger period being closed then read ALLHailEd's advise above. I have done this a few times.
 
Greetings, and happy Friday!. Separate "Financial Dates" environments can be set up so that only those with access to the financial dates environment can update the prior period. Essentially, this is set up by having a separate company master apply to the financial dates environment. The financial dates environment can therefore have the company master values set to 2/28/2015, as an example, while the rest of the organization is moving along in March. So it's an environment-level setting, not a user-level setting. Hope that helps.

This is the approach we usually see where the prior period still needs to be open for certain users while the rest of the business transacts in the new period.
 
Back
Top