1 PACKAGE JTF_PERZ_DATA_PUB as
2 /* $Header: jtfzppds.pls 120.2 2005/11/02 03:59:11 skothe ship $ */
3 --
4 --
5 -- Start of Comments
6 --
7 -- NAME
8 -- JTF_PERZ_DATA_PUB
9 --
10 -- PURPOSE
11 -- Public API for creating, getting and updating personalized data objects
12 -- in the Personalization Framework.
13 --
14 -- NOTES
15 -- This is a pulicly accessible pacakge. It should be used by all
16 -- sources for creating, getting and updating personalized data objects
17 -- in the Personalization Framework.
18 --
19 -- HISTORY
20 -- 05/26/99 CCHANDRA Created
21 -- 05/26/99 CCHANDRA Added Create, get, update APIs
22 -- 05/26/99 SMATTEGU updated create, get and update APIs
23 -- 06/20/99 CCHANDRA updated APIs, renamed package
24 -- 07/28/99 CCHANDRA added documentation, user notes.
25 -- 09/20/99 SMATTEGU Changed
26 -- DATA_ATTRIB_REC_TYPE, DATA_OUT_REC_TYPE
27 -- save, create and get_perz_data APIs
28 -- 09/27/99 SMATTEGU Documenting the entire package
29 -- 01/24/00 SMATTEGU Documenting the entire package
30 -- 02/03/2000 SMATTEGU Enhancement #1181062 changing the
31 -- perz_data_name size from 60 to 120
32 --
33 -- End of Comments
34 --
35 -- *****************************************************************************
36 -- *****************************************************************************
37 -- Start of Comments
38 --
39 -- DATA_ATTRIB_REC_TYPE Rec
40 --
41 -- This record is used to set the data attributes associated
42 -- with a personalized data object.
43 --
44 -- End of Comments
45
46 TYPE DATA_ATTRIB_REC_TYPE IS RECORD
47 (
48 PERZ_DATA_ATTRIB_ID NUMBER := NULL,
49 PERZ_DATA_ID NUMBER := NULL,
50 ATTRIBUTE_NAME VARCHAR2(60) := NULL,
51 ATTRIBUTE_TYPE VARCHAR2(30) := NULL,
52 ATTRIBUTE_VALUE VARCHAR2(300) := NULL,
53 ATTRIBUTE_CONTEXT VARCHAR2(360) := NULL
54 );
55
56 -- Start of Comments
57 --
58 -- DATA_ATTRIB_REC_TYPE Table: DATA_ATTRIB_TBL_TYPE
59 --
60 --
61 -- End of Comments
62
63 TYPE DATA_ATTRIB_TBL_TYPE IS TABLE OF DATA_ATTRIB_REC_TYPE
64 INDEX BY BINARY_INTEGER;
65
66 -- G_MISS definition for table
67 G_MISS_DATA_ATTRIB_TBL DATA_ATTRIB_TBL_TYPE;
68
69 -- *****************************************************************************
70 -- DATA_OUT_REC_TYPE
71 --
72 -- This record defines the out record for a get performed on the database.
73 -- The table of results returned from Get_Perz_Data(..) will be a table
74 -- of this record type.
75 --
76 --
77 -- End of Comments
78
79 TYPE DATA_OUT_REC_TYPE IS RECORD
80 (
81 PERZ_DATA_ID NUMBER := NULL,
82 PROFILE_ID NUMBER := NULL,
83 APPLICATION_ID NUMBER := NULL,
84 PERZ_DATA_NAME VARCHAR2(120) := NULL,
85 PERZ_DATA_TYPE VARCHAR2(30) := NULL,
86 PERZ_DATA_DESC VARCHAR2(240) := NULL
87 );
88
89 -- Start of Comments
90 --
91 -- DATA_OUT_TBL_TYPE Table: DATA_OUT_REC_TYPE
92 --
93 --
94 -- End of Comments
95
96 TYPE DATA_OUT_TBL_TYPE IS TABLE OF DATA_OUT_REC_TYPE
97 INDEX BY BINARY_INTEGER;
98 -- *****************************************************************************
99 -- *****************************************************************************
100
101 -- Start of Comments
102 --
103 -- API name : Save_Perz_Data
104 -- Type : Public
105 -- Function : Create or update if exists, a personalized data object and
106 -- associated data attributes with values.
107 --
108 -- Parameters :
109 -- IN :
110 -- p_api_version_number IN NUMBER Required
111 -- p_init_msg_list IN VARCHAR2 Optional
112 -- p_commit IN VARCHAR Optional
113 --
114 -- p_application_id IN NUMBER Required
115
116 -- p_profile_id IN NUMBER Optional
117 -- p_profile_name IN VARCHAR2 Optional
118 -- p_profile_type IN VARCHAR2 Optional
119 -- p_profile_attrib IN PERZ_PROFILE_PUB.PROFILE_ATTRIB_TBL_TYPE
120 -- Optional
121 -- p_perz_data_id IN NUMBER Optional
122 -- p_perz_data_name IN VARCHAR2 Required
123 -- p_perz_data_type IN VARCHAR2 Required
124 -- p_perz_data_desc IN VARCHAR2 Optional
125 -- p_data_attrib_tbl IN JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE
126 --
127 -- OUT :
128 -- x_perz_data_id OUT NUMBER
129 -- x_return_status OUT VARCHAR2
130 -- x_msg_count OUT NUMBER
131 -- x_msg_data OUT VARCHAR2
132 --
133 --
134 -- Version : Current version 1.0
135 -- Initial version 1.0
136 --
137 -- Notes: This API createsor Updates the PerzData Object. If Profile is
138 -- not existing and necessary information is given, this API can create
139 -- the profile on the fly.
140 --
141 --
142 -- *****************************************************************************
143 --
144 -- USAGE NOTES :
145 --
146 -- 1. This API creates or updates if it already exists, a PerzData Object in
147 -- the personalization framework.
148 --
149 -- Of the input parameters p_profile_id (or the name of the profile
150 -- [p_profile_name] and its attributes p_Profile_Attrib) is a required field.
151 -- The other required fields are p_application_id, p_perz_data_name
152 -- p_perz_data_type (like BOOKMARKS, SHOPPING_TEMPLATE, etc.).
153 -- The PerzData Name and Type have to be unique for a given
154 -- profile id and application id, or the API will return an error.
155 -- The PerzData Name has to be made of characters with no spaces.
156 --
157 -- 2. The p_perz_data_desc is the description (free text) of Personalized data
158 -- object being saved. If PerzData Id is given, it must be unique at
159 -- the database. Otherwise, the API will return an error.
160 --
161 -- 3. The p_data_attrib_tbl is the table that holds the fields and values
162 -- associated with a PerzData. The ATTRIBUTE_NAME field holds the name/tag of the
163 -- attribute associated with a data object. The ATTRIBUTE_TYPE field holds the
164 -- type for this data attribute. The ATTRIBUTE_VALUE is used to store the
165 -- value of the data attribute. The ATTRIBUTE_CONTEXT is the context for that
166 -- value. For example, one could have a record like :
167 -- [BOOKMARK1, STRING, http://www.cnn.com, NULL].
168 --
169 -- 4. The main out parameter for this API is x_return_status which returns
170 -- FND_API.G_RETURN_SUCCESS when the API completes successfully
171 -- FND_API.G_RETURN_UNEXPECTED when the API reaches a unxpected state
172 -- FND_API.G_RETURN_ERROR when the API hits an error
173 --
174 -- *****************************************************************************
175 --
176
177 PROCEDURE Save_Perz_Data
178 ( p_api_version_number IN NUMBER,
179 p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
180 p_commit IN VARCHAR := FND_API.G_FALSE,
181
182 p_application_id IN NUMBER,
183 p_profile_id IN NUMBER,
184 p_profile_name IN VARCHAR2,
185 p_profile_type IN VARCHAR2,
186 p_profile_attrib IN JTF_PERZ_PROFILE_PUB.PROFILE_ATTRIB_TBL_TYPE
187 := JTF_PERZ_PROFILE_PUB.G_MISS_PROFILE_ATTRIB_TBL,
188 p_perz_data_id IN NUMBER,
189 p_perz_data_name IN VARCHAR2,
190 p_perz_data_type IN VARCHAR2,
191 p_perz_data_desc IN VARCHAR2,
192 p_data_attrib_tbl IN JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE
193 := JTF_PERZ_DATA_PUB.G_MISS_DATA_ATTRIB_TBL,
194
195 x_perz_data_id OUT NOCOPY /* file.sql.39 change */ NUMBER,
196 x_return_status OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
197 x_msg_count OUT NOCOPY /* file.sql.39 change */ NUMBER,
198 x_msg_data OUT NOCOPY /* file.sql.39 change */ VARCHAR2
199 );
200 -- *****************************************************************************
201
202
203 -- Start of Comments
204 --
205 -- API name : Create_Perz_Data
206 -- Type : Public
207 -- Function : Create a PerzData Object and associated data attributes
208 -- and values, for a given profile and application id.
209 --
210 -- Parameters :
211 -- IN :
212 -- p_api_version_number IN NUMBER Required
213 -- p_init_msg_list IN VARCHAR2 Optional
214 -- p_commit IN VARCHAR Optional
215 --
216 -- p_application_id IN NUMBER Required
217 -- p_profile_id IN NUMBER Optional
218 -- p_profile_name IN VARCHAR2 Optional
219 --
220 -- p_perz_data_id IN NUMBER Optional
221 -- p_perz_data_name IN VARCHAR2 Required
222 -- p_perz_data_type IN VARCHAR2 Required
223 -- p_perz_data_desc IN VARCHAR2 Optional
224 -- p_data_attrib_tbl IN JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE
225 --
226 -- OUT :
227 -- x_perz_data_id OUT NUMBER
228 -- x_return_status OUT VARCHAR2
229 -- x_msg_count OUT NUMBER
230 -- x_msg_data OUT VARCHAR2
231 --
232 --
233 -- Version :Current version 1.0
234 -- Initial version 1.0
235 --
236 -- Notes:
237 --
238 --
239 --
240 -- ******************************************************************************
241 --
242 --
243 -- USAGE NOTES :
244 --
245 -- 1. This API creates a PerzData Object in the personalization framework.
246 --
247 -- Of the input parameters p_profile_id (or the name of the profile
248 -- [p_profile_name] and its attributes p_Profile_Attrib) is a required field.
249 -- The other required fields are p_application_id, p_perz_data_name
250 -- p_perz_data_type (like BOOKMARKS, SHOPPING_TEMPLATE, etc.).
251 -- The PerzData Name and Type have to be unique for a given
252 -- profile id and application id, or the API will return an error.
253 -- The PerzData Name has to be made of characters with no spaces.
254 --
255 -- 2. The p_perz_data_desc is the description (free text) of Personalized
256 -- data object being saved. If PerzData Id is given, it must be unique at
257 -- the database. Otherwise, the API will return an error.
258 --
259 -- 3. The p_data_attrib_tbl is the table that holds the fields and values
260 -- associated with a PerzData. The ATTRIBUTE_NAME field holds the name/tag
261 -- of the attribute associated with a data object. The ATTRIBUTE_TYPE field
262 -- holds the type for this data attribute. The ATTRIBUTE_VALUE is used to
263 -- store the value of the data attribute. The ATTRIBUTE_CONTEXT is the context
264 -- for that value. For example, one could have a record like :
265 -- [BOOKMARK1, STRING, http://www.cnn.com, NULL].
266 --
267 -- 4. The main out parameter for this API is x_return_status which returns
268 -- FND_API.G_RETURN_SUCCESS when the API completes successfully
269 -- FND_API.G_RETURN_UNEXPECTED when the API reaches a unxpected state
270 -- FND_API.G_RETURN_ERROR when the API hits an error
271 -- *******************************************************************************
272
273 PROCEDURE Create_Perz_Data
274 ( p_api_version_number IN NUMBER,
275 p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
276 p_commit IN VARCHAR := FND_API.G_FALSE,
277
278 p_application_id IN NUMBER,
279 p_profile_id IN NUMBER,
280 p_profile_name IN VARCHAR2,
281 p_perz_data_id IN NUMBER,
282 p_perz_data_name IN VARCHAR2,
283 p_perz_data_type IN VARCHAR2,
284 p_perz_data_desc IN VARCHAR2,
285 p_data_attrib_tbl IN JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE
286 := JTF_PERZ_DATA_PUB.G_MISS_DATA_ATTRIB_TBL,
287
288 x_perz_data_id OUT NOCOPY /* file.sql.39 change */ NUMBER,
289 x_return_status OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
290 x_msg_count OUT NOCOPY /* file.sql.39 change */ NUMBER,
291 x_msg_data OUT NOCOPY /* file.sql.39 change */ VARCHAR2
292 );
293
294 -- *****************************************************************************
295
296
297 -- Start of Comments
298 --
299 -- API name : Get_Perz_Data
300 -- Type : Public
301 -- Function : Get personalized data object, attribute value pairs
302 -- for a given personalized data object and profile and app id.
303 --
304 -- Parameters :
305 -- IN :
306 -- p_api_version_number IN NUMBER Required
307 -- p_init_msg_list IN VARCHAR2 Optional
308 --
309 -- p_application_id IN NUMBER Required
310 -- p_profile_id IN NUMBER Optional
311 -- p_profile_name IN VARCHAR2 Optional
312 --
313 -- p_perz_data_id IN NUMBER Optional
314 -- p_perz_data_name IN VARCHAR2 Optional
315 -- p_perz_data_type IN VARCHAR2 Optional
316
317 -- OUT :
318 -- x_perz_data_id OUT NUMBER,
319 -- x_perz_data_name OUT VARCHAR2,
320 -- x_perz_data_type OUT VARCHAR2,
321 -- x_perz_data_desc OUT VARCHAR2,
322 -- x_data_attrib_tbl OUT JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE,
323 --
324 -- x_return_status OUT VARCHAR2
325 -- x_msg_count OUT NUMBER
326 -- x_msg_data OUT VARCHAR2
327 --
328 -- Version :Current version 1.0
329 -- Initial version 1.0
330 --
331 -- Notes:
332 --
333 --
334 --
335 -- *****************************************************************************
336 --
337 -- USAGE NOTES :
338 --
339 -- 1. This API gets/queries a personalized data object from the personalization
340 -- framework. Of the input parameters p_profile_id (or the name of the profile
341 -- p_profile_name) the application id (p_application_id), the name of the
342 -- data object p_perz_data_name and type are required fields. Sending in the
343 -- data id (p_perz_data_id) will improve performance.
344 --
345 -- 2. x_perz_data_id, x_perz_data_name, x_perz_data_type and x_perz_data_desc
346 -- holds the query header details.
347 --
348 -- 3. The x_data_attrib_tbl holds the output set from the PerzData Attributes.
349 -- This is a table of type JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE.
350 --
351 -- 4. The other out parameter for this API is x_return_status which returns
352 -- FND_API.G_RETURN_SUCCESS when the API completes successfully
353 -- FND_API.G_RETURN_UNEXPECTED when the API reaches a unxpected state
354 -- FND_API.G_RETURN_ERROR when the API hits an error
355 --
356 -- 5. This API will only return one PerzData and it's details.
357 -- If there are more than one retrieved then, this results in an error
358
359 -- *****************************************************************************
360
361 PROCEDURE Get_Perz_Data
362 ( p_api_version_number IN NUMBER,
363 p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
364
365 p_application_id IN NUMBER,
366 p_profile_id IN NUMBER,
367 p_profile_name IN VARCHAR2,
368 p_perz_data_id IN NUMBER,
369 p_perz_data_name IN VARCHAR2,
370 p_perz_data_type IN VARCHAR2 := NULL,
371
372 x_perz_data_id OUT NOCOPY /* file.sql.39 change */ NUMBER,
373 x_perz_data_name OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
374 x_perz_data_type OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
375 x_perz_data_desc OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
376 x_data_attrib_tbl OUT NOCOPY /* file.sql.39 change */ JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE,
377
378 x_return_status OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
379 x_msg_count OUT NOCOPY /* file.sql.39 change */ NUMBER,
380 x_msg_data OUT NOCOPY /* file.sql.39 change */ VARCHAR2
381 );
382 -- *****************************************************************************
383 --
384 -- Start of Comments
385 --
386 -- API name : Get_Perz_Data_Summary
387 -- Type : Public
388 -- Function : Get PerzData object
389 --
390 --
391 -- Parameters :
392 -- IN :
393 -- p_api_version_number IN NUMBER Required
394 -- p_init_msg_list IN VARCHAR2 Optional
395 --
396 -- p_application_id IN NUMBER Required
397 -- p_profile_id IN NUMBER Optional
398 -- p_profile_name IN VARCHAR2 Optional
399 --
400 -- p_perz_data_id IN NUMBER Optional
401 -- p_perz_data_name IN VARCHAR2 Optional
402 -- p_perz_data_type IN VARCHAR2 Optional
403
404 -- OUT :
408 -- x_perz_data_desc OUT VARCHAR2,
405 -- x_perz_data_id OUT NUMBER,
406 -- x_perz_data_name OUT VARCHAR2,
407 -- x_perz_data_type OUT VARCHAR2,
409 -- x_data_attrib_tbl OUT JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE,
410 --
411 -- x_return_status OUT VARCHAR2
412 -- x_msg_count OUT NUMBER
413 -- x_msg_data OUT VARCHAR2
414 --
415 -- Version :Current version 1.0
416 -- Initial version 1.0
417 --
418 -- Notes:
419 --
420 --
421 --
422 -- *****************************************************************************
423 --
424 -- USAGE NOTES :
425 --
426 -- 1. This API gets/queries a PerzData object from the personalization
427 -- framework. Of the input parameters p_profile_id (or the name of the
428 -- profile p_profile_name) the application id (p_application_id), the
429 -- name and type of the data object are required fields.
430 -- Sending in the data id (p_perz_data_id) will improve performance.
431 --
432 -- 3. The x_data_out_tbl holds the output set from the PerzData.
433 -- This is a table of type JTF_PERZ_DATA_PUB.DATA_OUT_TBL_TYPE.
434 --
435 -- 4. The other out parameter for this API is x_return_status which returns
436 -- FND_API.G_RETURN_SUCCESS when the API completes successfully
437 -- FND_API.G_RETURN_UNEXPECTED when the API reaches a unxpected state
438 -- FND_API.G_RETURN_ERROR when the API hits an error
439 --
440 -- *****************************************************************************
441
442
443 PROCEDURE Get_Perz_Data_Summary
444 ( p_api_version_number IN NUMBER,
445 p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
446
447 p_application_id IN NUMBER,
448 p_profile_id IN NUMBER,
449 p_profile_name IN VARCHAR2,
450 p_perz_data_id IN NUMBER,
451 p_perz_data_name IN VARCHAR2,
452 p_perz_data_type IN VARCHAR2 := NULL,
453
454 x_data_out_tbl OUT NOCOPY /* file.sql.39 change */ JTF_PERZ_DATA_PUB.DATA_OUT_TBL_TYPE,
455
456 x_return_status OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
457 x_msg_count OUT NOCOPY /* file.sql.39 change */ NUMBER,
458 x_msg_data OUT NOCOPY /* file.sql.39 change */ VARCHAR2
459 );
460 -- *****************************************************************************
461 -- Start of Comments
462 --
463 -- API name : Update_Perz_Data
464 -- Type : Public
465 -- Function : Update PerzData object
466 --
467 -- Parameters :
468 -- IN :
469 -- p_api_version_number IN NUMBER Required
470 -- p_init_msg_list IN VARCHAR2 Optional
471 -- p_commit IN VARCHAR Optional
472 --
473 -- p_application_id IN NUMBER Required
474 -- p_profile_id IN NUMBER Required
475 --
476 -- p_perz_data_id IN NUMBER Optional
477 -- p_perz_data_name IN VARCHAR2 Required
478 -- p_perz_data_type IN VARCHAR2 Required
479 -- p_perz_data_desc IN VARCHAR2 Optional
480 -- p_data_attrib_tbl IN JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE
481 --
482 -- OUT :
483 -- x_perz_data_id OUT NUMBER
484 -- x_return_status OUT VARCHAR2
485 -- x_msg_count OUT NUMBER
486 -- x_msg_data OUT VARCHAR2
487 --
488 --
489 --
490 -- Version :Current version 1.0
491 -- Initial version 1.0
492 --
493 -- Notes:
494 --
495 -- *****************************************************************************
496 --
497 --
498 -- USAGE NOTES :
499 --
500 -- 1. This API updates a PerzData Object in the personalization framework.
501 --
502 -- The required fields are profile_id,p_application_id, p_perz_data_name
503 -- or id, p_perz_data_type. The PerzData Name and Type have to be unique
504 -- for a given profile id and application id, or
505 -- the API will return an error.
506 --
507 -- 2. The p_perz_data_desc is the description of Personalized data
508 -- object saved. If PerzData Id is given, it must be unique at
509 -- the database. Otherwise, the API will return an error.
510 --
511 -- 3. The p_data_attrib_tbl is the table that holds the fields and values
512 -- associated with a PerzData. The ATTRIBUTE_NAME field holds the name/tag of the
513 -- attribute associated with a data object. The ATTRIBUTE_TYPE field holds the
514 -- type for this data attribute. The ATTRIBUTE_VALUE is used to store the
515 -- value of the data attribute. The ATTRIBUTE_CONTEXT is the context for that
516 -- value. For example, one could have a record like :
517 -- [BOOKMARK1, STRING, http://www.cnn.com, NULL].
518 --
519 -- 5. The main out parameter for this API is x_return_status which returns
520 -- FND_API.G_RETURN_SUCCESS when the API completes successfully
521 -- FND_API.G_RETURN_UNEXPECTED when the API reaches a unxpected state
522 -- FND_API.G_RETURN_ERROR when the API hits an error
523 --
524 -- *****************************************************************************
525 --
526
527 PROCEDURE Update_Perz_Data
528 ( p_api_version_number IN NUMBER,
529 p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
530 p_commit IN VARCHAR := FND_API.G_FALSE,
531
532 p_application_id IN NUMBER,
533 p_profile_id IN NUMBER,
534
535 p_perz_data_id IN NUMBER,
536 p_perz_data_name IN VARCHAR2,
537 p_perz_data_type IN VARCHAR2 := NULL,
541
538 p_perz_data_desc IN VARCHAR2,
539 p_data_attrib_tbl IN JTF_PERZ_DATA_PUB.DATA_ATTRIB_TBL_TYPE
540 := JTF_PERZ_DATA_PUB.G_MISS_DATA_ATTRIB_TBL,
542 x_perz_data_id OUT NOCOPY /* file.sql.39 change */ NUMBER,
543 x_return_status OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
544 x_msg_count OUT NOCOPY /* file.sql.39 change */ NUMBER,
545 x_msg_data OUT NOCOPY /* file.sql.39 change */ VARCHAR2
546 );
547 -- *****************************************************************************
548
549 -- Start of Comments
550 --
551 -- API name : Delete_Perz_Data
552 -- Type : Public
553 -- Function : Deletes a PerzData object
554 --
555 -- Paramaeters :
556 -- IN :
557 -- p_api_version_number IN NUMBER Required
558 -- p_init_msg_list IN VARCHAR2 Optional
559 -- p_commit IN VARCHAR Optional
560 --
561 -- p_application_id IN NUMBER Required
562 -- p_profile_id IN NUMBER Required
563 -- p_perz_data_id IN NUMBER Required
564 --
565 -- OUT :
566 -- x_return_status OUT VARCHAR2
567 -- x_msg_count OUT NUMBER
568 -- x_msg_data OUT VARCHAR2
569 --
570 --
571 --
572 -- Version : Current version 1.0
573 -- Initial version 1.0
574 --
575 -- Notes:
576 --
577 -- *****************************************************************************
578 --
579 -- USAGE NOTES :
580 --
584 -- required fields.
581 -- 1. This API deletes a personalized data object from the personalization framework.
582 -- Of the input parameters p_profile_id (or the name of the profile p_profile_name)
583 -- the application id (p_application_id) and the data id p_perz_data_id are
585 --
586 -- 2. The out parameter for this API is x_return_status which returns
587 -- FND_API.G_RETURN_SUCCESS when the API completes successfully
588 -- FND_API.G_RETURN_UNEXPECTED when the API reaches a unxpected state
589 -- FND_API.G_RETURN_ERROR when the API hits an error
590 --
591 -- *****************************************************************************
592
593 PROCEDURE Delete_Perz_Data
594 ( p_api_version_number IN NUMBER,
595 p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE,
596 p_commit IN VARCHAR := FND_API.G_FALSE,
597
598 p_application_id IN NUMBER,
599 p_profile_id IN NUMBER,
600 p_perz_data_id IN NUMBER,
601
602 x_return_status OUT NOCOPY /* file.sql.39 change */ VARCHAR2,
603 x_msg_count OUT NOCOPY /* file.sql.39 change */ NUMBER,
604 x_msg_data OUT NOCOPY /* file.sql.39 change */ VARCHAR2
605 );
606
607 -- *****************************************************************************
608 -- *****************************************************************************
609 END JTF_PERZ_DATA_PUB;
[Home] [Help]