APPS.OE_CREDIT_WF dependencies on OE_HOLDS_PUB

Line 318: OE_Holds_PUB.Apply_Holds

314: l_hold_source_rec.hold_entity_code := 'O'; -- Order Hold
315: l_hold_source_rec.hold_entity_id := l_header_id; -- Order Header
316:
317:
318: OE_Holds_PUB.Apply_Holds
319: ( p_api_version => 1.0
320: , p_header_id => l_header_id
321: , p_hold_source_rec => l_hold_source_rec
322: , x_return_status => l_return_status

Line 328: OE_Holds_PUB.Apply_Holds

324: , x_msg_data => l_msg_data
325: );
326:
327: /*
328: OE_Holds_PUB.Apply_Holds
329: ( p_header_id => l_header_id
330: , p_hold_id => 1 -- Credit Failure Hold
331: , p_entity_code => 'O' -- Order Hold
332: , p_entity_id => l_header_id -- Order Header id

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

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

Line 506: OE_Holds_PUB.Release_Holds

502: END IF;
503:
504: /*-------------------- Releasing credit hold -------------------------------*/
505: l_hold_release_rec.release_reason_code := 'PASS_CREDIT';
506: OE_Holds_PUB.Release_Holds
507: ( p_api_version => 1.0
508: , p_hold_id => 1
509: , p_entity_code => 'O'
510: , p_entity_id => l_hold_entity_id

Line 519: OE_Holds_PUB.RELEASE_HOLDS

515: , x_msg_data => l_msg_data
516: );
517:
518: /*
519: OE_Holds_PUB.RELEASE_HOLDS
520: ( p_entity_id => l_hold_entity_id
521: , p_hold_id => 1 -- Credit hold ID
522: , p_reason_code => 'PASS_CREDIT'
523: , p_entity_code => 'O' -- Order Entity