DBA Data[Home] [Help]

APPS.CZ_OM_ATP_CALLBACK dependencies on FND_API

Line 118: IF (g_return_status <> FND_API.G_RET_STS_SUCCESS) THEN

114: ELSE
115: MSC_ATP_GLOBAL.extend_atp(g_atp_rec, g_return_status, p_count);
116: END IF;
117:
118: IF (g_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
119: RAISE extend_atp_rec_exc;
120: END IF;
121:
122: EXCEPTION

Line 585: IF (l_return_status <> FND_API.G_RET_STS_SUCCESS) THEN

581: l_ndebug := 5;
582:
583: -- calculate ATP
584: MSC_ATP_GLOBAL.get_atp_session_id(l_atp_session_id, l_return_status);
585: IF (l_return_status <> FND_API.G_RET_STS_SUCCESS) THEN
586: raise l_atp_session_id_exc;
587: END IF;
588:
589: l_ndebug := 6;

Line 615: IF l_return_status = FND_API.G_RET_STS_ERROR OR l_return_status = FND_API.G_RET_STS_SUCCESS THEN

611: -- The error_code is defined by the lookup_type 'MTL_DEMAND_INTERFACE_ERRORS' in the
612: -- table mfg_lookups.
613: -- Display error messages in ATP notification window by selecting 'meaning' for the given error_codes
614: -- bug 2737013 fix: retrieve any possible error message even when the return status is success
615: IF l_return_status = FND_API.G_RET_STS_ERROR OR l_return_status = FND_API.G_RET_STS_SUCCESS THEN
616: l_error_msg_count := g_atp_rec.error_code.COUNT;
617: cz_utils.log_report('cz_om_atp_callback', 'call_atp', l_ndebug,
618: 'Known Error ... Count : ' || l_error_msg_count, fnd_log.LEVEL_STATEMENT);
619:

Line 643: ELSIF l_return_status = FND_API.G_RET_STS_UNEXP_ERROR THEN

639: fnd_log.LEVEL_STATEMENT);
640: END LOOP;
641:
642: -- will display error message using x_msg_data returned from MRP_ATP_PUB.CALL_ATP
643: ELSIF l_return_status = FND_API.G_RET_STS_UNEXP_ERROR THEN
644: cz_utils.log_report('cz_om_atp_callback', 'call_atp', l_ndebug,
645: 'UnExpected Error from ...', fnd_log.LEVEL_STATEMENT);
646: RAISE l_call_atp_exc;
647: END IF;