APPS.CZ_MODEL_UTIL_PVT dependencies on CZ_EXPL_PAIR

Line 607: return "SYSTEM".cz_expl_pair_tbl

603: END get_ui_refs_under_model;
604: --------------------------------------------------------------------------------
605:
606: FUNCTION get_parallel_expls (p_encl_expl_id in number, p_desc_expl_id in number, p_max_expl_depth in number)
607: return "SYSTEM".cz_expl_pair_tbl
608: is
609: -- Added new component to CZ_EXPL_PAIR for bug 4486182, 7/12/2005
610: -- model reference depth, to support field of same name in cz_uicomponent_hgrid_v
611: --

Line 609: -- Added new component to CZ_EXPL_PAIR for bug 4486182, 7/12/2005

605:
606: FUNCTION get_parallel_expls (p_encl_expl_id in number, p_desc_expl_id in number, p_max_expl_depth in number)
607: return "SYSTEM".cz_expl_pair_tbl
608: is
609: -- Added new component to CZ_EXPL_PAIR for bug 4486182, 7/12/2005
610: -- model reference depth, to support field of same name in cz_uicomponent_hgrid_v
611: --
612: -- restructured algorithm 2004-10-12
613: -- uses the same parallel-expl query structure, but instead of joining to a table case as cz_expl_pair_tbl,

Line 613: -- uses the same parallel-expl query structure, but instead of joining to a table case as cz_expl_pair_tbl,

609: -- Added new component to CZ_EXPL_PAIR for bug 4486182, 7/12/2005
610: -- model reference depth, to support field of same name in cz_uicomponent_hgrid_v
611: --
612: -- restructured algorithm 2004-10-12
613: -- uses the same parallel-expl query structure, but instead of joining to a table case as cz_expl_pair_tbl,
614: -- this approach simply iterates over the pairs and gets the matching children for each
615: -- this allows me to use a single cz_expl_pair_tbl.
616: pairs "SYSTEM".cz_expl_pair_tbl := "SYSTEM".cz_expl_pair_tbl ();
617: paircount number;

Line 615: -- this allows me to use a single cz_expl_pair_tbl.

611: --
612: -- restructured algorithm 2004-10-12
613: -- uses the same parallel-expl query structure, but instead of joining to a table case as cz_expl_pair_tbl,
614: -- this approach simply iterates over the pairs and gets the matching children for each
615: -- this allows me to use a single cz_expl_pair_tbl.
616: pairs "SYSTEM".cz_expl_pair_tbl := "SYSTEM".cz_expl_pair_tbl ();
617: paircount number;
618: newpair "SYSTEM".cz_expl_pair;
619: cur_pair_index number;

Line 616: pairs "SYSTEM".cz_expl_pair_tbl := "SYSTEM".cz_expl_pair_tbl ();

612: -- restructured algorithm 2004-10-12
613: -- uses the same parallel-expl query structure, but instead of joining to a table case as cz_expl_pair_tbl,
614: -- this approach simply iterates over the pairs and gets the matching children for each
615: -- this allows me to use a single cz_expl_pair_tbl.
616: pairs "SYSTEM".cz_expl_pair_tbl := "SYSTEM".cz_expl_pair_tbl ();
617: paircount number;
618: newpair "SYSTEM".cz_expl_pair;
619: cur_pair_index number;
620: start_encl_depth number;

Line 618: newpair "SYSTEM".cz_expl_pair;

614: -- this approach simply iterates over the pairs and gets the matching children for each
615: -- this allows me to use a single cz_expl_pair_tbl.
616: pairs "SYSTEM".cz_expl_pair_tbl := "SYSTEM".cz_expl_pair_tbl ();
617: paircount number;
618: newpair "SYSTEM".cz_expl_pair;
619: cur_pair_index number;
620: start_encl_depth number;
621: desc_ref_depth number;
622: curdepth number;

Line 654: pairs (paircount) := "SYSTEM".cz_expl_pair (

650: pairs.extend ();
651: paircount := 1;
652:
653: -- take the requested pair, instantiate it, and put it at the top of the results
654: pairs (paircount) := "SYSTEM".cz_expl_pair (
655: ENCLOSING_EXPL_ID => p_encl_expl_id,
656: DESCENDANT_EXPL_ID => p_desc_expl_id,
657: DESC_EXPL_REFERENCE_DEPTH => desc_ref_depth
658: );

Line 697: newpair := "SYSTEM".cz_expl_pair (

693: r_xp.deleted_flag = '0' and
694: c_xp.deleted_flag = '0'
695: )
696: loop
697: newpair := "SYSTEM".cz_expl_pair (
698: ENCLOSING_EXPL_ID => nextpair.encl_expl,
699: DESCENDANT_EXPL_ID => nextpair.desc_expl,
700: DESC_EXPL_REFERENCE_DEPTH => desc_ref_depth);
701: pairs.extend ();