This content has been marked as final. Show 8 replies
No, no need to set them up as buyers to access requisition. Looks like your our purchasing options are setup is not complete??
what could be missing,see i'm suporting stuff that has had a lot of people working on it and there is no documentation,i'll look at the options in the meantime.
Check if he has created a default folder with a saved query.
If yes, have him or the sysadmin, delete the folder.
PO screens have this problem. The "Save query" button is checked by default. So users don't realize it when they create a new folder. Once they save it, they can not query other requisitions.
Hope this answers your question
they have not created a default folder...
You know that you can not open an approved/inprocess req? Right?
1) Are all superusers having this problem or just one?
2) Can the superuser not open any req or just one?
3) Can the user query it up on the req. summary screen?
You mentioned that you are getting FRM-40212: Invalid value for field REQ_NUM error_. Please confirm which screen you are using to query requisition number (requisition Summary or Requisition form).. For query it is wise to use Requisition summary form.
Basically we get this kind of error in requisition form when
*1) A particular requisition does no exist.*
2) or If Requisition is valid but it is in Approved status.
How to resolve it.
1) create a new requisition, Save it..Please don't approve it.. Query the requisition in same screen..
Hope this will help :)
The requisition does exist and is valid,
if we create the super user as a buyer then he can quiry but if we don't he can't quiry and we get that error.
Any employee of an organization can raise a requisition, not necessarily that he should be defined as a buyer... To access requisition form in APPS, you need to be defined as an employee, not as a buyer. Please correct me if I am wrong here.
Did you check if any menu or function has been dropped from the responsibility? Do check what's the main menu attached (like Menu : Purchasing SuperUser GUI) to you PO responsibility. and all appropriate sub-menus of requisitions are attached to it.
e.g. Purchasing SuperUser GUI (Main Menu) ---> Requisitions: (Sub Menu) --> Requisitions Summary: Subfunctions, function : Requisition Summary