SAP SLT Replication

Hi All,
We to need to load the data from the Source (ECC ) to HANA, using the SAP SLT server and need clarifications on below points.
1) Does the SLT replication server will overwrite in target for the changed records in the source
Eg:- If the sales has done on feb is 7 quantity and on march it is 9, will SLT would over write the values as 9 ? if so how to track the history of records in HANA and do a model based on the History of records ?
2) How to create model based on the time, if the user runs the report with Feb as the selection he should be able to see the quantity as 7 and thats why we require the history of records also
Kindly suggest
Thanks,
Shree

Hi Vijayashree,
SLT will overwrite the data in HANA whenever there is a change in the source system for that record.
In order to get the report based on time then every time record has to be inserted for each and every change instead of updating and there should be fields something like valid_from and valid_to.
In case of update then current record valid_to has to be updated with current date and a new record has to be inserted for valid_from as current date and valid_to to future date.
In such cases only we can get history records. With BODS ETL tool, it is easy to accomplish.
With SLT such transformation is not simple. Can we do this using IUUC_REPL_CONTENT by ABAP Include is even question to me.
Lets see what Tobias Koebler suggests!!!!!
Regards
Raj

Similar Messages

SAP LT 2.0 && SLT Replication in HANA : query

Hello LT experts,
I am sure that we could use SAP SLT Replication (Data provisioning method) using HANA with source system as SAP or Non SAP SYSTEMS.
Please advise if the same works with SAP LT.20 for system landscape transformation project.I mean source for SAP LT2.0 would be Non-sap and target ofcourse would be SAP (which could be consolidation of many existing SAP productive systems).
Thank you
Shishupal.

Hi Shishupal,
If I understand correctly, you are looking for difference between SLT in HANA and SAP Landscape Transformation 2.o(SLT again ). Both these two tools are from same framework. But SLT in HANA is used as a replication tool, whereas, as you said we use HANA as a secondary database and the source is may be SAP or NON SAP. In case of SLT 2.0, this tool is used in during company marge, merging company code, merge profit area (used basically when two company merge scenario etc). May be you already know that for SLT in HANA requires DMIS addon in 7.02 netweaver systems like wise for SLT 2.0 DMIS is required for SLT 2.0 ad additionally one more addon component SHC_CONT is required. So we have two things
SLT replication tool
SLT 1.0 or 2.0
Regards,
Rafikul

Inserting a conversion routine in SLT replication from SAP EWM system to HANA

We are a new SAP HANA customer trying to get the 1st report out… having few issues with data replications from SAP EWM system. EWM material conversion use a Kernel level FM to convert material GUID code to human readable material code, HANA does not use this routine so we are exploring whether we can insert ABAP routine to update the SLT replication or conversion logic, for example we can call EWM: CONVERSION_EXIT_MDLPD_OUTPUT routine and update human readable material code into correct data field in HANA. With this HANA can see the reportable material code directly. We came across few SLT specific FM’s in EWM, but need to find an enhancement spot to insert a code. I really appreciate If any of you SLT experts can let us know what would be the best way to do this.

Hi,
well, some correction notes for SP08 were missing. Mea culpa :-) Unfortunately implementation of the notes did not solve all Problems. Now the field length is correct but the field order and "not null"-Status of the fields is still wrong.
Best regards
Harry

SLT Replication for the same table from Multiple Source Systems

Hello,
With HANA 1.0 SP03, it is now possible to connect multiple source systems to the same SLT Replication server and from there on to the same schema in SAP HANA - does this mean same table as well? Or will it be different tables?
My doubt:
Consider i am replicating the information from KNA1 from 2 Source Systems - say SourceA and SourceB.
If I have different records in SourceA.KNA1 and SourceB.KNA1, i believe the records will be added during the replication and as a result, the final table has 2 different records.
Now, if the same record appears in the KNA1 tables from both the sources, the final table should hold only 1 record.
Also, if the same Customer's record is posted in both the systems with different values, it should add the records.
How does HANA have a check in this situation?
Please throw some light on this.

Hi Vishal,
i suggest you to take a look to SAP HANA SPS03 Master Guide. There is a comparison table for the three replication technologies available (see page 25).
For Multi-System Support, there are these values:
- Trigger-Based Replication (SLT Replication): Multiple source systems to multiple SAP HANA instances (one source system can be connected to one SAP HANA schema only)
So i think that in your case you should consider BO Data Services (losing real-time analytics capabilities of course).
Regards
Leopoldo Capasso

SAP LT Replication Implementation

Dear Experts,
When we use SAP LT Replication server, How it works?
When we need to implement in BW Project?
What is benefits compare to SAP Dataservices? How about license cost and maintance for SAP LT server?
Rgds,
Das

Hi Das,
I hope you may get more info about SLT.
http://scn.sap.com/docs/DOC-59784
http://help.sap.com/saphelp_hba/helpdata/en/dc/13d75264e19d36e10000000a44538d/content.htm?frameset=/en/29/0bd752c1cca91ae10000000a44538d/frameset.htm&current_toc=/en/38/b9ea52e9fbe22de10000000a423f68/plain.htm&node_id=15
http://help.sap.com/hana/sap_landscape_transformation_for_sap_hana_operations_guide_en.pdf
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70dd6e62-0113-3110-f58e-92aa5a784377?QuickLink=index&overridelayout=true&59511066929077

1:N SLT replication configuration

Hello Experts,
I am doing a configuration for 1:N SAP HANA replication to setup high available HANA in our environment.
My plan is to replication the tables from the same source ERP into 2 different HANA installations.
I have done the setup using the allow multiple usage flag for both of the configuration and the configurations were created successfully. My problem is that the 2 different mass transfer ID's are using the same logging table in the source system. In the configurations I used a dedicated tablespace where all the logging tables should be create and I was expecting to have 2 different logging tables for the same ERP table but that is not the case.
After successful initial load for VBAK R3 table into the 2 different schema, the delta load is happening only into one if the schema. So it seems if one of the configuration is performed the replication based on the logging table, the second is not doing anything.
Did anybody face similar issue? We are running on DMIS2010 SP10.
Thanks in advance for any help.
BR
Tamas

Hi Tobias,
I was referring to the new 1898479 and there this statement
Note that a switch between 1:1 and 1:N replication is not recommended! It might create some inconsistencies if part of the tables were initially selected for replication in an 1:1 context and later it is switched to 1:N or vice versa. So please only do this if absolutely indispensable!
Maybe there is other note I could use.
BR
Tamas

Error while creating Configuration for SLT replication

Hi All,
I have got Hana trial version system and I am trying to do data replication using SLT.
While doing the configuration using transaction LTR, I am getting error as attached.
Though I am getting an error, entry is getting into the DBCON table but when I trying to check the connection via the report ADBC_TEST_CONNECTION, I am getting error as :-
Could not open connection TMPI07762120130424061216 .
sql error 10.709- occured:
Connection failed (RTE:[89001] Cannot resolve host name 'hanacloud' rc=8: node name or service name not known)
Note:- I am using hanacloud as hostname in hana studio and its working fine there
Can anyone can suggest, what can be the solution for it.
Thanks in advance,
Gopal

Hi Gopal,
Could you please clarify what type of trial system youhave received? Even though you will get the same HANA software but based on the delivery and deployment (On Premise or Cloud (which is again Develop Edition or HANA One for productive cases)), some of the deployment parameters are different. SAP HANA One is SAP HANA in public cloud (currently only at AWS) with hourly pricing and community support for productive and commercial use cases.
By the way, for new SAP HANA One customers:
PROMOTION- February 18- May 30, 2013 - AWS customers who are new to SAP Hana One on the AWS Marketplace will receive $120 of AWS Promotion Credit if they use at least 10 hours of SAP Hana One between February 18 and May 30, 2013. For AWS Marketplace customers who qualify, the Promotional credit will be sent to the email address registered to their AWS Marketplace account. Restrictions apply; see offer terms at https://aws.amazon.com/marketplace/help/201119060 for more details.
Thanks,
Swapan

SAP online replication.

Hello,
we are planing a disaster site for our systems,
SAP4.7 (OS/400)
SAP5.0 (OS/400)
BI7.01 (OS/400)
PI 7.0 clustered( WIN2003x64 with DB2)
The request is for online IP based replication between Production site and DR site. Is it possible to use the same host names (in DR )for all systems and Application Servers and still perform the IP based replication without problems?
Any answer or hint will be appreciated
Thank you,
Dimitrios

You may want to check the attachment to SAP Note 568820. If you configure your HA solution as described in the attached document "iASP_Configuration.pdf", you will define a "virtual" host name that can be switched between the primary and the backup server. SAGUI and other tools access the server over the virtual host name, and the setup defines whether it is currently assigned to the primary server or to the backup server. Besides that, each server keeps a unique physical host name that can be used for other things, like system administration tools.
Kind regards,
Christian Bartels.

MaxDB to HANA replication via SLT suffers from 8 characters password limitation?

Hi experts,
We are trying to replicate data from a NW BPM instance (SAP NW PO (Java) on MaxDB with, let's say, sid PO7) via SLT to SAP HANA.
(Version info: MaxDB 7.9, SLT DMIS 2011 SP5, HANA 1.0 SP6 Rev68.)
So we use the ADBC connection route, via the DBCON table.
We want to use the SAPPO7DB user because it is impossible (we think) to have another MaxDB-user connect to the SAPPO7DB (personal) SCHEMA with all the authorizations described in 1778969 - SAP LT Replication Server: Using MaxDB as non-SAP source .
So we resort to the SAPPO7DB user who has a password of 8+ characters. Connecting via SQL Studio is no problem, however via DBCON and testing via ABAP report ADBC_CHECK_CONNECTION we get "sql error 4.008- occured: POS(1) Unknown user name/password combination" errors.
When connecting a DUMMY maxdb user with a passowrd of 8 chars, the connection test is successful. With a password of more than 8 chars, the test fails.
So is the DBCON connectivity indeed suffering from the ancient 8 characters password limitation?
If so, how to fix this? Our workaround would be to change the SAPPO7DB password to a new one of 8 characters in length. Of course, we want the PO system to keep on running, so in which configuration thingy would we need to change this password so the app server can connect to the db? (This is my lack of Java Basis knowledge showing...)
Cheers, Wout

Hi Wout,
I am also performing similar replication from PO to HANA which is not working.
Replication scenario : BPM(PO) -> SLT -> HANA
Please see my post : Table BC_BPEM_EL_ENTRY not found in the control table DMC_MT_TABLES
Please help if you have any idea on this? Thanks in advance.
Cheers,
Naresh

1:N Replication Scenario Approach

Hi,
We plan to split HANA and like to consider the parallel run option whereby we build the new hardware and do a migration/restore from existing Production onto the new box. Then we like to switch on SLT for both the existing and new HANA boxes and run the models in parallel to compare the results before we switch off the old one.
This would mean that we need to setup new SLT triggers for the new server whilst the existing triggers are still running.The current configuration for SLT -- Allow Multiple Usage is not selected.How we can perform this in our landscape?What would be the best approach?

Hi Roy,
look at this note. it describes how to setup 1:n once you already created the config without "multiple usage" flagged.
Best,
Tobias
SAP Note 1898479:
SLT replication: Redefinition of existing DB triggers

1:N Replication Health Check

Hello,
When we run the check of 1:N Replication Health Check We are getting the following:
We cant replicate the tables mentioned in this report.
How should we proceed to fix this issue?
Thanks,
Amir

Hi Roy,
look at this note. it describes how to setup 1:n once you already created the config without "multiple usage" flagged.
Best,
Tobias
SAP Note 1898479:
SLT replication: Redefinition of existing DB triggers

SAP MII 15.0:HANA as a back-end ! Distributed Architecture

Dear MII Consultants & Architects,
I have a query here regarding SAP MII 15.0 when it is deployed as de-centralized.
Lets say there are 3 Plants.Each plant needs a local MII system.
How a local MII system will interact with HANA if HANA is a central entity?
Will all the local MII installations which have their respective SQL/Oracle do a SLT replication with HANA?
Regards,
Muddassar

There's not just a single way to interact between MII & HANA; there are many options that are available so that we can support the underlying business scenario in the best way. For options and architectures that support them have a look here:
SAP MII, HANA/ESP and Lumira (Technical)
I also have a technical architectures deck that I can share with you if you like just email me directly for it.
Please let me know what you think of my post about MII & HANA,
Sam

SLT Scenario in question: ECC - SLT- HANA DB

Hello Team,
Issue : I need propose a scenario where we need to recover the data in a table in case of any failure occurs (where point in time recovery is not possible) or there is mismatch in Target database (HANA) when compared to ECC source system.
The following are key constraints:
Re-Replicate the table by stopping the replication and starting again is not an option.
Data from BW is being replicated on real time and customer has mission critical reporting which does not allow downtime.
(in case of re-conciliation issue 1 hr downtime may be allowed as exception)
I have reviewed the documentation available and did not find any clear solution (steps) for recovery. How can we recover in the case of above scenario where replicating the tables again is not an option?
Please provide your viewpoint as this will be helpful in fast tracking the solution.
Regards,
Hemanth Aluri

Hi,
If you cannot recover to the last point in time, you can use the
replication logging feature that is available with the DMIS 2011 SP6.
Replication logging can be switched on for all tables of a
complete configurations via the checkbox ‘Activate Replication Logging’ at
the time when the configuration is created.
The SLT Application Operation Guide describes:
If you need to activate replication logging for an
existing configuration, or if you want to deactivate replication logging, you
need to adjust some entries in the SAP LT Replication Server configuration
tables.
You can also activate or deactivate replication
logging for specific tables if required.
By default the data retention period is 3 days, you
can change this either generally per configuration or individually per table
More details in chapter 6 of the Application Operations Guide: Application
Operations Guide
Best,
Tobias

Can SLT replicate data directly to Hadoop

Hi,
Has anyone successfully connected SAP SLT directly to Hadoop or other big data services where the big data is the target? We have a scenario where our SAP OER will produce millions of records of which we wish to report against but see that the scale, ie number of records plus the data retention requirements will mean a typical SAP BW and or a SAP HANA will not be a viable architecture.
So is SLT a contender, excluding potential license discussions?
Thanks
Brian

Hi Justin,
with the gerneral replication to non-ABAP DBs as a target we made some good movements and got a lot of experience within the last year in customer projects. Despite that we do not plan to release it with the next SP version unrestrictedly because we did not test all available setups so far. So we cannot brand it as out-of-the-box working from a legal perspective. Anyhow when you have a scenario with the replication to non-ABAP just conctact us, ususally we did with the common databases already some customer projects and can enable it without any efforts.
For the general strategy it is planned to release it unrestricted with SP9 mid of 2015. Technically it is alreay working.
When I talked about non-ABAP DB it is only the DB's that are supported by NW (Oracle, MS SQL, IBM, ASE, MaxDB, Informix). All other DB's are only supported if the SAP basis team would deliver a library that allows SLT to connect to this DB. Hadoop is not include - unfortunately we are dependent on this team and their strategy.
Best,
Tobias

Is using Sybase Rep Server with SAP HANA a possibility?

We have a customer has system that they are already using Sybase Replication Server. They are asking to add HANA and BusinessObjects BI Platform as a sidecar, to there system and remove the Java applications they are using for reporting. They are wondering if they can use Sybase Rep server to move the data into Hana instead of SLT.

If you have a SAP Business Suite system then SLT is the recommended approach since carries out a application level replication of sorts. However, for non SAP Business Suite systems you do have the option to use Sybase Replication Server for HANA. Ask your customer to speak to their SAP Account Manager and she/he will be able to advice them on the option.
Have a look at the link below for pointers:Replicating data to HANA using SAP Sybase Replication Server.

SAP SLT Replication

Similar Messages

Maybe you are looking for