eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.WIP_DIAG_REPETITIVE dependencies on JTF_DIAGNOSTIC_COREAPI

Line 22: JTF_DIAGNOSTIC_COREAPI.insert_style_sheet;

18: we_dyn_where_clause VARCHAR2(1000):= null;
19: BEGIN
20: JTF_DIAGNOSTIC_ADAPTUTIL.setUpVars;
21: JTF_DIAGNOSTIC_ADAPTUTIL.addStringToReport('@html');
22: JTF_DIAGNOSTIC_COREAPI.insert_style_sheet;
23: row_limit := 1000;
24: -- accept input
25: l_org_id := JTF_DIAGNOSTIC_ADAPTUTIL.getInputValue('OrganizationId',inputs);
26:

Line 82: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,

78: ' AND WPB.ORGANIZATION_ID = MMT.ORGANIZATION_ID '||
79: ' AND WPB.ACCT_PERIOD_ID = mmt.ACCT_PERIOD_ID) '||
80: 'ORDER BY mmt.organization_id, we.wip_entity_name, mmt.transaction_id';
81:
82: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
83: 'Transactions that erred due to missing record in WIP_PERIOD_BALANCES for Repetitive Schedule. (CST_NO_BALANCE_ROW)',true,null,'Y',row_limit);
84:
85: IF (dummy_num = row_limit) THEN
86: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit || ' rows to prevent an excessively large output file.
');

Line 86: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit || ' rows to prevent an excessively large output file.
');

82: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
83: 'Transactions that erred due to missing record in WIP_PERIOD_BALANCES for Repetitive Schedule. (CST_NO_BALANCE_ROW)',true,null,'Y',row_limit);
84:
85: IF (dummy_num = row_limit) THEN
86: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit || ' rows to prevent an excessively large output file.
');
87: END IF;
88:
89: IF (dummy_num > 0) THEN
90: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. These are erred transactions due to missing record in WIP_PERIOD_BALANCES.';

Line 91: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);

87: END IF;
88:
89: IF (dummy_num > 0) THEN
90: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. These are erred transactions due to missing record in WIP_PERIOD_BALANCES.';
91: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
92: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
93: END IF;
94:
95: statusStr := 'SUCCESS';

Line 92: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');

88:
89: IF (dummy_num > 0) THEN
90: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. These are erred transactions due to missing record in WIP_PERIOD_BALANCES.';
91: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
92: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
93: END IF;
94:
95: statusStr := 'SUCCESS';
96: isFatal := 'FALSE';

Line 144: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,

140: ' WHERE mmta.transaction_id = mmt.transaction_id ' ||
141: ' AND mmta.organization_id = mmt.organization_id) '||
142: 'ORDER BY mmt.organization_id, we.wip_entity_name, mmt.transaction_id';
143:
144: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
145: 'Missing Allocations for Repetitive Schedule Transactions resulted from Manual Transaction or Component Pick Release process.',true,null,'Y',row_limit);
146:
147: IF (dummy_num = row_limit) THEN
148: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

Line 148: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

144: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
145: 'Missing Allocations for Repetitive Schedule Transactions resulted from Manual Transaction or Component Pick Release process.',true,null,'Y',row_limit);
146:
147: IF (dummy_num = row_limit) THEN
148: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');
149: END IF;
150:
151: IF (dummy_num > 0) THEN
152: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. ' ||

Line 154: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);

150:
151: IF (dummy_num > 0) THEN
152: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. ' ||
153: 'These are transactions resulted from Manual Transaction or Component Pick Release process, in error due to missing repetitive schedule allocations.';
154: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
155: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
156: END IF;
157:
158: statusStr := 'SUCCESS';

Line 155: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');

151: IF (dummy_num > 0) THEN
152: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. ' ||
153: 'These are transactions resulted from Manual Transaction or Component Pick Release process, in error due to missing repetitive schedule allocations.';
154: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
155: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
156: END IF;
157:
158: statusStr := 'SUCCESS';
159: isFatal := 'FALSE';

Line 207: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,

203: ' AND mmta.organization_id = mmt.organization_id) '||
204: 'ORDER BY mmt.organization_id, we.wip_entity_name, mmt.transaction_id';
205:
206:
207: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
208: 'Missing Allocations for Repetitive Schedule Transactions resulted from Move Transactions.',true,null,'Y',row_limit);
209:
210: IF (dummy_num = row_limit) THEN
211: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

Line 211: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

207: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
208: 'Missing Allocations for Repetitive Schedule Transactions resulted from Move Transactions.',true,null,'Y',row_limit);
209:
210: IF (dummy_num = row_limit) THEN
211: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');
212: END IF;
213:
214: IF (dummy_num > 0) THEN
215: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. ' ||

Line 217: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);

213:
214: IF (dummy_num > 0) THEN
215: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. ' ||
216: 'These are transactions resulted from Move Transactions, in error due to missing repetitive schedule allocations.';
217: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
218: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
219: END IF;
220:
221: statusStr := 'SUCCESS';

Line 218: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');

214: IF (dummy_num > 0) THEN
215: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. ' ||
216: 'These are transactions resulted from Move Transactions, in error due to missing repetitive schedule allocations.';
217: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
218: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
219: END IF;
220:
221: statusStr := 'SUCCESS';
222: isFatal := 'FALSE';

Line 270: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,

266: ' WHERE mmta.transaction_id = mmt.transaction_id ' ||
267: ' AND mmta.organization_id = mmt.organization_id) '||
268: 'ORDER BY mmt.organization_id, we.wip_entity_name, mmt.transaction_id';
269:
270: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
271: 'Missing Allocations for Repetitive Schedule Transactions resulted from Completion / Return / Scrap / Return From Scrap Transactions.',true,null,'Y',row_limit);
272:
273: IF (dummy_num = row_limit) THEN
274: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

Line 274: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

270: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
271: 'Missing Allocations for Repetitive Schedule Transactions resulted from Completion / Return / Scrap / Return From Scrap Transactions.',true,null,'Y',row_limit);
272:
273: IF (dummy_num = row_limit) THEN
274: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');
275: END IF;
276:
277: IF (dummy_num > 0) THEN
278: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||

Line 280: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);

276:
277: IF (dummy_num > 0) THEN
278: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||
279: 'These are transactions resulted from Completion / Return / Scrap / Return from Scrap Transactions, in error due to missing repetitive schedule allocations.';
280: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
281: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
282: END IF;
283:
284: statusStr := 'SUCCESS';

Line 281: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');

277: IF (dummy_num > 0) THEN
278: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||
279: 'These are transactions resulted from Completion / Return / Scrap / Return from Scrap Transactions, in error due to missing repetitive schedule allocations.';
280: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
281: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
282: END IF;
283:
284: statusStr := 'SUCCESS';
285: isFatal := 'FALSE';

Line 336: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,'Incorrect WIP Material Allocations for Repetitive Schedule Transactions resulted from Move Transactions.',true,null,'Y',row_limit);

332: ' AND wmta.organization_id = mmt.organization_id ' ||
333: ' AND wmta.repetitive_schedule_id = mmta.repetitive_schedule_id) '||
334: 'ORDER BY mmt.organization_id, we.wip_entity_name, mmt.transaction_id';
335:
336: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,'Incorrect WIP Material Allocations for Repetitive Schedule Transactions resulted from Move Transactions.',true,null,'Y',row_limit);
337:
338: IF (dummy_num = row_limit) THEN
339: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');
340: END IF;

Line 339: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

335:
336: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,'Incorrect WIP Material Allocations for Repetitive Schedule Transactions resulted from Move Transactions.',true,null,'Y',row_limit);
337:
338: IF (dummy_num = row_limit) THEN
339: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');
340: END IF;
341:
342: IF (dummy_num > 0) THEN
343: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||

Line 345: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);

341:
342: IF (dummy_num > 0) THEN
343: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||
344: 'These are transactions resulted from Move Transactions, in error due to incorrect repetitive schedule allocations.';
345: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
346: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
347: END IF;
348:
349: statusStr := 'SUCCESS';

Line 346: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');

342: IF (dummy_num > 0) THEN
343: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||
344: 'These are transactions resulted from Move Transactions, in error due to incorrect repetitive schedule allocations.';
345: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
346: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
347: END IF;
348:
349: statusStr := 'SUCCESS';
350: isFatal := 'FALSE';

Line 408: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,

404: ' AND mmt1.organization_id = mmt1.organization_id ' ||
405: ' AND mmta1.repetitive_schedule_id = mmta.repetitive_schedule_id) '||
406: 'ORDER BY mmt.organization_id, we.wip_entity_name, mmt.transaction_id';
407:
408: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
409: 'Incorrect WIP Allocations for Repetitive Schedule Transactions resulted from Completion / Return / Scrap / Return From Scrap Transactions.',true,null,'Y',row_limit);
410:
411: IF (dummy_num = row_limit) THEN
412: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

Line 412: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');

408: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,
409: 'Incorrect WIP Allocations for Repetitive Schedule Transactions resulted from Completion / Return / Scrap / Return From Scrap Transactions.',true,null,'Y',row_limit);
410:
411: IF (dummy_num = row_limit) THEN
412: JTF_DIAGNOSTIC_COREAPI.Line_Out('
Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file.
');
413: END IF;
414:
415: IF (dummy_num > 0) THEN
416: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||

Line 418: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);

414:
415: IF (dummy_num > 0) THEN
416: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||
417: 'These are transactions resulted from Completion / Return / Scrap / Return from Scrap Transactions, in error due to incorrect repetitive schedule allocations.';
418: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
419: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
420: END IF;
421:
422: statusStr := 'SUCCESS';

Line 419: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');

415: IF (dummy_num > 0) THEN
416: reportStr := 'The rows returned above signify data-inconsistency in material transactions related to repetitive schedules. '||
417: 'These are transactions resulted from Completion / Return / Scrap / Return from Scrap Transactions, in error due to incorrect repetitive schedule allocations.';
418: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);
419: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.

');
420: END IF;
421:
422: statusStr := 'SUCCESS';
423: isFatal := 'FALSE';

APPS.WIP_DIAG_REPETITIVE dependencies on JTF_DIAGNOSTIC_COREAPI

Line 22: JTF_DIAGNOSTIC_COREAPI.insert_style_sheet;

Line 82: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,

Line 86: JTF_DIAGNOSTIC_COREAPI.Line_Out(' Output limited to the first '|| row_limit || ' rows to prevent an excessively large output file. ');

Line 91: JTF_DIAGNOSTIC_COREAPI.ErrorPrint(reportStr);

Line 92: JTF_DIAGNOSTIC_COREAPI.ActionErrorLink('Please refer to Metalink note ', 402202.1, 'to get the root-cause patch and steps to correct the data.');

Line 144: dummy_num:= JTF_DIAGNOSTIC_COREAPI.display_sql(sqltxt,

Line 148: JTF_DIAGNOSTIC_COREAPI.Line_Out(' Output limited to the first '|| row_limit ||' rows to prevent an excessively large output file. ');