1 Package pay_rfm_bus as
2 /* $Header: pyrfmrhi.pkh 120.0 2005/05/29 08:20 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 -- 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_report_format_mapping_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_report_format_mapping_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_report_format_mapping_id in number
38 ,p_associated_column1 in varchar2 default null
39 );
40 --
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
75 (p_rec in pay_rfm_shd.g_rec_type
76 ,p_effective_date in date
77 ,p_datetrack_mode in varchar2
78 ,p_validation_start_date in date
79 ,p_validation_end_date in date
80 );
81 --
82 -- ----------------------------------------------------------------------------
83 -- |---------------------------< update_validate >----------------------------|
84 -- ----------------------------------------------------------------------------
85 -- {Start Of Comments}
86 --
87 -- Description:
88 -- This procedure controls the execution of all update business rules
89 -- validation.
90 --
91 -- Prerequisites:
92 -- This private procedure is called from upd procedure.
93 --
94 -- In Parameters:
95 -- A Pl/Sql record structre.
96 --
97 -- Post Success:
98 -- Processing continues.
99 --
100 -- Post Failure:
101 -- If a business rules fails the error will not be handled by this procedure
102 -- unless explicity coded.
103 --
104 -- Developer Implementation Notes:
105 -- For update, your business rules should be executed from this procedure and
106 -- should ideally (unless really necessary) just be straight procedure or
107 -- function calls. Try and avoid using conditional branching logic.
108 --
109 -- Access Status:
110 -- Internal Row Handler Use Only.
111 --
112 -- {End Of Comments}
113 -- ----------------------------------------------------------------------------
114 Procedure update_validate
115 (p_rec in pay_rfm_shd.g_rec_type
116 ,p_effective_date in date
117 ,p_datetrack_mode in varchar2
118 ,p_validation_start_date in date
119 ,p_validation_end_date in date
120 );
121 --
122 -- ----------------------------------------------------------------------------
123 -- |---------------------------< delete_validate >----------------------------|
124 -- ----------------------------------------------------------------------------
125 -- {Start Of Comments}
126 --
127 -- Description:
128 -- This procedure controls the execution of all delete business rules
129 -- validation.
130 --
131 -- Prerequisites:
132 -- This private procedure is called from del procedure.
133 --
134 -- In Parameters:
135 -- A Pl/Sql record structure.
136 --
137 -- Post Success:
138 -- Processing continues.
139 --
140 -- Post Failure:
141 -- If a business rules fails the error will not be handled by this procedure
142 -- unless explicity coded.
143 --
144 -- Developer Implementation Notes:
145 -- For delete, your business rules should be executed from this procedure and
146 -- should ideally (unless really necessary) just be straight procedure or
147 -- function calls. Try and avoid using conditional branching logic.
148 --
149 -- Access Status:
150 -- Internal Row Handler Use Only.
151 --
152 -- {End Of Comments}
153 -- ----------------------------------------------------------------------------
154 Procedure delete_validate
155 (p_rec in pay_rfm_shd.g_rec_type
156 ,p_effective_date in date
157 ,p_datetrack_mode in varchar2
158 ,p_validation_start_date in date
159 ,p_validation_end_date in date
160 );
161 --
162 -- ----------------------------------------------------------------------------
163 -- |-------------------< chk_report_format_mapping_id >-----------------------|
164 -- ----------------------------------------------------------------------------
165 -- {Start Of Comments}
166 --
167 -- Description:
168 -- This procedure is used to check the validity of the
169 -- report_format_mapping_id that will be used for the report format mapping.
170 -- Though this id is generated internally, this check is necessary
171 -- because the primary key constraint on this table does not consist of this
172 -- column and hence any discrepancy in report_format_mapping_id will not be
173 -- caught by the primary key constraint.
174 --
175 -- Pre Conditions:
176 -- Must be called only while Insert and after the report_format_mapping_id
177 -- is derived.
178 --
179 --
180 -- In Arguments:
181 -- report_format_mapping_id
182 --
183 --
184 -- Post Success:
185 -- Processing continues.
186 --
187 --
188 -- Post Failure:
189 -- Failure might occur if the report_format_mapping_id is null or
190 -- there already exists a different report format mapping with the
191 -- same id. Errors are trapped and reported.
192 --
193 -- Access Status:
194 -- Internal Row Handler Use Only.
195 --
196 -- {End Of Comments}
197 -- ----------------------------------------------------------------------------
198 Procedure chk_report_format_mapping_id
199 ( p_report_format_mapping_id in number );
200 --
201 end pay_rfm_bus;
[Home] [Help]