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_BUGS

Line 25: the query has to join on ad_snapshots,ad_snapshot_bugfixes and ad_bugs

21: resulting in simpler joins. This function queries on AD_SNAPSHOT_BUGFIXES
22: bug_status column to report the status of a bug.
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.

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 50: from AD_BUGS b, AD_TRACKABLE_ENTITIES adte

46: return varchar2
47: is
48: cursor FIND_BUG_ID_CURSOR is
49: select b.bug_id
50: from AD_BUGS b, AD_TRACKABLE_ENTITIES adte
51: where b.bug_number = p_bug_number
52: and upper(b.trackable_entity_abbr) =
53: DECODE(UPPER(adte.abbreviation),'SO', 'SQLSO',
54: 'FA', 'OFA',

Line 64: l_bugid ad_bugs.bug_id%type;

60: or b.generic_patch = 'y'
61: );
62:
63: l_bugst ad_snapshot_bugfixes.bug_status%type;
64: l_bugid ad_bugs.bug_id%type;
65: l_snapshot_id ad_snapshots.snapshot_id%type;
66:
67: l_row_found boolean := TRUE;
68: begin

Line 163: l_bug_id ad_bugs.bug_id%type;

159: p_language in varchar2)
160: return varchar2
161: is
162: l_snapshot_id ad_snapshots.snapshot_id%type;
163: l_bug_id ad_bugs.bug_id%type;
164: l_bugst ad_snapshot_bugfixes.bug_status%type;
165: BEGIN
166:
167: if (p_appl_top_id = -1)

Line 199: from AD_BUGS b

195: end if;
196:
197: begin
198: select b.bug_id into l_bug_id
199: from AD_BUGS b
200: where b.bug_number = p_bug_number
201: and b.baseline_name = p_baseline_name
202: and b.aru_release_name = p_release_name
203: and b.language = p_language;

Line 455: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is

451: select bug_id
452: from AD_PATCH_RUN_BUGS
453: where patch_run_id = p_patch_run_id;
454:
455: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is
456: select success_flag
457: from AD_PATCH_RUN_BUGS
458: where patch_run_id <> p_patch_run_id
459: and bug_id = p_bug_id;

Line 540: l_bug_id ad_bugs.bug_id%TYPE;

536: p_appl_top_id in number,
537: p_bug_id in number,
538: p_flag in varchar2)
539: is
540: l_bug_id ad_bugs.bug_id%TYPE;
541: l_snapshot_id AD_SNAPSHOTS.snapshot_id%type;
542:
543: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is
544: select success_flag

Line 543: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is

539: is
540: l_bug_id ad_bugs.bug_id%TYPE;
541: l_snapshot_id AD_SNAPSHOTS.snapshot_id%type;
542:
543: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) is
544: select success_flag
545: from AD_PATCH_RUN_BUGS
546: where patch_run_id <> p_patch_run_id
547: and bug_id = p_bug_id;

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

606: end mark_bug_in_snpbgfix;
607:
608: /*****************************************************************************
609: Mark patch runs as successful or unsuccessful, in a given appl_top_id,
610: cascading to ad_patch_run_bugs and ad_bugs. This procedure will use
611: patch_run_id, which would be selected via another layer of sql report that
612: the user would run to list all patch_run_ids for a given patch_name,
613: appl_top_id and a date.
614: *****************************************************************************/

Line 688: unsuccessful and cascade to ad_patch_runs and ad_bugs in the following

684: end are_all_bugs_for_patch_succ;
685:
686: /*************************************************************************
687: Given a patch_run_id and a bug number, mark the bug as successful or
688: unsuccessful and cascade to ad_patch_runs and ad_bugs in the following
689: manner:
690: - update AD_PATCH_RUN_BUGS for the specified patch run and bug
691: - Also update AD_PATCH_RUNS in the following cases:
692: - if updating bug to successful and all other bugs for this patch run

Line 697: - cascade update AD_BUGS as described above based on values in

693: are successful and patch run marked as unsuccessful, update patch run
694: to successful.
695: - if updating bug to unsuccessful and patch run marked
696: as successful, update patch run to unsuccessful.
697: - cascade update AD_BUGS as described above based on values in
698: AD_PATCH_RUN_BUGS.
699: *************************************************************************/
700:
701: procedure mark_bug_succ(p_patch_run_id in NUMBER ,

Line 708: l_bug_id ad_bugs.bug_id%TYPE;

704: p_bug_number in varchar2,
705: p_flag in varchar2,
706: p_reason_text in varchar2)
707: is
708: l_bug_id ad_bugs.bug_id%TYPE;
709: l_patch_succ ad_snapshot_bugfixes.success_flag%TYPE;
710:
711: begin
712:

Line 713: -- get bug id from ad_bugs for the passed bug number and aru_release_name.

709: l_patch_succ ad_snapshot_bugfixes.success_flag%TYPE;
710:
711: begin
712:
713: -- get bug id from ad_bugs for the passed bug number and aru_release_name.
714:
715: begin
716: select bug_id into l_bug_id
717: from AD_BUGS

Line 717: from AD_BUGS

713: -- get bug id from ad_bugs for the passed bug number and aru_release_name.
714:
715: begin
716: select bug_id into l_bug_id
717: from AD_BUGS
718: where bug_number = p_bug_number
719: and aru_release_name = p_release_name;
720: exception
721: when no_data_found then

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

817: - bug_number (eg., '1234567')
818: - application_status, the patch application status (e.g.,IMPLICITLY_APPLIED)
819: - appl_top_id, to know which appl_top, user is requesting patch status for.
820:
821: 2/15/02 : app_short_name is moved from AD_BUGS to AD_PATCH_RUN_BUGS
822: due to AOL's requirement, since AOL doesn't always know
823: app_short_name to pass.
824: *******************************************************************************/
825: procedure set_patch_status(p_release_name in varchar2,

Line 830: l_bug_id ad_bugs.bug_id%TYPE;

826: p_appl_top_id number,
827: p_bug_number in varchar2,
828: p_bug_status in varchar2)
829: is
830: l_bug_id ad_bugs.bug_id%TYPE;
831: l_snapshot_id ad_snapshots.snapshot_id%TYPE;
832: l_snapshot_bug_id ad_snapshot_bugfixes.snapshot_bug_id%TYPE;
833:
834: begin

Line 836: -- CASE I: On create, when there are no entries in AD_BUGS for the

832: l_snapshot_bug_id ad_snapshot_bugfixes.snapshot_bug_id%TYPE;
833:
834: begin
835:
836: -- CASE I: On create, when there are no entries in AD_BUGS for the
837: -- passed bug_number, aru_release_name. create a row in AD_BUGS and
838: -- AD_SNAPSHOT_BUGFIXES.
839:
840: -- First get the snapshot_id, from the given appl_top_id to work on.

Line 837: -- passed bug_number, aru_release_name. create a row in AD_BUGS and

833:
834: begin
835:
836: -- CASE I: On create, when there are no entries in AD_BUGS for the
837: -- passed bug_number, aru_release_name. create a row in AD_BUGS and
838: -- AD_SNAPSHOT_BUGFIXES.
839:
840: -- First get the snapshot_id, from the given appl_top_id to work on.
841:

Line 876: from AD_BUGS

872: end if;
873:
874: begin
875: select bug_id into l_bug_id
876: from AD_BUGS
877: where bug_number = p_bug_number
878: and aru_release_name = p_release_name;
879: exception
880: when no_data_found then

Line 884: select ad_bugs_s.nextval into l_bug_id from dual;

880: when no_data_found then
881:
882: -- Insert a new record
883:
884: select ad_bugs_s.nextval into l_bug_id from dual;
885:
886: begin
887: insert into AD_BUGS
888: (bug_id, bug_number,

Line 887: insert into AD_BUGS

883:
884: select ad_bugs_s.nextval into l_bug_id from dual;
885:
886: begin
887: insert into AD_BUGS
888: (bug_id, bug_number,
889: creation_date, aru_release_name,
890: last_update_date, last_updated_by,created_by)
891: values(l_bug_id,

Line 902: 'into AD_BUGS for bug_number = '||

898: exception
899: when dup_val_on_index then
900: raise_application_error(-20001,
901: 'Attempting to insert a duplicate record '||
902: 'into AD_BUGS for bug_number = '||
903: p_bug_number || ' and release '||
904: p_release_name);
905:
906: when others then

Line 911: 'into AD_BUGS for bug_number = '||

907: g_errm := sqlerrm;
908: raise_application_error(-20001, g_errm ||
909: 'Error occurred in set_patch_status() '||
910: 'while trying to insert new record '||
911: 'into AD_BUGS for bug_number = '||
912: p_bug_number || ' and release '||
913: p_release_name);
914: end;
915: end;

Line 971: -- If you are here means there was a record in AD_BUGS and

967: 'table for '||p_bug_number||
968: ' '||p_release_name);
969: end;
970:
971: -- If you are here means there was a record in AD_BUGS and
972: -- AD_SNAPSHOT_BUGFIXES.
973: -- So just update the existing record.
974:
975: begin