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 241: * EGO_USER_ATTR_DATA_TABLE (described above). The procedure organizes

237: /*#
238: * Processes User-Defined Attribute data for one object instance.
239: * Parameters provide identifying data and metadata for an object
240: * instance, along with an EGO_USER_ATTR_ROW_TABLE and an accompanying
241: * EGO_USER_ATTR_DATA_TABLE (described above). The procedure organizes
242: * the data from the two tables and calls Process_Row for each distinct
243: * attribute group row passing all the attribute data for that row.
244: * Current version: 1.0
245: *

Line 318: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE

314: PROCEDURE Process_User_Attrs_Data (
315: p_api_version IN NUMBER
316: ,p_object_name IN VARCHAR2
317: ,p_attributes_row_table IN EGO_USER_ATTR_ROW_TABLE
318: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE
319: ,p_pk_column_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
320: ,p_class_code_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
321: ,p_user_privileges_on_object IN EGO_VARCHAR_TBL_TYPE DEFAULT NULL
322: ,p_entity_id IN NUMBER DEFAULT NULL

Line 345: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE

341: PROCEDURE Process_User_Attrs_Data (
342: p_api_version IN NUMBER
343: ,p_object_name IN VARCHAR2
344: ,p_attributes_row_table IN EGO_USER_ATTR_ROW_TABLE
345: ,p_attributes_data_table IN EGO_USER_ATTR_DATA_TABLE
346: ,p_pk_column_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
347: ,p_class_code_name_value_pairs IN EGO_COL_NAME_VALUE_PAIR_ARRAY
348: ,p_user_privileges_on_object IN EGO_VARCHAR_TBL_TYPE DEFAULT NULL
349: ,p_entity_id IN NUMBER DEFAULT NULL

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

372: * as well as an EGO_ATTR_GROUP_REQUEST_TABLE (described above) specifying
373: * the data to fetch. The procedure fetches the requested data from the
374: * database (transforming internal values to display values as necessary)
375: * and returns it in the form of two tables: an EGO_USER_ATTR_ROW_TABLE and
376: * a corresponding EGO_USER_ATTR_DATA_TABLE (both of which are described
377: * above).
378: * Current version: 1.0
379: *
380: * @param p_api_version Pass the value listed as 'Current version' above.

Line 451: ,x_attributes_data_table OUT NOCOPY EGO_USER_ATTR_DATA_TABLE

447: ,p_init_fnd_msg_list IN VARCHAR2 DEFAULT FND_API.G_FALSE
448: ,p_add_errors_to_fnd_stack IN VARCHAR2 DEFAULT FND_API.G_FALSE
449: ,p_commit IN VARCHAR2 DEFAULT FND_API.G_FALSE
450: ,x_attributes_row_table OUT NOCOPY EGO_USER_ATTR_ROW_TABLE
451: ,x_attributes_data_table OUT NOCOPY EGO_USER_ATTR_DATA_TABLE
452: ,x_return_status OUT NOCOPY VARCHAR2
453: ,x_errorcode OUT NOCOPY NUMBER
454: ,x_msg_count OUT NOCOPY NUMBER
455: ,x_msg_data OUT NOCOPY VARCHAR2