DBA Data[Home] [Help]

PACKAGE: APPS.AME_ITL_BUS

Source


1 Package ame_itl_bus as
2 /* $Header: amitlrhi.pkh 120.0 2005/09/02 04:01 mbocutt 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_item_class_id
15 --     already exists.
16 --
17 --  In Arguments:
18 --    p_item_class_id
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 procedure set_security_group_id
33   (p_item_class_id                        in number
34   ,p_associated_column1                   in varchar2 default null
35   );
36 --
37 --
38 -- ---------------------------------------------------------------------------
39 -- |---------------------< return_legislation_code >-------------------------|
40 -- ---------------------------------------------------------------------------
41 -- {Start Of Comments}
42 --
43 --  Description:
44 --    Return the legislation code for a specific primary key value
45 --
46 --  Prerequisites:
47 --    The primary key identified by p_item_class_id
48 --     already exists.
49 --
50 --  In Arguments:
51 --    p_item_class_id
52 --
53 --
54 --  Post Success:
55 --    The business group's legislation code will be returned.
56 --
57 --  Post Failure:
58 --    An error is raised if the value does not exist.
59 --
60 --  Access Status:
61 --    Internal Development Use Only.
62 --
63 -- {End Of Comments}
64 -- ---------------------------------------------------------------------------
65 FUNCTION return_legislation_code
66   (p_item_class_id                        in     number
67   ,p_language                             in     varchar2
68   ) RETURN varchar2;
69 --
70 --
71 -- ----------------------------------------------------------------------------
72 -- |---------------------------< insert_validate >----------------------------|
73 -- ----------------------------------------------------------------------------
74 -- {Start of comments}
75 --
76 -- Description:
77 --   This procedure controls the execution of all insert business rules
78 --   validation.
79 --
80 -- Prerequisites:
81 --   This private procedure is called from ins procedure.
82 --
83 -- In Parameters:
84 --   A Pl/Sql record structure.
85 --
86 -- Post Success:
87 --   Processing continues.
88 --
89 -- Post Failure:
90 --   If a business rules fails the error will not be handled by this procedure
91 --   unless explicity coded.
92 --
93 -- Developer Implementation Notes:
94 --   For insert, your business rules should be executed from this procedure
95 --   and should ideally (unless really necessary) just be straight procedure
96 --   or function calls. Try and avoid using conditional branching logic.
97 --
98 -- Access Status:
99 --   Internal Row Handler Use Only.
100 --
101 -- {End of comments}
102 -- ----------------------------------------------------------------------------
103 Procedure insert_validate
104   (p_rec                          in ame_itl_shd.g_rec_type
105   );
106 --
107 -- ----------------------------------------------------------------------------
108 -- |---------------------------< update_validate >----------------------------|
109 -- ----------------------------------------------------------------------------
110 -- {Start Of Comments}
111 --
112 -- Description:
113 --   This procedure controls the execution of all update business rules
114 --   validation.
115 --
116 -- Prerequisites:
117 --   This private procedure is called from upd procedure.
118 --
119 -- In Parameters:
120 --   A Pl/Sql record structure.
121 --
122 -- Post Success:
123 --   Processing continues.
124 --
125 -- Post Failure:
126 --   If a business rules fails the error will not be handled by this procedure
127 --   unless explicity coded.
128 --
129 -- Access Status:
130 --   Internal Row Handler Use Only.
131 --
132 -- {End Of Comments}
133 -- ----------------------------------------------------------------------------
134 Procedure update_validate
135   (p_rec                          in ame_itl_shd.g_rec_type
136   );
137 --
138 -- ----------------------------------------------------------------------------
139 -- |---------------------------< delete_validate >----------------------------|
140 -- ----------------------------------------------------------------------------
141 -- {Start Of Comments}
142 --
143 -- Description:
144 --   This procedure controls the execution of all delete business rules
145 --   validation.
146 --
147 -- Prerequisites:
148 --   This private procedure is called from del procedure.
149 --
150 -- In Parameters:
151 --   A Pl/Sql record structure.
152 --
153 -- Post Success:
154 --   Processing continues.
155 --
156 -- Post Failure:
157 --   If a business rules fails the error will not be handled by this procedure
158 --   unless explicity coded.
159 --
160 -- Developer Implementation Notes:
161 --   For delete, your business rules should be executed from this procedure
162 --   and should ideally (unless really necessary) just be straight procedure
163 --   or function calls. Try and avoid using conditional branching logic.
164 --
165 -- Access Status:
166 --   Internal Row Handler Use Only.
167 --
168 -- {End Of Comments}
169 -- ----------------------------------------------------------------------------
170 Procedure delete_validate
171   (p_rec              in ame_itl_shd.g_rec_type
172   );
173 --
174 end ame_itl_bus;