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.MTL_ABC_COMPILE_PKG dependencies on STANDARD

Line 52: --GSCC File.Date.5 standard. Bug:4410902

48: AND C1.CALENDAR_CODE = x_cal_code
49: AND C1.EXCEPTION_SET_ID = x_except_id
50: AND ( C1.CALENDAR_DATE >= F.FORECAST_DATE
51: --Added format mask while using to_date function to comply with
52: --GSCC File.Date.5 standard. Bug:4410902
53: -- Bug# 6819570, replaced the to_date function used earlier with
54: -- FND_DATE.canonical_to_date which does not require format mask,
55: -- hence avoiding ORA-01861 'literal does not match format string' error.
56: AND C1.CALENDAR_DATE >= FND_DATE.canonical_to_date(x_start_date)

Line 91: --GSCC File.Date.5 standard. Bug:4410902

87: AND W1.EXCEPTION_SET_ID = x_except_id
88: AND (W1.WEEK_START_DATE >= F.FORECAST_DATE
89: AND W1.WEEK_START_DATE <= NVL(F.RATE_END_DATE, F.FORECAST_DATE))
90: --Added format mask while using to_date function to comply with
91: --GSCC File.Date.5 standard. Bug:4410902
92: -- Bug# 6819570, replaced the to_date function used earlier with
93: -- FND_DATE.canonical_to_date which does not require format mask,
94: -- hence avoiding ORA-01861 'literal does not match format string' error.
95: AND W1.NEXT_DATE > FND_DATE.canonical_to_date(x_start_date)

Line 106: --GSCC File.Date.5 standard. Bug:4410902

102: AND C3.CALENDAR_DATE= W1.WEEK_START_DATE
103: AND C2.CALENDAR_DATE = W1.NEXT_DATE
104: AND (C1.CALENDAR_DATE >= C3.CALENDAR_DATE
105: --Added format mask while using to_date function to comply with
106: --GSCC File.Date.5 standard. Bug:4410902
107: -- Bug# 6819570, replaced the to_date function used earlier with
108: -- FND_DATE.canonical_to_date which does not require format mask,
109: -- hence avoiding ORA-01861 'literal does not match format string' error.
110: AND C1.CALENDAR_DATE >= FND_DATE.canonical_to_date(x_start_date)

Line 147: --GSCC File.Date.5 standard. Bug:4410902

143: AND W1.EXCEPTION_SET_ID = x_except_id
144: AND (W1.PERIOD_START_DATE >= F.FORECAST_DATE
145: AND W1.PERIOD_START_DATE <= NVL(F.RATE_END_DATE, F.FORECAST_DATE))
146: --Added format mask while using to_date function to comply with
147: --GSCC File.Date.5 standard. Bug:4410902
148: -- Bug# 6819570, replaced the to_date function used earlier with
149: -- FND_DATE.canonical_to_date which does not require format mask,
150: -- hence avoiding ORA-01861 'literal does not match format string' error.
151: AND W1.NEXT_DATE > FND_DATE.canonical_to_date(x_start_date)

Line 162: --GSCC File.Date.5 standard. Bug:4410902

158: AND C3.CALENDAR_DATE= W1.PERIOD_START_DATE
159: AND C2.CALENDAR_DATE = W1.NEXT_DATE
160: AND (C1.CALENDAR_DATE >= C3.CALENDAR_DATE
161: --Added format mask while using to_date function to comply with
162: --GSCC File.Date.5 standard. Bug:4410902
163: -- Bug# 6819570, replaced the to_date function used earlier with
164: -- FND_DATE.canonical_to_date which does not require format mask,
165: -- hence avoiding ORA-01861 'literal does not match format string' error.
166: AND C1.CALENDAR_DATE >= FND_DATE.canonical_to_date(x_start_date)

Line 169: --GSCC File.Date.5 standard. Bug:4410902

165: -- hence avoiding ORA-01861 'literal does not match format string' error.
166: AND C1.CALENDAR_DATE >= FND_DATE.canonical_to_date(x_start_date)
167: AND C1.CALENDAR_DATE = C1.NEXT_DATE
168: --Added format mask while using to_date function to comply with
169: --GSCC File.Date.5 standard. Bug:4410902
170: -- Bug# 6819570, replaced the to_date function used earlier with
171: -- FND_DATE.canonical_to_date which does not require format mask,
172: -- hence avoiding ORA-01861 'literal does not match format string' error.
173: AND C1.CALENDAR_DATE <= FND_DATE.canonical_to_date(x_cutoff_date)