DBA Data[Home] [Help]

PACKAGE: APPS.PQH_TCT_BUS

Source


1 Package pqh_tct_bus as
2 /* $Header: pqtctrhi.pkh 120.2.12000000.2 2007/04/19 12:48:28 brsinha noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |-------------------------< Additional Checks >----------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- ----------------------------------------------------------------------------
10 -- |-------------------------<chk_identifiers_count>--------------------------|
11 -- ----------------------------------------------------------------------------
12 --
13 -- Description:
14 --   This procedure validates if the count of list and member identifiers
15 --   satisfy the set business rules.
16 --
17 PROCEDURE chk_identifiers_count(p_transaction_category_id  in   number,
18                                 p_routing_type             in   varchar2,
19                                 p_min_member_identifiers   in   number,
20                                 p_max_list_identifiers     in   number,
21                                 p_max_member_identifiers   in   number);
22 
23 --
24 -- Description:
25 --   This procedure checks if active transactions exists for the transaction
26 --   category
27 --
28 FUNCTION chk_active_transaction_exists(p_short_name in VARCHAR2,
29                                        p_transaction_category_id IN NUMBER)
30 RETURN VARCHAR2;
31 --
32 --
33 FUNCTION chk_active_transaction_exists(p_transaction_category_id IN NUMBER)
34 RETURN VARCHAR2;
35 --
36 PROCEDURE chk_valid_routing_exists(p_transaction_category_id IN NUMBER,
37                                    p_routing_type            IN VARCHAR2);
38 --
39 Procedure get_routing_category_name(p_routing_category_id     in number,
40                                 p_routing_category_name  out nocopy varchar2);
41   --
42 -- ----------------------------------------------------------------------------
43 -- |---------------------------< insert_validate >----------------------------|
44 -- ----------------------------------------------------------------------------
45 -- {Start Of Comments}
46 --
47 -- Description:
48 --   This procedure controls the execution of all insert business rules
49 --   validation.
50 --
51 -- Prerequisites:
52 --   This private procedure is called from ins procedure.
53 --
54 -- In Parameters:
55 --   A Pl/Sql record structre.
56 --
57 -- Post Success:
58 --   Processing continues.
59 --
60 -- Post Failure:
61 --   If a business rules fails the error will not be handled by this procedure
62 --   unless explicity coded.
63 --
64 -- Developer Implementation Notes:
65 --   For insert, your business rules should be executed from this procedure and
66 --   should ideally (unless really necessary) just be straight procedure or
67 --   function calls. Try and avoid using conditional branching logic.
68 --
69 -- Access Status:
70 --   Internal Row Handler Use Only.
71 --
72 -- {End Of Comments}
73 -- ----------------------------------------------------------------------------
74 Procedure insert_validate(p_rec in pqh_tct_shd.g_rec_type
75                          ,p_effective_date in date);
76 --
77 -- ----------------------------------------------------------------------------
78 -- |---------------------------< update_validate >----------------------------|
79 -- ----------------------------------------------------------------------------
80 -- {Start Of Comments}
81 --
82 -- Description:
83 --   This procedure controls the execution of all update business rules
84 --   validation.
85 --
86 -- Prerequisites:
87 --   This private procedure is called from upd procedure.
88 --
89 -- In Parameters:
90 --   A Pl/Sql record structre.
91 --
92 -- Post Success:
93 --   Processing continues.
94 --
95 -- Post Failure:
96 --   If a business rules fails the error will not be handled by this procedure
97 --   unless explicity coded.
98 --
99 -- Developer Implementation Notes:
100 --   For update, your business rules should be executed from this procedure and
101 --   should ideally (unless really necessary) just be straight procedure or
102 --   function calls. Try and avoid using conditional branching logic.
103 --
104 -- Access Status:
105 --   Internal Row Handler Use Only.
106 --
107 -- {End Of Comments}
108 -- ----------------------------------------------------------------------------
109 Procedure update_validate(p_rec in pqh_tct_shd.g_rec_type
110                          ,p_effective_date in date);
111 --
112 -- ----------------------------------------------------------------------------
113 -- |---------------------------< delete_validate >----------------------------|
114 -- ----------------------------------------------------------------------------
115 -- {Start Of Comments}
116 --
117 -- Description:
118 --   This procedure controls the execution of all delete business rules
119 --   validation.
120 --
121 -- Prerequisites:
122 --   This private procedure is called from del procedure.
123 --
124 -- In Parameters:
125 --   A Pl/Sql record structre.
126 --
127 -- Post Success:
128 --   Processing continues.
129 --
130 -- Post Failure:
131 --   If a business rules fails the error will not be handled by this procedure
132 --   unless explicity coded.
133 --
134 -- Developer Implementation Notes:
135 --   For delete, your business rules should be executed from this procedure and
136 --   should ideally (unless really necessary) just be straight procedure or
137 --   function calls. Try and avoid using conditional branching logic.
138 --
139 -- Access Status:
140 --   Internal Row Handler Use Only.
141 --
142 -- {End Of Comments}
143 -- ----------------------------------------------------------------------------
144 Procedure delete_validate(p_rec in pqh_tct_shd.g_rec_type
145                          ,p_effective_date in date);
146 --
147 end pqh_tct_bus;