[1] R. J. Qureshi, L. Kovacs, B. Harangi, B. Nagy, T. Peto, A. Hajdu: Combining algorithms for automatic detection of optic disc and macula in fundus images, ELSEVIER Computer Vision and Image Understanding, 116 (2012) 138-145. IF: 2.404
[2] B. Nagy, B. Antal, A. Hajdu: Image Database Clustering To Improve Microaneurysm Detection In Color Fundus Images, The 25th International Symposium on Computer-Based Medical System (CBMS 2012), Rome, Italy, accepted.
[3] B. Harangi, B. Nagy, A. Hajdu: Improving the detection of excessive activation of ciliaris muscle by clustering thermal images, 11th Quantitative InfraRed Thermography (QIRT 2012), Naples, Italy, 2012, accepted.
[4] B. Nagy, B. Harangi, B. Antal, A. Hajdu: Ensemble-based exudate detection in color fundus images, 7th International Symposium on Image and Signal Processing and Analysis (ISPA 2011), Dubrovnik, Croatia, 2011, pp. 700-703.
[5] L. Kovacs, B. Harangi, B. Nagy, A. Hajdu, R. J. Qureshi: Gráf alapú vakfolt és sárgafolt detektálás retina felvételeken, Alakfelismerők Társaságának 8. konferenciája (KÉPAF 2011), Szeged, Magyarország, 2011. január 25-28, 13 pages, pp. 329-341.
[6] R. J. Qureshi, L. Kovacs, B. Harangi, B. Nagy, A. Hajdu: Graph Based Detection of optic disc and fovea in retinal images, 4th International Workshop on Soft Computing Applications (IEEE SOFA 2010), Arad, 15-17 July, 2010, pp. 143 – 148.
[7] B. Nagy, L. Kovacs, B. Harangi, R. J. Qureshi, A. Hajdu: Automatic detection of the fovea and optic disk in digital retinal images by combining algorithms, 8th International Conference on Applied Informatics (ICAI 2010), Eger, pp. 143-152.
[8] R. J. Qureshi, L. Kovács, B. Harangi, B. Nagy, A. Hajdu, T. Peto: Detection of the optic disc and the macula through combining algorithms, University of Debrecen, Faculty of Informatics, Preprints No. 380 (Technical Reports No. 7/2010).
Girly Coding
2017. május 8., hétfő
2015. január 22., csütörtök
Oracle - Troubleshooting Workflow
1. Create SQL query to get ITEM_KEY
Use wf_messages_vl and wf_notifications tables.
2. Use Workflow Administrator Web Applications responsibility
3. Select Administrator Workflow > Status Monitor
4. Add Type Internal Name and Item Key and Go.
4.1. Click on Activity History
Go to Notification column > Click Open > Shows error message
4.2. Click on Status Diagram
Check the process you are interested in.
5. Open the workflow in Workflow Builder > Processes (double click) > Click on the button > Check Function Name -> package and function name
6. Check the code behind
resultout := Wf_Engine.eng_completed||':F';
Determines which case of the workflow will happen. This is an error one.
Use wf_messages_vl and wf_notifications tables.
2. Use Workflow Administrator Web Applications responsibility
3. Select Administrator Workflow > Status Monitor
4. Add Type Internal Name and Item Key and Go.
Check the process you are interested in.
5. Open the workflow in Workflow Builder > Processes (double click) > Click on the button > Check Function Name -> package and function name
6. Check the code behind
resultout := Wf_Engine.eng_completed||':F';
Determines which case of the workflow will happen. This is an error one.
2015. január 8., csütörtök
Oracle - fnd_profile_option_values
| level_id | level | level_value |
| 1001 | Site | |
| 1002 | Application | application_id |
| 1003 | Responsibility | responsibility_id |
| 1004 | User | user_id |
| 1005 | Server | |
| 1006 | Organization | |
| 1007 | Server + Responsibility |
2015. január 6., kedd
Oracle - Version and location of files
.class /opt/apps/r12/<host_name>/apps/apps_st/comn/java/classes/oracle/apps/<application_code>/
.fmb, .fmx $<TOP>/forms/US
.pls $<TOP>/patch/115/sql/
.odf $<TOP>/patch/115/odf/
.pld $<AU_TOP>/resource
<TOP>:
$AP_TOP: /opt/apps/r12/<host_name>/apps/apps_st/appl/ap/12.0.0/
$AU_TOP: /opt/apps/r12/<host_name>/apps/apps_st/appl/au/12.0.0/
$FUN_TOP: /opt/apps/r12/<host_name>/apps/apps_st/appl/fun/12.0.0/
$PSA_TOP: /opt/apps/r12/<host_name>/apps/apps_st/appl/psa/12.0.0/
$ZX_TOP: /opt/apps/r12/<host_name>/apps/apps_st/appl/zx/12.0.0/
2014. december 16., kedd
Oracle - Version of Applications
1. Use System Administration responsibility
2. Select Oracle Applications Manager > Applications Usage
3. You can see the version of the desired application in the Patch set column.
2. Select Oracle Applications Manager > Applications Usage
3. You can see the version of the desired application in the Patch set column.
2014. november 19., szerda
Oracle - Trace, FND Debug Log, FND Diagnostics
I. Trace
Type 1
1. Set Initialization SQL Statement - Custom Profile Option at User level:
BEGIN
fnd_ctl.fnd_sess_ctl(
'',''
,'TRUE','TRUE','LOG'
, 'ALTER SESSION SET TRACEFILE_IDENTIFIER=''TEST'' EVENTS=''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12''' );
END;
2. Find the trace file(s)
3. Use tkprof <input_file_name>.trc <output_file_name>.prf in $ORACLE_HOME folder and enjoy the readable output :-)
Advantage: more detailed trace file.
Disadvantage: the user has to sign out before the Profile Option setting and then sign in again.
Type 2
1. Set Utilities:Diagnostics Profile Option to Yes at User Level.
2. Go to Help > Diagnostics > Trace and select Trace with Binds and Waits
3. A note appears where you will find your trace file.
Advantage: the user doesn't have to sign out, the settings have effect immediately.
Disadvantage: less detailed trace file.
II. FND Debug Log
1. Set the following Profile Options at User level:
1.1. Set FND: Debug Log Enabled to Yes
1.2. Set FND: Debug Log Level to 1 if you would like to use it in code as C_LEVEL_STATEMENT or
1.3. Set FND: Debug Log Level to Statement
1.4. Set FND: Debug Log Module to %
2. Query log_sequence -> &1st_value
select max(log_sequence)
from fnd_log_messages;
3. Do what you would like to debug.
4. Query log_sequence again -> &2nd_value
5. Query your debug log:
SELECT substr(module,1,70), MESSAGE_TEXT, timestamp, log_sequence
from fnd_log_messages
where log_sequence between &1st_value AND &2nd_value
ORDER BY log_sequence;
6. Set the Profile Options back to the original values.
III. FND Diagnostics
1. Set FND: Diagnostics Profile Option to Yes at User level.
2. Click "Diagnostics" tool menu.
3. Select "Show Log on screen" in Diagnostic field and "Statement" in Log Level field and click "Go" button.
4. Do about what you would like to have the log. The log will be displayed at the bottom of the screen.
5. Turn off logging: click "Diagnostics" tool menu, select "Show Log on screen" in Diagnostic field and "Turn off screen logging" in Log Level field and click "Go" button.
6. Set FND: Diagnostics Profile Option to No at User level.
Type 1
1. Set Initialization SQL Statement - Custom Profile Option at User level:
BEGIN
fnd_ctl.fnd_sess_ctl(
'',''
,'TRUE','TRUE','LOG'
, 'ALTER SESSION SET TRACEFILE_IDENTIFIER=''TEST'' EVENTS=''10046 TRACE NAME CONTEXT FOREVER, LEVEL 12''' );
END;
2. Find the trace file(s)
3. Use tkprof <input_file_name>.trc <output_file_name>.prf in $ORACLE_HOME folder and enjoy the readable output :-)
Advantage: more detailed trace file.
Disadvantage: the user has to sign out before the Profile Option setting and then sign in again.
Type 2
1. Set Utilities:Diagnostics Profile Option to Yes at User Level.
2. Go to Help > Diagnostics > Trace and select Trace with Binds and Waits
3. A note appears where you will find your trace file.
Advantage: the user doesn't have to sign out, the settings have effect immediately.
Disadvantage: less detailed trace file.
II. FND Debug Log
1. Set the following Profile Options at User level:
1.1. Set FND: Debug Log Enabled to Yes
1.2. Set FND: Debug Log Level to 1 if you would like to use it in code as C_LEVEL_STATEMENT or
1.3. Set FND: Debug Log Level to Statement
1.4. Set FND: Debug Log Module to %
2. Query log_sequence -> &1st_value
select max(log_sequence)
from fnd_log_messages;
3. Do what you would like to debug.
4. Query log_sequence again -> &2nd_value
5. Query your debug log:
SELECT substr(module,1,70), MESSAGE_TEXT, timestamp, log_sequence
from fnd_log_messages
where log_sequence between &1st_value AND &2nd_value
ORDER BY log_sequence;
6. Set the Profile Options back to the original values.
III. FND Diagnostics
1. Set FND: Diagnostics Profile Option to Yes at User level.
2. Click "Diagnostics" tool menu.
3. Select "Show Log on screen" in Diagnostic field and "Statement" in Log Level field and click "Go" button.
4. Do about what you would like to have the log. The log will be displayed at the bottom of the screen.
5. Turn off logging: click "Diagnostics" tool menu, select "Show Log on screen" in Diagnostic field and "Turn off screen logging" in Log Level field and click "Go" button.
6. Set FND: Diagnostics Profile Option to No at User level.
2014. október 27., hétfő
Oracle - Enable Record History in OAF
1. Set FND: Record History Enabled Profile Option to Yes at Site level
2. Set Personalize Self-Service Defn Profile Option to Yes at User level
3. Set FND: Personalization Region Link Enabled Profile Option to Yes at User level
4. Click on Personalize Page

5. Click on Edit

6. Find Record History Enabled and set to true at the desired level

See more details here.
2. Set Personalize Self-Service Defn Profile Option to Yes at User level
3. Set FND: Personalization Region Link Enabled Profile Option to Yes at User level
4. Click on Personalize Page
5. Click on Edit
6. Find Record History Enabled and set to true at the desired level
See more details here.
Feliratkozás:
Megjegyzések (Atom)










