Issues in using LSMW IDOC method for Article Hierarchy

Hi Experts,
I am working on a scenario for uploading article hierarchy using LSMW idoc method.
Details:
Message type WMATGRP
IDoc type WMATGRP01
But as per my understanig, for processing, there should be a inbound Function module/Process code. But I am unable to find out any process code for this in tcode WE42/We60.
Could you please help in this problem.
Regards
Krishan Kumar

Hi Saeed,
For example if you want t create bom through lsmw then we will *** two files one header and other item one.In the same way .In lsmw start by keeping the idoc method i will only propose at second step how many files it need. Just map the idoc and see. Post if need more help.
Regards,
Madhu.

Similar Messages

Problem LSMW + IDOC method for message type : MATMAS

hi friends,
I am using LSMW + IDOC method Message : MATMAS , idoc type : MATMAS03 .Setting every thing are fine. Finally Material is not created with error "message have been issued number : <idoc number>".
data : material, industry type, material type, description, Basic unit of mesure.
Please help me.
Balaji.T.

Hi,
I have nothing found regarding your issue. But maybe a look at SAP note 638058 will give you a hint.
Regards,
Klaus

Multiple Source Structure in single flatfile using lsmw idoc method

Hi Abapers,
we have a requirement for Business partner Data mIgration into CRM system using LSMW idoc method,I got a flat file
which has multiple source structures like(header structure,Tax structure,Mailstructure,Identification structure,bankdetails structure,card strcuture........etc of 12 structures) with identification for each structure. can any one help me how to handle this in lsmw or any link of this kind of scenario will be helpful for me .
Thanks and Regards,

Hi Saeed,
For example if you want t create bom through lsmw then we will *** two files one header and other item one.In the same way .In lsmw start by keeping the idoc method i will only propose at second step how many files it need. Just map the idoc and see. Post if need more help.
Regards,
Madhu.

Import Product Price and Condition using LSMW IDoc method

Hi Friends,
I am working on the Product Import to CRM from flat file using LSMW IDoc method using the "CRMXIF_PRODUCT_MATERIAL_SAVE" message type.
I am able to import the entire product with its required details except the Price and its conditions.
Can anyone please let me know which structure or with message type to be used to import the Product Price and condition using the IDoc method.
Please pass on your valuable comments.
Thanking you,
Naveen

Hi Naveen.
I am doing the same thing but only the product gets created and the details like short text, unit etc. do not get populated. The idoc gets processed successfuly. Can you share the fields that are required to be mapped or are mandatory.

Create Purchase info record using LSMW idoc method

Hello Friends,
I am trying to update Purchase Info records using LSMW Standard program RM06IBI0.
But it is not updating the condition price details and scale Quantity.
For that the form suggessted LSMW IDOC method. with : Message Type         COND_A / COND_A02.
But i dont know is the info record created earlier to this step or else we can create both using this method
at a time ? Does anybody please suggest.
( Actually Purchase Info record created using transaction ME11 ).
Regards,
Phaneendra

you first create the info record and subsequently you load the conditions.
become familiar with the condition tables and its key first. Check How table A017 and A018 are maintained.
Intresting is the field VAKEY which is actually the link to your info record.
This is a combination of vendor, material, purchasing org, plant , and info record indicator.
data: begin of ZZVARKEYA,
        ZLIFNR like LFM1-LIFNR,
        ZMATNR like MARc-MATNR,
        ZEKORG like LFM1-EKORG,
        ZWERKS like MARC-WERKS,
        ZINFTYP like EINE-ESOKZ,
        end of zzvarkeyA.

Step by step instruction for Using LSMW Recoding method for Material Master

Guys,
Can some one explain step by step procedure for uploading the materials master data to R/3 by using LSMW Recoding method. By the time you reply I will go through the rule of uploading the data..
Thanks guys,
Dhanu.

Hi,
The Legacy System Migration Workbench (LSMW) is a tool recommended by SAP that you can use to transfer data once only or periodically from legacy systems into an R/3 System.
The LSM Workbench covers the following steps:
(1)Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files)
(2)Convert the data from source format to target format
(3)Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
The Steps for LSME are:
Example: Customer Master upload:
LSMW to Update Customer Master Records with Transaction Recording
Call Legacy System Migration Workbench by entering transaction code LSMW. Every conversion task is grouped together as Project / Subproject / Object structure. Create a Project called LSMW_DEMO and a Subproject as CUSTOMERS and Object as CUST_REC
Step 1: Maintain Object attributes
In this example, you will be updating the customer master records with the help of recording a transaction (XD02). Choose radio button Batch Input Recording and click on the recording overview icon to record the R/3 transaction. Enter the Recording name as XD02_REC, the description as Customer Master Updates Recording, and the transaction code as XD02.
Step 2. Maintain Source Structures
Give a name and a description to the source structure
Step 3. Maintain Source Fields
In this step, you need to list what fields are present in the source structure. The easiest way is to click on u2018Table Maintenanceu2019 icon to enter Fieldname, Type and Length for each field
Step 4: Maintain Structure Relations
Execute a step to u2018Maintain Structure Relationsu2019. Since, there is only one Source and Target Structure, the relationship is defaulted automatically.
Step 5: Maintain field mapping and conversion rules
Field RF02D-D0310 represents that you chose u2018Sales viewu2019 for the customer Master screen accordingly its value should be set to X. Keep your cursor on field RF02D-D0310 and click on Constant rule icon to choose the constant value of u2018Xu2019.
If your source file already has the field value, you choose rule u2018Source Fieldu2019.
Keep cursor on field u2018KUNNRu2019 and click on u2018Assign Source fieldu2019 icon to choose source field CUSTOMER from structure XD02S
Step 6: Maintain fixed values, translations, user-defined routines
You can also maintain re-usable translations and user-defined routines, which can be used across conversion tasks. In this case, that step is not required.
Step 7: Specify files
In this step, we define how the layout of the input file is. The input file is a [Tab] delimited with the first row as field names. It is present on my PC (local drive) as C:\XD02.txt.
Step 8: Assign files
Execute step u2018Assign Filesu2019 and the system automatically defaults the filename to the source structure.
Step 9: Read data
In this step, LSMW reads the data from the source file (from your PCu2019s local drive). You have the option to read only selected rows and convert data values to Internal format.
Step 10: Display read data
This step is optional. If required, you can review the field contents for the rows of data read.
Step 11: Convert data
This is the step that actually converts the source data (in source format) to a target format. Based on the conversion rules defined, source fields are mapped to target fields.
Step 12: Display Converted data
Again this is an optional step to view how the source data is converted to internal SAP format
Step 13: Create batch input session
Once the source data is converted in an internal format, you can create a batch session to process updates.
Step 14: Run Batch Input Session
You can execute the BDC session by Run Batch input session. Executing a batch input session is a standard SM35 transaction for managing BDC sessions. Once you have successfully executed the batch input session, the customer master records are updated in the system. You can confirm this by viewing the customer master records (XD03).
Follow the link for material master
http://www.sap123.com/showthread.php?t=98
Regards,
Biju K

Re:Uploading of material master data using lsmw-idoc method

Hi friends,
While processing each idoc one log on window is opening,and status of idoc is 51,eventhough i am passing material description to maktx of e1maktm,it is showing an 'No description is passed'.
Colud you please tell me how to correct these errors,i am new to this lsmw-idoc method.
Thanks in advance,
Anusha.

Thank you for reply.
Actually I am uploading the data in flat file from file port to sap.
In idoc inbound processing of lsmw i have created a file port and iam giving the logical system name of the same client.
is this the correct procedure.
Every time when i process each idoc one new logon window is opening and it is showing idoc status as 51.
could you please tell me how to correct this one.

Error while uploading the data Using LSMW - Idoc method

Hi Experts,
I am working on LSMW using Idoc method. Till 12th step (Display converted data) i wasn't got any problem. For the Idoc method, I have to specify details to Idoc inbound processing from the menu settings.
In that screen I have to specify file port, partner type and partner no. I have created a file port ZFILE. Can u tell me what ahould I pass in that screen? Where should be the file i.e in the application server or presentation server? What should be the directory and function module. Can u provide step by step?
After that I have to specify partn.type. What should I select for that?
After that I have to specify partner no. Whether it is inbound or outbound?
I got No data found for the following detials.
port - ZFILE
in the inbound file tab, e:\ as physical directory; EDI_PATH_CREATE_USERNAME as function module.
Partner type - US
Parnter no. - LSMW with the inbound parameters message type - MATMAS and Process code - MATM.
Please tell me how can I upload properly? Please don't ignore as i am asking same question again becasue I have gone through related threads also. But i didn't find the exact requirement.
proper documentation will be rewarded.
Thanks in Advance.
James.

Hello,
I could identify the error. It was due to incorrect UOM. Problem resolved.
Thanks,
Madhura

Sales Order Creation using LSMW IDOC method.. ( Custome Interface)

Hi ABAP'rs,
                 Please provide me LSMW steps for creating Sales Order using IDOC method.
                        Thanks and Regards,
                                              Param.

LSMW-IDOC in General
LSMW Step by Step Guide: Legacy System Migration Workbench is an R/3 Based tool for data transfer from legacy to R/3 for one time or periodic transfer.
Basic technique is Import data from Spreadsheet / Sequential file, convert from source format to target format and import into R/3 database. LSMW not part of standard R/3, if we need this product email [email protected]
Advantages of LSMW:
Most of the functions are within R/3, hence platform independence.
Quality and data consistency due to standard import techniques.
Data mapping and conversion rules are reusable across projects.
A variety of technical possibilities of data conversion.
Generation of the conversion program on the basis of defined rules
Interface for data in spreadsheet format.
Creation of data migration objects on the basis of recorded transactions.
Charge-free for SAP customers and partners.
Working With LSMW:
Use TCODE LSMW
Objects of LSMW:
Project ID with max of 10 char to Name the data transfer project.
Subproject Used as further structuring attribute.
Object ID with max of 10 Characters, to name the Business object .
Project can have multiple sub projects and subprojects can have multiple objects.
Project documentation displays any documentation maintained for individual pop ups and processing steps
User Guide: Clicking on Enter leads to interactive user guide which displays the Project name, sub project name and object to be created.
Object type and import techniques:
Standard Batch / Direct input.
Batch Input Recording
   o If no standard programs available
   o To reduce number of target fields.
   o Only for fixed screen sequence.
BAPI
IDOC
o Settings and preparations needed for each project
Preparations for IDOC inbound processing:
Choose settings -> IDOC inbound processing in LSMW
Set up File port for file transfer, create port using WE21.
Additionally set up RFC port for submitting data packages directly to function module IDoc_Inbound_Asynchronous, without creating a file during data conversion.
Setup partner type (SAP recommended US) using WE44.
Maintain partner number using WE20.
Activate IDOC inbound processing.
Verify workflow customizing.
Steps in creating LSMW Project:
Maintain attributes choose the import method.
Maintain source structure/s with or without hierarchical relations. (Header, Detail)
Maintain source fields for the source structures. Possible field types C,N,X, date, amount and packed filed with decimal places.
Fields can be maintained individually or in table form or copy from other sources using upload from a text file
Maintain relationship between source and target structures.
Maintain Field mapping and conversion rules
For each Target field the following information is displayed:
o Field description
o Assigned source fields (if any)
o Rule type (fixed value, translation etc.)
o Coding.
o Some fields are preset by the system & are marked with Default setting.
Maintain Fixed values, translations, user defined routines Here reusable rules can be processed like assigning fixed values, translation definition etc.
Specify Files
o Legacy data location on PC / application server
o File for read data ( extension .lsm.read)
o File for converted data (extension .lsm.conv)
Assign Files to defined source structures
Read data Can process all the data or part of data by specifying from / to transaction numbers.
Display read data To verify the input data being read
Convert Data Data conversion happens here, if data conversion program is not up to date, it gets regenerated automatically.
Display converted data To verify the converted data
Import Data Based on the object type selected
Standard Batch input or Recording
o Generate Batch input session
o Run Batch input session
Standard Direct input session
o Direct input program or direct input transaction is called
BAPI / IDOC Technique:
IDOC creation
o Information packages from the converted data are stored on R/3 Database.
o system assigns a number to every IDOC.
o The file of converted data is deleted.
IDOC processing
o IDOCS created are posted to the corresponding application program.
o Application program checks data and posts in the application database.
Finally Transport LSMW Projects:
R/3 Transport system
o Extras ->Create change request
o Change request can be exported/imported using CTS
Export Project
o Select / Deselect part / entire project & export to another R/3 system
Import Project
o Exported mapping / rules can be imported through PC file
o Existing Project data gets overwritten
o Prevent overwriting by using
Import under different name
Presetting for Inbound IDOC processing not transportable.
Reward if useful.
regards
santhosh reddy

Modify existing data using LSMW IDoc method

Hi experts,
I am trying to transfer activity data from R/3 system to CRM using Idoc LSMW method.
It working fine that LSMW creates new activities in CRM system, & there is a check in the conversion code that if the activity we are trying to transfer exists in CRM system it will skip that transaction.
Now the requirement is that we don't want to skip, if the activity is already present in CRM system than it should modify the existing.
IDOC used :                       CRMXIF_ORDER_SAVE_M02
Msg type used:                 CRMXIF_ORDER_SAVE
Note:
LSMW will not create activities in the system; SXDA data transfer workbench will be used to process the data in CRM system. SXDA project has following two steps:
-     Merge files u2013 This step uses a custom function module to merge one or more than one files and creates a file which is   required for LSMW.
-     Convert the data u2013 This step uses LSMW as the conversion method
-     Load the data u2013 This step uses the IDoc object interface
Now the doubt is that if i remove the check than it will create an another activity with same activity no. or modify the existing one, or is there another way to modify the existing activity in CRM system?
Waiting for a qiuck response.
Thanks
d_marco

HI,
Thanks for your quick valuable response.
I have a doubt, we are transferring activities from R/3 system to CRM system, & these activities are maintained in R/3 application system in the form of text files
Now the question is if the text file contains 10 activities( transactions) with there header, partner & item details & from these 10 activities some are new & some are already present in CRM system, than will it be possible to create the new ones & update the existing ones withe single LSMW project run.
I think that we can put a check in the conversion code where transaction begins that if the particular activity( transaction) already present in CRM system than set a flag as "U" to update, if activities are new than set it as "I" to insert & than pass this flag in the conversion rule to the field "OBJECT_TASK" of IDOC structure
or
we need to maintain text files as for update or insert separately but not for mixed task of update/insert.
Will this update/insert process also work's if we are using a copy of standard IDOC type with some custom segments & custom fields.
Thanks
d_marco

Application logs for log handling in lsmw idoc method

Hi Abapers,
Im using LSMW IDOC method for data transfer from legacy to sap system.Now the requirement is to handle application logs for log handling i.e i have to make use of custom report to handle logs,can any one tell me what all steps to be done for this or if any one can share a link related to application logs would be greatly appreciated.
Thanks.
Edited by: saeed.abap on Dec 27, 2011 5:13 PM

Hi Saeed,
Please check with this fms
1) BAL_DSP_LOG_DISPLA
2) APPL_LOG_READ_DB
3) IDOC_GET_MESSAGE_ATTRIBUTE
There is a wiki [Error Log Lsmw|http://wiki.sdn.sap.com/wiki/display/Snippets/ErrorLogProgramforBAPIandIDocMethodin+LSMW] available.
Regards,
Madhu.
Edited by: madhurao123 on Dec 28, 2011 8:25 AM

How to upload different views of customer master data using LSMW-IDOC

I need to upload customer master data using LSMW Idoc method for my client. Now customer will have different views like main view, Sales data, Company code data, Partner function data etc. And except main data all other data can be multiple for each customer. We are going to upload data from tab delimited .TXT file. Should I propose different LSMW for upload different views for the customer from different .TXT files? or we can upload all the customer related data (like main view data and partner function data )from a single .TXT file. Kindly suggest which one in convenient and how we can prepare the data file in both cases.

convinient is the method that you can handle.
but as the guy who loads the data you have to load the data like they are available, like it is convinient for others to prepare the data.
In general there is no problem to use an IDOC method to load a customer master with multiple comany codes and several sales orgs in one shot.
the data can be in one source file, but need then to be maintained in a certain way
Example1: all data in 1 structure
GD1 - CC1 - SO1
GD1 - CC2 - SO2
GD1 - CC2 - SO3
in this case the GD (general data) is redundand in each line which has different Company code data or different Sales Org data
Example2: all data in 3 sturcures but one file
GD1
.CC1
.CC2
..SO1
..SO2
..SO3
Example3: data delivered in 3 files - you join the files in LSMW, they must have a common identifier like the old customer number in the beginning of each file
FILE General data:
GD1
GD2
GD3
file Compamy code data:
CC1
CC2
CC3
file Sales org data:
SO1
SO2
SO3
LSMW is flexible and can handle each of this scenarios, are you flexible too?

LSMW using IDOC method for scheduling agreement - MM

I am using LSMW IDOC method to create Scheduling agreement. i am using message type : PURSAG_CREATE. I have completed the field mapping and when i tried to process the idoc i am getting the following error.
No instance of object type PurchSchedAgreement has been created. External reference: # 1
There are no clue why this error is popping up.
please let me know if anyone faced similar issues.

try entering the values in WE19 and do the posting for teting purpose, make sure you are passing all the values.

LSMW using IDOC method for scheduling agreement

I am using LSMW IDOC method to create Scheduling agreement. i am using message type : PURSAG_CREATE. I have completed the field mapping and when i tried to process the idoc i am getting the following error.
No instance of object type PurchSchedAgreement has been created. External reference: # 1
There are no clue why this error is popping up.
please let me know if anyone faced similar issues.

Are you using external number range for scheduling agreement, then you have to pass the SA number too if not then check with your MM functional consultant to change the number range from external to internal provided it is agreed by your customer

Vendor Address is not updating in ADRC table by LSMW IDOC method

Hi,
I'm updating Vendor address data by LSMW IDoc method
for this i'm using ADRMAS as msg type and ADRMAS02 as Idoc type.
In partner profiles Process code given as BAPI for this.
i maintained entry in TSADOBJ table LFA1 as OBJTYPE,1 as ADDR TYPE,0001 as context,LFA1 as TABLENAME,ADRNR as FIELDNAME, ADRC as TABLE PERS, ADDRNUMBER as FIELD PERS
Idoc generating sucessfully.
But data is not updating in database.
i think the problem in TSADOBJ config.
Please give exact configuration which can update vendor data.
Thanks in advance

be open minded. SAP gives several import methods to load vendors. one of them is per IDOC.
But the vendor master IDOC does not automatically create the adress master.
And even more important, if you migrate data from one SAP system to another, the IDOC method is more straight forward than the batch input, because you can send the IDOCs from legacy system to new system, you will then have a 1:1 relation of the structure in LSMW and you can create vendor masters by knowing the new vendor number from an internal number range already in LSMW, long before you actually post the vendor. With batch input you can either post with numbers from external number range, or you just dont know the new number already in LSMW.
And you dont need to download the data to Excel. And further, the LFA1 adress data has less information than the ADRC adress data.

Issues in using LSMW IDOC method for Article Hierarchy

Similar Messages

Maybe you are looking for