select * from icx_parameters
Tuesday, 24 October 2017
Find the EBS application url from the database
select * from icx_parameters
Find the application top server path from the database
Select Distinct Variable_Name "TOP_NAME"
,Value "PATH"
From Fnd_Env_Context Fec ,
Fnd_Concurrent_Processes Fcp,
fnd_concurrent_requests fcr
Where 1=1
And Fec.Concurrent_Process_Id=Fcp.Concurrent_Process_Id
And Fec.Concurrent_Process_Id=Fcr.Controlling_Manager
And Fec.Variable_Name ='&TOP_NAME'; -- AU_TOP FND_TOP CUSTOM_TOP etc...
Sunday, 22 October 2017
Enable the debug profiles for concurrent program or API
For Concurrent Program:
FND: Debug Log Enabled YES
FND: Debug Log Filename NULL
FND: Debug Log Level STATEMENT -- Unexpected, Error, Exception, Event, Procedure, Statement
FND: Debug Log Module %
SELECT log.module , log.message_text message
FROM fnd_log_messages log,
fnd_log_transaction_context con
WHERE con.transaction_id = < request_id >
AND con.transaction_type = 'REQUEST'
AND con.transaction_context_id = log.transaction_context_id
ORDER BY log.log_sequence;
For API:
1) Execute below before API call:
fnd_global.apps_initialize(fnd_user_id, fnd_resp_id, fnd_appl_id);
fnd_profile.put('AFLOG_ENABLED', 'Y');
fnd_profile.put('AFLOG_MODULE', '%');
fnd_profile.put('AFLOG_LEVEL','1'); -- Level 1 is Statement Level
fnd_log_repository.init;
2) Find the current max log sequence value
SELECT MAX(LOG_SEQUENCE)
FROM FND_LOG_MESSAGES;
3) Call API
4) Execute below after API call:
fnd_global.apps_initialize(fnd_user_id, fnd_resp_id, fnd_appl_id);
fnd_profile.put('AFLOG_ENABLED', 'N');
fnd_profile.put('AFLOG_MODULE', '%');
fnd_profile.put('AFLOG_LEVEL','1'); -- Level 1 is Statement Level
fnd_log_repository.init;
FND: Debug Log Enabled YES
FND: Debug Log Filename NULL
FND: Debug Log Level STATEMENT -- Unexpected, Error, Exception, Event, Procedure, Statement
FND: Debug Log Module %
SELECT log.module , log.message_text message
FROM fnd_log_messages log,
fnd_log_transaction_context con
WHERE con.transaction_id = < request_id >
AND con.transaction_type = 'REQUEST'
AND con.transaction_context_id = log.transaction_context_id
ORDER BY log.log_sequence;
For API:
1) Execute below before API call:
fnd_global.apps_initialize(fnd_user_id, fnd_resp_id, fnd_appl_id);
fnd_profile.put('AFLOG_ENABLED', 'Y');
fnd_profile.put('AFLOG_MODULE', '%');
fnd_profile.put('AFLOG_LEVEL','1'); -- Level 1 is Statement Level
fnd_log_repository.init;
2) Find the current max log sequence value
SELECT MAX(LOG_SEQUENCE)
FROM FND_LOG_MESSAGES;
3) Call API
4) Execute below after API call:
fnd_global.apps_initialize(fnd_user_id, fnd_resp_id, fnd_appl_id);
fnd_profile.put('AFLOG_ENABLED', 'N');
fnd_profile.put('AFLOG_MODULE', '%');
fnd_profile.put('AFLOG_LEVEL','1'); -- Level 1 is Statement Level
fnd_log_repository.init;
5) Run the below query
SELECT module, message_text
FROM fnd_log_messages
WHERE log_sequence > &max_log_from_step2
ORDER BY log_sequence;
Query to find the current running sql query of the concurrent program
select hash_value,sql_text
from v$sqltext
where hash_value in (select vs.sql_hash_value
from v$session vs
where vs.module like '%CONC_PRGO_SHORT_NAME%')
order by hash_value,piece;
Queries to find the DB locked object
select * from v$lock;
select C.OWNER,C.OBJECT_NAME,C.OBJECT_TYPE,B.sid,B.SERIAL#,B.STATUS,B.OSUSER,B.MACHINE
from V$LOCKED_OBJECT a
, V$SESSION B
, DBA_OBJECTS C
where 1=1
and b.sid = a.session_id
and a.OBJECT_ID = C.OBJECT_ID
;
select acc.*
from DBA_DDL_LOCKS LOCKS
, V$ACCESS ACC
where 1=1
and LOCKS.session_id = ACC.sid
;
select * from V$ACCESS;
select distinct B.sid,B.SERIAL#--c.object_id--C.OWNER,C.OBJECT_NAME,C.OBJECT_TYPE,B.sid,B.SERIAL#,B.STATUS,B.OSUSER,B.MACHINE
from V$LOCKED_OBJECT a
, V$SESSION B
, DBA_OBJECTS C
where 1=1
and b.sid = a.session_id
and a.OBJECT_ID = C.OBJECT_ID
--and c.object_id in (3384631,3384632)
and c.object_name = 'CONC_PROG_SHORT_NAME';
select acc.*
from DBA_DDL_LOCKS LOCKS
, V$ACCESS ACC
where 1=1
and LOCKS.session_id = ACC.sid;
select * from V$ACCESS;
SELECT SID,SERIAL#
FROM V$SESSION
WHERE SID IN (SELECT SESSION_ID
FROM DBA_DML_LOCKS
WHERE NAME = 'CONC_PROG_SHORT_NAME');
ALTER SYSTEM KILL SESSION 'SID,SERIALl#';
ALTER SYSTEM KILL SESSION '6247,5179';
Sunday, 30 April 2017
Setting the JDEV_USER_HOME Environment Variable for OAF
- Right click on My Computer > Properties > Advanced System Settings
- Select the Advanced tab and click on Environment Variables button.
- Click on New button to create a New User Variable.
- Variable Name: JDEV_USER_HOME
Variable Value: <jdev_install_dir>\jdevhome\jdev
where <jdev_install_dir> is the drive where you installed the JDeveloper OA Extension zip file. For example: D:\OAFR12\jdevhome\jdev - Select OK in each of the dialogs you opened to save the new user environment variable
Monday, 21 March 2016
Form Personalizations : Restrict to modify Unit Selling Price on Order Line
Form Personalization Steps to restrict Unit_Selling_Price modification on Order Line.
Step 1:
Testcase:
When we go to order lines tab 'Unit Selling Price' field is editable
when we click on 'Unit Selling Price' field, it will be grayed out.
We can follow same steps to restrict any other field(Ordered_Quantity, etc..) modifications
Subscribe to:
Posts (Atom)


