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 467: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);

463: */
464: l_msg_count := FND_MSG_PUB.count_msg;
465: IF l_msg_count > 0 THEN
466: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
467: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);
468: END IF;
469: RAISE FND_API.G_EXC_ERROR;
470: END IF;
471:

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

471:
472: -- jaramana End
473:
474: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
475: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed Convert_Line_Tbl, About to OE_ORDER_GRP.PROCESS_ORDER');
476: END IF;
477:
478: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
479: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack

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

474: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
475: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed Convert_Line_Tbl, About to OE_ORDER_GRP.PROCESS_ORDER');
476: END IF;
477:
478: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
479: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
480: OE_ORDER_GRP.PROCESS_ORDER(
481: p_api_version_number => 1.0,
482: p_init_msg_list => FND_API.G_TRUE,

Line 480: OE_ORDER_GRP.PROCESS_ORDER(

476: END IF;
477:
478: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
479: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
480: OE_ORDER_GRP.PROCESS_ORDER(
481: p_api_version_number => 1.0,
482: p_init_msg_list => FND_API.G_TRUE,
483: x_return_status => x_return_status,
484: x_msg_count => x_msg_count,

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

511: x_action_request_tbl => x_action_request_tbl );
512:
513:
514: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
515: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);
516: END IF;
517:
518: IF (x_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
519: FOR i IN 1..x_msg_count LOOP

Line 543: OE_ORDER_GRP.PROCESS_ORDER

539: Modified by jaramana on January 11, 2008 to fix the Bug 5935388/6504122
540: If success is returned by the Public API, clear the message stack to eat up any warning messages from OM API.
541: Otherwise, OAExceptionUtils.checkErrors will consider these as errors.
542: Also note that had there been any validation errors that had been accumulated we would have thrown before the call to
543: OE_ORDER_GRP.PROCESS_ORDER
544: */
545:
546: ELSIF(x_return_status = FND_API.G_RET_STS_SUCCESS) THEN
547: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN

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

624: /*
625: Modified by jaramana on January 11, 2008 for fixing the Bug 5935388/6504122
626: The "Create Shipment" action passes p_init_msg_list as TRUE as it is the starting point.
627: p_init_msg_list is passed as FALSE otherwise. So the "Create Shipment" action is flushing the
628: warning messages generated by OE_ORDER_GRP.PROCESS_ORDER. So the shipment is created without
629: any errors (Warning converted to errors by OAExceptionUtils.checkErrors in the absence of
630: certain tokens).
631: */
632: Create_IB_Transaction(

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

969: */
970: l_msg_count := FND_MSG_PUB.count_msg;
971: IF l_msg_count > 0 THEN
972: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
973: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);
974: END IF;
975: RAISE FND_API.G_EXC_ERROR;
976: END IF;
977:

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

976: END IF;
977:
978: -- jaramana End
979:
980: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
981: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
982: OE_ORDER_GRP.PROCESS_ORDER(
983: p_api_version_number => 1.0,
984: p_init_msg_list => FND_API.G_TRUE,

Line 982: OE_ORDER_GRP.PROCESS_ORDER(

978: -- jaramana End
979:
980: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
981: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
982: OE_ORDER_GRP.PROCESS_ORDER(
983: p_api_version_number => 1.0,
984: p_init_msg_list => FND_API.G_TRUE,
985: x_return_status => x_return_status,
986: x_msg_count => x_msg_count,

Line 1040: OE_ORDER_GRP.PROCESS_ORDER

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

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

1265: */
1266: l_msg_count := FND_MSG_PUB.count_msg;
1267: IF l_msg_count > 0 THEN
1268: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
1269: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Error Count Before calling OE_ORDER_GRP.PROCESS_ORDER: '||l_msg_count);
1270: END IF;
1271: RAISE FND_API.G_EXC_ERROR;
1272: END IF;
1273:

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

1270: END IF;
1271: RAISE FND_API.G_EXC_ERROR;
1272: END IF;
1273:
1274: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
1275: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
1276: OE_ORDER_GRP.PROCESS_ORDER(
1277: p_api_version_number => 1.0,
1278: p_init_msg_list => FND_API.G_TRUE,

Line 1276: OE_ORDER_GRP.PROCESS_ORDER(

1272: END IF;
1273:
1274: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
1275: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
1276: OE_ORDER_GRP.PROCESS_ORDER(
1277: p_api_version_number => 1.0,
1278: p_init_msg_list => FND_API.G_TRUE,
1279: x_return_status => x_return_status,
1280: x_msg_count => x_msg_count,

Line 1330: OE_ORDER_GRP.PROCESS_ORDER

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

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

6177: RAISE Fnd_Api.g_exc_error;
6178: END IF;
6179:
6180: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
6181: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to OE_ORDER_GRP.PROCESS_ORDER');
6182: END IF;
6183:
6184: l_header_rec := OE_ORDER_PUB.G_MISS_HEADER_REC;
6185: l_line_tbl := OE_ORDER_PUB.G_MISS_LINE_TBL;

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

6207: l_count := l_count + 1;
6208: END LOOP;
6209: CLOSE get_oe_order_lines;
6210:
6211: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
6212: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
6213: OE_ORDER_GRP.PROCESS_ORDER(
6214: p_api_version_number => 1.0,
6215: p_init_msg_list => FND_API.G_TRUE,

Line 6213: OE_ORDER_GRP.PROCESS_ORDER(

6209: CLOSE get_oe_order_lines;
6210:
6211: --OE_ORDER_GRP uses its own message stack OE_MSG_PUB, so we should pass p_init_msg_list as true to this API
6212: --Note that this also does an FND_MSG_PUB.initialize along with clearing its own error stack
6213: OE_ORDER_GRP.PROCESS_ORDER(
6214: p_api_version_number => 1.0,
6215: p_init_msg_list => FND_API.G_TRUE,
6216: x_return_status => x_return_status,
6217: x_msg_count => x_msg_count,

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

6245: x_action_request_tbl => x_action_request_tbl );
6246:
6247:
6248: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
6249: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);
6250: END IF;
6251:
6252: IF (x_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
6253: FOR i IN 1..x_msg_count LOOP

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

7226: l_oe_lot_serial_tbl(1) := l_oe_lot_serial_rec;
7227: END IF;
7228:
7229: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
7230: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to call OE_ORDER_GRP.PROCESS_ORDER');
7231: END IF;
7232:
7233: OE_ORDER_GRP.PROCESS_ORDER(
7234: p_api_version_number => 1.0,

Line 7233: OE_ORDER_GRP.PROCESS_ORDER(

7229: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
7230: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'About to call OE_ORDER_GRP.PROCESS_ORDER');
7231: END IF;
7232:
7233: OE_ORDER_GRP.PROCESS_ORDER(
7234: p_api_version_number => 1.0,
7235: p_init_msg_list => FND_API.G_TRUE,
7236: x_return_status => x_return_status,
7237: x_msg_count => x_msg_count,

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

7269: l_osp_order_line_dtls.oe_return_line_id := x_line_tbl(1).line_id;
7270: END IF;
7271:
7272: IF (FND_LOG.LEVEL_STATEMENT >= FND_LOG.G_CURRENT_RUNTIME_LEVEL) THEN
7273: FND_LOG.STRING(FND_LOG.LEVEL_STATEMENT, L_DEBUG_KEY, 'Completed OE_ORDER_GRP.PROCESS_ORDER, x_return_status = ' || x_return_status);
7274: 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);
7275: END IF;
7276:
7277: IF (x_return_status <> FND_API.G_RET_STS_SUCCESS) THEN