Transformations

How is a filter rule in SLT actually implemented under the hood, and how does it relate to transformation rules?

A DBA wants to add SLT filter rules to reduce load on the source system and speed up replication. Why won't that work?

For heterogeneous SLT landscapes, where do you find the authoritative list of supported source/target database type mapping combinations?

In an SLT event-based rule, what are the two ways to supply the ABAP logic?

A stakeholder wants to use SAP LT Replication Server to do heavy multi-source cleansing, joins and enrichment like a full ETL job. Why is that the wrong tool choice?

When is SLT the better place to perform a data transformation rather than fixing the data in the source system?

In SLT, what are the two named building blocks that make up a transformation, and which handles data-type differences versus custom logic?

Replicating from an SAP ERP source into SAP HANA — how many data-type mapping steps actually happen, and why?

Why can the second data-type mapping step (ABAP Dictionary types → target DB types) be skipped when the target is an ABAP-based SAP system?

A non-ABAP source (e.g. Microsoft SQL Server) is replicating into SAP HANA via SLT. What extra mapping layer is introduced compared with an ABAP source?

For a non-ABAP source system, who is responsible for guaranteeing that SLT's data-type mapping and conversion are correct?

Someone plans to use SLT to decommission a legacy/third-party system such as JD Edwards. Why is that use case specifically cautioned against?

You need to change the default HANA data-type mapping for every table in an SLT configuration at once. Where do you set it?

A table has a mapping in Global Mapping Values AND a different mapping in that table's Mapping Values tab. Which one wins?

Within a table's Mapping Values, what is the difference between the 'Data Types' option and the 'Table Fields' option?

When specifying a Target DB Type for a HANA table in SLT mapping, why should you NOT type 'NOT NULL' or 'NULL' into the Target DB Type field yourself?

In SLT rule assignment, when should you pick a field-based rule versus an event-based rule?

Where in the SLT UI do you create a rule assignment, and what must you select first before creating it?

You created a field-based rule to force CURRENCY to 'USD', saved it, and it isn't being applied during load/replication. What step was missed?

What kind of migration objects are field-based rules unable to handle in SLT?

In an SLT event-based rule using the BOR/EOR events, how do you access the source and target record data?

What extra capability does an event-based rule give you over a field-based rule, beyond touching multiple fields?