Transport Logical system DEV To Production

Hi friends,
can you guys tell me how to transport Logical system from DEV system to Production system.
please help me its urgent..
Thanks in Advance

Hi Rashmi,
Go to SALE Transcation and click on basic settings ->logical system
-> define logical system and there u can click on tabe view menu and the transport ... it will ask u for a request ....
regards,
Santosh

Similar Messages

Logical System Change for Production System

Hi experts
We have new CRM and BI project. Logical System name of our ERP production system is not in naming standart. So we want to change logical system name and run BDLS in production system.
Is there any risk about this prosedure?
Best Regards...

Hi,
It is not advisable to change the logical system in production client once its assigned.
Regards,
Nisit

Transport sequence from dev to production

Dear Folks,
I am done with development & i would like to transport all the developed objects to production.
Could anyone provide the sequence along with necessary steps.
How to assign new requests to all the objects developed including queries.
Basically these are the list of objects:
Info objects,info area, info object catalogs,dtps, transformations, multi provider, info package, replicated data sources,queries etc.
I would like to assign once again new requests to all the objects developed and transport them.
Awaiting kind response.
Thanks,
Kitu

Hi,
Please follow the sequence:----
The respective Transports should have the following objects:
1. Base Objects -
a. Info Area
b. Info object catalogs
c. Info Objects
2. Info Providers u2013
a. Info Cubes
b. Multi Providers
c. Info Sets
d. Data Store Objects
e. Info Cube Aggregates
3. Transfer Rules u2013
a. Application Components
b. Communication Structure
c. Data Source replica
d. Info Packages
e. Transfer Rules
f. Transformations
g. Info Source Transaction data
h. Transfer Structure
i. Data sources (Active version)
j. Routines & BW Formulas used in the Transfer routines
k. Extract Structures
l. (Note) If the transfer structures and related objects are being transferred without preceding
Base Objects transport (e.g. while fixing an error) it is safer to transport the related Info
Objects as well.
4. Update Rules u2013
a. Update rules
b. Routines and formulas used in Update rules
c. DTPs
5. Process Chains u2013
a. Process Chains
b. Process Chain Starter
c. Process Variants
d. Event u2013 Administration Chains
6. Report Objects u2013
a. Reports
b. Report Objects
c. Web Templates
Hope this helps......
Assign if helps...
Regards,
SUman

Logical systems in production with CUA

Hi,
We have recently implemented CUA and are rolling out ECC 6.0. We created the logical systems for development, QA, and production in the development system and transported them to QA and production.
The solution manager system is the CUA master.
We normally only have production logical systems defined in production and would like to remove the development, QA, and solution manager systems. If we attempt to delete these definitions in production in SALE, it complains that the logical system is still used in distrubution model CUA, although solution manager, not production, is the CUA master.
If we are using CUA, do we have to have all logical systems defined in all client systems?
TIA,
Russ

Hi Pradeep,
I don't think that's quite it. SM1 is the master. I'm in the production system (PE1) trying to delete the development system (DB1). I am not trying to delete SM1. I'm getting the following message.
Logical system DB1CLNT300 must not be deleted
Message no. B1199
Diagnosis
The logical system DB1CLNT300 is still used in distribution model CUA (client 800).
System Response
The deletion cannot be carried out.
Procedure
Confirm that the logical system DB1CLNT300 is really no longer used. Delete it first from distribution model CUA (client 800), then delete it here.
Thanks and best regards,
Russ

Transaction Launcher: Logical System in Production System does not change

Hi,
I created a transaction launcher in the CRM development system (CRD) to launch the transaction IL02 in the ECC 6.0 system (ECD). Then I transported the changes from CRD to the CRM production system CRP. I also transported the changes from ECD to ECC production system ECP.
However, when I see the transaction launcher in CRP system, it is still configured for the URL of ECD. I want the transaction launcher to connect to ECP. One option I have is to change the class name in the CRP system. However, I am not allowed to create a new ABAP class in the production system. Is there any other way to change the target system automatically in production system?
Thanks,
Rohan.

Thanks Piyush. Could you be a bit more specific? I followed these steps:
1. In transaction CRMS_IC_CROSS_SYS, created a logical system URL for production system
2. In customizing setting Copy/Delete Launch Transactions, deleted the transaction launcher id.
3. In customizing setting Configure Transaction Launcher, created the same transaction launcher id newly.
I still am not able to change the logical system. However, I can do it if I change the class name.
While deleting the transaction launcher id, should I be deleting all dependencies?
Regards,
Rohan.

Same logical systems for two environments productive

Hi gurus.
I have a question for ALE
There are two production systems a copy of another, who want to connect both to configure the ALE, but by mistake, both systems were the same logical system when they made the copy. Since this change takes months. At the moment I can not make this change in BDLS because it is a productive environment.
When trying to configure the ALE, I am have problems with the logical system name, although one of the settings I gave it another name when you configure the transaction BD64.
Guys, what I find solution to configure the ALE, without changing the logical system to a productive environments ??????
Regards,
Desiré

Hi Mark, thanks for the replay.
I understand also that the solution is to execute the BDLS to change the logical system and convert all tables to new logical system.
I don´t know how the process copy for both system productive.
The problem is that both environments are connected to BW, and other applications and they opened an OSS note to SAP consulting and and the answer given is that they did not recommend changing the logical system.
I thought if there was another way to configure ALE without having the problem of changing the logical system environments.
Regards,
Desiré

Original Logical System Of Product

Hello,
I am new to GTS and am finding it difficult to find the original Logical System for a Product in GTS. I found table /SAPSLL/TCOGVA, which shows the Logical System to Logical System Group. Then there is /SAPSLL/PNTPR, which shows the Logical System Group and Product. However, I would like to know which logical systems a product was found.
Is this possible in GTS?
Thank you in advance.
Regards, Dean.

Hi,
This is allways an issue, as this information, I beleive, gets lost along the way. So there are 2 hints for you. Either you find it out via the RFC user that created the Product (for that you need a different RFC user for each System, which I woul drecommend anyway), which you will find in the general Tab of the Product master. If you need this information on a constant base, I suggest you transfer it with the material and add it into an additionnal Field.
Let me know if that helps.
Marc

Logical Systems & SRM Customizing

Dear Experts,
I would like to guarantee BDLS won't be executed within our SRM Productive environment. Unfortunately, according to the functional team and because of customizing requirements, it appears logical systems cannot be generic enough to guarantee the process. For instance, the organizational structure refers to <SID>CLNT<MANDT> instead of alias like 'ECC'.
Any advice to ensure to the infrastructure team they will never run BDLS after transports?
Thanks and Regards,
Ludovic

Hi,
thanks for your prompt answer. Unfortunately, the issue is a bit more complex.
1) We have defined a backend RFC in SRM : <DEV>CLNT100
2) We have define a distribution model in BD64 referencing this RFC connection
3) We tried to define R3 and SRM as alias within the customizing : "master data/ALE Options/logical sytem", SMOEAC, etc... (refering <DEV>CLNT100)
4) We have changed the organizational structure PPOMA_BBP in order to reference R3
5) Under "Master Data>Determining financial system for product type", we have defined (source = R3 / target = SRM) and so on, and so on...
6) We have launched the replication and then tried to retrieve products categories from PPOMA_BBP
Unfortunately, there is no existing product type under logical system R3 but under <DEV>CLNT100 and the shopping cart doesn't work => missing logical system
However, when naming the logical system <DEV>CLNT100 (instead of R3), everything is working ...
Unfortunately, when we will transport additional customizing to another system, this customizing will refer <DEV>CLNT100 instead of <PRD>CLNT100.
On site, SRM experts use to launch BDLS after customizing transports in productive systems in order to modify the SID. We cannot afford to launch BDLS in a productive environment which will probably take several hours to run.
Thanks for your recommandations,
Sincerly,
Ludovic

Could not determine BW release of logical system 'BWPCLNT100

after a BI systemcopy (production to development) we get the following
error when we run load jobs of type "delta load". full loads work fine
"Could not determine BW release of logical system 'BWPCLNT100'"
even if i start the deltaload from the R/3 system with transaction RSA3
with update mode "C" i get the same error . when i use update mode "F"
it works fine , but that's not the thing we want.
BWPCLNT100 is the logical system of the productive system .
we have changed all the logical system setting to BWDCLNT100 using
transaction BDLS and we have also changed all entries in RSBASIDOC,
RSISOSMAP, RSOSFIELDMAP,.... .
we have done several systemcopies in the past , they all worked fine
and without this error. this is the first copy in BI 7.00 .
are there any loadmodules which have to be regenerated with the new logical system name?
thank you for your help and kind regards hannes toefferl

Hi,
As you said you are getting error after system copy when you are doing the delta load and full load is working fine for you.
This mainly happens due to init disturbance in the source system.
I would suggest you to delete the init and rerun the Init from BW once again.
This should solve your problem.
Thanks
Mayank

Setup SCC4 ( logical system)???

Hi all,
I couldn't setup logical system for the test system because the production & test systems use the same client key (for example:100). The logical system for production is setup already and use 100 for the client key.
Any suggestion?
Thank you

Hi Suneel!
IT it not advised by sap to assign a client to multiple Logical systems . I am posting the excerpt from SAP IMG for Logical system node.
Logical system
 The distribution of data between systems makes it necessary to identify each system as a unique logical system.
 A logical system is an application system in which the applications are coordinated to work in one common database. In SAP terms, a logical system corresponds to a client.
 The logical system is important in the following SAP areas:
 o Communication between two or more logical systems
 ALE business process (e.g. Cost Center Accounting): defines the system in which a particular application is running. Only in this system can master data can be changed.
 Business Object Repository: The name of the logical system in which an object is located is always contained in the key of that Workflow object. In the following steps, you must define each client as a logical system by first of all defining logical systems and then assigning the clients to the corresponding logical systems.
 Note 
 Assignments must be unique (that is, one client can only be assigned to one logical System.
 o More than one client must never be assigned to the same logical system.
 o The logical system must be unique across the company. It must not be used by any other system in the ALE network.
 The same applies to pre-production systems and production systems: the pre-production system must be assigned to a different logical system from the production system.
 o If the logical system of a document reference is not initial and is different from your own system, the system assumes that the document is located on another system.
Recommendation 
Ensure that the assignment of IDs with the authorization to maintain logical systems is monitored (that is, only one person should have authorization to do this).
Hope it makes the things clear
with regards
ashwin

Logical system Name Change Via Transport

Hi All,
Recently we made changes in parallel processing profile customizing table (/SAPAPO/SDP_PAR) and created entries for Macro Jobs and CIF.
For Application "CIF Delta Report", Logical system is mandatory and in Dev we gave the APO Dev Logical System Name (AD1XXX). Now when we moved the changes to Quality, expectation was that Logical system name for CIF Entry in the table would change to AQ1XXX - However, it still shows as AD1XXX there. Moreover AD1XXX entry is not a valid entry in Quality System and even when we see Drop Down values for that column (Press F4) - Only APO and ECC Quality systems names are appearing.
Please suggest how can this logical system name be corrected. One option is running BDLS, but when this TR moves to Production there also we might end up in same scenario (Logical system as AD1XXX instead of AP1XXX) and running BDLS in Production wont be approved.
Please suggest if there is any other option to handle this.
Regards,
Alok

Hi Alok,
we describe a solution in our
SAP Rapid Deployment Solutions (RDS)
Quick Link
                Access SAP Rapid Deployment Solutions (RDS) directly via
                  http://service.sap.com/rds
SAP Demand and Supply Network Planning rapid-deployment solution
Quick Link
    Access this area directly via
http://service.sap.com
/rds-dpa
In confgiguration guide
Central Master Data Replication (SCO)
you can read how it is done with
Create Entries in Table
TVARVC for Logical System Variable in Variants
Frank

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

Logical system same in DEV/QAS/PRD for ALE

Hi friends,
We haven't used ALE but now need to set it up. Problem is, DEV and QAS are copies of PRD so all three have the same logical system name. I read about how using bdls to rename the logical system can create inconsistencies and am worried it can ruin our transport system.
Appreciate your comments, thanks & best regards.
Claudio

Using BDLSS in comaprsion to BDLS - logical systems can also be converted remotely in all partner system.
Please refer: SAP notes
544509 - ALE: Converting the name of the "logical system"
121163 - BDLS: Converting logical system names
1478123 - FAQ: Source system
Divyanshu

Transport XI System Landscape Directory Contents from Production to Quality

Hi
I want to transport SLD contents from my production environment to the quality environment.
I could see a link in of export in the SLD Administration page, will that help me. I think that link will allow me to transfer whole contents however I want to transfer only the non production systems from SLD.
Is it possible, if yes then please tell the steps.
Thanks

Hi,
I want to transport SLD contents from my production environment to the quality environment
Did you see this weblog,
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
Also there are other using file transport,
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
This will get you an overview.
Hope this helps.
You can also Use CMS for transport.
Regards,
Anirban.

Regarding logical system assigining to transport request

hi, all,
how to assign the transport request for logical system.,....because i transported the interfaces to quality system..please guided me in this

Hello Sai
I am not sure about the meaning of your question.
You do no assign any logical system to a transport request but you must define the target system (see Properties of request). Calling the search help for this field you see that the target systems are coming from the active transport configuration (STMS).
Perhaps your question is about how to set the client in which the request is imported. Regarding workbench request containing client-independent objects it does not matter whether you import into client '000' or your productive client.
For customizing requests containing client-dependent objects you set the client when executing the import (either in STMS or via command line when calling the tp command directly).
Regards
Uwe

Transport Logical system DEV To Production

Similar Messages

Maybe you are looking for