1 Package pqh_bre_bus as
2 /* $Header: pqbrerhi.pkh 120.0 2005/05/29 01:34:33 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |----------------------< set_security_group_id >--------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
11 -- group context.
12 --
13 -- Prerequisites:
14 --
15 -- In Arguments:
16 -- p_pool_Id
17 -- p_transaction_type
18 -- p_txn_detail_id
19 --
20 -- Post Success:
21 -- The security_group_id will be set in CLIENT_INFO.
22 --
23 -- Post Failure:
24 -- An error is raised if the value does not exist.
25 --
26 -- Access Status:
27 -- Internal Development Use Only.
28 --
29 -- {End Of Comments}
30 -- ---------------------------------------------------------------------------
31 procedure set_security_group_id
32 (p_pool_id in number
33 ,p_transaction_type in varchar2
34 ,p_txn_detail_id in number
35 ,p_associated_column1 in varchar2 default null
36 );
37 --
38 --
39 -- ---------------------------------------------------------------------------
40 -- |---------------------< return_legislation_code >-------------------------|
41 -- ---------------------------------------------------------------------------
42 -- {Start Of Comments}
43 --
44 -- Description:
45 -- Return the legislation code for a specific primary key value
46 --
47 -- Prerequisites:
48 -- The primary key identified by p_reallocation_id
49 -- already exists.
50 --
51 -- In Arguments:
52 -- p_reallocation_id
53 --
54 --
55 -- Post Success:
56 -- The business group's legislation code will be returned.
57 --
58 -- Post Failure:
59 -- An error is raised if the value does not exist.
60 --
61 -- Access Status:
62 -- Internal Development Use Only.
63 --
64 -- {End Of Comments}
65 -- ---------------------------------------------------------------------------
66 FUNCTION return_legislation_code
67 (p_reallocation_id in number
68 ) RETURN varchar2;
69 --
70 --
71 -- ----------------------------------------------------------------------------
72 -- |---------------------------< insert_validate >----------------------------|
73 -- ----------------------------------------------------------------------------
74 -- {Start of comments}
75 --
76 -- Description:
77 -- This procedure controls the execution of all insert business rules
78 -- validation.
79 --
80 -- Prerequisites:
81 -- This private procedure is called from ins procedure.
82 --
83 -- In Parameters:
84 -- A Pl/Sql record structure.
85 --
86 -- Post Success:
87 -- Processing continues.
88 --
89 -- Post Failure:
90 -- If a business rules fails the error will not be handled by this procedure
91 -- unless explicity coded.
92 --
93 -- Developer Implementation Notes:
94 -- For insert, your business rules should be executed from this procedure
95 -- and should ideally (unless really necessary) just be straight procedure
96 -- or function calls. Try and avoid using conditional branching logic.
97 --
98 -- Access Status:
99 -- Internal Row Handler Use Only.
100 --
101 -- {End of comments}
102 -- ----------------------------------------------------------------------------
103 Procedure insert_validate
104 (p_effective_date in date
105 ,p_rec in pqh_bre_shd.g_rec_type
106 );
107 --
108 -- ----------------------------------------------------------------------------
109 -- |---------------------------< update_validate >----------------------------|
110 -- ----------------------------------------------------------------------------
111 -- {Start Of Comments}
112 --
113 -- Description:
114 -- This procedure controls the execution of all update business rules
115 -- validation.
116 --
117 -- Prerequisites:
118 -- This private procedure is called from upd procedure.
119 --
120 -- In Parameters:
121 -- A Pl/Sql record structure.
122 --
123 -- Post Success:
124 -- Processing continues.
125 --
126 -- Post Failure:
127 -- If a business rules fails the error will not be handled by this procedure
128 -- unless explicity coded.
129 --
130 -- Access Status:
131 -- Internal Row Handler Use Only.
132 --
133 -- {End Of Comments}
134 -- ----------------------------------------------------------------------------
135 Procedure update_validate
136 (p_effective_date in date
137 ,p_rec in pqh_bre_shd.g_rec_type
138 );
139 --
140 -- ----------------------------------------------------------------------------
141 -- |---------------------------< delete_validate >----------------------------|
142 -- ----------------------------------------------------------------------------
143 -- {Start Of Comments}
144 --
145 -- Description:
146 -- This procedure controls the execution of all delete business rules
147 -- validation.
148 --
149 -- Prerequisites:
150 -- This private procedure is called from del procedure.
151 --
152 -- In Parameters:
153 -- A Pl/Sql record structure.
154 --
155 -- Post Success:
156 -- Processing continues.
157 --
158 -- Post Failure:
159 -- If a business rules fails the error will not be handled by this procedure
160 -- unless explicity coded.
161 --
162 -- Developer Implementation Notes:
163 -- For delete, your business rules should be executed from this procedure
164 -- and should ideally (unless really necessary) just be straight procedure
165 -- or function calls. Try and avoid using conditional branching logic.
166 --
167 -- Access Status:
168 -- Internal Row Handler Use Only.
169 --
170 -- {End Of Comments}
171 -- ----------------------------------------------------------------------------
172 Procedure delete_validate
173 (p_rec in pqh_bre_shd.g_rec_type
174 );
175 --
176 end pqh_bre_bus;