Transports from XI 3.0 to PI 7.0

Hi all,
is it possible to transport from a NW2004 XI 3.0 (SP17) to a NW2004s PI 7.0 (SP09) system. As I know, the XI features are the same on both systems. Have somebody already done this with Repository and Directory Objects?
Stefan

Hi,
If you are looking at taking a back up of your IR and ID before you move to PI 7.0 and NW 2004s take a look at this article,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/fdfc51ff-0701-0010-9fb5-cd2ef5f98e10
Like you mentioned both XI 3.0 and PI 7.0 are the same in terms of features. So, there I dont think there will be any issue in terms of migrating objects as well.
Regards,
Bhavesh

Similar Messages

Can not transport from DEV to PRD (Hang up)

Hi Experts,
Please help.. I have this problem, was not able to transport from Dev to Prod, it just hang up.. I've read a lot in web how to solve this problem and did the following:
   ==> Stop all TP running in OS level
   ==> Delete all pending job in Import Monitor (with truck logo)
   ==> and the last to be done is to delete the data from table TRBAT, but it took so long to delete the data in that table.. What I've noticed is that the data left in table TRBAT is the transport number wherein user was log-off during transport execution (as in the middle of the process)..
What should be the solution of this problem, as we can not proceed with the transport of our changes made in DEV system, as it just hang up in there.. and I'm also having this problem in deleteing data from TRBAT table.
Thanks.
Edited by: Deo Pasion on Feb 20, 2010 7:25 AM

Hi,
Its well known problem which is discussed many times in many threads.
Did you check TP System Log and TMS Alert of the System ?
Execute RSTPTEST report to check the STMS configuration. Also check the existence/status of RDDIMPDP Background Job.
Please refer these useful threads with similar symptoms.
[Transport (STMS) issue + Hang|Transport (STMS) issue + Hang]
[regarding STMS_IMPORT Transport Hang.|regarding STMS_IMPORT Transport Hang.]
Also check this SAP Note 71353 - Transports hang during background steps.
Regards
Bhavik G. Shroff

Moving XI transports from QA to Prod server

Hello,
We are getting ready to send our XI transports from the QA server to the production server. We are currently using the file transfer method - we have not yet finished setting up the CMS server.
Now my question is this:
For the Integration Repository, am I supposed to send the same file created from our dev server to the production server, or do I create a new transport file from our QA box and send that file to production? Same question applies to the Integration Directory.
For example, the FileA.tpz gets created in the dev server, exported to the QA server. Developers are done testing in QA and want to move the objects to production. Should I export the same FileA.tpz to the production box OR generate a new transport file from the QA server (FileB.tpz) and send that to production box instead?
Thanks in advance.

Joy,
Ideally you should move from Dev to QA and from QA to Prod. Then everything will be in sync. If you move directly from Dev to Prod and if there any changes then they will not be in QA. So this should not happen.
Because only after developement you will move to QA. Once when you test in QA then you will move to Production from QA.
Check this weblogs for further info:
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
/people/marion.schlotte/blog/2006/03/30/best-practices-for-nwdi-track-design-for-ongoing-development
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
/people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
---Satish

Reg: Error while transporting from Quality to Production

Hi ,
I am facing a problem while transporting ODS from quality to production.. The same works perfectly when i transport from Dev to quality.
The Error Displayed while transporting is
Start of the after-import method RS_ODSO_AFTER_IMPORT for object type
The creation of the export DataSource failed
Password logon no longer possible - too many failed attempts
Error when creating the export DataSource and dependent Objects
Error when activating DataStore Object
The creation of the export DataSource failed
Password logon no longer possible - too many failed attempts
Error when creating the export DataSource and dependent Objects
Error when resetting DataStore Object to the active version
Kindly give me some suggestion ..
Thanks in advance
Regards
Guru

go to the source system RFC connection in SM59 and do a remote login - if you get the login page there then there is an issue with the RFC connection. also check if any other system is using the same RFC.. we had a situation where th R/3 connection was being used by 3 BI instances and everytime we reset the password , another system would lock the sme , ultimately we identified the systems and did a password reset in all the systems and then the issue got resolved.
but then we also faced the same issue you faced and it was related to login issues - check the remote login and that will tell you.

Ended with return code: === 8 === while doing transports from Dev to Test

Hi Experts,
We are doing transports from BD1 to BQ1 and getting this error message.
Could anyone please let me know why and what would be the solution for the following error message:
Execution of programs after import (XPRA)
Transport request   : BD1K900065
System              : BQ1
tp path             : tp
Version and release: 370.00.09 700
Execution of programs after import (XPRA)
End date and time : 20070803133308
Ended with return code: ===> 8 <===
Thanks in advance.
Best Regards,
Chandu.

Raymonds,
There is huge list of errors coming up. Some of them are as below:
Navigation attribute 0SALESORG is missing in characteristic 0PLANT
Navigation attribute 0SALES_DIST is missing in characteristic 0PLANT
Characteristic 0RT_LOCATIO: Referenced characteristic 0PLANT not (actively) available
Attribute 0INT_CUST from characteristic 0SALESORG not (actively) available
Attribute 0CRM_MKTELM from characteristic 0UCCONTRACT not (actively) available
Attribute 0CRM_MKTELM from characteristic 0UCCONTRACT not (actively) available
Hierarchy characteristic 0BPARTNER of characteristic 0UCCONTRACT is not active
Characteristic 0UCOUTLCONT: Referenced characteristic 0UCCONTRACT not (actively) available
Characteristic 0UCOUTLCONT: Referenced characteristic 0UCCONTRACT not (actively) available
Thanks in advance.
Best Regards,
Chandu.

Problems when transporting from DEV to PROD

Hi experts, I have problem during transport from DEV to Production.
We have a DEV, QAS and PRODUCTION and we have transport from DEV to QAS very well. But when we transport from DEV to PROD, recibe an error like:
After beginning the import method RS_IOBC_AFTER_IMPORT for Objects types IOBC mode (activation)
Failed to verify catalog InfoObjetos ZCM_UNIMET_CHA01
The InfoObjeto ZCM_RENC version does not exist in active
The InfoObjeto ZCM_RENM version does not exist in active
1.The Query is: Wy if the transport go OK from DE to QAS, then The transport from DEV to PROD terminated in error?.
2. There are any items to check in production before to transport?.
PD: All of the Objects in DEV are in ACTIVE status
Tanks,
Ramon Sulvaran

The transport ended in QAS with error code (4) and ended in Producion with error code (8), the detal of the error in Production begin with:
Home After import RS_ODSO_AFTER_IMPORT method for type (s) ODSO object (trigger mode)
Activation of DataStore objects of type Object
Check DataStore objects of type Object
DataStore Object Verification ZCM_DS01
The DataStore object is consistent ZCM_DS01
Burning the DataStore objects of type Object
Internal activation (DataStore Object)
Pretreatment / Creating DDIC objects to DataStore Object ZCM_DS01
Table / View / BIC/AZCM_DS0100 (type 0) DataStore object recorded ZCM_DS01
Create / Delete the indexes for the active table
Table / View / BIC/AZCM_DS0140 (type 4) recorded ZCM_DS01 DataStore object
Type of table / BIC/WAZCM_DS0100 recorded
Table / View / BIC/VZCM_DS012 (type VIEW) recorded ZCM_DS01 DataStore object
Log ZCM_DS01 DataStore object changes was recorded successfully
Writing Object Catalog entries (Tadiran)
He has written the object TABL / BIC/AZCM_DS0100 in catálgo objects (Tadiran)
He has written the object TABL / BIC/AZCM_DS0140 in catálgo objects (Tadiran)
He has written the object TABL / BIC/VZCM_DS012 in catálgo objects (Tadiran)
He has written the object TTYP / BIC/WAZCM_DS0100 in catálgo objects (Tadiran)
Activate all ABAP Dictionary objects (5):
Error / Warning in progr.activación Dict., Detailed log> Detail
Activate table / BIC/AZCM_DS0100.
Lack of expansion to the category table
Lack of extension category for include or subtype .......
When i go to BW Production to check teh object. I see tha the Object was create but in inactive status (grey color). When y Try to Actiavate it y see the error: Error/ Warning in program Activation Dcit. Detailed Log -> Detail

Web Template Changes not visible after transport from Development to Test

Weu2019ve run into a problem doing web development in BI 7.0 that I suspect someone has seen before and may quickly be able to point us in the correct direction. Changes that are made to web templates in the Web Application Designer are correctly transported from development to the test environment, but we are still seeing the old version of the template when the report is executed. We are able to see the web template changes in the Web Application Designer in the test environment. We believe this is a caching issue and have cleared the query cache and the HTTP cache in SMICM. Unfortunately, this has not resolved the issue. Can you suggest another approach to resolve this issue?

Not sure what you mean by browser cache. We have deleted history, cookies, and all temporary Internet files. The issue isn't limited to a single user, but exists for all users. Through extensive testing we have established that you are able to see the web template changes in test in the WAD(Web Application Designer) after they have been transported from development, but can only view the changes when the web template is run for the first time. Changes to existing templates can be seen in the WAD in test, but are not seen when the report is run. The old version of the template appears to held in cache somewhere, but we haven't been able to find it and clear it.

HT202879 I am switching to Apple macbook pro from Windows laptop. Is Apple compatible with Microsoft Office? How can I transport from Windows to Mac? What I have saved on external hardrives, will I be able to open it on Mac?

I am switching to Apple macbook pro from Windows laptop. Is Apple compatible with Microsoft Office? How can I transport from Windows to Mac? What I have saved on external hardrives, will I be able to open it on Mac?

Office for Mac, http://www.microsoft.com/mac/products, can open/edit/create Office documents.If your external drive is formatted NTFS then you can copy the Office documents to your computer and work on them. You won't be able to save the files back to your NTFS formatted drive. But you will be able to save the documents to your internal drive. You can move all the external files to your internal drive then format the external drive for Apple. Then you can copy the files back to your external drive for ongoing use.

I am switching to Apple macbook pro from Windows laptop. Is Apple compatible with Microsoft Office? How can I transport from Windows to Mac? What I have saved on external hardrives, will I be able to open it on Mac?

I am switching to Apple macbook pro from Windows laptop. Is Apple compatible with Microsoft Office? How can I transport from Windows to Mac? What I have saved on external hardrives, will I be able to open it on Mac?

Is Apple compatible with Microsoft Office?
Any computer is compatible as long as it can read and write Office files. But for perfect (or at least near perfect) compatibility, you would want to purchase Office 2011 for Mac.
How can I transport from Windows to Mac?
You can't directly transport any installation of Windows. All PC's come with a machine specific version of Windows intended for that PC. They don't have all of the hardware drivers the retail disks cover.
If you want Windows on your Mac, you would first purchase a full version copy (NOT an upgrade disk) of Windows 7 or 8. Those are the only supported versions on newer Macs. You install it through the supplied Boot Camp utility that comes with the Mac to create a new partition for Windows, and then install the retail copy of Windows you purchased.
The reason only these versions of Windows are supported is the same basic reason as a machine specific version of Windows for a PC. Apple only includes the necessary Mac hardware drivers for Win 7 or 8 on new Macs.
Once Windows is installed, you could then install the version of Office for Windows you already own. The nuisance of a Boot Camp partition is that you have to physically boot to either Windows or OS X, so you can only use the apps of the OS you're in at the time. To use both at once, you'd have to use virtual machine software (Parallels, VMware, VirtualBox) and then install Windows within that. Then you'd be able to run Windows inside of OS X and have access to both at the same time.

Transporting from DEV server to Production Server

Dear Experts,
Like in ABAP and other SAP modules we are having Transport Requests to transport from Dev server to Production server In XI how can we transport all the configuration done by me from Dev server to Production server.

Hi,
In XI we can transport in two ways :
1) File Transport
2) Using CMS which needs configuration to be done
Using the File Transport you can easily the Export the Objects and Import the Objects in the Target system.
Select the Object in the Design or Configuration ->right Click you will find Export option.
When you select the It creates the .tpz file which can be imported in the Target System
Using file transfer or CMS we transport xi objects.
Transporting XI from DEV to QA
Look into this blog for how to export / improt IR and ID objects,
XI Software Logistics II: Overview
XI Software Logistics 1: SLD Preparation
Transporting IR,ID Objects using File System
http://help.sap.com/saphelp_nw2004s/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/5e56006c17e748a68bb3843ed5aab8/frameset.htm
Regards
Ganga

Transporting from DEV to QA

We have 3 different sld's for DEV,QA,and PRD systems.
i need to transport my XI objects from DEV to QA.i'm working on standard XI contents.
i need answers for my following questions.
1.if i use full export for transporting SLD from DEV to QA,can i use the same tecnical systems and business systems in QA?
Can T.S and B.S also get transported from DEV to QA?
2.In such case how to define business systems groups and transport targets?
pls don't send any blogs..i've all the blogs
thanks
Abhijit

Hi,
1.if i use full export for transporting SLD from DEV to QA,can i use the same tecnical systems and business systems in QA?
Can T.S and B.S also get transported from DEV to QA?
You can use same technical systems and Business systems.
1. Go to Dev SLD and Export all your SWCV, Products, Technical and Business Systems. This is nothing but saving of the SLD objects as a CIM file on your local machine. You would also need to export the Technical And Business System poitning to your XI integration server .
2. Go to the QA SLD and then import these objects exported in Step 1 in QA SLD
3. Now, create the QA Tech and Business Systems in the QA SLD
4. Go to the Dev Business systems imported on the QS SLD and you will have an option Transport Targets. In this map the Source Business System to the Target Business Systems.
Make sure that all Dev Business Systems have the correspodning Transport Targets for the QA Business SYstems
5. Now if you import the ID objects in QA , the business systems name will be renamed automatically.
2.In such case how to define business systems groups and transport targets?
You need to create Transport Groups on your QA SLD. One for Dev and One for QA. You can create Transport Groups only for Integration Server Business Systems.
And this is why you would need to export the Dev XI technical System and Business System from the SLD of Dev and Import it into the QA SLD.
2. Create the transport groups and then assign all Dev Business Systems to Dev Group, all QA Business Systems to QA group and then create the transport targets.
You use the Option related Integration server in the Business Systems to assign a Business System to a Group.
Refer
Problem regarding xi transport
Thanks
Swarup
Edited by: Swarup Sawant on Feb 26, 2008 11:55 AM

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,

DataSources transport from development to QA TESTING???

Hi Gurus,
I developed some objects in my D system using a generic extractions. I used 3 DataSources .
Ii transported all my SAP BW object in the testing system. now I need to collect my 3 DataSource in the R/3 development System to the R/3 system. Please can anyone show me the steps. I tried all day but no result. Please help me, I need the steps.
Thank You Gurus.

Hi
You are using Tbales, so collect Table if it is Z/Y table, if it is SAP table then not required.
1.Collect Tables and DataSources in request and transport from D ECC to Q ECC.
2.Replicate DS in Q BW system.
3.Collect InfoObjects and Transport from D BW to Q BW.
4.Collect Cube/DSO and Transport from D BW to Q BW.
5.Collect Multiproviders if you have any and Transport from D BW to Q BW.
6.Collect Transfer/InfoSource and Transport from D BW to Q BW.
7.Collect Update Rules and Transport from D BW to Q BW.
8.Collect Reports and Transport from D BW to Q BW.
Thanks
Reddy

Transports from development to Test/Production

Hi there,
While transporting objects from development to QA or Production, is there any way we can change the the name of the target staging database. For example, if TableA is the target table going to stageA database and when i move this object from development to QA or Production where staging database has a different name. So how can i handle this..should i have same database names in all the environments Dev, QA and Prod? i know we can do it manually changing staging database name one by one for each object but how can we handle it if we have hundreds or thousands of objects?

You should setup and use multiple configurations on a single datastore. The whole point (well, almost the whole point) of the ability to setup multiple configurations, pointing (typically) at different databases, inside a single datastore is to be able to re-point a dataflow at a different database without recoding. To "transport" from dev to QA, for instance, is as simple as either changing the default configuration of a datastore (from the dev database to the QA database), or making use of system configurations, which are just named sets of datastore configurations, which are, then, picked at runtime (or when scheduling a job). Of course, your schemas need to be essentially the same between environments.
Best wishes,
Jeff Prenevost

Transports from ECC 5.0 to ECC 6.0

Hello,
We are considering using transports from the 5.0 system to make configuration changes in the 6.0 system (and even some workbench items). Besides, the obvious issues with conflicting configuration, is there a technical reason why they should not attempt this? I look for notes to know it, and there are the note NOTE 1090842, but there are no answer for transports between realese ECC 5.0 to ECC 6.0. Do you know if it is a special case?
Thanks in advance for your answer,
Xènia

Hello,
This is always a bad idea.
However, if you feel like that, I only recommend it if you are transporting Z objects that you know perfectly. This way you can make corrections at the very moment the potential problem happens. Before the import, please compare both objects, in release 5.0 and 6.0, and look for the differences. Plan what would happen if the 5.0 object replaces the 6.0 one.
Don't do it with standard objects.
Regards
Francisco

Transports from XI 3.0 to PI 7.0

Similar Messages

Maybe you are looking for