DBA Data[Home] [Help]

PACKAGE: APPS.OTA_TFL_API_BUS

Source


1 Package ota_tfl_api_bus as
2 /* $Header: ottfl01t.pkh 120.0 2005/05/29 07:41:52 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |---------------------------< insert_validate >----------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 --   This procedure controls the execution of all insert business rules
11 --   validation.
12 --
13 -- Pre Conditions:
14 --   This private procedure is called from ins procedure.
15 --
16 -- In Arguments:
17 --   A Pl/Sql record structre.
18 --
19 -- Post Success:
20 --   Processing continues.
21 --
22 -- Post Failure:
23 --   If a business rules fails the error will not be handled by this procedure
24 --   unless explicity coded.
25 --
26 -- Developer Implementation Notes:
27 --   For insert, your business rules should be coded within this procedure and
28 --   should ideally (unless really necessary) just be straight procedure or
29 --   function calls. Try and avoid using conditional branching logic.
30 --
31 -- Access Status:
32 --   Internal Development Use Only.
33 --
34 -- {End Of Comments}
35 -- ----------------------------------------------------------------------------
36 Procedure insert_validate( p_rec               in out nocopy ota_tfl_api_shd.g_rec_type
37                          , p_transaction_type  in varchar2);
38 --
39 -- ----------------------------------------------------------------------------
40 -- |---------------------------< update_validate >----------------------------|
41 -- ----------------------------------------------------------------------------
42 -- {Start Of Comments}
43 --
44 -- Description:
45 --   This procedure controls the execution of all update business rules
46 --   validation.
47 --
48 -- Pre Conditions:
49 --   This private procedure is called from upd procedure.
50 --
51 -- In Arguments:
52 --   A Pl/Sql record structre.
53 --
54 -- Post Success:
55 --   Processing continues.
56 --
57 -- Post Failure:
58 --   If a business rules fails the error will not be handled by this procedure
59 --   unless explicity coded.
60 --
61 -- Developer Implementation Notes:
62 --   For update, your business rules should be coded within this procedure and
63 --   should ideally (unless really necessary) just be straight procedure or
64 --   function calls. Try and avoid using conditional branching logic.
65 --
66 -- Access Status:
67 --   Internal Development Use Only.
68 --
69 -- {End Of Comments}
70 -- ----------------------------------------------------------------------------
71 Procedure update_validate( p_rec               in out nocopy  ota_tfl_api_shd.g_rec_type
72                          , p_money_amount      in out nocopy number
73                          , p_unitary_amount    in out nocopy number
74                          , p_date_raised       in out nocopy date
75                          , p_sequence_number   in out nocopy number
76                          , p_transaction_type  in varchar2);
77 --
78 -- ----------------------------------------------------------------------------
79 -- |---------------------------< delete_validate >----------------------------|
80 -- ----------------------------------------------------------------------------
81 -- {Start Of Comments}
82 --
83 -- Description:
84 --   This procedure controls the execution of all delete business rules
85 --   validation.
86 --
87 -- Pre Conditions:
88 --   This private procedure is called from del procedure.
89 --
90 -- In Arguments:
91 --   A Pl/Sql record structre.
92 --
93 -- Post Success:
94 --   Processing continues.
95 --
96 -- Post Failure:
97 --   If a business rules fails the error will not be handled by this procedure
98 --   unless explicity coded.
99 --
100 -- Developer Implementation Notes:
101 --   For delete, your business rules should be coded within this procedure and
102 --   should ideally (unless really necessary) just be straight procedure or
103 --   function calls. Try and avoid using conditional branching logic.
104 --
105 -- Access Status:
106 --   Internal Development Use Only.
107 --
108 -- {End Of Comments}
109 -- ----------------------------------------------------------------------------
110 Procedure delete_validate(p_rec in ota_tfl_api_shd.g_rec_type);
111 --
112 
113 -- ---------------------------------------------------------------------------
114 -- |----------------------< set_security_group_id >--------------------------|
115 -- ---------------------------------------------------------------------------
116 -- {Start Of Comments}
117 --
118 --  Description:
119 --    Sets the security_group_id in CLIENT_INFO for the appropriate business
120 --    group context.
121 --
122 --  Prerequisites:
123 --    The primary key identified by p_finance_line_id
124 --     already exists.
125 --
126 --  In Arguments:
127 --    p_finance_line_id
128 --
129 --
130 --  Post Success:
131 --    The security_group_id will be set in CLIENT_INFO.
132 --
133 --  Post Failure:
134 --    An error is raised if the value does not exist.
135 --
136 --  Access Status:
137 --    Internal Development Use Only.
138 --
139 -- {End Of Comments}
140 -- ---------------------------------------------------------------------------
141 procedure set_security_group_id
142   (p_finance_line_id				in number
143   ,p_associated_column1                   in varchar2 default null
144   );
145 --
146 
147 --
148 -- ----------------------------------------------------------------------------
149 -- |-----------------------< return_legislation_code >-------------------------|
150 -- ----------------------------------------------------------------------------
151 --
152 -- {Start Of Comments}
153 --
154 -- Description:
155 --   This function will be used by the user hooks. This will be  used
156 --   of by the user hooks of ota_finance_lines business process.
157 --
158 -- Pre Conditions:
159 --   This function will be called by the user hook packages.
160 --
161 -- In Arguments:
162 --   p_finance_line_id
163 --
164 -- Post Success:
165 --   Processing continues.
166 --
167 -- Post Failure:
168 --   Errors out
169 --
170 -- Developer Implementation Notes:
171 --
172 -- Access Status:
173 --   Internal Development Use Only.
174 --
175 -- {End Of Comments}
176 --------------------------------------------------------------------------------
177 --
178 
179 Function return_legislation_code
180          (  p_finance_line_id     in number
181           ) return varchar2;
182 
183 
184 
185 end ota_tfl_api_bus;