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.AD_PATCH dependencies on AD_PATCH_RUN_BUGS

Line 27: 2/15/02 : app_short_name is moved from AD_BUGS to AD_PATCH_RUN_BUGS

23: With the snapshot project, and changes to the patch history data
24: model, the bug_status column is moved to ad_snapshot_bugfixes and hence
25: the query has to join on ad_snapshots,ad_snapshot_bugfixes and ad_bugs
26: tables.
27: 2/15/02 : app_short_name is moved from AD_BUGS to AD_PATCH_RUN_BUGS
28: due to AOL's requirement, since AOL doesn't always know
29: app_short_name to pass.
30: **************************************************************************/
31: function is_patch_applied (p_release_name in varchar2,

Line 444: cascade update AD_SNAPSHOT_BUGFIXES based on the values in AD_PATCH_RUN_BUGS.

440:
441:
442:
443: /*************************************************************************
444: cascade update AD_SNAPSHOT_BUGFIXES based on the values in AD_PATCH_RUN_BUGS.
445: - Don't update AD_SNAPSHOT_BUGFIXES at all if already set to the value
446: being updated.
447: - When updating to successful, just mark row in AD_SNAPSHOT_BUGFIXES
448: as successful.

Line 450: as not successful if there are no rows in AD_PATCH_RUN_BUGS marked as

446: being updated.
447: - When updating to successful, just mark row in AD_SNAPSHOT_BUGFIXES
448: as successful.
449: - When updating to unsuccessful, only mark row in AD_SNAPSHOT_BUGFIXES
450: as not successful if there are no rows in AD_PATCH_RUN_BUGS marked as
451: successful for the bug, product, and aru_release.
452: This routine updates AD_SNAPSHOT_BUGFIXES for given a patch_run_id and
453: a flag.
454: *************************************************************************/

Line 463: from AD_PATCH_RUN_BUGS

459: l_snapshot_id AD_SNAPSHOTS.snapshot_id%type;
460:
461: cursor BUG_ID_CUR is
462: select bug_id
463: from AD_PATCH_RUN_BUGS
464: where patch_run_id = p_patch_run_id;
465:
466: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is
467: select success_flag

Line 468: from AD_PATCH_RUN_BUGS

464: where patch_run_id = p_patch_run_id;
465:
466: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is
467: select success_flag
468: from AD_PATCH_RUN_BUGS
469: where patch_run_id <> p_patch_run_id
470: and bug_id = p_bug_id;
471:
472: no_update boolean := FALSE;

Line 495: and bugfix_id in (select bug_id from AD_PATCH_RUN_BUGS

491: begin
492: update AD_SNAPSHOT_BUGFIXES
493: set success_flag = p_flag
494: where snapshot_id = l_snapshot_id
495: and bugfix_id in (select bug_id from AD_PATCH_RUN_BUGS
496: where patch_run_id = p_patch_run_id);
497: exception when others then
498: g_errm := sqlerrm;
499: raise_application_error(-20001, g_errm ||

Line 537: cascade update AD_SNAPSHOT_BUGFIXES based on the values in AD_PATCH_RUN_BUGS.

533: end if;
534: end mark_patch_bug_in_snpbgfix;
535:
536: /*************************************************************************
537: cascade update AD_SNAPSHOT_BUGFIXES based on the values in AD_PATCH_RUN_BUGS.
538: - Don't update AD_SNAPSHOT_BUGFIXES at all if already set to the value
539: being updated.
540: - When updating to successful, just mark row in AD_SNAPSHOT_BUGFIXES
541: as successful.

Line 543: as not successful if there are no rows in AD_PATCH_RUN_BUGS marked as

539: being updated.
540: - When updating to successful, just mark row in AD_SNAPSHOT_BUGFIXES
541: as successful.
542: - When updating to unsuccessful, only mark row in AD_SNAPSHOT_BUGFIXES
543: as not successful if there are no rows in AD_PATCH_RUN_BUGS marked as
544: successful for the bug, product, and aru_release.
545: This routine updates AD_SNAPSHOT_BUGFIXES, given a patch_run, bug id.
546: *************************************************************************/
547: procedure mark_bug_in_snpbgfix(p_patch_run_id in number,

Line 557: from AD_PATCH_RUN_BUGS

553: l_snapshot_id AD_SNAPSHOTS.snapshot_id%type;
554:
555: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is
556: select success_flag
557: from AD_PATCH_RUN_BUGS
558: where patch_run_id <> p_patch_run_id
559: and bug_id = p_bug_id;
560:
561: no_update boolean := FALSE;

Line 623: cascading to ad_patch_run_bugs and ad_bugs. This procedure will use

619: end mark_bug_in_snpbgfix;
620:
621: /*****************************************************************************
622: Mark patch runs as successful or unsuccessful, in a given appl_top_id,
623: cascading to ad_patch_run_bugs and ad_bugs. This procedure will use
624: patch_run_id, which would be selected via another layer of sql report that
625: the user would run to list all patch_run_ids for a given patch_name,
626: appl_top_id and a date.
627: *****************************************************************************/

Line 652: update AD_PATCH_RUN_BUGS

648: 'for patch_run_id = ' || p_patch_run_id);
649: end;
650:
651: begin
652: update AD_PATCH_RUN_BUGS
653: set success_flag = p_flag, failure_comments = p_reason_text
654: where patch_run_id = p_patch_run_id;
655: exception when others then
656: g_errm := sqlerrm;

Line 660: 'in AD_PATCH_RUN_BUGS '||

656: g_errm := sqlerrm;
657: raise_application_error(-20001, g_errm ||
658: 'Error occurred in mark_patch_succ() '||
659: 'while trying to update success_flag '||
660: 'in AD_PATCH_RUN_BUGS '||
661: 'for patch_run_id = ' || p_patch_run_id);
662: end;
663:
664: mark_patch_bug_in_snpbgfix(p_appl_top_id,p_patch_run_id,p_flag);

Line 671: Go thru all the bug_id's for the given patch_run_id in ad_patch_run_bugs

667:
668:
669: /*************************************************************************
670: are_all_bugs_for_patch_succ(p_patch_run_id);
671: Go thru all the bug_id's for the given patch_run_id in ad_patch_run_bugs
672: to get all the bugs for a given patch and check if all the bugs have
673: success_flag set to 'Y' or 'N' and return true or false accordingly.
674: *************************************************************************/
675: function are_all_bugs_for_patch_succ(p_patch_run_id in

Line 684: from AD_PATCH_RUN_BUGS

680: begin
681:
682: begin
683: select success_flag into l_flag
684: from AD_PATCH_RUN_BUGS
685: where patch_run_id = p_patch_run_id
686: and success_flag = 'N';
687: exception
688: when no_data_found then

Line 703: - update AD_PATCH_RUN_BUGS for the specified patch run and bug

699: /*************************************************************************
700: Given a patch_run_id and a bug number, mark the bug as successful or
701: unsuccessful and cascade to ad_patch_runs and ad_bugs in the following
702: manner:
703: - update AD_PATCH_RUN_BUGS for the specified patch run and bug
704: - Also update AD_PATCH_RUNS in the following cases:
705: - if updating bug to successful and all other bugs for this patch run
706: are successful and patch run marked as unsuccessful, update patch run
707: to successful.

Line 711: AD_PATCH_RUN_BUGS.

707: to successful.
708: - if updating bug to unsuccessful and patch run marked
709: as successful, update patch run to unsuccessful.
710: - cascade update AD_BUGS as described above based on values in
711: AD_PATCH_RUN_BUGS.
712: *************************************************************************/
713:
714: procedure mark_bug_succ(p_patch_run_id in NUMBER ,
715: p_appl_top_id in number,

Line 750: update AD_PATCH_RUN_BUGS

746: update ad_patch_runs for the specified patch run and bug.
747: */
748:
749: begin
750: update AD_PATCH_RUN_BUGS
751: set success_flag = p_flag, failure_comments = p_reason_text
752: where patch_run_id = p_patch_run_id and
753: bug_id = l_bug_id;
754: exception when others then

Line 819: -- above based on values in AD_PATCH_RUN_BUGS.

815: end if;
816:
817: -- Case IV:
818: -- cascade update AD_SNAPSHOT_BUGFIXES just like in mark_patch_succ
819: -- above based on values in AD_PATCH_RUN_BUGS.
820:
821: mark_bug_in_snpbgfix(p_patch_run_id,p_appl_top_id,l_bug_id,p_flag);
822:
823: end mark_bug_succ;

Line 834: 2/15/02 : app_short_name is moved from AD_BUGS to AD_PATCH_RUN_BUGS

830: - bug_number (eg., '1234567')
831: - application_status, the patch application status (e.g.,IMPLICITLY_APPLIED)
832: - appl_top_id, to know which appl_top, user is requesting patch status for.
833:
834: 2/15/02 : app_short_name is moved from AD_BUGS to AD_PATCH_RUN_BUGS
835: due to AOL's requirement, since AOL doesn't always know
836: app_short_name to pass.
837: *******************************************************************************/
838: procedure set_patch_status(p_release_name in varchar2,