Data migration through IDoc processing in LSMW

Hi all,
I have an requirement wherein i need to transfer material master data through LSMW conversion process into R/3 database.The data is to be posted through ARTMAS04 inbound IDoc.
The problem is to transfer the data simultaneousely through multiple instances of E1BPE1MARAEXTRT segment of ARTMAS04 IDoc.
for example:
I need to have an assignment that should work like this:
E1BPE1MARAEXTRT[]-FIELD1 = '00001'
E1BPE1MARAEXTRT[]-FIELD1 = '76545'
E1BPE1MARAEXTRT[]-FIELD1 = 'SAP'.
Can anybody help me in acheiving this example scenario in LSMW.
Thanks.

HI everybody,
i had solved the problem myself.
Thanks all.

Similar Messages

RDS for SAP data migration through IDOC's

Dear Experts
Just now we have installed BODS 4.1 and RDS also installed now. I am in the process of exploring the RDS. I found all the migration objects is available in the form of IDOC's. Now my questions are
How to work on custom IDOC's. Do i need to extensively code on R/3 side to upload the custom fields. Like user exit or BADI for custom fileds
If yes then i would say implementation time through RDS will remain more or less same time.
Through BODS or by RDS migration objects is there any way without coding on ABAP R/3 side, Can we achieve migrating custom fields
Please let me how to achieve above requirements by RDS
Thanks
Vijay Mukunthan

Hi Vijay,
You are right, the standard content of the Rapid Data Migration RDS packages brings the content with the standard IDoc interface for SAP standard only. So custom objects are not pre-built with the package. However, we incorporated the foundation to include custom coding as easy as possible:
1) IDoc
We are using the standard interface technology IDoc. IDocs do have an enhancement concept which is described in the online help. There are three main cases and all of them are supported, however two need additional coding:
Z-fields: Additional fields in existing tables lead to IDoc segment extensions
With the IDoc segment versioning concept this is easy to realize without any ABAP coding
Z-tables: Additional IDoc segments will be necessary and lead to a new IDoc version
With the IDoc versioning concept you can easily add Z-segments with leveraging provided user exits
Custom business objects:
You can even create a complete own IDoc message type in Z-namespace for own stuff, leveraging the given ALE layer of the IDoc middleware
2) Enhancement guide
With the RDS package we offer an enhancement guide which helps you to modify the jobs and data flows in the SAP Data Services content according to the changes in the target IDoc structure to reflect additional fields and tables. We built it as a step-by-step guide following for a sample IDoc type but will work similarly for any IDoc.
Best regards,
Frank Densborn.

CP issues during data migration through IDOC

HI,
We are migrating data from One server to another thru PFAL, but the CP data is not posted as it gives the error
Relationship starting from 01P 00093159 impossible - 01CP50002607 does not exist/is not active
is there a way to migrate the CP data ?

Hi
Check the BD64 configuration if the relationship is filtered out in the Message type.
Try sending the CP object first to the other server and then resend the person again. The error is because the The object is not existing the Target system.
Hope this helps, if so reward.
Thanks
Shyam

WM DATA MIGRATION THROUGH LSMW

Hi
I am Rahul Here.
In a roll out project we want to migrate all the WM data from Server 1 to Server 2.
can someone tell me what all the things are required to be done?
What should be the process?
The process as per my knowledge
1. Download from existing server1 in a format (What that format should be?)
2. Uploade the files to the new system in the same format.
Please comment. Urgent please.
Rahul

Is it just WM that moves, the entire SAP system?
As the material master views will go with the rest of the material master.
So there is no extra/additional work.
In any case, check following link for the datatransfer in WM:
http://help.sap.com/saphelp_40b/helpdata/es/dc/1939516e36d1118b3f0060b03ca329/content.htm

Sales based data migration through LSMW BAPI (BUS1505) change

Hi Everyone,
keep getting this error message while trying to load sales based scenario.
there is neither no term category in the sales rules's structure nor it is in reporting rule's structure.
error message
Term category 1410 cannot be used in sales rules
Thanks in advance.
Regards,
John

John,
That is hilarious I know that feeling.
Not sure why you are getting this error but try following -
1. Make sure your file does not have data in cells which you don't use.
2. Structures which you do not want to pass any values in, do not pass those structures at all. Means if you wish to change only business partner then user only 1 structure and one header record for identifying the contract that is it. Do not pass any other structure not even blank in the file.
3. Make sure in source to target mapping you have made correct assignment if by mistake you have made incorrect assignment you will get bad data.
4. When you read your data execute step display read data and review where you see 1410.
5. Similarly when you execute Convert step in LSMW execute display converted data and you will see if 1410 was populated.
last step if none of the above works ) Display the conversion program and put a debug point at this particulat field and see from where this value is being passed. This is no standard error so it has to be your LSMW/Input file.
Let me know what it was
Jag

Steps in idoc process in lsmw

hello i need to migrate lsmw using idocs ?can anybody please tell me the ateps in idoc method
Regards
priya

Hi,
If you have knowledge of IDoc you can easily perform the following steps for LSMW through Inbound Idoc
To use IDoc inbound processing, you must first perform the following steps:
Step 1.Define or select a file port for transporting the file. Optionally, you can also create a tRFC port.
Step 2.     The partner type has to be defined or selected.
( WE20 to Maintain Partner Profiles )
For example-
Partner type:US
Report name:/SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine:READ_USER
Short text:     Testing
Step 3.     The partner number has to be defined or selected.
For example
Partner number:LSMW
Partner type:US
Partner status:A (active)
Type:US
Language:     EN or DE
ID:Your user ID
Step 4.     IDoc inbound processing must be activated, and the workflow customizing must be checked. Both of these tasks are performed once in each system.
For this Step 4you need to doi the following things
I) Choose Workflow customizing.
   The Workflow Customizing screen appears.
II)Choose Perform Automatic Workflow Customizing.
   The auto customizing log for the runtime system is displayed.
III)Check the entries.
The following entries of the workflow runtime system must have a green checkmark assigned to them:
Maintain System Administrator for Workflow.
Configure RFC Destination.
Classify Decision Task as General.
Activate Send to Objects
Thanks
PK

Data upload through IDOC

Hi Friends,
I want to upload data to ME01 (source list) and ME11 (info record) transaction using IDOC
please guide me how to handle it programatically.
Thanks in Advance
Gayathri

HI
see this link click on each link it will show you step and screen shot of that step
http://www.****************/Tutorials/LSMW/IDocMethod/
Rewar di fusefull

Error in data migration through DTW

Hi All,
      I am creating a template for user define Master data table from DTW, when i am trying to port data by using that template through DTW. it is giving error like--'Master data type User table cannot add row'
So can any one have solution for this.
Regard's
Hari

hi,
object name is U_SCRAPMAST
Code     Name     U_SCD     U_SDSC     U_Status
Code     Name     U_SCD     U_SDSC     U_Status
1          SCR1     SCR1
2          SCR2     SCR2
regard's
Hari

HELP ME ON DATA MIGRATION PLEASE

Hi
what is SAP data migration what kind of tools and techniques include in that and also please what are the roles and responsibilities include in that when we are working on project.(RELATED TO ABAP)

Data Migration Current Situation
Data migration or data conversion is a persistent issue facing most organizations who have implemented SAP. Whether it is during the final phases of a new SAP implementation, during SAP upgrades and updates, during corporate restructurings, or during mergers and acquisitions, data migration continues to remain a challenging problem for IT.
Most data migration projects are faced with a time and budget crunch. But, these projects usually require extensive support from programmers and other technical experts and therefore data migration projects tend to get expensive and time-consuming.
The tools for data transfer and data migration provided by SAP are very technical and have a steep learning curve associated with them and they require technical experts to build and implement the data migration scripts.
Data Migration Ideal Scenario
An ideal data migration scenario would let the data migration project be implemented by the end user departments themselves. A few super-users within these end-user departments that supply the data should have the ability to transfer and migrate data themselves without relying on technical experts. Such a scenario would significantly cut the time and effort required in a data migration project.
Reaching such an ideal scenario would require data migration tools that are easy to learn and require no programming. Furthermore, these tools should work across all the different SAP modules and the SAP products, including the different versions of SAP.
Data Migration
Data Migration is the process of moving required (and most often very large) volumes of data from our clients existing systems to new systems. Existing systems can be anything from custom-built IT infrastructures to spreadsheets and standalone databases.
Data Migration encompasses all the necessary steps to cleanse, correct and move the data into the new system *. Technological changes, change in providers, software updates or data warehousing / data mining projects make such delicate and critical operations necessary.
Data Migration can be done using BDC, LSMW, BAPI, Idoc's.
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
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.
Refer this
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 ?
http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html
http://www.****************/InterviewQ/interviewQ.htm
http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Check these step-by-step links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
regards,
srinivas
*reward for useful answers*

Failing Search String in EBS through IDOC

Dear All,
we upload our EBS through idoc processing of type finsta. The problem is that for a particular bank theres a search string attached which will replace the posting rule if a certain but fix narration (say "Trf 66852") is received in note to payee field apart from the fixed external transaction code. The problem is that, in the idoc segment, though i am putting the same fixed narration as Trf66852 however the posting rule is not replacing. I am not able to determine even if the search string is working. I tried checking in EBSTS but apart from two blank lines nothing much is appearing. If anyone ever come across this issue pls share your experience.
best regds
Subha

Hi Subha,
The Notes to payee updates from FINSTA IDoc should work.
1. If you want to know if the configured search string is working or not, you can simulate it in OTPM, where the search strings are defined in the search string definition > Simulation. You need to entry the text from bank in Simulation and click on test.
2. Secondly, you can check in table FEBRE where the notes to Payee fields are updated.
Regards,
Kavita

Data Transfer using LSMW IDOC processing with multiple segments

we need to post the document data (Header structure, BP item structure, G/L item structure..etc) using LSMW IDOC processing.
is it possible to transfer data for all these structures (Segments) in single file?

Thanks for the reply.
I am assuming when we are specifying the file in LSMW we are going to give the option to generate the file with include all structures.
could you please elaborate further is there any thing specific we need to do while configuring LSMW to get the file for all segments in the IDOC with field names which we are going to populate with data, so that we can use it for data transfer.
any help document will be helpful.

Data Migration-LSMW using IDoc Method

Hi Friends,
I have contract relevant information in the form of a excel spreadsheet/tab delimited flat file.
This transactional data has information such as Header Data, Item Data and Sub Item data (BOM explosion).
I need to migrate this data from the flat file to the CRM application using the IDoc Method of LSMW.
/When I used the Batch Input Recording method, the item data was not captured during recording./
Kindly send me relevant information to [email protected]
Thanks in Anticipation
rgards,
Praveen

Hello Sven,
thanks for your comment. Unfortunatelly those both transactions do not exitst because I work on SAP CRM 7.0 instead of SAP ECC. I also looked for similar transactions in the table but didn't find anything.

What are the steps we have to fallow to upload data through IDOC in LSMW?

What are the steps we have to fallow to upload data through IDOC in LSMW?

HI
see this link click on each link it will show you step and screen shot of that step
http://www.****************/Tutorials/LSMW/IDocMethod/
Rewar di fusefull

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

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

Data migration through IDoc processing in LSMW

Similar Messages

Maybe you are looking for