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

Similar Messages

Checks to be done before moving the objects from DEvV to PROD systems

Hi,
Please provide the standard methods and checks to be done in the transport requests before moving the objects from DEv to PROD.
Please help us here.

In se10 find your request and
Upper left corner - Request\task -> Complete check -> Object (syntax check) and Check Request Consistency.
This you can do for your request and all the tasks included in your request.
Note: Transport may still fail due to numerous reason (i.e) not all the objects needed are collected in the request,
but at atleast it gives some assurance that objects are not blocked in other requests etc...

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

Notification about errors during transport from DEV to QAS server.

Hi Guys.
Is there any way of alerting the user about the errors that arise when moving the transaction from DEV client to QAS client?
For Instance,In DEV the program may be working fine and while transporting sometimes errors can arise by not including all the necessary files while moving to QAS server.
Kind of auto-email facility notifying the user...

Hi,
there might be some standard functionality for TMS but if you can't find anything then you can still use BADI CTS_IMPORT_FEEDBACK. The only method if this BADI is called right after import of each transport.
Cheers

Error in PC while transporting from Qual to Prod

Hi All,
i am getting the error while tarnsporting the PC from qual to prod.I have introduce only AND event in PC and change one Attrib Change step.
In TR i have collected PC,Event,Attrib Change step.
But while transporting it result in error at one DTP step.I have checked the corresponding DTP is present there in Prod but with diffrent technical name.
As far as i know it should have replace the corresponding DTP present in prod..
Is this the error from BI side or connection error between system from basis.
Or is this something related to system being out of sync with eachother.
i am also showing you the error i get as below:
Version 'M' of chain ********* was saved without checking
Results of check for process     in chain :
Results of check for process     in chain :
Results of check for process *DTP_LOAD DTP_4KYC4AJY4UAPLDJ4MZE8YYUYL in chain* ZA_SD_006:
I got error in this DTP
Results of check for process LOADING ZPAK_4GJLZPDJRV346VYKJLGKTDK7S in chain ZA_SD_006:
Start of the after-import method RS_RSPC_AFTER_IMPORT for object type(s) RSPC (Delete Mode)
Start of the after-import method RS_RSPV_AFTER_IMPORT for object type(s) RSPV (Delete Mode)
Start of the after-import method RS_EVEN_AFTER_IMPORT for object type(s) EVEN (Delete Mode)
     / | Errors occurred during post-handling RS_AFTER_IMPORT for EVEN L                                                                     |
RS_AFTER_IMPORT belongs to package RS
     / | The errors affect the following components:                                                                                |
     / |    BW-WHM (Warehouse Management)                                                                                |
     / |   Post-import method RS_AFTER_IMPORT completed for EVEN L, date and time: 20110411140348                                              |
Start of subsequent processing ... 20110411140341
End of subsequent processing... 20110411140348
Start of................ 20110411140348
     / |        End of.................. 20110411140348                                                                                |
Execution of programs after import (XPRA)
End date and time : 20110411140348
     / | Ended with return code: ===> 8 <===

Hi Deepak,
When you migrate DTPs from Dev to Prod , a new DTP ID are generated in Prod system and your DTP in the Process chain points to Dev's DTP and that is why you get this error
What i can think of is this scenario:
1. Original chain created and transported to Production. There due to some requirement the DTP would have changed(some body deletd the original one and created new one). Now the existing chain in production have the new DTP created there.
2. When u tried transporting the original chain from Dev it had the DTP created initially.
3. Since the DTP existing in Prod is having a different technical name than the one initially created in Dev so due to this this mismatch it might not get activated.
4. So better to create the DTP there itself and add it to the chain.
Regards
Raj

Transport from DEV to PROD BPC 7.5

Hi
i had a question of transporting AppSets from DEV to PROD System.
On the PROD Systems are no AppSets the PROD System is completly new.
Is it possible to transport the AppSets directly from the DEV to the PROD or must we first make a Backup in the DEV and an Restore in the PROD.
Thank you for your help.

Hi Carsten,
As far as i understand you need to transport application sets individually, from development to production. The object type ASET and APPM refer to an application set and application respectively.
As mentioned above, you can check and confirm from SAP Support if the back up mode ia now available to users.
Hope this helps.
Regards,
Poonam

Moving a transport from Q/A to Production

I have imported a transport from Development to Q/A. How do I now import it into production? Thanks

Niten
After testing objects in QA and if you feel every thing is OK then transport into Production system. This transport also will go directly from Dev to Production but not from QA to Production.
Same Transport number which you moved to QA. You don't have to create other one.
Hope this helps
Thnaks
Sat

"No service for system..." after transporting from dev to prod

Hi,
again i have a problem like some other guys also had. I already checked several postings concerning this issue!
We transported dev-objects to prod, also ID-object like Business Systems.
The sender side now changed their communication for sending IDoc's to our Prod-XI. While sending IDoc's form Prod R/3 they get "no service for system SAPPSI, client010.." etc.
I already checked:
1. idx1 port is SAPPSI pointing to right destination PSI
2. idx2 all necessary Metadata are loaded
3. checked adapter specific identifiers in ID and also reloaded them with no change!
4. in receiver IDoc CC i added RFC-Dest: PSI and Port is SAPPSI
5. did a cache refresh!
I need to let you know that we are using one SLD and already communicated with the sender-prod r/3 -system to SAP XI -DEV.
can someone please help us?! we have no clue what might be wrong!!
br

Well i have some strange thoughts:
when the idoc is send in sender-system the values on sender informations are:
Port: SAPPSI
Partner number: PSICLNT010
Type: LS
The error we receive is:
no service for system SAPPSI, client 010 in Integration Directory
Shouldn't there be the Partner-Number like PSICLNT010?!
Can someone confirm and tell me if i am right?!
br

Very urgent-moving ora9i db from win2k to win2003 server

hi
i need step by step solution to move oracle 9i database from win2k to win2003 server.
i thank u in advance who help me at right time.

Steps:
1. install oracle software in windows 2003.
2. shutdown database 9i
3. copy all files in old database to windows 2003 server.
4. use "oradim" to create an instance
5. change some locations for datafiles/controlfiles/logfiles... if needed
6. startup your 9iDB in windows 2003.

Does moving SP code from DB to App Server help scale an application?

We have an application developed using Oracle 10g Forms / 10g DB? All our processing is done using SPs. So they all run in the DB server. Even our Inserts/updates/deletes to a table are handled by SPs.
The site with the maximum simultaneous users (i.e. concurrent users) is one with 100 concurrent users.
We have prospective customer whose requirement is 300 concurrent users. Our application won't be able to handle it since the DB server is a single processor server with limited memory.
One suggestion was move the SPs to the App Server by moving them to the Form. Since OAS has a PL engine they will run in the App Server and hence remove the workload of the DB.
I don't buy this. My point is, even if SPs are moved to the app. server still the SQLs will run in the DB server, right?
So what is the advantage?

christian, I just modified the original post thinking nobody will reply since it's very long. Thanks a lot for the reply. For others and myself also here is my original question.
I have a problem like this: Take this scenario. We have a TELCO app. It is an E-Business Web Application (i.e. Dynamic Web Site) developed using ASP.Net/C#. App. Server is IAS and DB is Oracle 10g. IAS and the DB reside in 2 servers. Both are single processor servers.
The maximum simultaneous user load is 500. i.e. 500 users can be working in the system at one time.
Now suppose 500 users login at the same time and perform 500 different operations (i.e. querying, inserts, updates, deletes). Now all 500 operations will go to the App Server. From there the C# code will perform everything using Oracle stored procedures (SP). I.e. we first make a connection to the DB, SP is invoked by passing parameters, it will perform the operation in the DB, send the output to the App. Server C# code and we will close the Oracle connection (in App Server. C# code).
Now, the 500 operations will obviously have to wait in a queue and the SQLs will be processed in the DB server.
Now, question is how does CONNECTION POOLING help in this situation?
I have been told that the above method of using DB SP to perform processing will make the whole system very slow since all the load of the processing has to borne by the DB Server and since DB Operations involve disk I/O it will be very slow. They say you cannot SCALE the application with this DB Processing mode and you have to move to App. Server processing mode in order to scale your application. I.e. If the number of users increases to 1000 our application won’t be able to handle it and will get very slow.
What they suggest is to move all the processing to the App. Server (i.e. App. Svr. Memory). They also say that CONNECTION POOLING can help even further to improve the performance.
I have some issues with this. First of all to get all the data to the App server memory for each user process from the DB will not only require disk I/O, it will also involve a network trip. That will obviously take time. Again the DB requests to fetch the data will have to wait in the DB queue. Then we do the processing in the App. Server memory and then we have to again write to the DB server which again will require a network trip and disk I/O. According to my thinking won’t this take MORE TIME than doing it in the DB server??
Also how can CONNECTION POOLING help. In C# we OPEN a connection ONLY just before run the SP or get the data and we close the connection just after the operation is over.
I don’t’ see how CONNECTION POOLING can improve anything?
I also don’t see how moving data into the App. Server from the DB Server can improve the performance. I think that will only decrease performance.
Am I right or have I missed something?
Edited by: user12240205 on Nov 17, 2010 2:04 AM

SAP "Z" Script Transport from DEV -- TO-- QTY Server

Experts....
We have created a Z SAP Script. in DEVELOPMENT CLIENT : 100
We have successfully transported the changes from DEVELOPMENT CLIENT to UNIT TESTING CLIENT 120 in the same system thru SCC1.
UNIT TESTING RESULTS are OK, and our DEVELOPER has given a request to import into production.
But we imported the request, But changes are not reflecting in QUALITY.
I found below thread but i failed to understand...the last steps...
Can any one please help in this regard.
SAP Script transport issue
Rgds

Finally.....We could able to close this....
Weunderstood....to do inital fill in target client we do it from "000" clinet to "XXX" target clinet
once it is available ..the rest all goes with CLASSIC TRANSPORT APPROACH.
Not sure why the inital Transport request with changed did nor worked.
With the help of ABAP Expert...we just reactivated the in SE71 and added into request
imported the request into Quality & Worked..
When the inital fill is completed for SAP Standard ,
the rest of changes to is managed thru SAP Classic Transport Method.
For "Z" script..even no where connected with "000" client.
As we fixed with above assumptions...we conclude as above....
i request any expert to correct us if our assumptions in wrong direction.
Rgds

DBIF_RSQL_SQL_ERROR while doing a transport from DEV to PROD

Hi,
We are trying to transport some requests from our BW Development to BW Production. As we are importing the request we are facing the following two runtime errors in Dev.
1.
Database error text........: "ORA-01654: unable to extend index SAPSR3.TBTCO~1
by 128 in tablespace PSAPSR3"
Internal call code.........: "[RSQL/INSR/TBTCO ]"
2.
Database error text........: "ORA-01653: unable to extend table
SAPSR3.TMSALOGAR by 128 in tablespace PSAPSR3"
Internal call code.........: "[RSQL/INSR/TMSALOGAR ]"
Looking forward to your help on this error. Additionally please let me know if this has got anything to do with Production? Or as this is occuring in Development this is an development issue only?
Thanks,
Andy Kroos.

Ask your basis guys to increase the table space...
check this thread...
[Error : DBIF_RSQL_SQL_ERROR;
--- Thanks...

BEx Query objects transported from Dev to Prod Test do not overwrite

Hello,
I'm migrating BEx queries that were developed in a Dev instance and then packaged and imported into a prod test environment. The queries that already exist in qual are not overwritten with the changes, and the transport imports successfully. New queries import just fine and without issue. I'm not sure if this is a problem with how I am packaging the query for transport or some level of pre-work that is not being done in Prod test. Basis has confirmed that they are allowing re-writes when Importing.
Any suggestions?
Thanks.
Matt

Hi ,
Whenever we create a query in the System it generates reference ID's ( ELTUID,SELTUID,COMPUID etc) in backend.
For e.g.if you create a query in your quality system (Z_TEST) it will have a COMPUID generated for it (e.g ABCD).
Now when you create a query in Dev system (with the same technical name Z_TEST) a new COMPUID will get generated (e.g EFGH)
So when you transport Z_TEST to QUALTY ,it will create a new entry against COMPUID.thus having two instances of the same query.So best option would be to delete the old instance after transporting the new instance.
This wil solve your problem.
-Vikram Srivastava

Problem with sap script while transporting from dev to quality server

Hi experts,
In dev server i am getting correct output in sap script.But when it is transporting to quality server alignment is different.Printer name is same both in dev and quality.Please give an answer for this query.
Thanks
suresh

Hi Suresh,
This could be a problem with the Sapscript buffers. Try running the report RSTXDELL on the system to clear the Sapscript buffers?
To do this you can use RSTXDELL report with default settings except it is better to have * instead of the current client number in the Client field.
After this, create a new spool and see if the problem is resolved?
Regards,
Aidan

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

Similar Messages

Maybe you are looking for