From to Dev to QA

Hello All,
How to go about moving changes from DEV to QA?

hi,
check transport docs and sap help
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/5ee7377a98c17fe10000009b38f842/frameset.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e883de94-0501-0010-7d95-de5ffa503a86
http://help.sap.com/saphelp_nw2004s/helpdata/en/b5/1d733b73a8f706e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/38e1824eb711d182bf0000e829fbfe/frameset.htm
Re: Transport Organizer---
transport query (bex objects)
http://help.sap.com/saphelp_nw2004s/helpdata/en/38/5ee7377a98c17fe10000009b38f842/frameset.htm
hope this helps.

Similar Messages

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.

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

What are the precautions to be taken to move the objects from BI Dev to Pro

What are the precautions to be taken to move the objects from BI Dev to BI Production.
how to move the objects from BI Dev to BI production.
Thanks
sapsdnhelp

Hi,
Please check out this PDF
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50b1d20e-c1e8-2c10-d9b9-d48eb3a83d89?QuickLink=index&overridelayout=true
Hope it helps
Regards,
AL

BI Portal is not displaying Dashboard while Executing from BI Dev System

HI Friends,
I have created Dashboard based on Bex Query using SAP Netweaver Connection and published it to BI Dev System.
it was running good but past 3-4 days it is not working.
When I am executing it from BI Dev its not showing the output in BI portal.
its only show initializing part of dashboard.
please suggest ........
Regards
Sanjeev

has your bex query changed that the dashboard is sourcing its data from? if so, and you have set the connection to "refresh before components load" it will sit at this state until it times out (error handeling is not great). perhaps worth dropping a refresh button in an trying it without refresh on open - this will rule out (or in) a problem with the data connection.
Cheers,
Jeremy

Promoting Universe from BI Dev to BI Prod

Hi Expert,
I have created one universe on Bex query in BI Dev server and I want to export this universe
in my BI Production.
My Bex query is already transported in BI Dev to BI Prod.
While I am promoting my universe from BI Dev to BI Prod through LCM it is promoted in BO Prod but,
connection is still referring the BI Dev it is not change in BI Prod.
Thanks and Regards
Lalit Kumar

Neither LCM nor Import Wizard will change the application server / SAP system that the connection points to.
Log into Universe Designer in your production environment, import the universe, re-point the connection parameters and export the universe to the CMS again.

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

Is it possible to transfer an iOs App from an dev account to another one?

Is it possible to transfer an iOs App from an dev account to another one?

'transfers' have to take place outside of the store between the two parties....app comes out/goes away....moves to new home....goes back into the store as a new app with no connection to before.

How to move offline form from SAP dev to QA and Production environments?

I developed and Adobe Form that can be used offline - steps in development are as below:
1. Webservice generated out of a BAPI in SAP.
2. WSDL generated from SOAMANAGER transaction code and kept on a newtowrk folder
3. Used this WSDL to prepare the form in SAP WebDynpro view
4. generated the URL of the webservice per Dev / QA / Prod when the form is being generated out of the WebDynrpo app - function module ICM_SERVER_INFO (used here)
4. Placed a regular type button on the form and passed the URL on the click of the button
5. This worked fine in Dev system.
6. Now the transports are moved to QA. But click of the button was still pointing to the Dev system.
7. Realized that it is reading the Dev WSDL from the network drive - it still tries to submit to the dev url of the webservice
8. So generated the WSDL from SOAMANAGER fo QA and over wrote with the Dev WSDL files.
9. When I opent he Adobe Form in WebDypro in QA, it reads the new WSDLs and updates the correct URLs - I checked this in the XML of the source of the Adobe Form
10. here comes the problem - even though step 9 is done correctly, I can not save the form and activate it to reflect the new URLs - since QA is not open. Same procedure may need to be followed in case of Production also.
So the question is:
How to circumvent this issue of updating the WSDL and URL after the development transport is moved to QA and Prodcution?
Or - QA and Prod have to opened, WSDL and URl updated in change mode of form and a transport also created?
(seems to be a limitation)
(I looked a bit but did not get any pointers when I googled - may be my search is not correct).
Please advise.
Thanks,

hi Chandra,
I store the url in one of hidden field in form, then copy javascript below to click event, button control type: Regular.
just replace all the "<>" in the code below.
var message;
var response;
// The name of the data connection will be pulled from the WSDLConnection name in the ConnectionSet packet
var sWSDLName = <DataConnection name>;
// clone, modify and execute the connection.
var vConnection = xfa.connectionSet[sWSDLName].clone(true);
vConnection.soapAddress.value = <url>;
// Execute the connection, without remerge data after the result.
var ws_rc = vConnection.execute(true);
for multiple data connection, you have to repeat these code with replace different data connection name and it's url address.
you may use script object (something like subroutine).
Regards,
Kathy Lau

Error when transporting Webservice from our DEV system to QA system

Hello, I created a web service from an rfc by following the wizard from Utilities>More Utilities> Create Web Service. This was created in our 030 client of DEV. I had to create two transports one client independent that was the VI and Service and one Client dependent for the actual webservice. I then transported the webservice to our DEV 200 client and all worked well. Next I transported both to our QA box, first the vi/Service transport then the webservice transport. This is not working, in our QA system, from wsadmin when trying to get the wsdl error is Could not determine wsdl address (ICF ERROR) and from wsconfig when I pull up the service definition and variant the status shows a red stop sign. Is there a trick to transporting this webservice to different systems?
I def award points for helpful answers
Cheers
Devlin

hi,
I had this problem once and in my case the service wasn't activated in SICF.
so see your service tree under /sap/bc/srt/rfc/sap/<your_service> and probably it's inactive (grayed out). right klick and activate it.
anton

How to manage your environments, going from Development (DEV) to Production (PRD) with Management Packs.

I am looking for a way to go from the development (DEV) environment to the production (PRD) environment in a controlled manner.
As I do not want to manually click around with a walk-through screen-shots document = error prone.
As I read these articles
http://technet.microsoft.com/en-us/library/hh519659.aspx
http://blogs.technet.com/b/antoni/archive/2013/10/09/system-center-service-manager-operations-manager-management-pack-and-naming-convention-best-practices.aspx
http://blogs.technet.com/b/wincat/archive/2013/03/28/copying-user-roles-between-management-servers-in-service-manager-2012.aspx
http://www.netiviaconsulting.com/2012/05/10/staying-organized-with-scsm-beware-of-the-management-pack-jungle/
I still have some questions:
1. Can all MPs (un-sealed) be exported from DEV and imported to PRD without breaking things?
2. Are there any known pitfalls?
3. Do you have some tips on this matter? In other words, how do you manage this?
Regards,
Erik

Alex is spot-on. Most MPs are environment/management group independent.
But some MPs contain what I call "Environment Specific Variables". In my experience, ESVs are in:
1) Templates (such as the runbook guids)
2) Criteria blocks (like view criteria, and rule criteria)
3) Parameters (such as write action parameters, and console task parameters)
Alex already gave an example of a template ESV.
An example of a Criteria ESV might be some view that you developed that returns objects that have a specific set of values in your dev environment, but may be different for your prod environment. ie: You have a view whose criteria looks afor a specific business
service ServiceId property. Let's say "Business Service X". But "Business Service X" has a different ServiceId in your dev environment than in your prod environment. So, every time you import your view MP from dev to prod, you have to remember to change your
criteria.
A quick Parameter ESV example; you have a notification subscription (a rule+writeaction). In Dev, you've hardcoded the notification recipient to be yourself. In Prod, the recipient has to be your boss. So, every time you import your MP from Dev to Prod,
you have to remember to change the recipient parameter in the subscription's writeaction.
Like Alex said, handling ESVs by hand is error-prone and time consuming.
Alex, when you write that utility, you should make it more robust. Within an MP, allow a user to pick and configure
any ESV. Store that configuration. Then, just run the MP through the utility and have it automatically set all the configured ESVs to the appropriate environment specific value :) (It's been something I've wanted to write into TFS for
a while, but I never take the time to do it ;) ) If an ESV is missing (because it was removed or changed in such a way that it no longer resembles the configured ESV), throw a warning during conversion.

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 of mitigation controls from GRC Dev to GRC Production in 10.0

Hi All,
Is there an option to transport mitigation controls from Dev to Prod in 10.0. Where is that option available. We could not find even download or upload option unlike 5.3 in 10.0
Thanks and Best Regards,
Srihari.K

Hi
I can see that this question is marked as answered . Could you please update what steps were taken for transporting mitigation controls? Thanks
Best Regards
Srilakshmi S

Transpoting problem from BI DEV to BI QA

Hi ,
(SAP_BW Patch :16 , BI_CONT :8)
We are moving from DEV to QA.i ve transported infoareas,infoobject catalogs and infoobjects.
now im trying to transport master data (that is infosources ,UR and transfer rules.)
im collecting the objects in the following manner.
Ex:0CUSTOMER
Grouping :in data flow before
collection mode : automatic
Here im unable see the transfer rules but UR and infosources are there.(in transport connection screen)
Conversion of logical system namesin Dev i didnt maintain any thing
in QA i ve mainted Conversion of logical system names as
*Original S S Target S S
BI DEV - BI QA
R3 DEV - R/3 QA
I havnt chkd the box 7.0.
Assgnment of source system to source system id
here i clicked on suggest source system ids
i ve AU and AU.
Even i did a trail with transporting the request to QA but no luck it ended with error 4.But not getting Transfer rules in Quality.But I am getting only infosources and update rules only in quality.
Regards,
Gupta

Hi Guptha,
Before ding uch transports first transport the DS from Dev to R/3 then replicate them and then try to transport Transfer rules. I hope it may solve ue rpoblem.
Regards,
Rajkandula

In TMS, can you have routes from a dev to multiple consolidation systems?

My developers want to be able to choose from a list of target systems when creating a transport so that transport would go to a target group, or individual systems.
Currently, I have my my ECC 6.0 Dev system transport routes configured to send to a transport group which adds the transports to two other systems queues. there is a SAP layer and zxxx layer. All custom development classes
use the zxxx layer.
My problem is that sometimes they only want the transport to go to one system or the other, but not both. They would like to choose which system to use in the target system field when creating a transport. Is this possible?
All development classes (packages) use the same
transport layers, either sap or zxxx, I have tried to create routes from DEV to these to 3 different locations, but TMS only lets me use the layer for one route. if I create a SAP route to the /ZXXX/ target group it will not let me also create a SAP route to the individual systems. It appears you can only use a layer to go to one destination.
Is there some way to give them a choice? The developers swear they have seen this before in development systems.
Thanks, Pat

Hello Pat,
The customer i work for has a complex landscape. We have one development system and 6 quality systems.
I have just checked the transport routes in STMS and i see that there are a lot Z layer created for the transport routes to the multiple systems.
Hence i agree with you from an SAP standard point of view all options are closed out. (and believe me i am working on the old R/3 3.1 version)
But what is the problem with transport target group. Just because a request goes and sits in the buffer of a system, it does not mean the request has been imported. right? why cant you convince them on those lines?
But at the same time, i hope your company does not use the standard SAP concept od doing an import all every few hours.
Regards,
Prashant

TOBJ entries missing from upgrade dev and test systems

Hi,
We are in the process of ECC Upgrade from 4.7 to ECC 6.0 and upgraded our dev and test systems. We missing some SAP defined object entries in TOBJ table from dev and test. Because of this some of the roles getting transport errors if the roles contain those missing objects. We tried to transport the missing entries but we don't see any provision for that. Does any one through an idea to move those missing entries from dev to test. Not sure we will get same error in production. This table updates during upgrade and may be we missed some thing in test as though we followed the same upgrade process for both systems.
Thank you
Venkat

Possibly you are no longer licensed for components which these objects are called from in their concepts.
In that case the ability to start the component objects should be removed as well.
Of course if some Z-programs checked these objects or SAP's own "package concept" extended syntax checks did not respect them then you might have problems.
This should normally only apply to manual authorization instances, as if you had upgraded the roles and regenerated them, then you would not have this problem (in the roles).
It tells us something about how you or someone else without any training have built these roles (or subsequently mucked them up...)...
When reading stuff like this, I am always of two minds...
1) SAP should make the concepts simpler and more intuitive to use without "cowboy" activities allowed by users with SAP_ALL etc.
2) Customers should bleed for their own sins for not training people appropriatly (here, faking CV's is also ma major pest!).
It is always a bit of a cat & mouse game and ends up in forums such as SDN in the long run.
Some of it might also have become "available" to be used by SAP (I believe it was the 6.20 upgrade which installed everything...).
Real bugger. I would accept it and test as best you can. You can also compare "where.used-lists" and "code scans" before and after the upgrade to see whether it is used by foreign repository objects.
The scan is more reliable here, as sometimes the object name itself is a variable from a data declaration or condition which you cannot see in the "procedural" code.
Cheers,
Julius

From to Dev to QA

Similar Messages

Maybe you are looking for