DBA Data[Home] [Help]

APPS.AME_UTIL dependencies on WF_CORE

Line 4093: which will let us order the call stack in our admin UI. The call to wf_core.context

4089: The wf_item_activity_statuses_v.error_name and error_message columns store the exception.
4090: The query against that view is per item type, which should be the
4091: ame_calling_aps.transaction_type_id, and per item key, which should be the transaction ID
4092: in the OAM schema and code. So all we need is the package name, routine name, and log ID,
4093: which will let us order the call stack in our admin UI. The call to wf_core.context
4094: puts the package name in upper case to make the query against wf_item_activity_statuses_v
4095: easier (comparing 'AME%' without having to uppercase anything in the query).
4096: */
4097: wf_core.context(pkg_name => upper(packageNameIn),

Line 4097: wf_core.context(pkg_name => upper(packageNameIn),

4093: which will let us order the call stack in our admin UI. The call to wf_core.context
4094: puts the package name in upper case to make the query against wf_item_activity_statuses_v
4095: easier (comparing 'AME%' without having to uppercase anything in the query).
4096: */
4097: wf_core.context(pkg_name => upper(packageNameIn),
4098: proc_name => routineNameIn,
4099: arg1 => logId);
4100: end if;
4101: exception