Transporting Clients Between Systems

Hi,
I wan to copy some client between 2 diferent systems.
There is no connection between them.
I got this link :
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24c824ba111d189750000e8322d00/content.htm
So i need to go in Source System and use Tcode SCC8.
But the Tcode SCC8 ask about target system using RFC and like a said before there is no connection between them.
I just wan to gerate the requests. And them later import in target client coping Data and Cofile from SO.
Please help me.
Thanks.

Hi Ed,
It doesn't have to be Target system to export the client. You can export for any client and import the TR's to target system.
Otherwise, You can define a virtual system in STMS and You can perform client export and import thru scc8. Move the co-files and data files to target server to import the client.
Please refer to below link
http://help.sap.com/saphelp_smehp1/helpdata/en/44/b4a0db7acc11d1899e0000e829fbbd/content.htm (Create Virtual System)
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24c824ba111d189750000e8322d00/content.htm
Thanks,
Sravanthi

Similar Messages

Copy clients between systems

I already copy clients from one Sap system to another, both systems was with same release, components, add-ons.
Now the TST system is upgraded to oracle 10 but the PRD system is still on oracle 9, we need to have some time for testing.
Is it possible to copy clients between these 2 systems with different oracle version?
Please advise.
Cheers.

Hi,
yes you can .
also check Note 557132 - CC-TOPIC: Remote client copy
regards,
kaushal

STMS - Transport Routes - Multiple Clients and Systems

Hi Guys
We are setting up a ERP Landscape based in four systems
AED - Gold Development (Most Development starts from here)
AEC - Customer Development (101,102,103...)
AEQ - Customer QA (401,402,403,...)
AEP - QA Production (701,702,703,...)
Our main goal is to release transports from AED 100 to all clients in AEC (101,102,103...)
CTC was already set up to 1, and all system share a same Trans Dir
For this purpose I have created a transport Group /SOD_DEV/ and added AEC 101, 102 and new clients would be added
Only customizing request should be replicated on each client, and workbench only for one client.
Then, I need also all the transports from AEC go their respective client transport queue in AEQ and AEP
Example:
AEC 101 --> AEQ 401 --> AEP 701
AEC 102 --> AEQ 402 --> AEP 702
And in the future it should be able to expand to
AEC 103 --> AEQ 403 --> AEP 703 and go on.
My questions are:
Should I create a Transport Group for Customizing and Transport Layer for Workbench? O can I use a single Tranport Layer for both Workbench/Customizing?
How can i create a route from AEC so transports who got imported in 101 are automatically delivered to 401 and then 701?
Thanks
Martin

Hi Yuksel, thanks for your input.
We agree with a tranport Group between AED and AEC. Transport layer is ZAED.
All developments made in AED, are distributed to Transport Group /SOD/ to all AEC clients (100,101,102...)
Now comes the tricky part
for example, all requests that were imported in AEC 101 should be delivered to AEQ 401 and then delivered to AEP 701 only
That why I didn't put a transport group between AEC and AEQ, since it should be a dependency.
Any transport that was imported on AEC should follow their respective route
Workbench: AEC 100 --> AEQ 400 --> AEP 700 (Sytem-Wide Workbench requests)
Client 1: AEC 101 --> AEQ 401 --> AEP 701 (Client-Dependent Customizing)
Client 2 :AEC 102 --> AEQ 402 --> AEP 702 (Client-Dependent Customizing)
And it wiil follow with
Client 3 AEC 103 --> AEQ 403 --> AEP 703 (Client-Dependent Customizing)
It created these delivery routes; as example for Client1: AED101-AEQ401 and AEQ401-AEP701. Is that correct?
See attached the screenshot for better reference, you are welcome to further suggestions
Best
Martin

Can i do client export import between systems with different patch levels

we want to do a client export import between two systems. As I understand the patch levels should be the same in both for this to happen..
But right now I am in a situation where time is a big constrant. The basis patch level is on par. But the rest are not. Can I do client import successfully at this stage.

The only thing that may stop it working could be additional functionality between the systems.
I work on XI and there is a huge difference between SP12 and SP15. We were able to do the transports between systems, but as Dev was patched before QA, and the transport was reliant on standard settings not being available, it still went though, but we had to transport it again after applying SP15 to QA.
Again, it probably depends on what System you have running on Netweaver...

Transports between systems after support package application

Hi gurus, we need to apply a lot of support packages into the development system and I wanna know if in the meantime we need to "freeze" all transports between systems.
This because the systems (DEV - QA - PRD) are in differente support package level. This until we apply the support packages into the others systems
Thanks in advance.
Ronald.

Yes, any transport which is taking SAP standard code from DEV to QA to PRD should not move if the systems in landscape are on different support pack level. Because it can happen that SAP has done some modification to that standard code in new support pack.
However, anything which is isolated Z-development (like some z-output report or smartforms) can proceed.
But, I suggest , stop moving transports until all systems have same support pack level.
G@urav.

Difference between system copy and Remote Client copy?

Hi,
Can any body suggest me , What are the major difference between System copy and Remote Client Copy.
As per my knowledge , Both are different
1.In system copy entire data recovered mean copy from Source to target
2.In Remote client copy All Client data can't me import if you choose SAP_ALL profile also
I hope Transaction data and user data can't copied
Anybody share this Question and Give me some idea about this
If anybody give brief explanation that is very gratefull.
regards,
Balaram

Hi,
System copy will replicate all database from source to target system.
In remote copy only client in which you are performing the copy will get refresh. Also, remote client copy will be done between systems on same patch level. with SAP_ALL profile you can bring all data in target system including your transactional data.
Thanks
Sunny

Difference between system refresh and client refresh

Hi all,
I have one dout what is the difference between system refresh and client refresh,kindly tell me the answer?
BR
krishnamurthy.

Hi,
Client is part of a system.
Client copy :Can happen within a single system(local client copy) or to other system (i.e b/w systems) .
Here we have some profiles to extract the data depending on the need.
System Copy: We are copying the entire system to other system.we get the entire systems data (DB) .
In both the cases we have to make sure that they are on same application component and are on same patch level.
Thanks!!
Edited by: Vani n on Jun 27, 2008 2:45 PM

Transport of ABAP Unit Test Classes between systems.

Hi guys
I have a bit of a dilemma on hands here pertaining to the transport of ABAP Unit test classes. Generally when you create a transport containing classes the transport manager will automatically include all "programs" related to the class like the local type definitions, local implementations and with ABAP Unit the local test classes.
The question that I have is how would one go about excluding the ABAP Unit test classes in transports to production systems and pre-WAS 6.40 systems that do not support ABAP Unit? Does the transport system automatically manage this for you? Any help ideas regarding this would be greatly appreciated.
Kind regards
Ettienne Hugo

Hello Ettienne
I have a very similar problem that I have to maintain objects for release 6.20 and 6.40. Since I appreciate ABAP Unit Tests as being very helpful I do not want to miss them even in such a situation.
My approach is as following:
- If possible, I try to separate the local classes from the tested object, for example:
- Report or function group
- contains an include like <z_include_ft01>
- Within <z_include_ft01> I have a single stament <z_include_au01>
The actual ABAP Unit Tests are coded in <z_include_au01>. Now if I need to ship the development to a release < 6.40 the only thing I need to do is to comment the single INCLUDE statement in <z_include_ft01>. This manual step cannot be ommitted (however, it would be simple task to define an eCATT doing this). In addition, include <z_include_au01> should not be in the transport request for the development (if it happened the import error would not affect the function of the development because it is no longer linked together).
Advantage of this approach:
- I clearly see that my development contains ABAP Unit Tests (use naming conventions for the includes) and
- I can ship - with little effort - the development to SAP releases not supporting ABAP Unit Testing yet
Regards
Uwe

Probelms while replicating Data Source and transport into test system

I find the following error messages whilre transporting into test system.
DataSource 0EC_PCA_1 does not exist in source system of version A.
Mapping between data source 0EC_PCA_1 and source system is inconsistent.
DataSource 0EC_PCA_1 does not exist in source system of version A.
Field AFABE will not be delivered from DataSource 0EC_PCA_1 in source system.
any ideas please..........
Enhanced the Extract structure and activated the data source in Source system
Replicate the Data source in BI and install the Infosource through BI Content activated and transport them to Test system.

Hi,
1.First transport the data source from R/3 dev to R/3 quality
2.Replicate the data source in BI Quality ( make sure you that in the data source tab, you are searching the data source below the appropriate source system ---otherwise you data source may not appear)
3.goto rsd1in BI development for activataing the info objects which you have added extra in the info source (z info objects )
activate these info objects and collect in another request
4.transport these info objects from BI dev to BI quality
5.transport entire data source to bw quality.
Thanks,
Tarun Brijwani.
Edited by: Tarun Brijwani on Apr 6, 2009 4:26 PM
Edited by: Tarun Brijwani on Apr 6, 2009 4:26 PM

Stock Transport Order between Two Company codes

Dear All
Scenario-- Stock transport order Between two company codes.
The valuation of Comapny Codes is at Moving Average Price.
I have a scenario
MAP of Issuing Plant-- Rs. 10 / kg
I am able to pick up the price of Rs.10 (MAP) of issuing plant while creating PO.
in receving plant.
At the time of Goods issu the MAP has changed & become Rs.12/kg. Hence the goods issue takes place at Rs.12/- perkg.
When we make GR at receiving plant ,the valuation of GR is at Rs.10 i.e at PO price.
Is it possible to have a GR valuation at Goods issue price for that delivery note?
Request Your feedback urgently.

The invoice has the material costs at time of goods issue.
You receipt is valuated to PO price. But when you post the invoice, then the MAP is adjusted,
By setting up EDI, SAP will probably post the invoice before the goods receipt is done, hence the GR should be valuated with the invoice price.
from Note 518368 - FAQ: Valuation for the purchase order;
With which price is the goods receipt posted for a purchase order?
Answer:
If the goods receipt is executed before the invoice receipt, the goods movement is valuated with the purchase order price. If an invoice is already posted, the system uses the price of the invoice. If a partial invoice is received, the partial quantity corresponding to the invoice is valuated with the invoice price, the rest is valuated with the purchase order price.
For more detailed information, refer to both the documentation of the material valuation and Note 380883.
see as well Note 547570 - FAQ: VPRS in pricing

Stock transport order between storage locations and assignment category type E not in MRP

Hello Gurus,
I have a stock transport order between 2 storage location which belongs to the same plant. Besides the stock transport order is allocated to a sales order (account assigment category E). When I run the MD03, the system take into account the quantity of the stock transport order as a future entry and this is wrong. I need that the MRP has not into account the stock transport order as an entry.
As an important information, If I modify the stock transport order removing the account asignment category E (sales order), then the MRP doesn't take into account it, so this is correct.
Could anybody tell me how to get it?
Thanks in advanced.

Laura,
It is normal that MRP will consider an STO as a receipt element; this is basic planning. It is unclear to me why you think you do not want it to do so, but I will assume you have some logical reason.
Contrary to what some others may have suggested, changing the scope of check for availability checking has no effect on which elements are considered for MRP. MRP is a completely separate functionality from Availability Check.
For Location > Location STOs (within a plant), then, you normally have the receipt element of the STO in the destination storage location, and the requirements element of an equal amount in the source storage location. Net of these two elements is zero, unless you have already issued the STO at the source location.
Changing the Account assignment from "E" means that the STO will not be relevant for your Sales order (in other words, when you receive this STO into the destination storage location, it cannot be used for your sales order). In a general MTO scenario, it also means that the proceeds of this STO (the stock you received) cannot be used for ANY sales orders.
One way that some people make an STO 'not relevant' for MRP is to alter the destination storage location such that it is not relevant for MRP. You can change the MRP relevancy of the storage location in MM02 > MRP4 tab
Best Regards,
DB49

Transport Error: Source system does not exist. Message no. RSAR203

Hi,
after transporting from BI_DEVELOP to BI_TEST I get an error whil importing Datasources:
Source system ERP_DEVELOP_SOURCESYSTEM does not exist - Message no. RSAR203
Which is upon the first sight correct, because I got the followings systems, RFC's and BI Sourcesystem:
ERP_DEVELOP -> BI_DEVELOP with RFC & Sourcesystem ERP_DEVELOP_SOURCESYSTEM pointing to ERP_DEVELOP
ERP_TEST -> BI_TEST with RFC & Sourcesystem ERP_TEST_SOURCESYSETM pointing to ERP_TEST
Can I map in the transport ( and how) in a way that the transports do not fail ?
ERP_DEVELOP_SOURCESYSTEM to ERP_TEST_SOURCESYSETM
or
Do I need to setup in BI_TEST a Sourcesystem ERP_DEVELOP_SOURCESYSTEM pointing to ERP_TEST ?
Thank You
Martin
Edited by: Martin Sautter on Jul 25, 2011 12:59 PM

Hi Martin,
You have to maintain the transport connection between your ERP_DEVELOP and ERP_TEST
your transport path should be as below
BI_DEVELOP -
> BI_TEST
ERP_DEVELOP -
> ERP_TEST
1)Make sure you have FRC connection between BI_DEVELOP and ERP_DEVELOP, BI_TEST and ERP_TEST
2)check you have transport connection between BI_DEVELOP and BI_TEST,ERP_DEVELOP and ERP_TEST
Now you transports should not fail
Hope this helps
Regards,
Venkatesh

Problem in transporting Variants - "You cant transport client-specific obj"

Hi,
I am facing a problem while trying to transport variant from DEV to QAS.
When I tried to transport one of the variants (of a program) from DEV to QAS (quality system), it gave me an error that: "You cannot transport client-specific objects".
Pleasehelp.
Thanks,
Vishal.

Hi,
The program is Not a local object. I am trying to assign the variant to a transport via. SE38->variant->display->utilities->transport request-> request number.
Is there a way to modify this variant from client specific to "non-client-specific".
Also, please let me know hoe do we copy this variant into a new variant which is not client specific (i.e. a global variant).
Thanks,
Vishal.

Transport Request Between Server

Dear All,
I did request from One client to Other client in Same Server. Its working fine.
But I don't know, How to transport Request between One server ( QTY ) to Another Server ( DEV ).
Let me know.
Edited by: thomas_raja on May 30, 2011 4:08 PM

DEV --> QAS is a straight way which will be done by your BASIS team.
If you have different requirement than this, also contact them.
Regards,
Nick Loy

GL Account/Product category mapping not working in transported client

We have implemented SRM 5 and an Ecc 6.0 backend.
We have transported the GL Account /Product category mapping config from the DEV client to the Quality client. In the quality client we run BDLS to set the correct backend system for the GL account/product category mapping.
When we create a shopping cart, GL accounts are not determined. We have noticed that in table BBP_DET_ACCOUNT, the backend system is still pointing to the DEV client backend system not the quality client backend system. Why is this?
Do we have to always manually reset this config in every client that we transport this table if we have new or changed entries?

Hi,
See this related threads:
Re: Client Copy SRM from prod to dev -Urgent
product category creation and g/l account assignment updation
BR,
Disha.
Pls reward points for useful answers.

Transporting Clients Between Systems

Similar Messages

Maybe you are looking for