Data migration methods

Hi experts. I am working on a study for a data migration project where data from multiple legacy systems would be moved into SAP. Apart from LSMW and BDC, what are the other useful methods when the data migration involves huge volumes of upload data?

Hi,
Obviously the answer depends to a certain extent on the circumstances of your project (complexity of data, volume, etc) and on the object in question, but here are a few rules of thumb.
If you are new to this I would stay away from IDOCs and BAPIs as the set up is often a little complicated and if there are errors the problem is often not too easy to identify. And IDOC processing is not always as quick as people assume. For example, the customer master IDOC is processed in the background by a call transaction of XD01.
For you I would suggest definitely using LSMW, and where possible within LSMW use the standard uploads. There will be situations where the standard upload does not cover everything (again using customers as an example, it will not include the extended address data or the long texts) but I would still use the standard upload to load as much as you can, and then write a couple of simple update BDC recordings (XD02, XK02, etc) to add what's missing.
Some examples of the standard upload programs are:
Customers - RFBIDE00
Vendors - RFBIKE00
Materials - RMDATIND
All finance transactions - RFBIBL00
Fixed assets - RAALTD01
The standard uploads are normally well documented; they often use BDC (not RMDATIND) so are quite transparent; and they are generally pretty flexible.
There are a few standard uploads which are not so good, such as the sales order load, and to a lesser extent the purchase order load. In these cases you might need to look at using the BAPIs but get help from someone who has used them before.
You might want to use recordings for very simple loads like bank master.
If migrating SAP to SAP, where possible you would look to transfer master data via ALE using IDOCs. But again you need to know what you are doing and it sounds like you are moving from a non-SAP to a SAP system anyway.
Good luck,
Ben
http://www.harlex-ltd.com

Similar Messages

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

How can we do the data migration between Oracle Applications and SAP R/3.

Hi All,
How can we do the data migration between Oracle Applications and SAP R/3 system.What are all the possible ways to move bulk data from Oracle Apps to SAP r/3 system.
Provide any 3rd party tools which supports data migration and also pls rpovide the SAP's own data migration tools with supports the above feature.
Awaiting for best possible solution.
Thanks in advance.
Regards
Dharmaraju

the 3rd party tool is ETL , you can use ETL tool and the prepare the load files then you can use LSMW method to upload the data to SAP.

DMS Data Migration-Help required

Hi,
I don't have enough knowledge on DMS Data migration.
In our recent Implementation, we are implementing SAP DMS.
Our client has more legacy data which is in their server. So we have to upload all the data's into SAP DMS.
I gone through few SCN threads and understand that LSMW & BDC will be used for Data migration.
Which is the best method for Data migration?
We are having 50+ document types and it has different processes (status network), Classification & few Object links.
Please advice me and provide me some examples to upload legacy data in DMS.
Thanks in Advance,
Ravi

Hi Ravi,
There are few approach discussed in the thread https://scn.sap.com/thread/2119796
You may check feasibility on these approaches for your scenario.
We are having 50+ document types and it has different processes (status network), Classification & few Object links.
Creating these configurations into SAP is one time and should not be a problem.
I gone through few SCN threads and understand that LSMW & BDC will be used for Data migration.
Which is the best method for Data migration?
How much volume of data do you have in legacy system ?
Have a thought on whether do you really need to migrate all these data into SAP DMS ???
OR
You can configure the DMS system and start fresh leaving the document in legacy system as it is.
Hope this helps.
Regards,
Deepak Kori

SAP Master data migration tools

Hi,
I would like to know if any SAP standard tools which are available for all master data migration,Kindly share the same which is required for us now.
We have to migrate the data from legacy systems to SAP and we have to use only SAP Standard master data migration tools.
Kindly share the same.
Thanks and Regards,
Raveendra

Raveendra,
SAP migrates data from legacy system using standard tools like LSMW, BDC, BAPI. Under LSMW you will have Batch input, Batch recording, BAPI and IDOCs options. Depending upon requirement you can choose any one of them. BAPI is advisable instead of BDC method.
Also for utilities industry SAP has provided ISU Migration tool (EMIGALL).

SAP HR Data Migration Strategy

Hello Guys,
I worked in Data migration in the areas like SD,MM,FI. But I am new to HR. Can anybody please give me the HR data migration stratagey like what data's (eg, Master ,transactional etc) we need to load and sequences and methods available for each type?
Thanks
Kal

Hi chakri,
Documentation we use is Data Convertion Bueprint which is simply customer's requirements accroding to what infotypes he needs, what data should be migrated and which org. elements will be imported.
Another one is Master Template which is actually prepared by us (technical team). We prepare LSMW for each infotype mentioed in former document, then we document it in this master template to provide to customer required flat files format. We prepare such becuase sometimes some filed may be fixed, some added and even are read-only so should be skipped. So this document differs a bit with previous one in regards to infotypes' used fields. Than we sent this document to our local functional team which is resposible for providing files with given format.
In first document there are also some Golden rules, which describes exact steps for one entire cycle (staring from deliveirng the file, ending with validation of loaded data for one infotype), which each involed party should follow.
The last but not least important document is what we call Loading sequence. I already described it previously. It is just the order of loading the data to infotypes which you should follow. It also contains such information as
- number of records in provided file
- number of errors, successfully loaded records
- files which we share with functional team (error logs)
- finally files which we sent as validation data (extracted from system after successful load of infotype)
Unfortunatelly I can't provide you any of them as these are company documents which are not to be distributed. Sorry I am not allowed to break this rule.
Anyhow I hope it will give you an overview of what kind of documentation you need. It is of course of your team how you organize your work and documentation.
All in all crucial thing is communication between teams, which from my experiaence sometimes fails.
One more thing:
Always remeber to give points to usefull answers, that's how the forum works. Of course it is not obligatory !
Rememebr if you get something, you appreciate it by assigning points:)
Cheers
Marcin

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 from 4.7 system to ECC 6.0

Hi All,
I am a Solution Architect. Currently working on a typical pursuit requirement. the requirement is as below:
One of our customer is currently on SAP 4.7 system. Their current system is shared by 2 companies & the companies got demerged now. Hence they are palnning for fresh ECC 6.0 implementation & migrating Master data & transactional data related to this customer from the current 4.7 system to ECC 6.0.
I am seeing possible way for data migration is through ALE or LSMW. But I am not confident about the execution plan & process.
I would wish to know from you people is:
1. The different methods to do data migration from 4.7 to ECC 6.0 with pros & cons
2. How to plan for data migration
3. Risks & mitigations during data migration
4. different kind of skill set & duration required to accomplish this requirement
Currently we are planning for 6 months for the ECC 6.0 core modules implementation.
If you have undergone this kind of project then request you to share your experience. Any information on this regard is appreciated.
Thanks & Regards,
Suresh

Hi
Go through eh below link for Best Practices
http://help.sap.com/bp_hcmv1600/HCM_US/HTML/master_data.htm
[Risk Factors|http://www.informatica.com/INFA_Resources/article_sap_netweaver_mag_data_migration.pdf]
[Different Methods|http://www.sap-img.com/general/what-are-the-methods-to-migrate-data-from-a-legacy-system-to-sap.htm]
[Best Practices|http://partners.netapp.com/go/techontap/NGS_migration.pdf]
Regards
Pavan

How to use IDoc. in data migration?

Dear Expert,
How can I use IDoc. method in Data Migration???

Hi,
You can use Idoc method in data migration using LSMW - Idoc method.
In LSMW select the Idoc method and give the Message type and Basic type according to your requirement.
Before that you need to maintain the Idoc inbound processing.
Goto LSMW initial screen,
LSMW -> Settings -> IDoc Inbound Processing. Maintain File port, partner type and partner no.
After maintaining the Partner no. goto WE20 (maintain partner no.) and add the message type in the Inbound parameters of the partner no. Also we need to maintain the Process code for the message type.
After all this settings we can use Idoc method for data migration.
The rest of the steps are same as other methods till convert data.
Regards,
Asif Ali Khan

Business Partner Data Migration

Hi experts,
I have few options for doing data migration for business partners for CRM.
1. Using customized program (BAPI/FM)
2. LSMW (IDOC)
3. tcode KCLL and KCLJ
May i know which method is most efficient/fastest/easiest?
Regards,
st

Hi
If standard transaction codes satisfy all your requirements, then you can proceed with the Tcodes.
Only, If they dont then we use other methods like BAPI...
So, now you can decide which one to go with.
PS: There are no complications as such with BAPI. It is important to know how to work on a BAPI. Thats all.
Regards,
Vishwa.

Data Migration questions

Hi,
I'm in the process of migrating my SQL Server 7 database to Oracle 10g R2 using SQL Developer (Version 1.5.1).
When migrating the data, the process terminated half way through due to network problem.
Is it safe to re-do the data migration from there?
Will SQL Developer migration workbench "know" when to pick up from where it last stop? Will this create duplicate records in the target database?
Any recommendation on the best approach to migrate the data will be much appreciated.
Thanks
wilora

Hi Wilora,
SQL Developer will not "know" of the previous data migration.
You need to truncate all your tables first. You can write a quick script to do this.
SELECT 'truncate table ' || table_name || ';' FROM user_tables ; -- obviously be connected to your migrated user.
Then perform the data migration again. Online data migration is only suitable for smaller datasets ,say <100 mb. If you have a network issue again. I would truncate the tables so they are ready to receive the data again. And use the offline data move method.
Heres a quick viewlet of the offline data move
http://www.oracle.com/technology/tech/migration/workbench/viewlets/ofdm.html
Regards,
Dermot.

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

Data Migration examples

can give some examples on data migration?...thanks.

Hi Gow.
Difference Between Batch Input and Call Transaction in BDC
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
Batch Data Communication (BDC) is the oldest batch interfacing technique that SAP provided since the early versions of R/3.   BDC is not a typical integration tool, in the sense that, it can be only be used for uploading data into R/3 and so it is
not bi-directional.
BDC works on the principle of simulating user input for transactional screen, via an ABAP program.
Typically the input comes in the form of a flat file. The ABAP program reads this file and formats the input data screen by screen into an internal table (BDCDATA). The transaction is then started using this internal table as the input and executed in the background.
In Call Transaction, the transactions are triggered at the time of processing itself and so the ABAP program must do the error handling. It can also be used for real-time interfaces and custom error handling & logging features. Whereas in
Batch Input Sessions, the ABAP program creates a session with all the transactional data, and this session can be viewed, scheduled and processed (using Transaction SM35) at a later time. The latter technique has a built-in error processing mechanism too.
Batch Input (BI) programs still use the classical BDC approach but doesnt require an ABAP program to be written to format the BDCDATA. The user has to format the data using predefined structures and store it in a flat file. The BI program then reads this and invokes the transaction mentioned in the header record of the file.
Direct Input (DI) programs work exactly similar to BI programs. But the only difference is, instead of processing screens they validate fields and directly load the data into tables using standard function modules. For this reason, DI programs are much faster (RMDATIND - Material Master DI program works at least 5 times faster) than the BDC counterpart and so ideally suited for loading large volume data. DI programs are not available for all application areas.
Differences between bdc session method and call transaction method.
The most important aspects of the batch session interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel
The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. - No batch input processing log is generated.
Explain in detail with example what is batch input session?
Batch Input Session:
- It is a sequence of transactions, which is generated when user run a particular program.
- It contains the accounting documents that are to be created. The SAP system stores these transactions until you decide to process them online.
- It does not update transaction figures until the session has been processed. Using this technique, you can transfer large amounts of data to the SAP system in a short time.
Three processing modes of executing Batch Input Session :-
(1) Run Visibly : You can correct faulty transactions online & work step-by-step through the transactions not yet executed.
(2) Display Errors only : You can correct faulty transactions online.   Transactions not yet executed, but without error, run in the background.
(3) Run in Background : Recommended by SAP.
<b>Kindly Reward Points If You Found The Reply Usefull<b>,
Cheers,
Chaitanya.

LSMW data migration porcess from the beginning

Hi gurus,
I do understand that there are 14 steps to be completed during migration, but can anyone give me a basic idea as what needs to be done prior to the above steps when starting a data migration project, as i have been only involved in the LSMW(14 steps) process before.
Thanks in advance, points will be awarded for all answers.
Ganga

Hello
As an intro:
Classical data migrations are typically limited to master data and
tend to cause multiple negative impacts on workflow and oper-
ating business units.
To minimize costs, risks, and effort during a data migration and ensure a smooth changeover for operational business processs items, and better reporting
capabilities SAP recently come with a Data Migration Solution called SAP Accelerated Data Migration tool.
This advanced tool, coupled with support from the SAP Services organization and SAP partners, lets you easily migrate and integrate application data from any legacy system into SAP applications and reduce migration costs significantly.
Data migration is done in 4th phase i.e. the final preparation stage of ASAP methodology.
As far as LSMW is concerned, BDC and LSMW both are use for loading data into SAP system. The difference is ,LSMW is loading tool by SAP where you can use various methods to upload, massage data or cleansed your data while loading into SAP from legacy system. The method can be BDC, BAPI, Idocs or SAP ABAP codes. Usually in BDC the user has to write an ABAP program or use other utility to load legacy data.
LSMW has been developed mainly for the Functional people who has no knowledge of the technical aspects of report or BDC in ABAP because its very user friendly and handy to use. So, simply they can upload the master records using LSMW.
Reg
assign points if useful

SAP Accelerated Data Migration

Hi
Can someone tell me if this tool is used only for extraction or can it also be used for reporting??. Whats the transaction code. Do you have to buy an addon to your existing R/3 to have this functional.
Kindly advise.
Thanks
Prahlad

The SAP Safe Passage Data Migration Services provides the tools and methods you need to make a smooth transition from your Peoplesoft, JDEdwards or Siebel system to mySAP ERP or SAP CRM.
SAP Accelerated Data Migration focuses primarily on supporting customers in using the SAP ADM migration tool and ensuring that all migration aspects are included in the implementation project of mySAP ERP or SAP CRM. The migration tool transfers master data as well as history and transaction data. The business process started in the non-SAP system can be continued in the new SAP system without process interruption
refer the below page to download an article ( about 4 page)
http://www.sap.com/community/pub/SimpleSearchResultPage.epx?SearchID=5430195
mail me at [email protected] if you are not able to download
Regards
Vivek
Reward points for all useful answers

Data migration methods

Similar Messages

Maybe you are looking for