The purge job functionality is just a wrapper over the DBMS_SCHEDULER package, so if you want to schedule this task to be executed at another time, you should use DBMS_SCHEDULER functionality.
In your case after executing your code, DBA_AUDIT_MGMT_CLEANUP_JOBS has the following information:
SQL> SELECT JOB_NAME,JOB_STATUS,AUDIT_TRAIL,JOB_FREQUENCY FROM DBA_AUDIT_MGMT_CLEANUP_JOBS ;
JOB_NAME JOB_STAT AUDIT_TRAIL JOB_FREQUENCY
------------------------- -------- ---------------------------- ------------------------------
DAILY_AUDIT_PURGE_JOB ENABLED STANDARD AUDIT TRAIL FREQ=HOURLY;INTERVAL=720
And DBA_SCHEDULER_JOBS has the following:
SQL> SELECT job_name, next_run_date, state, enabled FROM dba_scheduler_jobs WHERE job_name LIKE '%AUDIT%' ;
JOB_NAME NEXT_RUN_DATE STATE ENABL
------------------------- ------------------------------------------------------------ --------------- -----
DAILY_AUDIT_PURGE_JOB 15-AUG-15 01.11.40.411757 AM AMERICA/ARGENTINA/RIO_GALLEGOS SCHEDULED TRUE
Schedule a new "manual" job as usual:
BEGIN
DBMS_SCHEDULER.CREATE_JOB (
job_name => 'MANUAL_AUDIT_PURGE_JOB',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL(1, TRUE, 1); END;',
enabled => TRUE,
comments => 'Manual Audit Purge Job');
END;
/
And then you can verify its execution by querying dba_scheduler_job_log as follows:
select log_date
, job_name
, status
from dba_scheduler_job_log
order by log_date asc;
You will get something like this:
LOG_DATE JOB_NAME STATUS
--------------------------------------------------------------------------- ------------------------- ------------------------------
16-JUL-15 01.50.03.081815 AM -03:00 ORACLE_APEX_MAIL_QUEUE SUCCEEDED
16-JUL-15 01.52.29.935133 AM -03:00 MANUAL_AUDIT_PURGE_JOB SUCCEEDED
Note: This POC was performed using 12.1.0.2.0 release.