, ,

How to View/Access Other User Concurrent Request in Oracle Apps R12

When user OPERATIONS submit a request at System Administratorresponsibility, this user can see the log and output files of this request. But the other user (ex: SYSADMIN) cannot do that even has the same responsibility. If we use the View All Concurrent Requests (System Administrator Mode) form, we only can see the request but not the output file of this request.
So, if we want to access the request output of the same responsibility from another user’s requests, then we need to follow the below setup steps:
1. Login as SYSADMIN with Functional Developer responsibility and update the object Concurrent Requests
1.a. Search Concurrent Requests object and click the link to update it.
CR_1
1.b. Create new Instance Set
CR_2
1.c. Enter Name, Code, Description and Predicate for the new instance Set.
Predicate:
&TABLE_ALIAS.request_id in (select cr.request_id from fnd_concurrent_requests cr where cr.responsibility_id = fnd_global.resp_id and cr.responsibility_application_id = fnd_global.resp_appl_id)
.
CR_3
1.d. New Instance Set successful created.
CR_4
2. Login as SYSADMIN with User Management responsibility and using theRoles and Role Inheritance Tab
2.a. Create Role and then create a Grant for the Role, Data Security Object choose Concurrent Requests
RRI_1
RRI_2
RRI_3
2.b. Choose the Data Context Type Instance Set and choose the Instance Set created in above step (EY – Access Request Output of Same Responsibility)
RRI_4
2.c. Choose Permission Set Request Operations
RRI_5
2.d. Role and Grant created.
RRI_6
3. Assign the role to users as needed. The users with this role will be able to see the log and output files for the same as responsibility.
3.a. Query the user that you want to add this new role and click Update.
UR_1
3.b. Assign the new Role and Apply to activated
UR_2
UR_3
4. User OPERATIONS submit request Signon Audit Users with Request ID 5831028.User SYSADMIN will be able to find the Request ID 5831028 and the View Output and View Log buttons are Enable also.
OPR_CR
SYS_CR
But if otherwise, user OPERATIONS cannot find the Request that userSYSADMIN submitted, because the Role just grant to the user SYSADMIN.
Reference: Doc ID 804296.1
/by
, , , ,

R12 – Meaning for Concurrent Request Status Codes and Phase Codes

Concurrent Request Phase Codes:

SELECT LOOKUP_CODE, MEANING
  FROM FND_LOOKUP_VALUES
 WHERE LOOKUP_TYPE = ‘CP_PHASE_CODE’ AND LANGUAGE = ‘US’
       AND ENABLED_FLAG = ‘Y’;

LOOKUP_CODE
MEANING
C
Completed
I
Inactive
P
Pending
R
Running

Concurrent Request Status Codes:

SELECT LOOKUP_CODE, MEANING
  FROM FND_LOOKUP_VALUES
 WHERE LOOKUP_TYPE = ‘CP_STATUS_CODE’ AND LANGUAGE = ‘US’
       AND ENABLED_FLAG = ‘Y’;

LOOKUP_CODE
MEANING
R
Normal
I
Normal
Z
Waiting
D
Cancelled
U
Disabled
E
Error
M
No Manager
C
Normal
H
On Hold
W
Paused
B
Resuming
P
Scheduled
Q
Standby
S
Suspended
X
Terminated
T
Terminating
A
Waiting
G
Warning

Normally a concurrent request proceeds through three, possibly four, life cycle stages or phases,

Phase Code
Meaning with Description
Pending
Request is waiting to be run
Running
Request is running
Completed
Request has finished
Inactive
Request cannot be run

Within each phase, a request’s condition or status may change. Below appears a listing of each phase and the various states that a concurrent request can go through.

The status and the description of each meaning given below:

Phase
Status
Description
PENDING
Normal
Request is waiting for the next available manager.
Standby
Program to run request is incompatible with other program(s) currently running.
Scheduled
Request is scheduled to start at a future time or date.
Waiting
A child request is waiting for its Parent request to mark it ready to run. For example, a report in a report set that runs sequentially must wait for a prior report to complete.



RUNNING
Normal
Request is running normally.
Paused
Parent request pauses for all its child requests to complete. For example, a report set pauses for all reports in the set to complete.
Resuming
All requests submitted by the same parent request have completed running. The Parent request is waiting to be restarted.
Terminating
Running request is terminated, by selecting Terminate in the Status field of   the Request Details zone.



COMPLETED
Normal
Request completes normally.
Error
Request failed to complete successfully.
Warning
Request completes with warnings. For example, a report is generated successfully but fails to print.
Cancelled
Pending or Inactive request is cancelled, by selecting Cancel in the Status field of the Request Details zone.
Terminated
Running request is terminated, by selecting Terminate in the Status field of   the Request Details zone.



INACTIVE
Disabled
Program to run request is not enabled. Contact your system administrator.
On Hold
Pending request is placed on hold, by selecting Hold in the Status field of the Request Details zone.
No Manager
No manager is defined to run the request. Check with your system administrator.
/by
, , , ,

How to Enable Personalization link for OAF Pages using Profile Options

To Access OAF Personalization in Oracle Apps, we need to set the values of following profiles options to enable Personalization Page link in OAF Pages. You can enable these profile options at all levels (Function, Site, Responsibility, User)


These four profile options are mandatory for working on OAF personalization in apps. To Assign these Profile Options, we need to go to System Administrator or Functional Administrator Responsibility.

Navigation:
System Administrator -> Profile -> System
Functional Administrator -> Core Services -> Profiles

Profile Name
Profile Value
FND: Diagnostics
Yes
Personalize Self-Service Defn
Yes
FND: Personalization Region Link Enabled
Yes / Minimal
Disable Self-Service Personal
No

Meanings:

1. FND: Diagnostics
Setting the FND: Diagnostics (FND_DIAGNOSTICS) profile option to “Yes” will enable the diagnostics global button to be rendered on the screen.

2. Personalize Self-Service Defn
Set the value to Yes to allow ‘Personalize’ link to appear at the right top of the OAF page.

3. FND: Personalization Region Link Enabled
It renders the “Personalize  Region” links above each  region in a page. Each link  takes you first to the Choose Personalization Context page, then to the Page Hierarchy Personalization page with focus on the region node from which  you selected the “Personalize  Region” link.

Two Options
Set the value to Yes to display all the personalization links above each OAF page region.
Set the value to Minimal to display key regional links.

4. Disable Self-Service Personal
Set the value to No will enable all OAF personalizations on all pages at all levels (Function, Site, Responsibility, User)


/by
, , ,

Solution: Problem with Desktop Integrator in R12 OAF Screen

While Accessing Web ADI Responsibility some times we will get the below error message. To Fix this issue we need to disable one profile option value.

Error:
Desktop Integration is not a valid responsibility for the current user. Please contact your System Administrator.


Solution:
By default below Profile Option is either Null or Yes. Just set the below option, then you can access the screen.

Set Profile Option : 

ADI: Use Function Security => No

/by
, ,

How to Solve Concurrent Program Output Post Processor(OPP) Issue in R12

Output Post Processor is very common term used in the Oracle Apps terminology which is used to publish the XML content to PDF/Excel etc.


I have faced several issues with the EBS XML Reports esp. during or after Output Post processing.
Issue# 1- Concurrent Request completed with Warning and timed out
Concurrent Request completed with Warning and in the log file says the request timed out.


Fix:-
Go to System Administrator -> Profile -> System

Make the Profile Concurrent: OPP Process Timeout to 10800.

This issue comes when the OPP is timed out to publish the output. The time out will be based upon the value in the profile. For e.g. if the value set at this profile is 600 it means the program waits for 10 mins (600/60) and if OPP does not publish the output within this time then it will timed out. Having higher value i.e. 10800 which is 3 hours will solve most of the issues that may cause due to high volume of the data.



Issue# 2- Concurrent Request completed with Error with Java Heap Space.

This is very common issue when size of the XML is huge and OPP fails to publish the data it will generate this error.

One way to fix this issue is to see how many Active OPP Services is running on the server. We had this issue for one of my client and by increasing the number of OPP Services from 4 to 8 solves this issue.

System Administrator -> Concurrent ->Manager ->Administer
Click on Output Post Processor and then click Processes.

/by