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.AP_DRILLDOWN_PUB_PKG dependencies on XLA_EVENTS_PUB_PKG

Line 45: ) RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

41: ( p_legal_entity_id IN NUMBER,
42: p_ledger_id IN NUMBER,
43: p_invoice_id IN NUMBER,
44: p_calling_sequence IN VARCHAR2
45: ) RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;
46:
47: /*---------------------------------------------------------------
48: |Private procedure: get_payment_event_source_info
49: +---------------------------------------------------------------*/

Line 55: ) RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

51: ( p_legal_entity_id IN NUMBER,
52: p_ledger_id IN NUMBER,
53: p_check_id IN NUMBER,
54: p_calling_sequence IN VARCHAR2
55: ) RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;
56:
57: /*========================================================================
58: | PROCEDURE: DRILLDOWN
59: | COMMENT: DRILLDOWN procedure provides a public API for sla to return

Line 245: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

241:
242: l_org_id NUMBER(15);
243: l_legal_entity_id NUMBER(15);
244: l_ledger_id NUMBER(15);
245: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;
246: l_accounting_mode VARCHAR2(1);
247: l_accounting_flag VARCHAR2(1);
248: l_gl_posting_flag VARCHAR2(1);
249: l_transfer_flag VARCHAR2(1);

Line 257: l_t_array_event_info xla_events_pub_pkg.t_array_event_info;

253: l_log_msg FND_LOG_MESSAGES.MESSAGE_TEXT%TYPE;
254:
255: ind BINARY_INTEGER := 1;
256: l_event_list t_event_ids_type;
257: l_t_array_event_info xla_events_pub_pkg.t_array_event_info;
258: l_procedure_name CONSTANT VARCHAR2(30) := 'invoice_online_accounting';
259:
260: BEGIN
261:

Line 342: l_t_array_event_info := xla_events_pub_pkg.get_array_event_info

338:
339:
340: IF ( l_accounting_mode <> 'D' AND p_retcode <> 0 ) THEN
341:
342: l_t_array_event_info := xla_events_pub_pkg.get_array_event_info
343: (p_event_source_info => l_event_source_info
344: ,p_event_class_code => NULL
345: ,p_event_type_code => NULL
346: ,p_event_date => NULL

Line 443: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

439:
440: l_org_id NUMBER(15);
441: l_legal_entity_id NUMBER(15);
442: l_ledger_id NUMBER(15);
443: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;
444: l_accounting_mode VARCHAR2(1);
445: l_accounting_flag VARCHAR2(1);
446: l_gl_posting_flag VARCHAR2(1);
447: l_transfer_flag VARCHAR2(1);

Line 455: l_t_array_event_info xla_events_pub_pkg.t_array_event_info;

451: l_log_msg FND_LOG_MESSAGES.MESSAGE_TEXT%TYPE;
452:
453: ind BINARY_INTEGER := 1;
454: l_event_list t_event_ids_type;
455: l_t_array_event_info xla_events_pub_pkg.t_array_event_info;
456: l_procedure_name CONSTANT VARCHAR2(30) := 'payment_online_accounting';
457:
458:
459: BEGIN

Line 541: l_t_array_event_info := xla_events_pub_pkg.get_array_event_info

537: -- When payment accounting option is CLEAR ONLY, need to set the
538: -- posted_flag to 'Y' for payment create and maturity event after online
539: -- accounting
540:
541: l_t_array_event_info := xla_events_pub_pkg.get_array_event_info
542: (p_event_source_info => l_event_source_info
543: ,p_event_class_code => NULL
544: ,p_event_type_code => NULL
545: ,p_event_date => NULL

Line 644: | RETURN: XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO

Line 659: RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO

655: p_legal_entity_id IN NUMBER,
656: p_ledger_id IN NUMBER,
657: p_invoice_id IN NUMBER,
658: p_calling_sequence IN VARCHAR2)
659: RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO
660: IS
661:
662: l_invoice_num VARCHAR2(50);
663: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

Line 663: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

659: RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO
660: IS
661:
662: l_invoice_num VARCHAR2(50);
663: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;
664: l_curr_calling_sequence VARCHAR2(2000);
665: l_log_msg FND_LOG_MESSAGES.MESSAGE_TEXT%TYPE;
666:
667: BEGIN

Line 723: | RETURN: XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO

Line 738: RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO

734: p_legal_entity_id IN NUMBER,
735: p_ledger_id IN NUMBER,
736: p_check_id IN NUMBER,
737: p_calling_sequence IN VARCHAR2)
738: RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO
739: IS
740:
741: l_check_number NUMBER(15);
742: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

Line 742: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;

738: RETURN XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO
739: IS
740:
741: l_check_number NUMBER(15);
742: l_event_source_info XLA_EVENTS_PUB_PKG.T_EVENT_SOURCE_INFO;
743: l_curr_calling_sequence VARCHAR2(2000);
744: l_log_msg FND_LOG_MESSAGES.MESSAGE_TEXT%TYPE;
745:
746: BEGIN