Attribute 'Unicode checks active'

Hi,
we just made an upgrade from 4.6 to ECC 6.0.
The unicode conversion check and the unicode conversion itself is done.
Each Abap program that has the attribute 'Unicode checks active' not checked ( off ), is causing a syntax error in the new system. Up till now we manually adjusted each attribute of each program, just to get the basic business transactions running.
My question is: what went wrong, and what is the best way of solving all this errors at once ?
Thanks in advance,
Rolf

Rolf,
I'm using ECC 6.0. I tried to do what you suggested for setting unicode flag active for a bunch of programs. Unfortunatelly, I'm bumping in the following problem:
I run UCCHECK and I get "green light" for some objects that don't have unicode flag active yet. So I click on the correspondent line and after on "Set Unicode Attribute" button. I get a pop-up saying that unicode is set active and program is written into a transport request... i click on OK. Another pop-up comes up. "Set Unicode Flag?", I click on Yes. Then, another pop-up comes up saying "Set Flag for Error-Free Programs Only?". I tried Yes, and I get this information message "The current system is not the original system". I tried also NO, but same message is shown.
Any idea on how to get it right?
Thanks.

Similar Messages

  • Unicode Check Active

    Hi All,
             I want to know about "Unicode Check Active" in ABAP Editor Program Attributes.I don't know anything about this.I want to know
    What is Unicode Check Active.
    How to Activate this Check Box.
    what is meant by Code Pages.
    What is UTF-8 UTF-16 & UTF-32.
    What is the Use of It.
    In ABAP Code the Unicode Check Doesn't Support the some syntax like Open Data set and Describe Lines like that what are all the syntax in ABAP it doesn't support.
    Can anybody give me the clear idea about this.So, it will be very helpful to me.This is very urgent.Surely i will reward more points.
    Thanks,
    Swapna.

    Hi,
    Unicode Check is one of the latest enhancement in SAP which has been done so as to provide SAP product in almost all the language that is spoken in the world.
    A program as to be made Unicode check Active in its attribute so that it can be used in Unicode enabled SAP system.
    what is unicode?
    From Release 6.10, ABAP supports multi-byte coding for characters in Unicode. Prior to Release 6.10, ABAP used only character sets that were based on single-byte codes – such as ASCII and EBCDIC – or double-byte codes, such as SJIS and BIG5.
    what is unicode enabled program?
    A Unicode-enabled ABAP program is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system as in a Unicode system .In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
    Type of errors in unocode check.
    This switch to Unicode affects all statements where an explicit or implicit assumption is made about the internal length of a character. If you use these statements in a program that is designed to exploit the Unicode capabilities of the runtime environment, they must be checked and changed if necessary. Once a Unicode-enabled program has been changed accordingly, it behaves in the same way in both Unicode and non-Unicode systems. You can develop programs in a non-Unicode system (NUS) and then import them into a Unicode system
    UNICODE CHECK ACTIVE:
    You need to use the transaction UCCHECK.
    The report documentation is here
    ABAP Unicode Scan Tool UCCHECK
    You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.
    Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.
    Selection of Objects:
    The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:
    PROG Report
    CLAS Class
    FUGR Function groups
    FUGX Function group (with customer include, customer area)
    FUGS Function group (with customer include, SAP area)
    LDBA Logical Database
    CNTX Context
    TYPE Type pool
    INTF Interface
    Only Examine Programs with Non-Activated Unicode Flag
    By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.
    Only Objects with TADIR Entry
    By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.
    Exclude Packages $*
    By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.
    Display Modified SAP Programs Also
    By default, SAP programs are not checked in customer systems. If you also want to check SAP programs that were modified in a customer system (see transaction SE95), you can activate this option.
    Maximum Number of Programs:
    To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:
    Call transaction SAMT
    Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH
    For further information refer to documentation for transaction SAMT.
    Displaying Points that Cannot Be Analyzed Statically
    If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.
    To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.
    Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).
    Applikation-Specific Checks
    These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.
    View Maintenance
    Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.
    UPLOAD/DOWNLOAD
    The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.
    Reward Points if found helpfull..
    Cheers,
    Chandra Sekhar.

  • Unicode Check Active For SAP Script

    How to set Unicode Check Active attribute for SAP Script and Smartform

    Hello,
    the Unicode Check Active flag is a program attribute. You can set this flag to check the syntax of an ABAP program. It is not available for SAPScript forms or SAP Smartforms. The attached screenshot shows how the flag is set in the attributes of an example program.
    Best Regards

  • Include programs are not having Unicode checks active check box ?

    Hi all,
    Why the Include programs are not having Unicode checks active check box ?
    Thanks in advance
    KR

    >
    KR wrote:
    > Hi all,
    >
    > Why the Include programs are not having Unicode checks active check box ?
    >
    > Thanks in advance
    > KR
    Hi KR,
    First of all, Because of include programs not executable by any where, its mandatory to attach all the includes to one main program which is to be usefull for business or enduser purpose. Here only unicode concept will occurs whether the server is being used in only one country or many. if its used in only one country no need to go for unicode active checks, iff the server is used in more than one country, its mandatory to go for unicode checks active.
    Regards
    Arani Bhaskar

  • Unicode checks active

    Whts is Unicode Prgram.Why do we select Unicode checks active?
    Plz guide

    Refer to the below related threads
    what is unicode
    unicode
    unicode
    unicode

  • Question Regarding Unicode Checks

    Hi Abapers,
                          What is Need of Transaction:UCCODE, what are the things which i need to check after giving the program name , and executing , what sholud be the out come ...  negative means what will happen....
                        positive means what will happen.....
    With Regards
    Bhaskar Rao.M

    Hi,
    Transaction code is UCCHECK.
    ABAP Unicode Scan Tool UCCHECK
    You can use transaction UCCHECK  to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.
    Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.
    Selection of Objects:
    The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:
    PROG Report
    CLAS Class
    FUGR Function groups
    FUGX Function group (with customer include, customer area)
    FUGS Function group (with customer include, SAP area)
    LDBA Logical Database
    CNTX Context
    TYPE Type pool
    INTF Interface
    Only Examine Programs with Non-Activated Unicode Flag
    By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.
    Only Objects with TADIR Entry
    By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.
    Exclude Packages $*
    By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.
    Also Examine Modified SAP Programs
    By deafult, SAP programs are not checked in customer systems. If you want to check SAP programs that were modified in customer systems (see transaction SE95), you can activate this option.
    Maximum Number of Programs:
    To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:
    - Call transaction SAMT
    - Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH
    For further information refer to documentation for transaction SAMT.
    Displaying Points that Cannot Be Analyzed Statically
    If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.
    To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.
    Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).
    Applikation-Specific Checks
    These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.
    View Maintenance
    Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.
    UPLOAD/DOWNLOAD
    The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.
    Regards,
    Sruthi

  • Getting errors while conversion of  ABAP program into Unicode check

    Hi,
    I changed the one ABAP program for some requirement and try to save it, it is giving error that the program is not unicode compatible.I set the unicode checks active box  under Attributes and again activate it .It is not allowing to concatenate the two variables which is declared as follows :
    constants: c_tab    type x value '09',      "tab character
                      c_cr     type x value '0D'.       "carriage return character
    I tried to use field symbols but still giving error (code after change)
    constants: c_tab    type x value '09',      "tab character
                      c_cr     type x value '0D'.       "carriage return character
    field-symbols : <f_c_tab> type any,
                            <f_c_cr> type  any.
    Assign c_tab to <f_c_tab> CASTING type c.
    Assign c_cr  to  <f_c_cr>  CASTING type c.
    error :The length of "C_TAB" in bytes must be a multiple of the size of a Unicode character (regardless of the size of the Unicode character).
    pls guide me so that I can cancatenate the c_tab and c_cr variables

    Hi,
    Tab Character ----->Data: tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
    Carraige Return---->Data : cr(2)  type c value cl_abap_char_utilities=>cr_lf..
    You will not be able to use the concatenate statement for hexadecimal variables in unciode system.
    Try using the above equivalent character variables. In unicode system avoid using hexadecimal variables wherever possible
    Regards,
    lakshman.

  • Regarding updating unicode check flag to all z* programs at once

    Hi  all,
    We are upgrading from 4.7 to ecc 6.0   ,
    we have created one pilot  server  where we  have installed  ecc 6.0 and  all prduction data is copied on it .
    OUR basis team has done that process and  it is done with unicode check  active  ,
    But   all Z  programs  such as few  customs programs  are still non-unicode  as they are old programs  so want
    to update unicode check flag which is pressent in attributes of program .
    MANUALly you can do for each program and activate  that i know  ,but how to do it all at once  .
    Because when we Excecute  UCCheck  we  get all programs   which are nonunicode   , in which it shows that programs The system found no Unicode syntax errors . whichneeds to be just do unicode check flag active and activate the program  .
    How that can be done  at once all .
    Regards
    Deepak.

    Hi ,
    My problem is solved  ....
    i found that  after executing  UCCHECK transaction code  ,in display  you will find one button on rigth side
    "set unicode attribute"   .  after selecting no of programs at once we can  press that butoon .
    The Unicode flag is set for the selected programs. The programs are
    written into interactively selectable transport requests and generated.
    You must later release the transport requests.
    I hope this will be helpfull to all.
    Regards
    Deepak.

  • Unicode Checks for Include Types

    Hi All,
    How can we check for the Unicode checks in Include Programs?
    If a Executable program which has got its unicoide checks active flagged and which calls an include in it,
    Will the include program also have the unicode check active in it?
    Or is it determined in any other way?
    In general how does an include program react for unicode checks in the call program.
    Thanks in advance,
    Sai

    Hi Rainer,
    Where do i find  the include is unicode checked or not?
    If i go to the attributes of an include i dont find the unicode checks active displayed for it.
    Is there any other  way of determining it?
    Or the include's unicode check is dependent on that of the calling program.
    Thanks,
    Sai

  • Activating Unicode check at global/workbench level

    In order to Unicode-enable at the ABAP level, you need to check the box "Activate Unicode check" in the attributes of your ABAP program.
    I would like to know whether its possible to do the same at a global level.

    Hi!
      Installing a R/3 Unicode System and activating your ABAP Program for Unicode Check are two different things.
      First if you want a complete R/3 system with Unicode Active, then you should have a Unicode Kernel & Unicode Database and the decision whether you want it to be unicode is decided during R/3 Installation.
      Secondly, Irrespective of whether you have a Unicode or Non-Unicode System, your ABAP programs can be activated for Unicode Check.The only condition is that if you have a Non-Unicode R/3 system you can Check or Uncheck the box for Unicode in the ABAP Program Attributes.Whereas if you have a Unicode System then in the ABAP program attributes it needs to be turned on for all ABAP Programs for the system to check for unicode syntaxes.
      I understand your initial question was to Activate "n" ABAP Programs for Unicode all at one place instead of doing each one at the Program attributes.
    I believe this is how unicode works!
       Pl look at the topic
       "Unicode-Enabling of ABAP Programs"
    in
    https://www.sdn.sap.com/sdn/developerareas/abap.sdn
    for detailed understanding, if you have not seen it yet.
    Gisk

  • Isn't unicode check defaulted in ECC 6.0 ?

    I see a checkbox called unicode check box in the attributes when I create the ABAP program. This check is to make sure that during sytanx check the system will perform unicode check.
    Now, I had an assumption that this check box is used only when you are executing programs on lower level of SAP like SAP 4.6C or 4.7 to ensure that programs are checked for unicode check.
    But, I see that in ECC 6.0 also if you don't use this check box the system will bypass the unicode check. I thought that in ECC 6.0 , unicode check is done by default, but it does not sound like that .
    Can someone throw some light on this ?
    Regards,
    Rajesh.

    Hello Rajesh
    I do not think so. You could do the following test on your system (Unicode or non-Unicode?):
    Write a simple ABAP report and try move data between a structured and an unstructured variable, e.g.:
    DATA: gd_string    TYPE string.  " unstructured, C-container
    DATA: gs_kna1     TYPE kna1.
    SELECT SINGLE * FROM kna1 INTO gs_kna1.
    gd_string = gs_kna1.  " should give Unicode error -> use instead cl_abap_container_utilities class
    Regards
      Uwe

  • JSF- view with no key-attributes cannot be activated

    Hi,
    i have a view Called Globals with 2 transient varibales , when i open many sessions at the same time and work with them , i got error
    JBO-30003: The application pool (model.PlacingModuleLocal) failed to checkout an application module due to the following exception:oracle.jbo.JboException: JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-25052: ViewObject Globals with no key-attributes cannot be activated!
    each attribute of the view have
    Updateable = Always
    Queyable is Checked
    Passivative is checked
    in the view properties, tab Tuning => No Rows
    and "Fill Last Page " and "Passivate State " and "Including All Transient Variables"
    all the 3 are checked
    the view is NOT based on Entity Object
    i use this view for holding data from SelectOneListBox
    should i modify the view by any way ?
    By The Way this view is exactly the same in SRDemo
    Any Suggestions?
    thanks....

    hi,
    answer is here
    http://www.oracle.com/webapps/online-help/jdeveloper/10.1.2/state/content/navId.4/navSetId._/vtTopicFile.bc4jjavadoc%7Crt%7Coracle%7Cjbo%7CCSMessageBundle~html/
    and it says
    JBO-25052: JboException
    Cause: A ViewObject with no key attributes has transient passivatable attributes. This type of ViewObject cannot participate in passivation/activation.
    Action: Set one or more attributes as key attributes for this ViewObject
    that means that SRDemo may have a little bug which is any attribute should be key attr in Globals view

  • How to activate unicode check flag

    How do we activate the "unicode check" flag for programs generated by workflow objects.

    Hi ,
    My problem is solved  ....
    i found that  after executing  UCCHECK transaction code  ,in display  you will find one button on rigth side
    "set unicode attribute"   .  after selecting no of programs at once we can  press that butoon .
    The Unicode flag is set for the selected programs. The programs are
    written into interactively selectable transport requests and generated.
    You must later release the transport requests.
    I hope this will be helpfull to all.
    Regards
    Deepak.

  • Wat is the importance of unicode check

    hi
    when i m creating program using se38 in attributes i found unicode check box.. can any body tells the importance of this check box..
    thanks...

    hi..
    Before release 6.10, SAP software used character sets based on codes such as ASCII and EBCDIC. In these codes, every character is displayed by one byte; therefore character sets like these are also called single-byte codepages. Since they are only one byte, a maximum of only 256 characters was possible. Due to this, each language had its own character set or this character set was suitable for only some languages. There are also other languages such as Japanese ,Chinese etc which required 2 byte since one byte is not sufficient for displaying all the character set of an East Asian languages, so double-byte codepages are used in which every character consists of one or two bytes.
    u2022     ASCII (American Standard Code for Information Interchange) encodes each character using 1 byte = 8 bit. This makes it possible to represent a maximum of 28 = 256 characters to which the combinations [00000000, 11111111] are assigned.
    u2022     EBCDI (Extended Binary Coded Decimal Interchange) also uses 1 byte to encode each character, which again makes it possible to represent 256 characters.
    u2022     Double-byte code pages require 1 or 2 bytes for each character. This allows you to form 216 = 65536 combinations where usually only 10,000 - 15,000 characters are used.
    Using these character sets, you can account for each language relevant to the SAP System. However, problems occur if you want to merge texts from different incompatible character sets in a central system. Equally, exchanging data between systems with incompatible character sets can result in unprecedented situations.
         Unicode is a universal encoded character set that allows you to store information from any language using a single character set.
         Unicode provides a unique code for every character, independent platform, program or language.
    i think u ll get some idea regarding unicode ..

  • Errors in unicode check

    Plz tell me wht type  of errors might occur while doing unicode check?
    Plz tell me wht is unicode and unicode check

    hi pavan,
    <b>what is unicode?</b>
    From Release 6.10, ABAP supports multi-byte coding for characters in Unicode. Prior to Release 6.10, ABAP used only character sets that were based on single-byte codes – such as ASCII and EBCDIC – or double-byte codes, such as SJIS and BIG5.
    <b>what is unicode enabled program?</b>
    A Unicode-enabled ABAP program  is a program in which all Unicode checks are effective. Such a program returns the same results in a non-Unicode system  as in a Unicode system .In order to perform the relevant syntax checks, you must activate the Unicode flag in the screens of the program and class attributes.
    <b>Type of errors in unocode check.</b>
    This switch to Unicode affects all statements where an explicit or implicit assumption is made about the internal length of a character. If you use these statements in a program that is designed to exploit the Unicode capabilities of the runtime environment, they must be checked and changed if necessary. Once a Unicode-enabled program has been changed accordingly, it behaves in the same way in both Unicode and non-Unicode systems. You can develop programs in a non-Unicode system (NUS) and then import them into a Unicode system (US).
    <b>Hope this is helpful, Do reward points.</b>

Maybe you are looking for