APPS.OE_CREDIT_WF dependencies on OE_HOLDS_PUB

Line 312: OE_Holds_PUB.Apply_Holds

308: l_hold_source_rec.hold_entity_code := 'O'; -- Order Hold
309: l_hold_source_rec.hold_entity_id := l_header_id; -- Order Header
310:
311:
312: OE_Holds_PUB.Apply_Holds
313: ( p_api_version => 1.0
314: , p_header_id => l_header_id
315: , p_hold_source_rec => l_hold_source_rec
316: , x_return_status => l_return_status

Line 322: OE_Holds_PUB.Apply_Holds

318: , x_msg_data => l_msg_data
319: );
320:
321: /*
322: OE_Holds_PUB.Apply_Holds
323: ( p_header_id => l_header_id
324: , p_hold_id => 1 -- Credit Failure Hold
325: , p_entity_code => 'O' -- Order Hold
326: , p_entity_id => l_header_id -- Order Header id

Line 404: release hold API in OE_HOLDS_PUB. It is provided

400: end OE_APPLY_CREDIT_HOLD;
401:
402: /*-----------------------------------------------------
403: This procedure is a workflow wrapper to the Public
404: release hold API in OE_HOLDS_PUB. It is provided
405: here so that when the credit manager responds to
406: his notification that a credit review is required
407: for a customer whose order has gone on credit hold,
408: we can automate the removal of the hold if the

Line 500: OE_Holds_PUB.Release_Holds

496: END IF;
497:
498: /*-------------------- Releasing credit hold -------------------------------*/
499: l_hold_release_rec.release_reason_code := 'PASS_CREDIT';
500: OE_Holds_PUB.Release_Holds
501: ( p_api_version => 1.0
502: , p_hold_id => 1
503: , p_entity_code => 'O'
504: , p_entity_id => l_hold_entity_id

Line 513: OE_Holds_PUB.RELEASE_HOLDS

509: , x_msg_data => l_msg_data
510: );
511:
512: /*
513: OE_Holds_PUB.RELEASE_HOLDS
514: ( p_entity_id => l_hold_entity_id
515: , p_hold_id => 1 -- Credit hold ID
516: , p_reason_code => 'PASS_CREDIT'
517: , p_entity_code => 'O' -- Order Entity