Structural changes in the source table

[roberto_falk]

Hi,

I've created a Z table called ZSLT with 3 column: MANDT, ID and NAME.

I've inserted one record and after, started the replication. The record was replicated correctly into HANA.

After, I've added a new column called SURNAME in the source table. I waited 5 minutes and then I inserted a new records. I was expecting that this new column would be reflected in the HANA system, but instead, an error is showed in the iuuc_sync_mon transaction:

Z_ZSLT_017: Run 0000000001 aborted due to data inconsistency in 20150410 at 190018

Execution of program /1CADMC/OLC_001000000001654 failed, return code 3

As far as I understood, table changes should be reflected automatically, right? Any idea wha might be wrong here?

See below the systems version:

DMIS 2011_1_731 0007 SAPK-11607INDMIS - Installed on both systems (source and SLT dedicated machine).

HANA SP8 1.00.83.00.395718

Thanks and regards,

Roberto Falk

[Former Member]

Hi Robert,

If the source table is in ECC ...Just adjust the table in SE14.

Put the table name and click on activate and adjust the database.

Once done try to do the replication.

Hope it helps.

Regards,

Kannan

[roberto_falk]

Hi Kannan,

but we always have to do this, when changing tables that are being replicated?

I wonder in a huge company, an important table (like MARA for example) is being replicated, and then, a new note is applied and a new column is added to MARA. How many days/weeks will pass, until someone realizes that the replication is not working anymore? I believe people are not checking SLT status everyday....

Is this the expected behavior?

Best regards,

Roberto Falk

[Former Member]

Hi Robert,

I understand your concern.You were talking about custom table right.There in order to ensure the data consistency during structural change SE14 and table maintainace generator is recommended,

For case of standard table like Mara,all data consistency is ensured by the transaction level.Case of mara it is updated via Material master transactions.Even for standard table we can mostly add fields only in CI includes.For there is less chance of it to happens.

SLT will take care of default table adjustments via the ALTER.Just incase it didnt work take a look at the first 2 SAP Notes

Just check the useful link

Hope you got the point.

Regards,

Kannan

[roberto_falk]

Hi Subhash / Kannan,

sorry my delay, I was sick this week. See below the requested information:

I've created this table on a ECC, basis 731 sp 12. Both notes you sent are already applies via SP.

All that I did was to include a new column called SURNAME, no key field changed.

I've adjusted the table using tcode se14 as suggested. but I still have an error in the replication. I've then stopped the replication and then started the replication again. After, finally the new column was replicated to HANA.

I've created on this test a Z table, but I faced the same issue when changing a stardand table (J_1BNFDOC). This table is part of the Brazilian localization and usually is really really big, so, I think would be difficult to stop the replication (and loose all data already replicated) adjust thru se14, and after restart replication.

Let me know your comments.

Best regards,

Roberto Falk

[Former Member]

Hi Roberto,

We are also facing same issue, have you found any solution ?

Thanks,

Somen

[roberto_falk]

Hi Somen,

No changes. Everytime I have to remove the table from SLT, and re-include it.

Best regards,

Roberto Falk

[former_member208919]

Hi Roberto,

Can you please tell me the source system details .

Did you change the key definition of the table ?

Also please check the dictionary tables DD02L, DD02T and DD08L if they are in the status Replicate, or In Process.

Now let me describe the scenario in detail,

If your source System is on SAP NetWeaver Basis 6.40 or lower, and key definition is changed the trigger will fail. In this case you have to stop the replication for the affected table and start the replication.

If the Source System is on SAP NetWeaver Basis 7.00 - 7.30: you have to implement SAP Note 1655725 and 1875769. By implementing these two notes on the ABAP source system, simple table structure changes (adding a non-key field) are possible with active SLT triggers.

In case of complex table structure changes (change data type or length, add or delete key fields) the trigger and logging table have to be dropped and recreated. you have to implement SAP Note 1749824 for this case.

Hope it can help you.

Thanks,

Subhash