Quantcast
Channel: SCN : Discussion List - SAP LT Replication Server
Viewing all 562 articles
Browse latest View live

Create Events in BOL , BOR

$
0
0

Hello SLT Experts ,

Depending on the values of a first table I want to use a filter in a second table during  the migration , I have found 

this piece of code in BOL which it is  suppose allow me to read the info of a specific table in this case VBRK

 

select * from dmc_acspl_select  into table lt_acspl_select where migr_obj_alias = 'VBRK'

 

I have tried to put this code but I am not even able to active it ..., I get statement not accesible ,  I try to activate the whole function group no luck ,  same error , use start-of-selection but during migration I get an error .

Do you know what the problem is ? Is there any documentation about programing the includes ? the structures ? etc  available regarding this topic somewhere . ?

thank you very much 


Help! Replication of SAP ECC HR Payroll and Other HR Tables in SAP HANA

$
0
0

Hello all

 

I need some more information here. I have tried searching and have not found anything conclusive on replication of HR data via SLT into SAP HANA. All the documents say that SLT can handle but how, it is explained no where. HR cluster tables are very different than other cluster tables like BSEG, KONV where on replication, a meaningful table is created in SAP HANA. However, in case of HR cluster tables, I am not sure how this will work. The content in PCLx tables is stored very differently. Even if we replicate, it will not make much sense.

 

I found the following that refer to each other:

 

There is no proper guide or documentation I could find that could explain replication of HR tables.

 

Could somebody help as to what steps are required? Do we need to replicate PCLx tables via SLT and it will be taken care of or we need to perform declustering first and then replication? I am not sure what SLT's declustering framework does. If so, please guide.

reload for tables to BW

$
0
0

Hi gurus.

 

I have set up as below-

 

ERP->SLT->BW ODP

 

I have done init load for some tables however due to some issue I need to reload them - but am not able to delete original rpelication log from LTRC in SLT. I have deleted data frm BW but can you confirm how to delete logs entry from LTRC in SLT.

 

I have used below option but it does not delete  table entry from LTRC

 

Delete loaded tables from configuraion for ODQ scenario..

as shown in attached screnehsot if we dont delete original entry and do re init it will come as second entry with substitution.

ODQ_DAEMON job details needed

$
0
0

Hi all,

I need details on ODQ_DAEMON job that is required in SLT. i have ODP scenario set up in BW on hana which is pulling data from ERP via SLT. but this ODQ_DAEMON job is not running- however I am able to load init data without any issue.

 

attached screenshot shows issue. please advice

 

thanks

SLT Real Time replication via ODQ from ERP does not send new records to BW DSO

$
0
0

Hello.

 

We are currently trying to implement a real time replication scenario transferring data of a table in ERP replicated via an SLT server to a BW on HANA system using ODQ. However no changes in the table are transferred to the DSO in BW.

 

We have been following presentations and video instruction but did not succeed in the end. The following steps we did:

1) Creation of a configuration in SLT – source RFC to the ERP system, target RFC to the SLT with ODQ as scenario.

2) Creation of source system in folder “ODP SLT Queue” in BW connecting to the configuration in the SLT server.

3) Creation of data source using the SLT source system by selecting some small table from the list of ERP tables.

4) Creation of DSO and transformation comparable to the source table structure.

5) Creation of real time DTP.

6) In the RDA monitor we generate and execute a repair process chain – it derives all records from the source table in ERP – these appear active in the DSO.

 

When we add a new record to the ERP table it is not replicated to the DSO. In the ODQ monitor on the SLT we see the DTP and the open request as subscriber but the number of units and rows is zero.

image002.jpg

But when we switch to the unit view there the added records appear and the values are correct.

image004.jpg

Therefore we assume that the issue is somewhere in our ODQ configuration. We have checked the background job on the SLT server ODQ_DAEMON_CLIENT_001 and it is running every 15 min for not more than 2 seconds.

image006.jpg

Is it correct that the job only runs short? Our understanding was that the job will run for 15 mins checking the queues every 15 seconds and sending an RFC to the BW when required so the BW will extract the data.

In the job log there are only 2 messages (“End of daemon period: 17.06.2015 at 00:29:31. Takt time is 15 seconds” – the end of the daemon period is exactly 15 min minus 15 sec after the start / “Notification task 1 started on server cuvdhan03_V08_00”). We do not know if the system executes the RFC call. In the transactions SMQ1/2 nothing is recorded neither in BW nor SLT and we do not know any other way to check.

 

We have checked the SAP notes but the only one we found was related to missing authorization (the system users have SAP_ALL and SAP_NEW as well as the specific profile for BW background users (S_BI-WX_RFC in SLT, S_BI-WHM_RFC in BW).

 

Our version are the following: DMIS on ERP 2011_1_731 SP7, DMIS on ERP 2011_1_731 SP8, BW 740 SP10.

 

Could somebody please comment how the ODQ_DAEMON job should behave?

Are there any other jobs which are relevant and which we could monitor?

Can we see somehow if the SLT sends the information about updates to BW via RFC?

Does anybody have any idea what we are doing wrong?

 

Many thanks, Thomas

SLT Error 3 during Reading Type 1 Replication

$
0
0

I recently received an Error Type 3 on one of my larger SLT data loads.  After looking further, it is tied to about 10 access plans.  Some of the access plans completely failed to write while others had portions within the access plan that was successful.  Since this is 100's of millions, I wanted to see if SLT will resolve these failed loads by itself, if I can rerun the failed jobs or if I have to start over?  Thanks for everyone's assistance.

Non-SAP targets data transfer

$
0
0

Hi Experts,


We are currently on SP7 and have requirement to transfer data to non-SAP targets.

 

I noticed that I can select non-SAP sources but target is only HANA DB (which is greyed out). Although, in drop down I can see different databases.

 

Please can you let know which is the latest SP available and through that non-SAP targets will be open?

 

Capture.JPG

 

Thanks.

BJ

How to load manual offline journal entries into Central Finance?

$
0
0

Hi Gurus,

 

I would like to consult with you as whether it`s possible to load manual offline journal entries(say entries recorded in excel sheet) into Central Finance through SAP Landscape Transformation Replication server? My clients have some branches which haven`t been implemented with any ERP products yet, all journal entries are being kept offline, while other branches have implemented with SAP ERP or non-SAP ERP. In the Library I can see instruction as how to integrate SAP or non-SAP ERP with Central Finance, but there is no discussion as how to handle those manual entries.

 

Please advise.

 

Regards,

Tommy Wei


Trigger in HANA on a replicated table

$
0
0

Hi all,

 

I have written a trigger for a replicated table (EKPO) which has been replicated from ECC to HANA. The trigger inserts values to a separate table based on values in EKPO. However the EKPO table's replication is stopped after creation of the trigger with an error being generated and replication starts after the trigger is deleted. I need to trigger a value based on values being updated from ECC for the table EKPO. Any ideas on how I could do this ?

 

Thanks,

Best Regards,

Nuzhi

Structural changes in the source table

$
0
0

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

LTR transaction not working

$
0
0

Hi All,

 

When execute the T-code LTR. Internet explorer opens up and displays as the content cannot be displayed.

Could you please tell me what is missing here?

 

 

Thanks & Regards,

Somen

SLT with MSSQL as target

$
0
0

Hi Experts,

 

We're in the process of setting up the SLT with ECC as source system and MSSQL as target. In the configuration of SLT, we could only select 'HANA' as the Database system in the 3rd step of specifying the target system though we can see the other Database in the dropdown but this dropdown is disable so we can't change from HANA to MSSQL.

Is there anything we need to do in order to enable this dropdown so we could select the other Database ?

 

SLT config.png

 

Thanks

Alok

Error While triggering tables from SLT to HANA

$
0
0

Hi Experts,

 

I have created configuration successfully.After this i am facing issue like below,

Error in Table replication.PNG

 

Error in table trigering.PNG

 

error inIUUC_SYNC_MON.PNG

 

Error in HANA studio,

Error in HANA studio Data provisioning.PNG

 

 

Please help me for the above issue.

 

Thanks in Advance.

Jana

Impact On Table Replication after Heterogeneous Migration

$
0
0

Hello Experts,

 

 

We are going to migrate Pre-Production systems SCM & CRM from AIX to Red Hat Linux.

Source & target database remains the same (DB2 LUW 10.5).

 

 

This is the migration of DB server only. Application server are already on Linux.

 

 

These SCM & CRM are source systems for pre-production HANA via SLT.

 

 

SCM(source) --> SLT --> HANA

CRM (source) --> SLT --> HANA

 

 

When we did migration of our DEV environment & started Master Job in SLT, trigger in SOURCE systems went into "INCONSISTENT" status. While the triggers in CRM systems were regenerated , for SCM system we had to reload tables again to HANA which could be additional downtime for users in case of Pre-production & Production systems and we want to avoid this.

 

 

What precautionary steps (other than stopping the MASTER job in SLT) we can take before migration so that trigger status doesnt go into "INCONSISTENT" State after migration?

 

 

Kindly provide your valuable inputs & suggestions.

 

 

Best Regards

Sachin Bhatt

SAP Basis

SLT Does not replicate all documents

$
0
0

Dear SAP LT Gurus,

 

We are using SLT in the following configuration: SAP ECC being replicated to a SQL Server Database 2008 (no in memory then).

 

We are facing so many issues with this configuration that it is better to filter the real blocking ones....

 

My problem is very simple: we have started to synchronize only 2016 Fiscal Year for BSEG table in SLT. The number of SHOWN replicated records was online with the number of records in BSEG table but we did not check in the first time the target table. After some days, we found out that we were missing a lot of records! Not all of the BSEG records were replicated! And this everyday! Everyday some records are replicated and some not....

 

After 1 week we were missing 750 000 documents (documents not ITEMS!!!!)! And the health check of the table is a real Christmas tree!

 

Checks for table BSEG started (mass transfer ID 006)

Table BSEG not found in the control table DMC_MT_TABLES

Source table for BSEG is

Last action is W-Resume (Wakeup) Replication, status is E-Error/ Aborted; "Is Last" = No (from 31.01.2016 00:19:55)

Current action is ; status is

Log table /1CADMC/00000989 created in sender system for table BSEG, and has 9 records

The following triggers are defined for table BSEG:

Trigger BSEG; status is 2-Activated

Latency for table BSEG is 71,10s (average of last 24 hours)

No access plan found for table

Migration object =Z__006;Defined? = No, Generated? = No (X = Yes, blank = No)

System status indicates issues with the load process for table BSEG

Checks  for table BSEG finished (mass transfer ID 006)

The troubleshooting activity has detected critical issues

 

And the cherry on the cake: we are not able to properly delete the data in the logging table (see other post without any answer) even if we correctly stop the replication process.

 

Can anybody help?? This is really critical right now for us and we would like to avoid a new initial replication.

Thanks.

Cyril.


SLT Issue : data structure mismatch

$
0
0

Hi There,

 

I am trying to SLT data from SoH(on premise)  to other HANA DB (in Cloud)

 

Successfully created SLT job and connected to target, but I see below error during replication.

 

Start of batch processing

Begin of data transfer (mass processing 001, access plan/precalc. 00001)

Current server:

Current work process number: 20938

Run 0000000001 started at 20150803 084836

Error in generic write: data structure mismatch

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

 

 

Can see tables on Target but no data.

Tried to recreate new SLT jobs and removal/create tables and basic trouble shooting.

 

Any comments appreciated.  Thank you

SLT replication error

$
0
0

hi,

 

I am getting error linked to replication init for BSEG table. the scenario is erp->SLT ODQ->BW on HANA.

 

 

Error - no IUUC data found for migration object Z_RFBLG_123

 

 

Kindly advice what can be done as i am facing strange issues - lot of new errorrs !

 

My SLT is on DMIS SP009

 

 

thanks

Change default write mode

$
0
0

Hi,

 

Is it possible to change the transfer behaviour from Array Insert into Single Insert when starting replication for tables?

The default method is Array Insert, but the problem is that table replication fails due to duplicate keys.

 

What I would like to achieve, instead of manually changing the transfer behaviour to Single insert for each table (almost 500), is that SLT uses Single Insert automatically when starting replication.

 

Regards,

Jaapslt.png

SLT configuration issue.

$
0
0

Dear Friends,

 

I am facing issue with SLT configuration.

 

My requirement is to load ECC data to HANA system but when try to made configuration in SLT i am facing issue master ID. It says that Register Configuration failed for Mass Transfer ID and Schema" when i click on "Create configuration" in "Review and Create" step.

 

Please through some outputs for this. How i can solve this issue.

 

Regards,

VaraPrasad.

IUUC_REPL_CONTENT, Table Settings, Partition Command changes drops table

$
0
0

I came across a SAP LT issue recently that I would like to share since it currently has a bad side effect. I am working with SAP Support to get it fixed.

 

We have HANA table partitioning configured in SAP LT instead of HANA directly. This was done to save time when replicating SAP ECC 6.0 data to HANA since getting the table loaded and partitioned occurs in one step.  This is especially helpful when performing SAP test system refreshes which we do 2 - 4 times a year and partitioning large tables out of our 3.5 TB source database.

 

The issue we are encountering is occurring with DMIS 2011_1_731 SP 8 or SP 10 installed in a dedicated SAP LT server. When running transaction IUUC_REPL_CONTENT and using the Table Settings, Partition Command, two things are not working right: 

  1. When saving Partition Command modifications, the system drops spaces from the defintion.  This results in errors when saving or worse, it saves but then the table doesn't replicate properly due to syntax issues.
  2. Making changes to the defintion in the Partition Command section on a table that is currently replicating results in that table being dropped from HANA!  This has occurred to us with a SAP LT DMIS SP 10 system replicating to HANA revision 102 and a SAP LT DMIS SP 8 system replicating to HANA revision 96.  In each system, the table was dropped after saving the changes in IUUC_REPL_CONTENT but the LTRC display of replicating tables did not reflect that the destination table no longer existed in HANA.

 

Lesson learned until a fix is created:  don't change your partitioning configuration in SAP LT unless you plan to also drop and replicate your data from scratch.

 

Robert

Viewing all 562 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>