Transfer GL Accounts to a new SAP System

I need to transfer G/L accounts to a new SAP system.
I am trying to use Data Transfer Workbench. I need to know do we create it in the Company Code from where I have to move the GL master data or in the target system.
One more question, after Extract GL Master Data file is generated-the next step is to create the spreadsheet file. I am not able to find where we do it.
All help is appreciated.

I am using the tcode SXDA. The next step as explained in the SAP R/3 documentation is Processing a file with spreadsheets. It done as follows:
Import the file using a spreadsheet program and set the columns to the data format Text.
Edit the file using the spreadsheet. You can enter your data manually or copy it from another spreadsheet file.
When you have finished editing the file, save it with the extension "txt".
But I am not able to figure out how to do that. If anyone knows, please explain little bit in more detail like how can I import the file using a spreadsheet program.

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 you’ll 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 don’t 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

  • How do I transfer my account To my new ipad?

    I have a new Mini/Retina that I want to replace my iPad 2 with.  I want to use my same old AT&T account for cellular/data connection, so how do I transfer my account To my new iPad?
    The guy at the AT&T store (where I bought the Mini) said I would have to start it as a backup from the old machine, and I might have to switch SIM cards (believable), but there must be more to it than that.  At what point shoud I shut off the old iPad account?  If I do it at the wrong time it seems like there should be a conflict (perhaps the SIM card).  Is there a procedure posted anywhere?  (He also gave me a 1-800 number to call for help - so I suspect I'll need it.  But you guys are so good, I'll start here.)
    TIA

    If your iPad 2 has a newer iOS version than your new iPad Air then you'll need to update the iPad Air to newest iOS before you can restore it from the iPad 2's backup. Its conceivable that being in the store the new iPad air does not have the most recent iOS installed.
    Anyway as to the AT&T service. you should not have to anything on the old iPad.
    Simply remove the sim card, go to your AT&T store and ask for a new sim that fits your new iPad with your current service on it. Then simply insert the new sim card into the new iPad.  In the process of setting up the new sim card, the old one will be deactivated by AT&T.
    Without a sim card the old iPad will have no cell service.

  • Transfer data from dot net to sap system

    Hi gurus!
    please , help me out , i wanna transfer data from dot net to sap system. i have no idea abt it.
    Points can be given sure!!!!!!
    Rahul Deshmukh

    Hi,
    You need to create a RFC(Remote Function Call) to achieve this.
    Goto Transaction SE37
    Import Parameters(What all data you are going to pass from JAVA to SAP)
    EXPORT parameters(What all data you want to pass from SAP to JAVA)
    TABLES parameters (What all tables you want to pass from JAVA to SAP)
    Goto Attributes tab & select Remote Enabled.
    Do the coding to insert records in ZTABLE.
    Activate the RFC
    Now, in JAVA code to login to sap & call the RFC with the required data.
    Best regards,
    Prashant

  • GuiXT:  Recently we have added new SAP system EIQ

    Hi,
    Our client is using GuiXT since long time. Recently my firm started
    taking care of GuiXT operations. Recently we have added new SAP system EIQ. GuiXT is not working on the new system. It is working fine with other existing SAP system EIT and EIK. Please let me know what all GuiXT related settings need to be done on the new server.
    Thanks in Advance
    Regards
    Gaurav Raghuvanshi
    Message was edited by: Matthew Billingham - Please read the Terms and Conditions re: "urgent"

    Hi Gaurav,
    You need an additional key for the new system, which Synactive will provide as part of your client contract. Once you have the new key configured in the guixt ini file, everything should work as desired.
    Good luck.
    Best,
    Vishal

  • My iPad was stolen and I want to know how I can deactivate it and how do I transfer my account to my new iPad

    Hi there  My i Pad was stolen and I would like to know how do I deactivate it and how do I transfer my account to my new i Pad Thanks Linda

    If you enabled the "Find My iDevice" feature prior to the device being lost/stolen, log into iCloud and deactivate it. If you did not, there is nothing that can be done.
    As for the content, it should all be on your computer, simply connect the new iPad and sync what you would like to the device.

  • I have a new computer how do I transfer iTunes account to the new computer?

    How do you transfer an iTunes account to a new computer?

    Go to the iTunes Store and select "Purchased" from the Quick Links side bar on the right. Go through all the tabs to download again for free

  • My old computer is dying and I want to transfer my account to my new computer.  I will not be using the old computer at all.  What is the best way do do this?

    I want to stop using my old computer completely and transfer my itunes account to my new computer.  What is the best way to do this?

    A simple search

  • New SAP system menu option

    Just a quick question, if you add a new function code to the Standard SAP System Menu options via program MENUSYST / status MEN where do you add the abap code for this functionality?
    Regards
    Mart

    The necessary java code to achieve this needs to be put in the file: includes/bodyStart.jsp above the line that creates the navigation bar:
    <% String navBar = p.getMainNavigation();
    For example, let's say we want to add a new tab that gives us a shortcut to the debug/session pages, and a sub-tab below it that lists all configuration objects in the repository. Here's the code for it:
    // Add a tab..
    com.waveset.ui.PageNavigation DEBUG_PAGE = new com.waveset.ui.PageNavigation("Debug", "debug/session.jsp", 0);
    DEBUG_PAGE.setRequiredPerms(new com.waveset.object.Permission[] { new com.waveset.object.Permission(com.waveset.object.Type.SYSTEM, com.waveset.object.Right.VIEW, true) });
    p.addPage(DEBUG_PAGE);
    // Add a sub-tab..
    String urlDebugListConfiguration = "debug/List_Objects.jsp?List_Objects_Type=Configuration";
    if (! DEBUG_PAGE.containsSubPage(urlDebugListConfiguration) ) {
    com.waveset.ui.PageNavigation DEBUG_LIST_CONF_PAGE = new com.waveset.ui.PageNavigation("List Configuration", urlDebugListConfiguration, 0);
    DEBUG_LIST_CONF_PAGE.setRequiredPerms(new com.waveset.object.Permission[] { new com.waveset.object.Permission(com.waveset.object.Type.CONFIGURATION, com.waveset.object.Right.VIEW, true)});
    DEBUG_PAGE.addSubPage(DEBUG_LIST_CONF_PAGE);
    As seen above, appropriate rights can be coded to limit the visibility of these tabs to administrators with certain capabilities. For a complete list of rights, refer to the IDM documentation and the java-docs for com.waveset.object.Type and com.waveset.object.Right.

  • "I have New SAP System"

    Hell All,
    I had a fresh Sap System How to configure all the connections.
    Regards,
    ch.

    Hi ch:
    Take a look at the SAP notes below.
    Note 184971 - "Notes on BW source system connections"
    Note 1478123 - "FAQ: Source system"
    Note 184447 - "Building a BW-system landscape"
    Regarrds,
    Francisco Milán.

  • Purchase Order Data transfer from one old sap system to new sap system

    hi all,
    Suppose i have created some purchase orders in one client( old sytem) that are accurate according to our need .
    Now instead of creating same purchase orders again in in new system is a useless task.
    SO i want to upload these purchase order directly from SAP old system to
    SAP new system.
    How to execute this task.
    CAN anybody help me out with simple example  plz..
    thnx & rgds

    using ALE & IDOCS you can trasfer data from one system to another

  • How do I transfer iTunes account to a new computer?

    How do I transfer my ITunes accout to a new computer?

    Do you mean transfer your iTunes library to a new computer?
    Copy the entire /music/iTunes/ folder from old computer to /Music/ on new computer.
    Your iTunes account is used to make purchases from the iTunes store.

  • Material master upload to new SAP system

    Hi,
    Please help me to decide the procedure on migrating material master from ECC 5.0 to ECC 6.0.
    One of my idea is to use LSMW and other is to use ALE.
    I am expecting many changes in the current material master, so using standard ALE BD10 is difficult. Example: ECC5.0 material type "ABC" would be "XYZ". (XYZ and ABC are of same material type, example: FERT). I choose to have different material number in new system. Like that there are few more changes.
    What are all the best methods to extract the data from ECC5.0? I was checking the program RMDATGEN to download the data, but it is not readable. I can prepare a file format and map the columns in ECC6.0 LSMW. Since both the systems are SAP, I am thinking why to prepare a seperate input file format? Again I need to download the data from ECC5.0 for that format. Is there a simple to download and upload the data? Please let me know.
    Thanks
    Nagarajan

    Here you define your Partner profile:
    IMG > Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Partner Profiles and Time of Processing > Maintain Partner Profile Manually
    And in the details you define for yor message type MATMAS:
    Receiver port: X
    Output mode: Collect Idocs and Do not start subsystem
    This collection writes the idocs to a file.
    This file can then be found in SAP file system with transaction AL11.
    a clever basis guy can then move it from there to your network.

  • Bought new computer. How do I transfer my account to my new computer?

    I have an older lap top that has my itunes account and playlist. How can I transfer it to the new lap top I just bought? I have Windows 7

    Install itunes on the new laptop, first.
    You can log into the itunes store and start using your account at any time - there isn't really any "transfer" going on, for that part.
    You do need to transfer the music files and the itunes database, though. Do that the same way you are transferring over other stuff like digital photos, browser bookmarks, etc. I've used my home network in the past when we've gotten a new PC.
    For itunes, the important folder is C:\....\iTunes. Just replace that folder on the new machine with the iTunes folder (and all its subfolders) from the old machine.
    Have a look at the new PC's preferences to make sure they're set up correctly, and don't forget to deauthorize your old PC if you're getting rid of it. And....don't get rid of it until you are sure you have everything set up like you want!

  • How can I transfer my account to a new PC?

    I moved recently, and my account is currently on my parents' computer. I would like to know how I can get my account onto my boyfriends' computer. Help is greatly appreciated!

    If you copy the entire iTunes folder to the new computer (with iTunes not running) you don't need to readd anything. The content will be there when you launch iTunes on the new computer.

Maybe you are looking for