1 package hxc_tat_bus AUTHID CURRENT_USER as
2 /* $Header: hxtatrhi.pkh 120.1 2006/04/24 05:53:24 gsirigin noship $ */
3 -- -------------------------------------------------------------------------
4 -- |----------------------< set_security_group_id >------------------------|
5 -- -------------------------------------------------------------------------
6 -- {Start Of Comments}
7 --
8 -- Description:
9 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
10 -- group context.
11 --
12 -- Prerequisites:
13 -- The primary key identified by p_time_attribute_id
14 -- already exists.
15 --
16 -- In Arguments:
17 -- p_time_attribute_id
18 --
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_time_attribute_id in number
33 );
34
35 -- -------------------------------------------------------------------------
36 -- |---------------------< return_legislation_code >-----------------------|
37 -- -------------------------------------------------------------------------
38 -- {Start Of Comments}
39 --
40 -- Description:
41 -- Return the legislation code for a specific primary key value
42 --
43 -- Prerequisites:
44 -- The primary key identified by p_time_attribute_id
45 -- already exists.
46 --
47 -- In Arguments:
48 -- p_time_attribute_id
49 --
50 --
51 -- Post Success:
52 -- The business group's legislation code will be returned.
53 --
54 -- Post Failure:
55 -- An error is raised if the value does not exist.
56 --
57 -- Access Status:
58 -- Internal Development Use Only.
59 --
60 -- {End Of Comments}
61 -- -------------------------------------------------------------------------
62 function return_legislation_code
63 (p_time_attribute_id in number
64 ) return varchar2;
65
66 -- --------------------------------------------------------------------------
67 -- |---------------------------< insert_validate >--------------------------|
68 -- --------------------------------------------------------------------------
69 -- {Start of comments}
70 --
71 -- Description:
72 -- This procedure controls the execution of all insert business rules
73 -- validation.
74 --
75 -- Prerequisites:
76 -- This private procedure is called from ins procedure.
77 --
78 -- In Parameters:
79 -- A Pl/Sql record structure.
80 --
81 -- Post Success:
82 -- Processing continues.
83 --
84 -- Post Failure:
85 -- If a business rules fails the error will not be handled by this procedure
86 -- unless explicity coded.
87 --
88 -- Developer Implementation Notes:
89 -- For insert, your business rules should be executed from this procedure and
90 -- should ideally (unless really necessary) just be straight procedure or
91 -- function calls. Try and avoid using conditional branching logic.
92 --
93 -- Access Status:
94 -- Internal Row Handler Use Only.
95 --
96 -- {End of comments}
97 -- --------------------------------------------------------------------------
98 procedure insert_validate
99 (p_effective_date in date
100 ,p_rec in hxc_tat_shd.g_rec_type
101 );
102
103 -- --------------------------------------------------------------------------
104 -- |---------------------------< update_validate >--------------------------|
105 -- --------------------------------------------------------------------------
106 -- {Start Of Comments}
107 --
108 -- Description:
109 -- This procedure controls the execution of all update business rules
110 -- validation.
111 --
112 -- Prerequisites:
113 -- This private procedure is called from upd procedure.
114 --
115 -- In Parameters:
116 -- A Pl/Sql record structure.
117 --
118 -- Post Success:
119 -- Processing continues.
120 --
121 -- Post Failure:
122 -- If a business rules fails the error will not be handled by this procedure
123 -- unless explicity coded.
124 --
125 -- Developer Implementation Notes:
126 -- For update, your business rules should be executed from this procedure and
127 -- should ideally (unless really necessary) just be straight procedure or
128 -- function calls. Try and avoid using conditional branching logic.
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 hxc_tat_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 and
164 -- should ideally (unless really necessary) just be straight procedure or
165 -- function calls. Try and avoid using conditional branching logic.
166 --
167 -- Access Status:
168 -- Internal Row Handler Use Only.
169 --
170 --
171 -- --------------------------------------------------------------------------
172 procedure delete_validate
173 (p_rec in hxc_tat_shd.g_rec_type
174 );
175
176 end hxc_tat_bus;
[Home] [Help]