ERPstuff - Oracle EBS Community

Dear Members [:)],

I have a requirement which is as explained below:

For a certain GL Super User responsibility, I want to restrict the posting for certain categories.

For instance let us say I want to restrict the posting for a journal category 'A'.

So,as soon as user queries the journals with categories A the posting button in the form should be disabled.

Is there any standard functionality by which we can acheive this?

Thanks in advance for your valuable replies.

<font color="blue"><b>Regards,
Arun Reddy</b></font id="blue">[:)]

merely by removing the posting option present in the value set will have no impact on the post button available in GL journol window.....what u have to do if u want to take away the posting rights from the user remove the post functionality button from its responsibility,u can do it from the system adminstrator responsibility.....but if u want that user should retain this right but only this account will not be posted in GL ur fist solution is valid.

Try forms personalization. thanks

i think form personalization will effect all....can we control limit like petty cash through form personalization???

Generally Form personalisation effects at user level not atresponsibility level. Create a new user for concerned and do the form personalisation. it will effects at that particular user only. Let me know if any other possibility.

thanks sree02.oracle for providing valuable info,r u sure it is at user level and my question is still intact can we control limit like petty cash through form personalization???

Please do not mix two different issues under one topic. For petty cash related issue check the following topic,

topic.asp?TOPIC_ID=3675

Thanks

Dear Members[:)],

I forgot to update this topic.

I acheived this functionality by doing forms personalization at the responsibility level.

Forms Personalization can be done at the responsibility level.

Now it is working.

Thanks a lot for all of your valuable replies.

<font color="red"><b>Best Regards[:)],
Arun Reddy.</b></font id="red">

Dear Arun,
It will be nice if you can share the steps you have taken with screen shots. Thanks

Dear Admin [:)],

Because of security reasons I cannot share the screens but I can explain the steps in detail what I followed.

<u><b>The steps are as follows:</b></u>

<font color="red"><b>Note1</b>:</font id="red">Here I have restriced the posting of journals of a category known as 'BACH'.So all the conditions include this value.

<font color="red"><b>Note2:</b></font id="red">All the triggers I have created at responsibility level.

<font color="red"><b>Step1:</b></font id="red">

To restrict at the folder level I have created two triggers which are as follows:

1/ Name: XX_Folder_Post
Trigger: When-New_Record-Instance
Condition: ${item.folder.user_je_category_name.value} ='BACH'

For this condition I made the display of the respective post button as false.

2/ Name: XX_Folder_Post1
Trigger: When-New-Record-Instance
Condition: ${item.folder.user_je_category_name.value}! ='BACH'

For this condition I made the display of the respective post button as false.

<font color="red"><b>Step2:</b></font id="red">

At the batch level since we cannot differentiate the journals based on category ,I have restriced the posting of journals source wise.

To restrict at the batch level I have created one trigger which is as follows:

Name: XX_Batch_Post
Trigger: When-New-Record-Instance
Condition: ${item.batch.je_source_name.value}='Manual'

For this condition I made the display of the respective post button as false.

By following the method described in <font color="red"><b>Step1</b></font id="red"> I have created similar type of triggers at the header level and also at the creation of new journals.

This made me to acheive the respective functionality.

<font color="red"><b>Best Regards[:)],
Arun Reddy.
E-Mail:arunapps@gmail.com</b></font id="red">