DBA Data[Home] [Help]

PACKAGE: APPS.BEN_LPL_BUS

Source


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