ECC 6.0 upgrade BDC, LSMW, IDOC checking stratergy

Hi Experts,
We have developed lot of LSMW involving BDC recordings, programs, IDOC and BAPI to load the data. We are now upgrading to ECC 6.0 and hence like to know the approach or check list whcih will help to check these objects and find out the differences or corrections to be done before moving to ECC 6.0 box.
can u please let me know a check list or any utility program that will help to identify the difference or issues? thx for response.
Ganesh

The best way to find out if everything works is to upgrade a test system and check your process. There's no tool available. LSMW itself didn't change but there may be changes in function modules you use.
Markus

Similar Messages

  • Bdc & Lsmw upgrade issues

    Can anyone please let me know the issues faced while upgrading bdc & Lsmw from lower version to higher version.

    Hi
    The following problems can be encountered
    1. Absence of certian screen fields.... usually the custom fields which are in lower version and not transported to higher version.
    2. Screen flow might change. Thus make sure that screen flow defined in BDC is same as the actual screen flow in the transaction.
    Regards,
    Vara

  • Screens not working in ECC 6 after upgradation from 4.6c.

    Hi,
    The custom developed screens which where developed in 4.6c version is not working properly in ECC 6 after upgradation.Do i have to make any more changes for this .? If anyone have an idea please help me in this issue.The custom developed things are an extended functionality we have done to r/3.
    Regards,
    jinesh kumar c.

    Hi,
    Check the Transportatation Logs in STMS for the programs/screens and check whether they are successfully tranported or not?
    Because some times we get Dynpro errors for transportation of the screens.
    Reward if useful.
    regards,
    Anji

  • ECC-600 EHP4 upgrade with VIRSAHR 520 700 - PREP_EXTENSION/ADDON_QCALC

    Hi
    We are getting following error at phase PREP_EXTENSION/ADDON_QCALC in the ECC 6.0 upgrade:
    3 ETN256 You want to install the following add-on components:
    3 ETN248 Component: "VIRSAHR" rel. "520_700", Support Package
    level: "0" (component type "A")
    3 ETN248 Component: "VIRSANH" rel. "520_700", Support Package
    level: "0" (component type "A")
    2 ETN085X"2. Adding Add-on Installation Queue" " " " " " "
    3 ETN262 Calculating queue part for add-on "VIRSAHR" rel. "520_700"
    3 ETN490 Use the Add-On installation package "SAPK-523EXINVIRSAHR"
    (type &4"AOX") for Add-On &2"VIRSAHR" rel.&3"520_700"
    3 ETN245 The following import prerequisites of OCS Package "SAPK-
    523EXINVIRSAHR" have not been met:
    3 ETN264 In the (alternatively) Requirement set "01":
    3WETN491 Required software component "SAP_HR" rel."600" is not installed2WETN543 OCS package "SAPK-523EXINVIRSAHR" does not match the current
    software component vector
    1 ETN214X."**************************************************"
    We have alreacy checked note 1002147, which clearly states that we have to include SAPK-523EXINVIRSAHR in the upgrade. SAP_HR is part of the upgrade.
    We have included SAP_HR and other Support Package as per the queue generated by Solution Manager, but we did not include VIRSAHR & VIRSANH Packages until we got to this phase. We then included these support packages in eps\in directory, but we are now getting this error now.
    Any ideas?
    Regards
    Chandu

    Hi
    This is what the solution provided by SAP Support:
    Quote:
    we have finally found the problem, it's a bug in the package upload
    functionality used by the upgrade. The consequence of this bug is that
    Support Packages whose EPS files (.PAT files) have a certain string in
    the name, namely the string 0000000 after the _ and before .PAT
    extension, are not properly uploaded to the ABAP system and hence are
    not visible or known to the upgrade.
    This bug will be fixed in the next upgrade tool fix, but in the meantimeyou can use the following workaround:
    Check your EPS/in directory after the CAR/SAR Archives of the SPs are
    extracted and rename all .PAT and .ATT files, which have a name like
    *_0000000.PAT (or *_0000000.ATT), by changing the string 0000000 to
    9000000. For example, for the VIRSANH SP SAPK-52302INVIRSANH rename the
    file VS30020106486_0000000.PAT to VS30020106486_9000000.PAT
    Afterwards, the upgrade will upload the informations about the SP
    properly and the SP can be included into the upgrade.
    Files:
    31/01/2007 07:32 329 VS30020106486_0000000.ATT
    31/01/2007 07:32 554,073 VS30020106486_0000000.PAT
    If these two files are renamed to e.g.
    VS30020106486_9000000.ATT
    VS30020106486_9000000.PAT
    the affected VIRSANH SP2 is uploaded correctly by the upgrade
    functionality and the SP inclusion of the VIRSANH SPs works.
    Sorry, as of now I cannot promise you a date when the tool fix will be
    available. I have found this bug only today in the evening (german time)and will discuss this with the responsible colleagues tomorrow.
    Afterwards, I will know more...
    Unquote:
    Hope this helps. We have decided against upgrading to 530_700 as it will involve upgrading GRC system and also new version has lot of new functionalities, which we like explore it after the ECC upgrade.
    Also, I would not suggest deleting VIRSAHR as all the config and customising done for VIRSAHR will be lost.
    Regards
    Chandu
    Edited by: Chandu Cheeti on Jan 17, 2010 11:19 AM

  • 4.6 C to ECC 6.0 Upgrade Project Timeline Sheet in MPP format

    Dear all,
    We are now proposing our customer for the 4.6c to ECC 6.0 Upgrade.
    Our customer is currently in 4.6c/oracle 9i/HPUX 11 i. He wants to move to ECC 6.0.
    If you have the project timeline for the above Technical Upgrade, can you pl send it to me.
    If you don't have in MPP format atleast send me the Work Breakdown structure with timelines.
    I shall modity the same to our customer and submit
    Thanks & Regards
    Senthil
    [email protected]

    Preparation Phase* 6 days
    Kick Off Meeting 1 day
    Upgrade Project Procedures Preparation 1 day
    Prepare Upgrade Project Plan 1 day
    Technical Requirements Assessment 3 days
    Assess Training needs of Key-users & End-users 1 day
    Prepare Detailed Basis Activity List for DEV, QA & PRD 1 day
    Business Blueprint Phase 6 days
    Develop System Landscape Upgrade Plan 1 day
    Functional Requirement Checklist 1 day
    ABAP Development check list 1 day
    Develop detailed Training Procedures & Documentation for Key Users & End Users 1 day
    Identify Testing Scope & Scenarios 1 day
    Identify Authorizations Conversion to Roles for SAP ECC 6.0 2 days
    Develop Documents as per Basis Activity List 1 day
    Develop Authorization Matrix for Activity Groups to Roles Conversion 2 days
    Prepare Upgrade Deliverables Checklist 1 day
    Realization Phase 28 days
    Installation of Solution Manager 3.2 System 1 day
    Creation of New Development System for Upgrade Project (Homogenous System Copy - PRD) 2 days
    Upgrade to AIX & Oracle 10g, SAP ECC 6.0 on New Development Server 3 days
    Upgrade Frontend Software 4 days
    Perform SPAU & SPDD Corrections 5 days
    Perform ABAP Development & Corrections 10 days Perform Authorizations Conversions and corrections after upgrade 8 days
    Perform Upgrade Testing for each Application Module 7 days
    Perform Unit & Integration Testing 6 days
    Perform Training to Key Users & End Users (Generic & Specific) 3 days
    Upgrade to AIX, Oracle 10g, SAP ECC 6.0 on Quality System 1 day
    Homogenous System Copy of PRD to New Quality & Upgrade to AIX, Oracle 10g & SAP ECC 6.0 2 days Perform Testing in Quality System 3 days
    Testing by end users on Quality System 1 day
    Production Realization & Go-Live Phase 6 days
    Upgrade to Production System Operating System to AIX (after close of business hours - 23:00) 1 day
    Oracle Upgrade to 10g (after close of business hours - 23:00) 1 day
    SAP Release Upgrade to ECC 6.0(Downtime Minimized - Downtime occurs in non-business hours) 2 days
    User Acceptance Testing 1 day
    Production System Go-Live 1 day
    Post Go-Live Support 14 days
    Post Go-Live Support 14 days Note: This is high level plan subject to change during Business Blue Print Phase 0 days
    This is taken from a post in Ittoolbox, May be this is generic. Hope you can tailor this to meet your requirements.

  • 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

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

  • Bdc,lsmw,bapi

    hello all,
    please tell me about difference between bdc , lsmw, bapi
    Moderator Message: Search for available information before posting.
    Edited by: kishan P on Dec 28, 2010 4:32 PM

    Hi Karthik,
    All the 3 can be used for the same purpose.
    BDC - was the first provided by SAP for mass data entry in to SAP Database with Screen checks
    LSMW - Originated as a 3rd party tool with many more functionalities and ease of use
    BAPI - Some times the transaction screens changes, in those cases the BDC's fail as they purely refer to the screen elements. BAPI's provide a more consistent way to make entries in SAP systems without referencing the screen elements but still adhering to the underlying business logic, so the data entry is syntactically and semantically correct.
    Hope this helps.
    Regards,
    Gaurav

  • 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

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

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

  • DB Migration and ECC 6.0 Upgrade

    I have a number of questions, we have a SAP R/3 4.7x200 landscape that is currently Windows 2003 and SQL2000 both 32 bit, we want to do the following, move to Windows 2003 and SQL2005 64bit, perform a Unicode and ECC6.0 Upgrade.
    here are the steps I am planning on new hardware
    1. Migrate to 64bit
    -install 64bit OS and SQL2006 64bit on new hardware
    -export db from current 32 bit and import into 64 bit system
         a. I am confused, I have seen threads where it appears this was done in house, do we need an SAP certified      person to complete this task, this is a hetergenous copy? Note 82478
         b. can we do this inhouse if we follow the SAP documentation and checklists provided and have their signoff      with checks
    - Run tests and then confirm process before real migration
    2. Perform Unicode Upgrade
    - run this on sandbox, test and verify
    3. Perform ECC 6.0 upgrade
    - run this on sandbox a no. of times confirm
    - freezing development and starting with DEV (this is a small landscape, we can do this)
    p.s can steps 2 and 3 be combined in one step, I have broken that out, to in my mind make it simpler to fix if anything breaks.

    Hi,
    DB Migration
    1. MS SQL Server 2000 is based on BIN collation and MS SQL Server 2005 is BIN2 collation. SO you need to first convert BIN to BIN2 collation.
    Note 960769  Windows Migration from 32bit to 64bit x8664
    Note 799058 - Setting Up Microsoft SQL Server 2005
    2. can steps 2 and 3 be combined in one step?
    Yes. check with link http://service.sap.com/erp-upgrade
    Regards,
    Srini Nookala

  • Any Specific Guide for Ecc 5.0 upgrade to ECC 6.0 (linux/oracle)?

    Hi Gurus
    Is there any  specific guide available for the Upgrade of ECC 5.0 to ECC 6.0 from service market place.
    for the linux operating system and oracle database. or atleast , I want to know what are the mimimum checks to be done (prerequisities) in the ECC 5.0 system which need to upgrade into ECC6.0.
    Thanks in advance
    Balaji

    Hi,
    There is not an specific guide for ECC 5.0 upgrade, just the guides specific for your OS/DB combination, they can be downloaded in https://websmp204.sap-ag.de/instguides but you should use the Unix/Oracle document,

Maybe you are looking for