Skip to Content
Within this blog you find the updated list of allavailable notes for the SAP LT Replication Server. Please read and apply the recent notes to ensure an easy operation.

General Notes

SAP HANA 1.0: Central Note – SAP LT Replication Server – 1605140
HANA LTR – Clarification on DMIS releases – 1691975
SAP LT Replication Server: Collective Note – non-SAP Sources – 1768805

SAP LT Replication Server for ODP – 2120574 (central ODP note: 1931427 )

SAP LT Replication Server for SAP Central Finance 2154420

Relevant Notes from other Components

Note Description Source System Replication Server Comment
1875338 Structural Changes are not handled automatically Your SLT System is runnning on SAP_BASIS 710/711 or 720 and therefore
structural changes are not done by SLT automatically
1860891 Structural Changes are not handled automatically After applying note 1749824 structural changes are not
done by SLT automatically
1762397 GEN_ALTER_TABLE cannot be used for secondary database
1749824 Treatment of SLT triggers during transport
1655725 Check for DB trigger made less strict
1875769 Check for DB trigger made less strict (not null)
1761723 COMPUTE_INT_PLUS_OVERFLOW in CL_SQL_RESULT_SET->NEXT To prevent shortdump if the access plan calculation of very large tables should be parallelized
1738448 ORA-08103 during INSERT/UPDATE into LOB basicfiles Prevent problems in source system during initial load if Oracle version 11.2.0.2 or 11.2.0.3 in combination of ASSM with basic LOBs is used
1730566 Recommended performance-related system settings in SLO – DTL This note serves as central reference point (composite SAP note) for performance-related recommendations.
2080398 DB_GET_TRIGGERTEXT For HANA source systems, it wasn’t possible to view the trigger statement of existing triggers
2107724 DB400: DB_GET_TRIGGERTEXT did not work correctly For DB400 source systems, it wasn’t possible to view the trigger statement of existing triggers

Additional Information

Note Description
1905253 Duplicate key error on intial load
2070029 Secondary Unique Indices created by SAP LT Replication Server in target HANA database

DMIS 2011 SP08

Central Note: 2114257 – Installation/Upgrade SLT – DMIS 2011 SP8

Note Description Source System Replication Server Comment
2121963 SLT (2011 SP08) – Correction 00 Mandatory correction to solve conflict with note 2079660
2100164 SLT (2011 SP08) – Correction 01
2101084 Support the HANA feature multiDB Manual activity necessary
2120886 SLT (2011 SP08) – Correction 02
2123494 SLT –  recreate logging tables
2124481 SLT (2011 SP08) – Correction 03
2125689 SLT (2011 SP08) – Correction 04
2130758 SLT (2011 SP08) – Correction 05
2135150 SLT (2011 SP08) – Correction 06
2137555 SLT (2011 SP08) – Correction 07
2141006 SLT (2011 SP08) – Correction 08
2143477 SLT (2011 SP08) – Correction 09
2146431 SLT (2011 SP08) – Correction 10
2155066 SLT (2011 SP08) – Correction 11
2159291

SLT (2011 SP08) – Correction 12

2125528 SLT (2011 SP08) – Latency Calculation Correction
2163599 SLT (2011 SP08) – Correction 13
2171832 SLT (2011 SP08) – Correction 14
2176361 SLT (2011 SP08) – Correction 15 In special cases regeneration of runtime object is necessary.

Non SAP Replication

Note Description
2079660 SLT (2011 SP06/SP07/SP08) – Non-SAP – Support for long table names
2105098 SLT (2011 SP07/SP08) Non-SAP – enable Sybase source system
2150163 SLT (2011 SP06 – SP08) nonABAP MS SQL replication: short dumps in data transfer due to wrong mapping of decimal fields
2134016 SLT (2011 SP08) Non-SAP – enable DB6 as receiver system
2152547 SLT (2011 SP07/SP08) nonABAP DB2/DB6 replication: VARCHAR key fields with length > 255
2154448 SLT (2011 SP8) NON SAP Replication from Informix database
2164295 SLT (2011 SP07/SP08) nonABAP Oracle (unicode) field length
2159420 SLT (2011 SP08) Non-SAP – space chars for MSSQL
2167319 SLT (2011 SP08) nonABAP MaxDB *CHAR *BYTE and DATE errors
2167913 SLT (2011 SP07/SP08) NonABAP ORA field length – notefix
2173478 SLT (2011 SP08) Non-SAP: Oracle (unicode) CHAR-field length; Logtab creation on MaxDB

ODQ/ODP Replication

Note Description Comment
2124485 SLT ODP Scenario (DMIS 2011 SP08) – Correction 01 Enables table structure deviations for ODQ/ODP

DMIS 2011 SP07

Central Note: 2016511– Installation/Upgrade SLT – DMIS 2011 SP7

Note Description Source System Replication Server Comment
2016512 SLT (2011 SP07) – Correction 01
2041240 SLT (2011 SP07) – Correction 02
2057779 SLT (2011 SP07) – Correction 03
2063692 SLT (2011 SP07) – Correction 04
2067439 SLT (2011 SP07) – Correction 05
2072445 SLT (2011 SP07) – Correction 06
2085216 SLT (2011 SP07) – Correction 07
2105350 SLT (2011 SP07) – Correction 08
2101084 Support the HANA feature multiDB Manual activity necessary
2111616 SLT (2011 SP07) – Correction 09
2116707 SLT (2011 SP07) – Correction 10
2118125 SLT (2011 SP07) – Correction 11
2119784 SLT (2011 SP07) – Correction 12
2122184 SLT (2011 SP07) – Correction 13
2123494 SLT –  recreate logging tables
2124636 SLT (2011 SP07) – Correction 14
2129942 SLT (2011 SP06 and SP7): Declustering of INDX-like tables failed if done for multiple RELIDs
2135660 SLT (2011 SP07) – Correction 16
2136940 SLT (2011 SP07) – Correction 17
2147421 SLT (2011 SP07) – Correction 18
2154460 SLT (2011 SP07) – Correction 19 Note corrects error made in Correction 18
2154799 SLT (2011 SP07) – Correction 20
2129201 SLT (2011 SP07) – Correction 15

Non SAP Replication

Note Description
2042805 SLT (2011 SP07) – NON SAP – Correction 01
2051883 SLT (2011 SP07) – NON SAP – Correction 02
2065115 SLT   (2011 SP6/SP7 2010 SP10) – NVARCHAR Correction
2073332 SLT (2011 SP7) – Non-SAP – Correction 03
2075180 SLT (2011 SP7) – Non-SAP – Correction 04
2079660 SLT (2011 SP06/SP07) – Non-SAP – Support for long table names
2082839 SLT (2011 SP7) – Non-SAP – Correction 05
2097984 SLT (2011 SP07) – Non-SAP – Correction 06
2164295 SLT (2011 SP07/SP08) nonABAP Oracle (unicode) field length
2167319 SLT (2011 SP08) nonABAP MaxDB *CHAR *BYTE and DATE errors
2167913 SLT (2011 SP07/SP08) NonABAP ORA field length – notefix
2173783 SLT (2011 SP07) NonABAP ORA (unicode): length of CHAR-fields too large
2175613 SLT (2011 SP07) NonABAP ORA (unicode): CHAR-255-fields are mapped to CHAR-765-fields

DMIS 2011 SP06 / DMIS 2010 SP10

Central Note: 1958809 – Installation/Upgrade SLT – DMIS 2011 SP6
Note Description Source System Replication Server Comment
1944270 SLT (2011 SP06 / 2010 SP10) – Correction 01
1971302 SLT (2011 SP06 / 2010 SP10) : Critical performance issue concerning logging table creation critical performance hint
1975984 SLT (2011 SP06 / 2010 SP10) – Correction 02
1981030 SLT (2011 SP06 / 2010 SP10) – Correction 03
1984061 SLT (2011 SP06 / 2010 SP10) – Correction 04
1985423 Access plan calculation / data selection activity with parallelization selects too many data
1984947 SLT (2011 SP06 / 2010 SP10) – Correction 05
1988366 SLT (2011 SP06 / 2010 SP10) – Correction 06
1989442 SLT (2011 SP06 / 2010 SP10) – Correction 07
1990054 SLT (2011 SP06 / 2010 SP10) – Correction 08
1992138 SLT (2011 SP06 / 2010 SP10) – Correction 09
1994248 SLT (2011 SP06 / 2010 SP10) – Correction 10
1997846 SLT (2010 SP10) – Corrections / adding of missing functions for 4.6C 4.6C source only
1995954 SLT (2011 SP06 / 2010 SP10) – Correction 11
2002569 SLT (2011 SP06 – SP05 – SP04) – multi-node HANA logtab creation
2001386 SLT (2011 SP06 / 2010 SP10) – Correction 12
2006632 SLT (2011 SP06 / 2010 SP10) – Correction 13
2018260 SLT (2011 SP06 / 2010 SP10) – Correction 14
2020898 SLT (2011 SP06 / 2010 SP10) – Correction 15
2027865 SLT (2011 SP06 / 2010 SP10) – Correction 16
2034183 SLT – Logtab-Check adjustable on Configuration-Level (DMIS2011 SP6) Manual Activity required
2035207 SLT (2011 SP06 / 2010 SP10) – Correction 17
2037015 SLT (2011 SP06 / 2010 SP10) – Correction 18
2039056 SLT (2011 SP06 / 2010 SP10) – Correction 19
2044697 SLT (2011 SP06 / 2010 SP10) – Correction 20
2048809 SLT (2011 SP06 / 2010 SP10) – Correction 21
2053149 SLT (2011 SP06 / 2010 SP10) – Correction 22
2054955 SLT (2011 SP06 / 2010 SP10) – Correction 23
2057397 SLT (2011 SP06 / 2010 SP10) – Correction 24
2058739 SLT (2011 SP06 / 2010 SP10) – Correction 25
2060034 SLT (2011 SP06 / 2010 SP10) – Correction 26 with manual activity
2070851 SLT (2011 SP06 / 2010 SP10) – Correction 27
2079022 SLT (2011 SP06) – additional correction for correction 22
2054955 SLT (2011 SP06 / 2010 SP10) – Correction 23
2057397 SLT (2011 SP06 / 2010 SP10) – Correction 24
2058739 SLT (2011 SP06 / 2010 SP10) – Correction 25
2060034 SLT (2011 SP06 / 2010 SP10) – Correction 26 with manual activity
2072436 SLT (2011 SP05 + SP06) – Correction for Message Type X Shortdumps in the Monitor Job
2070851 SLT (2011 SP06 / 2010 SP10) – Correction 27
2079022 SLT (2011 SP06) – additional correction for correction 22
2081827 SLT (2011 SP06 / 2010 SP10) – Correction 29
2114243 SLT – Logtab-Check adjustable on Configuration-Level II (DMIS2011 SP6)
2116936 SLT (2011 SP06 / 2010 SP10) – Correction 31
2123494 SLT –  recreate logging tables

Non SAP Replication

Note Description
1983148 SLT (2011 SP06 / 2010 SP10) – NON SAP – Correction 01
2005474 SLT (2011 SP06 / 2010 SP10) – NON SAP – Correction 02
2011228 SLT (2011 SP06 / 2010 SP10) – NON SAP – Correction 03
2015417 SLT (2011 SP06 / 2010 SP10) – NON SAP – Correction 04
2031652 SLT (2011 SP06 / 2010 SP10) – NON SAP – Correction 05
2036407 SLT (2011 SP06) – NON SAP – Correction 06
2039199 SLT (2011 SP06 / 2010 SP10) – NON SAP – Correction 07
2042801 SLT (2011 SP06) – NON SAP – Correction 08
2051828 SLT (2011 SP06) – NON SAP – Correction 09
2058849 SLT (2011 SP06) – NON SAP – Correction 10
2065115 SLT   (2011 SP6/SP7 2010 SP10) – NVARCHAR Correction
2077754 DMIS 2011 SLT non ABAP correction for Support Packages 5 + 6: Missing data in initial load

BW PSA Replication

Note Description
1998237 SLT (DMIS 2011 SP04/05/06 DMIS 2010 SP09/10) BW-PSA Scenario – IMPORT_ERROR dumps

DMIS 2011 SP05

Central Note: 1882433 – Installation/Upgrade SLT – DMIS 2011 SP5
HOT FIX for DMIS_2011 SP05 
Due to technical reasons, make sure that SAP Note 1817467 (related to SAP_BASIS) is applied before installing DMIS_2011 SP05 in any SAP system with SAP_BASIS 7.00 (or higher) – most important in all productive SAP systems! If this is not possible, consider SAP Note 1899578 as an alternative solution. This is relevant for new installations of and upgrade to DMIS_2011 SP05.

SAP Replication

Note Description Source System Replication Server
1869693 SLT (2011 SP05) – Correction 01
1897801 SLT (2011 SP05) – Correction 02
1902902 SLT (2011 SP05) – Correction 03
1904713 SLT (2011 SP05) – Correction 04
1908827 SLT (2011 SP05) – Correction 05
1911361 SLT (2011 SP05) – Correction 06
1912602 SLT (2011 SP05) – Correction 07
1921120 SLT (2011 SP05) – Correction 08
1927825 SLT (2011 SP05) – Correction 09
1933424 SLT (2011 SP05&SP04 / 2010 SP09) – reduce the load on the sender system // Performance note – also implement 1953008
1935614 SLT replication: Trigger creation fails for pool tables, if DB system is DB6 (DB2 UDB)
1941378 SLT (2011 SP05) – Correction 10
1945151 SLT (2011 SP05) – Correction 11
1952709 SLT (2011 SP05) – Correction 12
1970384 SLT Correction for multi-client initial load
1961344 SLT (2011 SP05) – Correction 13
1965188 SLT (2011 SP05) – Correction 14
1971489 SLT (2011 SP05) – Correction 15
1975505 SLT (2011 SP05) – Correction 16
1977981 SLT (2011 SP05) – Correction 17
1981963 SLT (2011 SP0 4+5 / 2010 SP 9) Correction for data replication with multiple usage of source system tables
1990411 SLT (2011 SP05) – Correction 19
1995329 SLT (2011 SP05) – Correction 20
1997812 SLT (2011 SP0 4+5 / 2010 SP 9) Deregistration of 1:N consumers if logging table accidentally deleted by hand
2001654 SLT (2011 SP04+5/ 2010 SP09) – Structure changes for action Record Only
2002569 SLT (2011 SP06 – SP05 – SP04) – multi-node HANA logtab creation
2038223 SLT (2011 SP05) – Correction 22

Non SAP Replication

Note Description
1903462 SLT (2011 SP05) – NON SAP – Correction 01
1921769 SLT (2011 SP05) – NON SAP – Correction 02
1923685 SLT (2011 SP05) – NON SAP – Correction 03
1929612 SLT (2011 SP05) – NON SAP – Correction 04
1936583 SLT (2011 SP05) – NON SAP – Correction 05
1937950 SLT (2011 SP05) – NON SAP – Correction 06
1943565 SLT (2011 SP05) – NON SAP – Correction 07
1946062 SLT (2011 SP05) – NON SAP – Correction 08
1955228 SLT (2011 SP05) – NON SAP – Correction 09
1969025 SLT (2011 SP05) – NON SAP – Correction 10
1969792 SLT (2011 SP05) – NON SAP – Correction 11
ODQ/ODP Replication
Note Description
1914221 SLT ODP-scenario (2011 SP05) – Correction 01
BW PSA Replication
Note Description
1916576 Missing Authorization for Replication into SAP BW (PSA)
1998237 SLT (DMIS 2011 SP04/05/06 DMIS 2010 SP09/10) BW-PSA Scenario – IMPORT_ERROR dumps

DMIS 2010 SP9 / DMIS 2011 SP04

Central Note: 1824710 – Installation/Upgrade SLT – DMIS 2011 SP4 / 2010 SP9

SAP Replication

Note Description Source System Replication Server
1810627 SLT (2011 SP04 / 2010 SP09) – Correction 01
1825770 SLT (2011 SP04 / 2010 SP09) – Correction 02
1828748 SLT (2011 SP04 / 2010 SP09) – Correction 03
1829750 SLT (2011 SP04 / 2010 SP09) – Correction 04
1837965 SLT (2011 SP04 / 2010 SP09) – Correction 05
1845467 SLT (2011 SP04 /2010 SP09) – Correction 06
1847664 SLT (2011 SP04 / 2010 SP09) – Correction 07
1855712 SLT (2011 SP04 / 2010 SP09) – Correction 08
1856898 SLT (2011 SP04 / 2010 SP09) – Correction 09
1856349 SLT (2011 SP04 / 2010 SP09) – Correction 10
1857962 SLT (2011 SP04 / 2010 SP09) – Correction 11
1860829 SLT (2011 SP04 / 2010 SP09) – Correction 12
1862774 SLT (2011 SP04 / 2010 SP09) – Correction 13
1864525 SLT (2011 SP04 / 2010 SP09) – Correction 14
1868061 SLT (2011 SP04 / 2010 SP09) – Correction 15
1874308 SLT (2011 SP04 / 2010 SP09) – Correction 16
1877463 SLT (2011 SP04 / 2010 SP09) – Correction 17
1894485 SLT (2011 SP04 / 2010 SP09) – Correction 18
1890826 SLT (2011 SP04 / 2010 SP09) – Correction 19
1894485 SLT (2011 SP04 / 2010 SP09) – Correction 20
1896220 SLT (2011 SP04 / 2010 SP09) – Correction 21
1897359 SLT (2011 SP04 / 2010 SP09) – Correction 22
1899169 SLT (2011 SP04 / 2010 SP09) – Correction 23
1903814 SLT (2011 SP04 / 2010 SP09) – Correction 24
1908852 SLT (2011 SP04 / 2010 SP09) – Correction 25
1981963 SLT (2011 SP0 4+5 / 2010 SP 9) Correction for data replication with multiple usage of source system tables
1977981 SLT   (2011 SP04/SP05 / 2010 SP09) – Correction 17
1970384 SLT Correction for multi-client initial load
1953008 SLT (2011 SP05&SP04 / 2010 SP09 ) – Fix for Note 1933424
1935614 SLT replication: Trigger creation fails for pool tables, if DB system is DB6 (DB2 UDB
1929762 SLT replication: wrong file selected in archive load
1933222 SLT (2011 SP05&SP04 / 2010 SP09)
1933424 SLT (2011 SP05&SP04 / 2010 SP09) – reduce the load on the sender system
1975785 SLT (2011 SP04 / 2010 SP09) – Correction 26

Non SAP Replication

Note Description
1833880 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 01
1834450 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 02
1839747 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 03
1842631 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 04
1846761 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 05
1847331 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 06
1850422 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 07
1856526 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 08
1863198 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 09
1869032 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 10
1869854 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 11
1878911 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 12
1887639 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 13
1903457 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 14
1936472 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 16
1942601 SLT (2011 SP04/2010 SP09) – NON SAP – Correction 19

DMIS 2011 SP3 / DMIS 2010 SP8

Central Note: 1759156 – Installation/Upgrade SLT – DMIS 2011 SP3 / 2010 SP8

SAP Replication

NZDT Trigger creation fails for DB6

Note Description Source System Replication Server
1776664 SLT (2010 SP08 / 2011 SP03) – Correction 00
1759074 SLT (2010 SP08 / 2011 SP03) – Correction 01
1772982 SLT (2010 SP08 / 2011 SP03) – Correction 02
1773430 SLT (2010 SP08 / 2011 SP03) – Correction 03
1762397 GEN_ALTER_TABLE cannot be used for secondary database
1775913 SLT (2010 SP08 / 2011 SP03) – Correction 04
1761723 COMPUTE_INT_PLUS_OVERFLOW in CL_SQL_RESULT_SET->NEXT
1757899
1789499 SLT (2010 SP08 / 2011 SP03) – Correction 05
1790038 SLT (2010 SP08 / 2011 SP03) – Correction 06
1798814 SLT (2010 SP08 / 2011 SP03) – Correction 07
1801562 SLT (2010 SP08 / 2011 SP03) – Correction 08
1806630 SLT (2010 SP08 / 2011 SP03) – Correction 09 INDX-like Tables
1810000 SLT (2010 SP08 / 2011 SP03) – Correction 10 Add Field failed
1811627 SLT (2010 SP08 / 2011 SP03) – Correction 11
1742491 replace PUT_TADIR_INSERT with TR_TADIR_INTERFACE
1821520 replace PUT_TADIR_INSERT with TR_TADIR_INTERFACE  – 2 part
1813089 SLT (2010 SP08 / 2011 SP03) – Correction 12
1828638 SLT (2010 SP08 / 2011 SP03) – Correction 13 parallelization
1837963 SLT (2010 SP08 / 2011 SP03) – Correction 14
1842497 SLT (2010 SP08 / 2011 SP03) – Correction 15
1842802 SLT (2010 SP08 / 2011 SP03) – Correction 16
1846112 SLT (2010 SP08 / 2011 SP03) – Correction 17
1864526 SLT (2010 SP08 / 2011 SP03) – Correction 18

Non SAP Replication

Note Description
1771692 SLT (2010 SP08 / 2011 SP03) – NON SAP – Correction 01
1788987 SLT (2010 SP08 / 2011 SP03) – NON SAP – Correction 02
1774794 HANA LTR: Non-SAP – creation of new configuration fails
1770309 HANA LTR: IUUC_REPL_CONTENT NON SAP fix
1806753 Hana LTR (SP7,SP8) : NON SAP MSSQL – NUMERIC key fields
1822003 SLT (2010 SP08/2011 SP03) – NON SAP – MSSQL logtab
1844797 SLT (2010 SP8/ 2011 SP3) – NON SAP – DB6 trigger creation
To report this post you need to login first.

29 Comments

You must be Logged on to comment or reply to a post.

      1. Former Member

        Hi Tobias,

        I really like to commend your work on this subject it is amazing. I am trying to implement SLT for replication into BW. For the moment it seem that only note:1808251 is required on SAP BW.

        Do you have a list of required notes for BW? Or possible prerequisites to be met on the BW side.

        Regards

        Olusegun

        (0) 
  1. Former Member

    Hi Tobias,

    We’re currently on DMIS 2011 SP4. Do you recommend that we implement all of the suggested 25 notes upfront, or should we only implement a note if we run into an issue and find a note that is relevant to the issue.

    Regards,
    Raj

    (0) 
    1. Tobias Koebler Post author

      Hi,

      in general I would recommend that you implement all notes to avoid any issues upfront. When it is running for you – sure you can also stay at the note lvl and do not implement. You can also think to apply SP5.

      Best,

      Tobias

      (0) 
  2. Former Member

    Quick Question Tobias.

    Do you know if we can schedule the start and stop of replication on a daily basis. I am not referring to scheduling the replication here.

    My scenario is Source SQL Server DB -> SLT NW System -> HANA.

    Everyday Source SQL Server gets refreshed and we are manually stopping the replication just after refresh and starting it again. We know this will delete and create triggers which we are fine with. Is there a way we could automate this at all. Please advise.

    Regards

    Kalyan

    (0) 
  3. Former Member

    Hi Tobias,


    I have configured SLT. after that i am able to replicate all new table using LTRC, but i am facing issue with the table DD02L, DD02T,DD08L  like below,T001 table replication.PNGError in HANA.PNG

    Please tell me why this table only not going to replicate and i seen one SCN post as you said that Tables are suspend Mode. what is the meaning of suspend mode, how it will remove from suspend mode.

    Thanks

    Jana

    (0) 
      1. Sergio Guerrero

        Tobias Koebler I have the same issue and i am using HANA SP09 – any updates on how to do this ? i am not able to replicate data.. the only thing that worked was after a manual insert of the table name into the RS_ORDER table, i was able to see the table structure from the source system (MSSQL Server 2008R2) but we are still unable to replicate any data

        any documentation or links are appreciated

        (0) 
        1. Former Member

          hi Sergio,

          If the table structure is getting created, can you check few things :

          1. do triggers get created ? (LTR or LTRC)

          2. can you confirm if the access plan calculation was complete. you can check the  jobs on ECC for access plan calculation and also in data transfer monitor in LTRC while its on.

          3.was a complete clean up and re-config attempted ?

          4. are the authorizations correct ( try with SAP_ALL once after you have saP_ALL is regenerated)

          Regards,

          Jayesh

          (0) 
            1. Sergio Guerrero

              Jayesh –

              what do you refer to when you mentioned… access plan calculation? i am not sure where that would be found or where i need to find it.

              thanks

              SG

              (0) 
  4. Former Member

    Hi Experts,

    I have SLT installed on my same ECC system and its version is

    DMIS 2011_1_731 0010 SAPK-11610INDMIS DMIS 2011_1

    I am able to successfully create configuration but apart from DD* Tables, its not replicating any more tables. status shows replication initial load and nothing happens after that.

    Which note should be referred for correction notes?

    Regards,

    Saritha

    (0) 
  5. Manish Gupta

    Hi Tobias,

    I am working on the Business Integration scenario using an Oracle database, my log tables CFIN_LOG* got created and conversion objects generated as well.

    but any changes in the source system are not getting captured in the logging tables. I found note 2244291, which is not available in the above list. Can you please confirm if this note will be helpful to solve the issue?

    Source system: (note status shows “can be implemented”)

    DMIS 2011_1_700 0010 SAPK-11310INDMIS DMIS 2011_1

    SLT System: (note already implemented)

    DMIS 2011_1_731 0010 SAPK-11610INDMIS DMIS 2011_1

    Thanks,

    Manish

    (0) 
  6. Former Member

    Hi Tobias,

    We planning to upgrade DMIS from DMIS 2011 SP10 to DMIS 2011 SP11.

    Do we have a central note where we can apply all the relevant notes for SP11 in source and replication systems.

    Naresh A

    (0) 
      1. Former Member

        Thanks Shruthi.

        I am planning to upgrade DMIS from SP08 to SP11. Do I need to implement correction notes and manual activities which are related to SP09 and SP10 after applying them?

        Naresh A

        (0) 
  7. Former Member

    Hi Tobias,

    Can you please help me with the below query ?

    While running SLO LT package activities is there any way to select the specific server on which we can run the background job ? to make faster process with the server having less number of users login at the same time.

    Thank you in advance .

     

     

    Best Regards,

    Pritish

     

    (0) 
  8. Former Member

    Hi Tobias,

    I am facing some issues in the replication DMIS2011 SP11

    1. How to Replicate STXL table.. Like INDEX
    2. After Start Replication for many tables, “Trigger Status” is not displaying / Current Action shows “Replication (Initial Load).
    3. How can improve Replication fast.

    Thanks

    Amit

    (0) 
  9. Former Member

    Hi,

    i replicated a Table (RFCDES) from MAXDB 7.9 to MSSQL(Enterprise version) without Problems, first with Transaction DB50 configured the conexion from MSSQL und MAXDB and then with the Transaction LTRC create a new SLT for “MSSQL to MAXDB” then click it  and choose  the Option “Data Provision” then in the Popup Window choose “Process charching start” (with this Option will create the Structur  of Table in MSSQL)  then choose the Option “Start Replication” this Option will be the Daten from Table Charge. (actually replicate online).

    Now i try to replicate Table from MSSQL(Enterprise Version) to MAXDB 7.9  but i not have the Option “Process charching start” in the Popup Window.

    if stand it choose the Option “Start replication”  it give me a error, The Table isn’t in the Datadicctionary.

    Maybe someone had the same Problem ?

    Thanks,

    Juan

    (0) 
  10. Former Member

    Hi,

    We want to maintain the mapping of object in the source system instead of Target system (S/4). Can we maintain the mapping in source system and execute the SLT and do the transformation in SLT and avoid building custom tables in S/4 system?

    Regards,

    Vikash

    (0) 

Leave a Reply