Data migration - procedure

I have three tables and want to create another table that includes the structure of all the three tables and later drop the three tables.
How to acheive the data migration by writing a procedure.
Thanks in advance
Raghu

That is indeed the better option. If you insist on writing a procedure, a few selects from the DBA_TABLES, an array and some dynamic SQL should do the trick. After that you can transfer the data, and drop the tables.

Similar Messages

Data migration procedure for upgrade

Hi,
I am working in upgrading 3.0B to BI7.0. The BI7.0 Production is already stabilized and already in use.
My query is, to the existing BI7, I need to push data from 3.0B.
Please clarify.
Thanks in advance,
Rama Murthy..

Export data from 3.0B to flat file (through open hub) and then load it to BI 7.0.
Basically upgrade supposed to be system copy of 3.0B to new box (BI 7.0 box and then upgrade) .
Hope this helps..

Data Migration of Excise Duty payables at initial upload

Hi!
Can any one tell me, how to upload initial Excise Duty payable in data migration procedure.
for example if different excise duty payables like ED, CESS, SEC.CESS for normal goods and capital goods.
thanks in advances.
regs,
ramesh b

Hi Ramesh,
From my exposure with indian company codes these are just another GL account to be migrated since there are
no dependies you can do the mapping from legacy to the new sap system the GL account.
Just my view
regards
pbb

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

Data migration from hard drive, as opposed to over firewire in target mode

i'm selling my macbook and getting a new imac. in an attempt to be fiscally responsible, i will be buying the imac after i have the cash in had for the macbook. i will do a carbon copy clone tonight, but when i get the new imac, how painful will the data migration be from the external hard drive to the new imac?

beerbrewerbrian wrote:
i'm selling my macbook and getting a new imac. in an attempt to be fiscally responsible, i will be buying the imac after i have the cash in had for the macbook. i will do a carbon copy clone tonight, but when i get the new imac, how painful will the data migration be from the external hard drive to the new imac?
A new iMac includes the migration assistant utility. Plug your external drive into your new iMac. Start up the iMac for the first time. The iMac first time procedure ask if you want to migrate your data. Say yes.
You can run migration assistant later. It's in:
Macintosh-HD -> Applications -> Utilities -> Migration Assistant
Robert

SAP Legacy data Migration Starategy/Process

Hi Friends
I would request you, if anybody let me knwo the process of legacy data migration into sap. What are steps I have to follow while doing legacy data migration. My questions are:
1) How to upload GL balances from legacy to SAP
2) How to upload Vendor and Customer open items into sap
3) Asset balances How to upload
4) what is the use of Migration clearing accounts.
Kindly provide if any documents for legacy data migration into sap.
Thanks in advance
Rao

Dear Rao,
Just check the bwlow link you can understand easly to upload the balances.
http://www.saptechies.com/sap-pdf-books-download/SAP_Go_live_strategy11248141773.pdf
Check the bwlow procedure for the same way do it.
First create 5 Dummy GL codes. These GL code should be zero at the end of uploading balances.
1     GL Offset Account               Dr
          Asset Offset Account          Cr
          AP Offset Account          Cr
          Sales          Cr
          Other GL's          Cr
2     Cash               Dr
     Consumption               Dr
     Asset Offset Account               Dr
     AR Offset Account               Dr
     Material Offset Account               Dr
     Other GL's               Dr
          GL Offset Account     x     Cr
3     AP Offset Account               Dr
          Vendor 1          Cr
          Vendor 2          Cr
          Vendor 3          Cr
4     Customer 1               Dr
     Customer 2               Dr
     Customer 3               Dr
          AR Offset Account          Cr
5     Fixed Asset 1               Dr
     Fixed Asset 2               Dr
          Asset Offset Account          Cr
          Acc. Depreciation Account          Cr
6     Stock Inventory Account               Dr
          Material Offset Account          Cr
Regards,

Module for data migration from pdf(zip) to pdf(unzip)

Hi all,
I am Working on Data migration using SAP XI with out using IR.
I want to Zip the pdf file in the Sender CC and unzip the same in Receiver CC.
I am using PAYLOADZIPBEAN to zip the pdf.
Did any one work on zipping and unzipping the PDF files?
Kindly let me know the Module I need to use for the same.
Thanks,
Sree

Hi Sree,
Please go through this blog and follow the step by step procedure for configuring your scenario.
/people/stefan.grube/blog/2007/02/20/working-with-the-payloadzipbean-module-of-the-xi-adapter-framework
Its a nice blog and i have configured my scenario using the same already.
Thanks and Regards,
Sanjeev.

Data Migration techniques

Hi Experts,
I want to know about data migration techniques and how we can best use MDM while migrating old version of R/3 to new version of R/3....
I have implemented SAP MDM in cases where we have number of SAP R/3 instances across different region and we were taking data from different R/3 one by one and doing data stan'zation,consolidation, Harmonization and all... I am not talking about all this...
There was a good explanation from Markus Ganser about Duplicate data and identical data... I know all this..but my question is when I have only one SAP R/3 and I still want to implement MDM solution while migrating my old R/3 instance to new one, How can I proceed in this scenario? What is the data migration technique...
I know the common answer will be to use MDM as a middle ware..take Master data from old instance and after consolidation, send it back to new instance and at the same time send tran'data directly to new version... But is this worth doing this? Is there any other approach?
If there is any document on this or any one have idea about data migration techniques while implementing MDM solution than send me documents on [email protected].......
In short, I am looking for below 3 points while doing migration along with SAP MDM
Data Migration techniques
Prerequisites
Methodology in this kind of scenario
Step by step procedure
cheers,
R.n

hi..
here i am sending u the link for complete Data Migration Life Cycle
<a href="http://www.redwoodsystems.co.uk/dataMWhitePaper.html#links">http://www.redwoodsystems.co.uk/dataMWhitePaper.html#links</a>
hope it might be of any use to u
thank you & reward points if useful
Message was edited by:
Dasari Narendra

SAP Accelarated Data migration

Hi All,
Could someone kindly provide more info about SAP ADM. I am uanble to get any info about the same. I would like to understand as to how exactly the tool works. I have the 4 page PDF that is posted on the site but its not clear on the actual tool. Can someone kindly provide me with some document or screen shots or any more info about it. My mail id is [email protected] Could someone kindly reply at the earliest.
Thanks
Prahlad

Hi Prahlad,
Go through this hope u can understand.
With SAP Accelerated Data Migration, you can reduce migration
costs by as much as 50% and avoid interruption of business
processes. Moreover, shutting down the source system after
migration reduces system administration costs and total cost
of operations. In short, you realize the following benefits:
Significantly reduced cost and time to complete migration
projects
Accurate, cost-effective data transfer applicable for any kind
of source system
Better data quality because of preconfigured business objects
that ensure data consistency
Improved end-user productivity and acceptance thanks to
migration of historical data
Effective migration that avoids interruption of business
processes
Full support services to avoid risks and ensure the optimum
performance of your new business applications
Faster return on investment
In short, a smoother, more cost-effective migration to a new
technology solution ultimately positions your organization
to lower your total cost of ownership, maintain competitive
advantage, and pursue new business opportunities.
Expertise in Action
SAP Accelerated Data Migration applies a business objectoriented,
two-step approach that uses a neutral interface as a staging area
and predefined migration content for the conversion and upload
of data. The neutral interface enables the SAP tool to generate
predefined migration content and prevents all potential legal
issues regarding the intellectual property of any source-system
vendor. The whole data migration process from the source to
the target system consists of just two steps, as follows:
1. Data is extracted from the source system into the standard
interface as XML files.
2. Data migrates from the interface into the mySAP Business
Suite database. The migration is based on a new migration
workbench engine developed by SAP based on the SAP
NetWeaver® platform. All requirements for mapping structures
and fields and developing complex conversion rules are solved
within this engine (see Figure 1).
Once the migration is complete, business-unit end users have
access to all the legacy data in the new applications as if it had
originated there. They can continue to work on the existing
business process items in the new applications and benefit from
improved functionality.
Lifting the Limitations
Much of the cost and effort involved in classical data migrations
are generated by migration content development, as follows:
Identifying business objects for migration to properly support
the business
Defining the structure and field mapping for the relevant
business objects
Developing conversion rules for all necessary value mapping
Readily available migration content can simplify this effort.
SAP Accelerated Data Migration provides preconfigured business
content, helping you migrate it to your new system more efficiently
and rapidly. The tool allows the migration of all types of
data, independent of its current state within a business process.
This includes master and dynamic data, as well as partially
processed and historical data, to minimize data loss. Business
processes are uninterrupted and normal operation procedures
can be retained.
By providing a standard, neutral interface and reading data as an
XML file, SAP Accelerated Data Migration is applicable for any
kind of source system. Preconfigured data migration objects built
specifically for SAP applications significantly simplify the conversion
from non-SAP software data into SAP software data objects,
yielding far-reaching benefits. Besides reducing related IT costs,
you can be certain of consistency across business-object boundaries.
Through a direct insert into the database, you avoid the
performance limitations of classical data migration.
Reward points if helpful.
Thanks

Data migration ALE or idocs and bapis

hi ,
thank you guys for the support.
i am into a data migration project.
i need the initial setup for the idocs and bapis.
i dont know anything about these so can u send me the process for the setup and the data migration process too with idocs and bapis.
i didnt understand when they asked me if we can data migrate with a ALE, is that the same as using idocs and bapis or is it a different approach.
u can send me at any inofrmation connected to my eamil addr.
i would really appreciate that.
thank you.

Hi,
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
just refer to the link below
http://www.sapmaterial.com/?gclid=CN322K28t4sCFQ-WbgodSGbK2g
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
Example Code
U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
U can find these parameters for a particular condition type in table KONV.
*& Form saveTransactionJOCR
text
--> p1 text
<-- p2 text
FORM saveTransactionJOCR .
data: salesdocument like BAPIVBELN-VBELN,
order_header_inx like bapisdh1x,
order_header_in like bapisdh1,
return type standard table of bapiret2 with header line,
conditions_in type standard table of bapicond with header line,
conditions_inx type standard table of bapicondx with header line,
logic_switch like BAPISDLS,
step_nr like conditions_in-cond_st_no,
item_nr like conditions_in-itm_number,
cond_count like conditions_in-cond_count,
cond_type like conditions_in-cond_type.
salesdocument = wa_order_information-VBELN.
LOGIC_SWITCH-COND_HANDL = 'X'.
order_header_inx-updateflag = 'U'.
conditions
clear conditions_in[].
clear conditions_inx[].
clear: step_nr,
item_nr,
cond_count,
cond_type.
step_nr = '710'.
item_nr = '000000'.
cond_count = '01'.
cond_type = 'ZCP2'.
CONDITIONS_IN-ITM_NUMBER = item_nr.
conditions_in-cond_st_no = step_nr.
CONDITIONS_IN-COND_COUNT = cond_count.
CONDITIONS_IN-COND_TYPE = cond_type.
CONDITIONS_IN-COND_VALUE = 666.
CONDITIONS_IN-CURRENCY = 'EUR'.
append conditions_in.
CONDITIONS_INX-ITM_NUMBER = item_nr.
conditions_inx-cond_st_no = step_nr.
CONDITIONS_INX-COND_COUNT = cond_count.
CONDITIONS_INX-COND_TYPE = cond_type.
CONDITIONS_INX-UPDATEFLAG = 'U'.
CONDITIONS_INX-COND_VALUE = 'X'.
CONDITIONS_INX-CURRENCY = 'X'.
append conditions_inx.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
EXPORTING
SALESDOCUMENT = salesdocument
ORDER_HEADER_IN = order_header_in
ORDER_HEADER_INX = order_header_inx
LOGIC_SWITCH = logic_switch
TABLES
RETURN = return
CONDITIONS_IN = conditions_in
CONDITIONS_INX = conditions_inx
if return-type ne 'E'.
commit work and wait.
endif.
ENDFORM. " saveTransactionJOCR
Bdc to Bapi
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
for VA01 use BAPI_SALESORDER_CREATEFROMDAT2
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
Bapi to VB(Visual Basic)
Long back I had used the following flow structure to acheive the same.
Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
You need to have com4abap.exe
If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
else refer OSS note 419822 for installation of com4abap
after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
for setting up com4abap and rfc destination please refer to the documentation for com4abap.
Invoke NEW DCOM session
call function 'BEGIN_COM_SESSION'
exporting
service_dest = service_dest "(this will be a RFC destination created in SM59)
importing
worker_dest = worker_dest
exceptions
connect_to_dcom_service_failed = 1
connect_to_dcom_worker_failed = 2
others = 3.
call function 'create_com_instance' destination worker_dest
exporting
clsid = g_c_clsid
typelib = g_c_typelib
importing
instid = g_f_oid
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
call function 'com_invoke' destination worker_dest
exporting
%instid = g_f_oid
%method = 'UpdatePDF'
sntemp = g_v_const_filent
snsysid = sy-sysid
snflag = 'N'
tables
rssaptable = g_t_pdfdetail1
%return = g_t_pdfdetail1 "t_test
exceptions
communication_failure = 1 message g_f_msg
system_failure = 2 message g_f_msg
invalid_instance_id = 3
others = 4.
then close the com session , using
FM delete_com_instance
FM END_COM_SESSION
Thanks and regards,
Sarada

Data Migration Best Practice

Is the a clear cut best practice procedure for conducting data migration from one company to a new one ?

I don't think there is a clear cut for that. Best Practice would always be relative. It varies dramatically depending on many factors. There is no magical bullet here.
One except for above: you should always use Tab delimited Text format. It is DTW friendly format.
Thanks,
Gordon

ALE/IDOC for Data Migration of some master data

Are ALE/IDOC available for data migration of the following master data:?
1)General Tasklists in PM
2)Equipment Tasklists in PM
3)Single Cycle plans in PM
4)Strategy plans in PM
5)Equipments
6)Functional locations
7)Measuring points
8)Work Centers
9)Equipment BOMS
10)QM Info Records
11)Sampling procedure
12)Certificate Profiles QM
13)Inspection Plans
14)Material master-QM View
15)PP Recipes
16)Equipment BOM
If anyone has worked worked on ALE/IDOC for data migration, please guide

Hi Dirk ,
Thanks for your reply . Can we use matmas03 for loading. What will be the differences between these two IDOCS.

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

Dought in data migration

Hi Guys ,
I have a small dought related to data migration .
Like
i have a field FISCPER - Fiscal Year /Period is available in the Datasource (Example, 0FI_GL_6) but not available in BSEG,BSEG_ADD ,ZTABLES, FAGLFLEXA Tables..
How to get into BI..
i know there are few steps in involved in getting that field to Bi .
can any buddy let me know what is the procedure to get that field to BI .valuble inputs will be surly be rewarded .
Thanks ,
Vinay .

Hi Vinay,
we cant take zfields in the LSMW by using DI ,
if is there anything like this better to go for BI (Recording method).
if u want to use only DI method, there is an alternative field or not for a particular field search for that and mapp the field in a proper way(carefully).
Reward points if helpful.
Thanks
Naveen khan

Error detail in data migration?

Hi all,
I'm migrating an Access database to Oracle using SQL Developer and the migration workbench.
When I run the data migration, it almost all works, but one table has one error.
I get a list of tables, with rows, total rows, errors and total errors.
Only one error is reported in the summary. 2208 out of 2209 records migrated in this table.
How do I find out what the problem is?
Is there a log anywhere?
Is the data migration script visible anywhere?
Thanks,
Greg H

Hi Dermot,
It turns out there's some corrupt data in the Access database. That or it's in a language that I don't have installed on my machine.
Access displays it as a bunch of squares.
I guess if Access can't figure out how to display it, it would be unreasonable to expect a migration tool to.
The Export Table Data failed with "error #5 Invalid procedure call or argument" and did not create the file for this table.
I'll send this one record back to the business and let them figure out which record it is and if it's important.
Thanks for your help,
Greg H

Data migration - procedure

Similar Messages

Maybe you are looking for