DBA Data[Home] [Help]

PACKAGE: APPS.PAY_AUD_SHD

Source


1 Package pay_aud_shd as
2 /* $Header: pyaudrhi.pkh 120.0 2005/05/29 03:04:51 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                    Global Record Type Specification                      |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9   (stat_trans_audit_id            number(15)
10   ,transaction_type                varchar2(30)
11   ,transaction_subtype             varchar2(30)
12   ,transaction_date                date
13   ,transaction_effective_date      date
14   ,business_group_id               number(15)
15   ,person_id                       number(9)
16   ,assignment_id                   number(9)
17   ,source1                         varchar2(30)
18   ,source1_type                    varchar2(30)
19   ,source2                         varchar2(30)
20   ,source2_type                    varchar2(30)
21   ,source3                         varchar2(30)
22   ,source3_type                    varchar2(30)
23   ,source4                         varchar2(30)
24   ,source4_type                    varchar2(30)
25   ,source5                         varchar2(30)
26   ,source5_type                    varchar2(30)
27   ,transaction_parent_id           number(15)
28   ,audit_information_category      varchar2(30)
29   ,audit_information1              varchar2(150)
30   ,audit_information2              varchar2(150)
31   ,audit_information3              varchar2(150)
32   ,audit_information4              varchar2(150)
33   ,audit_information5              varchar2(150)
34   ,audit_information6              varchar2(150)
35   ,audit_information7              varchar2(150)
36   ,audit_information8              varchar2(150)
37   ,audit_information9              varchar2(150)
38   ,audit_information10             varchar2(150)
39   ,audit_information11             varchar2(150)
40   ,audit_information12             varchar2(150)
41   ,audit_information13             varchar2(150)
42   ,audit_information14             varchar2(150)
43   ,audit_information15             varchar2(150)
44   ,audit_information16             varchar2(150)
45   ,audit_information17             varchar2(150)
46   ,audit_information18             varchar2(150)
47   ,audit_information19             varchar2(150)
48   ,audit_information20             varchar2(150)
49   ,audit_information21             varchar2(150)
50   ,audit_information22             varchar2(150)
51   ,audit_information23             varchar2(150)
52   ,audit_information24             varchar2(150)
53   ,audit_information25             varchar2(150)
54   ,audit_information26             varchar2(150)
55   ,audit_information27             varchar2(150)
56   ,audit_information28             varchar2(150)
57   ,audit_information29             varchar2(150)
58   ,audit_information30             varchar2(150)
59   ,title                           varchar2(30)
60   ,object_version_number           number(9)
61   );
62 --
63 -- ----------------------------------------------------------------------------
64 -- |           Global Definitions - Internal Development Use Only             |
65 -- ----------------------------------------------------------------------------
66 --
67 g_old_rec  g_rec_type;                            -- Global record definition
68 --
69 -- ----------------------------------------------------------------------------
70 -- |---------------------------< constraint_error >---------------------------|
71 -- ----------------------------------------------------------------------------
72 -- {Start Of Comments}
73 --
74 -- Description:
75 --   This procedure is called when a constraint has been violated (i.e.
76 --   The exception hr_api.check_integrity_violated,
77 --   hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
78 --   hr_api.unique_integrity_violated has been raised).
79 --   The exceptions can only be raised as follows:
80 --   1) A check constraint can only be violated during an INSERT or UPDATE
81 --      dml operation.
82 --   2) A parent integrity constraint can only be violated during an
83 --      INSERT or UPDATE dml operation.
84 --   3) A child integrity constraint can only be violated during an
85 --      DELETE dml operation.
86 --   4) A unique integrity constraint can only be violated during INSERT or
87 --      UPDATE dml operation.
88 --
89 -- Prerequisites:
90 --   1) Either hr_api.check_integrity_violated,
91 --      hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
92 --      hr_api.unique_integrity_violated has been raised with the subsequent
93 --      stripping of the constraint name from the generated error message
94 --      text.
95 --   2) Standalone validation test which corresponds with a constraint error.
96 --
97 -- In Parameter:
98 --   p_constraint_name is in upper format and is just the constraint name
99 --   (e.g. not prefixed by brackets, schema owner etc).
100 --
101 -- Post Success:
102 --   Development dependant.
103 --
104 -- Post Failure:
105 --   Developement dependant.
106 --
107 -- Developer Implementation Notes:
108 --   For each constraint being checked the hr system package failure message
109 --   has been generated as a template only. These system error messages should
110 --   be modified as required (i.e. change the system failure message to a user
111 --   friendly defined error message).
112 --
113 -- Access Status:
114 --   Internal Development Use Only.
115 --
116 -- {End Of Comments}
117 -- ----------------------------------------------------------------------------
118 Procedure constraint_error
119   (p_constraint_name in all_constraints.constraint_name%TYPE);
120 --
121 -- ----------------------------------------------------------------------------
122 -- |---------------------------------< lck >----------------------------------|
123 -- ----------------------------------------------------------------------------
124 -- {Start of comments}
125 --
126 -- Description:
127 --   The Lck process has two main functions to perform. Firstly, the row to be
128 --   updated or deleted must be locked. The locking of the row will only be
129 --   successful if the row is not currently locked by another user.
130 --   Secondly, during the locking of the row, the row is selected into
131 --   the g_old_rec data structure which enables the current row values from the
132 --   server to be available to the api.
133 --
134 -- Prerequisites:
135 --   When attempting to call the lock the object version number (if defined)
136 --   is mandatory.
137 --
138 -- In Parameters:
139 --   The arguments to the Lck process are the primary key(s) which uniquely
140 --   identify the row and the object version number of row.
141 --
142 -- Post Success:
143 --   On successful completion of the Lck process the row to be updated or
144 --   deleted will be locked and selected into the global data structure
145 --   g_old_rec.
146 --
147 -- Post Failure:
148 --   The Lck process can fail for three reasons:
149 --   1) When attempting to lock the row the row could already be locked by
150 --      another user. This will raise the HR_Api.Object_Locked exception.
151 --   2) The row which is required to be locked doesn't exist in the HR Schema.
152 --      This error is trapped and reported using the message name
153 --      'HR_7220_INVALID_PRIMARY_KEY'.
154 --   3) The row although existing in the HR Schema has a different object
155 --      version number than the object version number specified.
156 --      This error is trapped and reported using the message name
157 --      'HR_7155_OBJECT_INVALID'.
158 --
159 -- Developer Implementation Notes:
160 --   For each primary key and the object version number arguments add a
161 --   call to hr_api.mandatory_arg_error procedure to ensure that these
162 --   argument values are not null.
163 --
164 -- Access Status:
165 --   Internal Development Use Only.
166 --
167 -- {End of comments}
168 -- ----------------------------------------------------------------------------
169 Procedure lck
170   (p_stat_trans_audit_id                 in     number
171   ,p_object_version_number                in     number
172   );
173 --
174 -- ----------------------------------------------------------------------------
175 -- |-----------------------------< convert_args >-----------------------------|
176 -- ----------------------------------------------------------------------------
177 -- {Start Of Comments}
178 --
179 -- Description:
180 --   This function is used to turn attribute parameters into the record
181 --   structure parameter g_rec_type.
182 --
183 -- Prerequisites:
184 --   This is a private function and can only be called from the ins or upd
185 --   attribute processes.
186 --
187 -- In Parameters:
188 --
189 -- Post Success:
190 --   A returning record structure will be returned.
191 --
192 -- Post Failure:
193 --   No direct error handling is required within this function.  Any possible
194 --   errors within this function will be a PL/SQL value error due to conversion
195 --   of datatypes or data lengths.
196 --
197 -- Developer Implementation Notes:
198 --   None.
199 --
200 -- Access Status:
201 --   Internal Row Handler Use Only.
202 --
203 -- {End Of Comments}
204 -- ----------------------------------------------------------------------------
205 Function convert_args
206   (p_stat_trans_audit_id           in number
207   ,p_transaction_type               in varchar2
208   ,p_transaction_subtype            in varchar2
209   ,p_transaction_date               in date
210   ,p_transaction_effective_date     in date
211   ,p_business_group_id              in number
212   ,p_person_id                      in number
213   ,p_assignment_id                  in number
214   ,p_source1                        in varchar2
215   ,p_source1_type                   in varchar2
216   ,p_source2                        in varchar2
217   ,p_source2_type                   in varchar2
218   ,p_source3                        in varchar2
219   ,p_source3_type                   in varchar2
220   ,p_source4                        in varchar2
221   ,p_source4_type                   in varchar2
222   ,p_source5                        in varchar2
223   ,p_source5_type                   in varchar2
224   ,p_transaction_parent_id          in number
225   ,p_audit_information_category     in varchar2
226   ,p_audit_information1             in varchar2
227   ,p_audit_information2             in varchar2
228   ,p_audit_information3             in varchar2
229   ,p_audit_information4             in varchar2
230   ,p_audit_information5             in varchar2
231   ,p_audit_information6             in varchar2
232   ,p_audit_information7             in varchar2
233   ,p_audit_information8             in varchar2
234   ,p_audit_information9             in varchar2
235   ,p_audit_information10            in varchar2
236   ,p_audit_information11            in varchar2
237   ,p_audit_information12            in varchar2
238   ,p_audit_information13            in varchar2
239   ,p_audit_information14            in varchar2
240   ,p_audit_information15            in varchar2
241   ,p_audit_information16            in varchar2
242   ,p_audit_information17            in varchar2
243   ,p_audit_information18            in varchar2
244   ,p_audit_information19            in varchar2
245   ,p_audit_information20            in varchar2
246   ,p_audit_information21            in varchar2
247   ,p_audit_information22            in varchar2
248   ,p_audit_information23            in varchar2
249   ,p_audit_information24            in varchar2
250   ,p_audit_information25            in varchar2
251   ,p_audit_information26            in varchar2
252   ,p_audit_information27            in varchar2
253   ,p_audit_information28            in varchar2
254   ,p_audit_information29            in varchar2
255   ,p_audit_information30            in varchar2
256   ,p_title                          in varchar2
257   ,p_object_version_number          in number
258   )
259   Return g_rec_type;
260 --
261 end pay_aud_shd;