The m_pck_omi_utl.create_job procedure has the following call specification:
PROCEDURE create_job
(p_proj_id IN m_projects.proj_id%TYPE,
p_omij_code IN m_omi_import_jobs.omij_code%TYPE,
p_omi_data_source IN m_omi_import_jobs.omi_data_source%TYPE,
p_dp_id IN m_disciplines.dp_id%TYPE,
p_import_path IN m_omi_import_jobs.import_path%TYPE,
p_import_file IN m_omi_import_jobs.import_file%TYPE,
p_stat_id IN m_status.stat_id%TYPE,
p_lst_id IN m_list_status.lst_id%TYPE,
p_transfer_ind IN m_omi_import_jobs.transfer_ind%TYPE,
p_find_ident_ind IN m_omi_import_jobs.find_ident_ind%TYPE,
p_recognize_ind IN m_omi_import_jobs.recognize_ind%TYPE,
p_rev_increment_ind IN m_omi_import_jobs.rev_increment_ind%TYPE,
p_transaction_size IN m_omi_import_jobs.transaction_size%TYPE,
p_mapping_ind IN m_omi_import_jobs.mapping_ind%TYPE,
p_pbc_id IN m_pds_bom_configs.pbc_id%TYPE,
p_pds_start_ln_id IN m_omi_import_jobs.pds_start_ln_id%TYPE,
p_company_id IN m_companies.company_id%TYPE,
p_user_comment IN m_omi_import_jobs.user_comment%TYPE,
p_omij_id IN OUT m_omi_import_jobs.omij_id%TYPE);
This procedure creates a job definition record according to the parameters you pass and then commits this transaction. It is not necessary to use this procedure for a custom loading logic; however, its presence enables you to create a job programmatically if you, for example, use a host language environment, and it thus encapsulates access to the Smart Materials OMI data structure, which might be subject to change between versions into a single stored procedure call.
If you use this procedure, you must store the OMIJ_ID in a host variable in your program because this internal job ID is necessary for a call to the m_pck_omi_custom.omi_load procedure as a call parameter.