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.GMICCAL dependencies on IC_PERD_BAL

Line 311: delete_ic_perd_bal

307: RETURN SQLCODE;
308: END trans_date_validate;
309: /* =============================================
310: FUNCTION:
311: delete_ic_perd_bal
312:
313: DESCRIPTION:
314: This PL/SQL function is responsible for
315: deleting rows from the ic_perd_bal in conjuction

Line 315: deleting rows from the ic_perd_bal in conjuction

311: delete_ic_perd_bal
312:
313: DESCRIPTION:
314: This PL/SQL function is responsible for
315: deleting rows from the ic_perd_bal in conjuction
316: with the rerunning of a preliminary close.
317:
318: SYNOPSIS:
319: iret := GMICCAL.delete_ic_perd_bal(pfiscal_yr, pperiod,

Line 319: iret := GMICCAL.delete_ic_perd_bal(pfiscal_yr, pperiod,

315: deleting rows from the ic_perd_bal in conjuction
316: with the rerunning of a preliminary close.
317:
318: SYNOPSIS:
319: iret := GMICCAL.delete_ic_perd_bal(pfiscal_yr, pperiod,
320: pwhse_code);
321:
322: pfiscal_yr - The fiscal year for the Calendar.
323: pperiod - The period within the Fiscal year.

Line 331: delete_ic_perd_bal was missing a return value.

327: 0 Success
328:
329: HISTORY:
330: M Petrosino 25-Mar-1999 B859062
331: delete_ic_perd_bal was missing a return value.
332: added return 0 to function.
333: ============================================= */
334: FUNCTION delete_ic_perd_bal(pfiscal_year VARCHAR2,
335: pperiod NUMBER,

Line 334: FUNCTION delete_ic_perd_bal(pfiscal_year VARCHAR2,

330: M Petrosino 25-Mar-1999 B859062
331: delete_ic_perd_bal was missing a return value.
332: added return 0 to function.
333: ============================================= */
334: FUNCTION delete_ic_perd_bal(pfiscal_year VARCHAR2,
335: pperiod NUMBER,
336: pwhse_code VARCHAR2)
337: RETURN NUMBER IS
338:

Line 342: DELETE from ic_perd_bal

338:
339: /* ========================================*/
340: BEGIN
341:
342: DELETE from ic_perd_bal
343: WHERE fiscal_year = UPPER(pfiscal_year)
344: AND period = pperiod
345: AND whse_code = UPPER(pwhse_code);
346:

Line 359: END delete_ic_perd_bal;

355:
356: EXCEPTION
357: WHEN OTHERS THEN
358: RETURN SQLCODE;
359: END delete_ic_perd_bal;
360: /* =============================================
361: FUNCTION:
362: insert_ic_perd_bal
363:

Line 362: insert_ic_perd_bal

358: RETURN SQLCODE;
359: END delete_ic_perd_bal;
360: /* =============================================
361: FUNCTION:
362: insert_ic_perd_bal
363:
364: DESCRIPTION:
365: This PL/SQL function is responsible for
366: inserting rows from the ic_perd_bal in conjuction

Line 366: inserting rows from the ic_perd_bal in conjuction

362: insert_ic_perd_bal
363:
364: DESCRIPTION:
365: This PL/SQL function is responsible for
366: inserting rows from the ic_perd_bal in conjuction
367: with the running of a preliminary or Final close.
368: This is the initial seeding of this table.
369:
370: SYNOPSIS:

Line 371: iret := GMICCAL.insert_ic_perd_bal(pwhse_code);

367: with the running of a preliminary or Final close.
368: This is the initial seeding of this table.
369:
370: SYNOPSIS:
371: iret := GMICCAL.insert_ic_perd_bal(pwhse_code);
372:
373: pfiscal_year - Fiscal Year of Calendar.
374: pper_id - Period ID surrogate of period within
375: calendar.

Line 384: FUNCTION insert_ic_perd_bal(pfiscal_year VARCHAR2,

380: RETURNS:
381: < 0 Oracle RDBMS error.
382: >= 0 The number of rows inserted.
383: ============================================= */
384: FUNCTION insert_ic_perd_bal(pfiscal_year VARCHAR2,
385: pper_id NUMBER,
386: pperiod NUMBER,
387: pwhse_code VARCHAR2,
388: pop_code NUMBER)

Line 394: INSERT INTO ic_perd_bal

390:
391: /* ========================================*/
392: BEGIN
393:
394: INSERT INTO ic_perd_bal
395: (perd_bal_id, gl_posted_ind, period_id, fiscal_year, --bug#2230683
396: period, item_id, lot_id,
397: whse_code, location, loct_onhand, loct_onhand2,
398: loct_usage, loct_usage2, loct_yield, loct_yield2,

Line 418: END insert_ic_perd_bal;

414: EXCEPTION
415: WHEN OTHERS THEN
416:
417: RETURN SQLCODE;
418: END insert_ic_perd_bal;
419: /* =============================================
420: FUNCTION:
421: calc_usage_yield
422:

Line 540: results to the ic_perd_bal table.

536: LOOP
537: /* This first condition checks to see if something
538: has changed or we do not have anymore rows. If
539: this condition is true, it is time to write our
540: results to the ic_perd_bal table.
541: =============================================== */
542: IF (l_prev_item_id <> l_item_id OR
543: l_prev_lot_id <> l_lot_id OR
544: l_prev_location <> l_location OR

Line 553: UPDATE ic_perd_bal

549: let's grab what we accumulated and update
550: the perpetual balances for this item, lot,
551: and location.
552: =========================================== */
553: UPDATE ic_perd_bal
554: SET loct_onhand = loct_onhand - ROUND(l_delta_qty, 9),
555: loct_onhand2 = loct_onhand2 - ROUND(l_delta_qty2, 9),
556: loct_usage = ROUND(l_usage_qty, 9),
557: loct_usage2 = ROUND(l_usage_qty2, 9),

Line 575: INSERT INTO ic_perd_bal

571: /* This could be because of a 'PURGE EMPTY BALANCES'
572: was run on this particular item. Therefore, the
573: row does not exist so we have to insert it!
574: ================================================*/
575: INSERT INTO ic_perd_bal
576: (perd_bal_id, gl_posted_ind, period_id, lot_id, --bug#2230683
577: whse_code, location, item_id,
578: fiscal_year, period, loct_onhand, loct_onhand2,
579: loct_usage, loct_usage2, loct_yield, loct_yield2,