DBA Data[Home] [Help]

PACKAGE: APPS.PER_WBI_BUS

Source


1 Package per_wbi_bus as
2 /* $Header: pewbirhi.pkh 120.0 2005/05/31 23:04:14 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 --
13 --  Prerequisites:
14 --    The primary key identified by p_workbench_item_code
15 --     already exists.
16 --
17 --  In Arguments:
18 --    p_workbench_item_code
19 --
20 --
21 --  Post Success:
22 --    The security_group_id will be set in CLIENT_INFO.
23 --
24 --  Post Failure:
25 --    An error is raised if the value does not exist.
26 --
27 --  Access Status:
28 --    Internal Development Use Only.
29 --
30 -- {End Of Comments}
31 -- ---------------------------------------------------------------------------
32 
33 procedure set_security_group_id
34   (p_workbench_item_code                  in varchar2
35   ,p_associated_column1                   in varchar2 default null
36   );
37 
38 --
39 --
40 -- ---------------------------------------------------------------------------
41 -- |---------------------< return_legislation_code >-------------------------|
42 -- ---------------------------------------------------------------------------
43 -- {Start Of Comments}
44 --
45 --  Description:
46 --    Return the legislation code for a specific primary key value
47 --
48 --  Prerequisites:
49 --    The primary key identified by p_workbench_item_code
50 --     already exists.
51 --
52 --  In Arguments:
53 --    p_workbench_item_code
54 --
55 --
56 --  Post Success:
57 --    The business group's legislation code will be returned.
58 --
59 --  Post Failure:
60 --    An error is raised if the value does not exist.
61 --
62 --  Access Status:
63 --    Internal Development Use Only.
64 --
65 -- {End Of Comments}
66 -- ---------------------------------------------------------------------------
67 
68 FUNCTION return_legislation_code
69   (p_workbench_item_code                  in     varchar2
70   ) RETURN varchar2;
71 
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 structure.
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
98 --   and should ideally (unless really necessary) just be straight procedure
99 --   or 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_effective_date               in date
108   ,p_rec                          in per_wbi_shd.g_rec_type
109   );
110 --
111 -- ----------------------------------------------------------------------------
112 -- |---------------------------< update_validate >----------------------------|
113 -- ----------------------------------------------------------------------------
114 -- {Start Of Comments}
115 --
116 -- Description:
117 --   This procedure controls the execution of all update business rules
118 --   validation.
119 --
120 -- Prerequisites:
121 --   This private procedure is called from upd procedure.
122 --
123 -- In Parameters:
124 --   A Pl/Sql record structure.
125 --
126 -- Post Success:
127 --   Processing continues.
128 --
129 -- Post Failure:
130 --   If a business rules fails the error will not be handled by this procedure
131 --   unless explicity coded.
132 --
133 -- Access Status:
134 --   Internal Row Handler Use Only.
135 --
136 -- {End Of Comments}
137 -- ----------------------------------------------------------------------------
138 Procedure update_validate
139   (p_effective_date               in date
140   ,p_rec                          in per_wbi_shd.g_rec_type
141   );
142 --
143 -- ----------------------------------------------------------------------------
144 -- |---------------------------< delete_validate >----------------------------|
145 -- ----------------------------------------------------------------------------
146 -- {Start Of Comments}
147 --
148 -- Description:
149 --   This procedure controls the execution of all delete business rules
150 --   validation.
151 --
152 -- Prerequisites:
153 --   This private procedure is called from del procedure.
154 --
155 -- In Parameters:
156 --   A Pl/Sql record structure.
157 --
158 -- Post Success:
159 --   Processing continues.
160 --
161 -- Post Failure:
162 --   If a business rules fails the error will not be handled by this procedure
163 --   unless explicity coded.
164 --
165 -- Developer Implementation Notes:
166 --   For delete, your business rules should be executed from this procedure
167 --   and should ideally (unless really necessary) just be straight procedure
168 --   or function calls. Try and avoid using conditional branching logic.
169 --
170 -- Access Status:
171 --   Internal Row Handler Use Only.
172 --
173 -- {End Of Comments}
174 -- ----------------------------------------------------------------------------
175 Procedure delete_validate
176   (p_rec              in per_wbi_shd.g_rec_type
177   );
178 --
179 end per_wbi_bus;