DBA Data[Home] [Help]

APPS.EGO_USER_ATTRS_DATA_PUB dependencies on EGO_USER_ATTR_DATA_TABLE

Line 73: * = EGO_USER_ATTR_DATA_TABLE =

69: * MTL_INTERFACE_ERRORS whose TRANSACTION_ID column values match the
70: * passed-in USER_ROW_IDENTIFIER.
71: *
72: * ============================
73: * = EGO_USER_ATTR_DATA_TABLE =
74: * ============================
75: *
76: *


77: CREATE EGO_USER_ATTR_DATA_TABLE AS TABLE OF EGO_USER_ATTR_DATA_OBJ;

Line 77: CREATE EGO_USER_ATTR_DATA_TABLE AS TABLE OF EGO_USER_ATTR_DATA_OBJ;

73: * = EGO_USER_ATTR_DATA_TABLE =
74: * ============================
75: *
76: *


77: CREATE EGO_USER_ATTR_DATA_TABLE AS TABLE OF EGO_USER_ATTR_DATA_OBJ;
78: *

79: *
80: * =========================
81: * = EGO_USER_ATTR_ROW_OBJ =

Line 248: * EGO_USER_ATTR_DATA_TABLE (described above). The procedure organizes

244: /*#
245: * Processes User-Defined Attribute data for one object instance.
246: * Parameters provide identifying data and metadata for an object
247: * instance, along with an EGO_USER_ATTR_ROW_TABLE and an accompanying
248: * EGO_USER_ATTR_DATA_TABLE (described above). The procedure organizes
249: * the data from the two tables and calls Process_Row for each distinct
250: * attribute group row passing all the attribute data for that row.
251: * Current version: 1.0
252: *

Line 327: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE

323: PROCEDURE Process_User_Attrs_Data (
324: p_api_version IN NUMBER
325: ,p_object_name IN VARCHAR2
326: ,p_attributes_row_table IN EGO_USER_ATTR_ROW_TABLE
327: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE
328: ,p_pk_column_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
329: ,p_class_code_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
330: ,p_user_privileges_on_object IN EGO_VARCHAR_TBL_TYPE DEFAULT NULL
331: ,p_entity_id IN NUMBER DEFAULT NULL

Line 354: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE

350: PROCEDURE Process_User_Attrs_Data (
351: p_api_version IN NUMBER
352: ,p_object_name IN VARCHAR2
353: ,p_attributes_row_table IN EGO_USER_ATTR_ROW_TABLE
354: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE
355: ,p_pk_column_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
356: ,p_class_code_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
357: ,p_user_privileges_on_object IN EGO_VARCHAR_TBL_TYPE DEFAULT NULL
358: ,p_entity_id IN NUMBER DEFAULT NULL

Line 385: * a corresponding EGO_USER_ATTR_DATA_TABLE (both of which are described

381: * as well as an EGO_ATTR_GROUP_REQUEST_TABLE (described above) specifying
382: * the data to fetch. The procedure fetches the requested data from the
383: * database (transforming internal values to display values as necessary)
384: * and returns it in the form of two tables: an EGO_USER_ATTR_ROW_TABLE and
385: * a corresponding EGO_USER_ATTR_DATA_TABLE (both of which are described
386: * above).
387: * Current version: 1.0
388: *
389: * @param p_api_version Pass the value listed as 'Current version' above.

Line 460: ,x_attributes_data_table OUT NOCOPY EGO_USER_ATTR_DATA_TABLE

456: ,p_init_fnd_msg_list IN VARCHAR2 DEFAULT FND_API.G_FALSE
457: ,p_add_errors_to_fnd_stack IN VARCHAR2 DEFAULT FND_API.G_FALSE
458: ,p_commit IN VARCHAR2 DEFAULT FND_API.G_FALSE
459: ,x_attributes_row_table OUT NOCOPY EGO_USER_ATTR_ROW_TABLE
460: ,x_attributes_data_table OUT NOCOPY EGO_USER_ATTR_DATA_TABLE
461: ,x_return_status OUT NOCOPY VARCHAR2
462: ,x_errorcode OUT NOCOPY NUMBER
463: ,x_msg_count OUT NOCOPY NUMBER
464: ,x_msg_data OUT NOCOPY VARCHAR2