[Home] [Help]
285: | are committed based on the commit_point parameter. |
286: | |
287: | If a database error is detected during the execution of any purge |
288: | function, all uncommitted rows are rolled back and an error message |
289: | is written to SO_EXCEPTIONS; using OEPUR as the context prefix. |
290: | |
291: | ARGUMENTS |
292: | Input: p_request_id NUMBER Identifies orders to be purged by this |
293: | sub-process. |
327: * Success: Any positive value. Processing continues.. *
328: * 0 = Success, rows deleted/purged *
329: * 100, 1403 are considered to be successful *
330: * Failure: Any negative value. Processing is rolled back. *
331: * Error has already been recorded in so_exceptions *
332: *********************************************************************/
333:
334: return_status := OEXPURGE.so_purge_headers( v_header_id,
335: p_request_id);
1513: ELSE
1514: v_message_text := SQLERRM( p_return_status );
1515: END IF;
1516:
1517: SELECT so_exceptions_s.NEXTVAL
1518: INTO v_exception_id
1519: FROM DUAL;
1520:
1521: SELECT UID
1533: FROM fnd_concurrent_programs
1534: WHERE application_id=v_application_id
1535: AND concurrent_program_name='OEXPURGE';
1536:
1537: INSERT INTO so_exceptions -- record an error
1538: VALUES ( v_exception_id, -- sequence number
1539: SYSDATE, -- creation date
1540: v_uid, -- created by
1541: SYSDATE, -- last updated date