eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.AMS_AGENDAS_PVT dependencies on FND_API

Line 64: -- 6. Please don't pass in any FND_API.g_mess_char/num/date.

60: -- the sequence.
61: -- 4. If a flag column is passed in, check if it is 'Y' or 'N'.
62: -- Raise exception for invalid flag.
63: -- 5. If a flag column is not passed in, default it to 'Y' or 'N'.
64: -- 6. Please don't pass in any FND_API.g_mess_char/num/date.
65: ---------------------------------------------------------------------
66:
67: PROCEDURE create_agenda(
68: p_api_version IN NUMBER,

Line 69: p_init_msg_list IN VARCHAR2 := FND_API.g_false,

65: ---------------------------------------------------------------------
66:
67: PROCEDURE create_agenda(
68: p_api_version IN NUMBER,
69: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
70: p_commit IN VARCHAR2 := FND_API.g_false,
71: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
72:
73: p_agenda_rec IN agenda_rec_type,

Line 70: p_commit IN VARCHAR2 := FND_API.g_false,

66:
67: PROCEDURE create_agenda(
68: p_api_version IN NUMBER,
69: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
70: p_commit IN VARCHAR2 := FND_API.g_false,
71: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
72:
73: p_agenda_rec IN agenda_rec_type,
74:

Line 71: p_validation_level IN NUMBER := FND_API.g_valid_level_full,

67: PROCEDURE create_agenda(
68: p_api_version IN NUMBER,
69: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
70: p_commit IN VARCHAR2 := FND_API.g_false,
71: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
72:
73: p_agenda_rec IN agenda_rec_type,
74:
75: x_return_status OUT NOCOPY VARCHAR2,

Line 99: p_init_msg_list IN VARCHAR2 := FND_API.g_false,

95: -- 1. Raise exception if the object_version_number doesn't match.
96: --------------------------------------------------------------------
97: PROCEDURE delete_agenda(
98: p_api_version IN NUMBER,
99: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
100: p_commit IN VARCHAR2 := FND_API.g_false,
101:
102: p_agenda_id IN NUMBER,
103: p_object_version IN NUMBER,

Line 100: p_commit IN VARCHAR2 := FND_API.g_false,

96: --------------------------------------------------------------------
97: PROCEDURE delete_agenda(
98: p_api_version IN NUMBER,
99: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
100: p_commit IN VARCHAR2 := FND_API.g_false,
101:
102: p_agenda_id IN NUMBER,
103: p_object_version IN NUMBER,
104:

Line 127: p_init_msg_list IN VARCHAR2 := FND_API.g_false,

123: -- 1. Raise exception if the object_version_number doesn't match.
124: --------------------------------------------------------------------
125: PROCEDURE lock_agenda(
126: p_api_version IN NUMBER,
127: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
128:
129: p_agenda_id IN NUMBER,
130: p_object_version IN NUMBER,
131:

Line 150: -- 2. If an attribute is passed in as FND_API.g_miss_char/num/date,

146: -- p_agenda_rec: the record with new items
147: --
148: -- NOTES
149: -- 1. Raise exception if the object_version_number doesn't match.
150: -- 2. If an attribute is passed in as FND_API.g_miss_char/num/date,
151: -- that column won't be updated.
152: ----------------------------------------------------------------------
153: PROCEDURE update_agenda(
154: p_api_version IN NUMBER,

Line 155: p_init_msg_list IN VARCHAR2 := FND_API.g_false,

151: -- that column won't be updated.
152: ----------------------------------------------------------------------
153: PROCEDURE update_agenda(
154: p_api_version IN NUMBER,
155: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
156: p_commit IN VARCHAR2 := FND_API.g_false,
157: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
158:
159: p_agenda_rec IN agenda_rec_type,

Line 156: p_commit IN VARCHAR2 := FND_API.g_false,

152: ----------------------------------------------------------------------
153: PROCEDURE update_agenda(
154: p_api_version IN NUMBER,
155: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
156: p_commit IN VARCHAR2 := FND_API.g_false,
157: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
158:
159: p_agenda_rec IN agenda_rec_type,
160:

Line 157: p_validation_level IN NUMBER := FND_API.g_valid_level_full,

153: PROCEDURE update_agenda(
154: p_api_version IN NUMBER,
155: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
156: p_commit IN VARCHAR2 := FND_API.g_false,
157: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
158:
159: p_agenda_rec IN agenda_rec_type,
160:
161: x_return_status OUT NOCOPY VARCHAR2,

Line 179: -- should not be any FND_API.g_miss_char/num/date in it.

175: -- p_agenda_rec: the agenda record to be validated
176: --
177: -- NOTES
178: -- 1. p_agenda_rec should be the complete agenda record. There
179: -- should not be any FND_API.g_miss_char/num/date in it.
180: ----------------------------------------------------------------------
181: PROCEDURE validate_agenda(
182: p_api_version IN NUMBER,
183: p_init_msg_list IN VARCHAR2 := FND_API.g_false,

Line 183: p_init_msg_list IN VARCHAR2 := FND_API.g_false,

179: -- should not be any FND_API.g_miss_char/num/date in it.
180: ----------------------------------------------------------------------
181: PROCEDURE validate_agenda(
182: p_api_version IN NUMBER,
183: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
184: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
185:
186: p_agenda_rec IN agenda_rec_type,
187:

Line 184: p_validation_level IN NUMBER := FND_API.g_valid_level_full,

180: ----------------------------------------------------------------------
181: PROCEDURE validate_agenda(
182: p_api_version IN NUMBER,
183: p_init_msg_list IN VARCHAR2 := FND_API.g_false,
184: p_validation_level IN NUMBER := FND_API.g_valid_level_full,
185:
186: p_agenda_rec IN agenda_rec_type,
187:
188: x_return_status OUT NOCOPY VARCHAR2,

Line 222: -- as FND_API.g_miss_char/num/date

218: -- Check the record level business rules.
219: --
220: -- PARAMETERS
221: -- p_agenda_rec: the record to be validated; may contain attributes
222: -- as FND_API.g_miss_char/num/date
223: -- p_complete_rec: the complete record after all "g_miss" items
224: -- have been replaced by current database values
225: ---------------------------------------------------------------------
226: PROCEDURE validate_agenda_record(

Line 238: -- Initialize all attributes to be FND_API.g_miss_char/num/date.

234: -- PROCEDURE
235: -- init_agenda_rec
236: --
237: -- PURPOSE
238: -- Initialize all attributes to be FND_API.g_miss_char/num/date.
239: ---------------------------------------------------------------------
240: PROCEDURE init_agenda_rec(
241: p_agenda_rec IN agenda_rec_type,
242: x_agenda_rec OUT NOCOPY agenda_rec_type

Line 252: -- FND_API.g_miss_char/num/date if the user doesn't want to

248: -- complete_agenda_rec
249: --
250: -- PURPOSE
251: -- For update_agenda, some attributes may be passed in as
252: -- FND_API.g_miss_char/num/date if the user doesn't want to
253: -- update those attributes. This procedure will replace the
254: -- "g_miss" attributes with current database values.
255: --
256: -- PARAMETERS

Line 258: -- FND_API.g_miss_char/num/date

254: -- "g_miss" attributes with current database values.
255: --
256: -- PARAMETERS
257: -- p_agenda_rec: the record which may contain attributes as
258: -- FND_API.g_miss_char/num/date
259: -- x_complete_rec: the complete record after all "g_miss" items
260: -- have been replaced by current database values
261: ---------------------------------------------------------------------
262: PROCEDURE complete_agenda_rec(