[Home] [Help]
1 PACKAGE AMS_ObjectAttribute_PVT AUTHID CURRENT_USER AS
2 /* $Header: amsvobas.pls 115.11 2001/12/17 16:15:21 pkm ship $ */
3
4
5 ---------------------------------------------------------------------
6 -- PROCEDURE
7 -- create_object_attributes
8 --
9 -- PURPOSE
10 -- Create all the attributes used by an object (campaign/event/event offering)
11 --
12 -- PARAMETERS
13 -- p_object_type : the four letter indicator for the object (Campaign / event / offering)
14 -- p_object_id : Unique identifier that identifies the object
15 -- p_setup_id : identifier of the setup type used to create the object
16 --
17 -- NOTES
18 -- 1. Check if object type and setup type are valid.
19 -- 2. select all the attributes available for this setup type from ams_custom_setup_attr and
20 -- insert it in to ams_object_attributes
21 -- 3. Insert the mandatory general attribute with the display sequence no 0.
22 -- (This general attribute is mandatory for all objects and should be displayed first. This
23 -- attribute will also have the defined flag checked as details are filled during object creation.)
24
25 -- USAGE
26 -- Use this procedure whenever a new object (campaign/event/event offering) is created.
27 -- This will insert all the available attributes for this object and setup combination.
28 ---------------------------------------------------------------------
29 PROCEDURE create_object_attributes(
30 p_api_version IN NUMBER,
31 p_init_msg_list IN VARCHAR2 := FND_API.g_false,
32 p_commit IN VARCHAR2 := FND_API.g_false,
33 p_validation_level IN NUMBER := FND_API.g_valid_level_full,
34
35 x_return_status OUT VARCHAR2,
36 x_msg_count OUT NUMBER,
37 x_msg_data OUT VARCHAR2,
38
39 p_object_type IN VARCHAR2,
40 p_object_id IN NUMBER,
41 p_setup_id IN NUMBER
42 );
43
44
45 ---------------------------------------------------------------------
46 -- PROCEDURE
47 -- modify_object_attribute
48 --
49 -- PURPOSE
50 -- Create all the attributes used by an object (campaign/event/event offering)
51 --
52 -- PARAMETERS
53 -- p_object_type : the four letter indicator for the object (Campaign / event / offering)
54 -- p_object_id : Unique identifier that identifies the object
55 -- p_attr : identifier of the setup type used to create the object
56 -- p_attr_defined_flag : flag to indicate if values are defined for the attribute or not (Y/N)
57 --
58 -- NOTES
59 -- 1. Check if object type and and attribute are valid.
60 -- 2. Update the attribute defined flag
61
62 -- USAGE
63 -- Use this procedure whenever values are entered for an object atribute.
64 -- (ex. If a Product is defined for a campaign call this procedure and pass the attr_defined_flag as 'Y'.
65 -- This would tell the user that a product has already been defined for the campaign.)
66 -- Use this procedure when all the values are deleted for an object attribute
67 -- (ex. If all Products for a campaign are deleted, call this procedure and pass the attr_defined_flag as 'N'.
68 -- This would tell the user that no product has been defined for the campaign.)
69 --
70 --
71 ---------------------------------------------------------------------
72 PROCEDURE modify_object_attribute(
73 p_api_version IN NUMBER,
74 p_init_msg_list IN VARCHAR2 := FND_API.g_false,
75 p_commit IN VARCHAR2 := FND_API.g_false,
76 p_validation_level IN NUMBER := FND_API.g_valid_level_full,
77
78 x_return_status OUT VARCHAR2,
79 x_msg_count OUT NUMBER,
80 x_msg_data OUT VARCHAR2,
81
82 p_object_type IN VARCHAR2,
83 p_object_id IN NUMBER,
84 p_attr IN VARCHAR2,
85 p_attr_defined_flag IN VARCHAR2
86 );
87
88
89 ---------------------------------------------------------------------
90 -- FUNCTION
91 -- check_object_attribute
92 --
93 -- PURPOSE
94 -- Check if an attribute can be attached to the specified object.
95 ---------------------------------------------------------------------
96 FUNCTION check_object_attribute(
97 p_obj_type IN VARCHAR2,
98 p_obj_id IN NUMBER,
99 p_attribute IN VARCHAR2
100 )
101 RETURN VARCHAR2; --FND_API.g_true/g_false
102
103
104 END AMS_ObjectAttribute_PVT;
|
|
|
|