1 Package pay_etp_bus AUTHID CURRENT_USER as
2 /* $Header: pyetprhi.pkh 120.3 2007/02/01 10:39:46 mshingan 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 -- It is only valid to call this procedure when the primary key
13 -- is within a buisiness group context.
14 --
15 -- Prerequisites:
16 -- The primary key identified by p_element_type_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_element_type_id
21 --
22 --
23 -- Post Success:
24 -- The security_group_id will be set in CLIENT_INFO.
25 --
26 -- Post Failure:
27 -- An error is raised if the value does not exist.
28 -- An error is also raised when the primary key data is outside
29 -- of a buisiness group context.
30 --
31 -- Access Status:
32 -- Internal Development Use Only.
33 --
34 -- {End Of Comments}
35 -- ---------------------------------------------------------------------------
36 procedure set_security_group_id
37 (p_element_type_id in number
38 ,p_associated_column1 in varchar2 default null
39 );
40 --
41 --
42 -- ---------------------------------------------------------------------------
43 -- |---------------------< return_legislation_code >-------------------------|
44 -- ---------------------------------------------------------------------------
45 -- {Start Of Comments}
46 --
47 -- Description:
48 -- Return the legislation code for a specific primary key value
49 --
50 -- Prerequisites:
51 -- The primary key identified by p_element_type_id
52 -- already exists.
53 --
54 -- In Arguments:
55 -- p_element_type_id
56 --
57 --
58 -- Post Success:
59 -- The business group's legislation code will be returned.
60 --
61 -- Post Failure:
62 -- An error is raised if the value does not exist.
63 --
64 -- Access Status:
65 -- Internal Development Use Only.
66 --
67 -- {End Of Comments}
68 -- ---------------------------------------------------------------------------
69 FUNCTION return_legislation_code
70 (p_element_type_id in number
71 ) RETURN varchar2;
72 --
73 --
74 -- ----------------------------------------------------------------------------
75 -- |---------------------------< insert_validate >----------------------------|
76 -- ----------------------------------------------------------------------------
77 -- {Start Of Comments}
78 --
79 -- Description:
80 -- This procedure controls the execution of all insert business rules
81 -- validation.
82 --
83 -- Prerequisites:
84 -- This private procedure is called from ins procedure.
85 --
86 -- In Parameters:
87 -- A Pl/Sql record structre.
88 --
89 -- Post Success:
90 -- Processing continues.
91 --
92 -- Post Failure:
93 -- If a business rules fails the error will not be handled by this procedure
94 -- unless explicity coded.
95 --
96 -- Developer Implementation Notes:
97 -- For insert, your business rules should be executed from this procedure and
98 -- should ideally (unless really necessary) just be straight procedure or
99 -- function calls. Try and avoid using conditional branching logic.
100 --
101 -- Access Status:
102 -- Internal Row Handler Use Only.
103 --
104 -- {End Of Comments}
105 -- ----------------------------------------------------------------------------
106 Procedure insert_validate
107 (p_rec in pay_etp_shd.g_rec_type
108 ,p_effective_date in date
109 ,p_datetrack_mode in varchar2
110 ,p_validation_start_date in date
111 ,p_validation_end_date in date
112 ,p_processing_priority_warning out nocopy boolean
113 );
114 --
115 -- ----------------------------------------------------------------------------
116 -- |---------------------------< update_validate >----------------------------|
117 -- ----------------------------------------------------------------------------
118 -- {Start Of Comments}
119 --
120 -- Description:
121 -- This procedure controls the execution of all update business rules
122 -- validation.
123 --
124 -- Prerequisites:
125 -- This private procedure is called from upd procedure.
126 --
127 -- In Parameters:
128 -- A Pl/Sql record structre.
129 --
130 -- Post Success:
131 -- Processing continues.
132 --
133 -- Post Failure:
134 -- If a business rules fails the error will not be handled by this procedure
135 -- unless explicity coded.
136 --
137 -- Developer Implementation Notes:
138 -- For update, your business rules should be executed from this procedure and
139 -- should ideally (unless really necessary) just be straight procedure or
140 -- function calls. Try and avoid using conditional branching logic.
141 --
142 -- Access Status:
143 -- Internal Row Handler Use Only.
144 --
145 -- {End Of Comments}
146 -- ----------------------------------------------------------------------------
147 Procedure update_validate
148 (p_rec in pay_etp_shd.g_rec_type
149 ,p_effective_date in date
150 ,p_datetrack_mode in varchar2
151 ,p_validation_start_date in date
152 ,p_validation_end_date in date
153 ,p_processing_priority_warning out nocopy boolean
154 );
155 --
156 -- ----------------------------------------------------------------------------
157 -- |---------------------------< delete_validate >----------------------------|
158 -- ----------------------------------------------------------------------------
159 -- {Start Of Comments}
160 --
161 -- Description:
162 -- This procedure controls the execution of all delete business rules
163 -- validation.
164 --
165 -- Prerequisites:
166 -- This private procedure is called from del procedure.
167 --
168 -- In Parameters:
169 -- A Pl/Sql record structure.
170 --
171 -- Post Success:
172 -- Processing continues.
173 --
174 -- Post Failure:
175 -- If a business rules fails the error will not be handled by this procedure
176 -- unless explicity coded.
177 --
178 -- Developer Implementation Notes:
179 -- For delete, your business rules should be executed from this procedure and
180 -- should ideally (unless really necessary) just be straight procedure or
181 -- function calls. Try and avoid using conditional branching logic.
182 --
183 -- Access Status:
184 -- Internal Row Handler Use Only.
185 --
186 -- {End Of Comments}
187 -- ----------------------------------------------------------------------------
188 Procedure delete_validate
189 (p_rec in pay_etp_shd.g_rec_type
190 ,p_effective_date in date
191 ,p_datetrack_mode in varchar2
192 ,p_validation_start_date in date
193 ,p_validation_end_date in date
194 );
195 --
196 end pay_etp_bus;
[Home] [Help]