Conversion of Logical System name for "Error DTP" is not working

Hi All,
I have created a DTP and corresponding "Error DTP" for handling the Error records in development.
But when i move the both the DTP's to Consilidation systems,
DTP is getting converted to the consolidation R/3 systems (Example: TQS).
But the "Error DTP" is not getting converted with the source systems as R/3 cosolidation systems (TQS) and remains as source systems as Development R/3 system(TDS).
We are in BI 7.0 version with SP level of 13.Can anyone help how to resolve this issue? or any OSS note available to resolve this issue.
Thanks,
Muruganand.K

Closing Thread.

Similar Messages

Logical system name for this BI is not allowed

Working under Data Warehouse Workbench, when I click BI Content button, I get pop-up: "Logical system name for this BI is not allowed". Then I get three options from NW system: "Create", "Assign" or "Cancel".
What can I do? How to create a new Logical System?
Thanks,
Mike

Refer this link to create a Logical System...
http://help.sap.com/saphelp_nw70/helpdata/en/aa/b4b13b00ae793be10000000a11402f/content.htm

Conversion of logical system name fails

Hi,
when trying to transport a transformation on BW7 the logical conversion name is failing. When i check the setup (on rsa1 menu "Conversion of logical system names") it seams to be ok on source and target system.
Any tips to solve this ?
thx in advance

Hi,
when you are not maiantained the logical systems properly , then you will get that error when you are transporting the objects
in Bi production system ( to which server you are moving objects) in that you should maiantain the all logical systems as below
1) for examaple BI deve --- BI prd
one logical systm should be bi Dev to BI prd
2) ECC production connected to BOI production
Then one more logical assignment ECC prd to BI prd
normally those two you are maintained i think so.
but when you are moving the objects from the BI development to Bi production
the daat sources are pertaining to the ECC developmet
so that ECC deve to BI Dev ( here there is no problem)
when those daat source s you are moving to production it shows error
because that ECC deve Data source logical system should be changed to BI production
so you main tain one more logical system ECC dev to ECC PRD
in your BI system
Then try reimport the same.
Thansk & Regarsd,
sathish

Conversion of logical System Name

Hi,
I have read somewhere that Conversion of logical System Name is part of BW System check Before go live. Can someone explain the purpose of it.
Thanks in advance
krish

Hi,
There are two different activities related to this, if you have done the system copy then for changing the logical system name we will run BDLS transaction. Check the below link for more information,
[http://help.sap.com/saphelp_nw70/helpdata/en/33/c823dbaea911d6b29500508b6b8a93/content.htm]
But if you want to move the source system dependent objects from one system to another system then we maintain the source system and target system mapping in target system.
For transport method you can maintain the system names as suggested by Gaurav and you can check that in table RSLOGSYSMAP or you can directly maintain entries in this table.
Regards,
Durgesh.

Conversion of logical system names

Hi
Must the Conversion of logical system names be set up in each client.
I.e in the BW production client do I have to go and setup what the conversion is between before the transport and after the transport.
Also if I then go into this view and want to add my conversion detail, and the system doesn't exist (in table) do I have to create the entries in Dev and Transport it through?
Corne

Hi Corne,
If the correct entries don't exist in the underlying tables, you have maintain it in SPRO.
The entry in the table is cross client. hence it has to be done in Dev.
Go to SPRO -> SAP Netweaver -> Business Intelligence -> Links to Other Source Systems -> General Connection Settings
-> Define Logical System
1. To create a logical system, choose Edit -> New Entries.
2. Enter a name for the logical system that you want to create.
3. Enter a description of the logical system.
If you want to cange this entry:
a) Select the appropriate line.
b) Choose Edit -> Change field contents.
c) Enter the new text.
d) Choose Replace.
4. Save your entries.
Roy

Same logical system name for two productive systems - BW, PI issues

Dear all,
we have a productive system which serves two companies (different company codes). This system is connected both to BW and PI for both companies.
There is a requirement that these two companies must use their own system, so the whole landscape (dev,qa,prd) will be copied to different systems (different server with different system id).
As a result of the above procedure we wll have two different productive systems, as required, but we wll have the same logical system name for the two productive systems, which must be both connect to bw and PI.
However as far as I know:
- we cannot connect systems with same logical system name to BW,PI
- we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
How can we overcome the problem?
Please advice.

> However as far as I know:
> - we cannot connect systems with same logical system name to BW,PI
> - we cannot convert logical system name of the one of the two productive systems as they are productive and so this is not supported.
Right.
> How can we overcome the problem?
Since you split up systems (or plan to) I highly recommend booking an SLO service (http://service.sap.com/slo). Those people have to the tools and the knowlege to help you. I would not do this on my own.
Markus

Giving logical system name for PI 7.11 system

Hi,
how can i give logical system name for PI 7.11?
Thanks.

Check if this helps http://help.sap.com/saphelp_nw70/helpdata/en/aa/b4b13b00ae793be10000000a11402f/frameset.htm
if you are loking for naming conventing : use CLNT{client no.} eg: PIDCLNT001
Regards,
Srinivas

Changing the default logical system names for adaptive RFC models

Hello,
When I create an Adaptive RFC model the dialog that asks me to specify the model name, package, source folder, etc. has default values in the "Default logical system name for model instances" and "... RFC metadata".
I know I can type in another name there but I'd like to change the default name to something that fits our naming conventions. Can I change that? If so, can someone tell me where?
Thanks in advance!
David.

Suresh,
Thank you for your response. However, that is not what I was looking for. Sorry if my post was not clear.
I knew that I could change it AFTER the import. I also know that I can type in something else besides the default DURING the import.
What I am asking is if there is a way to change some configuration setting so that the 'default' that comes up in the drop down DURING the import is something different than what comes 'out-of-the-box' with NWDS.
Hope that clears up what I'm looking for.
David.
Message was edited by:
David Z. Pantich

Logical system name for acknowledgement in BPM

Hi,
I have a szenario:
IDOC --> BPM --> MAIL
Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
"Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
What can I do?
Possible Solution 1:
I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
Possible Solution 2:
I can enter an existing logical system name in the "adapter specific attributes".
BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
Is Solution 1) a common way?
Thanx
Regards
Wolfgang Hummel

Hi,
there are many ways:
some for aleaud are described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
>>>>Is Solution 1) a common way?
no this is not good a good idea
BTW
you can also supress aleaud raport IDX_NOALE
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Incorrect logical system name for datasources - entry not in TADIR

Hi all,
I currently can't replicate or edit any of my data sources because, after we applied some patches, the logical system name appears to be incorrect and a message is displayed saying the R3TR RSDS entry does not exist in table TADIR.
For example:
Object directory entry R3TR RSDS 0EMPLOYEE_0016_ATTR R3DEV does not exist.
That's correct, because all entries exist for my actual source system CD1CLNT175, not for SAP standard R3DEV.
Does anybody have any idea how I can update my source system configuration/mapping? I've looked on the forum but couldn't
find a clear cut answer.
Thanks a lot!
Markus

Hi all,
I think the solution lies in SAP note 1604726 "DataSources with package assignment cannot be activated"
1. When you access the change transaction RSDS, the system issues error message TK 753 "Object directory entry R3TR ... does not exist" twice.
2. When you try to activate the DataSource, the system issues error message TK 425 "Invalid call sequence for interfaces when recording changes".
My message is TK753.. and before that I receive TK425, I guess we have to apply SP28... time for Mario and Luigi to apply some pizzas... ehmm patches...!
I will let you know if that solved the problem, thanks for your help guys!
Markus

SLD: Adjust / Add logical system name for Business System [XI 3.0]

Hi,
In the System Landscape Directory, is it possible to adjust the logical system name of an already created business system?
I found in the content maintenance in Subset="All Classes", Class=SAP_BCClient" --> <MY_BUSINESSSYSTEM_ENTRY> the only possibility to add information on the logical system name of a business system.
Unfortunately, the information provided in the BCClient Entry is not forwarded to the Business System Entry for my Business System in the Business Landscape View of the SLD...
Is there another possibility to add the logical system name to an exisiting business system?
Regards
Kristian

In a third party business system, it is not possible to add a logical system, but you can delete the business system and recreate it with the same name without problems.
After assigning a new logical system to a business system, you have to go to the integration directory and reload the logical system for the business system. Therefore open the Business System in change mode and maintain the Logical System with menu service -> Adapterspecific Identifiers.
Regards
Stefan

Defining Logical System name for ALE using T.C- SPRO?

Hi,
Can anybody tell, how to define logical system name using T.C SPRO?
Where can I find the "Define Logical System for ALE"?
Thanks
Balaji

HI,
Use the SALE transaction , there you can have all steps clearly,
please see the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping
Regards
Chilla..

Logical System Name for Portal

Hi all,
I am busy documenting System Info for a newly installed Portal (EP6) including values such as SID, Sys No, etc.
I would like to know if a Portal has a Logical System Name.
As far as I know, it does not, but I would like to confirm.
Regards
Sunil

Hi,
As per the naming conventions its defined as <SID>CLNT<Client no>.
Then a system with SID = J2E and client = 000 will have a logical system name J2ECLNT000.
Hope this helps.
Regards
Bharathwaj

Conversion of logical system names in queries

hello,
We have the following problem in our multisource model.
Constant values have been assigned in queries in development : for instance, in line 1, the profit center is restricted to the constant value D3/9000/TTBC600
D3 : development source system
9000 : controlling area
TTBC600 : Profit center code
When we transport the query, we were expecting a conversion of the source system ID in this constant value but it is not the case.
could you tell me if this is a normal behaviour??
If yes, it means that we have to enter constant value in hard code without reference to the source system ID (indirect input, you cannot enter more than the length of the object i.e. TTBC600 in this case) and this can be at the origin of conflict if we have same code in different source system.
Thanks in advance for any answer
OD

Did your transports move up ok to your target system?
I am asking because your problem could be your mapping of source system to source system ID is not set up correctly or your "conversion of source system names after transport" is not set up correctly in your target system.

Default logical system names for application and metadata in models.

hi,
I have a dbt in web dynpro java. When we create a model, we give the logical system names. When our developement is over, do we have to change these names because in test system and subsequently production system, the backends will be oviously different than developement ?
how do we change them and re import after changing? in abap we cant change our code in test and prod systems right so how is it in web dynpro java ?
thanks

Hi Jeschael,
thanks for the reponse.
When I create the model, I give the default logical system names and on the next screen I give the
ip address of the backend system, client , login, password etc
Even though the logical system names wud be same in Dev, Test and Prod systems, the ip address, login password is different so how do I give it ?
thanks
B

Conversion of Logical System name for "Error DTP" is not working

Similar Messages

Maybe you are looking for