Issues during technical upgrade from 4.6c to ecc 6.0

Hi
We are doing a technical upgrade from 4.6C to ECC 6.0. Some transactions in QM module when tested in ECC 6.0 test client give a abap termination message (or dump) and certain transactions like qs42,46, qa18, qs34 etc do not get executed (error = no entry foound for......) and similarly in PP-PI module transactions like C203 have similar problems, even though master data does exist. What should I look for?  Can somebody pl. give details on configuration checks and the OSS notes from a functional point of view for a technical upgrade?
For certain transactions I get the error message - "Central system of distribution SM-P06CLNT430_TRUSTED is unreachable RFC destination SM_P06CLNT430_Trusted does not exist" - what does this mean?
thanks
BE

Hi,
1. Have you done successfull installation from 4.6C to ECC 6.0 at the time of PrePare ans SAPUP?
2. Check SP' for QM and PP-PI modules from http://service.sap.com/sp-stacks.
3. Configure RFC connections correctly, SM_<SID>CLNT<No>_Trusted automatically created, not manually.
http://service.sap.com/notes --> search for RFC trusted connections for Ecc 6.0
http://service.sap.com/upgrade.
Regards,
Srini Nookala

Similar Messages

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

  • Technical upgrade from 4.7 to ECC 6.0

    Experts,
    1.We need to make Technical upgrade in HR from 4.7 to ECC 6.0 with OM,PA, -ve Time,Payroll, Recruitment (other Modules also upgraded).Kindly let us know what will haeepen for the following .
    A.Configrations in SPRO
    B.Previous database (Cluster table for previous Time and payroll run)
    C.Master data of employees which is stored in Infotypes
    2.Also Kindly let us know is there anything we need to take care after moving from 4.7 to 6.0

    Hi Kumar,
    Basically there needs to be a Transport established between 4.7 and ECC6.00 Version . You can create Transport request for those tables whose value remain same in 4.7 nad ECC6.00 But for tables having changes you need to create the Configuration.
    1 more method applied by organization is a client copy of tables.
    My suggestion would be like this :
    1. Compare and Update Tables (from Configuration Handbook)
    Pay Frequency
    Define Period Modifiers
    V_T549R
    Define Date Modifiers
    V_T549L
    Check Payroll Accounting Area
    V_T549A
    Pay Scale Structure
    Define EE Subgroup Grouping for PCR and Collective Agreement Provision (CAP)
    V_503_B
    Check Pay Scale Type
    V_T510A
    Check Pay Scale Area
    V_T510G
    Check Assignment of Payscale Structure to Enterprise Structure
    V_001P_C
    Define Default for Pay Scale Data
    Feature - TARIF
    Setup payroll period for Collective Agreement Provision
    V_T510W
    Revise Pay Scale Groups and Levels
    V_T510
    Enterprise Structure for Wage Type Model
    T539A
    Feature - LGMST
    Revise Default Wage Types
    V_T539A - already tested
    Define Valuation of Base Wage Types
    V_T539J
    Legacy Data Transfer
    T558B
    T558D
    Define Periods for import
    T558B - already tested
    Rates of Pay
    T512W
    Pay Scale Allowance Group
    V_T7INA1
    Assign Pay Scale Groupings for Allowances
    V_T7INA3
    Define Basic Codes
    V_T7INB4
    Statutory
    Define Trust Details for Provident Fund
    V_T7INF1
    Assign Company Rates for Provident Fund
    V_T7INF5
    Define PF Trust Validity Period
    V_T7INF7
    Maintain Contribution Details for Provident Fund
    Feature: 40EPF
    V_T7INF3
    Define Contribution Type for Statutory rates for Provident Fund
    V_T7INF3 - already tested
    Employees' State Insurance
    V_511P_B
    V_T511P
    Maintain Number of Working Days in a Month
    V_511K_B
    V_T511K
    Define Personnel Area and Subarea Groupings for ESI
    V_T7INE1
    Assign ESI Groupings for Personnel Area and Subarea
    V_7IN0P_ESI
    Maintain Contribution Rates for ESI
    V_T7INE3
    Assign Universal Contribution Groupings for Universal Contribution Type
    V_T7INOP_ALL
    Assign slab code for Universal Contribution Grouping
    V_T7INU1
    Assign Slab code and other parameters for each state of a universal type
    V_T7INU3
    Assign contribution Value for each slab
    V_T7INU5
    Maintain Eligibility Details for Superannuation
    Feature - 40SAN
    Tax and Professional Tax
    Define Professional Tax Grouping Details
    V_T7INP1
    Maintain Method and Form Layout for Ptax Groupings
    T596F
    Maintain Re-Computation Behaviour of Tax related
    Feature - 40MWT
    Maintain Schema for Exemption on Medical Reimbursement / Insurance
    V_T7INT9
    Maintain Schema for Exemption of Child education and hostel allowance
    V_T511K - already tested
    V_T7INT9 - already tested
    Bonus Act
    T511K - already tested
    T511P - already tested
    One Time Bonus Tax
    Copy Wage Types
    V_T7INT9 - already tested
    V_T7INA9
    Define Compensation Area Feature
    Feature - CAREA
    Assign organizational assignment to Compensation Groups
    Feature - CMGRP
    Maintain Variant for Payroll Simulation
    Feature - 16CVA
    Maintain Payslip Variant
    Feature - 16EVA
    HRA/CLA/LTA
    Define Accomodation Types
    V_T7INT7
    Company Loans
    Maintain Loans Grouping
    Feature - 40LGR
    Mantain Loans Eligibility Checks and Limits
    Feature - 40 LGR - already tested
    Banking
    Setup House Banks
    V_T012
    Bank Account
    V_T012K
    Define Sending Banks
    Feature - DTAKT
    Check Text Keys for Payment Transactions
    V_T520S
    General Ledger
    Define Employee Grouping Account Determination
    Feature - PPMOD
    Define Symbolic Accounts
    V_T52EK
    V_T52EZ
    2. Compare and Update Genaral Tables     
    1     T512W
    2     T511K
    3     T511P
    4     TCURR
    5     T030
    2a. Compare and Update Additioanl PY-IN Tables     
    1     T7INTN TAN Number Maintainence
    2     T7INA1 Pay scale grouping for allowances
    3     T7INA3 Associating pay parameters to pay scale grouping
    4     T7INA5 Wage type model for pay scale grouping for allowances
    5     T7INA7 Reimbursements Allowances and Perks - base slabs
    6     T7INA9 Reimbursement allowances perks - eligibility and calculation
    7     T7INAA Salary year for pay scale grouping for allowances
    8     T7INB1 Basic Wages
    9     T7INB4 Basic Codes
    10     T7INB5 Basic Codes for Allowance Groups
    11     T7INB7 Basic slabs
    12     T7INB8 Appraisal Criteria
    13     T7INB9 Increment criteria
    14     T7INC1 Car types master
    15     T7INC3 Type and age eligibility for car schemes(COCS/OYCS)
    16     T7INC5 Perk valuation for cars
    17     T7INC7 Amount and number eligibility for car schemes(COCS/OYCS)
    18     T7INC9 Conveyance allowance eligibilty
    19     T7INCA Codes for Conveyance types
    20     T7IND1 Dearness allowance consumer price index  master
    21     T7IND3 Dearness allowance consumer price index value
    22     T7IND5 Dearness allowance basic slab details
    23     T7IND7 Dearness allowance calculation rules
    24     T7IND9 Dearness allowance consumer price index slabs
    25     T7INE1 Personnel area / subarea grouping for employees' state ins.
    26     T7INE3 Employees' state insurance contribution rates
    27     T7INF1 Trust Master
    28     T7INF3 Statutory rates for Provident fund
    29     T7INF5 Company rates for Provident Fund
    30     T7INF7 Trust details
    31     T7ING1 Gratuity Details Maintenance
    32     T7ING3 Gratuity ID Maintenance
    33     T7ING5 Gratuity ID and Related Wage Types
    34     T7INI0 Investment category limits
    35     T7INI2 Investment technical description and text
    36     T7INI4 Investment details
    37     T7INI5 Sub section description
    38     T7INI7 Sub section limit
    39     T7INI8 Sub division description
    40     T7INI9 Sub division details
    41     T7INIA Deduction wage type for Sec 88
    42     T7INIC Deduction wage type for Sec 80
    43     T7INJ1 Section 24 Deduction Details Maintenance
    44     T7INJ3 HR-IN: Loans Eligibility checks and limits
    45     T7INJ5 HR-IN: Loans Dusbursement Schedule
    46     T7INJ6 HR-IN : Loan Tranche Disbursement: Text for Events Code
    47     T7INL1 Leave validation for LTA
    48     T7INO1 One day salary deduction
    49     T7INP1 Professional tax grouping details
    50     T7INP3 Method and form layout for states
    51     T7INP4 Professional tax slab amounts
    52     T7INR1 Housing code for taxation
    53     T7INR3 Percentage/amount for housing related constant
    54     T7INR5 Housing related statutory constants for taxation
    55     T7INR7 Codes for Housing Types
    56     T7INR9 City category for housing type
    57     T7INS1 Superannuation Details Maintenance
    58     T7INS3 Superannuation ID
    59     T7INS5 Superannuation-Wagetype Details
    60     T7INT1 Slab codes for taxation
    61     T7INT3 Taxation slabs
    62     T7INT5 Personnel subarea grouping for Tax
    63     T7INT7 Tax codes for tax exemptions
    64     T7INT9 Taxability of wage types
    65     T7INU1 State for Universal Grouping
    66     T7INU3 Slab Codes for States
    67     T7INU5 Contribution Value for Each Slab
    68     T7INW1 Personnel area/subarea grouping for LWF
    69     T7INW3 Labour welfare fund rates
    70     T7INY1 Recovery of rounding off amounts
    71     T7INZ1 Factor for retiral benefits
    72     T7INZ3 Period of notice codes
    3. Compare Payroll Schemas     
    1     Compare ECC5- to ECC6 standard schemas
    2     Compare ECC5- to ECC6 customised schemas
    4. Compare Personnel Calculation Rules (PCR)     
    1     Compare ECC5- to ECC6 standard PCR's
    2     Compare ECC5- to ECC6 customised  PCR's
    B. Payroll Process     
    1     Generic Payroll Process
    1.1     Simulate Payroll
    1.2     Release Payroll
    1.3     Start Payroll
    1.4     Check result
    1.5     Corrections
    1.6     Remuneration statement
    1.7     Simulate and test FI/CO postings
    1.8     Simulate and Test Preliminary DME
    1.9     Run Preliminary DME Program
    2     Create a live posting run and create FI documents
    C. Regression Testing (Variance Monitor)     
    1     Compare Payroll Results
    Create a Excel with these contents and fill them up by saying the percentage of similarity and completetion.
    Please let me know if this is usefull
    Regards,
    Prabha

  • Technical Upgrade from 4.6c to Ecc 6.0

    Hello All.
    We have upgraded the system from 4.6c to ECC 6.0.
    We have got SPAU list and Unicode(UCCCHECK) program list.We have shortage of time to resolve both the list.
    I have few questions.
    1) Do we need to resolve UCCCHECK list  first or SPAU list.
    2) How we can modify programs,tables in SPAU list.
        Could you please give Some step by step need to perform in SPAU list.
    3)How we can convert UCCCHEK list
       Could you please give STEP by STEP procedure and transaction code.
    Thanks in Advance
    Muthu

    Hi Muthu,
    Please [check this link|http://help.sap.com/saphelp_nw04/helpdata/EN/83/7a18ecde6e11d195460000e82de14a/content.htm].Do the same with SPDD too.
    SPAU has to be done before going for the UCCHECK of custom objects.
    Thanks,
    Sai

  • LONGPOST.LOG Errors during Upgrade from 4.6C to ECC 6.0

    Dear all,
    We have received the below errors during our upgrade from 4.6C to ECC 6.0.
    Basically we have received three types of errors:
    1.
    4PETG065 RSUPGDEC: Table/structure "BAPE_VBAK" (component "SD-SLS" ) enhanced illegally: Error "2"
    2.
    A2PESEEF_BADI 103 BAdI implementation "/IRM/BADI_SDDOCFLOW" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "ZZ_MG_MASS_NEWSEG" must still be migrated A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
    A2PESEEF_BADI 103 BAdI implementation "ZOTC218E_1" must still be migrated
    3.
    3PETG447 Table and runtime object "/SSF/DHEAD" exist without DDIC reference ("Transp. table")
    3PETG447 Table and runtime object "/SSF/DTAB" exist without DDIC reference ("Transp. table")
    3PETG447 Table and runtime object "/SSF/PTAB" exist without DDIC reference ("Transp. table")
    Can anyone help us how to solve this issues.
    Thanks & Regards
    Senthil

    Hi,
    Senthil following are ans to ur questions
    1. After the SPAU remediation is completed, should I manually release the transport or should I start the upgrade and the upgrade will release that transport?
    Ans : Once your SPAU remediation is completed you should release the requests and then start the upgrade of the DEV system.
    2. How do we import this SPDD & SPAU transport in the QA and PRD, I mean at what stage of the upgrade we need to specify/ include this transport?
    Ans : Now when you start the QA or PRD upgrade at that time you come across a phase during PREPARE called ADJUSTPRP.
    Refer following note for further information --
    SAPNote 124522 - Importing a modification adjustment in 2nd upgrade
    3. Suppose the QA & PRD has more objects to adjust than our Dev box, and this transport will not take care of the delta objects, so in that case how should we remediate, we need to create an other transport request in QA and then it will become two transports?
    Ans : First of all this should not be the scenario where you have more modified objects than that in DEV. As all the modfications should take place in DEV first and then should be transported to QA and then PRD. But in such case what you can do is complete the upgrade of QA system and then you are still having 14 days to complete the SPAU objects. So you can make another request which can be transported as a post upgrade activity once the upgrade is completed in production. For SPDD you will have to take care of the SPDD objects if there are different than those in DEV during the ACT_700 phase only or else you might risk data.
    This is the reason why SAP always asks you to follow a proper transport path.
    4. If our dev box has more objects for remediation than our QA & PRD, then will these objects be also imported into the QA & PRD box?
    Ans : Yes, thats why you should be very sure about the SPAU objects that you have found in DEV. You need to compare the objects with QA and PRD and then only make the modifications.
    I hope i have answered all your queries.
    Regards,
    Suhas

  • Upgrade from 4.6c to ecc 6.0

    Hi,
    We are doing a technical upgrade from 4.6c to ecc 6.0 without activating New GL. As a functional consultant, what should i look for? I know that we need to test the business processes and check Z programs but anything specific, plzz let me know.
    What changes should be made in Asset Accounting?
    Regards
    Satya

    Thanks for the reply.
    What are the  changes made in Asset accounting after upgrading?
    I heard of RBE tool...how is it used for FI?? (u check for the mostly used transactions or what??)
    Anyone, plzz answer..waiting for ur replies
    Regards
    Satya

  • Find button issue in tool bar during upgrade from 4.6c to ECC 6

    Hi All,
    I came across one issue during the upgarde.
    In new system ECC 6:
    When i run the transaction IW51 then give the notification type SE(service notificaton) and then hit enter key.
    It leads to next screen there enter the value in the FUNCTIONAL lOCATION field some ex 9000004 and
    opposite to that field there is a structure list icon.
    Clicking that icon it leads to a structure list.
    My issue is: the FIND button and FIND NEXT button are disabled in the menu bar.I need the both buttons to be active
    When i seen in old system i.e 4.6c
    FIND button and FIND NEXT button are active.
    I made little change in the new system in include MIHIXF82 as shown below.
    SET PF-STATUS 'MAIN' ."EXCLUDING gt_excl_tab.
    I commented the EXCLUDING gt_excl_tab.
    Now FIND button and FIND NEXT button is active but when i click the FIND button there is no pop up is displayed.
    Usually pop up is displayed when we click FIND button in that we can enter the value which we have to find out.
    Regards
    Jai
    Edited by: Jayanth16 on Jan 28, 2010 8:07 AM

    Hi,
    In that program gui status MAIN is used.
    When i see that gui status and in FUNCTION KEYS the FIND button and FIND NEXT button
    the function codes are in orange color.Remaing BACK,EXIT,and CANCEL button function code are in white color.
    Whether the orange color indicates is in inactive mode?
    If so how can i activate those Function codes?
    Regards
    Jai

  • Error during Upgrade from 4.6c to ECC 6.0

    Hi All,
      We are facing an error when upgrading from 4.6c to ECC 6.0. We are facing this error on the table COEP - runtime object inconsistancy. What we found is there is ERP upgrade has created new extra fields in the table. In log file the error is specified as : Duplicate Field name, But we not able to find the duplicate field name in the table.  Please kindly help as early as possible. The upgrade process is stuck.
    Regards
    Anil Kumar K

    Hi Anil,
    Is this issue fixed? Can i know how you fixed it?
    replied to your message Re: How to adopt the index changes during upgrade.
    Thanks,
    Somar

  • Technical upgrade from 4.6C MDMP system to ECC 6.0 using CU & UC approach

    Hi SAP Experts,
    We are embarking on a project for Technical upgrade from SAP R/3 4.6C MDMP system to ECC 6.0 using the CU & UC approach for our Asian operations (comprising of India, Japan, Taiwan & Singapore).
    Please share with me the Best Practices you followed in your projects, checklists, DOs, DONTs, typical problems you encountered and the possible safeguards, any other useful information, etc.
    Since very little information is available from Organizations who have used the CU & UC upgrade approach successfully, I am raising this in SDN to share your experiences during the Technical upgrade.
    All useful information will be surely awarded with suitable points.
    Looking for your invaluable inputs which will be a BIG help for our project.
    Best regards,
    Rajaram

    Hello Rajaram!:
    It's a very big project, that you have to do in a lot of steps........
    If you want sent me a email with the problems and you want.
    Regards,
    Alfredo.

  • Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query

    Hi All,
    There is a Performance issue after Upgrade from 4.7 to ECC 6.0 with a select query in a report painter.
    This query is working fine when executed in 4.7 system where as it is running for more time in ECC6.0.
    Select query is on the table COSP.
    SELECT (FIELD_LIST)
            INTO CORRESPONDING FIELDS OF TABLE I_COSP PACKAGE SIZE 1000
            FROM  COSP CLIENT SPECIFIED
            WHERE GJAHR IN SELR_GJAHR
              AND KSTAR IN SELR_KSTAR
              AND LEDNR EQ '00'
              AND OBJNR IN SELR_OBJNR
              AND PERBL IN SELR_PERBL
              AND VERSN IN SELR_VERSN
              AND WRTTP IN SELR_WRTTP
              AND MANDT IN MANDTTAB
            GROUP BY (GROUP_LIST).
       LOOP AT I_COSP      .
         COSP                           = I_COSP      .
         PERFORM PCOSP       USING I_COSP-_COUNTER.
         CLEAR: $RWTAB, COSP                          .
         CLEAR CCR1S                         .
       ENDLOOP.
    ENDSELECT.
    I have checked with the table indexes, they were same as in 4.7 system.
    What can be the reson for the difference in execution time. How can this be reduced without adjusting the select query.
    Thanks in advance for the responses.
    Regards,
    Dedeepya.

    Hi,
    ohhhhh....... lots of problems in select query......this is not the way you should write it.
    Some generic comments:
    1. never use SELECT
                       endselect.
       SELECT
      into table
       for all entries in table
      where.
       use perform statment after this selection.
    2. Do not use into corresponding fields. use exact structure type.
    3. use proper sequence of fields in the where condition so that it helps table go according to indexes.
        e.g in your case
              sequence should be
    LEDNR
    OBJNR
    GJAHR
    WRTTP
    VERSN
    KSTAR
    HRKFT
    VRGNG
    VBUND
    PARGB
    BEKNZ
    TWAER
    PERBL
    sequence should be same as defined in table.
    Always keep select query as simple as possible and perform all other calculations etc. afterwords.
    I hope it helps.
    Regards,
    Pranaya

  • Technical Upgrade from XI 3.0 to PI 7.1

    Hi,
    My client is going for Technical Upgrade from XI 3.0 to PI 7.1 not fresh installation. They are asking for How best we can achieve this. I have gone through Decision making document and upgrade document from SAP. Apart from which please provide me the valuable Inputs like what measures we need to take care before and after upgrade as an XI developer. In our project about 90% of interfaces are having java mapping. will there be any changes to be done after upgrade.
    I already gone through below link
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/8085e299-718c-2a10-de94-928f62b763ce
    https://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655&overridelayout=true
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40a0868a-9d40-2b10-8cb4-8e0c53b56655
    Thanks in advance
    Venkatesh

    you can use this document as your base - http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/8085e299-718c-2a10-de94-928f62b763ce?quicklink=index&overridelayout=true
    do an upgrade from XI 3.0 to PI 7.1
    java mappings will still continue to work.
    But you might have to modify some graphical mapping, java proxies and modules if any

  • Technical upgrade from 4.6c to 6.0ecc with unicode conversion

    Hi Experts,
    Can you explain me technical upgrade from 4.6c to 6.0ecc with Unicode conversion.
    if u got any notes pls send it to [email protected]
    vijay

    Check these links. Search SDN  with Term "Upgradation" you will get lot of links
    http://help.sap.com/saphelp_nw04/helpdata/en/16/4b3c88170e11d6999d00508b6b8b11/frameset.htm
    http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f0f9f37c-be11-2a10-3baf-d5d7de5fb78d
    http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/system%2blandscape%2bconversion
    http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/project%2bplanning%2b-%2bmdmp%2bsystem
    http://www.sdn.sap.com/irj/sdn/wiki?path=/display/unicode/communication%2binterfaces
    Message was edited by: Jason Lax (Removed link to deleted content)

  • Table Enhancement Category during upgrade from 4.7 to ECC 6.0

    When our sandbox was upgraded from 4.7 to ECC 6.0, Basis had the ABAP developers change the Enhancement Category on about 400 tables, some of which were custom tables.  The enhancement category was previously u2018not classifiedu2019 on these tables. 
    Is this really necessary?  Has anyone not changed the enhancement categories on tables that were flagged during the upgrade?  Also, what happens if we select the wrong enhancement category?

    Jane,
    This is what SAP says,
    Short Text
    Enhancement Category Selection
    Definition
    Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
    You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
    In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
    Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
    Cannot be enhanced
    The structure must not be enhanced.
    Can be enhanced or character type
    All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
    Can be enhanced or character-type or numeric
    The structure and its enhancement must not contain any deep data types (tables, references, strings).
    Can be enhanced in any way
    The structure and its enhancement may contain components whose data type can be of any type.
    Not classified
    This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
    The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
    If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
    If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
    If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
    If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
    If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.

  • BW specific task during R/3 upgradation from 4.7 to ECC 6.0

    Hi Everybody,
    We are planning R/3 upgrade from 4.7 to ECC 6.0.  We are using  BW 3.5 . So, Can anybody share BW 3.5 specific task during pre-upgrade as well as post-upgrade for ECC Upgrade.
    Thanks & Regards,
    Sushant N. Tiwarekar

    Hello ALex,
    There is not a must to upgrade also your solman 3.2 when you upgrade your satellites, only consider if you need the solman diagnostic or not and also that the new functionality in solman 4.0.
    Which system is unicode, the satellite?
    There is also not problems having a non-unicode solman with unicode satellites and the other, having a unicode-solman "linked" to unicode-satellites.
    Hope this helps,
    Dolores

  • Role of Time Mgmt functional consultant during SAP Upgrade from 4.7 to ECC6

    Hi,
    Could anyone explain the role of a time management functional consultant during SAP upgrade from R/3 4.7 to ECC6.0. Please provide me if you got any documentation.
    Thanks,
    Sunny

    "After you upgrade to SAP ERP 6.0, you can enhance the functionality of your application without performing a further
    upgrade thanks to a new deployment technology u2013 the SAP enhancement package for SAP ERP. The enhancement
    packages simplify the way you manage and deploy new software functions for SAP ERP." - that is the real benefit of ECC 6.0
    There aren't any major changes to PTM functionalities from 4.7 to 6.0. I hope your system is already using IT 2006 instead of IT 0005. Under functional role, you are required to configure/test any functional upgrade and manage data.
    Regards
    Yash

Maybe you are looking for