Transport Collection includes Logical System?

Hi, I am collecting up Object for the BW Admin Cockpit and the collected list includes the BW Logical System as well. I can't understand why this would get picked up and I don't know what the consequences are for transporting this. The Transport Connection will not allow me to unselect it!
So I am thinking of just creating the transport with it and then manually deleting it in the transport.
Can anyone shed any light
1. why this is being included in my transport?
2. what the consequences of sending it might be
3. Is it OK to just manually delete it from the actual transport and not worry about it.
Here's a picture of the Transport Collection for review http://i44.tinypic.com/ofx1lv.png
Thanks for any insight...

1. why this is being included in my transport?
This would get connected, if u selected 'Grouping' option In dataflow before or In dataflow before and afetrwds
2. what the consequences of sending it might be
The corresponding logical system would be there in target system. Hence this is not required to transport
3. Is it OK to just manually delete it from the actual transport and not worry about it.
U can delete that manually

Similar Messages

Transport collecting incorrect Source System.

Hi SDNers,
In my BW DEV i got source systems to both R3 DEV and R3 Production.
reason for this is that the data in Dev is not correct.
When i use transport connection it only transfers Source System from the R3 DEV and not R3 Prod. I need the Source System from Production and not Development. How can i force it to use Source system from Prod and not Dev.
Thanks.
Andre.

Hi
in the transport connection before collecting your objects maintain the source system assignment sceen (toolbar or Shift+F7)
hope this helps...
Olivier.

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

One Idoc -- One Logical System ?

Hi everyone,
Right now i'm developed 6 interface using idoc (6 different business process). Do we need create logical system for each interface? Or just only one logical system? If we have success create this interfaces, how to transport this setting (logical system,rfc destination) to production system ? Thank you.
Regards,
Satria

Satria,
In R/3:
1. Logical System are careated only once. If there is a requirement then only they will be created by using tcode SALE (it's not so frequent).
2. You can see all logical system by using Tcode "BD54".
Note: In DEV, QA or PROD system, you will not be having authorization to create any logical system.
So, while doing outbound processing you can reuse the same logical system.
If still you have any doubt, kindly let me know.
Kindly set the thread to "Answered", once you get your final ans.
Regards,
Sarvesh
*****Reward points, if found helpfull.
Message was edited by:
Sarvesh Singh

Include a system in two different Transport Domain Controller

Hi folks,
I s it possible to configure a system in two different transport Domain Controller?
The two domain controllers will be in the same /usr/sap/trans file system.
thanks,
Má

Hello Má
Firstly to include system in the transport domain you need to have systems sharing common transport directory. Which you confirmed is the case.
Now when you try to change the Transport Domain of the system to make it part of another system it will overwrite current configuration.
Hence you wont be able to make one system part of two Domains.
There is no workaround available best of my infomation.
Regards
DG

How to include virtual system in transport domain

Hi all,
I have my development and quality servers running on one instance.at the time of configuring STMS,i have made the transport domain and included both the systems.Also i have configured production system as the virtual system.Now i have installed the production system on a different host with a different transport directory and want to include this system in the transort domain.in a way the virtual system will be replaced.
How should i do it.
Regards
Praveen

Hi Praveen,
If you want to include a system in your existing transport domain, just login into the system, in T-code STMS you will get a POP UP choose other configuration ,it will ask for-:
System
Description
Target Host
System Number
Save the settings and wait for some time it will automatically added in your Transport Domain.
Reward Points if find it useful.
Thanks,
Prashant.

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

Not able to include the system to its transport domain

Hello,
We are not able to include the system to its transport domain. We are getting the same error:
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Except.                CX_SY_OPEN_SQL_DB
Date and Time          01.10.2010 11:27:35
Please advice
Sankar

Hi Shyam,
This is actually a program error and the same can be rectified by implementing the [SAP NOTE 1412609 - DUPREQ when configuring the transport domain|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1412609] using the tcode SNOTE.
This will resolve ur issue.
Regards,
Varadharajan M

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

Business Service and logical system naming criteria across environments

Hi !
Imagine this scenario: File-XI-IDOC. There is a file server where files are uploaded by a legacy application. XI polls that directory, converts the file to IDOC and sends it to R/3.
R/3 is a production business system, for example "R3_PROD", the file server is a business SERVICE, because of its abstract nature.
Is it ok to give that business service a name such as "BS_FileServer" and then create the logical system "LS_FileServer" in R/3, to be able to receive IDOCs from the sender business service?
If we need to use 3 different file servers, one for development, one for test and another for production...is it ok to create the business service in each integration directory with SAME name, and the 3 logical systems with same name in each R/3 receiver...because creating business services as "BS_FileServer_DEV", "BS_FileServer_TEST" and "BS_FileServer_PROD" we imagine that could give us problems when transporting scenarios from dev to test, and from test to prod...because we will need to recreate the whole scenario using the new object denomination.. e.g. a scenario including BS_FileServer_DEV in development is called BS_FileServer_TEST in test..or worse..we could have the BS object transported and as a result we would have a BS_FileServer_DEV object in integration directory of our test environment...
Is this the right path?
Thanks,
Matias.

Hey,
When a technical system is defined for a product / s/w comp version we also enter the parameter for logical system name. If a buisness system is defined for a technical system then it in turns refers to the technical system with buisness system assigned to it.
Itz lyk linkage of PRODUCT -> S/W COM VERSION -> TECHNICAL SYSTEM (LOGICAL SYSTEM) -> BUSINESS SYSTEM
As per file to idoc scenario where BUSINESS SERVICE is used it doesn't refer to technical landscape so there is no question of Business system. With relevance to transports.
With File -XI-Idoc scenario the concept of logical system only comes into picture if we have a integration process also involved in the scenario. Where in adapter specific identifiers we specify the logical system name of the sender file system.
Integration Repository.
1) The Software Component version need to be same in all the landscapes that is a prerequisite else transport will fail.
Integration Directory:
2) Assuming that transport is being done for all the objects under a service and the objects has been transported to the test landscape business service with same name will be create in test sys only address and access parameters that have to be entered again and the change list has to be activated.
I haven't tried exporting individual object from ID so no clue.
Please refer the following link<a href="http://help.sap.com/saphelp_nw04/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm">Transporting XI Objects</a> .
Hope itz helpfull.
Cheers,
*RAJ*
*REWARD POINTS IF FOUND USEFULL*

ALE settings in sapR3 system logical system

Hi People
IN IDoc to File scenario
How to create Logical system(ALE settings) in SAP R3 system, i know little bit idea about that, we have to 1st create LS name (for R3 sys & PI sys), after that we have to assign that name's how to assign that, PLS can u provide me to with screen shots (if possible) r any links
Regards
shekar

Hi,
IDOC
http://msdn2.microsoft.com/en-us/library/ms942196.aspx
Idoc configuration Required~
in R/3
1) RFC destination pointing to XI
2) WE20 Partner Profile entries
in XI
1) RFC destination pointing to R/3
Go thru this -
configuration steps for receiving idoc in xi from r/3
Go thru these for Idoc to XI scenarios-
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
/people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
These will be the Configurations needed in your R3,
1. SM 59 - Create an RFC destination for your XI .
2. We21 -- Create a port for XI
3. We 20 -- Create a partner profile entry for the Outbound IDOCs for XI.
Configuration on XI
1. IDX2 - Import IDOC metadata.
For eg : Lets assume the R/3 system and Xi system are QZA and X7A.
In XI :
Step 1 : In SALE Tcode :
a)Create Logical systems for R/3 and XI.
EG : (QZACLNT100) and (X7ACLNT100).
b) Assign the logical system of XI to Client.(X7ACLNT100)
Both the above options u can find in SALE transaction under SENDING and RECEIVING SYSTEMS tab
Step 2 : In SM59 create RFC destination in XI pointing to R/3(i.e IP address of R/3) (This RFC Destination name shd be same as the Sender LS name)=> QZACLNT100 is my RFC destination.
Step 3: Create the PORT in XI for the Sender system and assign the RFC destination.
In R/3 :
Step 1:
In SALE Tcode :
a) Create Logical systems for R/3 and XI for
b) Assign the logical system of R/3 to Client.(QZACLNT100)
Step 2 : In SM59 create RFC destination in R/3 pointing to XI(i.e IP address of XI) (This RFC Destination name shd be same as the Receiver LS name)=> X7ACLNT100 is my RFC destination.
Step 3: In SALE Tcode under Modelling and Implementing Bussiness Processes-> maintain Disribution Model and Distribute Views.
a)Click on that ,it shall take to Tcode BD64 ,where u can create a Distribution Model.
b)Once you create that ADD MESSAGE type(You have the button at the top), there it shall ask for Receiver and Sender LS and Message type.
c)In Menu Bar EDIT->Generate Partner Profile.
Click on that and press Execute .
This shall create 2 partner profile X7ACLNT100 and QZACLNT100 ,X7ACLNT100(this is the partner number for QZA system) shall have the outbound parameter as CREMAS, and QZACLNT100 is created with no parameters ,you need not worry .
d) Click EDIT->MODEL VIEW->Distribute.
This shall distribute the model and you can see the distribution mode aslo getting created in XI system.
This configuration shall surely help u out as it worked out for me.
Configurations required for IDocs in R/3
In your XI system, you need to do the following.
1. Create a RFC destination to your R/3 system
2. Create a port in IDX1 of your XI system and use the RFC destination in step1.
3. Try importing a idoc metadata thru idx2 transaction to check whether the configuration is correct.
4. In your SLD configure the technical system and business system. The technical system should hold the logical system name you have in your R/3 system client.
5. Import the business system and you can use it in your configuration scenario.
Please also refer below links for details.
Go thru this-
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
SAP R3 ->Legacy system including master data using XI
Regards,
Phani

Change Logic System in BW

I had problems with the definition of the logic system in BW, what I described by unfamiliarity with the same code as that of R3 while attempting to create the system source tells me that this already exists.
Remove BW client in order to return to the allocation and make allocations again, but to execute the transaction RSA1 me wrong evoking the initial logic system.
How can eliminate this reference, without having to reinstall BW?
I tried using the BDLS transaction, the system allowed me to create source but will not let me do anything else.
Now, thank you very much for your comments.
Se me presentaron problemas con la definición del sistema lógico en BW, por desconocimiento lo definí con el mismo código que el de R3 y al intentar crear el sistema fuente, me indica que este ya existe.
Elimine el cliente en BW para poder volver a hacer la asignación y realice las asignaciones nuevamente, pero al ejecutar la transacción RSA1 me da error evocando al sistema lógico inicial.
¿Como se puede eliminar esta referencia, sin tener que volver a instalar BW?
Probé utilizando la transacción BDLS, me permitió crear el sistema fuente pero no me deja hacer nada más.
desde ya, muchas gracias por sus comentarios.

Hello,
in the transport connection of the Administrator Workbench there is a special collection mode for system copies. Select your Source system and use this mode. All source system dependend objects are collected in a transport request. Export this request, connect your new source system and maintain the translation of logical system names in the Admin Workbench. Then reimport the transpor request and all datasources, transferrules etc. are then 'copied' to the new source system. Have a look in SAP note 886102.
Hope that helps
Regards
Christoph Vortkamp

Logical Systems in Business Services

Hi
In Business Service creation, for Adapter Specific Identifiers, the parameter for the Logical System. It is only possible to assign one logical system to one Business Service ?.
i.e. to do
MyBusServ1, Z_LS_1
MyBusServ2, Z_LS_1
is not possible ?
When trying to assign Z_LS_1 to MyBusServ2 I get the error that Z_LS_1 is already assigned. Is there a way to circumvent ?, I do not want to create two logical systems in R/3 as the IDOCS types submitted by the Business Services are the same.
Thanks
Damien

Thanks for the replies
Sarvesh - The Business service is the sender of the information \ IDOC. If I remove the Adapter specific config then how will XI know what Logical system to apply to the IDOC ?.
Jaishankar - I am creating two IDOC's in SAP. MATMAS and PORDCR. The input file are coming from two different source systems. lets say sys1 and sys2. Both of thse for clarity are created in my scenario as Business Services. sys 1 creates MATMAS and PORDCR IDOC's int he syatem, sys2 creates PORDCR IDOC's in the system. As sys1 and sys2 are related in that they created the IDOC's as part od the same project then I would like to collect in the same partner profile in SAP e.g. Partner Profile ZPP_IDOC with IDOC types MATMAS PORDCR that serve as input for both systems. Logically I would assume that I can assing the logical system ZPP_IDOC to both the adapter specific parameter in both sys1 and sys2.
Thanks
Damien

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

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>

Transport Collection includes Logical System?

Similar Messages

Maybe you are looking for