Transports from BI Dev to BI QA

Hi Frinds,
In general what are the transports in the BI Dev environment which should be moved to create a BI QA client ? Any inputs greatly accpeted .
Thanks in advance,

Hi
Before importing a transport; we should make sure the following:-
1)     You have a request from the development team with a CID attached to the related CR (Change Request)
2)     You have done all pre-transport manual actions.
3)     There is no modifiable transport in the system (Except Dev. Boxes.)

Similar Messages

Transport from bi dev to bi prod - Ended with return code: 8

In transport connection we have collected infocube an its all related objects and created a transport request when moving from dev to prod it is showing this error log file
    KBDK900082       HBT-BI       HBT-BI/CUBE ZIC_C03/
        KBDK900083   HBT-BI       Repair
        KBDK900084   HBT-BI       Development/Correcti
            Application components
            InfoArea
            InfoCube
            Data Transfer Process: Active Version
            InfoObject
            Communication structure
            DataSource Replica
            InfoPackage
            Transfer Rules
            InfoSource transaction data
            DataStore Object
            Routine
            DataSource in BW
            Communication Structure for Transformation
            Transformation
            Update rules
Log File:                /usr/sap/trans/log/KBDR900082.KBP
         Execution of programs after import (XPRA)
         Transport request   : KBDK900082
         System              : KBP
         tp path             : tp
         Version and release: 376.01.14 701
         Post-import methods for change/transport request: KBDK900082
         Post-import method RSOD_SBEL_AFTER_IMPORT started for SBEL L, date and time: 20110907155447
         Start of the after-import method   for object type(s) SBEL (Metadata Documents)
         Post-import method RS_AFTER_IMPORT started for UPDR L, date and time: 20110907155448
         Start of the after-import method RS_AREA_AFTER_IMPORT for object type(s) AREA (Activation Mode)
         Start of the after-import method RS_APCO_AFTER_IMPORT for object type(s) APCO (Activation Mode)
         Start of the after-import method RS_ROUT_AFTER_IMPORT for object type(s) ROUT (Activation Mode)
         Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Activation Mode)
         Syntax error Incorrect statament: Expression missing Operand mi in row 20 position 0
         Characteristic 0UNLD_PT_WE: Error when activating or checking the transfer routine
         Attribute 0UNLD_PT_WE from characteristic 0VENDOR not (actively) available
         Characteristic 0VEND_PRIOR: Referenced characteristic 0VENDOR not (actively) available
         Characteristic 0VEND_PRIOR: Referenced characteristic 0VENDOR not (actively) available
         Attribute 0VENDOR from characteristic 0APO_LOCNO not (actively) available
         Attribute 0VENDOR from characteristic 0APO_LOCNO not (actively) available
   Characteristic 0APO_PLLOC: Referenced characteristic 0APO_LOCNO not (actively) available
   Characteristic 0APO_PLLOC: Referenced characteristic 0APO_LOCNO not (actively) available
   Attribute 0APO_LOCNO from characteristic 0APO_RESNAM not (actively) available
   Attribute 0VENDOR from characteristic 0APO_RESNAM not (actively) available
   Key figure 0APO_RSUTIL: Aggregation reference char.0APO_RSUTIL is not (actively) available
   Characteristic 0APO_STORES: Referenced characteristic 0APO_RESNAM not (actively) available
   Characteristic 0APO_STORES: Referenced characteristic 0APO_RESNAM not (actively) available
   InfoObject 0APO_LOCNO (in compound of characteristic 0APO_SUBLOC) not (act.) available
   Characteristic 0APO_VMILOC: Referenced characteristic 0APO_LOCNO not (actively) available
   Characteristic 0APO_VMILOC: Referenced characteristic 0APO_LOCNO not (actively) available
   Attribute 0VENDOR from characteristic 0BPARTNER not (actively) available
   Attribute 0APO_LOCNO from characteristic 0BPARTNER not (actively) available
   Attribute 0VENDOR from characteristic 0BPARTNER not (actively) available
   Characteristic 0BPARTNER1: Referenced characteristic 0BPARTNER not (actively) available
   Characteristic 0BPARTNER1: Referenced characteristic 0BPARTNER not (actively) available
   Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
   Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
   InfoObject 0BPARTNER1 (in compound of characteristic 0BPRELATION) not (act.) available
   InfoObject 0BPARTNER2 (in compound of characteristic 0BPRELATION) not (act.) available
   Characteristic 0BP_CONS: Referenced characteristic 0BPARTNER not (actively) available
   Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
   Characteristic 0BPARTNER2: Referenced characteristic 0BPARTNER not (actively) available
   InfoObject 0BPARTNER1 (in compound of characteristic 0BPRELATION) not (act.) available
   InfoObject 0BPARTNER2 (in compound of characteristic 0BPRELATION) not (act.) available
   Characteristic 0BP_CONS: Referenced characteristic 0BPARTNER not (actively) available
   Characteristic 0BP_CONS: Referenced characteristic 0BPARTNER not (actively) available
   Attribute 0BPARTNER from characteristic 0BP_GRP not (actively) available
   Characteristic 0BP_RESPPER: Referenced characteristic 0BPARTNER not (actively) available
   Navigation attribute 0BPPOSITION is missing in characteristic 0BPARTNER
   Navigation attribute 0USER_NAME is missing in characteristic 0BPARTNER
   Navigation attribute 0USER_SYST is missing in characteristic 0BPARTNER Attribute 0CRM_MKTELM from characteristic 0PSGUID not (actively) available
InfoObject 0PLANT (in compound of characteristic 0QUALIFIC) not (act.) available
Characteristic 0RT_CUSTPL: Referenced characteristic 0CUSTOMER not (actively) available
Characteristic 0RT_CUSTPL: Referenced characteristic 0CUSTOMER not (actively) available
Characteristic 0RT_LOCATIO: Referenced characteristic 0PLANT not (actively) available
Navigation attribute 0COMP_CODE is missing in characteristic 0PLANT
Navigation attribute 0COUNTRY is missing in characteristic 0PLANT
Navigation attribute 0COUNTY_CDE is missing in characteristic 0PLANT
Navigation attribute 0DISTR_CHAN is missing in characteristic 0PLANT
Navigation attribute 0PLANTCAT is missing in characteristic 0PLANT
Navigation attribute 0POSTAL_CD is missing in characteristic 0PLANT
Navigation attribute 0PURCH_ORG is missing in characteristic 0PLANT
Navigation attribute 0REGION is missing in characteristic 0PLANT
Navigation attribute 0RMA_FLAG is missing in characteristic 0PLANT
Navigation attribute 0RMA_REFPLT is missing in characteristic 0PLANT
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
Characteristic 0SOLD_TO: Referenced characteristic 0CUSTOMER not (actively) available
Navigation attribute 0ACCNT_GRP is missing in characteristic 0CUSTOMER
Navigation attribute 0BPARTNER is missing in characteristic 0CUSTOMER
Attribute 0BPARTNER from characteristic 0SOLD_TO not (actively) available
Navigation attribute 0COUNTRY is missing in characteristic 0CUSTOMER
Navigation attribute 0CUST_CLASS is missing in characteristic 0CUSTOMER
Navigation attribute 0CUST_MKT is missing in characteristic 0CUSTOMER
Navigation attribute 0DBDUNS_NUM is missing in characteristic 0CUSTOMER
Navigation attribute 0INDUSTRY is missing in characteristic 0CUSTOMER
Navigation attribute 0KEYACCOUNT is missing in characteristic 0CUSTOMER
Navigation attribute 0NIELSEN_ID is missing in characteristic 0CUSTOMER
Navigation attribute 0OUTL_TYPE is missing in characteristic 0CUSTOMER
regards

Hi Krishna,
It seems you have not collected all the info objects and reference info objects into transport request.
Collect the objects into transport request using transport connection in RSA1.
while selecting CUBE, select data flow before, it will collect all the objects into request.
if any business content info objects are there first install from business content and collect into transport request.
Regards,
Venkatesh

Transport Error from BI Dev to BI Production

Hi all,
I am started the BI transport from BI dev to BI production. we are not having BI quality.
I am transporting the DSO and the total data flow to the production.
I have copy the 0FIAR_O03 DSO to the Z DSO and i am transporting thr Z DSO(ZFIAR_O3) to BI production.
While transportation i am getting below error.
DataSource 8ZFIAR_O3 does not exist in source system EBP740 of version A |
Reading the Metadata of ZFIAR_O3 ...
Creating DataSource 8ZFIAR_O3 ...
Application component DM of DataSource 8ZFIAR_O3 does not exist
Error when creating the export DataSource and dependent Objects
| Error when activating DataStore Object ZFIAR_O3
Please suggest.
I have transported all the objects propely.
Regards,
Macwan James

Hi James,
This issue could be because the Application Component hierarchy might not be installed in Production System.
Collect the Application Components and transport to Production. Then reimport the failed request, should resolve.
Regards,
Chathia.

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

Transportation of Datasouces from BI DEV to BI QAS

Hi all,
         We have been facing some troubles while transporting from the BI DEV to BI QAS side .Our R/3 DEV source system is IED200 and R/3 QAS is IED400. I have trasnported all respective datasources from R/3 DEV to R/3 QAS , replicating the same on the BI QAS side.While Transportation of the datasources from BI DEV, its throwing back and RC=8 error . Its states that the Source System IED200 does not exist. Can you please suggest what is the next step that is to be taken ?

Dear Prathibha Pillai,
Maintain source system conversion in Quality system.
RSA1 --> Transport Connection --> Conversion(see button)
Maintain new entry:
Original Source system     Target Source System
IED200                             IED400
Then re import.
Hope it Helps
Srini

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

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

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

Query created in BW dev, modified in BW Q and want to transport from Q to P

Hello all,
I have created query in BW dev and then transported to BW qa, we had to modifed the query in BWqa system. There are a lot of queries we have done like this.
Now I want to transport only the queries (BEX objects) from Qa to Prod staright away, can that we done. If yes, do we have to create new package for transporting the bex objects.
Also how do we change the assigned packages on the elements which are not modified/created in QA since they already have package assigned to them wheich was created in BW dev.?
Thanks in advance,
Raj

What K J is trying to say is that the usual and recommendable transport path is
Dev to Quality -- Test the changes throughly
if satisfactory
DEV to Prod (the same transport needs to be imported into Prod)
else
go back to Dev and make the required changes and go back to the above step of testing in Q until sucessful.
By moving the same transport across the systems, you can ensure that all the systems are in sync. Lets say you started a query in Dev, moved it into Q and realized that you didnt add a field. Instead of coming back to Dev to do this, if you start making changes in Q (many clients do not allow this, but I've heard of some which do), collect the transport and move it into Prod...then the Q and Dev systems are out of sync! The query in Dev and that in Q are not the same.
Assign pts if helpful.

Handle metadata of configuration objects when transported from DEV to QA?

All,
I was reading this blog /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
<i>"Unlike IR when we import the scenarios in ID the configuration metadata will be lost and have to be manually entered in the QA ID. For Ex: Parameters like source directory, filename scheme, FTP server will vanish and have to be entered appropriately as required for QA sand box. After entering the metadata we need to activate all the scenario objects in the ID. After successful activation your interfaces are ready for testing."</i>
From the above I understand there are somethings(like adapter metadata..) that has to be entered manually when the objects are transported from dev to QA.
So my question is, for what all objects of ID needs metadata to be entered manually in QA.
Party?
Business systems(business systems, bus servcies, integration process)?
Communication channels?
Receiver determination?
Interface Determination?
Sender Agreement?
Receiver Agreement?
I appreciate your reply
Thanks
KK

Hi,
first of all it's not adapter's metadata
(adapter's metadata is something completely different)
the "thing" that will dissapear is the adapters'
configuration (configuration of your communication channels) - that's all
RFC destination (idoc adapter) ftp server (file adapter) etc.
basically all you need to do
is to fill it one every system (QAT, PRD etc.)
Regards,
michal

STMS , logs? for transports from DEV 200 to QAS 200, 201 & 202

We are transport from DEV client 200 to QAS client 200, 201 and 202 using stms and specifying which client we want the transport to go to.
After the transports, how can the development team find the logs for these transports.
Right now, we as basis can see the results after each of the transports to each client. IF there is an error then we stop and ask the dev. team to review the logs. However IF the transports go thru without error, HOW can we go back over time to confirm that there were in fact NO errors for transport to each client?
Thanks
Maria

Hello Maria
After you import the transport,in the STMS menu only you can see the option for checking import logs
just click on that and you will be able to see the import logs of a transport.If you drill the logs,you can see everything what the transports has done,what objects have been moved,also if there are any warnings or errors
Rohit

Transports from Dev System to Quality System, Objects copied in Local reque

Hi All,
I am doing transports from Dev Box to Quality Box, while collecting the objects , some required objects got collected in a local request(9xxxxxx) and some got collected in Work bench request(9yyyyyy), Now I want to add , the objects collected in the local request to the work bench request to have a single work bench request i.e 9yyyyyy for transport , with all the objects of the local request 9xxxxxx and already collected objects in work bench request 9yyyyyy,
Please provide the solution for the situation
Thanks in advance
suitable answers will be awarded
Prasad

Hi,
1.First see that your workbench request has a different target system than the ones pointed to by the development class/package of the objects you are trying to assign.
or,
The objects are not assigned to correct development class/package.
2. When we try to create a workbench request, we will see only the request and that is fine.
3.Now, release the local request containing your objects.
4.Include the local transport objects to the new workbench request (Ctrl + F11).
and release and transport the workbench request.
Pls assaign the points if it is useful.
Regards,
Raghavendra Rao.Kolli.

Transporting module pool program from sand dev to dev system

Hi,
Can any body tell me how to transport module pool objects(including screens) from sand dev to dev system rather than manually with in the same client.
regards,
prasad reddy.

Hi
Go to Screen painter and give your program name which you wanted to transport.
Go to --> Object directory entry and there enter Development class and press enter then it will ask for request,. create a request accordingly.
Then you can release the sub task and give the main request to your Basis person to move it to target system.
Regads
Suresh

Transports from PRD to QAS & DEV in SEM?

Hi,
I am in a strange situation. we are on BW 3.0B and SEM 3.1B. For some reasons, My predecessor who worked b4 me implemented SEM planning without DEV system and without transports.
I've been told that they are not developing any thing in DEV system rather they are developing and testing in QAS. once it is done, they make the same changes manually in PRD without transports.
they are doing this only for SEM planning. for BW, they are using DEV-QAS-PRD landscape and even transports.
I'm not even sure what to ask. but, I need to start from here. any suggestions would be highly appreciated.
Now, I need to start using DEV system for SEM planning as well just like for BW. but, PRD is already running.
can we transport PRD objects back to DEV and QAS?
once transported, can i start development in DEV and transport developed objects to QAS and then to PRD?
if we can, what are the precautions we need to take b4 transporting from PRD to QAS & DEV?
Is there a way, to find out the differences between "PRD and QAS" and "PRD and DEV" to make changes manually for small changes?
if nothing is being done, atleast what i can start with to use "landscape DEV->QAS->PRD and transports" by keeping PRD objects alive and running.
DEV is no where close in synchronous with QAS and PRD. there are quite a bit of differences between QAS and PRD but almost synchronous.
I'm in a big need of help.
any kinda ideas are welcome

Hi,
I am in a strange situation. we are on BW 3.0B and SEM 3.1B. For some reasons, My predecessor who worked b4 me implemented SEM planning without DEV system and without transports.
I've been told that they are not developing any thing in DEV system rather they are developing and testing in QAS. once it is done, they make the same changes manually in PRD without transports.
they are doing this only for SEM planning. for BW, they are using DEV-QAS-PRD landscape and even transports.
I'm not even sure what to ask. but, I need to start from here. any suggestions would be highly appreciated.
Now, I need to start using DEV system for SEM planning as well just like for BW. but, PRD is already running.
can we transport PRD objects back to DEV and QAS?
once transported, can i start development in DEV and transport developed objects to QAS and then to PRD?
if we can, what are the precautions we need to take b4 transporting from PRD to QAS & DEV?
Is there a way, to find out the differences between "PRD and QAS" and "PRD and DEV" to make changes manually for small changes?
if nothing is being done, atleast what i can start with to use "landscape DEV->QAS->PRD and transports" by keeping PRD objects alive and running.
DEV is no where close in synchronous with QAS and PRD. there are quite a bit of differences between QAS and PRD but almost synchronous.
I'm in a big need of help.
any kinda ideas are welcome

Transports from BI Dev to BI QA

Similar Messages

Maybe you are looking for