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.AHL_OSP_SHIPMENT_PUB dependencies on OE_ORDER_GRP

Line 502: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);

498: */
499: l_msg_count := FND_MSG_PUB.count_msg;
500: IF l_msg_count > 0 THEN
501: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
502: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);
503: END IF;
504: RAISE FND_API.G_EXC_ERROR;
505: END IF;
506:

Line 510: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed Convert_Line_Tbl, About to OE_ORDER_GRP.PROCESS_ORDER');

506:
507: -- jaramana End
508:
509: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
510: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed Convert_Line_Tbl, About to OE_ORDER_GRP.PROCESS_ORDER');
511: END IF;
512:
513: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
514: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack

Line 513: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API

509: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
510: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed Convert_Line_Tbl, About to OE_ORDER_GRP.PROCESS_ORDER');
511: END IF;
512:
513: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
514: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
515: OE_ORDER_GRP.PROCESS_ORDER(
516: p_api_version_number => 1.0,
517: p_init_msg_list => FND_API.G_TRUE,

Line 515: OE_ORDER_GRP.PROCESS_ORDER(

511: END IF;
512:
513: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
514: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
515: OE_ORDER_GRP.PROCESS_ORDER(
516: p_api_version_number => 1.0,
517: p_init_msg_list => FND_API.G_TRUE,
518: x_return_status => x_return_status,
519: x_msg_count => x_msg_count,

Line 550: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);

546: x_action_request_tbl => x_action_request_tbl );
547:
548:
549: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
550: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);
551: END IF;
552:
553: IF (x_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
554: FOR i IN 1..x_msg_count LOOP

Line 578: OE_ORDER_GRP.PROCESS_ORDER

574: Modified by jaramana on January 11, 2008 to fix the Bug 5935388/6504122
575: If success is returned by the Public API, clear the message stack to eat up any warning messages from OM API.
576: Otherwise, OAExceptionUtils.checkErrors will consider these as errors.
577: Also note that had there been any validation errors that had been accumulated we would have thrown before the call to
578: OE_ORDER_GRP.PROCESS_ORDER
579: */
580:
581: ELSIF(x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
582: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN

Line 663: warning messages generated by OE_ORDER_GRP.PROCESS_ORDER. So the shipment is created without

659: /*
660: Modified by jaramana on January 11, 2008 for fixing the Bug 5935388/6504122
661: The "Create Shipment" action passes p_init_msg_list as TRUE as it is the starting point.
662: p_init_msg_list is passed as FALSE otherwise. So the "Create Shipment" action is flushing the
663: warning messages generated by OE_ORDER_GRP.PROCESS_ORDER. So the shipment is created without
664: any errors (Warning converted to errors by OAExceptionUtils.checkErrors in the absence of
665: certain tokens).
666: */
667: Create_IB_Transaction(

Line 1008: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);

1004: */
1005: l_msg_count := FND_MSG_PUB.count_msg;
1006: IF l_msg_count > 0 THEN
1007: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
1008: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);
1009: END IF;
1010: RAISE FND_API.G_EXC_ERROR;
1011: END IF;
1012:

Line 1015: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API

1011: END IF;
1012:
1013: -- jaramana End
1014:
1015: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
1016: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
1017: OE_ORDER_GRP.PROCESS_ORDER(
1018: p_api_version_number => 1.0,
1019: p_init_msg_list => FND_API.G_TRUE,

Line 1017: OE_ORDER_GRP.PROCESS_ORDER(

1013: -- jaramana End
1014:
1015: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
1016: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
1017: OE_ORDER_GRP.PROCESS_ORDER(
1018: p_api_version_number => 1.0,
1019: p_init_msg_list => FND_API.G_TRUE,
1020: x_return_status => x_return_status,
1021: x_msg_count => x_msg_count,

Line 1075: OE_ORDER_GRP.PROCESS_ORDER

1071: Modified by jaramana on January 11, 2008 to fix the Bug 5935388/6504122
1072: If success is returned by the Public API, clear the message stack to eat up any warning messages from OM API.
1073: Otherwise, OAExceptionUtils.checkErrors will consider these as errors
1074: Also note that had there been any validation errors that had been accumulated we would have thrown before the call to
1075: OE_ORDER_GRP.PROCESS_ORDER
1076: */
1077: ELSIF(x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
1078: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
1079: FOR i IN 1..FND_MSG_PUB.count_msg LOOP

Line 1304: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);

1300: */
1301: l_msg_count := FND_MSG_PUB.count_msg;
1302: IF l_msg_count > 0 THEN
1303: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
1304: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);
1305: END IF;
1306: RAISE FND_API.G_EXC_ERROR;
1307: END IF;
1308:

Line 1309: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API

1305: END IF;
1306: RAISE FND_API.G_EXC_ERROR;
1307: END IF;
1308:
1309: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
1310: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
1311: OE_ORDER_GRP.PROCESS_ORDER(
1312: p_api_version_number => 1.0,
1313: p_init_msg_list => FND_API.G_TRUE,

Line 1311: OE_ORDER_GRP.PROCESS_ORDER(

1307: END IF;
1308:
1309: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
1310: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
1311: OE_ORDER_GRP.PROCESS_ORDER(
1312: p_api_version_number => 1.0,
1313: p_init_msg_list => FND_API.G_TRUE,
1314: x_return_status => x_return_status,
1315: x_msg_count => x_msg_count,

Line 1365: OE_ORDER_GRP.PROCESS_ORDER

1361: Modified by jaramana on January 11, 2008 to fix the Bug 5935388/6504122
1362: If success is returned by the Public API, clear the message stack to eat up any warning messages from OM API.
1363: Otherwise, OAExceptionUtils.checkErrors will consider these as errors
1364: Also note that had there been any validation errors that had been accumulated we would have thrown before the call to
1365: OE_ORDER_GRP.PROCESS_ORDER
1366: */
1367: ELSIF(x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
1368: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
1369: FOR i IN 1..FND_MSG_PUB.count_msg LOOP

Line 6226: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to OE_ORDER_GRP.PROCESS_ORDER');

6222: RAISE Fnd_Api.g_exc_error;
6223: END IF;
6224:
6225: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
6226: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to OE_ORDER_GRP.PROCESS_ORDER');
6227: END IF;
6228:
6229: l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
6230: l_line_tbl := OE_ORDER_PUB.G_MISS_LINE_TBL;

Line 6256: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API

6252: l_count := l_count + 1;
6253: END LOOP;
6254: CLOSE get_oe_order_lines;
6255:
6256: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
6257: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
6258: OE_ORDER_GRP.PROCESS_ORDER(
6259: p_api_version_number => 1.0,
6260: p_init_msg_list => FND_API.G_TRUE,

Line 6258: OE_ORDER_GRP.PROCESS_ORDER(

6254: CLOSE get_oe_order_lines;
6255:
6256: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
6257: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
6258: OE_ORDER_GRP.PROCESS_ORDER(
6259: p_api_version_number => 1.0,
6260: p_init_msg_list => FND_API.G_TRUE,
6261: x_return_status => x_return_status,
6262: x_msg_count => x_msg_count,

Line 6294: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);

6290: x_action_request_tbl => x_action_request_tbl );
6291:
6292:
6293: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
6294: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);
6295: END IF;
6296:
6297: IF (x_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
6298: FOR i IN 1..x_msg_count LOOP

Line 7280: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to call OE_ORDER_GRP.PROCESS_ORDER');

7276: l_oe_lot_serial_tbl(1) := l_oe_lot_serial_rec;
7277: END IF;
7278:
7279: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
7280: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to call OE_ORDER_GRP.PROCESS_ORDER');
7281: END IF;
7282:
7283: OE_ORDER_GRP.PROCESS_ORDER(
7284: p_api_version_number => 1.0,

Line 7283: OE_ORDER_GRP.PROCESS_ORDER(

7279: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
7280: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to call OE_ORDER_GRP.PROCESS_ORDER');
7281: END IF;
7282:
7283: OE_ORDER_GRP.PROCESS_ORDER(
7284: p_api_version_number => 1.0,
7285: p_init_msg_list => FND_API.G_TRUE,
7286: x_return_status => x_return_status,
7287: x_msg_count => x_msg_count,

Line 7323: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);

7319: l_osp_order_line_dtls.oe_return_line_id := x_line_tbl(1).line_id;
7320: END IF;
7321:
7322: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
7323: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);
7324: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'l_osp_order_line_dtls.oe_return_line_id = ' || l_osp_order_line_dtls.oe_return_line_id);
7325: END IF;
7326:
7327: IF (x_return_status <> FND_API.G_RET_STS_SUCCESS) THEN