Data Transfer thru LSMW

Hi Experts...
I would like to view the data which I have transfered to SAP system using LSMW.  The process run in background.  But how to check the data.
If anyone can also help me to see table thru SAP or using SQL query in Oracle.
Thanks,
Praveen.
Note: If this is not the right forum then pls guide to the concerned.

Hi tutika,
Once the data is successfully transfered to Target SAP system using LSMW, You can chech the status report of batch you have given for upload.It shows how much recors have been successfuly tranfered. Also you can see log details if any eror is there.
When u want to see actual recored/ data which has been tranfered in Target System , U can directly run transactions , Report or through SE 16 to confirm the data transfered.

Similar Messages

  • Data transfer thru lsmw via bapi

    how to perform data transfer thru lsmw via bapi.
    Thanks.
    Regards
    Rama

    HI
    BAPI stands for Business API(Application Program Interface).
    A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
    You can make your function module remotely enabled in attributes of Function module but
    A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
    BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
    The following standardized BAPIs are provided:
    Reading instances of SAP business objects
    GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
    The BAPI GetList() is a class method.
    GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
    The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
    Create( ) and CreateFromData! ( )
    The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
    Change( )
    The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
    Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
    The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
    Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
    Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
    BAPI-step by step
    http://www.sapgenie.com/abap/bapi/example.htm
    list of all bapis
    http://www.planetsap.com/LIST_ALL_BAPIs.htm
    for BAPI's
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sappoint.com/abap/bapiprg.pdf
    http://www.sappoint.com/abap/bapiactx.pdf
    http://www.sappoint.com/abap/bapilst.pdf
    http://www.sappoint.com/abap/bapiexer.pdf
    http://service.sap.com/ale
    http://service.sap.com/bapi
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    http://www.planetsap.com/Bapi_main_page.htm
    http://www.topxml.com/sap/sap_idoc_xml.asp
    http://www.sapdevelopment.co.uk/
    http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
    Also refer to the following links..
    www.sappoint.com/abap/bapiintro.pdf
    www.sap-img.com/bapi.htm
    www.sap-img.com/abap/bapi-conventions.htm
    www.planetsap.com/Bapi_main_page.htm
    www.sapgenie.com/abap/bapi/index.htm
    Checkout !!
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    u can check the below the material also
    Example Code
    U need to give the step_nr, item_nr, cond_count and cond_type so the correct conditon will be updated. If no condition exists for the given parameters, a new condition will be created.
    U can find these parameters for a particular condition type in table KONV.
    *& Form saveTransactionJOCR
    text
    --> p1 text
    <-- p2 text
    FORM saveTransactionJOCR .
    data: salesdocument like BAPIVBELN-VBELN,
    order_header_inx like bapisdh1x,
    order_header_in like bapisdh1,
    return type standard table of bapiret2 with header line,
    conditions_in type standard table of bapicond with header line,
    conditions_inx type standard table of bapicondx with header line,
    logic_switch like BAPISDLS,
    step_nr like conditions_in-cond_st_no,
    item_nr like conditions_in-itm_number,
    cond_count like conditions_in-cond_count,
    cond_type like conditions_in-cond_type.
    salesdocument = wa_order_information-VBELN.
    LOGIC_SWITCH-COND_HANDL = 'X'.
    order_header_inx-updateflag = 'U'.
    conditions
    clear conditions_in[].
    clear conditions_inx[].
    clear: step_nr,
    item_nr,
    cond_count,
    cond_type.
    step_nr = '710'.
    item_nr = '000000'.
    cond_count = '01'.
    cond_type = 'ZCP2'.
    CONDITIONS_IN-ITM_NUMBER = item_nr.
    conditions_in-cond_st_no = step_nr.
    CONDITIONS_IN-COND_COUNT = cond_count.
    CONDITIONS_IN-COND_TYPE = cond_type.
    CONDITIONS_IN-COND_VALUE = 666.
    CONDITIONS_IN-CURRENCY = 'EUR'.
    append conditions_in.
    CONDITIONS_INX-ITM_NUMBER = item_nr.
    conditions_inx-cond_st_no = step_nr.
    CONDITIONS_INX-COND_COUNT = cond_count.
    CONDITIONS_INX-COND_TYPE = cond_type.
    CONDITIONS_INX-UPDATEFLAG = 'U'.
    CONDITIONS_INX-COND_VALUE = 'X'.
    CONDITIONS_INX-CURRENCY = 'X'.
    append conditions_inx.
    CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
    SALESDOCUMENT = salesdocument
    ORDER_HEADER_IN = order_header_in
    ORDER_HEADER_INX = order_header_inx
    LOGIC_SWITCH = logic_switch
    TABLES
    RETURN = return
    CONDITIONS_IN = conditions_in
    CONDITIONS_INX = conditions_inx
    if return-type ne 'E'.
    commit work and wait.
    endif.
    ENDFORM. " saveTransactionJOCR
    Bdc to Bapi
    The steps to be followed are :
    1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
    [for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]
    2. Create a Z program and call the BAPi (same as a Funtion module call).
    2. Now, if you see this BAPi, it has
    -> Importing structures.
    eg: SALESDOCUMENT: this will take the Sales order header data as input.
    -> Tables parameters:
    eg: ORDER_ITEM_IN: this will take the line item data as input.
    Note :
    Only specify fields that should be changed
    Select these fields by entering an X in the checkboxes
    Enter a U in the UPDATEFLAG field
    Always specify key fields when changing the data, including in the checkboxes
    The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
    Maintain quantities and dates in the schedule line data
    Possible UPDATEFLAGS:
    U = change
    D = delete
    I = add
    Example
    1. Delete the whole order
    2. Delete order items
    3. Change the order
    4. Change the configuration
    Notes
    1. Minimum entry:
    You must enter the order number in the SALESDOCUMENT structure.
    You must always enter key fields for changes.
    You must always specify the update indicator in the ORDER_HEADER_INX.
    2. Commit control:
    The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
    For further details... refer to the Function Module documentation for the BAPi.
    Bapi to VB(Visual Basic)
    Long back I had used the following flow structure to acheive the same.
    Report -> SM59 RFC destination -> COM4ABAP -> VB.exe
    my report uses the rfc destination to create a COM session with com4abap. com4abap calls the vb.exe and manages the flow of data between sap and vb exe.
    You need to have com4abap.exe
    If com4abap is installed you will find it in sapgui installatin directory , C:\Program Files\SAPpc\sapgui\RFCSDK\com4abap.
    else refer OSS note 419822 for installation of com4abap
    after making the settings in com4abap to point to the vb program and setting up rfc destination in sm59 to point to com4abap session , you can use the following function modules to call the vb code.
    for setting up com4abap and rfc destination please refer to the documentation for com4abap.
    Invoke NEW DCOM session
    call function 'BEGIN_COM_SESSION'
    exporting
    service_dest = service_dest "(this will be a RFC destination created in SM59)
    importing
    worker_dest = worker_dest
    exceptions
    connect_to_dcom_service_failed = 1
    connect_to_dcom_worker_failed = 2
    others = 3.
    call function 'create_com_instance' destination worker_dest
    exporting
    clsid = g_c_clsid
    typelib = g_c_typelib
    importing
    instid = g_f_oid
    exceptions
    communication_failure = 1 message g_f_msg
    system_failure = 2 message g_f_msg
    invalid_instance_id = 3
    others = 4.
    call function 'com_invoke' destination worker_dest
    exporting
    %instid = g_f_oid
    %method = 'UpdatePDF'
    sntemp = g_v_const_filent
    snsysid = sy-sysid
    snflag = 'N'
    tables
    rssaptable = g_t_pdfdetail1
    %return = g_t_pdfdetail1 "t_test
    exceptions
    communication_failure = 1 message g_f_msg
    system_failure = 2 message g_f_msg
    invalid_instance_id = 3
    others = 4.
    then close the com session , using
    FM delete_com_instance
    FM END_COM_SESSION
    http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/5e114a4a1611d1894c0000e829fbbd/frameset.htm
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/saphelp_46c/helpdata/en/9b/417f07ee2211d1ad14080009b0fb56/frameset.htm
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    http://www.sapgenie.com/abap/bapi/example.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
    http://techrepublic.com.com/5100-6329-1051160.html#
    http://www.sap-img.com/bapi.htm
    http://www.sap-img.com/abap/bapi-conventions.htm
    http://www.sappoint.com/abap/bapiintro.pdf
    BAPI - BAPIs (Business Application Programming Interfaces) are the standard SAP interfaces. They play an important role in the technical integration and in the exchange of business data between SAP components, and between SAP and non-SAP components. BAPIs enable you to integrate these components and are therefore an important part of developing integration scenarios where multiple components are connected to each other, either on a local network or on the Internet.
    BAPIs allow integration at the business level, not the technical level. This provides for greater stability of the linkage and independence from the underlying communication technology.
    LSMW- No ABAP effort are required for the SAP data migration. However, effort are required to map the data into the structure according to the pre-determined format as specified by the pre-written ABAP upload program of the LSMW.
    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.
    More and more medium-sized firms are implementing SAP solutions, and many of them have their legacy data in desktop programs. In this case, the data is exported in a format that can be read by PC spreadsheet systems. As a result, the data transfer is mere child's play: Simply enter the field names in the first line of the table, and the LSM Workbench's import routine automatically generates the input file for your conversion program.
    The LSM Workbench lets you check the data for migration against the current settings of your customizing. The check is performed after the data migration, but before the update in your database.
    So although it was designed for uploading of legacy data it is not restricted to this use.
    We use it for mass changes, i.e. uploading new/replacement data and it is great, but there are limits on its functionality, depending on the complexity of the transaction you are trying to replicate.
    The SAP transaction code is 'LSMW' for SAP version 4.6x.
    Check your procedure using this Links.
    BAPI with LSMW
    http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI
    For document on using BAPI with LSMW, I suggest you to visit:
    http://www.****************/Tutorials/LSMW/BAPIinLSMW/BL1.htm
    What are the methods to migrate data from a legacy system to SAP?
    LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
    Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
    The LSMW comprises the following main steps:
    Read data (legacy data in spreadsheet tables and/or sequential files).
    Convert data (from the source into the target format).
    Import data (to the database used by the R/3 application.
    But, before these steps, you need to perform following steps :
    Define source structure : structure of data in the source file.
    Define target structure : structure of SAP that receives data.
    Field mapping: Mapping between the source and target structure with conversions, if any.
    Specify file: location of the source file
    Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
    How is the decision made which method should be followed? What is the procedure followed for this analysis?
    All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
    SO Bottom line is make choice of these methods based of real time requirements.
    These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
    Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use which
    You can create lsmw for data migration as follows (using session method):
    Example for xk01 (create vendor)
    Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
    1. TCode : LSMW.
    2. Enter Project name, sub project name and object name.
    Execute.
    3. Maintain object attributes.
    Execute
    select Batch Input recording
    goto->Recording overview
    create
    recording name.
    enter transaction code.
    start recording
    do recording as per ur choice.
    save + back.
    enter recording name in lsmw screen.
    save + back
    Now there will be 14 steps.
    2. MAINTAIN SOURCE STRUCTURES.
    Here you have to enter the name of internal table.
    display change
    create
    save + back
    3. MAINTAIN SOURCE FIELDS.
    display change
    select structure
    source_fields->copy fields.
    a dialogue window will come .
    select -> from data file
    apply source fields
    enter No. of fields
    length of fields
    attach file
    save + back
    4. MAINTAIN STRUCTURE RELATIONS
    display change
    save + back
    5. MAINTAN FIELD MAPPING & CONVERSION RULE
    display change
    click on source field, select exact field from structue and enter
    repeat these steps for all fields.
    save+back
    6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
    execute
    save + back
    7. SPECIFY FILES.
    display change
    click on legacy data
    attah flat file
    give description
    select tabulatore
    enter
    save + back
    8. ASSIGN FILE
    execute
    display change
    save + back
    9. IMPORT DATA.
    execute
    display change
    save + back
    10. DISPLAY IMPORTED DATA
    enter ok, it willl show records only.
    back
    11. CONVERT DATA
    execute
    display change
    save + back
    12. DISPLAY CONVERTED DATA
    execute
    display change
    save + back
    13. CREATE BATCH INPUT SESSION
    tick keep batch input folder
    F8
    back
    14. RUN BATCH INPUT SESSION.
    sm35 will come
    Object name will be shown here
    select object & process
    Regards
    Pavan

  • Different methods of data transfer in LSMW?v

    Different methods of data transfer in LSMW?v
    could u plz explain clearly

    please visit the following link
    https://wiki.sdn.sap.com/wiki/display/HOME/LSMW                                        
    http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc                                        
    There are four method!
    1-Direct Input Method
    2-BDC
    3-BAPI
    4-IDOC
    Please reward me point as way of thanks

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

  • Employees data uploaded thru lsmw not visible in ppome

    hi experts,
    i have uploaded some HR master data thru lsmw using tcode pa40.
    i am getting all the data in master tables pa0000,pa0001,pa0002.
    for example
    100 is a person with position manager(e.g. 5000234).
    i am getting his details in all the tables .and in pa 30 also when i type pernr i am getting all the informations.
    buit when in go in ppome to see the details of position organisational structure .
    under manager and that position no his name is not assigned .
    what may be the problem ????
    it's very urgent .... i am in production stage. pl. hep immediately
    regards,
    mani

    Hi Mani,
    Sorry yaar i dont have enough knowledge to discuss/tell abt spro, anyway go through this hope u can .
    More or less, the SPRO transaction is just a collection of table maintenance programs. So in order to see the changes to the tables, the tables must have the "log changes" checkbox assigned to the table itself. Some programs in spro may provide there own "changes" functionality.
    Here is the help on "Log Data Changes".
    Log data changes
    The logging flag defines whether changes to the data records of a table should be logged. If logging is activated, every change (with UPDATE, DELETE) to an existing data record by a user or an application program is recorded in a log table in the database.
    Note: Activating logging slows down accesses that change the table. First of all, a record must be written in the log table for each change. Secondly, many users access this log table in parallel. This could cause lock situations even though the users are working with different application tables.
    Dependencies
    Logging only takes place if parameter rec/client in the system profile is set correctly. Setting the flag on its own does not cause the table changes to be logged.
    The existing logs can be displayed with Transaction Table history (SCU3).
    As the help has described, use transaction SCU3 to view the change logs regarding customizing tables.
    Thanks
    NAveen khan

  • Employee data uploaded thru lsmw not visible in ppome

    hi experts,
    i have uploaded some HR master data thru lsmw using tcode pa40.
    i am getting all the data in master tables pa0000,pa0001,pa0002.
    for example
    100 is a person with position manager(e.g. 5000234).
    i am getting his details in all the tables .and in pa 30 also when i type pernr i am getting all the informations.
    buit when in go in ppome to see the details of position organisational structure .
    under manager and that position no his name is not assigned .
    what may be the problem ????
    it's very urgent .... i am in production stage. pl. hep immediately
    regards,
    mani

    hello is there anyone to help me

  • Error in asset data migration thru LSMW

    Hi u all,
    i have an issue while running an lsmw for asset data loads here, when i did it in foreground it saves the asset but when i run it in background its erring out
    i am doin it thru as91 whichis legacy transfers the error is
    Field RALT_DYNP_STRUC-ANBTR02(7) is not an input field     AS91     1     SAPLALTD     1100     14     S     00     347
    Field RALT_DYNP_STRUC-ANBTR03(7) is not an input field     AS91     1     SAPLALTD     1100     14     S     00     347
    this ANBTR02(7) n ANBTR03(7) are the *** spl dep fields for TAX and AMT in the takeover values tab,where we were giving the values of spl dep (Bonus value which is taken off in the acquisition yr)
    all is goin good in foreground but its giving the error whichi pasted above saying ..is not an input field, when i did it in background not able to figure out...
    Any help would be really grateful and appreciated......Thanka a lot in advance.

    Hi Nathan,
    as i mentioned earlier, it goes smooth when it is done manually or lsmw foreground, and answering to ur ques'n yes the fields are open. i am getting the error when i do it in batch input....
    Thanks ya
    Jay

  • Help reqd on MM data uploading thru LSMW by view steps...

    Hi all....
    Pls understand my requirement and post ur replies...i dont need the basic LSMW learning steps for MM,Vendor etc.,like that...
    My problem is...im want to upload my material master datas by steps like 1st i want to uplaod the basic views 1&2 for all the material types in one shot...
    next thing i want to load the other views like purchasing sales mrp plant qm accounting etc., in single shot......like screen to be extended formats....im mm01 or by mm02...
    when i did....no problem i've faced upto MRP loading...but the next view like plan,QM,accounting is not coming when recording in RUN batch input session..it says..."the material has been already extended and no input was given for this screen"....
    Hope u understand,my problem....
    if u have answers...pls post me on urgent basis.....
    thanks...
    sankar

    verify if all the materials have all the views you require.
    regards,
    srinivas
    <b>*reward for useful answers*</b>

  • SAP Retail : Article Master Data Transfer using LSMW/ARTMAS05: EAN Error

    Hi Bjorn Panter,
    I want to thank you for providing very informative articles on the Master Data of ERP Retail.
    We are currently loading articles to SAP from legacy and use your articles on ERP Retail as part of our knowledge warehouse.
    We have encountered an error which has stumped our conversion.
    We are getting an M3 535 error stating that "First specify the main EAN for the unit EA".  We are using LSMW (IDOC Method, Basic Type ARTMAS05).
    Our MARM segments have generic and variants.  The UPC and UPC category (set to UC) are filled for the variants and blank in the segment containing the generic.
    Our MEAN segments contain variants only with the UPC and UPC category (set to UC) filled.
    Our UC EAN category is configured with a blank check digit algorithm and a number range of 12 digits.  We are loading our variants with EANs that are 12 digits.
    When debugged IDOC_INPUT_ARTMAS, I noticed that :
    In routine  MARM_UEBERGEBEN (in function module BAPI_MATERIAL_MAINTAINDATA_RT), this code clears our MARMX indicators :
       LOOP AT UNITSOFMEASURE.
        ART_DATA_EXISTS = 'X'.    "JH/05.01.00/4.6C Entkopplung der MALG
        IF UNITSOFMEASURE-FUNCTION NE C_MSGFN_D.   ->>>> this checks if our function code is 003 (which is a delete).
    *     TMFIELDRES aufbauen
          CLEAR UNITSOFMEASUREX.                   ->>>> Since we are doing a create, it clears the indicators in unitsofmeasureX
    To bypass this clear, I debugged the program and overlayed the indicators and marked UPC and UPC category as 'X'.  This worked and we were able to post our IDOC successfully... THe UPCs showed in the MARM and MEAN tables.
    However, knowing that there are a lot of Retail companies loading articles into their SAP system, it would seem odd that no one has reported this as a bug or no one has posted this issue in SDN.  I could not find any OSS note related to this issue either.
    Can you please help us figure out what is wrong ? Have you encountered this error in the past ?  Is there something in config that we should check ?  Should we look at fields in our segments ?
    Any help from you would be greatly appreciated.
    Thanks,
    Sarah

    Dear Sarah,
    please open an OSS customer message.
    Put in a valid IDOC ARTMAS number with this error and open your system.
    I guess either it is a bug in IODC structure or you found a bug in software.
    My colleages will take care.
    Regards
    Björn

  • Creat Job for LSMW (periodical data transfer)- idoc BLAORD

    Hi,
    We are trying to create job for LSMW (thru frame program for periodic data transfer) for idoc BLAORD (Purchasing contract)
    When I am running the job that I created, the job is cancelled and the error is:
    "Upload from front-end is not possible in batch mode.
    Message no. /SAPDMC/LSMW_OBJ_070 020"
    How can I correct that? so I will be able to run a job (the job mast run background?)
    Thanks,
    Tal Sasson

    Hello,
    I was also receiving the same message /SAPDMC/LSMW_OBJ_070 020 even though I specified in /SAPDMC/SAP_LSMW_INTERFACE the server path. The problem was that in LSMW->Specify Files you have to delete the definition of front-end files and define application server files.
    That Flag File (Path and Name) (field /SAPDMC/LSOINP-FILENAME in program /SAPDMC/SAP_LSMW_INTERFACE) is kind of useless since it is ignored anyway and files defined in LSMW object are imported and they have to be read anyway if you use more than one file.
    Regards,
    Peter

  • How to upload Purchase Order Data thru LSMW

    Hi All,
    I need to upload Purchase order data thru LSMW. LSMW Provides standard object method which does not suit for split valuation. But in the client place split valuation is maintained. Is there any other of option of uploading the data.
    Regards,
    Srivatsan

    Dear Srivatsan
    For Upload Purchase order Data through LSMW
    Business object BUS2012 - Purchase Order
    Basic type PORDCR04
    Message type PORDCR
    Method CREATEFROMDATA
    With regards
    B.Ravindranath

  • Advantages of using BAPI over LSMW for data transfer

    Hellow,
    Can anybody please give an input for advantages of using BAPIs in data transfer compare to LSMW. If we use BAPI for data transfer of master and transaction data how it is more usefull compare to LSMWs developed.
    Thanks in advance
    Raghav

    Hi Raghavendra,
    Refer the links..may help.....
    [http://www.*******************/search?q=BAPIandLSMW+comparision]
    [http://www.*******************/search?q=bapi]
    Regards,
    Mdi.Deeba

  • Upload data thru LSMW -WBS with 3 levels

    Hi PS Experts,
    My situation is like I have to upload data thru LSMW for all Levels!  As I m doing for only L3 WBS with PD it is going upto 14 steps and executing.But for Level 2 and Level 3 it is not executing. In the Step "Read Data" it is showing blank.
    Can v upload these multilevel data thru LSMW? or how is like?
    Thanks in advance,
    Sanju..

    Hi Virendra,
    I think that your solution is very good for my purpose.
    But in my implementation there is no way to insert a new element in an existing WBS, I can only edit attributes for an element already created, for example, in cj02.
    I checked all the menus but i didn't find any useful command.
    Could you send me a screenshot of the keypoint in which you can create the element different from the first level?
    Thank you very much.
    Giorgio

  • LSMW - Periodic Data Transfer - wildcards in filename

    Hello,
    I have the following problem: The file, which has to be periodically read in is specifed for identification date + time e.g. DATAFILE_200820071250.txt
    In the step 'Specifiy Files ' I entered:
    serverDATAFILE_*.txt.
    In the step ' Frame Program for Periodic Data Transfer' I entered in 'Value for Wildcard (*)' the following interval: 0000000000000000 - 99999999999999999.
    During execution now (as a job with variant or directly) I receive always the same error message (/SAPDMC/LSMW524): "Specified values for wildcard (*) have not been defined" .
    How I have to define the filename with wildcard (*) of a file which is peridically read in by LSMW?????
    Thanks for your help!
    Atentamente le saluda / Mit freundlichen Grüssen / Yours sincerely
    Nicole Miosga

    Hi Nicole,
    As of my knowledge the way u have assigned the file name is incorrect,
    just check it once, and in SPECIFY FILES  there is values for wildcard ,
    i want to know what u did here.
    Thanks
    Naveen khan

  • MR21 Data upload using LSMW

    Hi,
    Please help me in creating an LSMW for MR21 Transaction. I have a flat file, But i'm not sure about how this can be acheived thru Direct Input. Please also educate me on the other techniques of acheiving this Data Transfer.
    Thanks & Regards,
    Sai

    Hi Thanks.
    I have used the same IDoc. But the following fields are not in the IDOC structure .
    2. RQPAS-QUALITAT - Qualitative Characteristic
    3. PLMK-MKVERSION - Version Number of the Master Inspection Characteristic
    4. PLMK-PMTVERSION - Version Number of the Inspection Method
    I found that MKVersions are maintaining in the MIC (Master of Inspection Characteristic) , Once the MIC number is given in the inpsection plan , It is populating the version automatically.
    SInce IDOC has qunatitive indicator, If value is populated to qunatitative indicator it is checking the quantative othwise if empty it is populating qualitative .
    Thanks,
    Karunanidhi

Maybe you are looking for