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.POA_DBI_UTIL_PKG dependencies on BIS_QUERY_ATTRIBUTES_TBL

Line 217: , x_custom_output out nocopy bis_query_attributes_tbl

213:
214: PROCEDURE get_custom_trend_binds
215: ( p_xtd in varchar2
216: , p_comparison_type in varchar2
217: , x_custom_output out nocopy bis_query_attributes_tbl
218: , p_opening_balance in varchar2 := 'N'
219: );
220:
221: PROCEDURE get_custom_status_binds(x_custom_output IN OUT NOCOPY BIS_QUERY_ATTRIBUTES_TBL);

Line 221: PROCEDURE get_custom_status_binds(x_custom_output IN OUT NOCOPY BIS_QUERY_ATTRIBUTES_TBL);

217: , x_custom_output out nocopy bis_query_attributes_tbl
218: , p_opening_balance in varchar2 := 'N'
219: );
220:
221: PROCEDURE get_custom_status_binds(x_custom_output IN OUT NOCOPY BIS_QUERY_ATTRIBUTES_TBL);
222:
223: FUNCTION get_trend_lag(p_xtd IN varchar2, p_comparison_type IN varchar2) return number;
224:
225: -- get_report_start_date function returns the BIS bind variable

Line 233: -- get_custom_balance_binds procedure updates the bis_query_attributes_tbl

229: , p_prior varchar2 := 'N'
230: )
231: return varchar2;
232:
233: -- get_custom_balance_binds procedure updates the bis_query_attributes_tbl
234: -- with the bind variables/values needed for balance reports
235: PROCEDURE get_custom_balance_binds
236: ( p_custom_output in out nocopy bis_query_attributes_tbl
237: , p_balance_fact in varchar2

Line 236: ( p_custom_output in out nocopy bis_query_attributes_tbl

232:
233: -- get_custom_balance_binds procedure updates the bis_query_attributes_tbl
234: -- with the bind variables/values needed for balance reports
235: PROCEDURE get_custom_balance_binds
236: ( p_custom_output in out nocopy bis_query_attributes_tbl
237: , p_balance_fact in varchar2
238: , p_xtd in varchar2 := null
239: );
240:

Line 241: -- get_custom_rolling_binds procedure updates the bis_query_attributes_tbl

237: , p_balance_fact in varchar2
238: , p_xtd in varchar2 := null
239: );
240:
241: -- get_custom_rolling_binds procedure updates the bis_query_attributes_tbl
242: -- with the bind variables/values needed for rolling period reports
243: -- will be unnecessary when fii/bis provide this functionality.
244: PROCEDURE get_custom_rolling_binds
245: ( p_custom_output in out nocopy bis_query_attributes_tbl

Line 245: ( p_custom_output in out nocopy bis_query_attributes_tbl

241: -- get_custom_rolling_binds procedure updates the bis_query_attributes_tbl
242: -- with the bind variables/values needed for rolling period reports
243: -- will be unnecessary when fii/bis provide this functionality.
244: PROCEDURE get_custom_rolling_binds
245: ( p_custom_output in out nocopy bis_query_attributes_tbl
246: , p_xtd in varchar2
247: );
248:
249: procedure bind_low_high

Line 255: , p_custom_output in out nocopy bis_query_attributes_tbl

251: , p_short_name in varchar2
252: , p_dim_level in varchar2
253: , p_low in varchar2
254: , p_high in varchar2
255: , p_custom_output in out nocopy bis_query_attributes_tbl
256: );
257:
258: -- Procedure to seed Bind variables for day level reporting
259: PROCEDURE get_custom_day_binds(p_custom_output IN OUT NOCOPY BIS_QUERY_ATTRIBUTES_TBL,

Line 259: PROCEDURE get_custom_day_binds(p_custom_output IN OUT NOCOPY BIS_QUERY_ATTRIBUTES_TBL,

255: , p_custom_output in out nocopy bis_query_attributes_tbl
256: );
257:
258: -- Procedure to seed Bind variables for day level reporting
259: PROCEDURE get_custom_day_binds(p_custom_output IN OUT NOCOPY BIS_QUERY_ATTRIBUTES_TBL,
260: p_as_of_date IN DATE,
261: p_comparison_type IN VARCHAR2);
262:
263: FUNCTION get_in_supplier_sec_where(p_supplier_value IN VARCHAR2) RETURN VARCHAR2;