Transport prod to qa

Hi Gurus,
Can I transport Multiprovider with all included cube and Query to the QA and then DEV syst.How and what steps , things need to consider and careful ??
Please advice in detail.Thanks in advance

HI ram,
Yes you can transport the MP with all the ICs and Query on the top of it if they are not there in QA system
If your underlying DSO's or ICs and queries build on the MP are already transported to QA and Prod system them no need to transport them.
You can simply colelct the MP in the transport request and transport the same to QA n PROD.
Collect only those objects which are not transported to QA n PROD.
Regards
KP

Similar Messages

Problems and question with Transport

Hi,
I have two questions about transporter tool I cannot solve by myself :
-When Transporting from dev system to quality system, data (result of each KPIs) are also transported. How to avoid that ?
- When Transporting in Production, How to avoid to overriding data already entered by users ?
Thanks in advance
Matt

Matt-
SSM Transporter is not like BW in that there is no delta option for data. When using the Transporter you will transport all the Entry & Approval data with your metadata. SSM Transporter cannot transport subsets of data, other than those specified in the Transporter list.
I am not sure what you are trying to accomplish here, but assuming that you want to upgrade 7.5 in dev and then move that to prod, here is a suggested sequence.
Upgrade DEV to the new SP and transport your PROD data into DEV for testing. You also have to move PAS models as well to make sure that the structure of the models are the same. The PAS models are where your data is going to be. The Entry & Approval data is also carried in the SSM metadata as mentioned above. So when transporting PROD data into DEV select the Delete all data in database before import -YES.
Figuring that your testing will take some time, probably additional data will be loaded in PROD during that time. When you've completed your testing, you will have to find a weekend or some period to take your SSM PROD system offline. When you do that you take the PROD system offline and Transport the data again, so you capture all current data and transport that into your upgrade DEV system ( In DEV when transporting Delete all data in database before import - YES). So now your DEV system is the same as your PROD. If you want to make any quick tests to verify, it's recommended. When confident they are the same-
Now, upgrade your PROD system to the new SP and when complete you can transport the data from DEV back in. Check your system and if it checks out put PROD back online. This ensures your data matches the current sets.
This is the very shorthand version, you still have to do all the steps of backing up customizations and all the other things that go along with installing SPs as specified in the guides.
Regards,
Bob

How-to retrieve deleted start routine

Hi!
I have written a start routine in an update rule for a data mart. This update rule was overwritten while the export data source of the related info cube was created again (during this the system automatically creates and activates a new update rule). My start routine within this update rule is lost.
Since this was happening in the development system I found the name (D8FOPYTRYTBF836EXIMLM2MGA) of the routine in the related transport order.
Does anyone know how to show this routine/object/program in an editor or how to rescue the code of the routine? Is there a possibility by any means (SE38 dont work)?
Any help highly appreciated and rewarded.
Best Regards,
Volker

try to search in RSAABAP , RSAROUT and RSUPDROUT tables..
If you don't find.. you can transport that request to quality system(retrive the code and delete this request from transport buffer.. no need to transport prod!) and again create another request with new changes and transport to Q and then to Prod

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

"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

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

Transporting Developmenrts from PI DEV to PI Prod

Hi Experts,
in my PI server, when ever I do a development in the ABAP stack, I release and transport the request to Basis. And In case of developments in Java stack, I use Change Management Service - Transport Studio to move it.
Apart from these processes, what other practices / processes are done in the industry to move developments to Prod..
Regards,
Arnab

Hi,
What is CTS+ and why is is introduced:
The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems in your system landscape.
The XI use case for CTS+ introduces a new transport handling mechanism that offers tighter integration for the transport of ABAP, Java, and Integration Builder objects (Integration Repository and Integration Directory) using the Change and Transport System (BC-CTS) functionality.
As your XI system requires both the ABAP and the Java stack of the SAP NetWeaver Application Server, the following transport tools are available after installation:
u2022
The ABAP transport environment (BC-CTS)
u2022
The file export and import mechanisms or CMS integration to transport Repository or Directory objects in your transport landscape
In addition, you might also have to transport Java development objects by using the SAP NetWeaver Development Infrastructure itself.
The enhancements to CTS in combination with the SAP Solution Manager Change Request Management (ChaRM) address the following issues:
u2022
Synchronized transports for mixed systems (ABAP & Java)
u2022
A unified application for mixed system landscapes
u2022
Tracking of non-ABAP transports including Change Request Management
For your XI landscapes there will be one central transport environment with CTS+ where you can manage all XI-relevant transport objects from a single entry point.
This how-to guide describes the configuration settings you must make in the CTS+ system and XI systems. The functionality must be set up according to the release version of the integrated XI system. The two configurations will be described separately:
u2022
Configuration setup for releases prior to SAP NetWeaver 7.0 SPS12 (also for SAP NetWeaver 2004 SPS14 and higher).
u2022
Configuration setup for release SAP NetWeaver 7.0 SPS12 and higher.
Refer the link for CTS+ step by step method of transport:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/80bbbd55-5004-2a10-f181-8bb096923cb6
http://help.sap.com/saphelp_nw04/helpdata/en/03/dcb6b6048711d3b42a00609419f767/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90d3b550-b6fb-2910-0fa5-ece5d61fb9c3
Regards,
Phani

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

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

Sql query to identify transports in dev but not in prod

I use sqlplus to select fields from saperp.e070v so I can compare transports in prod with those in qa. The purpose is to identify those transports that I need to run when I H-copy prod to QA. I'm using this where clause (TRFUNCTION='K' OR TRFUNCTION='W') . Should I look at TRSTATUS? I'd appreciate any recommendations or ideas. I do not have access to ABAP.

Thanks Markus.
Here are the distinct codes I found. Are there any ot these That I need to be concerned about? Is there a Key/Legend for these?
SQL> select distinct trstatus from saperp.e070v;
T
R
D
O
SQL> select distinct trfunction from saperp.e070v;
T
W
R
P
K
D
Q
M
T
X
F
S
T
G
12 rows selected.
SQL> describe saperp.e070v;
Name                                      Null?    Type
TRKORR                                    NOT NULL VARCHAR2(20)
TRFUNCTION                                NOT NULL VARCHAR2(1)
TRSTATUS                                  NOT NULL VARCHAR2(1)
TARSYSTEM                                 NOT NULL VARCHAR2(10)
AS4USER                                   NOT NULL VARCHAR2(12)
AS4DATE                                   NOT NULL VARCHAR2(8)
AS4TIME                                   NOT NULL VARCHAR2(6)
STRKORR                                   NOT NULL VARCHAR2(20)
LANGU                                     NOT NULL VARCHAR2(1)
AS4TEXT                                   NOT NULL VARCHAR2(60)
CLIENT                                    NOT NULL VARCHAR2(3)
SQL>
F
S
T
G
12 rows selected.
SQL> describe saperp.e070v;
Name                                      Null?    Type
TRKORR                                    NOT NULL VARCHAR2(20)
TRFUNCTION                                NOT NULL VARCHAR2(1)
TRSTATUS                                  NOT NULL VARCHAR2(1)
TARSYSTEM                                 NOT NULL VARCHAR2(10)
AS4USER                                   NOT NULL VARCHAR2(12)
AS4DATE                                   NOT NULL VARCHAR2(8)
AS4TIME                                   NOT NULL VARCHAR2(6)
STRKORR                                   NOT NULL VARCHAR2(20)
LANGU                                     NOT NULL VARCHAR2(1)
AS4TEXT                                   NOT NULL VARCHAR2(60)
CLIENT                                    NOT NULL VARCHAR2(3)
SQL>

How to remove Variable-Values prior to transporting to prod-system?

Hi specialists,
I've got the following problem:
We've got a mixed BEx-client-environment with user using BEx 3.5 as well as BEx 7.x.
So I create workbooks with BEx-Analyzer 3.5 and transport them from the developement-system to the production-system.
The problem: Obviously the variable-selection that I used at last in the developement-system is saved in the workbook. So let's say I tested the query in the dev-system with "DE01" as value for the company_code on the variable screen, then this value is saved in the workbook and transported to the prod-system.
In the production-system the value is not replaced anymore by the users permitted company-code values (the variable is based on the users permissions), but the user has to remove this "DE01" manually and has to enter all his personal company-codes manually - which makes the permission-bases-variable senseless.
Even if I clear all variable-values in the developement system (which is not possible for mandatory variables) prior to saving the workbook, the issue is the same: This time empty fields are presented in the prod-system, but the permission-based-variable isn't set correctly - the field stays empty (=exactly as it was when I saved the workbook in the dev-system).
So, how can I clear the variable-screen-values before I save and transport the workbook to the prod-system? The only way (and it is certainly not the recommended one) i found: If I cancel the query at once after having confirmed the variable-screen and save/transport that query, then the variables seem to be really empty and the permission-based variables in the prod-system work.

So, when user run the report in production, they will have to remove # for mandatory variables and put thier value.
Mh - most of our reports have variables for "company_code","sales_org" (for example).
Normaly this fields are not mandatory but optional.
But: Normaly if the user opens such a variable-screen (for the first time) the company_code and sales_org are preset according to the users permissions for this chars.
If I follow your description, then the variable-screen would open with "#" or "" - but wouldn't be replaced by the user's permitted values anymore :/ - hence the phone rings because the users didn't manage to restrict the variables to their permitted values.
Maybe this is a case for an oss-message for the area BW-BEX-ET-USAB Userability Frontend....

Transporting Objects to QA to Prod

hi,
Its a IDOC to XI to HTTP Receiver.
There are 10 different HTTP Receivers configured using SM59 with external type 'G'with the corresponding certificates installed using STRUST.
Now i think these cannot be transported and i have to install the new certificates for the Production URL's and RFC Destinations of type 'G' again in the Prod.
Is the above assumption right? If not is there any other method to do this?
Thanks in advance,
Tirumal

Hi Tirumal,
thats right. Destinations cant be transported, it would be senseless, because you dont want a a destination between a test and a productive system. You have to configure them manually. If you put the URL directly into the communication channel it is the same result. Transporting that channel you loose the URL.
Regards,
Udo

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

Transporting standard table from DEV to PROD

Hi All,
I have updated a table called T166K and T166P for Purchase Order Printouts.
I have entered few values in the above mentioned tables in DEV server.
Now, i would like to move these tables to Production, since i can not create values to these tables in Production server.
How to move tables from DEV till PROD...??
NOTE: While updating these tables, system didnt prompt for saving under Transport Request Numbers in DEV server.
Regards
Pavan

Hi,
You can use scatt tool to upload the data in the developement server. Prepare a file with data. Do it in developement environment only. then in SCATT you have remote logon facility using which you can run the scatt in developement environment and the result will be placed in the production server.
Let me know if you what more information on this.
Pls reward points if helpful
rgds,
Harikrishna

Transporting SLD objects from DEV to PROD

Hi,
I need to move My SLD objects from DEV to PROD. There is no QA. Also SLD is not common across DEV and PROD.
Thanks!!
Regards,
Miten.

Hi,
How to handle SLD for Tranporting Dev to Quality ser
https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df12869c4753
Transporting XI from DEV to QA
Transporting XI from DEV to QA
using CMS system. in XI
1. /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
2. /people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
3. /people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
4. /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi --> Overview of Transition from Dev to QA in XI
5. /people/sravya.talanki2/blog/2005/12/20/inconsistencies-while-transporting-rfc-objects-from-dev-to-qa-150-sp12
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
http://help.sap.com/saphelp_nw2004s/helpdata/en/93/a3a74046033913e10000000a155106/content.htm --> Transporting XI Objects
http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content .htm --> Configuring Groups and Transport Targets
Look into this blog for how to export / improt IR and ID objects,
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
Please go through these links which actualy show you how to configure CMS and also gives you all information regarding it.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
http://help.sap.com/saphelp_nw04/helpdata/en/de/a4214174abef23e10000000a155106/content.htm
/people/daniel.wirbser/blog/2005/10/27/tcsfilecreateexception--error-while-assembly-of-software-components-in-nwdi
http://help.sap.com/saphelp_nw04/helpdata/en/f6/719a2172f74b67b150612a7cd3b7df/content.htm
http://www.sap-hefte.de/download/dateien/964/074_lesesprobe.pdf
Here are some blogs.
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
Re: Moving project from Dev to QA
Error while exporting/transporting the Business system from Dev to Quality
Transporting the scenario frm Dev Server to PRD Server
transporting data from Dev to quality using CMS
Regards,
Phani
Reward points if Helpful

Transport prod to qa

Similar Messages

Maybe you are looking for