, ,

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 – How to Find XML Publisher Version

Method One: MetaInfo.class

The version of a specific Java Class has a one to one relationship with the currently installed version of Oracle XML Publisher.

/home/applprod >strings $OA_JAVA/oracle/apps/xdo/common/MetaInfo.class|grep -i ‘XML Publisher’

Oracle XML Publisher 5.6.3

/home/applprod >

Version 5.6.3 ships with update pack 12.1.3, which is Patch 8919491

“Patch R12.ATG_PF.B.delta.3: Oracle Applications Technology 12.1.3 Product Family Release Update Pack”

Method Two: SQL Query

SELECT DECODE (bug_number
, ‘3554613’, ‘4.5.0’
, ‘3263588’, ‘XDO.H’
, ‘3822219’, ‘5.0.0’
, ‘4236958’, ‘5.0.1’
, ‘4206181’, ‘5.5.0’
, ‘4561451’, ‘5.6.0’
, ‘4905678’, ‘5.6.1’
, ‘5097966’, ‘5.6.2’
, ‘5472959’, ‘5.6.3’) PATCH, bug_number
FROM ad_bugs
WHERE bug_number IN
(‘3554613′
, ‘3263588’
, ‘3822219’
, ‘4236958’
, ‘4206181’
, ‘4561451’
, ‘4905678’
, ‘5097966’
, ‘5472959’);

Method Three: Output PDF of the report (Document Properties)

doc_properties

 

/by
, , ,

R12 – GL-Receiving India Drill Down Query

Here is the query for Link between General Ledger and Receiving India data’s.

SELECT msib.segment1 item,
msib.description,
rsh.receipt_num,
mp.organization_code,
gjl.accounted_dr,
gjl.accounted_cr,
gjh.je_source,
gjh.je_category
FROM apps.gl_je_headers gjh,
apps.gl_je_lines gjl,
apps.gl_code_combinations_kfv gcc,
apps.gl_import_references gir,
apps.rcv_transactions rt,
apps.rcv_shipment_headers rsh,
apps.rcv_shipment_lines rsl,
apps.gl_je_batches gjb,
apps.mtl_parameters mp,
apps.mtl_system_items_b msib
WHERE gjh.je_header_id = gjl.je_header_id
AND gjh.je_header_id   = gir.je_header_id
AND gir.je_header_id   = gjl.je_header_id
AND gir.je_line_num    = gjl.je_line_num
AND gjb.je_batch_id    = gir.je_batch_id
AND GJH.JE_SOURCE      = ‘Purchasing India’
AND gjh.period_name    =’Nov-14′
AND gjl.reference_2 = ‘India Localization Entry’
AND gjl.code_combination_id = gcc.code_combination_id
AND rt.organization_id      = mp.organization_id
AND rt.transaction_id       = gjl.reference_5
AND rt.shipment_header_id   = rsh.shipment_header_id
AND rsl.shipment_header_id  = rsh.shipment_header_id
AND rsl.shipment_line_id    = rt.shipment_line_id
AND msib.inventory_item_id  = rsl.item_id
AND msib.organization_id    = rt.organization_id
AND gjl.period_name        IN
(SELECT DISTINCT period_name
FROM APPS.GL_PERIODS
WHERE START_DATE BETWEEN :P_FROM_PERIOD AND :P_TO_PERIOD
);

Note: This one was not linked with India Localization SLA Tables, its a direct link between GL and Localization Info’s

/by