Processing the batches of data in parallel

Question

Hi friends,
Can any one suggest me how to process the bathces of data in parallel.
Please see the requirement below.
•     A new version of ZREDISND1_OLD named ZREDISND1_EINVOICE with the possibility of processing the blocked invoices with parallel processing capability. The program will process the blocked invoices and will have the same results / outcome as the old program ZREDISND1_OLD had.
•     A new version of Z_RECTHI01_60 named ZRECTHI01_EINVOICE with the possibility of charging the amounts with parallel processing capability. The program will have the same results / outcome as the old program Z_RECTHI01_60 had.
•     An umbrella-program ZREDISND1_UMBRELLA will have de same capability as ZREDISND1_EINVOICE but will split the data automatically into batches, initial by supplier and additional by Business Partner followed by Contract Account. It will therefore act as an umbrella program for ZREDISND1_EINVOICE.
•     An umbrella-program ZRECTHI01_UMBRELLA will have the same capability as ZRECTHI01_EINVOICE but will split the data automatically into batches by suppliers. It will therefore act as an umbrella program for ZRECTHI01_EINVOICE.
•     For the realisation of the umbrella-programs a new table must be created. The table must contain all the service providers which are charged by E-Facturering. Also the indication if the blocked invoices belong to the service provider are processed indirect (the old method) or directly (the new method) must be stored. The table name will be ZEINVOICE.
I have to develop the umbrella programs.
Please suggest to me how implement this. Its an Urgent
Thanks in advance.
Vijay

Answer 1

We have 8 "short-fat" tables to hold the source data uploaded from the source file via SQL*Loader (the SQL*Loader step is fast). The data consists simply of strings of characters, which we treat simply as VARCHAR2 for the most part.
These tables consist essentially of a case key (composite key initially) plus up to 250 data columns. 8*250 = 2000, so we can handle up to 2000 of these variable values. The source data may have 100 any number of variable values in each record, but each record in a given file has the same structure. Each file-load event may have a different set of variables in different locations, so we have to map the short-fat columns COL001 etc to the corresponding variable definition (for validation etc) at runtime.
CASE_ID VARCHAR2(13)
COL001 VARCHAR2(10)
COL250     VARCHAR2(10)
We do a bit of initial validation in the short-fat tables, setting a surrogate key for each case etc (this is fast), then we pivot+validate this short-fat data column-by-column into a "long-thin" intermediate table, as this is the target format and we need to store the validation results anyway.
The intermediate table looks similar to this:
CASE_NUM_ID NUMBER(10) -- surrogate key to identify the parent case more easily
VARIABLE_ID NUMBER(10) -- PK of variable definition used for validation and in target table
VARIABLE_VALUE VARCHAR2(10) -- from COL001 etc
STATUS VARCHAR2(10) -- set during the pivot+validate process above
The target table looks very similar, but holds cumulative data for many weeks etc:
CASE_NUM_ID NUMBER(10) -- surrogate key to identify the parent case more easily
VARIABLE_ID NUMBER(10) -- PK of variable definition used for validation and in target table
VARIABLE_VALUE VARCHAR2(10)
We only ever load valid data into the target table.
Chris