Process to migrate configuration data from one BW development system to other

Hi SAP Gurus,
We need to migrate configuration data from one BW system DE1 to DE2.. Both systems are SAP net weaver 7.3.
DE1 is BW pre-production system and DE2 is BW DEV.
No transactional data required.
Please share a document if available.
Kindly, let me know the procedure for Remote Client copy or client export/import with steps.
Also let me know the pre-requisite for these activities.
Thanks,
Avadhesh Sharma
+91 8095226536

Hi,
Remote Client Copy (SCC9)
Remote client copy is performed in rare situation. When the client copy is done
between two different SAP systems, the copy is called remote client copy.
Before remote client copy is performed, a RFC connection must be set between those
systems using SM59.
1. Check RFC connection is working fine between two systems you want to perform
remote client copy using SM59
2. create client in the target system you want to copy the client
3. login to target client using user SAP* and password PASS
4. execute tcode SCC9 and select the RFC for the source system
5. select the profile you want to copy like SAP_ALL
6. select source client number you want to copy
7. Select source client master data , mostly it is the same client number
8. Now click on schedule as background job.
9. Leave the background server field blank.
10. Click schedule.
11. Select Immediate from next screen.
12. Save the screen.
13. Client copy is scheduled now as a background job and client copy process started.
14. The progress can be monitored using tcode SCC3
Client Export/Import
A client transport consists of two steps:
First a client export extracts client data from the source client
to files at the operating system level. Then the data is imported
from the operating system files into the target client.
To perform a client export, follow these steps:
1. Log on to the source client. From the SAP initial screen,
choose transaction SCC8 (Client Export). Select the data to
be copied using a profile.
2. Indicate the target system to which the client will be copied.
The target system must be defined in TMS as part of the
transport domain.
3. Begin the client export. Because copying is a lengthy
process, use scheduled background processing.
Do not run any other client copy tool before the
data export is finished.
This export process will generate up to three data files at the
operating system level:
• RO< number >: this file contains cross-client data
• RT< number >: this file contains client-specific data
• RX< number >: this file contains SAPscript texts
Depending on the type of data selected through the client
transport profile, the client copy command files added to the
buffer of the target system are as follows:
• <S-SID>KO<number>: this file is for cross-client data
• <S-SID>KT<number>: this file is for client-specific data
• <S-SID>KX<number>: this file is SAPscript texts
The client export change requests are not imported when an
Import all takes place. Therefore, you must import these requests into the target client
using TMS. Choose one of the transport requests of the client transport in the Transport
Management System (TMS). The other transport requests belonging to this client
transport are then automatically added in the correct order.
After the import process has completed, post-import activities are required for object
generation steps. After completing the import, log on to the target client. From the SAP
systems initial screen, choose transaction SCC7
Regards,
Chandu

Similar Messages

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Help with migrating user data from one account to another

I am on a G5 with 10.4.11. I installed FCP studio 6 and everything works fine except compressor. I have had only one user account on this mac (i will call it account 1). I was told to create another account (account 2), log on and see if compressor works. It does. Basically there are files missing on account 1 and compressor won't run. I have installed 3 times and no change.
Anyway I was told to migrate all my user data from account 1 to account 2. I have been looking at threads and want to make sure I am doing the right thing. I found a way to close. Please see if this works. IT may be from the tiger forum:
pick a short user name for your new account. then run the following terminal commands
sudo mkdir /users/newshortname
sudo ditto ~ /users/newshortname
You'll have to enter your admin password (which you won't see) after the first command. that's normal. This will copy your current home directory to /users/newshortname. Then go to system preferences->accounts and create a new account with the short name newshortname. You'll get a popup saying that a home directory by that name already exists and asking if you want to use it. say yes.
Anyway, I would like to migrate everything from account 1 to 2 and have all preferences...everything. I would also like to be able to delete the old account...account 1 and rename account 2. Since this is a home MAC, I really don't need it PW protected. I would like this MAC to just use my new account 2 at start up.
Please ask me any questions. This is my editing MAC, and I can't get around inside the OS. I know FCP like the back of my hand, but don't want to screw up this computer.
Thanks in advance.
Message was edited by: Nelson May

Yeah, you should be able to move most of it by changing permissions.
Network settings could be any/all of these though for instance...
/Users/YourUserName/Library/Preferences/ByHost/com.apple.networkConnect.<12 digit number>.plist
/Users/YourUserName/Library/Preferences/com.apple.internetconnect.plist
/Library/Preferences/SystemConfiguration/preferences.plist
/Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
/Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
/Library/Preferences/com.apple.sharing.firewall.plist
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
/Library/Preferences/com.apple.networkConfig.plist
/Library/Preferences/SystemConfiguration/com.apple.nat.plist
/Library/Preferences/com.apple.print.FaxPrefs.plist
As well as the old Keychain & cookies from your Browser.

How to migrate configurator models from one instance to another in R12

Hi
I want to migrate models from one instance to another using the Migrate models Program .For this do we need to create a Database link between the two configurator instances .Can anybody detail the steps to be followed

Sumit,
I am trying to figure out how to implement copying a quote line from one quote to another. Could you please let me know waht you found out regarding the usage of package. As of now I am only trying it in R11 but I will also need to know how to do it in R12 for future. So could you please tell me how you accomplished it in both releases with probably some sample code.
Thanks in advance,
Vinodh Ramadoss

How to copy data from one table to another (in other database)

Hi. I would like to copy all rows from one table to another (and not use BC4J). Tables can be in various databases. I have already 2 connections and I am able to browse source table using
ResultSet rset = stmt.executeQuery("select ...");
But I would not like to create special insert statement for every row . There will be problems with date formats etc and it will be slow. Can I use retrieved ResultSet somehow ? Maybe with method insertRow, but how, if ResultSet is based on select statement and want to insert into target table? Please point me in the right direction. Thanks.

No tools please, it must be common solution. We suceeded in converting our BC4J aplication to PostgreSQL, the MSSQL will be next. So we want to write simple aplication, which could transfer data from our tables between these 3 servers.

How can I migrate my data from one user to another (to eliminate a previous owner's shortname?)

I purchased a Macbook Pro second hand a couple of years ago and whilst I immediately changed my user name, didn't realise that the previous owner's short name still exists (I was a bit of a Mac virgin at the time!). I now have tonnes of documents, applications, settings, bookmarks, etc. which are assigned against the previous owner.
I've now bought myself an iMac and before I migrate from the older machine to the new iMac, I wish to remove all trace of the previous macbook pro owner.
In researching how to change the shortname user, I've tried virtually everything and everytime have to resort to time machine to restore my settings, desktop, etc. I simply cannot get this to work. Even what seems quite a comprehensive article and procedure didn't work i.e. "full monty" section of the following: http://www.macworld.com/article/1132693/changeshortusername.html
Having failed miserably using different techniques and subsequently having to restore three times from time machine which is costing me hours upon hours, I'm absolutely frustrated at how to do this ... all I want to do is migrate everything to a new user account and delete the old user and previous owner.
Surely someone out there can provide a fool proof, simple and effective method to migrate the user data and keep intact?
Please help if you can!

Pondini wrote:
The only possible downside to this is, the transferred account may lose permission to the files on previous backups.
Actually, there is a way to prevent that, also a bit odd. On the old Mac, go to System Preferences > Accounts and unlock the padlock. Control-click (right-click) the account you want to delete in the sidebar and select Advanced Options. That will bring up a window like this:
DO NOT CHANGE ANYTHING ON THAT WINDOW. Just note the UID number.
When you start up the new Mac, the first account created (during initial setup) is automatically assigned #501. The next is 502, etc. What you want to do is, after creating the first account, Restart and set up one or more temporary accounts in a way that will include that number; then set up an additional one (an Admin account with the identical names as the one you want to trash). Then log on to the additional one, delete the temporary ones and Restart your Mac (to finish clearing the numbers).
Log on and run Migration Assistant as above. That way, you'll get the prompt to rename it as above, but the UID it has will not be a duplicate, so Migration Assistant can transfer it "as is."
Message was edited by: Pondini

Migrating my data from one system to another

Hi All.
We have an application hosted on one SAP system. Now the users plan to use another server to host the application.
All data related to that app (around 10 tables) need to be migrated over too.
Is there any other way than to write a program to download/upload the data to/from a text/excel file?
Anything we can do to avoid writing the programme?
Thanks.

Thanks Krishna. But can you please elaborate on what you are saying?
How to "Add table values" to the TR?
I thought we could only migrate if we had a maintenance view and from there it shall automatically include in the TR if we maintained it via SM30?
But here the case is diff.
It is an application table with no view. Lets say Table Z123. It has 5 fields with MANDT too.
Now around 1000 entries have been filled by the application (program). Now how do I migrate those 1000 entries to another system via TR?
Thanks again!

Migrate all data from one subscription to a new one

Hi,
I'm working with a customer that has been testing apps with the Azure MSDN subscription of one of their employees. They have purchased Azure though credit card and they are willing to migrate all the contents from the MSDN subscription into the new EA Azure
tenant (this includes Virtual MAchines, Databases, web services, among other things). Is there an automatized way to do it?
regards,

hi,
Firstly, I suggest you could refer to Gaurav Mantri's post(http://stackoverflow.com/a/12274767 ). It seems like there are a lot of thing need you do. Also, I suggest you could contact azure support
team to resolve this issue.
Support Channel:
Please connect to Azure support ASAP, it's free, and it's the best choice for you.
Please contact support team by creating a support ticket at http://www.windowsazure.com/en-us/support/contact/
Or if that doesn't work because you don't have an active subscription you will need to contact general customer support to have them create a support ticket for you
http://support.microsoft.com/gp/customer-service-phone-numbers?wa=wsignin1.0
Regards,
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Migration of data from one user profile to a new (to me) Palm

I lost my Tungsten E2. bought a used Tungsten T2 as a replacement. I need to move all my data and programs from my desktop to the new handheld?
How do I do this?
THanks!!!
S
Post relates to: Tungsten T2

You will need to hard reset the E2. Change the hotsync conduits to desktop overwrites handheld. Connect the E2 to the PC and select to sync with an existing username. Select the username that has all your data and complete the sync.
The hard reset will erase all data on the device. Make sure you sync to the PC to backup your data.
Click on the following link to the kb.palm.com webpage for the article regarding reset procedures
http://www.palm.com/cgi-bin/cso_kbURL.cgi?ID=887
The best way to preserve your data is to export the data in each application in Palm Desktop to a seperate folder on your PC.
Create a new folder on your PC somewhere that is convenient. Name it something like Palm Desktop Data. Click on the link below and follow the instructions on that page for the export procedure.
http://www.palm.com/cgi-bin/cso_kbURL.cgi?ID=28734
Make sure you select all for the range in the export window.
With the data saved in the folder you created, make a copy of that folder and save to a flash drive, cd-rw or external hard drive.
Anytime you make a change in Palm Desktop, export the data that was changed to that folder and save again to the external media.
With this process you can always import the data back into Palm Desktop anytime you have a problem with the data in Palm Desktop or if your computer/hard drive/device crashes.
For reference purposes, click on the following link for the support page for your device on the kb.palm.com webpage.
http://kb.palm.com/wps/portal/kb/na/tungsten/e2/unlocked/home/page_en.html
There are links on the page to the user guide, troubleshooting, how to's, downloads, etc.
Message Edited by cygnusX1 on 10-07-2009 09:23 AM

Data migration from one DEV(DE1) system to other DEV(DE2) BW system using client copy or client export import

HI SAP Gurus,
Please find the below details:
SAP NetWeaver 7.3
We have to copy all customized or developed BW objects like master data, DSO's , Infocubes , Reports etc.
We need only the design changes but not the data within the DSO or cubes that exist .
We have tried below procedure:
1) Taken export of DE1 source client 400 with profile SAP_CUST
2) Imported transports generated for above export into DE2 target client 350.
3) Executed transaction SCC3 and performed post processing, post processing was successful . Still we are not able to see DSO's, infocubes ,reports.
Please lets us know what we need to do to fulfill our requirement.
Thanks,
Avadhesh
+ 91 8095226536

Hi Basis,
Please refer to below documentation on how to perform system copy in BI systems
How to System Copy in SAP Business Intelligence System Landscapes (NW2004)
Post processing steps for SAP BW system copy or db copy
BI systems has mostly cross client objects. So client copy with SAP_CUST profile will not serve your purpose.
Hope this helps.
Regards,
Deepak Kori

How to migrate Text data from one application to other

Hi All,
We've a old planning ASO application and users entered text data in data forms (Text cell) and also entered comments for the same cell
Is there any way that we can import the Text data & comments from the old application to new application (few Dimensions are different between the 2 applications)
Thanks,
PVR

Have you looked into using LCM as that can extract the relational data.
Cheers
John
http://john-goodwin.blogspot.com/

Migrating your data from one pc to another?

I recently installed photoshop elemens version 11 on a new laptop. I migrated the photo an film files. However, using the organizer the the files are recognized and shown, as usual. But the albums, created on the prevous laptop, were not recovered.

mtyj wrote:
I recently installed photoshop elemens version 11 on a new laptop. I migrated the photo an film files. However, using the organizer the the files are recognized and shown, as usual. But the albums, created on the prevous laptop, were not recovered.
How did you move (migrate) your files ?
The correct way fot the migration is:
http://helpx.adobe.com/photoshop-elements/kb/backup-restore-move-catalog-photoshop.html

To migrate match rules from one OEDQ's instance to other.

Hello,
We have configured match rules as per the requirement in one instance of OEDQ and now we need to transfer those match rules to the other instace of OEDQ. is there any specific way of transferring those rules to other instance of OEDQ? Kindly please guide.
Thank you.
Regards,
Zankrut.

The simplest way is to package up the project to file and import it into the other system. Best not to package lower level objects such as processes unless you are sure you have not altered dependent objects like reference data or jobs.
Note that if you have >1 server at the same version, Director can connect to multiple servers and drag and drop configuration between them (provided you have appropriate rights).
For production servers, you may want to consider using Autorun to load and run a baselined configuration at startup, and/or the use of the Subversion integration for change control.

Migrating CMSA Assets and Data from one server to another

Hello,
Is there an official way to migrate the data from one CMSA installation to another one? In the near future we're going to need to move from our development machine into the production environment, and it would be great if there was a way to get all the assets we've created in dev over to production without the need to manually re-create them all.
Is this possible?
Cheers,
Kristian

Check out http://help.adobe.com/en_US/LiveCycle/9.5/AssetComposerTechGuide/WS2bacbdf8d487e5824fb272 0612b944351b6-8000.html for this.

Is it possible to migrate data from a 4.6C system to an ECC 6.0 system?

Hello all,
We have an ECC6.0/Oracle 11g system which runs Finance, Purchasing and Payroll/HR for our own organisation.
We also have another 4.6C/Oracle9 system where we run only Payroll for another organisation.
This is a separate landscape (Dev / Test / Prod / DR) which runs on its own hardware.
Clearly, this 4.6C system has to be upgraded in the next 12 months or so before it is out of maintenance.
However, we are exploring whether it would be possible to migrate the data from the 4.6C system to our existing ECC6.0 system instead of upgrading the 4.6C system.
In this way, we can decommission the 4.6C hardware and simplify our landscape.
Has anyone undertaken a similar exercise who would be willing to share their experiences?
Or does anyone have any opinions as to whether this would even be possible?
Our initial thinking is that we would probably have to write our own conversion programs and/or possibly use LSMW but it's early days so any feedback is welcome.
Regards...John

Hi,
However, we are exploring whether it would be possible to migrate the data from the 4.6C system to our existing ECC6.0 system instead of upgrading the 4.6C system.
You can make of ALE/IDOCs technology to transfer the required data from 4.6C system to ECC 6.0 system. Here you will need to perform necessary mapping of the fields and perform required technical configuration. Later write ABAP codes to fetch and transfer data .
Hope this answers your query.
Regards,
Deepak Kori

Process to migrate configuration data from one BW development system to other

Similar Messages

Maybe you are looking for