In this post we are going to see how you can assign Process monitor access to users in Markview when users do not get access through mapped Oracle application responsibilities-
Normally users get markview accesses through Oracle responsibilities which are mapped to respective user group / user role.
There is a Markview API MVERP_User_Setup_Util.SynchUserRespGroupsRoles which can be used through trigger / Alert / Concurrent program etc to sync up Markview users with Oracle applications users.
If an user wants Process Monitor access which is generally a privileged access without requesting access in Oracle apps then do the following,
Step:1 Process monitor access resides in Utilities menu so
Go to, Administration > Menu Item Group Auth
Search for "Utilities" and see which user group gives that menu.
Step:2 Then go to, Administration > 170 MarkView Administration
Search for the user to whom "Process Monitor" access needs to be given >Go to Details> "User Group Assignments" menu > Add the user group found from Step 1.
Step:3 Give following access to the user in Process admin menu,
Go to Administration > Process Admin
Search for the user to whom "Process Monitor" access needs to be given >Go to Details> "User Role Grants" menu >
Give following roles to the user,
SQL*FLOW ADMINISTRATION
SQL*FLOW MONITOR
Save the configuration.
Walla!! This is it.
Clear browser cache (otherwise you would not see the changes immediately) > Login as the user > User would now have Process Monitor access.
Friday, January 22, 2010
Thursday, January 21, 2010
How to sudo in unix
What is Sudo?
How to Sudo?
For login as another user use the below command in the command line,
$ sudo -u user_name -H bash
--Replace user_name with the user name you want to sudo to
This will prompt for your password. If you are listed in the sudoer list then you would be logged in as user_name upon successful credentials.
How to Sudo?
For login as another user use the below command in the command line,
$ sudo -u user_name -H bash
--Replace user_name with the user name you want to sudo to
This will prompt for your password. If you are listed in the sudoer list then you would be logged in as user_name upon successful credentials.
ATF (After-the-fact) Invoices
You might have heard about senior management in companies / finance dep / CFO shouting to reduce the number of ATF Invoices.
--What is an ATF invoice?
--How to control them?
--Different types of ATF invoices
In this post I would try to answer all of these,
1. What is an ATF Invoice?
ATF invoice stands for After the fact invoices which means any invoicing happens before related PO is created in other words where PO approval date is later than Invoice date.
2. ATF invoices can be controlled via a hold in Invoices. Generally companies name it as "ATF PO". Through this finance operations managers, controllers and all keep track of all these expenses. Payment through NON-PO / ATF-PO invoices are considered as bad finance management / planning and it hurts company's budget.
3. Although companies try their best to stop ATF Invoices but there are genuine instances wherein invoice lands in ATF. Reasons for that like there is some mistake happens in the original PO such as currency issue etc. and it is known only when invoice is received and in order to pay that invoice another new PO is created for paying the invoices. In that case the invoice becomes ATF because it is before the new PO is generated.
To keep track of such genuine instances following can be done,
Step 1. Create a DFF at PO header level to keep reference of the old PO number.
Step 2. Create a custom program and schedule it to remove the ATF hold automatically by checking if the new PO has DFF populated with the old PO and the old PO approval date is before the invoice date.
To make this process full-proof, a validation can be put in step 1 wherein requestor info would be mendatory in PO distribution level and a mail can be sent to the requetor when the new PO is approved to double check that the new PO is related to the OLD PO. This would eliminate any manual PO creation error / misuse of ATF PO creation.
I have custom script to remove the hold from AP invoices. Please mail me to get a copy of that.
--What is an ATF invoice?
--How to control them?
--Different types of ATF invoices
In this post I would try to answer all of these,
1. What is an ATF Invoice?
ATF invoice stands for After the fact invoices which means any invoicing happens before related PO is created in other words where PO approval date is later than Invoice date.
2. ATF invoices can be controlled via a hold in Invoices. Generally companies name it as "ATF PO". Through this finance operations managers, controllers and all keep track of all these expenses. Payment through NON-PO / ATF-PO invoices are considered as bad finance management / planning and it hurts company's budget.
3. Although companies try their best to stop ATF Invoices but there are genuine instances wherein invoice lands in ATF. Reasons for that like there is some mistake happens in the original PO such as currency issue etc. and it is known only when invoice is received and in order to pay that invoice another new PO is created for paying the invoices. In that case the invoice becomes ATF because it is before the new PO is generated.
To keep track of such genuine instances following can be done,
Step 1. Create a DFF at PO header level to keep reference of the old PO number.
Step 2. Create a custom program and schedule it to remove the ATF hold automatically by checking if the new PO has DFF populated with the old PO and the old PO approval date is before the invoice date.
To make this process full-proof, a validation can be put in step 1 wherein requestor info would be mendatory in PO distribution level and a mail can be sent to the requetor when the new PO is approved to double check that the new PO is related to the OLD PO. This would eliminate any manual PO creation error / misuse of ATF PO creation.
I have custom script to remove the hold from AP invoices. Please mail me to get a copy of that.
java.lang.UnsupportedClassVersionError: oracle/apps/AvailableProg (Unsupported major.minor version 49.0)
Issue:Getting following error while opening an OAF page / executing JAVA Concurrent program
Oracle Apps version:11.5.x
Check the Java version by following command in the command prompt,
java -version
Error stack while the OA component is opened in the browser,
java.lang.UnsupportedClassVersionError: oracle/apps/AvailableProg (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Fix:
OC4J server that ships with Oracle Application server does not support the .class version and hence is the error.
Compiling your java code with lower jdk version like 1.4.2 or lower would resolve the issue.
Oracle Apps version:11.5.x
Check the Java version by following command in the command prompt,
java -version
Error stack while the OA component is opened in the browser,
java.lang.UnsupportedClassVersionError: oracle/apps/AvailableProg (Unsupported major.minor version 49.0) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:539) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:123) at java.net.URLClassLoader.defineClass(URLClassLoader.java:251) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:274) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at oracle.apps.fnd.cp.request.Run.main(Run.java:157)
Fix:
OC4J server that ships with Oracle Application server does not support the .class version and hence is the error.
Compiling your java code with lower jdk version like 1.4.2 or lower would resolve the issue.
Starting/Stopping Apache in Oracle Applications
Oracle Apps Ver: 11i
Execute the following command in Oracle Applications Server (Application Tier),
. $COMMON_TOP/admin/scripts/$TWO_TASK/adapcctl.sh status/stop/start
status- To get the status of the Apache
stop - To stop Apache
start - To start Apache
Any java class files migration, MDS migration (EO, VO XML files etc), OA personalizations migration need Apache bounce in 11i.
Execute the following command in Oracle Applications Server (Application Tier),
. $COMMON_TOP/admin/scripts/$TWO_TASK/adapcctl.sh status/stop/start
status- To get the status of the Apache
stop - To stop Apache
start - To start Apache
Any java class files migration, MDS migration (EO, VO XML files etc), OA personalizations migration need Apache bounce in 11i.
Wednesday, January 20, 2010
No approver found for Purchase Requisition||Requisition going to INCOMPLETE status
Issue:
Requisition could not be approved and goes to INCOMPLETE status after the final approver approves the requisition.
Symptom:
--Requestor and the final approver gets notification like "No approver found for Purchase Requisition"
--Requisiton goes to INCOMPLETE status.
Facts:
-- Requisition preparer is the manager of his subordinate/requestor.
-- There is a PO setup which restricts preparer from approving his/her own requisitoin.
-- REQAPPRV workflow completes with NO ERROR.
-- Following Events happened,
Preparer/Manager prepared the requisition for his subordinate/requestor and submitted for approval>PR went for requestor/suboridinate approval>Requestor approved the requisition>PR went for Manager of the requestor for approval who is the preparer/owner of the PR>Manager approved the PR>PR could not be approved and remained in INCOMPLETE status
Reason:
This is a standard functionality. There is a setup in PO which restricts the preparer from approving his/her own PO.
Here the Preparer is the manager of the requestor.
Suggested Fix:
Nothing can be done to this requisition. Ask the user to create a new Requisition and submit for approval.
3103: Attribute 'DOCUMENT_ID' does not exist for item 'PORPOCHA/RESPONSE_67359_39381'
Issue:PORPOCHA workflow goes to error at activity "START_PO_APPROVAL" (Launch PO Approval workflow).
This happens in case of PO Change requests for MODIFICATION (Not for cancellation)
Details:
Item type: PORPOCHA
Activity: "START_PO_APPROVAL" (Launch PO Approval workflow)
Item key: RESPONSE_%
WF Error message:3103: Attribute 'DOCUMENT_ID' does not exist for item 'PORPOCHA/RESPONSE_67359_39381'.
Here, the change request gets stuck in the workflow at the node as mentioned above.
The PO status goes to "REQUIRES REAPPROVAL".
Not all the PO change requests (for modification) goes to this condition. Some complete successfully without any error.
Retry does not work in this case. If retried then the workflow remains in the error at the same node but the error message shows "ORA-06512: at line ".
Workaround: Ask the buyer to manually approve the PO.
This happens in case of PO Change requests for MODIFICATION (Not for cancellation)
Details:
Item type: PORPOCHA
Activity: "START_PO_APPROVAL" (Launch PO Approval workflow)
Item key: RESPONSE_%
WF Error message:3103: Attribute 'DOCUMENT_ID' does not exist for item 'PORPOCHA/RESPONSE_67359_39381'.
Here, the change request gets stuck in the workflow at the node as mentioned above.
The PO status goes to "REQUIRES REAPPROVAL".
Not all the PO change requests (for modification) goes to this condition. Some complete successfully without any error.
Retry does not work in this case. If retried then the workflow remains in the error at the same node but the error message shows "ORA-06512: at line ".
Workaround: Ask the buyer to manually approve the PO.
Subscribe to:
Posts (Atom)