1 Package hr_lot_bus AUTHID CURRENT_USER as
2 /* $Header: hrlotrhi.pkh 120.0 2005/05/31 01:22:20 appldev noship $ */
3 --
4 -- Added proc for Bug 957239
5 -- ----------------------------------------------------------------------------
6 -- |---------------------------< set_translation_globals >--------------------|
7 --------------------------------------------------------------------------------
8 PROCEDURE set_translation_globals(p_business_group_id IN NUMBER,
9 p_legislation_code IN VARCHAR2);
10
11 -- ----------------------------------------------------------------------------
12 -- |---------------------------< chk_location_code >--------------------------|
13 -- ----------------------------------------------------------------------------
14 --
15 -- Description
16 -- This procedure is used to check that the location code is unique within
17 -- its language and business_group (if set). If the business_group_id is
18 -- null, the code must be unique within the language.
19 --
20 -- Pre Conditions
21 -- None.
22 --
23 -- In Parameters
24 --
25 -- p_language_id
26 -- p_location_code
27 -- p_language
28 -- p_business_group_id
29 -- p_called_from_form - affects which error message is used on error.
30 --
31 -- Post Success
32 -- Processing continues
33 --
34 -- Post Failure
35 -- Errors handled by the procedure
36 --
37 -- Access Status
38 -- Internal Row handler use only.
39 --
40 procedure chk_location_code
41 (
42 p_location_id in number,
43 p_location_code in varchar2,
44 p_language in varchar2,
45 p_business_group_id in number,
46 p_called_from_form in boolean
47 );
48 --
49 -- ----------------------------------------------------------------------------
50 -- |---------------------------< chk_location_code overload >----------------|
51 -- ----------------------------------------------------------------------------
52 --
53 -- Description
54 -- This procedure is used to check that the location code is unique within
55 -- its language and business_group (if set). If the business_group_id is
56 -- null, the code must be unique within the language.
57 --
58 -- This version is overloaded as this versions is used instead of
59 -- hr_location_api.validate_translation call in perwsloc.fmb
60 -- Pre Conditions
61 -- None.
62 --
63 -- In Parameters
64 --
65 -- language_id
66 -- location_code
67 -- language
68 -- description ( dummy param ,used to allow the form to compile )
69 --
70 --
71 -- Post Success
72 -- Processing continues
73 --
74 -- Post Failure
75 -- Errors handled by the client
76 --
77 -- Access Status
78 -- Used for call from Client code
79 --
80 procedure chk_location_code(location_id IN NUMBER,
81 language IN VARCHAR2,
82 location_code IN VARCHAR2,
83 description IN VARCHAR2);
84 -- ----------------------------------------------------------------------------
85 -- |---------------------------< insert_validate >----------------------------|
86 -- ----------------------------------------------------------------------------
87 -- {Start Of Comments}
88 --
89 -- Description:
90 -- This procedure controls the execution of all insert business rules
91 -- validation.
92 --
93 -- Prerequisites:
94 -- This private procedure is called from ins procedure.
95 --
96 -- In Parameters:
97 -- A Pl/Sql record structre.
98 --
99 -- Post Success:
100 -- Processing continues.
101 --
102 -- Post Failure:
103 -- If a business rules fails the error will not be handled by this procedure
104 -- unless explicity coded.
105 --
106 -- Developer Implementation Notes:
107 -- For insert, your business rules should be executed from this procedure and
108 -- should ideally (unless really necessary) just be straight procedure or
109 -- function calls. Try and avoid using conditional branching logic.
110 --
111 -- Access Status:
112 -- Internal Row Handler Use Only.
113 --
114 -- {End Of Comments}
115 -- ----------------------------------------------------------------------------
116 Procedure insert_validate(p_rec in hr_lot_shd.g_rec_type,
117 p_business_group_id in number);
118 --
119 -- ----------------------------------------------------------------------------
120 -- |---------------------------< update_validate >----------------------------|
121 -- ----------------------------------------------------------------------------
122 -- {Start Of Comments}
123 --
124 -- Description:
125 -- This procedure controls the execution of all update business rules
126 -- validation.
127 --
128 -- Prerequisites:
129 -- This private procedure is called from upd procedure.
130 --
131 -- In Parameters:
132 -- A Pl/Sql record structre.
133 --
134 -- Post Success:
135 -- Processing continues.
136 --
137 -- Post Failure:
138 -- If a business rules fails the error will not be handled by this procedure
139 -- unless explicity coded.
140 --
141 -- Developer Implementation Notes:
142 -- For update, your business rules should be executed from this procedure and
143 -- should ideally (unless really necessary) just be straight procedure or
144 -- function calls. Try and avoid using conditional branching logic.
145 --
146 -- Access Status:
147 -- Internal Row Handler Use Only.
148 --
149 -- {End Of Comments}
150 -- ----------------------------------------------------------------------------
151 Procedure update_validate( p_rec in hr_lot_shd.g_rec_type,
152 p_business_group_id in number);
153 --
154 -- ----------------------------------------------------------------------------
155 -- |---------------------------< delete_validate >----------------------------|
156 -- ----------------------------------------------------------------------------
157 -- {Start Of Comments}
158 --
159 -- Description:
160 -- This procedure controls the execution of all delete business rules
161 -- validation.
162 --
163 -- Prerequisites:
164 -- This private procedure is called from del procedure.
165 --
166 -- In Parameters:
167 -- A Pl/Sql record structre.
168 --
169 -- Post Success:
170 -- Processing continues.
171 --
172 -- Post Failure:
173 -- If a business rules fails the error will not be handled by this procedure
174 -- unless explicity coded.
175 --
176 -- Developer Implementation Notes:
177 -- For delete, your business rules should be executed from this procedure and
178 -- should ideally (unless really necessary) just be straight procedure or
179 -- function calls. Try and avoid using conditional branching logic.
180 --
181 -- Access Status:
182 -- Internal Row Handler Use Only.
183 --
184 -- {End Of Comments}
185 -- ----------------------------------------------------------------------------
186 Procedure delete_validate(p_rec in hr_lot_shd.g_rec_type);
187 --
188 end hr_lot_bus;
[Home] [Help]