Is it possible to prevent a user from creating and approving a JV

Hi,
Is it possible to prevent a user from creating and approving a JV. We have a rule that one user cannot do both. What happens is user#1 creates the JV, then some other user#9 approves the JV. Both user#1 and user#9 need to be able to create a JV and approve someone else's JV.
The transactions in question are...
F-02 General Posting - enter Journal Voucher (create & post)
F-65 Enter General Document - Parking (create)
FBV0 Post or Delete a Parked Document (approval)
Please let me know the details.
Thanks in advance,
regrads,
Chaks

Hi,
Requisition is submitted.....it means Requisition is saved or it means Requisition is Released..?
Regards,
manish

Similar Messages

How to prevent public users from creating and saving Word Documents

I have two public computers available for the public to view legal case documents. The program used uses the Word shell to save, view and print documents within the program. The clerk has stated that she does not want attorneys or others to
be able to create and save word documents on these computers. Is there a way to prevent a user on the public computers from opening word, creating a document and saving it?

Instead of installing Word on the public computer (or at least instead of making it available on the public account), you could install the free Word Viewer:
https://www.microsoft.com/en-us/download/details.aspx?id=4 and make that available for the public account. Alternatively, if you want to ensure the document retains its originally
formatting regardless of what printer may or may not be attached to the public computer, you could keep only PDF copies of the file where the public can access them and install the free Adobe Acrobat Reader for viewing:
https://get.adobe.com/reader/.
Cheers
Paul Edstein
[MS MVP - Word]

Cannot prevent authenticated users from creating a blog on "My Page"

I have a brand new Snow Leopard (10.6.1) 2.26 Ghz quad core Xserve with 12Gb RAM that will be used for web collaboration services. I've currently set up Wiki and Blog services with a group membership to allow creating wikis/blogs. The reason for this is for staff development purposes with the plan to add people into the group as they are trained. The process to set it all up was very simple, however, I'm having an issue preventing authenticated users from creating a personal blog. Although I can prevent the creation of wiki's to members of a group easily, any authenticated user on the server can log into "My Page" and will be able to create a blog. I've gone to server admin>choose the server>choose the "access" icon and set the column "for selected services below" (blog) to "allow only users and groups below" (the group) and it still doesn't prevent them from making a blog page. In WGM for the group on the "Basic" tab, the "enable the following services for this group" has only the choice of "none" and therefore since the site isn't showing as a choice, the Wiki, Blog, Calendar and Mailing List is grayed out. I've seen another thread that states in 10.6 that option for setting the service acl in the group settings of WGM is unavailable. Does anyone know a fix for my problem of security access for a "My Page" blog or is it a possible bug in Snow Leopard? Right now my only workaround is to remove the users access and enable it as they are trained. This isn't an ideal fix, however, because we have some users who want to limit their wiki or blog to authenticated users only, not public access. Any help will be greatly appreciated.
Message was edited by: dstrollo.il

Ran into this same issue.... Talked with a field engineer who confirmed the behavior. The question now is this a defect or "feature that does not work as as the audience desires". As I far can tell, the security setting for blogs in server admin does nothing at all. This has the potential to cause a few issues as you cannot limit who can have a blog.
Message was edited by: jlindler

10.6.1 Server - cannot prevent authenticated users from creating a blog

I have a brand new Snow Leopard (10.6.1) 2.26 Ghz quad core Xserve with 12Gb RAM that will be used for web collaboration services. I've currently set up Wiki and Blog services with a group membership to allow creating wikis/blogs. The reason for this is for staff development purposes with the plan to add people into the group as they are trained. The process to set it all up was very simple, however, I'm having an issue preventing authenticated users from creating a personal blog. Although I can prevent the creation of wiki's to members of a group easily, any authenticated user on the server can log into "My Page" and will be able to create a blog. I've gone to server admin>choose the server>choose the "access" icon and set the column "for selected services below" (blog) to "allow only users and groups below" (the group) and it still doesn't prevent them from making a blog page. In WGM for the group on the "Basic" tab, the "enable the following services for this group" has only the choice of "none" and therefore since the site isn't showing as a choice, the Wiki, Blog, Calendar and Mailing List is grayed out. I've seen another thread that states in 10.6 that option for setting the service acl in the group settings of WGM is unavailable. Does anyone know a fix for my problem of security access for a "My Page" blog or is it a possible bug in Snow Leopard? Right now my only workaround is to remove the users access and enable it as they are trained. This isn't an ideal fix, however, because we have some users who want to limit their wiki or blog to authenticated users only, not public access. Any help will be greatly appreciated.

Thanks for the suggestion, but that would prevent all users from creating personal blogs. I was hoping to be able to have a group of users that can create a personal blog outside of the blog attached to a wiki.

Is it possible to restrict the user from creating a sibling and allow him to ONLY create child nodes in DRM?

When in a hierarchy, a user right clicks on a node to crate a new node, he has two options
-Child
-Sibling
Is it possible to restrict the user from creating a sibling and allow him to ONLY create child nodes?
Business cases:
1. different level nodes need to have different prefixes.
- Thus, the default prefix property definition uses the level number to assign a prefix
- Also, a validation, to ensure the correct prefix, uses the level number
But if the user can create a child and a sibling then the default prefix will only be right for a single case and not both.
Thanks

If the images are exactly the same size then make sure the layer with the mask
is the active layer and in the other documents go to Select>Load Selection and choose
your document with the layer mask under Source document and under channel choose the layer mask.
After the selection loads press the layer mask icon at the bottom of the layers panel.
MTSTUNER

Is it possible to prevent the OS from dropping and deleting a network share shortcut?

One thing that has always bugged me about Mac OS is that when a network share becomes unresponsive or unavailable the shortcut on the desktop disappears and you get a glaring messaging that the share has been disconnected.
Is there any way to prevent a network share from being removed just because it becomes momentarily unavailable?
As an example, on a Windows machine the network share shortcut remains, you simply cannot use it but it is there and ready to go the moment the share comes back online. Is there some way to make OS X behave in this manner? Or is there a way to extend the time out interval for a network share?
Thanks.

Drag the icon into the sidebar of a Finder window under FAVORITES.

Prevent a user from accessing Cube Navigator

Is it possible to prevent a user from accessing the cube navigator in Analyzer so the user can only view reports that are setup? thanks

In Analyzer 6.2, there are some 'behind the scenes' parameters that can be added to suppress menu items. If you are currently using Analyzer 6.2, try adding the following parameter to your applet tag:<PARAM NAME = HideNav VALUE ="True">Note: this will hide the Navigate button for all users accessing the page.

Prevent multiple users from updating coherence cache data at the same time

Hi,
I have a web application which have a huge amount of data instead of storing the data in Http Session are storing it in coherence. Now multiple groups of users can use or update the same data in coherence. There are 100's of groups with several thousand users in each group. How do I prevent multiple users from updating the cache data. Here is the scenario. User logs-in checks in coherence if the data there and gets it from coherence and displays it on the ui if not get it from backend i.e. mainframe systems and store it in coherence before displaying it on the screen. Now some other user at the same time can also perform the same function and if don't find the data in coherence can get it from backend and start saving it in coherence while the other user is also in the process of saving or updating. How do I prevent this in coherence. As have to use the same key when storing in coherence because the same data is shared across users and don't want to keep multiple copies of the same data. Is there something coherence provides out-of-the-box or what is best approach to handle this scenario.
Thanks

Hi,
actually I believe, that if we are speaking about multiple users each with its own HttpSession, in case of two users accessing the same session attribute in their own session, the actually used cache keys will not be the same.
On the other hand, this is probably not what you would really like, you would possibly like to share that data among sessions.
You should probably consider using either read-through caching with the CacheLoader implementor doing the expensive data retrieval (if the data to be cached can be obtained outside of an HTTP container), or side caching with using Coherence locks or entry-processors for concurrency control on the data retrieval operations for the same key (take care of retries in this case).
Best regards,
Robert

Is there a way to prevent a user from using the graph cursor legend to delete a cursor?

I would like to have 2 cursors on a graph that can't be deleted by the user.

Hi Dennis,
I'm having this problem as well, and found your post. Are you referring to the Enabled State of the entire graph? If so, this prevents the user from moving the cursor at all while the VI is running, which, of course, defeats the purpose of having a cursor at all. Ideally, I would like to show the cursor palette and disable it's run-time shortcut menu. This doesn't appear to be possible. One workaround would be to hide the palle and instead include some indicators that show the cursors' values. I'd prefer to show the palette to keep the program simpler.
Any other solutions?
Thanks,
Alan
Alan Blankman, Technical Product Marketing Manager and LabVIEW Developer
LeCroy Corporation
800-553-2769 x 4412
http://www.lecroy.com
[email protected]

How to prevent users from creating transactional problems?

Dear Sirs...
Using JDeveloper 10.1.2 and ADF UIX technology. If i created a web application that contains many pages. Assume the application contains pages A,B,C,D.
The end user should access the pages A then B then C then D to get the transaction executed and commited correctly.
the problem is:
1- if a user navigates from A to B to C then he press the Back button to A then he commits the transaction, the data would be stored in correctly.
2- if page C requires some preparations in page B (initalization of session variables) and the user enters page A then he changes the URL to C, then this would cause inproper execution of application and so the data would be stored incorrectly.
so how can i prevent the user from pressing the back button of the browser (which i do not think is possible) or how can i prevent him from making any errors by inproper page navigation?
thanks for any help in advance and best regards

I really don't know if this is the correct way of doing it, but we prevent navigation directly to any page within our application if the HTTP Referer header is null. If it's null, we redirect to a page that says the user should use the navigation buttons provided and not enter the page via bookmarks, history, or direct navigation via a typed in URL.

Preventing the User from going back to the main page after logging out.

Hi all,
In my project I want to prevent the User from going back to the Main page, by clicking the back button of the browser, after the user has loggged out.I had invalidated the session so the user will not be able to do any operations, but he can vew the infos. I want to redirect to the login page if the user tries to go back using the back button after he has logged out.
I tried the same in this forum after loging out. Surprisingly it is the same. I can browse through all the operations i did even after logging out from here.
Is it not possible to do that in Servlets?Could somebody help?
Thanks,
Zach.

Hi,
You can use a servlet filter to do this , as it can interceptany request to your application you can decide to allow user access or not to any page/servlet.
public class Test implements Filter{
     public void destroy() {
     public void doFilter(ServletRequest arg0, ServletResponse arg1, FilterChain arg2) throws IOException,
               ServletException {
          System.out.println("filter");
          HttpServletRequest request = (HttpServletRequest) arg0;
          if(!request.getRequestURI().contains("index")){ // set condition that will be checked to verify if the user is logged in
               System.out.println("redirecting ... ");
               RequestDispatcher d = arg0.getRequestDispatcher("/index.jsp");
               d.forward(arg0, arg1);
          arg2.doFilter(arg0, arg1);
     public void init(FilterConfig arg0) throws ServletException {
}in you web.xml add :
<filter>
          <filter-name>test</filter-name>
          <filter-class>test.Test</filter-class>
     </filter>
     <filter-mapping>
          <filter-name>test</filter-name>
          <url-pattern>/*</url-pattern>
     </filter-mapping>

Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in oracle and yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

Hi All, We are in to Release 11.5.10.2.There is a specific requirement to Prevent users from creating Manual Sales Orders in Oracle and yet users should be able to book the Sales Orders Imported from CRM system into Orcale.Please advise.

Thanks for your advise.
However, I missed to mention that we have two set of users One is for Finished Goods and another for Spares.
Only Spares users need to be prevented from creating Direct/Manual Sales Orders in Oracle.
As you suggested, if this will be done at Form level, that may Disallow FG users also to create Manula Sales Orders which should not be the case.
Further, I tried to test one scenario through Processing Constraints but it did not work.
Application
OM
Validation Type
Entity
Temp
Short Name
TBL
Validation Semantics
Created By
Equal To
User(Myself)
Processing Cosntraint
Application
OM
Entity
Order Header
Constraint
Operation
User Action
Create
Not Allowed
Conditions
Group
Scope
Validation Entity
Record Set
Validation Template
101
Any
Order Header
Order
Above Created
Please advise.

How to prevent multiple users from updating the same data in coherence

Hi,
I have a Java Web Application and for data cache am using coherence 3.5. The same data maybe shared by multiple users which maybe in hundreds. Now how do I prevent multiple users from updating the same data in coherence i.e. is there something in coherence that will only allow one user a time to update. If one user is in a process of updating a data in coherence and some other user also tries to update then the second user should get an error.
Thanks

I have a question on the same line. How can I restrict someone from updating a cache value when I a process is already working on it. I tried locking the cache key but it does not stop other process to update it , it only does not allow other process to get lock on it.

Prevent multiple users from editing/approving the same form SPD 2013,SP 2013

Hello all, I have a workflow with a to do task, the task is assigned to a group so any of the users in that group can go in and do a quality check on form data and approve it. How do I prevent multiple users from working on the
same form? do I just require check out? or is there a way to notify the rest of the group that a user has already started the quality check.

The "Require Checkout" option is your best bet. You can also enable the auto checkout on edit option to allow minimal effort on the side of the user. Other users will then get the error message stating the item is checked out, if they try to
edit it.
If you'd like, you could add a workflow to the task list that triggers when something is changed. That workflow can check if the item is checked out and if so, email the other users assigned to the task.
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

How to prevent a user from entering characters into a number field

How do you prevent a user from entering characters like A or B into a field that is defined as a numeric field?
Please note that
- we use block validation (for other reasons)
- we are not able to convert these numeric fields to character fields
We want to avoid a user being hasseled with the FRM-40209 ... message.
This message is
- not very helpfull because it does not inform us what the problem field is
- not suppressable
Any hints ?

I went back to the drawing board on this one.
You are absolutely right : the message can be catched !
By writing an on-error trigger you can check for the error number. Sadly enough my first attempt on this used the on-message trigger which never fired hence my desperation.
Anyway, the on-error trigger in combination with :SYSTEM.CURRENT_ITEM or :SYSTEM.TRIGGER_ITEM enables me to display a more meaningfull message to my users.
Thanks for the hint.

Is it possible to prevent a user from creating and approving a JV

Similar Messages

Maybe you are looking for