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.AK_DEFAULT_VALIDATE dependencies on AK_OBJECT_ATTRIBUTES

Line 21: ak_object_attributes aoa

17: CURSOR l_object_api_csr(db_obj_name VARCHAR2) IS
18: select count(*)
19: from
20: ak_objects ao,
21: ak_object_attributes aoa
22: where
23: ao.database_object_name = db_obj_name and
24: aoa.database_object_name = db_obj_name and
25: ((ao.defaulting_api_pkg is not null and

Line 132: -- attributes from ak_object_attributes. If REGION then we get the attributes

128:
129: -- Yes, Yes, it's a kludge -- but it works well thank you. Based upon the
130: -- above input parameters, either the top or bottom select statement will
131: -- return rows, but not both. If the P_package_type is OBJECT then we get
132: -- attributes from ak_object_attributes. If REGION then we get the attributes
133: -- from ak_region_items. This allows the following program to reference
134: -- only one cursor for both types.
135: CURSOR l_csr( db_obj_name VARCHAR2,
136: db_reg_id NUMBER,

Line 142: from ak_object_attributes aoa,

138: select aa.attribute_application_id,
139: aa.attribute_code,
140: aa.data_type,
141: aa.attribute_value_length
142: from ak_object_attributes aoa,
143: ak_attributes aa
144: where aoa.database_object_name = db_obj_name and
145: aoa.attribute_application_id = aa.attribute_application_id and
146: aoa.attribute_code = aa.attribute_code