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.GMICVAL dependencies on GMICVAL

Line 1: PACKAGE BODY GMICVAL AS

1: PACKAGE BODY GMICVAL AS
2: /* $Header: gmicvalb.pls 115.6 2004/04/30 17:40:42 adeshmuk ship $ */
3: /* =============================================
4: PROCEDURE:
5: trans_date_val

Line 2: /* $Header: gmicvalb.pls 115.6 2004/04/30 17:40:42 adeshmuk ship $ */

1: PACKAGE BODY GMICVAL AS
2: /* $Header: gmicvalb.pls 115.6 2004/04/30 17:40:42 adeshmuk ship $ */
3: /* =============================================
4: PROCEDURE:
5: trans_date_val
6:

Line 13: iret := GMICVAL.trans_date_val(ptrans_date,

9: validating that a transaction date is in
10: an open warehouse and inventory calendar period.
11:
12: SYNOPSIS:
13: iret := GMICVAL.trans_date_val(ptrans_date,
14: porgn_code, pwhse_code);
15:
16: ptrans_date - transaction date
17: porgn_code - organization associated to the warehouse.

Line 91: GMICVAL.deviation_val(pitem_id, plot_id, pcur_qty,

87: contained in this package and handling all
88: error messaging centrally.
89:
90: SYNOPSIS:
91: GMICVAL.deviation_val(pitem_id, plot_id, pcur_qty,
92: pcur_uom, pnew_qty, pnew_uom);
93:
94: ============================================= */
95: PROCEDURE deviation_val(pitem_id NUMBER,

Line 124: l_iret := GMICVAL.dev_validation(pitem_id, plot_id, l_cur_qty,

120: END IF;
121:
122: l_new_qty := pnew_qty;
123:
124: l_iret := GMICVAL.dev_validation(pitem_id, plot_id, l_cur_qty,
125: pcur_uom, l_new_qty, pnew_uom, l_atomic);
126:
127: IF(l_iret = -68) THEN
128: FND_MESSAGE.set_name('GMI', 'IC_DEVIATION_HI_ERR');

Line 155: iret := GMICVAL.location_validation(plocation,

151: =============================
152: item2 | 0 | 2 | 2
153:
154: SYNOPSIS:
155: iret := GMICVAL.location_validation(plocation,
156: pwhse_code,ploct_ctl);
157:
158: plocation - location to be validated
159: pwhse_code - warehouse where the location resides.

Line 183: l_iret := GMICVAL.itm_location_val(plocation,

179: l_iret NUMBER := -1;
180:
181: BEGIN
182:
183: l_iret := GMICVAL.itm_location_val(plocation,
184: pwhse_code, ploct_ctl);
185:
186: IF (l_iret = -62) THEN
187: FND_MESSAGE.set_name('GMI', 'IC_LOCATION_ERR');

Line 225: iret := GMICVAL.item_val(pitem_id);

221: The second way to call this validation is
222: by item_no. See below function.
223:
224: SYNOPSIS:
225: iret := GMICVAL.item_val(pitem_id);
226:
227: pitem_id the item surrogate of the item you
228: are validating.
229:

Line 291: iret := GMICVAL.item_val(pitem_no);

287: The second way to call this validation is
288: by item_id. See above function.
289:
290: SYNOPSIS:
291: iret := GMICVAL.item_val(pitem_no);
292:
293: pitem_no the item number of the item you
294: are validating.
295:

Line 354: iret := GMICVAL.reason_code_val(preason_code);

350: This PL/SQL function is responsible for
351: validating valid reason codes.
352:
353: SYNOPSIS:
354: iret := GMICVAL.reason_code_val(preason_code);
355:
356: preason_code the reason code you are working on.
357:
358: RETURNS:

Line 414: iret := GMICVAL.itm_location_val(plocation, pwhse_code,

410: This PL/SQL function is responsible for
411: validating an items inventory location.
412:
413: SYNOPSIS:
414: iret := GMICVAL.itm_location_val(plocation, pwhse_code,
415: ploct_ctl);
416:
417: plocation the location you are working on.
418: pwhse_code the warehouse associated with the location.

Line 583: iret := GMICVAL.whse_location_val(porgn_code, pwhse_code,

579: This PL/SQL function is responsible for
580: validating an location in a particular warehouse.
581:
582: SYNOPSIS:
583: iret := GMICVAL.whse_location_val(porgn_code, pwhse_code,
584: plocation);
585:
586: porgn_code the organization associated to the whse.
587: pwhse_code the warehouse associated with the location.

Line 705: iret := GMICVAL.grade_val(pqc_grade);

701: This PL/SQL function is responsible for
702: validating an item's QC grade.
703:
704: SYNOPSIS:
705: iret := GMICVAL.grade_val(pqc_grade);
706:
707: pqc_grade the QC grade of an item.
708:
709: RETURNS:

Line 767: iret := GMICVAL.lot_status_val(plot_status);

763: validating the lot status of a lot controlled
764: and lot status controlled item.
765:
766: SYNOPSIS:
767: iret := GMICVAL.lot_status_val(plot_status);
768:
769: pclot_status the Lot Status of the item.
770:
771: RETURNS:

Line 828: iret := GMICVAL.whse_val(pwhse_code, porgn_code);

824: This PL/SQL function is responsible for
825: validating valid warehouse codes.
826:
827: SYNOPSIS:
828: iret := GMICVAL.whse_val(pwhse_code, porgn_code);
829:
830: pwhse_code the warehouse code you are working on.
831: porgn_code The organization associated with the
832: warehouse being validated.

Line 898: iret := GMICVAL.lot_validate(pitem_no, plot_no, psublot_no);

894: validating valid lot surrogates, lot numbers,
895: sulot numbers or combinations.
896:
897: SYNOPSIS:
898: iret := GMICVAL.lot_validate(pitem_no, plot_no, psublot_no);
899:
900: pitem_no the item number are working on.
901: plot_no the lot number you want to validate.
902: psublot_no the sublot number you want to validate.

Line 1042: iret := GMICVAL.lot_validate(pitem_no, plot_no, psublot_no);

1038: validating valid lot surrogates, lot numbers,
1039: sulot numbers or combinations.
1040:
1041: SYNOPSIS:
1042: iret := GMICVAL.lot_validate(pitem_no, plot_no, psublot_no);
1043:
1044: pitem_no the item number are working on.
1045: plot_no the lot number you want to validate.
1046: psublot_no the sublot number you want to validate.

Line 1138: iret := GMICVAL.co_code_val(porgn_code);

1134: validating that an organization passed is
1135: a company.
1136:
1137: SYNOPSIS:
1138: iret := GMICVAL.co_code_val(porgn_code);
1139:
1140: porgn_code the organization code you are working on.
1141:
1142: RETURNS:

Line 1206: iret := GMICVAL.orgn_code_val(porgn_code);

1202: This PL/SQL function is responsible for
1203: validating organizations.
1204:
1205: SYNOPSIS:
1206: iret := GMICVAL.orgn_code_val(porgn_code);
1207:
1208: porgn_code the orgn_code you are working on.
1209:
1210: RETURNS:

Line 1273: iret := GMICVAL.uomcode_val(puom_code);

1269: This PL/SQL function is responsible for
1270: validating a unit of measure code (ie. LBS).
1271:
1272: SYNOPSIS:
1273: iret := GMICVAL.uomcode_val(puom_code);
1274:
1275: puom_code the uom code you are working on.
1276:
1277: RETURNS:

Line 1416: l_iret := GMICVAL.det_dualum_ind(pitem_id);

1412: /* ============================================
1413: OK .... first let's go out and grab the
1414: required attributes we need for the item.
1415: ============================================ */
1416: l_iret := GMICVAL.det_dualum_ind(pitem_id);
1417:
1418: IF(l_iret < -1) THEN
1419: RETURN l_iret;
1420: ELSIF(l_iret = -1) THEN

Line 1453: l_iret := GMICVAL.calc_deviation(pitem_id, ptrans_qty2,

1449: low boundary, we have an error!
1450: ====================================================== */
1451: l_converted_qty := l_iret;
1452: l_iret := -1;
1453: l_iret := GMICVAL.calc_deviation(pitem_id, ptrans_qty2,
1454: l_converted_qty);
1455:
1456: IF(l_iret = VAL_CALCDEV_HIGH_ERR) THEN
1457: RETURN l_iret;

Line 1481: iret := GMICVAL.det_dualum_ind(pitem_id);

1477: returning the dual unit of measure indicator
1478: of an item.
1479:
1480: SYNOPSIS:
1481: iret := GMICVAL.det_dualum_ind(pitem_id);
1482:
1483: pitem_id the item surrogate you are working on.
1484: iodualum_ind The dual UOM indicator of the item.
1485: Valid values are:

Line 1554: iret := GMICVAL.calc_deviation(pitem_id, ptrans_qty2,

1550: is within the allowable deviation + or -
1551: of an item.
1552:
1553: SYNOPSIS:
1554: iret := GMICVAL.calc_deviation(pitem_id, ptrans_qty2,
1555: pconverted_qty);
1556:
1557: pitem_id the item surrogate you are working on.
1558: ptrans_qty2 the secondary quantity entered by the user.