DBA Data[Home] [Help]

APPS.OE_LINE_PAYMENT_SECURITY dependencies on OE_PC_CONSTRAINTS_ADMIN_PVT

Line 34: OE_PC_Constraints_Admin_Pvt.Clear_Cached_Results;

30:
31: -- clear the cached results so that the cache is reset for
32: -- the new order
33: IF p_record.line_id <> g_line_id THEN
34: OE_PC_Constraints_Admin_Pvt.Clear_Cached_Results;
35: g_line_id := p_record.line_id;
36: END IF;
37:
38: IF l_code_level >= '110510' THEN

Line 43: l_result := OE_PC_Constraints_Admin_PVT.Is_OP_constrained

39: OE_Order_Cache.Load_Order_Header(p_record.header_id);
40: l_transaction_phase_code := oe_order_cache.g_header_rec.transaction_phase_code;
41: END IF;
42:
43: l_result := OE_PC_Constraints_Admin_PVT.Is_OP_constrained
44: ( p_responsibility_id => nvl(fnd_global.resp_id, -1)
45: , p_application_id => nvl(fnd_global.resp_appl_id,-1) --added for bug3631547
46: , p_operation => p_operation
47: , p_qualifier_attribute => l_transaction_phase_code

Line 962: IF NOT OE_PC_Constraints_Admin_PVT.Check_On_Insert_Exists

958: -- Bug 1755817: if there are no attribute-specific insert
959: -- constraints, then no need to go further. Entity level
960: -- security check for CREATE will be called again from
961: -- process order after defaulting.
962: IF NOT OE_PC_Constraints_Admin_PVT.Check_On_Insert_Exists
963: (p_entity_id => OE_PC_GLOBALS.G_ENTITY_LINE_PAYMENT
964: ,p_responsibility_id => nvl(fnd_global.resp_id, -1)
965: ,p_application_id => nvl(fnd_global.resp_appl_id,-1) --added for bug3631547
966: )