[Home] [Help]
24: -- either plain or non-plain with 0 qty. Here, for 0 qty completed, the
25: -- transaction can be flipped to pending. For non-zero completed plain, a
26: -- 0 qty pending transaction is inserted. insert_batch_step_dtls performs
27: -- batch by batch processing in order to normalize pm_oprn_dtl
28: -- into gme_batch_step_activities and gme_batch_step_resources.
29: --
30: -- The main package to call is migrate_batch.run. If it is called with no parameters,
31: -- or as migrate_batch.run(p_commit => FALSE) a rollback is performed at the end of the
32: -- migration. This is for purposes of validation, so that the user can find all data
3148: p_message => 'number of records inserted = ' || l_act_cnt,
3149: p_error_type => 'P'
3150: );
3151:
3152: INSERT INTO gme_batch_step_resources
3153: (batchstep_resource_id,
3154: batchstep_activity_id,
3155: resources,
3156: cost_analysis_code,
3318: WHERE delete_mark < 100 AND
3319: delete_mark <> 1;
3320:
3321: insert_message (
3322: p_table_name => 'gme_batch_step_resources',
3323: p_procedure_name => 'insert_batch_step_dtls',
3324: p_parameters => 'none',
3325: p_message => 'number of records inserted = ' || SQL%ROWCOUNT,
3326: p_error_type => 'P'