DBA Data[Home] [Help]

PACKAGE: APPS.BEN_XER_UPD

Source


1 Package ben_xer_upd as
2 /* $Header: bexerrhi.pkh 120.0 2005/05/28 12:32:39 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 update a fully validated row for the HR schema passing back
13 --   to the calling process, any system generated values (e.g.
14 --   object version number attribute). This process is the main
15 --   backbone of the upd business process. The processing of this
16 --   procedure is as follows:
17 --   1) The row to be updated is locked and selected into the record
18 --      structure g_old_rec.
19 --   2) Because on update parameters which are not part of the update do not
20 --      have to be defaulted, we need to build up the updated row by
21 --      converting any system defaulted parameters to their corresponding
22 --      value.
23 --   3) The controlling validation process update_validate is then executed
24 --      which will execute all private and public validation business rule
25 --      processes.
26 --   4) The pre_update process is then executed which enables any
27 --      logic to be processed before the update dml process is executed.
28 --   5) The update_dml process will physical perform the update dml into the
29 --      specified entity.
30 --   6) The post_update process is then executed which enables any
31 --      logic to be processed after the update dml process.
32 --
33 -- Prerequisites:
34 --   The main parameters to the business process have to be in the record
35 --   format.
36 --
37 -- In Parameters:
38 --
39 -- Post Success:
40 --   The specified row will be fully validated and updated for the specified
41 --   entity without being committed.
42 --
43 -- Post Failure:
44 --   If an error has occurred, an error message will be supplied with the work
45 --   rolled back.
46 --
47 -- Developer Implementation Notes:
48 --   None.
49 --
50 -- Access Status:
51 --   Internal Development Use Only.
52 --
53 -- {End Of Comments}
54 -- ----------------------------------------------------------------------------
55 Procedure upd
56   (
57   p_effective_date               in date,
58   p_rec        in out nocopy ben_xer_shd.g_rec_type
59   );
60 --
61 -- ----------------------------------------------------------------------------
62 -- |---------------------------------< upd >----------------------------------|
63 -- ----------------------------------------------------------------------------
64 -- {Start Of Comments}
65 --
66 -- Description:
67 --   This procedure is the attribute interface for the update
68 --   process for the specified entity and is the outermost layer. The role
69 --   of this process is to update a fully validated row into the HR schema
70 --   passing back to the calling process, any system generated values
71 --   (e.g. object version number attributes). The processing of this
72 --   procedure is as follows:
73 --   1) The attributes are converted into a local record structure by
74 --      calling the convert_args function.
75 --   2) After the conversion has taken place, the corresponding record upd
76 --      interface process is executed.
77 --   3) OUT parameters are then set to their corresponding record attributes.
78 --
79 -- Prerequisites:
80 --
81 -- In Parameters:
82 --
83 -- Post Success:
84 --   A fully validated row will be updated for the specified entity
85 --   without being committed.
86 --
87 -- Post Failure:
88 --   If an error has occurred, an error message will be supplied with the work
89 --   rolled back.
90 --
91 -- Developer Implementation Notes:
92 --   None.
93 --
94 -- Access Status:
95 --   Internal Development Use Only.
96 --
97 -- {End Of Comments}
98 -- ----------------------------------------------------------------------------
99 Procedure upd
100   (
101   p_effective_date               in date,
102   p_ext_data_elmt_in_rcd_id      in number,
103   p_seq_num                      in number           default hr_api.g_number,
104   p_strt_pos                     in number           default hr_api.g_number,
105   p_dlmtr_val                    in varchar2         default hr_api.g_varchar2,
106   p_rqd_flag                     in varchar2         default hr_api.g_varchar2,
107   p_sprs_cd                      in varchar2         default hr_api.g_varchar2,
108   p_any_or_all_cd                in varchar2         default hr_api.g_varchar2,
109   p_ext_data_elmt_id             in number           default hr_api.g_number,
110   p_ext_rcd_id                   in number           default hr_api.g_number,
111   p_business_group_id            in number           default hr_api.g_number,
112   p_legislation_code             in varchar2         default hr_api.g_varchar2,
113   p_last_update_date             in date             default hr_api.g_date,
114   p_creation_date                in date             default hr_api.g_date,
115   p_last_updated_by              in number           default hr_api.g_number,
116   p_last_update_login            in number           default hr_api.g_number,
117   p_created_by                   in number           default hr_api.g_number,
118   p_object_version_number        in out nocopy number,
119   p_hide_flag                    in varchar2         default hr_api.g_varchar2
120   );
121 --
122 end ben_xer_upd;