on 2018 Apr 20 10:44 AM
Dears,
I'm replicating KNB1 table, filtering it on BUKRS.
I'm using DMIS 2011_1_731 Sp 12
Now I have to change the filters, adding more Filters items for new BUKRS codes.
Obviously I would like to avoid to stop the Replication and to redo the whole initial Load, also for those BUKRS that were already loaded before
My question is:
There is a way to avoid to redo the Initial Load for the whole table ?
Best regards
Hi,
Yes, there is an option in LTRS. You can specify the company codes you want the load to be done and not to be done.
Please check my blog here: https://blogs.sap.com/2017/11/29/load-missing-documents-using-slt/
Regards,
Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you would like reduce the set of data that you would like to replicate, then after that you define new filter you have to just rebuild the migration object. After that you define all filters, open your configuration in LTRC, goto on tab Processing Steps, execute step "Delete Load/Replication Objects" for table KNB1. Replication server automatically rebuild migration object, generate runtime object and replication will continue from the point where it stops before.
But if you would like to change filter extending the set of data, then you have only the chance to reload the whole table.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Andrey
let's see if I understood well.
With the "Delete Load/Replication Objects" (note 2109952 am I in right ? ) I will not delete the existent data on Hana and I should be able to add to the Replication process also the new data, but I will miss their Initial load.
If I need also the Intial load data for the new data, I must reload the whole table, including the data that already exist
Is it correct ?
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes. correct.
Regarding note 2109952: this KBA not fully suitable to your question. The KBA describes only regeneration of runtime object, but not a migration object. Migration object is object that describes how the data will be filtered, mapped, optimizes etc. The runtime object is generated code based on migration object. To take over new rule into the replication process you need to rebuild the migration object.
User | Count |
---|---|
67 | |
10 | |
10 | |
10 | |
10 | |
8 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.