When a registered user cannot view OPM inventoty is because he doesn't OPM organization permission.
For changing it , use OPM System Administrador responsability and go Setup System | User Organization.
You have to give organization permission for each user as you see below:
Wednesday, May 2, 2012
Friday, April 20, 2012
Set mandatory parameters in request
When you submit a request and information retrieved is not you expected it or blank, usually is because you not use success parameter because there are not mandatory.
Monday, April 16, 2012
Retrieve information from a DFF(Descriptive Flexfield)
Many times is neccesary add, modify or delete a DFF, but to find it can be, sometimes, imposible.
For do it, see instructions below:
Scenario: Find a DFF.
1. Go to screen when you need to add a new DFF.
(Help | Register History)
2.Retrieve the table name.
3. Now navigating to Application Developer responsability.(Flexfield | Descriptive | Register)
Query on table name and store Title and Application Content. If the name is ended with _V it means View, so the table could be: OE_ORDER_HEADERS_ALL or OE_ORDER_HEADERS_T. For finding purpose is better use wildcards: OE_ORDER_HEADERS%
4.Navigating (Flexfield | Descriptive | Segment). Quey on Title and Application Content. Pressing Segment button we will get segment information regardless DFF.
Tip: For modifying you have to unfrezee DFF and freeze DFF when you finish
For do it, see instructions below:
Scenario: Find a DFF.
1. Go to screen when you need to add a new DFF.
(Help | Register History)
2.Retrieve the table name.
3. Now navigating to Application Developer responsability.(Flexfield | Descriptive | Register)
Query on table name and store Title and Application Content. If the name is ended with _V it means View, so the table could be: OE_ORDER_HEADERS_ALL or OE_ORDER_HEADERS_T. For finding purpose is better use wildcards: OE_ORDER_HEADERS%
4.Navigating (Flexfield | Descriptive | Segment). Quey on Title and Application Content. Pressing Segment button we will get segment information regardless DFF.
Tip: For modifying you have to unfrezee DFF and freeze DFF when you finish
Wednesday, April 4, 2012
Kill Session using pl/sql Developer
Many times users process become hung and block other sessions user. For this reason .Using PL/SQL Developer program we can kill this process using Tools->Sessions Monitor as you see below:
In the next window appear all users sessions(including username) and modules. With right click mouse you can choose kill selected session option.
Warning: Kill sessions process have to do it carefully.
In the next window appear all users sessions(including username) and modules. With right click mouse you can choose kill selected session option.
Warning: Kill sessions process have to do it carefully.
Monday, December 19, 2011
Verify that the APPS-Tier and DB processes are down
Verify that the APPS-Tier processes are down using the Unix command ps -fu :
ps -fu grep FNDThe
This command shown above is checking for any process named FND% on Unix level. As long as 1 of these processes is running, the Concurrent Managers are not down (To bring the Concurrent Managers down can take up to 10 minutes and more).
Verify that the DB processes of the failed Instance are down on Unix level via following commands :
ps -fu grep ora
ps -fu
If your failed Installation was a Multi-User Instance, you have to execute the steps 1.5 until 1.7 under the ORACLE Username used for the DB-Tier Installation. The second command under step 1.8 should be executed for the APPS- and the DB-User Environment, to ensure that no process of the failed Installation is running anymore.
source:11i: How To Clean Up The UNIX Environment After EBS 11i Install Fails [ID 110372.1]
ps -fu
This command shown above is checking for any process named FND% on Unix level. As long as 1 of these processes is running, the Concurrent Managers are not down (To bring the Concurrent Managers down can take up to 10 minutes and more).
Verify that the DB processes of the failed Instance are down on Unix level via following commands :
ps -fu
ps -fu
If your failed Installation was a Multi-User Instance, you have to execute the steps 1.5 until 1.7 under the ORACLE Username used for the DB-Tier Installation. The second command under step 1.8 should be executed for the APPS- and the DB-User Environment, to ensure that no process of the failed Installation is running anymore.
source:11i: How To Clean Up The UNIX Environment After EBS 11i Install Fails [ID 110372.1]
Thursday, December 1, 2011
Create Your Query-Only Function in Oracle Forms
Function not available to this responsibility. Change responsibilities or contact System Administrator
Subscribe to:
Posts (Atom)



