Skip to Content
author's profile photo Former Member
Former Member

use HIDE in Function Module.

Hi expert,

When I using HIDE in my function module, i got an error message said that

"You cannot use HIDE with a local field". How can this happen and what can i do?

Pls advise. Thanks.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

3 Answers

  • Best Answer
    Posted on Nov 21, 2007 at 04:24 AM

    You need to define that field in the TOP include of the function module.



    The data definition should be inside the TOP includ of the FM



    Naimesh Patel

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 04:27 AM



    <b>ABAP Unicode Scan Tool UCCHECK</b>

    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.

    <b>Selection of Objects:</b>

    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:

    <b>PROG Report</b>

    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

    <b>Only Examine Programs with Non-Activated Unicode Flag</b>

    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.

    <b>Only Objects with TADIR Entry</b>

    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.

    <b>Exclude Packages $*</b>

    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.

    <b>Also Display Modified SAP Objects</b>

    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.

    <b>Maximum Number of Programs:</b>

    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 *).

    <b>Applikation-Specific Checks</b>

    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.

    <b>View Maintenance</b>

    Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.


    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.


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 21, 2007 at 04:27 AM

    sorry ignore this one

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.