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 170: l_bug_id ad_bugs.bug_id%type;

166: p_language in varchar2)
167: return varchar2
168: is
169: l_snapshot_id ad_snapshots.snapshot_id%type;
170: l_bug_id ad_bugs.bug_id%type;
171: l_bugst ad_snapshot_bugfixes.bug_status%type;
172: BEGIN
173:
174: if (p_appl_top_id = -1)

Line 208: from AD_BUGS b

204: end if;
205:
206: begin
207: select b.bug_id into l_bug_id
208: from AD_BUGS b
209: where b.bug_number = p_bug_number
210: and b.baseline_name = p_baseline_name
211: and b.aru_release_name = p_release_name
212: and b.language = p_language;

Line 466: cursor FIND_SUCC_CUR(p_bug_id in ad_bugs.bug_id%type) 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
468: from AD_PATCH_RUN_BUGS
469: where patch_run_id <> p_patch_run_id
470: and bug_id = p_bug_id;

Line 552: l_bug_id ad_bugs.bug_id%TYPE;

548: p_appl_top_id in number,
549: p_bug_id in number,
550: p_flag in varchar2)
551: is
552: l_bug_id ad_bugs.bug_id%TYPE;
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

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

551: is
552: l_bug_id ad_bugs.bug_id%TYPE;
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;

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 701: unsuccessful and cascade to ad_patch_runs and ad_bugs in the following

697: end are_all_bugs_for_patch_succ;
698:
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

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

706: are successful and patch run marked as unsuccessful, update patch run
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 ,

Line 721: l_bug_id ad_bugs.bug_id%TYPE;

717: p_bug_number in varchar2,
718: p_flag in varchar2,
719: p_reason_text in varchar2)
720: is
721: l_bug_id ad_bugs.bug_id%TYPE;
722: l_patch_succ ad_snapshot_bugfixes.success_flag%TYPE;
723:
724: begin
725:

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

722: l_patch_succ ad_snapshot_bugfixes.success_flag%TYPE;
723:
724: begin
725:
726: -- get bug id from ad_bugs for the passed bug number and aru_release_name.
727:
728: begin
729: select bug_id into l_bug_id
730: from AD_BUGS

Line 730: from AD_BUGS

726: -- get bug id from ad_bugs for the passed bug number and aru_release_name.
727:
728: begin
729: select bug_id into l_bug_id
730: from AD_BUGS
731: where bug_number = p_bug_number
732: and aru_release_name = p_release_name;
733: exception
734: when no_data_found then

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,

Line 843: l_bug_id ad_bugs.bug_id%TYPE;

839: p_appl_top_id number,
840: p_bug_number in varchar2,
841: p_bug_status in varchar2)
842: is
843: l_bug_id ad_bugs.bug_id%TYPE;
844: l_snapshot_id ad_snapshots.snapshot_id%TYPE;
845: l_snapshot_bug_id ad_snapshot_bugfixes.snapshot_bug_id%TYPE;
846:
847: begin

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

845: l_snapshot_bug_id ad_snapshot_bugfixes.snapshot_bug_id%TYPE;
846:
847: begin
848:
849: -- CASE I: On create, when there are no entries in AD_BUGS for the
850: -- passed bug_number, aru_release_name. create a row in AD_BUGS and
851: -- AD_SNAPSHOT_BUGFIXES.
852:
853: -- First get the snapshot_id, from the given appl_top_id to work on.

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

846:
847: begin
848:
849: -- CASE I: On create, when there are no entries in AD_BUGS for the
850: -- passed bug_number, aru_release_name. create a row in AD_BUGS and
851: -- AD_SNAPSHOT_BUGFIXES.
852:
853: -- First get the snapshot_id, from the given appl_top_id to work on.
854:

Line 891: from AD_BUGS

887: end if;
888:
889: begin
890: select bug_id into l_bug_id
891: from AD_BUGS
892: where bug_number = p_bug_number
893: and aru_release_name = p_release_name;
894: exception
895: when no_data_found then

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

895: when no_data_found then
896:
897: -- Insert a new record
898:
899: select ad_bugs_s.nextval into l_bug_id from dual;
900:
901: begin
902: insert into AD_BUGS
903: (bug_id, bug_number,

Line 902: insert into AD_BUGS

898:
899: select ad_bugs_s.nextval into l_bug_id from dual;
900:
901: begin
902: insert into AD_BUGS
903: (bug_id, bug_number,
904: creation_date, aru_release_name,
905: last_update_date, last_updated_by,created_by)
906: values(l_bug_id,

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

913: exception
914: when dup_val_on_index then
915: raise_application_error(-20001,
916: 'Attempting to insert a duplicate record '||
917: 'into AD_BUGS for bug_number = '||
918: p_bug_number || ' and release '||
919: p_release_name);
920:
921: when others then

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

922: g_errm := sqlerrm;
923: raise_application_error(-20001, g_errm ||
924: 'Error occurred in set_patch_status() '||
925: 'while trying to insert new record '||
926: 'into AD_BUGS for bug_number = '||
927: p_bug_number || ' and release '||
928: p_release_name);
929: end;
930: end;

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

982: 'table for '||p_bug_number||
983: ' '||p_release_name);
984: end;
985:
986: -- If you are here means there was a record in AD_BUGS and
987: -- AD_SNAPSHOT_BUGFIXES.
988: -- So just update the existing record.
989:
990: begin