how to restrict posting of journals.
-
- Posts: 74
- Joined: Wed Aug 26, 2009 5:24 pm
- Location: India
how to restrict posting of journals.
Hi all,
I have business requiremnet that i have two responsibilites in gl for monitaring journals (clerk,manager)
clerk will enter journals and manager will review them and post either manual,subledgers,legacy.
the requirement is clerk should not have the possibality to edit or post journals he just can enter journal and view journals.how can we achieve this
Thanks ®ards,
stalin
I have business requiremnet that i have two responsibilites in gl for monitaring journals (clerk,manager)
clerk will enter journals and manager will review them and post either manual,subledgers,legacy.
the requirement is clerk should not have the possibality to edit or post journals he just can enter journal and view journals.how can we achieve this
Thanks ®ards,
stalin
-
- Posts: 463
- Joined: Thu Nov 09, 2006 4:50 pm
- Location: India
- Contact:
Dear Stalin,
this is a very common requirement, which can by met by MENU EXCLUSIONS feature provided in Oracle System Administrator responsibility while creating your responsiblities for the users ...
You should remove the Posting Functionality from a GL responsibility that is being assigned to the Clerk, so that he will be in a position to enter the journals and view already created journals, but he will not be in a position to post the same ......
Also there is another feature available in GL called JOURNAL APPROVAL, where the users after entering the journals need to submit the journal for review .... a notification is sent to the approver ... upon approving the journal, it becomes eligible for posting ....
Regards,
Karthikeyan
this is a very common requirement, which can by met by MENU EXCLUSIONS feature provided in Oracle System Administrator responsibility while creating your responsiblities for the users ...
You should remove the Posting Functionality from a GL responsibility that is being assigned to the Clerk, so that he will be in a position to enter the journals and view already created journals, but he will not be in a position to post the same ......
Also there is another feature available in GL called JOURNAL APPROVAL, where the users after entering the journals need to submit the journal for review .... a notification is sent to the approver ... upon approving the journal, it becomes eligible for posting ....
Regards,
Karthikeyan
-
- Posts: 74
- Joined: Wed Aug 26, 2009 5:24 pm
- Location: India
-
- Posts: 463
- Joined: Thu Nov 09, 2006 4:50 pm
- Location: India
- Contact:
Dear Stalin,
I am not sure about the possibility of having "Entering Journals" and "Not Editing entered journals" functionality in the same responsibility ....
We can either deny an user from completly entering any journals or we can deny the user from posting completly ....
Not sure as to whether personalisation / customization could be of any use out here ... will await for other members to comment as to the solution / workaround
Regards,
Karthikeyan
I am not sure about the possibility of having "Entering Journals" and "Not Editing entered journals" functionality in the same responsibility ....
We can either deny an user from completly entering any journals or we can deny the user from posting completly ....
Not sure as to whether personalisation / customization could be of any use out here ... will await for other members to comment as to the solution / workaround
Regards,
Karthikeyan
-
- Posts: 74
- Joined: Wed Aug 26, 2009 5:24 pm
- Location: India
-
- Posts: 463
- Joined: Thu Nov 09, 2006 4:50 pm
- Location: India
- Contact:
Dear Stalin,
For transactions that are being transferred from Subledgers, they use very limited account code combinations. For all those natural account segment values you can place the Segment Qualifier of Control Account, which will restrict creating/editing transactions from GL for those account code combinations..... This can be used provided you do not use those subledger code combinations for any other purpose in General Ledger.
Regards,
Karthikeyan
For transactions that are being transferred from Subledgers, they use very limited account code combinations. For all those natural account segment values you can place the Segment Qualifier of Control Account, which will restrict creating/editing transactions from GL for those account code combinations..... This can be used provided you do not use those subledger code combinations for any other purpose in General Ledger.
Regards,
Karthikeyan
-
- Posts: 3
- Joined: Tue Feb 05, 2013 8:00 am
- Location: India
Hi,
First: Use Menu Exclusion and take off all the Posting Functions from the Clerk responsibility.
Second: Use Form Personalisation and restrict the editing of all the Journals where journal source is not Manual (Remember when ever you create manually a journal in Oracle it source as standard will be Manual) and spread sheet if you are using web ADI. Any Technical can help you do this.
First: Use Menu Exclusion and take off all the Posting Functions from the Clerk responsibility.
Second: Use Form Personalisation and restrict the editing of all the Journals where journal source is not Manual (Remember when ever you create manually a journal in Oracle it source as standard will be Manual) and spread sheet if you are using web ADI. Any Technical can help you do this.
Who is online
Users browsing this forum: Google [Bot] and 0 guests