DBA Data[Home] [Help]

PACKAGE: APPS.HR_EAP_UPD

Source


1 Package hr_eap_upd as
2 /* $Header: hreaprhi.pkh 120.0 2005/05/30 23:58 appldev noship $ */
3 -- ----------------------------------------------------------------------------
4 -- |----------------------------< update_sso_details >-------------------------|
5 -- ----------------------------------------------------------------------------
6 -- {Start of Comments}
7 -- Description:
8 --   This procedure is called to update the external application details in SSO
9 --   schema
10 --
11 -- Prerequisites:
12 --
13 -- In Parameters:
14 --   p_ext_application_id    IN   ext_application_id stored in
15 --                                hr_ki_ext_applications
16 --   p_app_code              IN   external app code
17 --   p_apptype               IN   application type
18 --   p_appurl                IN   URL for external application
19 --   p_logout_url            IN   URL for external application to logout
20 --   p_userfld               IN   name of user field
21 --   p_pwdfld                IN   name of password field
22 --   p_authused              IN   type of authentication used
23 --   p_fnameN                IN   additional names  (N=1..9)
24 --   p_fvalN                 IN   additional values (N=1..9)
25 --
26 -- Post Success:
27 -- External application is updated in SSO schema.
28 --
29 -- Post Failure:
30 --   An application error is raised if in case of failure
31 --
32 -- Developer Implementation Notes:
33 --   None.
34 --
35 -- Access Status:
36 --   Internal Development Use Only.
37 --
38 -- {End of Comments}
39 -- ----------------------------------------------------------------------------
40 procedure update_sso_details
41  (
42         p_ext_application_id   IN number,
43         p_app_code       IN VARCHAR2,
44         p_apptype        IN VARCHAR2,
45         p_appurl         IN VARCHAR2,
46         p_logout_url     IN VARCHAR2,
47         p_userfld        IN VARCHAR2,
48         p_pwdfld         IN VARCHAR2,
49         p_authused       IN VARCHAR2,
50         p_fname1         IN VARCHAR2 DEFAULT NULL,
51         p_fval1          IN VARCHAR2 DEFAULT NULL,
52         p_fname2         IN VARCHAR2 DEFAULT NULL,
53         p_fval2          IN VARCHAR2 DEFAULT NULL,
54         p_fname3         IN VARCHAR2 DEFAULT NULL,
55         p_fval3          IN VARCHAR2 DEFAULT NULL,
56         p_fname4         IN VARCHAR2 DEFAULT NULL,
57         p_fval4          IN VARCHAR2 DEFAULT NULL,
58         p_fname5         IN VARCHAR2 DEFAULT NULL,
59         p_fval5          IN VARCHAR2 DEFAULT NULL,
60         p_fname6         IN VARCHAR2 DEFAULT NULL,
61         p_fval6          IN VARCHAR2 DEFAULT NULL,
62         p_fname7         IN VARCHAR2 DEFAULT NULL,
63         p_fval7          IN VARCHAR2 DEFAULT NULL,
64         p_fname8         IN VARCHAR2 DEFAULT NULL,
65         p_fval8          IN VARCHAR2 DEFAULT NULL,
66         p_fname9         IN VARCHAR2 DEFAULT NULL,
67         p_fval9          IN VARCHAR2 DEFAULT NULL);
68 
69 
70 /* $Header: hreaprhi.pkh 120.0 2005/05/30 23:58 appldev noship $ */
71 --
72 -- ----------------------------------------------------------------------------
73 -- |----------------------------------< upd >---------------------------------|
74 -- ----------------------------------------------------------------------------
75 -- {Start Of Comments}
76 --
77 -- Description:
78 --   This procedure is the record interface for the update
79 --   process for the specified entity. The role of this process is
80 --   to update a fully validated row for the HR schema passing back
81 --   to the calling process, any system generated values (e.g.
82 --   object version number attribute). This process is the main
83 --   backbone of the upd business process. The processing of this
84 --   procedure is as follows:
85 --   1) The row to be updated is locked and selected into the record
86 --      structure g_old_rec.
87 --   2) Because on update parameters which are not part of the update do not
88 --      have to be defaulted, we need to build up the updated row by
89 --      converting any system defaulted parameters to their corresponding
90 --      value.
91 --   3) The controlling validation process update_validate is then executed
92 --      which will execute all private and public validation business rule
93 --      processes.
94 --   4) The pre_update process is then executed which enables any
95 --      logic to be processed before the update dml process is executed.
96 --   5) The update_dml process will physical perform the update dml into the
97 --      specified entity.
98 --   6) The post_update process is then executed which enables any
99 --      logic to be processed after the update dml process.
100 --
101 -- Prerequisites:
102 --   The main parameters to the business process have to be in the record
103 --   format.
104 --
105 -- In Parameters:
106 --
107 -- Post Success:
108 --   The specified row will be fully validated and updated for the specified
109 --   entity without being committed.
110 --
111 -- Post Failure:
112 --   If an error has occurred, an error message will be raised.
113 --
114 -- Developer Implementation Notes:
115 --   None.
116 --
117 -- Access Status:
118 --   Internal Development Use Only.
119 --
120 -- {End Of Comments}
121 -- ----------------------------------------------------------------------------
122 Procedure upd
123   (p_rec                          in out nocopy hr_eap_shd.g_rec_type
124   );
125 --
126 -- ----------------------------------------------------------------------------
127 -- |---------------------------------< upd >----------------------------------|
128 -- ----------------------------------------------------------------------------
129 -- {Start Of Comments}
130 --
131 -- Description:
132 --   This procedure is the attribute interface for the update
133 --   process for the specified entity and is the outermost layer. The role
134 --   of this process is to update a fully validated row into the HR schema
135 --   passing back to the calling process, any system generated values
136 --   (e.g. object version number attributes). The processing of this
137 --   procedure is as follows:
138 --   1) The attributes are converted into a local record structure by
139 --      calling the convert_args function.
140 --   2) After the conversion has taken place, the corresponding record upd
141 --      interface process is executed.
142 --   3) OUT parameters are then set to their corresponding record attributes.
143 --
144 -- Prerequisites:
145 --
146 -- In Parameters:
147 --
148 -- Post Success:
149 --   A fully validated row will be updated for the specified entity
150 --   without being committed.
151 --
152 -- Post Failure:
153 --   If an error has occurred, an error message will be raised.
154 --
155 -- Developer Implementation Notes:
156 --   None.
157 --
158 -- Access Status:
159 --   Internal Development Use Only.
160 --
161 -- {End Of Comments}
162 -- ----------------------------------------------------------------------------
163 Procedure upd
164   (p_ext_application_id           in     number
165   ,p_external_application_name    in     varchar2  default hr_api.g_varchar2
166 
167   );
168 --
169 end hr_eap_upd;