DBA Data[Home] [Help]

APPS.AR_UPGHARNESS_PKG dependencies on GL_PERIOD_STATUSES

Line 93: FROM gl_period_statuses gps

89: SELECT application_id,
90: ledger_id,
91: period_name,
92: period_year
93: FROM gl_period_statuses gps
94: WHERE gps.migration_status_code = 'P'
95: AND gps.application_id (+) = 222;
96: l_status VARCHAR2(1);
97: l_not_complete VARCHAR2(1);

Line 103: -- All requests end NORMAL - Update GL period statuses

99: BEGIN
100: OPEN c;
101: FETCH c INTO l_not_complete;
102: IF c%NOTFOUND THEN
103: -- All requests end NORMAL - Update GL period statuses
104: FOR l_update_gl_periods IN update_gl_periods LOOP
105: l_status := xla_upgrade_pub.set_migration_status_code
106: ( 222,
107: l_update_gl_periods.ledger_id,

Line 116: --Some requests ended with WARNING or ERROR - Do not update the GL period Statuses

112: END IF;
113: COMMIT;
114: END LOOP;
115: ELSE
116: --Some requests ended with WARNING or ERROR - Do not update the GL period Statuses
117: -- So that the next run processes them
118: NULL;
119: END IF;
120: CLOSE c;

Line 2108: --Update GL PERIOD STATUSES with XLA api

2104: update_req_control
2105: (p_request_control_id => l_xla_upg_rec.request_control_id,
2106: p_status => 'S');
2107:
2108: --Update GL PERIOD STATUSES with XLA api
2109: update_gl_period;
2110: ELSE
2111: retcode := '-2';
2112: