Mapping of Source System Names

Hello,
Has some body done the mapping of Source System for "Transport" to go through which is done using the following steps:
RSA1 --> Tools --> Mapping of Source System Names(Conversion of source system name after transport)
You have to enter the source system name and target source source.
So if I have following Landscape
1) R3DEV -> R3QA --> R3QPROD --> R3Prod
2) BWDEV -> BWQA --> BWQPROD --> BWPROD.
What should be entries in the table
OrSource TargSrceSy
1) R3DEV R3QA
2) R3DEV R3QPROD
3) R3DEV R3Prod
4) BWDDEV BWQA
Thanks,
-Hari
5) BWDDEV BWQPROD
6) BWDDEV BWPROD
or
1) R3DEV R3QA
2) R3QA R3QPROD
3) R3QPROD R3Prod
4) BWDDEV BWQA
5) BWQA BWQPROD
6) BWQPROD BWPROD

Thanks A.H.P. So just a click clarification. My question is
So BWQPROD will contian
OrSource TargSrceSy
 R3DEV R3QPROD
OR
 R3QA R3QPROD.
Because my basis the transport path is as shown below.
 R3DEV --> R3QA
 R3DEV --> R3QRPOD
 R3DEV --> R3PROD
So dev will transport to QA,QPROD,PROD
Thanks,
-Hari

Similar Messages

Conversion of source system names --- error in transport

hi
i want to transport my object from Dev111 to Quality222
but the transport ended up in error 8
it gave the error...
Source system PRODUCTION333 does not exist
I am confused,
shouldnot it should give error related to Quality system ???
how should be the mapping in Source system names?
after research it seems it should be maintained in
RSA1-TOOLS-mapping of SOURCE SYSTEM NAMES.
i have following systems...
BW- DEV111 QUTY222 PDN333
R3 DEV121 QUTY242 PDN363
What should the entries look like in which system

Landscape is -Transport should be send from Deve-Quality---Production
BW....................................
DEV111 QUTY222 PDN333
R3.....................................
DEV121 QUTY242 PDN363
CAN you advise if the entries SHOULD look like below in Quality and Production System???
Quality system should have entries like:
bw DEV111.............. bw Quality 222
r3 DEV121................ bw Quality222
Production system should have entries like:
bw Quality222.............. bw Production333
r3 DEV242................ bw Production333
Q1 ......IS THIS HOW ENTRIES SHOULD BE IN Quality & Production system???

Use BDLS in BI for re-mapping of source system

Hello,
Is it possible to use tr code BDLS in BI in order to automatically change source system assignment in source system related BI objects (such as info sources, info packages..)?
We have created a new ECC QA client and would like to load data from that to BI (the same BI system as before) and wish to avoid the manual work of manually re-mapping all source system related objects.
In the thread below the conclusion was that it's possible to use BDLS, but when executing it in test mode and looking at the affected tables, only the parter profiles and EDI-related tables seems to be modified with a new LSN (logical system name). However, I could not find a change in tables containing f.ex. info sources etc.
Fresh source system clients in production BW system
Is there anyway of doing this without manually re-mapping the BI objects?
Thanks,
F C
Message was edited by:
F C

Thanks!
When running a LSN conversion in BI from source OLTP to target OLTP in test mode and then checking some BI-object tables, I see that the logical system name is changed, so it's seems to me as if the infosources are changed.. (or?)
However, perhaps a transport in "system copy" mode is preferrable (?) In step 2, do you mean that I should first collect a system copy in a transport request and then collect "everything before" in the same transport request?
Any comments on BDLS, Patrick?
Regards,
F C
Message was edited by:
F C

Conversion of Source system name after transport

Dear All,
I need one clarification.
Say you have developed a fresh modelling in BW Dev server and your source system is R3 dev system. Now you need to transport all the request to BW Quality system but the source system will be R/3 quality system.
For this change of source system name we need to maintain some mappings.... From Tools menu there is an option to do this...
My doubt is in Production server how do we maintain the mapping...
Quality system ---> Production
or
Development system---->Production.
Hope i am clear....
Thanks & Regards,
Anup

Hello Anup,
The question you raised particularly is about the change of source system when your transports are alredy done. For this, i would like to say is that when you do any transports in the R/3 or BW front, the source system change is done only when :
1. It is done, when you have a single base system and different R/3 (source system)
2. If you have a single source (R/3) and a single destination (BW Quality), you do not need to map the source system.
Well, i case that is needed, you may do it via :
1. Go to RSA1
2. Go to Tools.
3. Tools -> Conversion of source system.
In the right most table column, provide the source system you need to connect with your BW system.
This will internally connect you with the specified R/3 system.
Hope it helps!
Neha.

Conversion of source system names

Hello Experts,
After having some transport problem (transporting infopackages), I notice that the source system mapping is not the same in DEV compared to PRD.
Other than change log which was not turned on, is there any other way I can find out who or when was the last change to this mapping table?
Am I right to say the mapping entries should exist in all systems? My DEV currently only has 1 entry compared to 6 entries in QAS and PRD.
The source system underwhich the infopackage resides is not shown in the DEV source system mapping table.
Is this the cause of my transport problem?
Regards,
Mirella Russo

Dear Experts,
Thanks for the useful information. Points awarded.
Am I right to say that mapping in target system cannot be transported and is set directly in target system QAS, PRD via RSA1 and no mapping is required even if there are other source systems, like flat file source systems, when the source system name is to be the same in all systems? In this case, my source system is a flatfile. Does this mean I need not maintain it? The 'no mapping' warning received in transport log shows that the flatfile source system concerned exists in the target system but no mapping. As I do not need source system name change, can I say I need not maintain in the mapping table? I still cannot understand why the error come about.
Many thank you in advance.
Regards,
Mirella Russo

Mapping of source systems

Dear
Sirs,
The mapping of source system has to be done for myself sourc system also or its enought if we do for sap r/3 source systems is
enought,,,Need your help..
Thanks
Regards
Radha

Hi
If you want to transport objects from quality to production.
You have to map the current source system (i.e here quality SS) to production SS.
It will be available in RSA1 ---> Tools -
> Conversion of logical system names after transport
Regards
sateesh
Edited by: sateesh kumar on May 14, 2010 2:25 PM

Error in code page mapping for Source system whil loading the data from ECC

HI Gurus,
I am working in a implementation project, Recently our BI sand box is up, when i am doing my load from 0comp_code_attr it is throwing an error "Error in code page mapping for source system"(This is my first load from ECC).
In details tab it is showing as the data is sent from the source system but the data is not reaching to the PSA.
Please let me know if there are any settings needs to be made.
Many thanks in Advance
Jagadeesh

HI V,
Thanks for your quick response. I did it but it didn't resolve the issue. since the system id which i am having is 3 digits(LEC) but there it is taking only 2 digits, so i clicked on the button called Propose system ids, it has praposed LE, but the issue is stil there.
Do we need to do any settings in LBWE??
Thanks and Regards
Jagadeesh

Error in code page mapping for Source System

Hi All,
We are Loading data into BI system from MDM System.
It was loading fine but Yesterday we got an error " Error in code page mapping for Source System"
Message Class: RSDS_ACCESS 13.
We alreday tried to Search any IDOCs with error/unprocessed , but there isn't any.
Any pointers for this error will be Helpful.
Regards,
Mayank

Our SP currently SAPKW70019 , the SAP note mentioned above required to apply SP for 13, which we already beyond that...unfortunately we still face the same problem .. almost every day ..
any advice.. ?
Edited by: Edi Erwan Abu Talib on Jun 22, 2009 8:22 AM

Error in codepage mapping for source system

Hi Experts,
I am getting the following error while loading data from ECC only for Account COPA datasource.
Error in codepage mapping for source system. Error text:
Message no. RSDS_ACCESS013
Regards,
Sandeep Sharma

Hi Sandeep,
This is a issue related to idocsRFC connections from teh sourcesystem....
U can contact ur BASIS team to solve this...
From their end they have to chk the unprocessed/errored idocs in BD87...
They have to run a report:RBDAGAIN to process the errored idoc's in the source which are in STATUS:'02'.
This is a solution for temporarilrly basis...
If this occurs regularly they have to change the settings in SM59 which is so important...
Refer exact note for this: 784381
The SAP note 613389 may also be relevant for the error message "Could not find code page for receiving system", please check the information given in the note and see if you can use it to resolve the problem.
Regards,
Marasa.

Error in codepage mapping for source system. Error

Hi BW Experts,
I am facing following error:
Error message: Error in codepage mapping for source system. Error text:
Details: Inbound Processing ( 1000 Records ) : Errors occurred
Error in codepage mapping for source system. Error text:
Update PSA ( 0 Records posted ) : Missing messages
I repeated the delta working and everything fine.
Does anybody know why this error occurs?

Run rsa13 (for bi 7.0) find your source system which one you are using for data transfer and double click on it and find special options there select the optioned i mentioned already.
Please search SDN you can fin threads related to this thread
if not let me know.
Regards.

Error in codepage mapping for source system. Error text:

guyz,
im facing the below issue in prod.
Error in codepage mapping for source system. Error text:
Message no. RSDS_ACCESS013
Collection in source system ended
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Inbound Processing
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
need your guidance,
cheerz,
raps.
Edited by: raps on Mar 1, 2012 9:39 AM

Hi ,
Kindly go throught the following threads for your issue resolution::
Error in code page mapping for Source System
Erroe in source system
Regards,
Arpit

Change source system name in variant in BWQ

Hi Gurus,
I created a process chain for global seetings for unit of measurement and fiscal year variants and transported to BWQ.
In BWQ, I found the source system name in variant is showing ERD source system name, but I need to change it to ERQ source system name. Any advice how to change source system name in variant in BWQ I would appreciate it.
Thanks
Liza

Hello Again Liza...
I had the same problem but I didn't need to include in process chain...
So to execute periodically you can change it in debug mode, not the best solution...
But since you need to use it in a process chain, you should copy that program to one of yours Z.
Do this:
Go to transaction se38 and insert the program name "RSIMPCUST".
Click on the button of "Copy" (Ctrl+F5).
Change the source program name to ZRSIMPCUST (or whatever you want)
Click Enter
Click the button to mark everything (F8)
Click Enter
On the next window of the name of the include click enter (leave it blank)
Click on the button Change of your Source Code
In line number 54 you'll find this in Selection Screen part:
PARAMETERS: logsys TYPE rsa_logsys MODIF ID p01.
PARAMETERS: logsysnm LIKE tbdlst-stext MODIF ID p02.
Delete those two lines and insert this ones:
PARAMETERS: logsys TYPE rsa_logsys.
PARAMETERS: logsysnm LIKE tbdlst-stext.
Now click on Activate button (Ctrl+F3)
Now you have a new program just like the old one but you can change the source system to whatever you want!
Please assign points,
Diogo.

Display Source System Name in Process Chain Email

We would like to show the source system name (QA, Prod, etc) in the email subject when process chain messages are emailed so we can easily discern between production messages and messages from our test system. There doesn't appear to be a straightforward way to do this.
I have seen a Re: Howto Insert System ID into Process Chain Email Message which discussed this topic and offered 2 potential solutions neither of which work for us:
1. Open the production system and modify the messsage directly in the production system
2. Edit the First & Last Name of the sending user in the production system (does not work for us because we use central user administration)
Can anyone suggest another method of accomplishing this requirement?

we achieved it by changing text of [email protected] from 'BIWREMOTE' to BIP BIWREMOTE'....so in our mails even though mail id is same, but it display it for us as BIP.
Just go for user BIWREMOTE, and change format field with whatever name you wanna recieve mail. It should work properly.

"Conversion of Source System names after the transport" : O

Experts:
Environment : BI 7.0 and SP 12
Tranports related to transformation rules are failing with inactive status...
Further investigation on this, I have noticed that in our QA system, where "Conversion of Source System names after the transport" : O screen, we have columns
Original Source System, Target Source System, 7.0, Description(I guess, since no name is found)
Everything looks fine to me with reference to actual techinical names of source/target system...
My question there is a check box on column "7.0", which is UNCHECKED. Is this correct?
My understanding is that, this check box needs to be CHECKED, since this is related " Only Valid for RSDS, TRFN and DTPA Objects ". Is this correct?
If yes, Can I check this box in QA system, save and retransport my requests. If so, what happens to standard BW objects i.e., transfer ruels, update rules etc...
OR do i need to create another entry with same source/target system and check the 7.0 box.
OR do i need to create 3 entries with same source/target system and check 7.0 box for each entry i.e., RSDS, TRFN, DTPA.
Finally, please advise the exact steps that need to be taken here...pros and cons
Your inputs will be of great help....
Thanks,
BI
Message was edited by:
B I

Hi,
Yes you need to check the checkbox as it is related to Data sources and transformation and DTPs. you can mark the check box if your client is modifiable, if not you need to transport the setting from DEV. Go to
SPRO > Business Intelligence>Transport Settings--> Change Source system name after transport.
you also need to maintain the Source system IDs .
Hope it helps.

Conversion of source system names after transport

Hi gurus,
Please someone can tell me how to configure the "conversion of source system names after transport" in the BI system as my transport is not working on a new BI System ?
Thx in advance

Hi Firmin,
You can do this in RSA1 in tools under conversion of logical source system names.
Here you maintain the development system or the system used for development as the source system.
You will have to mention the logical name of the development system.
In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
Check the folllowing link for more informationn on this.
[Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
Hope it helps you ,
Best regards,
Sunmit.

Mapping of Source System Names

Similar Messages

Maybe you are looking for