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.GMF_SUBLEDGER_PKG dependencies on GL_LEDGERS

Line 279: FROM org_organization_definitions le, gl_ledgers led,

275: mthd.default_lot_cost_type_id
276: INTO g_legal_entity_name, g_ledger_name,
277: g_cost_method_type, g_cost_type_code, g_cost_method,
278: g_default_cost_type_id
279: FROM org_organization_definitions le, gl_ledgers led,
280: cm_mthd_mst mthd, gem_lookups lk
281: WHERE le.organization_id = g_legal_entity_id
282: AND led.ledger_id = g_ledger_id
283: AND mthd.cost_type_id = g_cost_type_id

Line 303: FROM gl_ledgers gl

299: END;
300: BEGIN
301: SELECT gl.name
302: INTO g_ledger_name
303: FROM gl_ledgers gl
304: WHERE gl.ledger_id = g_ledger_id;
305: EXCEPTION
306: WHEN NO_DATA_FOUND then
307: g_log_msg := l_procedure_name || ': No data found in gl_ledgers query';

Line 307: g_log_msg := l_procedure_name || ': No data found in gl_ledgers query';

303: FROM gl_ledgers gl
304: WHERE gl.ledger_id = g_ledger_id;
305: EXCEPTION
306: WHEN NO_DATA_FOUND then
307: g_log_msg := l_procedure_name || ': No data found in gl_ledgers query';
308: IF (G_LEVEL_PROCEDURE >= G_CURRENT_RUNTIME_LEVEL ) THEN
309: FND_LOG.STRING(G_LEVEL_PROCEDURE, G_MODULE_NAME || l_procedure_name, g_log_msg);
310: END IF;
311: RAISE;

Line 1532: gl_ledgers gl,

1528: FROM org_acct_periods oap,
1529: hr_organization_information hoi,
1530: mtl_parameters mp,
1531: gmf_period_statuses gps,
1532: gl_ledgers gl,
1533: gmf_period_balances gpb
1534: WHERE gps.period_id = p_period_id
1535: AND hoi.org_information2 = gps.legal_entity_id
1536: AND hoi.org_information1 = gl.ledger_id

Line 1691: gl_ledgers gl

1687: x_inv_period
1688: FROM org_acct_periods oap,
1689: hr_organization_information hoi,
1690: gmf_period_statuses gps,
1691: gl_ledgers gl
1692: WHERE gps.period_id = l_prior_period_id
1693: AND hoi.org_information2 = gps.legal_entity_id
1694: AND hoi.org_information1 = gl.ledger_id
1695: AND oap.period_set_name = gl.period_set_name

Line 1999: FROM org_organization_definitions le, gl_ledgers led,

1995: mthd.default_lot_cost_type_id
1996: INTO g_legal_entity_name, g_ledger_name,
1997: g_cost_method_type, g_cost_type_code, g_cost_method,
1998: g_default_cost_type_id
1999: FROM org_organization_definitions le, gl_ledgers led,
2000: cm_mthd_mst mthd, gem_lookups lk
2001: WHERE le.organization_id = g_legal_entity_id
2002: AND led.ledger_id = g_ledger_id
2003: AND mthd.cost_type_id = g_cost_type_id

Line 2023: FROM gl_ledgers gl

2019: END;
2020: BEGIN
2021: SELECT gl.name
2022: INTO g_ledger_name
2023: FROM gl_ledgers gl
2024: WHERE gl.ledger_id = g_ledger_id;
2025: EXCEPTION
2026: WHEN NO_DATA_FOUND then
2027: g_log_msg := l_procedure_name || ': No data found in gl_ledgers query';

Line 2027: g_log_msg := l_procedure_name || ': No data found in gl_ledgers query';

2023: FROM gl_ledgers gl
2024: WHERE gl.ledger_id = g_ledger_id;
2025: EXCEPTION
2026: WHEN NO_DATA_FOUND then
2027: g_log_msg := l_procedure_name || ': No data found in gl_ledgers query';
2028: IF (G_LEVEL_PROCEDURE >= G_CURRENT_RUNTIME_LEVEL ) THEN
2029: FND_LOG.STRING(G_LEVEL_PROCEDURE, G_MODULE_NAME || l_procedure_name, g_log_msg);
2030: END IF;
2031: RAISE;