Pre_Execution_Function
Your adapter may require code to be run immediately before executing a Load Set, Data Mart, or Program. For example, a pre-execution procedure might check connectivity with the external system, prepare scripts for downloading to the Distributed Processing Server, and, for Load Sets, verify that source data structures and Oracle LSH target Table instances are compatible. The Pre_Execution_Function requires the following signature:
procedure <procname>(pi_nJobId in cdr_jobs.job_id%type)
pi_nJobId takes the jobID of the current object execution.
Some shipped adapters use a Pre_Execution_Function, including: SAS, Text, and Oracle Clinical Data Extract SAS View Load Sets; Oracle and SAS Data Marts.
Parent topic: Object Execution Functions and Procedures