In addition to the ARM - Mapping tools post before,
this is another situation we would like to get information.
We have established ADABAS to SQL using in house tools. Thus the mapping of PE and MU to target SQL table are handled differently to what ARM - Mapping tools is providing.
We want to know how Mapping tools can be used to map PE/MU to existing SQL tables (either with normalisation or not).
MU field using only 4 occurrences:
ADABAS field: M 1 JY CGT-COMPONENTS P 9.2
SQL table: CGT_COMPONENTS_1 decimal (18, 2) ,
CGT_COMPONENTS_2 decimal (18, 2),
CGT_COMPONENTS_3 decimal (18, 2),
CGT_COMPONENTS_4 decimal (18, 2)
PE field to be normalised:
P 1 JG IVST-OPTN-DETL
2 JH GRUP-PROD N 4.0
2 JI GRUP-PROD-UNIT-BLCE P 11.4
2 KJ SO-RBL-UNITS P 9.4
2 KK SO-RNP-UNITS P 9.4
2 KL SO-PRES-UNITS P 9.4
DFS_ACCOUNT_IVST_OPTN_DETL CPNY_CODE varchar (3) EXTL_ACCT_NMBR varchar (15) GRUP_PROD smallint GRUP_PROD_UNIT_BLCE decimal (18, 4) SO_RBL_UNITS decimal (18, 4) SO_RNP_UNITS decimal (18, 4) SO_PRES_UNITS decimal(18, 4)
We try the following:-
Drag the DDM to the Target Database (rather than dragging the fields to the columns of an existing table), the Mapping Tool will create a target table. If you look at the created table, you should see the generated index columns.
But the target columns do not have the same names as those in ADABAS, and not all columns are in the Target table.
We try in adding columns with the same names as the generated index columns into the existing tables.
By adding index columns, they will work for all inserts into the tables after the mapping has been done. How do we populate the indexes for the existing data on the table? I presume all updates to existing data will fail, as we have no index value in SQL.
Anything can help :?