Generated constructor in exception classes - ommitted textid in superclass

Hi,
debugging another program i stopped in the constructor of one of my own exception classes. Starring at the code one questoion arised
method constructor.
call method super->constructor
exporting
textid = textid
previous = previous
if textid is initial.
   me->textid = zcx_xi .
endif.
me->errortext = errortext .
me->sysid = sysid .
endmethod.
First of all i would use
if textid is *supplied*.
   me->textid = zcx_xi .
endif.
But this is not my question. If i'm raising this exception without supplying the textid the superclass is call with an initial textid, which is filled later pn with the predefined class named textid.
If i'm raising this exception specifying the textid as
raise exception type zcx_xi exporting textid = zcx_xi=>zcx_xi errortext = message.
the super class will not get an intial textid but the predefined one.
Both versions are working well delivering the errortext by the get_text( ) method in the catch branch.
But... is there really no difference calling the super class with initial value or given value?

It looks like there is no difference.
This code replaces any existing TEXTID set by Super class when we don't pass any TEXTID.
IF textid IS INITIAL.
   me->textid = CX_SY_ZERODIVIDE .
ENDIF.
If the code uses the attribute TEXTID (me->textid) instead of the importing parameter TEXTID, than it would make a lot difference.
IF ME->textid IS INITIAL.   " Attribute TEXTID
   me->textid = CX_SY_ZERODIVIDE .
ENDIF.
I guess, we need some SAP Official response before going ahead.
Regards,
Naimesh Patel

Similar Messages

  • Create a Exception Class

    hi all ,,
    can any one tell me how to create a exception class in ABAP OOPS concept ??
    if possible can give link also for document

    HI Jayakumar,
    Please go thru this document
    Exceptions are represented by objects that are instances of exception classes. Defining an exception is, therefore, the same as creating an exception class.
    All exception classes must inherit from the common superclass CX_ROOT and one of its subordinate classes:
    CX_STATIC_CHECK
    CX_DYNAMIC_CHECK
    CX_NO_CHECK
    . The assignment of exception classes to one of these three paths of the inheritance hierarchy determines the way in which the associated exceptions are propagated. There is a record of predefined exception classes CX_SY_... whose exceptions are raised in error situations in the runtime environment. These classes all inherit from CX_DYNAMIC_CHECK or CX_NO_CHECK but not from CX_STATIC_CHECK (see hierarchy in the ABAP keyword documentation).
    All exception classes must begin with the prefix CX_. They are usually defined globally with the Class Builder of the ABAP Workbench. Local exception classes can, however, also be defined.
    Individual (abstract) exception classes that are used as the superclass of further exception classes can be defined. The exceptions of the subordinate classes can be handled together using a superclass.
    Exception classes have the following features:
    Constructor
    The constructor must have a predefined structure and a specific interface. With global classes, the Class Builder generates the correct constructor and sets it to an unchangeable status. The constructor has two IMPORTING parameters:
    TEXTID of the SOTR_CONC type
    This parameter can be used to determine which of your exception texts the exception will use.
    PREVIOUS of the CX_ROOT type
    This parameter can be used to assign the PREVIOUS attribute a previous exception.
    Methods
    In exception classes, you can define your own methods. The following two predefined methods are inherited from the root class CX_ROOT:
    GET_TEXT
    Sends back the exception texts of a class (controlled by the TEXTID attribute) as a string.
    GET_SOURCE_POSITION
    Returns the program name, the name of a possible include program, and the line number of the statement that raised the exception.
    Attributes
    The attributes of exception classes are used to transport additional information on an error situation to the handler. The main piece of information is, however, always the fact that an exception of a particular class has occurred. The following attributes are inherited from CX_ROOT:
    TEXTID
    Used to specify the exception of a class more precisely by using several exception texts. Is evaluated in the GET_TEXT method.
    PREVIOUS
    If an exception is mapped to another exception, a reference to the original exception can be defined in this attribute via the EXPORTING addition of the RAISE EXCEPTION statement and by means of the constructor IMPORTING PARAMETER with the same name. This can result in a chain of exception objects. In the event of a runtime error, the exception texts of all the exceptions in the chain are output. Mapping an exception to another exception is only beneficial if the context in which the original exception occurred is important for characterizing the error situation.
    KERNEL_ERRID
    The name of the associated runtime error is stored in this attribute if the exception was raised by the runtime environment, for example, COMPUTE_INT_ZERODIVIDE with a division by zero. If the exception is not handled, precisely this runtime error occurs.
    Parameters cannot be transferred to the constructor for this attribute. If the exception is raised with RAISE EXCEPTION, the attribute is set to initial.
    Global Exception Classes
    Global exception classes are defined and managed in the Class Builder. If the correct naming convention (prefix CX_) and the class type Exception Class is chosen when a new class is created, the Class Builder automatically becomes the Exception Builder.
    The Exception Builder offers precisely the functionality required to define exception classes and generates independently-defined components that must not be changed. When classes are created, the category of the exception must be specified, in other words, whether it is to inherit from CX_STATIC_CHECK, CX_DYNAMIC_CHECK, or CX_NOCHECK.
    Tab Pages of the Exception Builder
    The Exception Builder has the tab pages Properties, Attributes, Methods, and Texts.
    The properties do not normally need to be changed.
    Except for the four inherited attributes mentioned above, further public attributes can be generated by the Exception Builder. The contents of these attributes specify the exception more clearly and manage the exception texts.
    All of the methods are inherited from CX_ROOT. New methods cannot be added. The instance constructor is generated automatically. It ensures that, when an exception is raised, the attributes have the right values. It also transfers the text of the superclass for an exception class whose exception text is not specified explicitly.
    The instance constructor is generated on the basis of the attributes, which are set up on the basis of the exception texts. Changing the attributes in superclasses can, therefore, invalidate the constructors of subordinate classes. The constructors of subordinate classes can be regenerated under Utilities ® CleanUp ® Constructor.
    Texts are a special feature of exception classes and the Exception Builder. For further information, refer to Exception Texts.
    Local Exception Classes
    Local exception classes can be defined for specific exceptions that only occur within one single ABAP program. The condition for a local exception class is that it inherits from one of the three classes CX_STATIC_CHECK, CX_DYNAMIC_CHECK, or CX_NO_CHECK, or from their subordinate classes. An individual constructor and individual attributes can be created. Individual methods should not be created, however, and the methods of superclasses should not be redefined.
    Examples of Local Exception Classes
    report DEMO_LOCAL_EXCEPTION_1.
    class CX_LOCAL_EXCEPTION definition
                            inheriting from CX_STATIC_CHECK.
    endclass.
    start-of-selection.
        try.
          raise exception type CX_LOCAL_EXCEPTION.
        catch CX_LOCAL_EXCEPTION.
          message 'Local Exception!' type 'I'.
      endtry.
    This example shows a minimal local exception class, which is simply the local representation of one of the three direct subordinate classes of CX_ROOT. It can be used in the program.
    report DEMO_LOCAL_EXCEPTION_2.
    class CX_LOCAL_EXCEPTION definition
                            inheriting from CX_STATIC_CHECK.
      public section.
        data LOCAL_TEXT type STRING.
        methods CONSTRUCTOR importing TEXT type STRING.
    endclass.
    class CX_LOCAL_EXCEPTION implementation.
      method CONSTRUCTOR.
        SUPER->CONSTRUCTOR( ).
        LOCAL_TEXT = TEXT.
      endmethod.
    endclass.
    data OREF type ref to CX_LOCAL_EXCEPTION.
    start-of-selection.
        try.
          raise exception type CX_LOCAL_EXCEPTION
                          exporting TEXT = `Local Exception`.
        catch CX_LOCAL_EXCEPTION into OREF.
          message OREF->LOCAL_TEXT type 'I'.
      endtry.
    In this example, the exception class from the previous example is extended to include an individual attribute and constructor. The IMPORTING parameter of the constructor must be supplied when the exception is raised (it is required here). The attribute can be evaluated in the handler of the exception.
    report DEMO_LOCAL_EXCEPTION_3.
    class CX_LOCAL_EXCEPTION definition
          inheriting from CX_SY_ARITHMETIC_ERROR.
      public section.
        methods CONSTRUCTOR importing SITUATION type STRING.
    endclass.
    class CX_LOCAL_EXCEPTION implementation.
      method CONSTRUCTOR.
        SUPER->CONSTRUCTOR( OPERATION = SITUATION ).
      endmethod.
    endclass.
    data OREF type ref to CX_LOCAL_EXCEPTION.
    data TEXT type STRING.
    start-of-selection.
        try.
          raise exception type CX_LOCAL_EXCEPTION
                exporting SITUATION = `START-OF-SELECTION`.
        catch CX_LOCAL_EXCEPTION into OREF.
          TEXT = OREF->GET_TEXT( ).
          message TEXT type 'I'.
      endtry.
    In this example, an exception class is derived from one of the predefined exception classes for error situations in the runtime environment. An individual constructor is defined with an individual IMPORTING parameter that supplies the superclass constructor with this parameter. When the exception is handled, the exception text, as defined in the superclass, is read with GET_TEXT.

  • How to generate "constructor" for parameter object

    Hello,
    As part of my research project I need to find the "constructor" of a given
    parameter object.
    For example: Suppose we have the following method -
    public void int pop(Stack st) {
    //some code...
    I want to generate code that calls this method and its parameter with its
    constructor. Like -
    pop(new Stack(10));
    As you can see I need to return a valid instance of the parameter to the
    method (null wont do).
    I dont know what library or API to use for this purpose.
    Your help is highly appreciated.
    Thanks,
    Fayezin

    That's not a great example. If you have a Stack class, then pop() should be a method on that class, not some other class. And if you created a new Stack object, then presumably it would be empty, so popping it should cause an exception.
    Anyway, if you want to get the constructor of a class, use Introspection. There may be a better solution though, depending on what you're actually trying to accomplish.

  • Get the values from Exception class

    Hi all ..
    In class i have raised one exception
    when i catch this exception in my program i m able to get the
    error message but i need to get all the parameters that i pass
    when i raise the exception ...
    i have raised like this
          RAISE EXCEPTION TYPE cx_bapi_error
            EXPORTING
              textid = cx_bapi_error=>cx_bo_error
              class_name = 'ZHS_'
              log_no = wa_bapi_return-log_no
              log_msg_no = wa_bapi_return-log_msg_no
              t100_msgid = wa_bapi_return-id
              t100_msgno = wa_bapi_return-number
              t100_msgv1 = wa_bapi_return-message_v1
              t100_msgv2 = wa_bapi_return-message_v2
              t100_msgv3 = wa_bapi_return-message_v3
              t100_msgv4 = wa_bapi_return-message_v4
              STATUS = lt_status
    and caught the exception like this in my program
        CATCH cx_bapi_error INTO go_error.
          gd_text = go_error->get_text( ).
          EXIT.
      ENDTRY.
    in this i m just getting the class name which i have passed in exception
    i need all other parameters that i have passed ..
    if u have any idea pls let me know ..
    Thanks in advance ...

    Hello Jayakumar
    Usually the attributes of standard exception classes are defines as <b>public</b> and <b>read-only</b>. Thus, you should be able to use the following coding:
    DATA:
      go_error   TYPE REF TO cx_bapi_error.  " specific exception class !!!
    TRY.
    RAISE EXCEPTION TYPE cx_bapi_error
    EXPORTING
    textid = cx_bapi_error=>cx_bo_error
    class_name = 'ZHS_'
    log_no = wa_bapi_return-log_no
    log_msg_no = wa_bapi_return-log_msg_no
    t100_msgid = wa_bapi_return-id
    t100_msgno = wa_bapi_return-number
    t100_msgv1 = wa_bapi_return-message_v1
    t100_msgv2 = wa_bapi_return-message_v2
    t100_msgv3 = wa_bapi_return-message_v3
    t100_msgv4 = wa_bapi_return-message_v4
    STATUS = lt_status.
    CATCH cx_bapi_error INTO go_error.
    gd_text = go_error->get_text( ).
    WRITE: go_error->t100_msgid,  " perhaps the attributes have different name
                go_error->t100_msgno, " check attribute names in SE24
    EXIT.
    ENDTRY.
    Regards
      Uwe

  • DAC ERROR EXCEPTION CLASS::: java.lang.NullPointerException

    hello guru,
    when i creating a execution plan in my local envt for testing
    I have assemble the subject area
    but while building the execution plan i am getting below error:
    SHTEST-TEST
    EXCEPTION CLASS::: java.lang.NullPointerException
    com.siebel.analytics.etl.execution.ExecutionParameterHelper.substituteNodeTables(ExecutionParameterHelper.java:174)
    com.siebel.analytics.etl.execution.ExecutionParameterHelper.parameterizeTask(ExecutionParameterHelper.java:141)
    com.siebel.analytics.etl.execution.ExecutionPlanDesigner.getExecutionPlanTasks(ExecutionPlanDesigner.java:738)
    com.siebel.analytics.etl.execution.ExecutionPlanDesigner.design(ExecutionPlanDesigner.java:1267)
    com.siebel.analytics.etl.client.util.tables.DefnBuildHelper.calculate(DefnBuildHelper.java:169)
    com.siebel.analytics.etl.client.util.tables.DefnBuildHelper.calculate(DefnBuildHelper.java:119)
    com.siebel.analytics.etl.client.view.table.EtlDefnTable.doOperation(EtlDefnTable.java:169)
    com.siebel.etl.gui.view.dialogs.WaitDialog.doOperation(WaitDialog.java:53)
    com.siebel.etl.gui.view.dialogs.WaitDialog$WorkerThread.run(WaitDialog.java:85)
    can anyone help on this.
    thanks

    Hello Shiva,
    I have tried to generate the paramenter index in going into execute tab.
    Acutally I have two database one is SH(for sales fact table) as source and other is SHTST (for target w_sales_F).
    when i go into that it try to click on generate button it shows only for SHTST not for SH
    more over in SHTST the value is coming as Informatica folder Sales where i created all mapping.
    SH and SHTST both are in same database oracle 10g.
    please help

  • Exception class help

    Hi,
    i create exception class like it write in the sap help and when i want to send the exception with parameters to the ABOVE METHODS i don't susses  i just get the message without the parameter ?
    there is simple guideline how o transfer the exception with parameters?
    br
    Ricardo

    HI Uwe,
    Thanks,
    This is my sample code:
    This is the first method on the tree:
    the method name is create .
    INSERT (lt_table_name) FROM <ls_obj>.
        IF sy-subrc <> 0.
          RAISE EXCEPTION TYPE /cx_db_db_error
            EXPORTING
              textid     = cx_db_error=>create_failed
              table_name = lt_table_name.
        ENDIF.
    this method call to the above method - create .
    TRY.
            CALL METHOD lo_obj_create->create
              CHANGING
                is_bound_object = ls_obj_user.
          CATCH cx_db_error INTO lo_exc.
            "Create user failed. Throw an exception.
            RAISE EXCEPTION TYPE cx_db_error
              EXPORTING
                textid     = cx_db_error=>create_user_error
                previous   = lo_exc.
            result = lo_exc->get_text( ).
        ENDTRY.
    here in result i just get the massage without the table name that i export in the first method ,what i miss here ?
    Best Regards
    Ricardo

  • Creating own Exception class

    In my past paper it says...
    Show how to create your own Exception class that derives from class Exception. The class should provide a default constructor which allows a "My Error message" message to be set, and a second constructor which has as an argument the error message. 4-MARKS
    Does this look right..?
    public class MyExcep extends Exception
         public MyExcep()
              super("My Error Message");
         public MyExcep(String message)
              super(message);
    }

    Yes. Do I get 4 marks now? or is it Four Marks?

  • Clientgen does not generate service specific exceptions

    Hi,
    When we use clientgen to generate client stubs and on exploding the generated
    _client.jar file we find that only the first service specific exception following
    RemoteException is being generated. All other exceptions seem to be missing. Here
    is an example of a sample service method:
    void actionWorkitem(WSCredentials credentials, String workitemUri, String action)
    throws RemoteException, WorkflowException, SameStateException;
    Here the last exception (i.e:SameStateException which is a service specific exception
    ) is missing in the generated client jar file.
    Is this a bug ?
    Any help in this issue is appreciated.
    Thanks,
    Anu.

    We are using 7.0.2. Do you acknowledge this as a bug?
    Also to add to the problem. If we use the clientgen generated stubs to make a
    soap call on the mentioned operation
    void actionWorkitem(WSCredentials credentials, String workitemUri,String action)
    throws RemoteException, WorkflowException, SameStateException;
    which would actually throw a SameStateException, the exception message comes
    as WorkflowException (which was the only exception class correctly generated by
    the clientgen.)
    This means the generated stubs wrap messages from all the service-specific exceptions
    into one service specific exception. This looks like a bug too.
    Thanks
    Puneet
    "manoj cheenath" <[email protected]> wrote:
    Which version of WLS?
    Please try out WLS 8.1 SP1. There are many fault related
    bug fixes done in SP1.
    Regards,
    -manoj
    http://manojc.com
    "Anu Alwar" <[email protected]> wrote in message
    news:3f329454$[email protected]..
    Hi,
    When we use clientgen to generate client stubs and on exploding thegenerated
    _client.jar file we find that only the first service specific exceptionfollowing
    RemoteException is being generated. All other exceptions seem to bemissing. Here
    is an example of a sample service method:
    void actionWorkitem(WSCredentials credentials, String workitemUri,String action)
    throws RemoteException, WorkflowException, SameStateException;
    Here the last exception (i.e:SameStateException which is a servicespecific exception
    ) is missing in the generated client jar file.
    Is this a bug ?
    Any help in this issue is appreciated.
    Thanks,
    Anu.

  • Making Own Exception Class

    Hi all,
    I m trying to make a new exception class which will be called when when any sort of exception occurs.After throwing that class how can i call other exception in that class eg. if in a class if sqlexception occurs & i m throwing myclass so how can i catch sqlexception in myclass.

    if in a class if sqlexception occurs & i m throwing myclass so how can i catch sqlexception in myclass.
    you can throw your class object only when you catch the original exception. so pass the oroginal exception object in the constructor of your exception class.
    hope you get what i mean.
    - Azodious

  • Each exception class in its own file????

    Hi, I am still quite new to java, and I don't fully understand exceptions. Could you please tell me if for each exception class you require do you have to have a a seperate file. e.g. I'm creating my own array exceptions classes.
    The following is the structure:
    ** The base array exceptions class
    public class arrayException extends Exception {
    public arrayException () { super(); }
    public arrayException (String s) { super(s); }
    ** The outofboundsArrayException
    public class outofboundsArrayException extends arrayException {
    public outofboundsArrayException ()
    { super("Number entered is out of bounds"); }
    public outofboundsArrayException (String s)
    { super(s); }
    ** The fullArrayExceptiom
    public class fullArrayException extends arrayException {
    public fullArrayException ()
    { super("The array is full"); }
    public fullArrayException (String s)
    { super(s); }
    So will the three classes above need their own file.
    I wanted to also know what the super does. I thought when the exception was raised, the text message in the super method is outputted, but i've tested that and it doesn't output (e.g. the error message "The array is full" doesn't output). The only thing that outputs is what you put in the catch part.
    Thank You very Much!

    Could you please tell me if
    for each exception class you require do you have to
    have a a seperate file.Yes. Exception classes are like any other public class in Java, in that it must be in its own file with the standard naming conventions.
    I wanted to also know what the super does. I thought
    when the exception was raised, the text message in
    the super method is outputted, but i've tested that
    and it doesn't outputsuper([0,]...[n]) calls a constructor in the superclass of your current class matching the signature super([0,]...[n]). In this particular case, the Exception's message property is being set by the parent constructor. If you were to leave out super([0,]...[n]), the default no-arg constructor of the superclass would be invoked, and the message would not be set.
    Use the getMessage() method of the Exception class to return the message value in later references to your object.

  • Wsdl2service exception class: case sensitive problem

    When I run wsdl2service on my .wsdl, file the generated class is a different case than the class name(CatalogException vs catalogException). The exception classes will not compile. Any ideas?
         <wsdl2service
         wsdl="ws_20/CatalogQueryService.wsdl"
         destDir="${src_gen}"
         typeMappingFile="${autotype}/types.xml"
         packageName="mil.dcgs.mdf.webservice"
         generateImpl='true'>
         <classpath refid='project.classpath'/>
         </wsdl2service>
    ================================================
    [wsdl2service] Generating web service from wsdl ws_20/CatalogQueryService.wsdl
    [wsdl2service] C:\views\dib\DIB\src_gen_mort\mil\dcgs\mdf\webservice\catalogException.java:9: class CatalogException is public, shou
    ld be declared in a file named CatalogException.java
    [wsdl2service] public class CatalogException extends java.lang.Exception
    [wsdl2service] ^
    [wsdl2service] C:\views\dib\DIB\src_gen_mort\mil\dcgs\mdf\webservice\dataAccessException.java:9: class DataAccessException is public
    , should be declared in a file named DataAccessException.java
    [wsdl2service] public class DataAccessException extends java.lang.Exception
    [wsdl2service] ^
    [wsdl2service] 2 errors
    [wsdl2service] java.io.IOException: Compiler failed executable.exec
    [wsdl2service] at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
    [wsdl2service] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    [wsdl2service] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    [wsdl2service] at weblogic.webservice.tools.build.internal.CompilerHelper.compileFiles(CompilerHelper.java:80)

    Windows filenames are not case-sensitive. So you can't have both EventSite.class and eventsite.class in the same directory. What you see there probably also involves Windows 98's habit of messing with the capitalization of file names (try creating a directory with the name of IBM, not Ibm).

  • Errors with CF 8.0.1 hotfix 3 and hotfix 4, "Object Instantiation Exception.Class not found"

    We need to get our servers up to date with the latest ColdFusion hotfixes in order to pass our security scans and policies. We have been following the Adobe instructions for installing the hotfixes, but we’re getting the same errors each time. The CF 8 hotfix 2 works fine, but once we install hotfix 3 and/or hotfix 4, we get the following errors:
    "Object Instantiation Exception.Class not found: coldfusion.security.ESAPIUtils The specific sequence of files included or processed is: C:\ColdFusion\wwwroot\WEB-INF\exception\java\lang\Exception.cfm, line: 12 "
    coldfusion.runtime.java.JavaObjectClassNotFoundException:
    We have dozens of servers running Windows XP, Netscape Enterprise Server 6.1 (I  know, don’t laugh), ColdFusion 8,0,1,195765, and Java Version 1.6.0_04. Just about  the only good thing about running XP on our servers is that it matches  our development boxes, so we have almost mirrored environments for dev,  test, and production. We do NOT have the CF install with the J2EE configuration.
    The crazy thing is, on tech note 51180 (http://kb2.adobe.com/cps/511/cpsid_51180.html), it says that the fix for bug # 71787 (Fix for "Object Instantiation Exception" thrown when calling a Java object constructor or method with a null argument under JDK 1.6.) was added in cumulative hotfix 2. However we don’t see this problem until we go to hotfix 3 (or 4).
    I’ve also been reading that other people had this same problem, and that the CF 8 hotfix 3 was not compatible with certain versions of JDK, then when you read the Adobe site for CF 8.0.1 hotfix 3, it says “Added the updated cumulative hotfix to make it compatible with jdk 1.4.x, 1.5.x and 1.6.x.”, so that makes me think that Adobe was supposed to have fixed this CF 8.0.1 hotfix 3 JDK incompatability issue - but unfortunately it's still not working for us. We have followed the instructions for removing the jar files and starting/restarting the CF server as directed, we’ve tried this 5-6 times, and still no luck.
    Recommendations? Seems like this is a ColdFusion bug to me – one that says is fixed on the Adobe site, but is not fixed in our environment. Please advise, thanks.

    For what it's worth, we had an MXUnit user describe a similar, though not identical, problem after installing the latest hotfixes. In his case, he's getting "NoSuchMethodExceptions".

  • Own ZCX Exception Class, how to translate

    Hi,
    i've written my own ZCX_XYZ exception class. On the tabstrip "Texts" i've entered some texts, but how can i translate those texts? When i'm going to Goto/Translations i'm just getting empty object list...

    Thanks for investigating again. Using SE63_OTR i'm getting the message that this is obsolet and i have to use SE63.
    To make things more clearer i made some screenshots.
    <a href="http://666kb.com/i/atri3x4ib1uryogzr.png">Class with Attributes</a>
    So i have a class ZCX_FTP, the superclass is CX_DYNAMIC_CHECK, and i have an attribut which was generated automatically with the same name of the class.
    The texts are as follows:
    <a href="http://666kb.com/i/atri6gk1z8qn3ff9j.png">Defined Text</a>
    So now i'm going to SE63 (BTW are these texts otr short texts or long ones?), entered the ID and pressed Edit:
    <a href="http://666kb.com/i/atri82j1b5x02q7ev.png">SE63 with ID</a>
    I'm getting Object does not exists....
    Logging on with different language might be a workaround with de/en, but i have some difficulties navigating inswedish, greek, france and half a dozen more languages. On the other hand, i do not want to hand over the source texts to those who translates the texts. I'm really lost in this and cant find online help/documentation dealing with this.

  • How to enhance exception class based on CX_ROOT

    I have created an exception class based on CX_ROOT (or CX_STATIC_CHECK, CX_DYNAMIC_CHECK). Now, I need to enhance its "constructor" method with my own parameters. How can I do this? Currently system does not allow this. But, I have seen many other exception classes enhanced the way I want? Any idea?
    Any pointers will be helpful.
    Regards, Neetu

    Hello Neetu
    Two steps are required to get additional IMPORTING parameters in the CONSTRUCTOR method of your exception class:
    (1) Create exception IDs (tabstrip Texts )
    Example:  ID=ZCX_SDN_CLASS, text=Invalid data type for field &FIELD& on screen &SCREEN& &REPORT&
    (2) Add corresponding instance attributes (read-only) to your exception class
    Examples: attributes FIELD, SCREEN, REPORT
    Now the CONSTRUCTOR has the additional IMPORTING parameters FIELD, SCREEN and REPORT.
    If you raise your exception class using id=ZCX_SDN_CLASS then the wildcards (e.g. &FIELD& in the text) will be replaced by IMPORTING parameter FIELD.
    Regards
      Uwe

  • What are exception class and persistant class?

    hi,
    what are exception class and persistant class?
    how are they different from the normal class?
    Regards,
    Anil

    Hii!
      Persistent Classes
    To use the Persistence Service for objects, the classes of these objects must be created as persistent classes in the Class Builder. The term persistent class does not imply that a class is persistent. (As a template for objects, every class is persistent). Rather, it means that the objects of that class and their state are managed by the Persistence Service. For example, the objects of these classes are instantiated in the ABAP program with a method of the Persistence Service, which ensures that the initialization is correct (not with the usual CREATE OBJECT statement). When the Class Builder creates a persistent class, it automatically generates an associated class, known as the class actor or class agent, whose methods manage the objects of persistent classes. As well as their identity, persistent classes can contain key attributes, which allow the Persistence Service to ensure that the content of each persistent object is unique.
      Check out this link
    http://www.sapnet.ru/abap_docu/ABENABAP_EXCEPTION_CLASSES.htm
    Regards
    Abhijeet

Maybe you are looking for

  • IF Statement in Queries

    Can we use an "if then else" statemtent in a query such that it executes particular query depending on the condition specified on a UDF? That is, if condition = true, then execute query1 else if condition = false then execute query2. How do we write

  • Could not be saved

    When I try to save a PDF file I get an error message that says: The document could not be saved. There was a problem reading this document(23). I am able to save on one of my computers but not the other. Can this be fixed?

  • How to add a new field to the Quote: Shipping and Bill Tab Payment region

    Hello All, We have a requirement to add payment description column to the Payment Region of Shipping and Bill tab in Quoting User(Quote Page). We have extended the View object HeaderPaymentsVOObj and created a custom view object, then created and por

  • Syncing apps from separate iTunes account.

    I have an iPhone 3, iPod Nano, iPod classic & iPod touch.  I just recently got an iPad from work.  The iPad was given to me for business purposes, however I was told that I may use it for fun/personal reasons as much as I'd like. My issue, is that my

  • PSE6 Mac OS - Save For Web won't save JPEG high res setting in Preset

    Why is it that, contrary to documentation, Save For Web won't remember that I always select JPEG High for every photo file I save? Each time, it comes up as "Custom" Low quality, and can't even remember that I want JPEG format. My reliable old copy o