LSMW-IDOCS

Hi All,
I am doing conversion of Business Partner and contact person relationship. We need to do this with LSMW using IDOCS. I am able to execute the 13th step i.e. Start Idoc generation. when i come to next step i.e. Start Idoc processing, i am getting errors(status 51) like :
1. Error status 'A' calling validation service,
2. Validation error occurred: Module CRM_BUPA_REL_VAL , BDoc type BUPA_REL
3.  Relationship Between Partner 0005000310 and 0005000210 Does Not Exist
4.  BP relationship 5000310 46D029A0C5CC012F000000000A321064 5000210 4689643
Please let me know how to rectify those errors :
I followed the steps like :
LSMW - > settings -> Idoc inbound processing
there i have given file port, partner type(LS) and partner no. Also in maintain partner no. i have given message type and process code(APLI).
Do i need to maintain some other settings ?
Please help me to solve this problem. I need it urgently.
Thanks & Regards,
Samm

Hi
The Error is not bcoz of settings -> Idoc inbound processing.
The Error 51 comes when there are errors in the Data integrity. So u better consult the Functional cosultant to find out the Reason.
You can test this IDOC using WE19 (test tool) where you can correct the errors and post the IDOC.
<b>reward if Helpful.</b>

Similar Messages

  • 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.

  • 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?

  • 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

  • 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.

  • Lsmw Idoc  ......

    Hi friends,
      I am working on LSMW Idoc ....after uploading the data ...The idoc got created with 53 staus successfully .
      after succesfull creation Of Idoc , when i check the data in the database  its not going to updating the data base.
    is there any standard program  for updaing the data in the DB.
    can any body help me......
    Regards,
    Jayan.

    the status 53 will set only after the data got updated sucessfully in the data base. May be you are checking in the wrong table.
    let mek now the IDOC name and table name that ur refering.

  • PO Creation, with same Legacy Item No : LSMW-IDOC

    Dear all,
    I am creatin PO's using LSMW IDOC Method - BUS2012.
    I could create PO's . But issue is , but issue is PO's are created with Item No in Sequence( 10,20 etc).
    We need to create PO with same Item No as in Input File.
    Eg: If Item No are 40 , 50 in input file. PO is created with Item 10 and 20.
    I need to create them with 40 & 50.
    Is there any option to achieve this.
    Thanks
    Praveen

    Hi,
    If you are using the BAPI method in the LSMW,
    Set the parameter ITEM_INTVL = 'X' which is in the parameter POHEADERX.
    This should allow external PO line item numbering.
    Please check.
    Thanks
    Naren

  • Document type not defined in lsmw idoc method

    hello  iam posting Open AR Line Items for contract account using message type
    CTRACDOCUMENT_CREATE  using lsmw idoc method .iam getting error as Document type not defined but actually when iam creating document manually item is created with out any error that means it is defined and my functional consultant is also saying he defined document type.can some body explain me what is the  problem.
    Regards
    priya

    Check OMW9, here document type is defined for the transaction MIRO..
    Go to OMW9, click in the Document Type.
    Then double click on MIRO.
    Also check the sap notes which is referred in the similar thread Document type not defined f5814

  • Maintain Structure Relations - LSMW - IDOC method

    Hi,
    Trying to use LSMW Idoc method to upload BP masters.
    Have maintained the ports, partner types, message types etc. When I reach the "Maintain structure relationship" step, I have a very big tree structure under EDI_DC40 when am trying to maintain the structure relationship between the source and the target in LSMW idoc method.
    Do I need to maintain my relationship at all the levels of the tree structure under EDI_DC40 or can I choose the nodes that are relevant and maintain a relationship only for them?
    Is there a short cut or a way where I can maintain relationship for each node under the target strucute EDI_DC40.
    Appreciate your inputs.
    SK

    Hi SK,
    There is no need to maintain EDI_DC40.
    In 'Maintain Structure Relations' step, you just need to create Relationship for the structure you want the information be uploaded in the BP. Mapping of the fields in the structure to your upload file's values will be done in next step. Hope the above helps

  • 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.

  • Vk11 pricing conditions for LSMW  IDOC method...

    Hi Guru's,
    I am working on LSMW Idoc method. For Pricng conditions
    i am using Message type  'COND_A'  and basic type 'COND_A04'  .
    when we execute 14th step Idoc generation. I am Facing some problem like its displaying information message
           ' Partner type does not exist with the name ,'TYPE'.
      like this iam facing some problem.
    I already created partner profile in we20  clearly..
    This is the different requireent ,i never faced this problem earlier.
    Can any body help me in this regard.
    Regards
    Jayan Jalla,

    Hi,
    Activate the indbound settings in the LSMW by pressing the button
    'Activate Idoc Inbound Processing'.
    Regards,
    Shan

  • 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

  • LSMW - Idoc method  - Urgent ??

    Hi,
    What is "Allow structure assignment to EDIDC40" ? on the object attributes maintenance screen (step 1) in the LSMW Idoc inbound processing.
    we are using CRM 5.0 to test the BP creation with the help of IDOC methods.
    any inputs or step by step IDOC BP creation guide/document will be highly appreciated and rewarded.
    you can mail the IDOC step by step doc to [email protected]
    Thanks
    SK

    Hello,
    normally the control structure EDIDC40 is filled automatically by LSMW. In some special cases you may want to defined your own mapping rules. In these cases you can set the flag and will then see EDIDC40 in the step where you do the fieldmapping.
    I would suggest not to set the flag unless you really urgently need to adopt rules
    for the IDoc control structure.
    Regards, Katja

  • LSMW IDOC method to upload material master

    hi,
    i want to upload the Material Master using LSMW Idoc Method.  I have not worked in LSMW IDOC MEthod previously
    can anyone help me.. please..
    ThankS IN ADVANCE
    GUHAPRIYAN

    hi Guhapriyan,
          In LSMW there are four method to migrate data.Idoc is one such method.You need to define three thing message type,
    Basic type,enhancement and a check box for enable structure for EDI.Once you complete this ,it ready to transfer.Before that you need to go through 12 basic steps.
    Hope this will help you.
    Regards,
    Albert

  • LSMW : Idoc method , Business Activities custom fields data upload

    Hi guys
    I am uploading Business activities using LSMW IDOC method and below message and idoc type
    Message type CRMXIF_ORDER_SAVE_M
    Basic idoc type : CRMXIF_ORDER_SAVE_M02
    Using EEWB I added few fields to business activities , along with the standard fields I want to upload the customer fields also .
    I tried to Extend the Basic idoc type CRMXIF_ORDER_SAVE_M02, but it was not allowing me to Extend ( since it is generated basic idoc type ) I tried the other Basic idoc types for Business activities , I got the same problem
    the basic idoc type contains only two Segments
    E101CRMXIF_CUSTOMER_H_X (parent)
    E101CRMXIF_CUSTOMER_H (child)
    with out my custom fields
    pls help how can i add my custom fields ( added by eewb) to the basic idoc type
    for uploading custom fields
    thanks in advance
    Warm regards
    Rajasekhar

    You are going to need to create an enhancement of the standard IDOC type in order to get your custom fields to show.  I can't remember the exact procedure, but you will need to create a Z-type based on the existing type in the system.  When you generate the z-type the fields will be filled in.
    Look at the following thread and it will give the basic steps
    How to delete Extention
    Good luck,
    Stephen

  • 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.

Maybe you are looking for