Upgrade FM conversion

hi all ,
i am upgrading the SAP system from 4.6 C to ECC 6.0 , i met this funciton , i know i should use REUSE_ALV_GRID_DISPLAY or REUSE_ALV_GRID_DISPLAY_LVC , but the function is totally diffrent i think , could you give some tips about the conversion between this 2 FMs ?(DISPLAY_BASIC_LIST' ->  REUSE_ALV_GRID_DISPLAY  OR DISPLAY_BASIC_LIST' -> REUSE_ALV_GRID_DISPLAY_LVC  )
    CALL FUNCTION 'DISPLAY_BASIC_LIST'
      EXPORTING
        basic_list_title           = blt
        file_name                  = 'fred'
        head_line1                 = hl1
        head_line2                 = hl2
        head_line3                 = hl3
        head_line4                 = hl4
*    FOOT_NOTE1                 = FN1
*    FOOT_NOTE2                 = FN2
*    FOOT_NOTE3                 = FN3
*   LAY_OUT                    = 0
        dyn_pushbutton_text1       = layout_title
        dyn_pushbutton_text2       = 'Exit'
*   DYN_PUSHBUTTON_TEXT3       =
*   DYN_PUSHBUTTON_TEXT4       =
*   DYN_PUSHBUTTON_TEXT5       =
*   DYN_PUSHBUTTON_TEXT6       =
*   DATA_STRUCTURE             = ' '
*   CURRENT_REPORT             =
*   LIST_LEVEL                 = ' '
*   ADDITIONAL_OPTIONS         = ' '
*   WORD_DOCUMENT              =
*   APPLICATION                =
*   OLDVALUES                  = ' '
*   NO_ALV_GRID                =
*   ALV_MARKER                 =
     IMPORTING
       return_code                = pf_button_screen_1
      TABLES
* BEG KERR-5GJUS7
*       data_tab                   = customer_sum_lay1
        data_tab                   = out_lay1
* END KERR-5GJUS7
        fieldname_tab              = fieldnames
        select_tab                 = selection_itab1
        error_tab                  = error_table
*   RECEIVERS                  =
     EXCEPTIONS
       download_problem           = 1
       no_data_tab_entries        = 2
       table_mismatch             = 3
       print_problems             = 4
       OTHERS                     = 5
Best regards
Kevin

Solved

Similar Messages

  • ABAP and Kernel Patches for Upgrade and Conversion in 4.6C

    Hi,
    We are in a process of upgrade and unicode conversion for the source release 4.6C (Kernel  46D_EXT Patch 2225).
    "Combined Upgrade&Unicode Conversion Guide"  for "SAP Basis 4.6C u2192 SAP NetWeaver 7.0 application Server ABAP Unicode Including Enhancement Package 1 Support Package 01 - 06" , In Software Requirements step,  it says
    "3. Import 4.6D Kernel patch 2326 from SAP Service Marketplace according to SAP Note 19466"
    We wanted to know whether "IT IS ABSOLUTELY NECCESSARY TO GO FOR THE KERNEL PATCH 2326".  We dont have "EBCIDIC code pages" in our MDMP system.
    We need to know  becauase we are also doing OS migration from AIX to Sun and this step will add to our production downtime.
    Please advice what are the other causes we should go for the kernel 2326.
    Regards

    Hello Mr. Nils Buerckel,
    Thanks for the reply.
    We wanted to be very sure whether we should used Kernel 46D Kernel patch 2326 (As it is specifically mentioned in the SAP CU&UC guide and in SAP Note 867193, It is mentioned that  "This patch contains enhancements that are required to execute the "INDX Analysis" scan)
    OR
    Can we go for the latest kernel patch avaialable at market place? And Will the latest kernel patch also contains the "enhancements that are required to execute the "INDX Analysis" ?
    Please reply
    Thanks

  • Combined Upgrade & Unicode Conversion (Consistency & Scans)

    Hi
    We are doing a combined Upgrade & UC conversion. 4.6C NUC to ECC6 eHP7 UC with an SLO MWB for Data. We have made a clone (System copy) of 4.6C and are running the SPUM4 tool on it (as per the guide) . My question: after I export the glossary from the Cloned 4.6C system and import it into the productive 4.6C system - do I have to run the Consistency Checks & SPUM4 Scans in the productive system or can this be avoided. I know I need the glossary in production so that delta data loads to the MWB can use the glossary, but do I need to run the scans in Production.
    Thank you in advance for your help in this question
    Robert

    Hi Robert,
    SPUM4 needs to be executed on the PRD system. Hence you need to import the vocabulary (you called it glossary) and then all the scans need to be executed in CU&UC. This is to ensure that all data on your system is scanned and ends up in the vocabulary / reprocess logs.
    Best regards,
    Nils Buerckel

  • Upgrading Raw Conversion X-Trans Censors

    Good Morning,
    I a thinking of upgrading my LR to the new 5.  I was able to try Irdient new upgrade for X-Trans and my file are so much more crisp and detailed then they are in LR with your support for the X-Trans.  Are you going to upgrade you support to match those of Irdient.  I am sure you have read the reviews and have used the product for your own edificaiton.  If you are not, I may have to switch, my business depends on my best product.

    I am running 4.4.  Adobe may want to see for themselves the difference in the raw conversion.  Please let me know if an upgrade is in the works.
    Date: Tue, 16 Jul 2013 06:32:12 -0700
    From: [email protected]
    To: [email protected]
    Subject: Upgrading Raw Conversion X-Trans Censors
    Re: Upgrading Raw Conversion X-Trans Censors created by DdeGannes in Photoshop Lightroom - View the full discussion
    What version of LR have you tested with the X-Trans sensor? I believe it was upgraded in LR 4.4. Have you tried LR5 a thirty day trial is available for free.
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5509723#5509723
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5509723#5509723
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5509723#5509723. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Photoshop Lightroom by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • PSE 8 upgrade album conversion issue

    I upgraded my system to Windows 7 and since I was going to have to reload everything anyway, I upgraded to PSE 8 at the same time.
    Before the upgrade I saved my catalog files to my external drive and then moved them back to the C:\Program Files\Adobe folder  I put it there because I didn't see a catalog folder under the Elements Organizer folder
    Anyway, I then converted my catalog - renamed it "My Catalog 7.0" to differentiate
    The conversion says it was good and upon inspection all meta tags and albums seem okay.  The issue is that it didn't bring in the images from May 2009 onward.  I know those were in the catalog in 7.0 and had tags on them.
    Any sggestions on how to get those images (with their metadata) into PSE 8.0?
    Susan

    Thanks John
    You were right, I pulled the wrong file to convert (the one I used to convert 6 to 7)
    Thankfully I had a back up and was able to restore my correct 7 catalog.  All is good now.

  • Combined upgrade & Unicode conversion.

    Hi
    I need some suggestions for my concerns: I would appreciate, if you reply ASAP for below situations and actions.
    Current system: HP unix DB: Oracle10.2.0.2
    SAP 6.20 with SP 61, single code page
    strategy: resource minimized.
    Upgrading from 4.7 was 6.20 to ECC6.0 with CU & unicode conversion.
    we ran UCCHECK and provide the list to ABAP, but they are not modifying now.
    Mean while we started the preconversion steps for unicode conversion and completed. SPUMG.
    Upgrade prepare is completed and currently in begining of down-time.
    so far ABAP programs are not unicode complaint!!!
    we don't know, when would they modify??
    If we complete the upgrade and post upg steps for ecc 6.0 and
    pre coversion steps for unicode.
    is it a problem, if the ABAP programs are not modified yet, can it be done after conversion and before export???
    or after import??
    Your time is highly appreciated.
    Thanks
    creddy

    Per CU&UC guide, you can do some conversions in parellel
    and after upgrade, you have to perform preparation steps and then export, that is what i am following.
    What you said is right for single code page conversion method.
    upgrade first
    unicode conversion second.
    I am following CU&UC method.
    Thanks
    reddy

  • MDMP: TWIN Upgrade + Unicode conversion

    Hello ,
    We have adopted twin upgrade and unicode conversion method and at present we are converting the twin system to unicode conversion.
    In Twin system we have completed SPUMG 7 scans. Whether i need to run UMG_TWIN_CREATE_TRANSPORT  now to save the results for twin preparation run or i need to perform this step after Additional preparatory step.
    Kindly suggest
    Regards
    Vinay

    Hi Vinay,
    Excerpt from the UCG:
    2.4 Final Preparation Steps
    2.4.1 SPUMG Updates
    If there is a time difference between the scan and the database export, it may happen that a new table has been created or a Support Package has brought a new table with it. In such a case, the preconversion must be rerun right before the export is carried out to ensure that the data change is reflected in the Export Control Table.
    End excerpt
    Hence this step is necessary in case of DB changes (e.g. new tables with or without  content).
    Therefore if you have significant changes, I would recommend to create the twin transport after this step.
    However this step has to be repeated in the PRD system as well (see TU&UC-Guide) to reflect the changes between Twin and PRD system. In order to minimize downtime, the differences between the two systems should be small.
    Best regards,
    Nils Buerckel
    SAP AG

  • 46C EBCDIC to UNICODE upgrade and conversion

    Can the UNICODE conversion processed be used directly on a 46C EBCDIC source system? Or is a conversion to 46C ASCII required before a UNICODE conversion?

    Hello Will,
    as Sally already explained, this is unfortunately not possible ;-((
    SAP does not support Unicode with 4.6C ;-(
    Therefore, only EBCDIC and ASCII are the options.
    As of 4.7 Unicode & ASCII are available.
    => the project could look as follows:
    - On 4.6 you need to go from EBCDIC to ASCII - 12 - 24h conversion time
    - Upgrade to ERP 6.0 EHP4 ASCII - total Runtime about 40-65h - downtime of that: 10-24h
    - Unicode Conversion Latin1 - 6-14h conversion time
    => You see, that the total runtime in one step is pretty long - e.g. for X-mas ...
    Otherwise, it is typical, that the ASCII CPC is done in one step and later on Upgrade & Unicode in one further step.
    For more details, we should talk together, but at least your project is pretty big ...
    Regards
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

  • SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

    Basis Gurus
       I am working on upgrade from R/3 4.6C to ECC 6.0.
    ECC 6.0 upgrade completed( still in non Unicode).  Now I am in the process of Unicode conversion.
    I have used following methods for the upgrade.
    1. Combined Upgrade & Unicode conversion(CU & UC)
    2. Resource minimized( as I am doing it in Sandbox).
      As I understand I need to perform the DB export and Import now for the unicode conversion.
      According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
      and then install Unicode system and import the same data file.
      My understanding was, when I choose, Resource minimized, I need to run Export and import
      in the same system.
      Can you please help me , whether I need another Unicode system for import ??
    Graham

    Hi,
    Dont get confused with upg strategy and unicode conversion.
    In general Upgrade strategy (either downtime-minimized/resource minimized)
    In unicode conversion you have export/import(exp/imp) of data concept
    In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
    Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
    It can be done in 2 ways.
    If you dont have addtional server for unicode conversion
           1)you can either do exp on same hardware and take bakup and do import using the exp dump.
           2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
    Hope this is clear.
    Regards,
    Vamshi.

  • 4.7EEx1.10 to ECC6.0 upgrade and Unicode conversion

    Hi Experts,
    We are going to initiate the upgrade from next month onwards. Subsequently i have started preparing the plan and strategy for the same.
    As our current setup is 4.7EEx110/Win 2003 R2-64 bit/Oracle 10.2.0.4.0 (Non unicode). And we have recently migrated on to this setup from WIn2k 32 bit. Also the current hardware is Unicode compatible.
    With respect to strategy for achieving this Upgrade and Unicode conversion, i am planning as follows.
    Step 1) Perform Unicode conversion on the current landscape (Both Export/import on the same servers)
    Step 2) Setup Temporary landscape as part of Dual maintenance strategy and migrate data from the current systems to temporary systems using backup/restore method.
    Step 3) Perform the SAP version upgrade on the current landscape and setup transport routes from temporary to current landscape in order to keep it in sync
    Step 4) after successful upgrade, decommission the temporary landscape
    Please provide your suggestions and valuable advices if there is anything wrong with my strategy and execution plan.
    Regards,
    Dheeraj

    Hi,
    Thanks. As i have already referred these notes as i am seeking advise with respect to my upgrade approach.
    However i have planned to perform in the following manner.
    1) Refresh Sandbox with Prod data and perform Upgrade to ECC6.0 EHP5 & subsequently Unicode conversion on the same server (Since both export & Import has to perform on the same hardware as we have recently migrated on this hardware which is Unicode compatible)
    2) Setup temporary landscape for DEv & QAs and establish transport connection to Production system in order to move urgent changes
    3) Keep a track of the changes which have transported during upgrade phase so that the same can be implemented in the upgraded systems i.e. Dev & QAS
    4) After Sandbox Migration and signoff, we will perform Dev & QAS upgrade & unicode conversion on the same hardware (Note: Since these are running on VMware can we export the data from the upgraded system and import on to a new VM?)
    5) Plan for production cutover and Upgrade the Prod system to ECC6.0 Ehp5 and then Unicode conversion. As i am planning to perform upgrade over the weekend and then Unicode conversion activity in the next weekend (Is it a right way?)
    My Production setup: DB on one Physical host and CI on separate Virtual host
    6) After the stabilization phase, we are planning for OS & DB upgrade as follows:
          a) Windows upgrade from 2003 R2 to Windows 2008 R2
          b) Oracle Upgrade from 10.2 to 11.2
    If anyone thinks that there is anything wrong with my above approach and need changes then please revert.
    I have one more doubt as I am going to upgrade 4.7EEx110 (WAS 620, Basis SP64) to ECC6.0 EHp5.As I presume that I can straight away upgrade from the current version to ECC6.0 Ehp5 without installing EHP. Kindly confirm
    Thanks

  • Error during upgrade phase JOB_RSUPGCUA_SHD

    Hi Everyone,
    We are in the process of completing a combined ERP 6.0 Upgrade / Unicode Conversion.  Our starting release is ECC 5.0 (ABAP only) and we are running Oracle 10.2.0.2 on AIX 5.3. 
    We are receiving the following error in phase JOB_RSUPGCUA_SHD:
    1 ETQ201XEntering upgrade-phase "JOB_RSUPGCUA_SHD" ("20080812163717")
    2 ETQ366 Connect variables are set for shadow instance access
    4 ETQ399 System-nr = '56', GwService = 'sapgw56'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=1
    4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
    4 ETQ010 Date & Time: 20080812163717
    4 ETQ260 Starting batchjob "RSUPGCUAGEN111"
    4 ETQ230 Starting RFC Login to: System = "ENP", GwHost = "aix12j1", GwService = "sapgw56"
    4 ETQ359 RFC Login to: System="ENP", Nr="56", GwHost="aix12j1", GwService="sapgw56"
    4 ETQ232 RFC Login succeeded
    4 ETQ233 Calling function module "SUBST_START_BATCHJOB" by RFC
    2EETQ235 Call of function module "SUBST_START_BATCHJOB" by RFC failed (error-status "10")
    2EETQ261 Start of batchjob "RSUPGCUAGEN111" failed
    1EETQ203 Upgrade phase "JOB_RSUPGCUA_SHD" aborted with errors ("20080812163717")
    We originally had some issues with the shadow system not starting in phase START_SHDI_FIRST.  The source of the problem was the value of paramter ipc/shm_psize_40 in the instance profile of the shadow system.  When we ran "sappfpar check" on the profile, the output indicated that the paramter was too small.  We backed up the profile, increased the parameter to the value "sappfpar check" recommended and then stopped the shadow system via "SAPup stopshd."  We then repeated the phase.  The shadow instance was started successfully and the upgrade proceeded with subsequent phases.
    We encountered the error above several phases later.  The shadow instance is started and I am able to login with user DDIC.  As detailed in the error message above, function module SUBST_START_BATCHJOB is aborting with error code 10.  Based on what I can interpret from source code of the function module, this seems to indicate that there is a problem with the program values.  The SM21 log indicates that "Program name RSUPGCUAGEN111 is invalid." 
    What do we need to do to get past this error?
    Thanks in advance for any assistance,
    Tommye

    for our case it was that the shadow instance was not completely stsarted, some processes were down, cause the ipc pool 40 was too small, i found the error in the killed work processes.
    Probleme resolved as susch. i hope it will help someone.
    Regards

  • Unicode conversion in situ

    Hi SCN,
    I'm looking at the possibility of running a Combined Upgrade & Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.
    However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).
    What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?
    This seems logically problematic as you need a target system to import to.
    I can imagine a process along these lines though...:
    1. Take SAP layer offline
    2. Run full backup of system
    3. Export system
    4. Drop database* (to make clean ready for new import)
    5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...
    6. ....and continue to run import into that database
    7. Complete Unicode conversion process
    However the big issue here for me is
    (a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple
    (b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.
    Any input/discussion on these points would be very welcome.
    Regards, doonan_79

    FYI Community. Feeling after reading and research is to use a temorary server to import unicode converted system data into; then swing disks back to the original host. Making all required hostname updates during the process.
    Allowing for parallel export/import, but going back to the original configured host to complete the process.

  • Issues during technical upgrade from  version 4.6C to ECC 6.0

    Dear All,
    We have done a technical upgrade from version 4.6C to ECC 6.0 and encountered following issues -
    In the t-code ABZE (acquisition with in house production) there is a check-box for reversal posting on screen with version 4.6C. However, this field is missing in ECC 6.0. Why so?
    In the report s_alr_87012327, there is a field "only with creation block" in version 4.6C. However, this field is missing in ECC 6.0. Why so?
    Request to kindly suggest the alternative to carry out the same in ECC 6.0.
    Thanks in advance.
    Regards,
    Dhawal

    Hi Akshya,
    Please find answers below.
    1) 4.6c is NON-UNICODE system, Can I upgrade it into ECC 6.0 UNICODE system?
    Yes you can.
    If you are on a single code page system then you can give a gap between your uprade and unicode conversion. There is no problem with the singlecode upgrade and conversion.
    But if your system is MDMP then you will have to do the CUUC method that is both upgrade and unicode conversion together. Though you can give a gap and sign an disclaimer with SAP it is still not recomended way.
    2) 4.6c does not have any ITS system installed. If we upgrade it to ECC6.0 ABAP only, then Can I activate WAS internal ITS?
    Yes you can activate it.
    3) 4.6c does not have any JAVA stack. When I upgrade it to ECC 6.0, can I upgrade it to dual stack (ABAP+JAVA)? If yes, then how?
    After the upgrade and unicode conversion you can install the java stack.
    Regards,
    Ravi.

  • JATO 1.2 to 2.0 upgrade

    Hello. Our team is currently analyzing the possibility of upgrading from SunOne App. Server 6.5 to 7.0 and from JATO 1.2 to 2.0. We are searching for others who have done the upgrade and conversion. Some of the questions we have follow:
    If you have upgraded from 6.5 to 7.0, how did the upgrade go? Were there any problems? Is 7.0 stable?
    If you have upgraded from 1.2 to 2.0, how did the conversion go? Were there problems? Was the conversion a major effort? Do the converted pages work in Studio 4.0? Is using Studio a huge benefit?
    Do you know if anyone else has done this?
    Answers to these question will help us to decide if we have to upgrade or not.
    Thank you in advance for any information you can provide to us!
    Sincerely,
    Jesudas Sundararajan (Das)
    Syngenta Seeds, Inc.
    7500 Olson Memorial Hwy.
    Golden Valley, MN 55427
    ph: 800-445-0956 ext. 7167(7am- 4pm cst)
    fx: 763-593-7299
    [email protected]

    (copied from my Yahoo Group response)
    The only thing I can give some info on is the JATO 1.2 to 2.0.
    First, the JATO runtime has very few changes in it from 1.2 to 2.0. Your app will typically run as is under 2.0. All you really need to do is replace the JATO JAR file. There may be a few minor details, but should not be any show stoppers.
    There are some new API's in 2.0, but the old stuff is just deprecated. There are some additionally API's to make JATO toolable, but have no affect on the runtime.
    The Studio really reduces the effort it takes to create JATO components. Lots of code gen that is easily manipulated via visual property editor. However, you still have the flexibility to hand code what you want.
    The way to bring your 1.2 app into a JATO 2.0 app is as follows:
    - use the Studio to create a new application with the same package structure as your current app
    - copy your view beans, tiled views, models and custom classes into the new package structure.
    Now this allows you to build new objects using 2.0 techniques (visual point/click creation) and the new components will run along side your old components. The old components will not show up in the Studio tool like the new components will. In other words, a newly created view bean is recognized as a "JATO ViewBean" because it has an extra design time meta data file that desribes it. Your older ViewBeans will not have this file and therefore, will only be recognized as a regular Java class.
    Creating this meta data file is not really something that can be reasonably done by hand, unfortunately.
    If your app will not grow, then go ahead and start using JATO 2.0 runtime, but don't worry about the Studio aspect. But if you plan to expand the app, it would be beneficial to continue with the Studio tools.
    Does anyone have some "real" world experience they can lend to the forum.
    craig

  • Twin Upgrade to NW7.3

    We are doing a Twin Upgrade to NW7.3 from 7.01.
    We only find the Twin Upgrade Guide for ECC6 (target release).
    Are there links for Twin Upgrade for NW7.3?
    Thanks for help.

    Hello Jennifer,
    Refer to the note Note 959698 - Twin Upgrade & Unicode Conversion and attached document in the note. Looks like, TU is only on ECC system and from 7.01 Unicode conversion and upgrade has to be done seperately.
    Thanks,
    Arjun

Maybe you are looking for