Treasury Data Migration

Friends,
One of our client has decided to use SAP Treasury and Risk Management. I have been asked to lead data migration within this area. For the same, I would like to know the generally used and needed master and transaction data for SAP Treasury Management. Also, let me know the various ways of migrating data into SAP TRM eg. BAPI's, Transaction Manager, LSMW etc.  
Regards,
Amey

Hello Amey,
Please find list of steps which might be helpful for data migration.
Legacy Data Transfer
1. Legacy data
transfer always happens on a key date.
2. The procedure is
different for securities and OTC because they deal differently with positions
on a key date.
3. For securities, we
simply need to copy the positions with all values as of the key date.
4. For OTC, the
entire transaction is copied as there is no explicit position management in the
transaction manager.
Customizing the Legacy Data Transfer:
You primarily need
customizing for the update types that the flows of the legacy data transfer
business transactions are to carry. We can find the settings under Treasury and
Risk Management à Transaction Management à General Settings à Tools à Legacy
Data Transfer à Flow Data à Update Types.
The update types are
divided into those for valuation area independent & dependent. The
independent one only relates to securities. à While the legacy data transfer is
usually not intended to update the general ledger, nevertheless you must mark
most of the update types as posting relevant and maintain an account
determination in customizing. This is necessary to ensure that the data in the position
management is complete and in particular the account assignment reference
transfers can be performed correctly.
Legacy Data Transfer for OTC:
Step
1: Existing OTC transactions enter the same way as new transactions.
Enter either manually (or) use existing BAPIs to import them. BAPIs list à Use
BAPI_FTR_FD_CREATE & BAPI_FTR_FXT_CREATE
for creating FD & FOREX transactions respectively. Similarly there are many
BAPIs for each product and we can get the list of BAPIs in BAPI transaction code
under the node Financials à Financial Supply Chain management. Use FTR_BAPI
Transaction to test run the Treasury BAPIs.We may define separate transaction
type for legacy transactions so that settlement (or) posting release is not
necessary.
Step 2: Now we must change status of all the historical flows
created in Step 1 to POSTED without actually generating accounting document. To do this we will use transaction TBB1_LC.
This is similar to transaction TBB1. Unlike TBB1, TBB1_LC affects all the valuation areas without giving an option to affect only operational area. We can see the posted flows by TBB1_LC in posting journal (TPM20) without any reference to accounting documents.
Step 3: Till now the historical flows do not yet explain the book value of OTC transactions. Hence we must first enter the historical valuation results. This is done using TPM63C which you can find under path Treasury and Risk Management à Transaction Management à General.Settings à Tools à Legacy
Data Transfer à Flow Data à Enter Valuation Area Dependant Data for MM.After entering the
valuation results use TPM63 to transfer values to Internal Position Management.
Legacy Data Transfer for Futures & Listed Options:
Step 1: Similar to OTC
Step 2: Similar to OTC
Step 3: Use transaction TPM63D (Valuation area dependant data for futures). We must establish the relationship between lot & the transaction on which it is based via the transaction number.
Legacy Data Transfer for Securities:
For securities position, it does not matter whether is arose in the past through a single purchase (or) a series of business transactions. The legacy data transfer thus seeks to build up the positions through One Business Transaction on the transfer key date.
Step 1: Before we enter business transactions, we must first create the master data of security position i.e. their Position Indicator. I) Use TPM61A (or) menu path Treasury and Risk Management Transaction
Management à General Settings  Tools à Legacy Data Transfer à Position Data Enter Position Information for Securities
II) Now create the position indicator using TPM61.
Step 2: Now we will enter the business transaction.
  I) Valuation area independent data for securities à For External Position
II) Valuation area dependant data for securities à For Internal Position Nevertheless, we need to use transaction set the effects of update type on position to change the positions. If you want to enter LOT Positions with the transactions of legacy data transfer, use the Item Number. Ensure that business transaction generating the position and the one for valuation results carry the same item number.
If you have built up
lots via normal procedures, you must specify the corresponding transaction number
when entering the valuation area dependant business transaction in the
transaction column.
Step 3: Now generate the business transactions using TPM63.We can initially build only valuation area independent data (external position) by checking “only valuation area independent data” button in TPM63. The external position can be checked in securities account cash flow i.e. external securities position in TPM40.
Also we created LSMW for each product.
Regards,
Jain

Similar Messages

  • Fixed Asset Data Migration Wizard

    Hi All,
    I tried to use Fixed Asset Data Migration Wizard to migration my fixed asset data from 8.82 to 9 in the development server.  The server only accessible by myself.
    When I start the migration run, system prompt me " To Continue with the fixed asset data migration, you must be the only user logged on to this company data".
    In fact I'm the only user in the company data and system not allow me to execute the migration.
    What are the causes that system recognise there is another user in the system?
    Please advise.
    Thanks in advance.
    Best Regards,
    Foong Yee

    Hi,
    If you're using SQL Server, try Detach (close existing connections) and re-Attach the database again then re-login and try executing again the wizard.
    Regards,
    Donald

  • Data Migration for Open Purchase Order

    Hi, All,
    Is there anyone know how to Count the volume for Open Purchase Order. What's the normal strategy for the Data Migration and Cut-over stage?
    My client want to know how many Open Purchase Order in the legacy system and then determine manual or automatic data migration. If manual, how to do? If automatic, how to do? Because all materials and vendors, plants are different number. How to track? How to find out to match between new and old?
    Thank you very much

    JC,
    Sounds a bit early to be making decisions about the realization phase.  It doesn't sound like you have finished the Blueprinting phase yet, much less the testing phase.
    Anyhow, in my experience I typically use LSMW (Legacy system migration workbench) to load MM master data (material masters), Inventory (WIP, RM, FG, etc) Purchasing Master data (Vendors, Purchase Info Records, Source Lists, Quota Arrangements), and Purchasing transactional documents (POs, PurReqs, Scheduling Agreements, etc).  Depending on the complexity and volume of data, it  may be necessary to write custom programs to load the data.  You will find this out during your requirements gathering.
    It is uncommon but possible to load all of these data manually.  I have never run across a client that wants to pay a consultant's hourly rate to sit at a terminal to peck away loading master data, so if the client intends to have his own users enter the data manually, the project manager should make provision that there will be qualified TRAINED client employees available for this data entry.  I did help with a portion of a conversion once manually; of Sales Credits, but there were only about 30 SD docs to load.   I did this the evening before go-live day, while I was waiting for some of my LSMW projects to complete in the background.
    A good opportunity to 'practice' your data loads is right after you have completed your development and customization, and you have gotten the approval from the client to proceed from the pilot build to the full test environment.  Once you have moved your workbench and customization into the client's test environment, but before integration testing, you can mass load all, or a substantial portion of your conversion data into the qual system.  You can treat it like a dry run for go-live, and fine tune your processes, as well as your LSMW projects.
    Yes, it is good practice to generate comparisons between legacy and SAP even if the client doesn't ask for it. For Purchase orders on the SAP side, you could use any of the standard SAP Purchasing reports, such as ME2W, ME2M, ME2C, ME2L, ME2N.  If these reports do not meet the requirements of the client, you could write a query to display the loaded data, or have an ABAPer write a custom report.
    You didn't ask, but you should also do comparisons of ALL loaded data - including master data.
    It sounds like you are implying that the client wants YOU to extract the legacy data.  For an SAP consultant, this is not very realistic (unless the legacy system is another SAP system).  Most of us do not understand the workings of the myriad legacy systems.  The client is usually expected to produce one or more legacy system technical experts for you to liase with.  You normally negotiate with the technical expert about every facet of of the data migration.  In addition, you will liase with business users, who will help you and the implementation team to logically validate that the final solution (turnkey SAP production system, fully loaded with data) will meet the client's business needs.
    Finally, you mentioned how do you track the mapping of master data between legacy and SAP.  There are many ways to do this.  I normally try to get the legacy person do the conversion on his end, eg, when he gives you the load file, you would like to have already translated the master data and inserted the SAP relevant values into the file.  If this is not possible, I usually use MS Access databases to maintain a master map, and I perform the mapping on a PC.  If your data package is small, you can probably get by using MS Excel or similar.
    Good Luck,
    DB49

  • Data migration of open production order

    Hello SAP gurus,
    Please advise me about the steps that should be followed for data migration of open production order from legacy to SAP.
    Regards,
    Anand

    Hello SAP gurus,
    Please advise me about the steps that should be followed for data migration of open production order from legacy to SAP.
    Regards,
    Anand

  • Data migration

    Dear all my friends,
    please help to share me about data migration before go-live FI system.
    i plan to migrate GL acct balance, AP/AR open item and last 3 months historical data.
    please help to show me : how should i do ?
    thanks !

    1. Normal GL Accounts: In this case line items are not required and totals are to be updated in SAP. This can be done using GL fast entry if the number is not too high.
    2. Open Item Managed GL Accounts: All the open line items are required to be uploaded in SAP from Legacy in order to clear them. Hence, a LSMW / BDC program has to be developed to upload the line items.
    BAPI_ACC_DOCUMENT_POST - for GL/AP/AR
    BAPI_ACC_INVOICE_RECEIPT_POST - for AP
    BAPI_ACC_GL_POSTING_POST - for GL
    GL Balance
    F-02 or RFBIBL00 or BAPI
    Dr GL a/c Credit Data migration Account or Clearing Account
    3. Customer & Vendor Open Items: All open line items in Customer and Vendor Accounts have to be brought in into SAP. For this also a LSMW / BDC program needs to be developed and upload the line items.
    Vendor Balances
    F-02 or RFBIBL00 or BAPI
    Credit Vendor a/c (individually) and Dr Data migration Account or Clearing Account
    Customer balances
    F-02 or RFBIBL00 or BAPI
    Dr Customers a/c (individually) and Dr Data migration Account or Clearing Account
    4. Asset Accounting: In case asset accounting is implemented the individual balances of each asset (Gross Value and Accumulated Depreciation) have to be uploaded using transaction AS91. For this also you need to develop a LSMW / BDC program. Further, you also need to update the GL Accounts related to Asset Accounts with totals for each asset class T.Code OASV.
    For uploading the Assets
    AS91 -> for uploading assets in AA
    OSAV --> for uploading assets in GL entry Dr Asset (individually) Cr Data migration Account or Clearing Account
    You can use LSMW for uploading all these things
    After uploading all, your data migration account will become zero

  • Confuse on PR & PO data migration approach new to MM module

    Hi All,
    I'm pretty confuse with the PO data migration approach when it comes to PO is GR or partial GR or GR&IR. I'm hoping that someone can enlighten me. i understand that we typically don't migrate PO when it is GR & IR, FI team usually will bring over to the new system as an vendor open item in AP. How about the PR or PO which have gone through or half release strategy? What is the follow up process?  I have created a criteria table below. How Could someone point me in the right direction? Thanks in advance.
    PR
    Criteria
    Data migration required
    Notes
    Open and Released
    Y
    Open and not Released
    Y
    Flag for Deletion
    N
    Flag for Block
    Y
    PO
    Criteria
    Data migration required
    Notes
    Open and Released
    Y
    Open and not Released
    Y
    GR but no IR
    GR & IR
    N
    AP will bring over as open item
    Flag for Deletion
    N
    Flag for Block
    Y
    Partial
    Y
    For partial GR to recreate PO only with missing GR quantity
    Regards,
    John

    Hi John,
    The approach that i have followed recently is that we have considered PO as the base document and converted other documents based on the PO condition. This means you first need to see if the PO is to be converted or not. Then you can proceed to convert the related documents like PR, Agreement, Info record, Source list, etc.
    Also open qty for PO should be considered for Material and Service line items both.
    Once a GR/SES is created, it gets updated in the PO history table EKBE with its related transaction/event type.i.e. EKBE-VGABE = 1 for GR and 9 for SES. Quantity and value also gets updated in case of material and services. You can compare this consumed quantities with PO quantity.
    Please see below from SCN and let me know if you need more info on PR or PO conversion.
    Purchase Requisition Conversion Strategy
    Thanks,
    Akash

  • Data Migration of FI-CA Cleared Items

    Hi,
    Currently I am working on a Data Migration project to migrate data from our FI-CA  module on ERP 4.7 to ECC 6.0.
    THere has been a request from the business to migrate historical data (e.g. Cleared items).
    Is there a SAP recommended approach or tools to load this data into the target environment?
    Currently all documentation around SAP data migrations talks about stategies for open item data migration however I have seen nothing arouund migrating historical financial data.
    Is this because it is not recommended or technically impossible?
    Regards
    Adam Gunn

    That BAPI is used typically for straight out vanilla GL, AR, AP postings, however you still have to create the other side of the entry and then clear it.
    I need to be able to migrate full history, which means from an FI-CA  viewpoint:
    1. Migrate FI-CA posting of liability against BP/contract account.
    2. Migrate associated payments.
    3. And then clearing documents.
    Basically the requirement is to represent the historical data in the new system as if it was posted and matched off.
    Is there a technical way to do this?
    OR,
    Do you migrate the FI-CA liabilties, then the associated payments and then run clearing on the target system?
    I suspect this is almost an impossible data migration requirement as development of the extraction and load process would be extremely complex and testing would take months to cover all posting scenarios in FI-CA. However, I would be interested if anyone has attempted to do this before.
    Adam

  • Data Migration from SAP r/3 to SAP R/3

    Hi all,
    What is the best method to migrate data from one verison of SAP to another verison of SAP ECC say from SAP 3.1 to SAP ECC 6.0?
    This is for all SAP modules including sd, mm, pp, fi, co master and transaction data.  I know there are number of technologies to load the data such as LSMW, IDOC, ALE, DI, etc but what is the best way to extract all data feeds to be loaded back into SAP.
    Thanks in advace.

    Take a look to the following link, may be useful for you
    SAP NetWeaver - Data Migration (CA-DMI) [original link is broken]
    if helpful reward points are appreciated

  • Data migration from legacy system to SAP

    hi all,
      could you please post some docs on migration from legacy system to SAP system., also the problems faced while migration and best practices in data migration
    regards
    sridharan

    Hi ,
    I require few details from you.
    1. What ETL tool you are using, If Informatica, it already have PowerConnect to connect to SAP. So you can create source and Target Structure and also you can use RFC's to send data to R/3. Else, for other ETL tools, can you prepare RFC's or any other way to send data to R/3. let me know the tool.
    2. Does R/3 contains the master data tables? If yes, then try to use LSMW for Mass upload of data to tables.
    If your client don't want to use either of these options please elaborate, what is the case.
    Regards
    Aashish Sinha

  • Data Migration from 11i to R12 Global - Open POs,lines, receipts & on hand upload, Is it possible to do the onhand qty upload with over riding of all receipts which uploaded against Open PO lines?

    Hi Friends,
    We are in a phase of data migration from 11i to R12 
    I was discussed with client & they wants extraction of all open POs which was generated after 01 Jan 2014 to till date in 11i.
    Condition for open POs is PO qty-received qty=>0
    critical Example for open PO is :PO no: 10 has 4 lines, 3lines full qty has been received & for 1 line partial qty(say 50 out of 100) received.
    in this case he wants in R12 uploading as PO no:10 should entered as open PO with all 4lines & 3 lines complete receipt should be done, for 4th line partial qty i.e 50 should be received.
    the question is if we upload on hand qty first, then open POs & receipts, it will increase the onhand qty in new system(mismatch of on hand qty's 11i to R12) 
    Is it possible to do the onhand qty upload with over riding of all receipts which uploaded against Open PO lines.
    Or Please advice best solution.
    Thanks & Regards
    Giri

    adetoye50 wrote:
    Dear Contacts Journal Support Team,
    FYI, this is a user to user support forum.  You are NOT addressing Apple here.
    Honestly, I doubt anyone is really going to take the time to read the novel you have written.

  • Data migration for open PO & PR

    Hi All,
    How to do the data migration for Open PO & Open PR ?
    Thanks
    pabi

    You can BAPI "BAPI_REQUIREMENT_CREATE" for PR creation from data.
    BAPI_PO_CREATE for PO creation.
    Regards
    Sanjay Kohli

  • Questions on data migration....

    Hi all,
    I'm currently facing the problem that my colleagues from the data migration team are about to migrate legacy data to the new system using BDC/LSMW.
    1.) Is it true that the system bypasses any checks concerning number ranges (even if the range doesn't exist at all)? Example: They're about to migrate master inspection characteristics. Let's assume that the old MIC had the number 1234 and the new MIC is supposed to have the number 0001_1234. Do I need to create and assign the external number range?
    2.) If I don't need the number range described under 1.) and I do the migration accordingly (again NO number range created and/or assigned). What would happen if I access this MIC in the future and try to use it in an inspection plan. Would the system reject the usage because there's no number range or would it work normally?
    Any help on this issue is greatly appreciated. Please let me know as well, if I need to post it in a different forum.
    Regards,
    Bobby

    Hi Boban,
    Defining of number ranges before you transfer the masters is must. For numeric titles use SAP std number range for Alphabetic one use external range.
    BR
    Shekhar

  • Data Migration from Legacy System in CRM

    Hi All,
    We are going to Implement a new CRM project, I have a problem with LSMW(Legacy System Migration Workbench ), I have some Conversion Objects of CRM and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
    Objects are like.,
    1. Accounts
    2. Actuate Reports
    3. Active Campaigns/Campaign Content/Dispositions
    4. Contacts
    5. Contracts
    6. Opportunities
    7. Payment Arrangement History
    8. Payments
    9. Premises
    10. Rate Changes
    11. Security Deposits
    12. Business Partner Relationships
    13. Web self-service information
    14. Usage that has been used for quotes
    15. Tax history information, including AXCIS
    17. Service Requests
    18. Service Order History
    19. Security Deposits
    20. Reference Values
    21. Rate Changes
    Can anybody please tell any transaction code in CRM where can I find the Data migration for the above objects is possible or not.
    Thanks in Advance,
    Sai.

    Hello,
    for migration into CRM I would suggest the 'XIF-Interfaces'; these are interfaces provided in CRM for connection to external systems. I'm not sure if this will cover all objects mentioned above, but at least some of them should exist.
    Some information about existing interfaces can be found in the integration repository under http://ifr.sap.com/index.html; from the start screen first select 'Enter the repository' and then have a look under 'generic components' and 'SAP CRM'.
    Regards, Katja Ohliger

  • Data Migration from Legacy System in IS-U

    Hi All,
    We are going to Implement a new IS-U project,  I have a problem with LSMW(Legacy System Migration Workbench ),  I have some Conversion Objects of IS-U and I need to know whether Data Migration is possible or not, please tell me how to find these Objects and how to know Data Migration is possible or not.
    Objects are like.,
    1. Accounts
    2. Actuate Reports
    3. Business Partner Relationships
    4. Active Campaigns/Campaign Content/Dispositions
    5. Connection Object
    6. Contacts
    7. Contracts
    8. Opportunities
    9. Payment Arrangement History
    10. Payments
    11. Premises
    12. Rate Changes
    13. Security Deposits
    these are few and there are some more..,
    Thanks in Advance,
    Sai.

    Hi Ram,
    Use Transaction Code EMIGALL. It will ask for company code. By default Company Code is SAP. If you entered with the SAP you will get all the objects.Then goto menu IS-U Migration-->User Handbook. It will give you details Idea.
    Also Check the following Procedure
    You can find detailed documentation of EMIGALL in SAP itself. Use Transaction EQ81 to display it. It provides all the concepts and procedures to work with EMIGALL.
    Here are some points about EMIGALL :
    1. It Migrates data Business Object wise
    2. It uses Direct Input Technique
    3. It has more than 100 objects of IS-U
    and the steps for implementation goes like this:
    1)You have to create a user specially for migration which will have all the authorizations related to migration workbench, BASIS and IS-U
    2)You have to create your own company in EMIGALL. There is a default company called SAP.
    3)Company SAP contains all the Business Objects
    4)You have to figure out what business objects u need and then u have to copy those business objects to ur company from Standard Company SAP
    5)Each objects contains more than one structure and each structure can contain more than one fields. The relation goes like this
    Object ---> Structure ---> Field
    6)You have to define field rules for each required field of the object. You have to mark "Not required" for fields u don't need
    7)After field rules for a given object is set u have to generate load report i.e. actual Direct Input Program which will migrate data. This program is generated on basis of field rules set by u.
    8)After the load report is generated u have to prepare an input file (import File) for migration. The import file should be according to structure provided by SAP and must be in binary format. SAP Provides the structure of file according to your configurations. You have to write ur own Data conversion program(in any language) for this task.
    9)You take import file as input and migrate the data using generated load program
    10)Finally u can check the Migration Statistics and Error Log
    Thanks and Regards,
    Jyotishankar Dutta
    Message was edited by:
            Jyotishankar Dutta
    Message was edited by:
            Jyotishankar Dutta

  • I had a data migration done from old iMac to new iMac, how do I use that file to find my old email contacts, Safari bookmarks, etc ?

    I recently had a data migration from old iMac to new iMac 11.2
    How do I use that data file to get old email contacts, Safari bookmarks, etc ?

    FireWire cables are dirt cheap and that's how you should be doing the migration. You might have to start over, wiping the new machine's HD, and restoring the software as described in the Everything Mac manual that came with it. See Best Practices and Setup new Mac for more details.

Maybe you are looking for