new source system

[phil_moh]

We've just copied the BW Production system onto a new server (Test BW).

The BW Production is pointing to Production ECC6.

We're have created a new RFC in the Test BW, which point to Test ECC system.

We have also perform the source system conversion via BDLS.

In RSA1 ->Source System, I can see name of the source system has been changed to Test ECC6.

However, when I right click on Source System ->Connection Parameter, I can see that

the Source System is still linked to the old RFC which is pointing to the Production ECC6.

How can I change this RFC so that it is pointing to the new RFC that we just created?

Please help, thank you.

[phil_moh]

no answer

[Former Member]

thats not an error. even we got the same message and after we deleted and created the connection again it worked fine.

[phil_moh]

Ananda,

thats not an error. even we got the same message and after we deleted and created the connection again it worked fine.

The problem is like I says, if we delete the Source System, all the Datasource, InfoSource etc of the existing data modelling will be gone correct? (This is the scary thing that I dont dare to try as I am not sure...)

So if I delete it and re-create the source system, then perform Activate and Replicate, will it link back again?

Is this what we should be doing?

Please advise, thank you.

Edited by: lynn on Mar 11, 2010 1:58 AM

[Former Member]

Hi,

Is that ok to modify the table RSBASIDOC manually ? Is there an existing transaction for that ?

regards,

[Former Member]

Hi Lynn,

Pls do the following:

1) Go to SPRO --> 'Change source system name after transport'.

2) Enter the OrSource System as <ECC Production SS> and point the Target source system to the <New R/3 Source system>.

3) Reimport the Transport.

Hope this helps.

Regards,

Shrey

[Former Member]

Usually the username created will be like bwremote/r3remote/aleremote. if you want to change it you can do in sm59 and save it. after this step, all jobs will be trigerred using the new user you have assigned.

[phil_moh]

Exactly where/what need to be change in SM59? In ECC6 or BW?

I am trying to load some data now but failed.

I right-click the Source System ->Para Connection, and I can logon into ECC6.

I have perform the Check and Activate on the Source System, no error.

When I try to load the data (Full Load with 1 request), I hit following error:

Error message from the source system

Diagnosis
An error occurred in the source system.

System Response
Caller 09 contains an error message.

Further analysis:
The error occurred in Service API .
Refer to the error message.

Procedure
How you remove the error depends on the error message.

Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request

.

What is the problem?

[Former Member]

follow the steps given:

http://wiki.sdn.sap.com/wiki/display/HOME/Installations%2CSystemCopiesandMigrations

http://wiki.sdn.sap.com/wiki/display/SL/Technical+Implementation

[phil_moh]

Thanks for the info.

But I can't find any solution there... I am having loading problem, please help.

[Former Member]

your loading problem is because of the source system connection. have your basis people setup the source system connection.

check these notes:

325525 - Copying and renaming systems in a BW environment

184754 - Procedure after BW database copy

121163 - 'Converting logical system names',

524554 - 'Storing destinations in the BW environment',

[phil_moh]

My basic do not know and they dont maintain BW because they're not sure.

Based on your knowledge, what do you think could cause the connection problem?

[Former Member]

what is the error you are getting when you right click on soure system and give "Check".

Are you using the Test ECC by copying production ECC ?

After the system copy, did you run a INIT load?

Edited by: Ananda Theerthan on Mar 3, 2010 1:06 AM

[phil_moh]

I dont have any error message when I click Source System ->Check.

I copied the Production BW to a another server ->BW Test. Then I connect this BW Test to ECC Test.

This is how I do it:

1) create the ECC Test logical system in BW Test.

2) run BDLS convert the ECC Prod to ECC Test.

3) delete old RFC that point to ECC Prod.

4) create new RFC that point to ECC Test.

5) Perform Soruce System Check and Activate (RSA1 ->Source System), all OK.

But I can do the data loading.

[Former Member]

if you can load data where is the error you are facing?

[phil_moh]

In the PSA, I can see the Request is RED.

I have the following error message from the Request:

Error message from the source system

Diagnosis
An error occurred in the source system.

System Response
Caller 09 contains an error message.

Further analysis:
The error occurred in Service API .
Refer to the error message.

Procedure
How you remove the error depends on the error message.

Any idea?

[Former Member]

in the monitor screen, check the complete error message in status tab.you will find a button below the message, click on that to get the detailed message.

then goto details and see in which step you are getting the error(extraction/processing etc).

Or...

in the menu , Environment ->job overview->Source System and then also it will take u to R/3 side .

Check the job status...finished/cancelled etc.

If cancelled, then reload .

In any case, read the log what is getting displayed.

1.Please replicate and activate the data source in bw side under the appropriate source system

and then try loading.

or

2.In the processmonitor of the info package, (in details tab) when you right click on the red ststements and select displaying messages, there will be a question mark appearing at the right hand side.

or

3.check whether all the objects all active or not.

4.check if data source is active on R/3 side or not...if no...activate the same.and reload.

Is it happening for the first time...if yes...were there any transports on R/3 or BW containing these objects

5.Also, goto BD87, in both R/3 and BW side...check if there are any idocs stuck...if yes...manually process them...

6.Check in sm58 in R/3 or BW....if there are any entries there for this...if yes...select them and press F6...

Edited by: Ananda Theerthan on Mar 3, 2010 1:23 AM

Edited by: Ananda Theerthan on Mar 3, 2010 1:27 AM

[phil_moh]

Hi Anada,

In the monitor screen ->Error message status tab, I have the following error:

No transfer structure is available for InfoSource 0CO_AREA_TEXT in the source system
Message no. R3007

Diagnosis
In the source system, there is no transfer structure available for InfoSource 0CO_AREA_TEXT.

System Response
The data transfer is terminated.

Procedure
In the Administrator Workbench, regenerate from this source system the transfer structure for InfoSource 0CO_AREA_TEXT.

I logon to the soruce syste ->sm37, and couldn't find any BI_RE* job.

In Source System ->BD87, the IDOC RSRQST have the following error:

No transfer structure is available for InfoSource 0CO_AREA_TEXT in the source system

I have replicated the Soruce System but still having the same problem.

What could be wrong?

[Former Member]

first do all the basic checks..

check whether datasource replicated

check if its active

check transfer rules are active

check infosource.

it seems your transfer rules doesnt exists or not active.

right click on datasource->replicate

Edited by: Ananda Theerthan on Mar 3, 2010 3:54 AM

[phil_moh]

Hi Anada,

I performed the RSA1 ->Source System ->Replicate again and YES, I can do the loading now!!!

Question, when I perform the Replicate, does it mean it will replicate all the DataSource in Source System ->RSA6??

Please advise, thanks

[Former Member]

if you select source system and replicate, all datasources will be replicated,

if you right click specific datasource and replicate, only that DS will be replicated.

Hope your problem is resolved now.

[phil_moh]

if you select source system and replicate, all datasources will be replicated,

So this will replicate all the datasource in ECC ->RSA6, correct?

[Former Member]

first thing, if your connection check is alright why do you want to restore it. restore option is used to set the connection again to the source system. you generally use it when the system is refreshed so that the same old connection is maintained.

if you have further questions, refer the below notes:

886102,1333302,184447

Edited by: Ananda Theerthan on Mar 3, 2010 6:39 AM

[phil_moh]

In that case, I should not required to perform the Restore?

I thought Restore will re-connect the BW to ECC Dev?

Actually I still dont quite understand why we need Restore, can you please explain a bit more?

I have gone thru those notes.

[phil_moh]

Hi Anada,

Regarding the data loadin, yes, I can do the data loading but when I execute the InfoPackage, I have the following message:

Carry out repairs in non-original system only if they are urgen
Message no. TR850

Diagnosis
This SAP System is not the original system of the object being edited.

System Response
The function continues.

Procedure
Only perform urgen repairs and also maintain these changes in the original system of the object.

I click continue, then I can load the data.

Why I have this message?

Edited by: lynn on Mar 3, 2010 9:15 AM

[Former Member]

this is a standard information you get when you try to change any object . you have to click continue and proceed. there is nothing wrong in it.

[phil_moh]

Thanks Ananda, I will ignore the message then.

Back to the "Restore", you're saying we do the "Restore" only if client Refresh. Can you please explain a bit more on this? I think I have some understanding on it already but still not exactly sure, please help.

1) So when exactly we required to perform the Restore?

2) Why you say we need it only after client refresh?

3) I thought Restore will re-connect the BW to ECC Dev? In this case, if we happened to connect to new ECC, we should perform "Restore"?

4) Why when I perform the "Restore", I have the error as mentioned earlier?

Kindly help, thanks in advance.

[Former Member]

normally the restore option is used to establish connection after system refresh.

so if you copy a system and want to establish a connection , you should not use this option.

[phil_moh]

I think I am not clear between "Refresh" and "system copy".

Can you explain the different?

[Former Member]

lets say you have made a DEVsystem out of production and you have been using it for some time. now if you want to update this dev system with recent data, you refresh the system from production to get all latest data. in this case, the connectivity between BI and R/3 is lost. so you can choose the option "restore" to make the connection again to the same system to which the rfc is pointing to.

if you make a system copy, the target system logical name is changed and new rfc is to be maintained. so you dont use refresh in this case. you have to create a new source system connection.

[phil_moh]

Ananda,

Thanks for your simple but clear explanation on the "Refresh / Copy".

At the moment (after the system copy), we have not change the logical system on the target BW system (the target BW system - copied of Production BW) is still using the Production BW logical system name. What we have done on the target BW system so far are:

1) Delete the old RFC that is pointed to Production ECC6.

2) Create new RFC that is pointed to Dev ECC6.

3) Run BDLS to convert the source system (from Production ECC6 to Dev ECC6).

4) In ECC6, we entered the target BW + Dev ECC6 entry in table RSBASIDOC table manually as it is missing - dont know why.

5) Now in RSA1 ->Source Syste, I can Activate/Replicate the Datasource. I can also load the data from Dev ECC6 into this BW.

6) But we just can't perform the "Restore".

7) If I choose to Delete the Source System, isn't it will delete all the Datasource, Transfer Structure etc use in the Dataflow?

Please advise, thanks in advance.

[Former Member]

yes you are right..if you delete the source system you loose all datasources. since you are using same logical name restore is not needed..if you are able to load data then the connection is well established.only if your logical system name is different you need to create a new connection without using the restore option.

how did you connect your BW to dev ECC?

[phil_moh]

Ananda,

This is how I connect the BW (copied of Production BW) to ECC6 Dev system:

1) In BW, delete the old RFC that is pointed to Production ECC6.

2) Create new RFC that is pointed to Dev ECC6.

3) In Dev ECC6, create new RFC point to this BW.

4) Run BDLS to convert the source system (from Production ECC6 to Dev ECC6).

5) For some reason, the entry is missing is Dev ECC6 ->table RSBASIDOC table, so we added it manually - not sure correct?

Ok, since the loading is working so I dont need to perform the "Restore". But I still feel that there is a problem as I hits the mentioned error when I perform the "Restore".

[Former Member]

you can modify the table manually also.

[Former Member]

thanks a lot

[Former Member]

maintain new rfc connection in sm59

[phil_moh]

we've maintain the new RFC.

I then deleted the old RFC.

Now if I right-click on the Source System -> Para Connection, it is using the RFC that I created.

Question:

1) In BW, I have created a new RFC that point to ECC

2) In ECC, I have created a new RFC that point to BW

3) In BW, if i do the data extraction, I will be using the RFC created in Step 1 and logon into ECC. But how does the system know that we should use the RFC that I created in Step 2 to bring back the data from ECC into BW? Where is link?

Please advise, thank you.

[Former Member]

ECC will have one RFC pointing to BW.so the system automatically knows which connection to use. So guess, you have deleted the old rfc in ECC and created new.

[phil_moh]

Yes, I have deleted the old RFC.

Now in the RSA1 ->Source System, when I click on the Restore, I have a screen to enter the Background user.

Why the field Background user in source system is always defaulted as BWREMOTE?

I have created a new user call BWBKGUS in source system and used this in the RFC also.

How can we change so that it will default as BWBKGUS?

Please help.

[Former Member]

yes

[phil_moh]

In that case, I might just have replicated those Datasource that I do not want!!!

How can I delete this from the RSA1 ->Source System -> now?

Please help.

[Former Member]

you have to delete it manually..

[phil_moh]

but exactly how?

[Former Member]

right click -> delete

[phil_moh]

Ok, I have done that.

I have another serious problem:

1) In RSA1 ->Source System, when I do the Restore, it prompt me for the backgournd user and password.

2) I enter background user and password, and click continue.

3) Then the logon screen (ECC6) appeared. I enter background user again and click enter to logon into ECC. Then I have the following message:

RFC destination already exists in source system Do you want to use this destination, check, or cancel source system connection?

4)

I choose "Use".

4) Then I have the following message:

Connection EA is used in the ECCCLNT060
source system as a connection DBWCLNT060 to BW.


Do you want to delete this connection in the source system?
Connection Is Restored After It Has Been Deleted Successfully

I choosed "Do not Delete"

I can't perform the Restore. But I can do data loading. What's the problem?

[Former Member]

if you want to restore, you have to choose the delete option..

[phil_moh]

What does it mean?

Why do I need to delete it?

What exactly will be deleted?

Little background:

I copied this BW from Production BW, which is pointing to Production ECC.

Now we have do the BDLS to convert the logical system in BW, and connect to Dev ECC.

When I restore, will it retore to Production ECC again???

confuse.