TRANSPORT INSIDE SAME BW SYSTEM?

Hi gurus,
Is it possible to set up a transport route from dev to dev system (inside same bw system so to speak). We have a need to change a source system assignment for transfer rules (old source system was deleted and now all the rules are pointing to old system which does not exists any more). Idea is to add an entry to mapping table (mapping of the source system names in rsa1) and then transport transfer rules to get them ponting to new (existing) source system instead of the old (deleted) one.
Your comments?
Thanks!

the above link is not working can somebody provide me the above link....
Regards
Kiran
Edited by: kiran kumar on Oct 27, 2008 5:07 PM
Edited by: kiran kumar on Oct 27, 2008 5:10 PM

Similar Messages

Send data via PI to a proxy inside the same PI system?

Hi,
I want to transfer data send to PI to several other applications and in addition to the same PI system. Therefor I thought PI proxy technology would be the best but. When I send the data to the PI proxy I will get an infinity loop.
So I want to do the same what is possible with IDOC scenarios. I found an article telling me that I need to set up a different client inside the PI system and configure this client as Application System and not as PI inside sxmb_adm.
But this does not work and I never found this article again.
Any ideas?
BR Markus

>
Jan-Markus Wilhelm wrote:
> Hi,
> I want to transfer data send to PI to several other applications and in addition to the same PI system. Therefor I thought PI proxy technology would be the best but. When I send the data to the PI proxy I will get an infinity loop.
>
> So I want to do the same what is possible with IDOC scenarios. I found an article telling me that I need to set up a different client inside the PI system and configure this client as Application System and not as PI inside sxmb_adm.
> But this does not work and I never found this article again.
>
> Any ideas?
>
> BR Markus
the only way, yes is to have a different client which is configured as the application system.
if you look into this blog it shows two different client of the XI system interacting with each other...
yours will be similar /people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy

DEV- QAS : Obligatory transport target for business system not found

Hi guys!
I have read all the other threads about this subject, but since I still have no success, I´m feeling obligated to ask you for a help (deadline approaching fast!)
I´m trying to transport a Communication Channel, from DEV environment to QAS. I'm having the 'usual' error:
Import failed because of business system transfer of object Communication Channel * | SIGA | SOAP_SYNC_SENDER: Obligatory transport target for business system SIGA not found in System Landscape Directory
Here were my steps:
Keep in mind that in DEV, everything was up and running: Software Component, Product, Technical System and Business System for this name "SIGA".
1 - In DEV, I created a new Technical System, named "SIGA_QAS", pointing to my QAS server. (Keeping in mind I already had a "SIGA" pointing to my DEV server.)
2 - Still in DEV, I did create two groups: GROUP_DEV and GROUP_QAS, one points to INTEGRATION_SERVER_DX1 (DEV) and the other INTEGRATION_SERVER_QX1 (QAS).
3 - Still in DEV, I created the Business System called "SIGA_QAS" also, pointing to my QAS server.
4 - Still in DEV, I went inside both Business Systems and put: "SIGA_QAS" as TARGET BS of "SIGA" (which automatically puts "SIGA" as SOURCE BS of "SIGA_QAS")
If I look at my QAS SLD, I can see all of these objects already there, since my BASIS team did activate the 'sync' between these two environments. So, I dont need to create anything 'new' in my QAS SLD, all the objects are there, same as DEV SLD.
If I try to EXPORT/IMPORT a simple Communication Channel (using file system or even CTS - I tried both) I get the error mentioned above.
But this is 'wierd' for me, since the error says: "business system SIGA not found in System Landscape Directory", but it is there, in both SLDs.
Am I missing something here?
Thanks!
Ricardo Sancio Lóra
Brazil

Hi,
If you not tried this then try it. Delete the Business System SIGA from Integration Directory in your QAS system and then again import the business system from SLD. Acitvate the changes and then import the CC from Dev to QAS.
Regards,
Sarvesh

Error while transporting ADDRESS to production system

Hi all,
We are in the process of a new rollout and we have created new plants and company codes. the same have been transported to quality and pre-production systems without any issues. however when we transport the same to Production, we face an error
The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
The object
R3TR TDAT ADDRESS_4.6*
has not yet been imported into client 100 without error.
the objects are getting transported with same address number as in development which in production points to a different address.
as far as i know the system should generate a new address number and assign it to the object during transport.
Any suggestion wud be great

the log is
   Post-import methods for change/transport request: MEDK909182
      on the application server: ITMISAPGW2
   Post-import method AFTER_IMP_CUST_ADDRESS started for ADDRESS_4.6 T, date and time: 20090714144548
   Post-processing taking place in client 100
   The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
   The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
   The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
   Post-import method AFTER_IMP_CUST_ADDRESS completed for ADDRESS_4.6 T, date and time: 20090714144548
   Post-import methods of change/transport request MEDK909182 completed
        Start of subsequent processing ... 20090714144547
        End of subsequent processing... 20090714144548
   Execute reports for change/transport request: MEDK909182
      on the application server: ITMISAPGW2
   Reports for change/transport request MEDK909182 have been executed
        Start of................ 20090714144548
        End of.................. 20090714144548
   Execution of programs after import (XPRA)
   End date and time : 20090714144548
   Ended with return code: ===> 8 <===
regards,
Tarun
Edited by: Tarun Bahal on Jul 16, 2009 9:41 PM

Transport target for business system not found in System Landscape Director

Folks,
We have new installed new PI 7.1 system and importing interfaces from the OLD XI 3.0 system in to new PID 7.1 system.
We are getting following error when we try to import an interfaces in to new PID system:
Import failed because of business system transfer object
Communication component XID_FileSystem: Obligatory
transport target for business system XID_FileSystem not found in
System Landscape Directory
We are yet to install PIQ system.
All the interfaces in the old XID system have transport target of XIQ system. I removed the transport taget for the interface, but transport target is still showing in the Business system under transport target head.
How can we overcome this issue as we will not have PIQ system atleast for two weeks.
Thanks in advance,
Regards
Chandu

Hi,
You need to maintain Transport Groups and target for business systems while SLD transports between your XI system and PI 7.1
Illustrated with DEv & PRD here.
Procedure:
1) Call Integration Builder screen on DEV Server with http://hostname:J2ee Port/rep
2) Call SLD (System Landscape Directory) Component from the Integration builder
Save all the Following .zip files on the Local Desktop
3) Select the Software Component & say Export that you want to Export from DEV
Server to Production server and which is going to use in the IR of XI
4) Also Select the Product of the above SWC and say Export
5) Select the Technical Systems (TS of XI & TS of the SAP R/3) and say Export
6) Select the Business System(s) & say Export; those are associated with above Exported
Technical systems.
In Production Server
1) Logon to the SLD of the Production Server.
2) Create a Technical System and Business system which points to the Production SAP R/3
3) Go to Administration TAB in the main page of SLD
4) Select the Import option to Import the SWC , PRD, TS,& BS which we Exported Earlier in DEV Server
5) Click on Browse and select the .zip files that is to Import into Production Server,
Which were stored on the local desktop at the time of DEV Server Export
And say Import Selected File Option
By this we exported and imported the SLD Objects
Now we have to create transport groups and transport targets in the Production server of SLD
Creation of Transport Groups
Edit GroupsGroup1) Select the Business systems
2) Click on New Group and give the name of the group as DEV_group & select the
Corresponding Development serveru2019s integration Server
3) Similar way create another group for Production serveru2019s business system as
PRD_group and select the Production serveru2019s integration Server
Creation of transport targets
This is to Define which business systems in two different groups correspond to each other
1) Select each Business system in the SLD and select transport TAB---click on
Add/Change Target and select its corresponding target business system.
For Example:
If you select the business system of Production XI server means
In the target you have to select group as DEVGROUP and the business system of Development XI server.
Like this do the same for other business systems also
Ex:
BS_PRD_Integration Server----
BS_DEV_Inetration Server
How to create Transport Groups & transport Targets
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content.htm
Regards
Seshagiri

Regarding query transport in BW quality system

Hi Experts ,
When I transport my query to BW quality system. It is showing error like "error activating element " .
I searched in SCN and found that name for this technical element can be seen in RSZELTDIR table.
I got technical name and it was query name itself. Again I transported only this element and it is giving same error.
I am working in BW 7.4 and fresh implementation is going on .
Is there anything which is missing while transport query in quality system .
I have attached snapshot .
Please help.
Thanks
Devesh Varshney

Hi,
Please try to check and follow below steps.
1. Thru RSA1-->transport connection, collect your query and all elements(RKC,CKF,variables ..etc)
2. Later check qll query elements are saved in custom package or &tmp. if its in $tmp then save package and store into custom package.
3. collect objects into new Transport request.
4. Check your transport request have any inconsistencies thru program - RSO_TLOGO_CHECK_REQUEST. Or
5. later release and import to targets system.
Even cross check query have any inconsistencies thru program - QUERY_CHECK.
if you get error, please share error information in detailed.
Thanks

Client transport from one sap system to another one

When I want to make a client transport from one sap system to another (i.e. the source system is a system without a enhancement package and the destination system is with ehp5) can it be that there come critical conflicts in the modules (like FI, CO or HCM or other ones)?

Hi Damian,
It is not recommanded to import TRs from SAP system not at equal level.
Get both the systems at same level if possible.
But still if you have senario like this , pls ask to transport owner about changes included to undersatnd criticallity
Regards,

Same Business system to two XI/PI landscapes and possibly two ESR's

Hello,
We are setting up a new PI 7 landscape in parallel to our current XI 3 landscape.
We do not foresee a migration of XI to PI in the short run so the two systems, XI and PI will run next to each other.
The problem we then have is with the ESR and proxies. The same business system must be able to connect to both XI and PI and must also be able to generate proxies with interface content from XI as well as with interface content from PI.
The connection from business system to ESR repository seems to be 1:1, only one ESR per business system (defined via SXMB_ADM)
Is there a way to allow ESR content from two XI/PI systems in one business system simultaneously?
How do we solve this issue?
Thanks
Tom

Hi Tom,
as you already said its 1:1 connection between ESR and business system. The connection is taken from the exchangeProfile, refer to [ABAP Proxy Generation on SAP help|http://help.sap.com/saphelp_nw04/helpdata/en/14/555f3c482a7331e10000000a114084/content.htm].
I suggest you to create the interfaces in XI, generate the proxies and transport to PI.
How are you going to use the to integration servers for ABAP proxy scenarios? I am asking because you only can use one integration server at a time for outbound ABAP proxies in SAP standard. You define the URL or RFC destination to the corresponding integration server in SXMB_ADMIN.
Regards, Martin

Same Technical System multiple Business systems?

Hello,
We have a unique (atleast i felt it) landscape where we have 2 Prod PI system. We have divided out interfaces logically into 2 categories and they will run on the respective prod system. Both this prod have its own SLD and hence there is no issue here.
The issue is with the Pre-Prod where like prod we have 2 PI systems (and 2 integration servers) but they both share the same SLD. We have only one SAP R/3 backend system and hence we have only one technical system in the SLD but this SAP R/3 system has to connect to both the Pre-prod systems for different interfaces. For this to happen we have to create 2 Business systems with the respective PI pre-prod Integration Server. But SLD doesnt allow to create 2 business systems for the same technical systems.
Is there any way around this as we cannot change the SAP R/3 system and also cant have different client in R/3 for each of PI Pre prod.
This is a major roadblock and requires your expert advice on how to proceed in this scenario.
Regards,
Yash

Shitij,
You are correct in understanding that the requirement is to create 2 business systems for the same technical system with same SID (S*1) and same client.
The reason i need this is because I have 2 PI system P1 and P2 with 2 different integration server which share the same SLD. Now when i create a business system for S1 i specific the inegration server for P1 and add this business system in the transport target for P*1.
How will i do the same for P2? I cannot create a new business system for S1 with integration server of P2 and add it in the transport target for P2. If i dont do it i cannot do any transports as it will give error like no Business system found in SLD.
Hope i made it clear.
Yash

Transport request from development system to testing system

Hi,
I have collected necessary objects in (development) the transport request except 0DUNN_AREA infoObject .Because info object 0COMP_CODE is compounded with Info object 0DUNN_AREA and 0COMP_CODE is in revised version in development system (But available in active version in testing). Suppose I release that transport request from development system to testing system it get overwrite 0COMP_CODE in testing system?
Thanks

Hi Jk,
Depending the same technical names it will get overwrite in the testing server. But if the object 0DUNN_AREA is necessary in any objects which u have collected then u havce to collect it in the rtequest or else u will get RC8.
Khaja

Import ID Configuration Scenarios and keep the same Business System names

Hi Guys,
Is it possible to transport ID Configuration Scenarios Objects between 2 XI systems and keep the same names for both sender and receiver Business Systems ? That is, to skip the SLD lookup for transport Source and Transport Targets systems ?
I tried to create the same Business Systems under the same name twice, but this was not possible. Any ideas ?
The reason is that I want to transport all the objects from one XI DEV server to another XI DEV server.
Thank you,
Best Regards,
Evaggelos Gkatzios

Hi,
We have done same but with bit of manual work (without Transport).
Create SLD object in target system with same name as in Souce XI system SLD.
IR & ID was exported using TPZ files from Source system & were imported in Target system.
It used same object names in both XI systems.
Regards
Sushil

Obligatory transport target for business system SAPR3D not found in System

HI All ,
We have installed New PI 7.1 system and stared migrating the interfaces from XI 3.0 to PI 7.1 . in Devlopement system .
IR object have been successfully deployed but while delopying ID objects got the following error . Obligatory transport target for business system SAPR3D not found in System Landscape Directory.
When I checked with business system transport target was not defined ., Please suggest how to go ahead further .
Thanks ,
Prakash

Hi Ravi,
Please go through below disucssion it is on the same line of your question.
Transport target for business system not found in System Landscape Director

Obligatory transport target for business system BS_DEV in SLD

Hi all,
   We are moving receiver detrmination from QA to PRD, there we are getting one error
"com.sap.aii.ibtransportclient.XiTransportException: caused by: ClientServerException exception:Impo
>>>rt failed because of business system transfer of object Receiver Determination   BS_DEV
>>>   *   *: Obligatory transport target for business system BS_DEV not found in Sys
>>>tem Landscape Directory caused by: com.sap.aii.ib.core.transport.api.PostprocessingException: Import
>>>failed because of business system transfer of object Receiver Determination   BS_DEV
*: Obligatory transport target for business system BS_DEV not found in Syste
>>>m Landscape Directory caused by: com.sap.aii.util.hmi.api.HmiMethodFault: caused by: ClientServerEx
>>>ception exception:Import failed because of business system transfer of object Receiver Determination
>>> BS_DEV      *   *:Obligatory transport target for business system WP
>>>C_Dev not found in System Landscape Directory caused by: com.sap.aii.ib.core.transport.api.Postproce
>>>ssingException: Import failed because of businesssystem transfer of object Receiver Determination
>>> BS_DEV     *   *: Obligatory transport target for business system BS_
>>>DEV not found in System Landscape Directory"
I am moving the same object from development to production, i feels ther is some problem in setting transport target.
BS_DEV target system is BS_QA, in development sld
BS_QA source system is BS_DEV anf target system Is BS_PRD in Quality sld
BS_PRD source system is BS_QA, in production.
The above error occurs when we are moving same object which i moved from development to quality to production.
whether i need to take obejct from quality and need to move that one to production, or i can use the same development object to production...?
Regards
Pradeep P N

Hi,
Even I am facing the same problem.
we have given the Transports Target as mentioned, but still facing the same error:
Deployment
Transport request   : DPIK900141
System              : QPI
tp path             : tp
Version and release: 375.30.25 710
CTS Deploy Service - Version 0.92 06.03.2007
========================================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/trans/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://sqnpi1.sap.sgroupit:51600
Double-stack system QPI
Deploy for XID
Deploy File = 2f8021d0f9ca11dea81e001a64925608
Start of Web service log
Deploy Service called with following parameters:
CommunicationData-Type:1
CommunicationData-Address:http://sqnpi1.sap.spoolzgroupit:51600/dir
CommunicationData-Host:sqnpi1.sap.sgroupit
CommunicationData-Port:51600
CommunicationData-User:'filled'
CommunicationData-Password:'filled'
Deployable(0)
Deployable-Type:1
Deployable-Id:/usr/sap/trans/data/DPIK900041/2f8021d0f9ca11dea81e001a64925608
com.sap.aii.ibtransportclient.XiTransportException: caused by: ClientServerException exception:Impo
>>>rt failed because of business system transfer of object Receiver Determination   DPI   SI_POS_CH_SN
Returncode:'8'
Deployment
End date and time : 20100105151741
Ended with return code: ===> 8 <===
Can anyone guide to solve it.

SLD- Same business System

Hi,
I have an APO system which has developement and production only.
We had developed an interface via PI where PI environments are in Dev/QA/Regression and Production.
Our SLD is shared between DEV/QA/Regression and separeate SLD in Production.
I am getting transport error between Dev and QA since it was not able to find a obligatory transport target.
I managed to download the same business system used in Dev for QA, but still the transport is giving error.
The business system is of ABAP type. Let me know how to deal with this.
Regards
Sam

Hello Sam,
in theory you're right, but this is not possible in SLD. Every Business System can only be assigned to exactly one environment (if I recall correctly it is a dropdown menu), so you cannot map it on itself. For each transport to a different environment you'll have to assign a different BS. So either you work with dummies or you leave out one transport, I don't think you have many other options.
One other option I have seen is two clients on the ABAP DEV system where one of them would serve as test/dev client and the other one as QAS client.
A different option would be to work with Business/Communication Components and avoid this transport rules. But since you use an ABAP system this is not the recommended procedure.
Regards,
Jörg

Transporting with diferent source systems.

Hi experts,
I am quite new in BW.
I have been developing some thing in sap BW.
I have Development, integration and Production in both BW and R3 source system. Each one should be connected with each other. So, development with development, integration with integration and production with production.
Here comes my doubt. All i have done is in the development systems. Now I want to transport and i don't know how to do this c'ause I want all the same things but connected to a different source system, and I think that when i am transporting I will have the Integration Business Warehouse connected with the development R3 system.
What should I do to avoid this and transport all but with a connection with a different system? Can anyone give me a clue please?
Thank you all!
Artur.

Hi,
BASIS team will comfigure the connection betwen BW systema nd R/3 system for all three environments.
R/3    DEV     -
>            QTY   -
>             PRD
              I                              I                        I
BW    DEV    -
>            QTY -
>               PRD
for transports, source systems Transports (R/3 datasource and tables) will be transported to QTYand PRD systems
and
for transports, BW Transports (BW infoobjects, DSO, Cube, Transformations....) will be transported to QTYand PRD systems.
[CTS and BW Transports]
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e]
Regards
Daya Sagar

TRANSPORT INSIDE SAME BW SYSTEM?

Similar Messages

Maybe you are looking for