BO DI for extracting data from legacy to SAP BW 7.0

Hi,
Has anyone worked on scenario where BO Data Integrator is being used as ETL tool for extracting data from legacy systems to SAP BW 7.0 ?
Please share your experience on such a landscpae or related documents any of you had come across.
Regards,
Pritesh

Hi,
BO Integrator connects with other system (Database) and you will be creating your reports on the top of that DB or system. It never saw it being used to pull data from legacy to BW.
Regards,
Bashir Awan

Similar Messages

BO DI for extracting data from legacy system to SAP BW 7.0

Hi,
Has anyone worked on scenario where BO Data Integrator is being used as ETL tool for extracting data from legacy systems to SAP BW 7.0 ?
Please share your experience on such a landscpae or related documents any of you had come across.
Regards,
Pritesh

There are couple of them - Lawson ERP, Kalido, AS/400. ECC 5.0 might be there as well.
Regards,
Pritesh.
Edited by: pritesh prakash on Jun 14, 2010 2:00 PM

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

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

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

How do you validate transfer of data from legacy to SAP (Tcode: SQVI)?

Hello PP members:
I would like to know how to validate transfer of data from legacy to SAP
A friend of mine was telling it has to do with SAP quick viewer(SQVI) but could not able to much leads on it
I would be thankful if can provide insights into the subject
Thanks for your time,
Suren R

Suren,
Yes, you could create queries in SAP with SQVI and get the data in SAP. But you need to be aware of all the relevant tables in SAP.
For information for creating queries use link:
http://help.sap.com/saphelp_47x200/helpdata/en/05/2b1df9209411d6b1d500508b6b8b11/frameset.htm
For getting the relevant tables the easiest way is :
1) Goto Se16.
2) Choose F4,
3) Click on SAP applications and drill down to the relevanttable.
Hope this is useful. If yes reward poins and close this thread.
Regards
Ram

Regarding Migrating data from Legacy to SAP

Hi All,
We are in Migration Project. We have to upload data from legacy to SAP, either using BDC or Cross-Applications in the following SD scenario's.
1. Customer Master
2. Inquiries
3. Quotations
4. Proposals
5. Sales Order
6. Goods Issue
I would like to know, which concept is better for each of the above scenario. Each option have advantages and disadvantages. So, I need suggestion regarding this.
Regards,
Sathya.

hi
LSMW and BDC are vastly different.
BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/backgrou nd processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
also check this link:
Diff. between LSMW & BDC
Re: bdc and lsmw
plz reward points if it helps
rgds.

Extract data from AMPLA to SAP BW

Hi All,
My requirement is to extract data from a Non SAP system called AMPLA (SQL Server 2012) to SAP BI system (7.0). I need to consider possible ways for SAP BI to extract data from Non SAP Systems like DB Connect, UD Connect, Web services etc. Does anyone have experience extracting AMPLA data to SAP BI system successfully and what method is ideal to be used? Also in what form is data usually available in AMPLA source system(tables/views etc)?

Hi Udit
Before that could you refer this SAP Notes for database connection
128126: Database Connect for external tools
1601608: How to access an external SQL Server database
Regards
Sriram

Extracting data from Legacy system - How do we get the data into a normaliz

Hi All,
Requirement that I have now is to get the data from 6 different tables ORACLE database to BI using DB Connect, where in each of those 6 tables has the transactional data as well - If it is only 2 tables, would have been creating a view and get the data. Each of the 6 tables are linked to one other by the Primary Key and Foreign key relation ship.
If it is from ERP system we would have created a Functional Module.
Please advice me on how to get the data to BI end from those tables in Legacy system.
Thanks in advance.

Anil:
I recommend following Ralph Kimball's EDW data modeling principles.
Have a staging layer of DSO's with data dump from source system. So have 6 different DSO's extracting data from 6 tables from source system independently.
Then have an integeration layer of DSO's depending on requirement. You could combine data from 2 or more DSO's here based on requirement and integrate your data here. Use primary key foreign key relationships here to do look ups or direct loads to do your business logic.
Then have an analytical layer of InfoCubes, MultiProviders, InfoSets as required.
The 3 layered architecture is a standard best practice that i have seen followed in many organizations. You could search for this type of architecture online under EDW (Enterprise Data Warehouse). There should be plenty of information available.
Good Luck.
MP.

How to extract data from legacy system to source file

Hi can anyone tell me the procedute to copy data from legacy system to source files....this data needs to be moved to base tables
can any one tell me the procedure and any sample code i,e any example
Thanks & Regards
Krish

You should post your thread to ...:
http://forums.oracle.com/forums/forum.jspa?forumID=183
providing all necessary info......!!!!
Greetings...
Sim

How to upload the master data from legacy to SAP

Hi Frends,
how to upload the master data from legacy system to SAP System once the configuration is over.how to carry forward the open items of vendors and customers while uploading.who will upload functional consultantsor ABAPER.
please clarify me
Regards
Sap Guru

Hi ,
use LSMW or BDC for uploading Master & transaction data.
This work is done by the Respective Functional team.
Chandra

Options for loading data from legacy mainframe to SAP CRM and ECC

Hello All,
I am new to SAP.
As part of data conversion planning from legacy mainframe to SAP CRM and ECC systems, I need to know the different tools available for loading the data and comparative analysis of the tools by showing the features. Please also describe the process to evaluate the tools (prototyping, technical discussions etc) and make the recommendations.
I would also appreciate any information on testing tools like (eCATT) and any third party tools (like Informatica)
I know I am asking for lot of things here. But, I really appreciate any information reagrding this.
Thanks,
Balu

Hi
Data Migration(Conversions) mainly involves the following Major Steps
Discovery->Extract->Cleanse->Transform->Load
Discovery-> Involves identifying various source systems available where the actual data is residing.
Extract->Extract the data from the source systems(legacy systems)
Cleanse->Cleanse the data by enriching it,De-duplications etc
Transform->Transform the data into SAP Loadable format
Load->Upload the data into SAP Using the Load Programs(Eg,BDC,LSMW,Data Transfer Workbench,BAPIs etc)
Also i would request you to visit http://www.businessobjects.com/solutions/im/data_migration.asp
Cheers,
Hakim

FM code for extracting data from 10 tables

Hi All,
I have a requirement, where i need to extract the data from 10 tables using FM which is further used to create a data source in SAP R3.
The fields are almost similar in all the tables but yet i have to fetch the data from all the tables.
My approach:
1. I have created a structure with all the fields in it from all the tables that comes to 35 fields.
2. create a structure of each table and loop it into an internal table and work area.
3. writing a read statement based on a key value from all the work areas and populate the same into my final structure.
Note: there is a key field that need to be considered when updating the data into final stucture.
All help on the code / logic would be appreciated.
Thanks
Moderator message : Spec/requirements dumping not allowed, show the work you have already done. Thread locked.
Edited by: Vinod Kumar on Feb 28, 2012 8:35 PM

Hi All,
I have a requirement, where i need to extract the data from 10 tables using FM which is further used to create a data source in SAP R3.
The fields are almost similar in all the tables but yet i have to fetch the data from all the tables.
My approach:
1. I have created a structure with all the fields in it from all the tables that comes to 35 fields.
2. create a structure of each table and loop it into an internal table and work area.
3. writing a read statement based on a key value from all the work areas and populate the same into my final structure.
Note: there is a key field that need to be considered when updating the data into final stucture.
All help on the code / logic would be appreciated.
Thanks
Moderator message : Spec/requirements dumping not allowed, show the work you have already done. Thread locked.
Edited by: Vinod Kumar on Feb 28, 2012 8:35 PM

Conversion of Vendor data from legacy to SAP

Hi Gurus,
In our conversion process, we have converted our legacy system vendors to SAP. After our conversion, during our validation, we have pulled data from LFA1 (pulled Vendor and Account Group), LFB1 (Pulled Vendor and Previous Account Number - ALTKN) and LFM1 (Pulled Vendor and Currency Code)
We have observed that the number of vendor records in the three tables are different. Here are the results
1) LFA1 - Number of records - 51,158
2) LFB1 - Number of records - 51,164
3) LFM1 - Number of records - 51,147
Can anybody guess why the number of vendor records are different in different tables?
Thanks

Hi,
I think the explanation is not so difficult:
LFA1 key fields: MANDT (client), LIFNR (vendorID)
LFB1 key fields: MANDT, LIFNR, BURKS (company code)
LFM1 key fields: MANDT, LIFNR, EKORG (purchasing organisation)
Relations:
LFA1 - LFB1 > 1 : N
LFA1 - LFM1 > 1 : N
You always have to have a record for a vendorIDin LFA1, but you not always have to have a record for this vendorID in LFB1 and LFM1 if the vendor is not extended for any company code or any purchasing organisation.
If the vendor is extended for a company a company code or purchasing organisation, it means you have a relevant record for the vendorID in LFB1 and LFM1.
You have more records (51 164) in LFB1 than in LFA1 (51 158) because one vendorID (only one record in LFA1) may be extended for several (more than one) company codes. Each extension of this vendorID for company code has a separate record in LFB1. (LFA1 > vendorA; LFB1 > vendorA-company code1 + vendorA-company code2)
Less record in LFM1 means that you have such vendorIDs (records) in LFA1 that are not extended for any purchasing organisation.
BR
Csaba
Edited by: Csaba Szommer on Jul 27, 2008 2:02 PM

Conversion of data from legacy into SAP using LSMW(Direct input)

Hi guys,
 I need a help from u for the following scenario. The scenario is about FI & MM Vendor Master Conversion.The brief description of this scenario is as follows:
 Conversion of Accounts Payable Vendor Master Record from Legacy systems into SAP. The purpose of this document is to define the master data fields that will need to be populated as well as the order in which the different parts of Vendor master should be loaded.
Transaction Code(s) to be used: XK01 Create Vendor Master Centrally RFBIKR00 LSMW Program RFBIBL00.
Please help me to do this scenario.
Regards
Ram.V

Hi Naveen,
 Send me the suitable screen shot to my id. Also if u can, send me the same for batch input too.
 My mail id is "[email protected]".

Extract data from PDF to SAP

Hi all,
 I have created an Offline form in sfp Transaction and emailed successfully .
 And now that Receiver has sent me the form with the filled pdf form to my outlook id ( bcas my mail id is being configured in SMTP) .
 Now I want to Update a table with that filled values in the received pdf..
1) What r all the steps should i follow now?
2) What for guided procedures or workflow?
3) Do i have the option to receive the mail to my Business workplace inbox instead my personal mail id?
i went thru all the related threads in this topic. But could not get the Idea..
If someone knows please suggest me ..
Thank you.
Rgrds.
Edited by: Deepa K on Feb 25, 2008 1:30 PM

Hi,
When you create an abap object based on standard interface IF_INBOUND_EXIT_BCS you will got 2 method .
First here is the attributes i define in my object , all are Private instance attributes.
XML_DOCUMENT type ref to IF_IXML_DOCUMENT.
CONVERTER type ref to CL_ABAP_CONV_IN_CE,
ATTACHEMENT_ATTRIBUTES type BCSS_DBPA,
ATTACHEMENT_FILE type BCSS_DBPC ,
BINARY_FILE Type XSTRING,
FORMXML Type STRING,
PDF_FORM_DATA Type XSTRING ,
XML_NODE Type Ref To IF_IXML_NODE,
XML_NODE_VALUE Type STRING.
Set this code in method CREATE_INSTANCE
* Check if the singleton instance has already
* been created.
IF instance is INITIAL.
CREATE OBJECT instance.
ENDIF.
* Return the iTE nstance.
ro_ref = instance.
The other method is where the mail will be process
here is a sample code for method PROCESS_INBOUND
* Data definition :
DATA : pdf_line TYPE solix .
DATA : nb_att(10) TYPE n.
DATA w_part TYPE int4 .
FIELD-SYMBOLS : <pdf_line> TYPE solix.
** Set return code so no other Inbound Exit will be done.
e_retcode = if_inbound_exit_bcs=>gc_terminate.
TRY .
* Get the email document that was sent.
 mail = io_sreq->get_document( ).
* Get number of attachement in the mail
* If number is lower than 2 that means no attachement to the mail
 nb_att = mail->get_body_part_count( ) - 1.
 CHECK nb_att GT 0.
 CLEAR w_part.
* Process each document
 DO nb_att TIMES.
 w_part = sy-index + 1 .
 CLEAR xml_document .
* Get attachement attributes
 attachement_attributes =
 mail->get_body_part_attributes( im_part = w_part ).
 IF attachement_attributes-doc_type IS INITIAL.
 DATA w_pos TYPE i .
 FIND '.' IN attachement_attributes-filename
 IN CHARACTER MODE MATCH OFFSET w_pos.
 ADD 1 TO w_pos.
 attachement_attributes-doc_type =
 attachement_attributes-filename+w_pos.
 ENDIF.
* Get the attachement
 attachement_file = mail->get_body_part_content( w_part ).
* If attachement is not a binary one ,
* transform it to binary.
 IF attachement_attributes-binary IS INITIAL.
 CALL FUNCTION 'SO_SOLITAB_TO_SOLIXTAB'
 EXPORTING
 ip_solitab = attachement_file-cont_text
 IMPORTING
 ep_solixtab = attachement_file-cont_hex.
 ENDIF.
* Convert the attachement file into an xstring.
 CLEAR binary_file.
 LOOP AT attachement_file-cont_hex ASSIGNING <pdf_line>.
 CONCATENATE binary_file <pdf_line>-line
 INTO binary_file IN BYTE MODE.
 ENDLOOP.
 TRANSLATE attachement_attributes-doc_type TO UPPER CASE.
* Process the file depending on file extension
* Only XML and PDF file is allow
 CASE attachement_attributes-doc_type .
 WHEN 'PDF'.
* Process an interactive form
 me->process_pdf_file( ).
 WHEN 'XML'.
* Process XML data
 me->process_xml_file( input_xstring = binary_file ).
 WHEN OTHERS.
* Nothing to do , process next attachement
 ENDCASE.
 CATCH zcx_pucl003 .
ENDTRY.
As you can see i add several specific method to my object in order to make the code more clear.
Here is the code for all the specifics methods
PROCESS_PDF_FILE
TRY.
* Extract the Data of the PDF as a XSTRING stream
 me->process_form( pdf = binary_file ).
 me->process_xml_file( input_xstring = pdf_form_data ).
 CATCH zcx_pucl003 INTO v_exception.
 RAISE EXCEPTION v_exception.
ENDTRY.
PROCESS_FORM with inbound parameter PDF type XSTRING
DATA :
 l_fp TYPE REF TO if_fp ,
 l_pdfobj TYPE REF TO if_fp_pdf_object .
TRY.
* Get a reference to the form processing class.
 l_fp = cl_fp=>get_reference( ).
* Get a reference to the PDF Object class.
 l_pdfobj = l_fp->create_pdf_object( ).
* Set the pdf in the PDF Object.
 l_pdfobj->set_document( pdfdata = pdf ).
* Set the PDF Object to extract data the Form data.
 l_pdfobj->set_extractdata( ).
* Execute call to ADS
 l_pdfobj->execute( ).
* Get the PDF Form data.
 l_pdfobj->get_data( IMPORTING formdata = pdf_form_data ).
 CATCH cx_fp_runtime_internal
 cx_fp_runtime_system
 cx_fp_runtime_usage.
ENDTRY.
PROCESS_XML_FILE with inbound parameter INPUT_XSTRING type XSTRING.
TRY.
 me->create_xml_document( input_xstring = input_xstring ).
 me->process_xml( ).
 CATCH ZCX_PUCL003 INTO v_exception.
 RAISE EXCEPTION v_exception.
ENDTRY.
CREATE_XML_DOCUMENT with inbound parameter INPUT_XSTRING type XSTRING.
DATA :
 l_ixml TYPE REF TO if_ixml,
 streamfactory TYPE REF TO if_ixml_stream_factory ,
 istream TYPE REF TO if_ixml_istream,
 parser TYPE REF TO if_ixml_parser.
DATA: parseerror TYPE REF TO if_ixml_parse_error,
 str TYPE string,
 i TYPE i,
 count TYPE i,
 index TYPE i.
DATA :
* Convert the xstring form data to string so it can be
* processed using the iXML classes.
TRY.
 converter = cl_abap_conv_in_ce=>create( input = input_xstring ).
 converter->read( IMPORTING data = formxml ).
* Get a reference to iXML object.
 l_ixml = cl_ixml=>create( ).
* Get iStream object from StreamFactory
 streamfactory = l_ixml->create_stream_factory( ).
 istream = streamfactory->create_istream_string( formxml ).
* Create an XML Document class that will be used to process the XML
 xml_document = l_ixml->create_document( ).
* Create the Parser class
 parser = l_ixml->create_parser( stream_factory = streamfactory
 istream = istream
 document = xml_document ).
* Parse the XML
 parser->parse( ).
 IF sy-subrc NE 0
 AND parser->num_errors( ) NE 0.
 count = parser->num_errors( ).
 index = 0.
 WHILE index < count.
 parseerror = parser->get_error( index = index ).
 str = parseerror->get_reason( ).
 index = index + 1.
 ENDWHILE.
 EXIT.
 ENDIF.
 CATCH cx_parameter_invalid_range
 cx_sy_codepage_converter_init
 cx_sy_conversion_codepage
 cx_parameter_invalid_type.
ENDTRY.
Method PROCESS_XML
DATA v_formname TYPE fpname.
* For each node of the XML file you want to retrieve the value
* Then use the specific method PROCESS_NODE .
* Find Node where System Id is store
CLEAR : xml_node ,
 xml_node_value.
TRY.
 me->process_node( node_name = 'SYSID' ).
 CHECK NOT xml_node_value IS INITIAL.
 CASE xml_node_value.
 WHEN sy-sysid.
* Search for Form name.
 me->process_node( node_name = 'FORM_NAME').
 CHECK NOT xml_node_value IS INITIAL.
 v_formname = xml_node_value.
 WHEN OTHERS.
 ENDCASE.
 CATCH cx_root.
ENDTRY.
Method PROCESS_NODE with inbound parameter NODE_NAME type STRING
CLEAR : xml_node , xml_node_value .
xml_node = xml_document->find_from_name( name = node_name ).
IF xml_node IS INITIAL.
* Missing one node in the form, nothing will be done
 RAISE EXCEPTION TYPE ....
ELSE.
 xml_node_value = xml_node->get_value( ).
ENDIF.
Hope this help you .
Best regards
Bertrand

Extract data from CRM to SAP R/3

Hi Experts,
I Facing Problem to Extract the data from database table BUT000 in CRM 2.0 System to SAP R/3 whether its possible to update the data directly in R/3 system from CRM. whether any functional module exists?
Plz Provide me details about it

Why do you need to copy it? The data is easily available from R/3 via RFC.
Rob

BO DI for extracting data from legacy to SAP BW 7.0

Similar Messages

Maybe you are looking for