DBA Data[Home] [Help]

APPS.POS_VENDOR_PUB_PKG dependencies on HZ_PARTIES

Line 451: l_party_id HZ_PARTIES.PARTY_ID%TYPE;

447: Added following varirables to build the message with bind variables.*/
448: l_segment1 AP_SUPPLIERS.SEGMENT1%TYPE;
449: l_vendor_id AP_SUPPLIERS.VENDOR_ID%TYPE;
450: l_vendor_name AP_SUPPLIERS.VENDOR_NAME%TYPE;
451: l_party_id HZ_PARTIES.PARTY_ID%TYPE;
452: event_id Number;
453: BEGIN
454:
455: savepoint crt_vndr_a;

Line 3163: -- with the exception of hardcoding the object name HZ_PARTIES which

3159: ) IS
3160: --
3161: -- This version of EGO's UDA Process User Attributes Data API is
3162: -- almost identical to the original version in ego_user_attrs_data_pub
3163: -- with the exception of hardcoding the object name HZ_PARTIES which
3164: -- is the only object name expected when accessing UDA for Supplier
3165: -- related entities.
3166: --
3167: -- Another minor difference is the following optional parameters. In the

Line 3201: l_object_name := 'HZ_PARTIES';

3197: l_message_type VARCHAR2(1000) := NULL;
3198:
3199: BEGIN
3200: SAVEPOINT Process_User_Attrs_Data_PUB;
3201: l_object_name := 'HZ_PARTIES';
3202: x_return_status := 'S';
3203:
3204: FOR i IN 1 .. p_attributes_row_table.count LOOP
3205: IF (p_attributes_row_table(i).data_level = 'SUPP_LEVEL') THEN

Line 3232: , p_object_id => NULL --l_object_id-- 22 for HZ_PARTIES, 87 for EGO_ITEM

3228: END LOOP;
3229:
3230: ego_user_attrs_data_pvt.Process_Row(
3231: p_api_version => p_api_version
3232: , p_object_id => NULL --l_object_id-- 22 for HZ_PARTIES, 87 for EGO_ITEM
3233: , p_object_name => l_object_name-- HZ_PARTIES/EGO_ITEM
3234: , p_attr_group_id => p_attributes_row_table(i).attr_group_id-- input
3235: , p_application_id => p_attributes_row_table(i).attr_group_app_id-- 177 for supplier, 431 for item
3236: , p_attr_group_type => p_attributes_row_table(i).attr_group_type-- POS_SUPP_PROFMGMT_GROUP/EGO_ITEMMGMT_GROUP

Line 3233: , p_object_name => l_object_name-- HZ_PARTIES/EGO_ITEM

3229:
3230: ego_user_attrs_data_pvt.Process_Row(
3231: p_api_version => p_api_version
3232: , p_object_id => NULL --l_object_id-- 22 for HZ_PARTIES, 87 for EGO_ITEM
3233: , p_object_name => l_object_name-- HZ_PARTIES/EGO_ITEM
3234: , p_attr_group_id => p_attributes_row_table(i).attr_group_id-- input
3235: , p_application_id => p_attributes_row_table(i).attr_group_app_id-- 177 for supplier, 431 for item
3236: , p_attr_group_type => p_attributes_row_table(i).attr_group_type-- POS_SUPP_PROFMGMT_GROUP/EGO_ITEMMGMT_GROUP
3237: , p_attr_group_name => p_attributes_row_table(i).attr_group_name-- input

Line 3302: -- with the exception of hardcoding the object name HZ_PARTIES which

3298: ) IS
3299: --
3300: -- This version of EGO's UDA Get User Attributes Data API is
3301: -- almost identical to the original version in ego_user_attrs_data_pub
3302: -- with the exception of hardcoding the object name HZ_PARTIES which
3303: -- is the only object name expected when accessing UDA for Supplier
3304: -- related entities.
3305: --
3306: -- Another minor difference is the following optional parameters. In the

Line 3322: p_object_name => 'HZ_PARTIES',

3318: --
3319: BEGIN
3320: ego_user_attrs_data_pub.get_user_attrs_data(
3321: p_api_version => p_api_version,
3322: p_object_name => 'HZ_PARTIES',
3323: p_pk_column_name_value_pairs => p_pk_column_name_value_pairs,
3324: p_attr_group_request_table => p_attr_group_request_table,
3325: p_user_privileges_on_object => p_user_privileges_on_object,
3326: p_entity_id => p_entity_id,