Source System(Logical system) issue

Hi All,
Recently we have done QA refresh & copied with production data.
For 0vendor master data we are extracting data from ECC source system. When I was trying to execute the DTP it is pointing older source system. We tried to create new DTP but when I'm executing still it is showing older system.
By using RSBKDTP_BDLS program I forcefully tried to convert old source system to new source system but we are unable to solve this issue.
Here I'm attaching the issue .Please help on this issue.
Best Regards,
Sammar.K

Hi Ram,
I have compared Production & QA system entry's in RSLOGSYSMAP Table.
in prd system
source       target
qa6            prb01
in qa system
source       target
qa6             qa6
we found in qa it is pointing wrong target.
Regards,
Sammar.K

Similar Messages

Prod source system issue

Dear All,
I have an issue in production system.
We applied a patch in BI prod and r3 prod for data lineage...but after that all process chains failed when i checked in source system connection ...there was no connection..
Now i want to restore my r3 prod source system in BI system Please tell me how to do that.
regards
shweta

Hello,
First check in SM59 whether the connection for the source system exits. If it does not then contact the BASIS team for connection.
If the connection is fine, then you can right click on the source system in BI and choose restore option.
But beware restoring with set the timestamp for all the datasources for that source system.
It will take time as it will replicate and activate all the datasources.
Regards,
Shashank

Source system issues post BW System Copy

Hi Team,
Post BW System Copy, we have observed that the RFC connection has changed.
However the Target Host port is maintained same as the required source system...
While checking the Connection, we are getting the following error messages:
@5C@     Port description contains errors: Incorrect destination MR0CLNT200     RSAR     669
@5C@     BI unknown in source system     RSAR     8
@5C@     BI IDoc type ZSMA002 is not the same as source system IDoc type     RSAR     371
@5C@     The following errors occurred in the source system:     RSAR     374
@5C@     EDI: Partner profile not available     E0     332
@5C@     Entry in inbound table not found     E0     414
@5C@     Entry in outbound table not found     E0     400
@5C@     Entry in outbound table not found     E0     400
@5D@     Destination MP0CLNT200 has incorrect Unicode setting; adjust it to destination     RSAR     673
Please advice.
Thanks & Regards
Sneha
Edited by: Sneha Santhanakrishnan on Mar 23, 2011 2:12 PM
Edited by: Sneha Santhanakrishnan on Mar 23, 2011 3:04 PM

Hi Arun,
Thanks..
Your solution worked for all the datasources except one wherin I am getting a error message while activating the Transformation as "System setting does not allow changes to be made to the object XXXXXXX"
Please note the Transformation is in the ACTIVE but NOT EXECUTABLE state.
Find below the details description on the issue.
Message no. TO128
Diagnosis
The system and namespace change option set for this SAP System does not allow any changes to be made to object RSFO 4L8RD1B5MKEQI3WSPE5S8MR2O.
System Response
Editing is terminated, the object can only be displayed.
Procedure
If you want to edit the object RSFO 4L8RD1B5MKEQI3WSPE5S8MR2O in this SAP System, have your system administator set the SAP System to "modifiable" for this object.
This can affect the modifiability of the namespace &1 or the namespaces that correspond to the pattern &1, as well as the global setting of the system change option.
The system change option is set using the Transport Organizer tools (Transaction SE03). Expand the Administration node and execute the program Set system change option. The options are described there.

New Source System Issue

Hi
We are trying to connect new Source System to BW. It is ECC 5.0.
When I try to activate the Source System, it generates the following error:
<b>EDI: Partner profile not available
Entry in inbound table not found
Entry in outbound table not found
Entry in outbound table not found</b>
I checked WE20, it looks good. This is very similar to the current R/3 System (4.6). I was able to REPLICATE the DATASOURCE with no issues.
Can you please let me know, how this could be resolved.
Regards,
GPK.

Hi Guru's
The OSS note mentioned was a good one. I did check that OSS to ensure we were on track. There was no loop hole i got in regards to this issue.
I cannot say why it worked for me but I could tell what I did.
1. Deleted the source system, I creted.
2. Created the Source System back again.
3. It worked, but the only difference I noted was that, the icon of the source system is like the BW and not like the r/3 icon. I don't know WHY??
Thank you all for your support and advices.
Regards,
GPK.

Process chain - Two source system issue

Hi Experts,
I face problem when i transport a process chain from BW DEV to Quality.
I have two source systems in Quality ECI and EXS.EXS is a sandbox server(Source system) which we no longer use.
When i transport the process chain from DEV to QA, i get two DTP's automatically added to Process chain in quality for two source systems ECI and EXS whereas i do not want the data to be loaded from EXS client.
I checked the BW dev system, it has only one DTP in the process chain.
Now I want to elminate the other DTP in the process chain in quality.
Please suggest.
Regards,
Srini

I Dont think so a DTP for EXS system has got created automatically when you transport the PC to QA (which actually doesn't exist in DEV).
Please check you DEV system once again, there might a DTP from EXS system also.. other wise go the Release TR and then check the contents-->iif you find two DTP's there then it is there in the dev system..
Any ways if you want to delete the other DTP from the PC in QA.. you can Delete it directly from the PC itself.. Goto change mode of the PC and then select the DTP which you want to delete-->then right click and hten Click on Remove Process -->then activate the PC..
Note: You might have authorization to edit the PC in QA then only you will be able to do the changes..

Multiple source system issue...

Hi,
We have two source system for BW Development and one source sytem for BWQ and BWP.
My query is: we have added two extra fields 0SOURCESYSTEM, 0FISCVARNT in the key fields to handle data from two different systems.
Do anyone have any more suggestion to handle such a scenario.
Suggestions will be highly appreciated.

Hi,
Incase if you are loading data from two sourcesytem ,you will have two data sources each representing one sourcesytem,then you can assign these to an infosurce with flexible update.
now you can craete two info packages for each source sytem and can load the data to the target
the steps may look something like this
replicate datasource1
replicate datasource2
create infosurce
assign datasource1 and datsource2 to infosurce
maintain transfer rules
under infosource
later create Ip for source1
create Ip for source2
crate target
create updaterules
map the infosoure to update rules
cheers,
Swapna.G

Source System Issue

Hi Gurus, I am getting "No matching FM area found" and "errors in the source system" when I try to load data thru an InfoPackage into PSA in BI7.0. This is newly installed BW DEV system for demo purposes.
I have checked that the latest SP13 are installed. SPRO settings are intact. I was wondering where the problem is. Please guide in this matter. Thnx

Hi SniffBW,
The error you are getting is from Funds Management (That's what FM means, is not function module).
Check this link: http://help.sap.com/saphelp_nw70/helpdata/EN/1a/8c425e8afe11d496d80000e835339d/frameset.htm
You need to enter a FM area as a parameter for the extraction.
Hope this helps.
Regards,
Diego

Error in the source systen with app log in source system

Hi experts
I am running a full load for 0HR_PT_2(Actual Personnel Times ).this load is loading the data and says no errors occurred and write an app log in source sytem saying
Extraction date for personnel number 00000000 set to 20081231.
I have tried to select the data selection of personnel no from
00000001 to 99999999.
but it still gives me the same warning.
please help me in solving.
thanking you
satish

Hi Satish,
Were you able to fix the application log in source system issue ? I am also facing the same problem for 0HR_PT_2 .
plz let me know.
Points will be awarded .

Job is not in Active mode, still in Ready mode in the source system

Hi Folks,
Process Chain carrying some data loads asusally today also, i noticed there is no action in the details tabs, then i checked in the source sytem, jobs in ready mode. why it is turned like this.
Can any one provide your valuable inputs on this...
Thanks,
V

Hi ,
Thanks for your quick responce on this..
My issue has been resolved: Issue occured due to in the source system issue. All BW job has been scheduled in one particular application server which is facing more than issue.
Basis team involved and resolved them.

Creating Source systems in two same logical BW systems from single R/3 sys

Hi All,
We are facing an issue while creating Source systems in two same logical BW systems, from single R/3 systems. Our Basis team is telling that if we want to connect the single R/3 system into 2 BW systems with same logical name, we will need to delete the source systems from one BW systems and create in another system. Also they told by doing so it will delete all the transfer rules and PSA table existing in the current BW system, which has the source system connectivity with the R3 system now.
Is this anyway to create the same source systems in two same logical BW systems, from single R/3 systems without deleting the transfer rules?. Also please help us to get anu OSS note or document explaining this in details.
Regards.
Muruganand.K

Hi Muruganand,
I dont think it is possible as connecting one R/3 Source System to two BW Systems.
If you could get the possible solution, please do reply to the post.
Regards,
Kiran

Source system connection issues

Hello BI Experts,
We had issues with the source system connection - from our BI system (NW 04s) to our R/3 system (ECC 6.0) .
From RSA1, when we right click on the R3 source sytem and do a "Check", it was erroring out: "Error in source system <Logsysname1>". This Logsysname1 was different one from the actual R/3 system's Logsys name (Logsysname2) .
To Fix this, we restored the connection by selecting the (R/3) Source system and right click and "Restore".
After providing the passwords for the RFC users, the system again asked "The Connection <XY> is used in the <Logsysname1> Source system as a connection." And we selected the "Delete" option here. Then in the Logon screen to R/3, we provided the administrator user Id and password.
Once the source system connection is complete, we checked the connection as mentioned above and the "Source Sytem connection is OK" now.
(1) But now, in the transaction RSA1, the R/3 system is displayed under "BI" instead of "SAP".
(2) When we asked our BI consultant to check the dataloads, he encountered an error: "No transfer structure is available for InfoSource <X> in the Source system. Errors in Source system".
How can we bring the R/3 system under "SAP" now?
If we delete the R/3 system (which is listed under BI) and recreate under "SAP", will the transfer rules will also get deleted?? How to avoid this issue?
Please advise.
John
SAP Basis.

Hi,
Please make sure that you have followed the below steps while creating the Source System
1.     In the initial screen of the source system, choose Tools ® Administration ® User Maintenance ® Users and create a background user with a password and the authorization profile S_BI-WX_RFC.
2.     Define the RFC destination parameters for the SAP source system in BW. To do this, choose Tools ® Administration ® Administration ® Network ® RFC Destinations in BW.
Enter the information taken from the source system on the server name.
u2022     Application server: pswdf090
u2022     System ID: IDF
u2022     System number: 90
The destination name has to correspond to the logical name of the source system that you entered for the process step Define Logical System in the implementation guide for the source system. For user and password, enter the background user that you created in step 1.
3.     Define the RFC destination parameters for the SAP BW in the source system. To do this, select Tools ® Administration ® Administration ® Network ® RFC Destinations in the source system. Enter the server name information taken from the BW system.
The destination name has to correspond to the logical name of the BW system that you entered in the process step Define Logical System in the BW Customizing Implementation Guide. ALE communicates using the name of the SAP Business Information Warehouse that you defined. The defined name represents how the SAP Business Information Warehouse is identified. For the user and password, enter the background user that you defined in the BW Customizing Implementation Guide under Business Information Warehouse ® Links to Other Systems ® Link Between SAP Systems and BW.
4.     Test both RFC destinations with the functions Test ® Connection and Test ® Authorization.
If an error occurs during the authorization check, the background user is not permitted in this client and with this password. If an error occurs in the connection test, it means there is a network problem.
5.     In the BW Administrator Workbench choose SOURCESYSTEMTREE ® Root ® Context Menu (right mouse button) ®Create and select the radio button for the manually creating an SAP source system.
6.     Enter a description for the source system and the logical name of the source system that you entered for the process step Maintain Logical System in the source system implementation guide.
If you still have any issues, let us know.
Regards,
Yogesh.

RSA1 - Source system(R3 - BI) restore issue

HI Everyone,
I am trying to restore my source system(R3) from BI from RSA1. iam getting some error.
Error:
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system SAPSQ1 does not accept any of the proposed values.
The last proposed value was BA.
System Response
Source system has not been connected.
Procedure
If you want to recreate the source system from BI information, then you can only use a single value, namely BA, because the connection already has this name in BI.
Delete the existing connections in the source system or contact a BI consultant.
I checked the table RSBASIDOC also. The Target BI logical system is not present. CHecked the partner profile & IDOC Ports also.
RFC connection is also working fine
We recently performed R3 system refresh
please help me resolve this issue since its a critical issue which neds to be resolved immediately
thanks & Regards,
Siva

If you have done system refresh then to restore the connections you have to follow the below note as per your scenario
Note 886102 - System Landscape Copy for SAP NetWeaver BW
Only then the connection can be restored

BDLS for conversion of logical source system name

Hello All,
I am trying to reassign a new source system NEW1 by replacing old source system OLD1 using BDLS in the source system.
But the NEW source system logical system name already exists as I created it . Can I delete the new source system and then use BDLS?
How do I make sure that the reassignment happens correctly?
And what precautions should be taken to avoid further consequences?
Regards,
NIKEKAB

BDLS does a pretty good job... Never had issues with it when using it... Always execute a test run, look for warnings or errors...
Yes, you can delete the source system before doing BDLS... I assume, since it is new, nothing is connected to it...
You always will have to check RFC connections, datasources replicas, rules, etc, once the conversion is done...
Make sure you take a look at note 886102, it has very good information and make reference to other relevant notes specific for BDLS, like 121163, 369759, etc... Read the notes carefully, follow the steps and you'll be fine...
Once everything is done and in place, you shouldn't have any surprises in the future... It's just normal maintenance...
Good luck...

BI Source system (critical issue)

Hi Friends,
I am working as a basis consultant.
we have a ECC6 Development server and in the same server we hav installed BI-Cont and using as a BI Dev sever too.
Client - 400 is R/3 Develop server
Client - 300 is BI Develop server
we cofigured 400 client as a source system for bi(300) and lot of develpments are made.
Now we are planning to make this ECC6 DEV as a Production server for BI. (simultaniously R/3 developments also will happen in the same server).
Now i have Created a new client-500 for BI(Production) in the same server and i want to add our R/3 Production server client-900(different server) as a Source system.
1 I maintained RS_MANDT_UNIQUE_SET and set to client 500.
2 I maintained table RSADMINA and set client 500
and BW_user
3 Created RFC between client 500 to PRD server client 900
now when i tried RSA1 Transaction in BI PRD client 500, it says "Logical system name has been changed for this system" "Message no. R3206"
when i see the long text it says
"The logical system name of this system is PRDCLNT500. However, this system was originally created with the logical system name DEVCLNT300. It is not permitted to change the logical system name, as connections to other systems will be damaged beyond repair.
System Response
The transaction is canceled.
Procedure
Change the name of the logical system (table T000) for client back to DEVCLNT300. This enables you to continue working with the system.
If you really want to change the logical name, than you can, if and when you:
change the system name back to DEVCLNT300,
delete all existing connections between this system and other systems,
delete all transfer structures that still exist, and
do not use ALE or Workflow."
1 I tried to remove the source system from 300, but it is prompting to delete lot of packages and it is going for a while. so i stopped it.
2 I removed all the RFC Connections between 300-400
3 I deleted the logical system "DEVCLNT300".
Still the same Issue "Logical system name has been changed for this system".
Please help me Resolving this issue, since this issue became so critical.
Thanks in advance
Prakash

Thank you for Replying
I know the landscape we are having will confuse.
In ECC6 DEV Server a new client 500 is created for BI Producion server (not exactly prod but assume like that).
There is seperate R/3 Production server (client-900) and that shud be configured as a source system for the new BI PRD Client 500.
I dont want any data from 300, infact i would delete the 300client (BIdevclt) after i configure everything in client 500.
I did all the BI post installation steps for client 500.( including RS_MANDT_UNIQUE_SET)
but since the 300 client was configured as BW dev in the same server, i am getting an error if i access RSA1 in client 500 "Logical system name has been changed for this system" "Message no. R3206"
I went through the BDLSS transaction, but it talks about converting logical system and i dont want to do that.
Client400 is configured as source system for bi dev 300. I want to delete all the configuration made in 300.
I want to know deleting the souce client manually from BI dev 300 client is the only way to fix this or anything else we could do it for this ERROR.

Issues on Sources System ECC and BI

Dear Friends,
I m trying to get datas (extractions) from ECC 6.0 QA 110 to BI DEV 100. But I only have the Source System to the ECC 6.0 DEV without any data, this connections is working very well. I asked the Basis Consultant to do another connection of the BI DEV 100 with the ECC 6.0 QA 110 using RFC connections with Bitemote with sapall, between ECC and BI. He already did it and I can see at SPRO under SAP NetWeaver > SAP BIW > Links to Other Systems > General Connection Setting > Assign Logical System to Client, on both sides in BI and ECC. The question is, do I need to do Any configuration at the BI side to active (create?) this new Source System ECC 6.0 QA 110? I hope Im clear. Thanks in advance.
Antony

Hi Frank,
I can't imagine any issues compared to other installations. The only thing you need to take care about is that in BI you can only work in one client and in your ecc system you can have multiple clients to work in. These will be treaten as different source systems for your bw.
regards
Siggi

Source System(Logical system) issue

Similar Messages

Maybe you are looking for