Skip to Content
0

Filter records for large tables in SLT replication

Dec 24, 2016 at 05:52 AM

1.2k

avatar image
Former Member

Hi, We are planning to filter records on few conditions for SLT replication on BSEG table. What are the options available.

1) do we need to write a stored procedure.

2) put condition filter in the standard table.

3) write an abap routine ?

4) any other config settings ?

Please advise how to handle the filter for full load or delta load ?

Thanks

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

5 Answers

avatar image
Former Member Jan 04, 2017 at 06:32 PM
0

Filtering can be implemented using LTRS.

1. LTRS-> Performance Options

2. Right Click on Performance Options to Add table

3. Go to Initial Load options tab

4. Select Reading type 4 OR 5 for enabling filters

5. Add your fields for filtering data

This option will filter the source data before loading into target, you can further customize filtering through ABAP code in the Rule Assignment section.

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Anil, will these filter's work only for the initial load or for the real time replication as well. Will there be any impact on the source system ? Please update.

thanks

0
Former Member
Former Member

Hi Daniel - Impact on the source system depends on the volume of data being moved.

Calculation will be done on the source system for initial loads and logging will be created for replication, tables such as BSEG and BKPF may impact the source system if you are planning move large volumes of data.

BSEG is a cluster table and with a volume of over 900 mil records may impact source system. We cannot really generalize on the impact it depends on the size/configuration of the environment.

0
avatar image
Former Member Jan 31, 2017 at 01:39 PM
0

Hi Daniel,

Filtering records can be done in SLT System in Tocde LTRS ->Performance tab as said above.

Here you can map your field what you wants to bring to the target and also transformation and code is supported. It completly depends how complex your requirement is.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Feb 08, 2017 at 05:53 AM
0

Hi

Filtering can work using the configurations settings for Initial Load and Replication. Therefore you can have a separate filter condition for Initial Load and a completely different one for Replication.

I found that for Replication the Filters only worked when they referred to key fields of the Source System.

An Alternative is to use a code include in the Table Rules and you can code your filter condition into there.

Regards

Arden

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Aug 25, 2017 at 07:42 AM
0

For anyone having the same issue, try using Reading Type 4 or 5 for filtering. Also there where restrictions until SP09 which thereafter have been resolved.

Share
10 |10000 characters needed characters left characters exceeded
Andrey Martynov
Aug 31, 2017 at 10:34 AM
0

I just want to add a couple tips about performance:
1. if you do only initial load it preferable way to filter data via LTRS/PerfomanceOptions. In such case the filtering is doing on source side before transferring to the central system. But it work only for the key fields.
2. if you need to design same filter for the initial load and for the replication or you want to filter records not only by key fields you have to implement the rule under TableOptions. Note that in this case the filtering is doing already on central server, that is worse for the performance

Share
10 |10000 characters needed characters left characters exceeded