Replication Timeout in Source System

When we try to replicate source system for ECC it times out in ECC.
We start replication in background in the BI system but it triggers a
job in ECC which times out as per the time out parameter set in ECC for dialog processes. Is there a way we can trigger background work process in ECC when we replicate data in BI.
ThanksAsad

hi,
   Basis team side they are saying that every thing is ok. today when i trigger the info package at background job , after extracting 37 lakh records , i got the same error that is
under details tab
Data Package 1 : arrived in BW ; Processing : Processing not yet finished, entry 70 still missing ,
this message for data package 2 also and
Data Package 151 : arrived in BW ; Processing : Selected number does not agree with transferred n
this message for data package 152, 153, 154,155.
under status tab the error message is
     *Error during import of results for employee 00004000     *
     *Errors in source system ( Message no. RSM340)     *
I find one thing that when i gave selection on employee number i got the data into psa with out any error but when i gave date as selection at infopackage level i got tha same above error.
Edited by: Srikanth.T on Feb 28, 2012 12:55 PM

Similar Messages

Replication RSDS and Source systems

What is the difference between the RSDS and choosing the Source systems and right click to do the replication?

would think then that Basis did the replication for 3.X datasources when they did the installation. Therefore, no prompt for selection. - correct
When I created the View and then the generic datsasource from RSO2, I used the Source system to replicate and it was doing the 3.X replication. Therefore, I was not able to see the datasource to do the assignment. -
Which I'm not sure of , no matter what kind of Ds it is/or has been replicated as (3.x or 7) it should show in the datasource tab, moreover the 3.x DS will have a small square beside the displayed name of the DS. might be there is some settings out there which enables us to see it. If so i'm not aware of it.
Is is a correct observation? - Not sure, on my system I can see all the DS no matter what kind they are.
I am trying to find reasons why when I used the Source system, right click to replicate it, it didn't show the datasource but when I did the RSDS it did.
you need to replicate before you can see the DS in RSDS. So ur replication did take place but just wasnt visisble

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

Restore source system without replication

Hi,
Normally one would do a restore of a source system after it has been refreshed with RSA1.
The "downside" is that it also do a replication of the datasources.
We want to split the procedure and do the restore of the source system without replication and the replication itself separately. Are there any transactions, FMs, reports, ... to achieve these tasks separately?
Eddy

Eddy,
I found out about that, but i never tried it, it is an interesting program, but i don't know how if it will ask whether a datasource need to be 3.x or 7. I guess if you execute as a background job it will not ask.
Regards,
Jorge Diogo

Problem in activating datasource after replication from source system

Hi Experts,
After replication of data sources from source system ,I get all data sources inactive. I tried to make it active manually but every time I get
Syntax error in GP_ERR_RSAPTD1, row 27 (-> long text)
    Message no. RG102
Diagnosis
    Field "/BIC/CCZVBAK2031" is unknown. It is neither in one of the
    specified tables nor defi...
How do I go about solving this problem....Any advise please...

Hello,
You do not mention your source system release but can you execute the check report
described in the SAP note 493422 , if this does not resolve the problem can you goto
RSA1, right click on the relevant "source system" and choose the "restore" option,
then please try and replicate and activate the datasource again.
If you have BW release 7.0 please check that the note 929751is applied in your system
or that you are on a higher support package level.
If there is still a problem please le me know your BW Release and Support package level.
Best Regards,
Des

Source system restore timeout

Hi guys,
I am trying to do a source system restore, but after about an hour it times-out and it doesn't complete the transfer structure restore across to BI.
Can anyone help on how to get around this?
Thanks in advance, points will be awarded.

Can you please explain more on ur question. What is the requirement.

Source system replication in BI 7.0

Hello All,
I want to replicate my datasource(for function module Generic extraction) in BI 7.0 system
I have replicated datasource in BI 7.....
Now when I want to create transformation....I selected my datasource and Source system(R/3)......but its giving a msg
Source not active
kindly suggest ...
Thanks in advance,
Sonu

Hi,
Check
1. in rsa1>source system>select your source system-->right click ->check
2.Rsa1>Tools->Source system Mapping in Bw
3.In sm59 tcode you can check the source system status.
If you find ther is no connection b/w Source and BW
Just Right click your sourcesystem (as in point1) -->go to Restore.(you can take the help of Basis team for this settings)
Regards
Hari

Error in Source system (Job is not going in to job log of CRM system)

Hi,
We replicated datasources from CRM server in BI 7 server and they get replicated and are in Active version
All transactiond atasources which are 7.0 version are executing successfully, but the Datasources which are in 3.5 version i.e. Datasource for master data infoobject gives error while executing infopackage.
The error message is as follows:
"Diagnosis
     In the source system, there is no transfer structure available for
     InfoSource 0CRM_MKTMETA_ATTR .
System Response
     The data transfer is terminated.
Procedure
     In the Administrator Workbench, regenerate from this source system the
     transfer structure for InfoSource 0CRM_MKTMETA_ATTR ."
Also while executing the infopackage the job log in source system is not able to create the corresponding job.
Following action are already been taken:
1. Datasource replication
2. Confirmed that the Transfer Structure are avialable and are in ACTIVE state.

Hi
It seems some changes are taken place at Source System for the Mast.Data DS. Try to Recheck the Same at Source System -- Activate/Retranport the same.
BI side.
RSA13Source System Your DS-- Replicate the Data Source -- Try to Run RS_TRANSTRUC_ACTIVATE_ALL(SE38) / Activate Transfer Rules Manually -- Then Full/Re Init -- Delta Uploads
Hope it helps and clear

Error when activate a SAP source system

Hello Experts,
I have an issue when I try to create a new SAP source system but I cannot complete this operation because a Timeout error occurs when the system made the destiny verification, the source system can be created but not activated, I already create the RFC connection and they are OK, I add the new logical system of the source system in the configuration (SBIW) in the general settings,and the data source tree is show succesfully and sems to work OK and the data sources seems to be OK too.
In the RSA1 transaction, go to source systems tree, choose the SAP source system called: "conexion a dev 200" -> right click and choose activate and the error occurs.
I have a Myself source system already created and activated, I cannot find the source of the problems thata cause the timeout error in the new source system.
Thank you vey much in advance,
Niurka

Yes, I try ti use the create automatically option first but it doesn't work, because says that we system already exists because here exist a myself source system with an RFC to R/# ( I don't know why), so I must use the manually creation option, I put the logical system, and all the requeriments of the screem. The system create the source system but when I try ti activate it, it is impossible to do it....!
I hope that you can give some tips or solution for this issue,
Thanks!

Source system BIDCLNT600 / ECCDEV210 does not exist

Hi all,
While transporting the BI dev transports to BI prod ,
I am facing the subjected error saying "
Source system ECCDEV210 does not exist
Source system BIDCLNT600 does not exist
Regards
Venkat

Hi,
I maintained the settings in BI Prod like:
Original Source System : ECCDEV210 (R/3 Dev)
Target Source System : ECCPRD400 (R/3 Prod)
But I am facing the other problems like:
1. Field ERDAT will not be delivered from DataSource 0WBS_ELEMT_ATTR in source system ECCPRD400
2. DataSource 0WBS_ELEMT_TEXT does not exist in source system ECCPRD400 of version A
3. Mapping between data source 0WBS_ELEMT_TEXT and source system ECCPRD400 is inconsistent
4. Reference to transfer structure 0BILBLK_DL_TEXT_BB not available. No activation possible.
5. Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Activation Mode)
6. Start of the after-import method RS_CUBE_AFTER_IMPORT for object type(s) CUBE (Delete Mode)
Like these so many repetitions in each area.
For the information:
1. I opened the R/3 prod system , activate the data sources (standard using RSA5) and replicated into the BI prod system.
So,whatever I activated in R/3 prod are available in BI prod after replication. After that I send the transport request. But I have not transported any request from R/3 Dev system to R/3 Prod system with the data sources.
2. I created the transport request based on Info cubes. First, In data flow before option and next request with " In data flow after " option and collection mode is " automatically"
Pl advice me.
Regards
Venkat

Source system ECQCLNT320 does not exist in BI Production

Hi,
When i am transporting the BI objects along with the datasources it is giving the following error.
our system Landscape:
BI Dev. & BI Qty Same Box
ECC Dev.
ECC Qty
ECC Prd.
in our landscape BI dev and BI Quality are the same Box, i am transporting BI cube objects along with ECC quality system datasources from BI dev. system. But when we import the cube request the following error is occuring.
Please help me as i am in typical stage.
ERROR: Start of the after-import method RS_RSDS_AFTER_IMPORT for object type(s) RSDS (Activation Mode)
Source system ECQCLNT320 does not exist
Can we transport the ECQ datasources from BI dev system where i am using them.
Thanks,
Baswa

Hi,
RC on ECQCLNT320 check the source connection under sourcesystem tab in Rsa1,it might having issue else
Check in the RSA6 (Sourcesystem) wether DataSource is active mode or not ,
Go to Tcode RSDS for Replication of DataSource in BW system .
Regards,
Satya

About creating a new source system on BW pointing to an Oracle database

hi friends
i m facing problems when i
creating a new source system on BW in AIX pointing to an Oracle database, our bw oracle use 10idatabase ,and we want to connet to 9idatabase(Windows) to get data for BW
(1.)     in /oracle/P01/102_64/network/admin tnsnames.ora I hava add
SJPT =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 68.16.211.177)(PORT = 1521))
    (CONNECT_DATA =
      (SERVICE_NAME = SJPT)
(2) and in etc/hosts I hava add
68.16.211.177 SJPT
(3) in p01adm> tnsping SJPT it is OK
(4)but when i
in BW RSA1 DATA SOURCE
create db connect:
DBMS: ORA
USER NAME: SAP
DB PASSWORD: SAP
[email protected]
i t give me the error message :
ORA-12154: TNS:could not resolve the connect identifier
please help me

HI,my trans.log file is
4 ETW000 R3trans version 6.13 (release 700 - 20.02.06 - 16:15:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 13.11.2007 - 10:16:48
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Tue Nov 13 10:16:48 2007                              81 0.000081
4 ETW000 [dev trc     ,00000] db_con_init called                                    29 0.000110
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                             50 0.000160
4 ETW000 [dev trc     ,00000] Loading DB library '/usr/sap/P01/SYS/exe/run/dboraslib.o' ...
4 ETW000                                                                              43 0.000203
4 ETW000 [dev trc     ,00000] load shared library (/usr/sap/P01/SYS/exe/run/dboraslib.o), hdl 0
4 ETW000                                                                           13346 0.013549
4 ETW000 [dev trc     ,00000] Library '/usr/sap/P01/SYS/exe/run/dboraslib.o' loaded
4 ETW000                                                                              32 0.013581
4 ETW000 [dev trc     ,00000] function DbSlExpFuns loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
4 ETW000                                                                              35 0.013616
4 ETW000 [dev trc     ,00000] Version of '/usr/sap/P01/SYS/exe/run/dboraslib.o' is "700.08", patchlevel (0.46)
4 ETW000                                                                              53 0.013669
4 ETW000 [dev trc     ,00000] function dsql_db_init loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
4 ETW000                                                                              34 0.013703
4 ETW000 [dev trc     ,00000] function dbdd_exp_funs loaded from library /usr/sap/P01/SYS/exe/run/dboraslib.o
4 ETW000                                                                              53 0.013756
4 ETW000 [dev trc     ,00000] New connection 0 created                              23 0.013779
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              39 0.013818
4 ETW000 [dev trc     ,00000] db_con_connect (con_name=R/3)                         45 0.013863
4 ETW000 [dev trc     ,00000] find_con_by_name found the following connection for reuse:
4 ETW000                                                                              32 0.013895
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              37 0.013932
4 ETW000 [dev trc     ,00000] Got LIBPATH=/usr/lib:/lib:/usr/sap/P01/SYS/exe/run:/oracle/P01/102_64/lib from environment
4 ETW000                                                                             325 0.014257
4 ETW000 [dev trc     ,00000] -->oci_initialize (con_hdl=0)                         47 0.014304
4 ETW000 [dev trc     ,00000] Client NLS settings: AMERICAN_AMERICA.UTF8          3234 0.017538
4 ETW000 [dev trc     ,00000] Logon as OPS$-user to get SAPSR3's password           28 0.017566
4 ETW000 [dev trc     ,00000] Connecting as /@P01 on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000                                                                              34 0.017600
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              35 0.017635
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x110f8b9c0 0x110fa3e38 0x110fa36e8
4 ETW000                                                                              36 0.017671
4 ETW000 [dev trc     ,00000] Allocating service context handle for con_hdl=0       37 0.017708
4 ETW000 [dev trc     ,00000] Allocating server context handle                      24 0.017732
4 ETW000 [dev trc     ,00000] Attaching to DB Server P01 (con_hdl=0,svchp=0x110f94398,svrhp=0x110fa6158)
4 ETW000                                                                              72 0.017804
4 ETW000 [dev trc     ,00000] Assigning server context 0x110fa6158 to service context 0x110f94398
4 ETW000                                                                           36191 0.053995
4 ETW000 [dev trc     ,00000] Allocating user session handle                        73 0.054068
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=0x110f94398,srvhp=0x110fa6158,usrhp=0x110f937a0)
4 ETW000                                                                              43 0.054111
4 ETW000 [dev trc     ,00000] Assigning user session 0x110f937a0 to service context 0x110f94398
4 ETW000                                                                           10613 0.064724
4 ETW000 [dev trc     ,00000] Now '/@P01' is connected (con_hdl 0, nls_hdl 0).
4 ETW000                                                                             964 0.065688
4 ETW000 [dbsloci.    ,00000] *** ERROR => ORA-942 when accessing table SAPUSER
4 ETW000                                                                            1183 0.066871
4 ETW000 [dev trc     ,00000] Disconnecting from connection 0 ...                   73 0.066944
4 ETW000 [dev trc     ,00000] Rolling back transaction ...                          28 0.066972
4 ETW000 [dev trc     ,00000] Closing user session (con_hdl=0,svchp=0x110f94398,usrhp=0x110f937a0)
4 ETW000                                                                             146 0.067118
4 ETW000 [dev trc     ,00000] Now I'm disconnected from ORACLE                     409 0.067527
4 ETW000 [dev trc     ,00000] Try to connect with default password                  23 0.067550
4 ETW000 [dev trc     ,00000] Connecting as SAPSR3/<pwd>@P01 on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
4 ETW000                                                                              34 0.067584
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              36 0.067620
4 ETW000 [dev trc     ,00000]    0 UTF8                                                      1 0x110f8b9c0 0x110fa3e38 0x110fa36e8
4 ETW000                                                                              36 0.067656
4 ETW000 [dev trc     ,00000] Assigning username to user session 0x110f937a0        22 0.067678
4 ETW000 [dev trc     ,00000] Assigning password to user session 0x110f937a0        41 0.067719
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=0x110f94398,srvhp=0x110fa6158,usrhp=0x110f937a0)
4 ETW000                                                                              37 0.067756
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000                                                                           33690 0.101446
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000                                                                              36 0.101482
4 ETW000 [dblink      ,00431] ***LOG BY2=>sql error 1017   performing CON [dblink#3 @ 431]
4 ETW000                                                                             122 0.101604
4 ETW000 [dblink      ,00431] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#3 @ 431]
4 ETW000                                                                              34 0.101638
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'P01'"

Multiple usage of Source System is not possible with installed DMIS version on source

Hello folks!
I`ve got a problem trying to adjust the Data Replication to SAP BW (on HANA) using SAP LT Replication Server.
I`ve deleted one connection and after that I`m trying to create new one through Configuration & Monitoring Dashboard (transaction LTR) with the same source / target systems.
As result when on the second step (Specify Source System) I specify RFC destination of the source system it appears an error with text
"Multiple usage of Source System is not possible with installed DMIS version on source".
But there`s no any adjusted connection in system now..
Please, help me to understand how to fix that problem, I can`t find a solution

Hi,
When you say that you 'deleted one connection', did you delete the RFC connection or the SLT Configuration? If it is not a real multiple usage scenario, then deactivate the 'allow multiple usage' flag, else install the correct DMIS version on both SLT and source.
Thanks
kris

BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0

Background:
I am relatively new to BW team and will be going through my 1st source system upgrade.
We currently have BI 7.0 SPS 17 connected to source system R/3 Enterprise EP1.
We are upgrading to the source system to ECC 6.0.
In Development and QA Environments:
we will have access to both old (R/3 Enterpirse) and the new (ECC 6.0) source systems.
We have a opportunity to compare the BW Objects, data flow and data loading from
both source systems.
In Production, however, we will just upgrade over 3 days downtime.
One Question that comes to mind in this regard...
What sort of things, we should be checking for before and after upgrade in Dev/QA and in Prod environments and what tools are available that can help the analysis and validation process ?
Some of the suggestions that were given to me include following points.
Before Upgrade:
1 Check data, taking pre images of it for testing with post upgrade.
2. Perform proper analysis of Source system related BW objects.
- A complete listing of actively used Datasources,.. etc.
3. Make delta queues empty,
Make sure that all existing deltas are loaded into BW.The last request delta must not deliver any data and must be green in the monitor.
4. Stop Process chains from BI (remove from schedule) and collection runs from R/3 side
After Upgrade:
1 After the OLTP upgrade, refer to note 458305 and other notes that are relevant to the actual upgrade
(depending on the R/3 system release / R/3 plug-in to BI plug-in compatibility).
2. Check logical system connections. Transactions SMQS, RSMO and SM59, If no access, then we can use Program RSRFCPIN_NEW for RFC Test.
3. Check and/or Activate control parameters for data transfer. SBIW ---> General Settings --->
Maintain Control Parameters for Data Transfer
http://help.sap.com/saphelp_nw70/helpdata/EN/51/85d6cf842825469a51b9a666442339/frameset.htm
4. Check for Changes to extract structures in LBWE Customizing Cockpit
- OSS Notes 328181, 396647, 380078 and 762951
5. Check if all the required transfer structures are active. See OSS Note 324520 for mass activation.
7. Check if all Source system related BW Objects are active - Transfer rules, Communication rules, update rules,DTPs,..etc.
Below is a link for some useful programs in this regard.
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action&pageid=35458
6. Test all important datasources using RSA3 and check for OLTP Datasources changes .
As soon as BW notices that the time stamp at the DataSource in the OLTP is newer than the one in the transfer structure, it requests replication of the DataSource and activation of the transfer structure. Transfer the relevant DataSources only if required, and transfer only the ones that have changed (RSA5 -> Delta).
7. Create Data flow objects (trnasfer rules, infopackages, trnasformations, DTPs) for the Replicate
new/changed datasources,if needed.
8. Check all CMOD enhancements.
If we are using a customer exit with the extractor in the OLTP, see Note 393492.
7. Check for unicode (all custom programs or Function Modules for DataSources)
5. Check all the queues in RSA7, start delta runs and test data consistency.
For delta problems:In the BW system, start the 'RSSM_OLTP_INIT_DELTA_UPDATE' program for the DataSource and the source (OLTP) system for which the init selections are then transferred from BW into the ROOSPRMSC and ROOSPRMSF tables in the source system so that the delta can continue.
9. Take back up of data posted during upgrade for contingency planing.
10. Run the entire set of process chains once if possible and let it pick up no data or the usual master data.
Since we have lot of experts in this forum, who have probably gone through such scenario many times, i wanted to request you to Please Please advise if i have stated anything incorrectly or if i am missing additional steps, OSS Notes, important details...

Thanks Rav for your detailed post and very helpful contribution by posting all the information you had regarding the upgrade.
We have similar scenario -
We are upgrading our source system from 4.7 to ECC 6.0. We have our BI system with BI 7.0 at support pack 19 (SAPKW70019).
Our strategy in ECC deployment ->
In development we copied our old DEV 4.7 system DXX to new ECC system DXY (new system ID).
In production we are going to use same system PRXX upgraded from 4.7 to ECC.
Now we are in testing phase of ECC with all interfaces like BI in Dev.
My questions are below ->
How can we change/transfer mapping of all our datasources in Dev BW system BID to new ECC dev system DXY (Eg. Logical system LOGDXY0040) from Old dev system DXX (Eg. Logical system LOGDXX0040). We donot want to create new datasources or change all transfer rules/Infosources for old BW3.x solutions on our BI.
Also in new ECC sourcesystem copy we see all datasources in Red in RSA7 transaction. Do we need to initialize again all the datasources from our BW BID system.
Is there any easy way for above scenario ?
Please let me know if you have any further helpful information during your ECC 6.0 upgrade connecting to BI 7.0 system.
I have found some other links which have some pieces of information regarding the topic -
Upgrade R/3 4.6C to ECC 6.0 already in BI 7.0
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/sap-r3-migration-and-sap-bw-version-1744205
BI 7.0: Source System upgrade from R/3 Enterprise to ECC 6.0
Re: ECC 6.0 Upgrade
Re: Impact of ECC 6.0 upgrade on BI/BW Environment.
ECC 5.0 to ECC 6.0 upgrade
Thanks
Prasanth

Problem Activating Source system RSAR 374, RSAR 375

Hi all,
Hoping you can help me with this issue. I have two
systems,one R/3 4.7 system and another BW 3.0B system.Both are recently installed. created user in client 800 on R/3. created user in client 100 on BW. i established RFC destination between both, Logical source system assignments and definitions of logical source systems on both. They are working correctly, But i couldnot succeed in creation of the source system. it gets created but it is not activated and ends with the following errors.
Message and the id next to it
1) The following errors occured in the source system. RSAR 374.
2) Result of the destination check: timeout . RSAR 375 .
when i try to activate it by right clicking on it , it does give these errors and activation gets terminated.
Can anyone pleaseeeeeeeeeeee with this. Thanks a lottttttt........
kishore karnati

Hi Kishore and Edwin,
I have exactly the same problem described here, except I am creating an ECC 6 source system in BI 7.
Therefore, I am wondering if you guys can elaborate on your experience.
I get the same error message RSAR 374 and RSAR 375.
I did both connection and authorization tests for the RFC in SM59 and it's OK.
What do you mean by the "basic concept of BWREMOTE AND ALEREMOTE background users."???
Please advise.
Cheers,
SJ

Replication Timeout in Source System

Similar Messages

Maybe you are looking for