1 Package pay_liv_upd AUTHID CURRENT_USER as
2 /* $Header: pylivrhi.pkh 120.0 2005/05/29 06:43:11 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |---------------------------------< upd >----------------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- This procedure is the record interface for the update
11 -- process for the specified entity. The role of this process is
12 -- to perform the datetrack update mode, fully validating the row
13 -- for the HR schema passing back to the calling process, any system
14 -- generated values (e.g. object version number attribute). This process
15 -- is the main backbone of the upd process. The processing of
16 -- this procedure is as follows:
17 -- 1) Ensure that the datetrack update mode is valid.
18 -- 2) The row to be updated is then locked and selected into the record
19 -- structure g_old_rec.
20 -- 3) Because on update parameters which are not part of the update do not
21 -- have to be defaulted, we need to build up the updated row by
22 -- converting any system defaulted parameters to their corresponding
23 -- value.
24 -- 4) The controlling validation process update_validate is then executed
25 -- which will execute all private and public validation business rule
26 -- processes.
27 -- 5) The pre_update process is then executed which enables any
28 -- logic to be processed before the update dml process is executed.
29 -- 6) The update_dml process will physical perform the update dml into the
30 -- specified entity.
31 -- 7) The post_update process is then executed which enables any
32 -- logic to be processed after the update dml process.
33 --
34 -- Prerequisites:
35 -- The main parameters to the process have to be in the record
36 -- format.
37 --
38 -- In Parameters:
39 -- p_effective_date
40 -- Specifies the date of the datetrack update operation.
41 -- p_datetrack_mode
42 -- Determines the datetrack update mode.
43 --
44 -- Post Success:
45 -- The specified row will be fully validated and datetracked updated for
46 -- the specified entity without being committed for the datetrack mode.
47 --
48 -- Post Failure:
49 -- If an error has occurred, an error message will be raised.
50 --
51 -- Developer Implementation Notes:
52 -- None.
53 --
54 -- Access Status:
55 -- Internal Development Use Only.
56 --
57 -- ----------------------------------------------------------------------------
58 Procedure upd
59 (p_effective_date in date
60 ,p_datetrack_mode in varchar2
61 ,p_rec in out nocopy pay_liv_shd.g_rec_type
62 ,p_default_range_warning out nocopy boolean
63 ,p_default_formula_warning out nocopy boolean
64 ,p_assignment_id_warning out nocopy boolean
65 ,p_formula_message out nocopy varchar2
66 );
67 --
68 -- ----------------------------------------------------------------------------
69 -- |-------------------------------< upd >------------------------------------|
70 -- ----------------------------------------------------------------------------
71 -- {Start Of Comments}
72 --
73 -- Description:
74 -- This procedure is the attribute interface for the datetrack update
75 -- process for the specified entity and is the outermost layer.
76 -- The role of this process is to update a fully validated row into the
77 -- HR schema passing back to the calling process, any system generated
78 -- values (e.g. object version number attributes). The processing of this
79 -- procedure is as follows:
80 -- 1) The attributes are converted into a local record structure by
81 -- calling the convert_args function.
82 -- 2) After the conversion has taken place, the corresponding record upd
83 -- interface process is executed.
84 -- 3) OUT parameters are then set to their corresponding record attributes.
85 --
86 -- Prerequisites:
87 --
88 -- In Parameters:
89 -- p_effective_date
90 -- Specifies the date of the datetrack update operation.
91 -- p_datetrack_mode
92 -- Determines the datetrack update mode.
93 --
94 -- Post Success:
95 -- A fully validated row will be updated for the specified entity
96 -- without being committed.
97 --
98 -- Post Failure:
99 -- If an error has occurred, an error message will be raised.
100 --
101 -- Developer Implementation Notes:
102 -- None.
103 --
104 -- Access Status:
105 -- Internal Development Use Only.
106 --
107 -- {End Of Comments}
108 -- ----------------------------------------------------------------------------
109 Procedure upd
110 (p_effective_date in date
111 ,p_datetrack_mode in varchar2
112 ,p_link_input_value_id in number
113 ,p_object_version_number in out nocopy number
114 ,p_element_link_id in number default hr_api.g_number
115 ,p_input_value_id in number default hr_api.g_number
116 ,p_costed_flag in varchar2 default hr_api.g_varchar2
117 ,p_default_value in varchar2 default hr_api.g_varchar2
118 ,p_max_value in varchar2 default hr_api.g_varchar2
119 ,p_min_value in varchar2 default hr_api.g_varchar2
120 ,p_warning_or_error in varchar2 default hr_api.g_varchar2
121 ,p_effective_start_date out nocopy date
122 ,p_effective_end_date out nocopy date
123 ,p_default_range_warning out nocopy boolean
124 ,p_default_formula_warning out nocopy boolean
125 ,p_assignment_id_warning out nocopy boolean
126 ,p_formula_message out nocopy varchar2
127 );
128 --
129 end pay_liv_upd;
[Home] [Help]