CREATE_OBJECT_CLASS_NOT_FOUND runtime error during extractor checking

Hi Gurus,
I had to modify a generic data source based on a database view. I had to add a field for extraction. Since this field was available in the tables on which the view was built but not used in the view, I modified the view to to include the field. Then, I modified the extract structure to include the newly added field.
Now, when I try to check the extractor in RSA3 (extract checker), I end up getting a runtime error with details as below.
Runtime Errors                    CREATE_OBJECT_CLASS_NOT_FOUND          
Except.                    CX_SY_CREATE_OBJECT_ERROR          
Date and Time                    3/6/2012     5:46:07     
     Short text                         
          CREATE OBJECT: The class "\CLASS=ZCL_IM_CLC" was not found.                    
     What happened?                         
          Error in the ABAP Application Program                    
          The current ABAP program "CL_EXIT_MASTER================CP" had to be                    
           terminated because it has                    
          come across a statement that unfortunately cannot be executed.                    
     Error analysis                         
          An exception occurred that is explained in detail below.                    
          The exception, which is assigned to class 'CX_SY_CREATE_OBJECT_ERROR', was not                    
           caught in                    
          procedure "INSTANTIATE_IMP_CLASS" "(METHOD)", nor was it propagated by a                    
           RAISING clause.                    
          Since the caller of the procedure could not have anticipated that the                    
          exception would occur, the current program is terminated.                    
          The reason for the exception is:                    
          The dynamically specified class "\CLASS=ZCL_IM_CLC" at CREATE OBJECT neither                    
           exists as                    
          local, nor as global class in the system, or is overshadowed by a local                    
          data type of the same name.                    
     Missing RAISING Clause in Interface                         
          Program                    CL_EXIT_MASTER================CP
          Include                    CL_EXIT_MASTER================CM002
          Row                    1
          Module type                    (METHOD)
          Module Name                    INSTANTIATE_IMP_CLASS
     Trigger Location of Exception                         
          Program                    CL_EXIT_MASTER================CP
          Include                    CL_EXIT_MASTER================CM002
          Row                    15
          Module type                    (METHOD)
          Module Name                    INSTANTIATE_IMP_CLASS
     Source Code Extract                         
     Line          SourceCde               
     1          METHOD instantiate_imp_class .               
     2                         
     3            DATA: abs_type_classname TYPE string,               
     4                  imp_obj            TYPE imp_obj_type.               
     5                         
     6          *   Look for objects that have been created for this class               
     7            READ TABLE imp_obj_tab INTO imp_obj               
     8                WITH TABLE KEY imp_name    = imp_name               
     9                               calling_obj = caller.               
     10            IF sy-subrc = 0.               
     11              instance = imp_obj-obj.               
     12            ELSE.               
     13              CONCATENATE '\CLASS=' imp_class INTO abs_type_classname.               
     14          *****  dynamic object creation     *******************************               
     >>>>>              CREATE OBJECT instance TYPE (abs_type_classname).               
     16          ******************************************************************               
     17              imp_obj-imp_name    = imp_name.               
     18              imp_obj-calling_obj = caller.               
     19              imp_obj-obj         = instance.               
     20              INSERT imp_obj INTO TABLE imp_obj_tab.               
     21            ENDIF.               
     22          ENDMETHOD.     
Can anybody please help me solve this issue?

Hi Ajay,
Please check the following threads for your issue::
System Exception
Exception              CX_SY_CREATE_OBJECT_ERROR
Why is CREATE_OBJECT_CLASS_NOT_FOUND ?
Dump CREATE_OBJECT_CLASS_NOT_FOUND with BADI in MM_MATBEL archiving object
Regards,
Arpit

Similar Messages

  • Adhoc Query : Error during selection; check the selection conditions

    Hi
    We have a report set-up and which we want to run using our adhoc query report tcode S_PH0_48000513
    The report, has a few different selection criteria in it to look at all action IT screen data in the system for ee's in specific personnel areas. There is also a criteria to allow us to paste in specific employee numbers we are interested in. The issue I am facing is that over about 3000 ids, the system automatically returns me a message when I click on the Output button to run the report which states:
    Error during selection; check the selection conditions
    Message no. PAIS206
    I am not sure why this is happening. The selection criteria are fine and the other day I ran the report and I experienced no issues. The report ran successfully. Now though, if I try and paste in all the ids I am interested in (about 8000) I get this message straightaway.
    Can anything be done to overcome this issue?
    Any advice would be much appreciated.
    Nicola

    Hi
    The message in full is:
    Error during selection; check the selection conditions
    Message no. PAIS206
    Diagnosis
    A runtime error occurred during dynamic selection.
    System response
    The runtime error will be caught; no short dump will be created. This error should not occur as a rule. However, very large select statements may trigger the runtime error SAPSQL_STMNT_TOO_LARGE or DBIF_RSQL_INVALID_RSQL. There is no way to prevent this happening. In this case, the error can only be caught.
    Procedure
    Check the selection conditions to see whether the error was caused because the option "Import from text file" included too many objects in the "Multiple selection" dialog. If this is so, you must limit the number of individual values.

  • Runtime error during full installation

    hi
    do any one know where SAPLE30B comes....
    i got a runtime error during full installation...
    it gives a error like : the error has occured because the table was not filled through user input on the selection screen of program SAPLE30D"
    i dont know where it went wrong
    i wil be greatful if u help me to solve it...
    Rdgs
    Chatriyan
    Edited by: Chatriyan india on Aug 1, 2008 7:46 AM

    Hi,
    this sounds as some field values were not transported to the internal tables. Which transaction do you use? In case you are trying to use dark installation routines, make sure all needed fields are filled (check within the dump). If this all does not help - open a customer message - a dump will always be inspected by SAP Support.
    KR
    Uwe

  • ERRORS during NAMETAB CHECK in checks phase of EHP Inst.

    Hi SDNers,
    I'm implementing SAP Enhancement Package 4  for ECC6 system (ABAP).I started the application and it gets through the checks phase ok, except errors  during the GENCHECKS/NTACT_CHK TEXT .
    I logged on se11 but I could not able to see Runtime Object .
    See below error message:
    %BEGIN PREP_GENCHECKS/NTACT_CHK TEXT
    ERROR> *** ERRORS during NAMETAB CHECK found ***
            Analyze the logfile NTCHK.ELG to determine
            the nametab, that caused the error.
            Call transaction se11 for the corresponding
            DDIC object. Choose menu Utilities -> Runtime Object -> Check
            If you repeat the phase and there is still an error,
            see also note Nr. 179334 for additional information
    +++++++++++++ Content of NTCHK.ELG +++++++
    1 ETQ201 Entering upgrade-phase "NTACT_CHK" ("20100309081807")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=<null>
    4 ETQ399 Set environment for standard connect:
    4 ETQ399 ENV: dbs_ora_schema=SAPR3
    4 ETQ399 ENV: auth_shadow_upgrade=0
    4 ETQ399 Set RFC variables for standard connect:
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Set tool parameters for standard connect:
    4 ETQ399   default TPPARAM: DEFAULT.TPP
    1 ETQ200 Executing actual phase 'PREP_GENCHECKS/NTACT_CHK'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'CHKANT'
    2 ETQ399 Arg[1] = 'DDNTT'
    2 ETQ399 Arg[2] = 'DDNTF'
    2 ETQ399 Arg[3] = 'DDNTT'
    2 ETQ399 Arg[4] = 'DDNTF'
    2 ETQ399 Arg[5] = ''
    2 ETQ399 Arg[6] = 'NOBUFRESET'
    2 ETQ399 Arg[7] = ''
    2 ETQ399 Arg[8] = ''
    2 ETQ399 Arg[9] = ''
    2 ETQ399 Arg[10] = 'NTCHK.ELG'
    4 ETQ380 computing toolpath for request "TP_NTACTION_SHD"
    4 ETQ381 request "TP_NTACTION_SHD" means "tp ntact for shadow tables"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_SHDNEW"
    4 ETQ383 translates to path "exenew"
    4 ETQ383 translates to path "exe"
    2 ETQ399 Checking of nametabs ...
    4 ETQ399 2010/03/09 08:18:07: put_execute: (tp) forkpid:1175614
    4 ETQ010 Date & Time: 20100309090358 
    Has anyone encountered anything similar? Any ideas?
    Thanks in advance,
    Faris AL-Saweed

    hi Niraij,
    below more details of SAPehpi_troubleticket.log
    This trouble ticket was created by SAPehpi on 20100310093046
    SAPehpi broke during phase NTACT_CHK in module PREP_GENCHECKS / General checks
    Error Message: No lines found in logfile matching 'PN......\.EQA'
    Summary of SAPehpi:
    SAPehpi Release:     7.10/1
    SAPehpi Version:     SAPehpi version 7.10/1
    Start Release:          700
    Target Release:          701
    Summary of host system details:
    SID:               EQA
    Host:               wmdsapeqa
    MS Host:          wmdsapeqa
    GW Host:          wmdsapeqa
    Start Path:          /usr/sap/EQA/DVEBMGS00/exe     
    Kernel Path:          /usr/sap/EQA/DVEBMGS00/exe
    Summary of operating system details:
    OS Type:          AIX
    OS Version:          5.2.0
    Summary of database details:
    Database Type:          ora
    Database Version:     10.2.0.4.0
    Summary of RFC details:
    Host:               wmdsapeqa
    GW Host:          wmdsapeqa
    Client:               000
    Destination:          EQA
    Language:          
    System No.:          00
    regards,
    Faris
    Edited by: Faris Solaiman Saweed on Mar 10, 2010 8:07 AM

  • Can not Update icloud for win7 Sheep error during transformation. check that the indicated transmitter propagating path is valid. tryet in appel updater and tryet downloading from apple but the same

    Can not Update icloud for win7 Gets
    Sheep error during transformation. check that the indicated transmitter propagating path is valid.
    tryet in appel updater and tryet downloading from apple but the same

    Hi,
    Found a note explaining the significance of these errors.
    It says:
    "NZE-28862: SSL connection failed
    Cause: This error occurred because the peer closed the connection.
    Action: Enable Oracle Net tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output."
    For further details you may refer the Note: 244527.1 - Explanation of "SSL call to NZ function nzos_Handshake failed" error codes
    Thanks & Regards,
    Sindhiya V.

  • 26 Error during syntax check of IDoc (outbound)

    Hi Experts
    I am using TPSDLS - Idoc(outbound).
    When we view in WE02 : for few of the deliveries it is working fine , but for some it is giving the following error
    26     Error during syntax check of IDoc (outbound)
    Please any one help me out for the same
    Thanks & Regards
    Shaveta

    Please check the segments for the idocs in error status in WE02. The segments in the idoc should be in the same sequence as defined while creating idoc in WE30.
    For eg. taking the case of invoic02 idoc.
    Segment E1EDP01 cannot come prior to segment E1EDK01.
    As in WE30 it is defined to come after E1EDK01\
    Please reward the points if this information is useful.

  • Tp error during EHPI checks NTCHK phase

    Hi,
    We are running the EHPI and recieve the following error during the Checks phase:
    Severe error(s) occured in phase PREP_GENCHECKS/NTACT_CHK!
    Last error code set: Process 'tp' exited with 12, see '/uexports/DV1/EHPI/abap/log/TP.ECO' for details
    Error during "tp ntaction"-call - check TP.ECO
    TP.ECO=
    SAPehpi> Starting subprocess 16165 at 20101007100438
    ENV: DIR_LIBRARY=/uexports/DV1/EHPI/abap/exenew
    ENV: JAVA_HOME=/opt/java1.4
    ENV: LD_LIBRARY_PATH=/uexports/DV1/EHPI/abap/exenew:/uexports/DV1/EHPI/jvm/jre/lib/ia64/server:/uexports/DV1/EHPI/jvm/jre/
    lib/ia64:/uexports/DV1/EHPI/jvm/jre/../lib/ia64
    ENV: NLS_LANG=AMERICAN_AMERICA.UTF8
    ENV: ORACLE_BASE=/oracle
    ENV: ORACLE_HOME=/oracle/DV1/102_64
    ENV: ORACLE_SID=DV1
    ENV: PATH=/uexports/DV1/EHPI/abap/exenew:/opt/java1.4/bin:/oracle/DV1/102_64/bin:.:/home/dv1adm:/usr/sap/DV1/SYS/exe/run:/
    usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/contrib/Q4/bin:/opt/perl/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/fcms/bin:/
    usr/contrib/kwdb/bin:/usr/bin/X11:/opt/graphics/common/bin:/opt/upgrade/bin:/opt/ipf/bin:/opt/resmon/bin:/opt/perf/bin:/op
    t/wbem/bin:/opt/wbem/sbin:/opt/prm/bin:/opt/sec_mgmt/bastille/bin:/opt/dsau/bin:/opt/dsau/sbin:/opt/gnome/bin:/opt/ignite/
    bin:/opt/sec_mgmt/spc/bin:/opt/ssh/bin:/opt/hpsmh/bin:/opt/wlm/bin:/opt/hpnpl//bin:/usr/contrib/bin/X11:/opt/sfm/bin:/opt/
    mozilla:/opt/perl_32/bin:/opt/perl_64/bin:/opt/swa/bin:/oa/cdirect/ndm/bin:.
    ENV: SAPSYSTEMNAME=DV1
    ENV: auth_shadow_upgrade=0
    ENV: dbms_type=ORA
    ENV: dbs_ora_schema=SAPR3
    ENV: dbs_ora_tnsname=DV1
    EXECUTING /uexports/DV1/EHPI/abap/exenew/tp (/uexports/DV1/EHPI/abap/exenew/tp) ntaction ntop=chkant DV1 pf=/uexports/DV1/
    EHPI/abap/bin/DEFAULT.TPP srctt=DDNTT srctf=DDNTF dsttt=DDNTT dsttf=DDNTF intdel=YES -Dntact_timecmp=no protyear=40
    initial value of NLS_LANG: 'AMERICAN_AMERICA.UTF8'
    This is /uexports/DV1/EHPI/abap/exenew/tp version 372.04.88 (release 701, unicode enabled)
    Warning: Parameter INTERRUPT is no longer used.
    Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 8).
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter INTERRUPT is no longer used.
    Warning: unknown parameter MAX_SEMAPHORE_WAIT in parameter file (line 8).
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter DBCONFPATH is no longer used.
    tp finished with return code: 12
    meaning:
      A tool used by tp aborted
    Process with ID 16165 terminated with status 12
    NTCHK.LOG=
    1 ETQ201 Entering upgrade-phase "NTACT_CHK" ("20101007100438")
    2 ETQ367 Connect variables are set for standard instance access
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Environment variables:
    4 ETQ399   dbs_ora_schema=SAPR3
    4 ETQ399   auth_shadow_upgrade=0
    4 ETQ399 Set environment for standard connect:
    4 ETQ399 ENV: dbs_ora_schema=SAPR3
    4 ETQ399 ENV: auth_shadow_upgrade=0
    4 ETQ399 Set RFC variables for standard connect:
    4 ETQ399 System-nr = '00', GwService = 'sapgw00'
    4 ETQ399 Set tool parameters for standard connect:
    4 ETQ399   default TPPARAM: DEFAULT.TPP
    1 ETQ200 Executing actual phase 'PREP_GENCHECKS/NTACT_CHK'.
    1 ETQ399 Phase arguments:
    2 ETQ399 Arg[0] = 'CHKANT'
    2 ETQ399 Arg[1] = 'DDNTT'
    2 ETQ399 Arg[2] = 'DDNTF'
    2 ETQ399 Arg[3] = 'DDNTT'
    2 ETQ399 Arg[4] = 'DDNTF'
    2 ETQ399 Arg[5] = ''
    2 ETQ399 Arg[6] = 'NOBUFRESET'
    2 ETQ399 Arg[7] = ''
    2 ETQ399 Arg[8] = ''
    2 ETQ399 Arg[9] = ''
    2 ETQ399 Arg[10] = 'NTCHK.ELG'
    4 ETQ380 computing toolpath for request "TP_NTACTION_SHD"
    4 ETQ381 request "TP_NTACTION_SHD" means "tp ntact for shadow tables"
    4 ETQ382 translates to group "R3UP_TOOL_GROUP_SHDNEW"
    4 ETQ383 translates to path "exenew"
    4 ETQ383 translates to path "exe"
    2 ETQ399 Checking of nametabs ...
    4 ETQ399 2010/10/07 10:04:38: put_execute: (tp) forkpid:16165
    It doesn't even get to the point of creating NTCHK.ELG
    -rw-rr   1 dv1adm     sapsys      287923 Oct  7 10:19 SAPehpichk.log
    -rw-rr   1 dv1adm     sapsys       13144 Oct  7 10:19 TROUBLE_SAVELOGS.LOG
    -rw-rr   1 dv1adm     sapsys      151957 Oct  7 10:19 SAPehpi_troubleticket_logs.sar
    -rw-rw-r--   1 dv1adm     sapsys       10039 Oct  7 10:19 SLOG700
    -rw-rw-r--   1 dv1adm     sapsys       80609 Oct  7 10:19 ALOG700
    -rw-rr   1 dv1adm     sapsys        9238 Oct  7 10:19 TP.ECO
    -rw-rr   1 dv1adm     sapsys        1729 Oct  7 10:19 SAPehpi_troubleticket.log
    -rw-rw-r--   1 dv1adm     sapsys     112988412 Oct  7 10:19 PN401007.DV1
    -rw-rr   1 dv1adm     sapsys        1292 Oct  7 10:05 NTCHK.LOG
    -rw-rr   1 dv1adm     sapsys       57379 Oct  7 10:05 SAPehpiConsole.log
    -rw-rw-r--   1 dv1adm     sapsys      148736 Oct  7 10:04 ULOG10_4
    -rw-rr   1 dv1adm     sapsys       10692 Oct  7 10:04 SAPehpi.ECO
    -rw-rr   1 dv1adm     sapsys       10581 Oct  7 10:04 NTCHK.SAV
    takderp1:dv1adm 530> ll NT*
    -rw-rr   1 dv1adm     sapsys        1292 Oct  7 10:05 NTCHK.LOG
    -rw-rr   1 dv1adm     sapsys       10581 Oct  7 10:04 NTCHK.SAV
    SAPehpi_troubleticket.log=
    This trouble ticket was created by SAPehpi on 20101007101947
    SAPehpi broke during phase NTACT_CHK in module PREP_GENCHECKS / General checks
    Error Message: Process 'tp' exited with 12, see '/uexports/DV1/EHPI/abap/log/TP.ECO' for details
    Error during "tp ntaction"-call - check TP.ECO
    Summary of SAPehpi:
    SAPehpi Release:        7.10/1
    SAPehpi Version:        SAPehpi version 7.10/1
    Start Release:          700
    Target Release:         701
    Summary of host system details:
    SID:                    DV1
    Host:                   takderp1
    MS Host:                takderp1
    GW Host:                takderp1
    Start Path:             /usr/sap/DV1/SYS/exe/run
    Kernel Path:            /usr/sap/DV1/SYS/exe/run
    Summary of operating system details:
    OS Type:                HP-UX IA64
    OS Version:             11.23
    Summary of database details:
    Database Type:          ora
    Database Version:       10.2.0.2.0
    Summary of RFC details:
    Host:                   takderp1
    GW Host:                takderp1
    Client:                 000
    Destination:            DV1
    Language:
    System No.:             00
    Any help would be appreciated.
    Thanks,
    Jim

    Hi Eric,
    I have the log posted above but here is an excert from the TP.ECO log.
    Warning: Parameter INTERRUPT is no longer used.
    Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
    Warning: Parameter WITH_TACOB is no longer used.
    Warning: Parameter IMPDP_BY_EVENT is no longer used.
    Warning: Parameter DBCONFPATH is no longer used.
    tp finished with return code: 12
    meaning:
      A tool used by tp aborted
    Process with ID 22858 terminated with status 12
    Regards,
    JIm

  • Error during availability check for order

    Hi PM experts,
    How can I make below warning message (W) to an error message (E)?
    Message no: CO820 (Error during availability check for order)
    Regards,
    Nizam
    PM Consultant

    Hi,
    you can cantrol not to release maint orders in case if parts are missing by OIOI transaction, here under Material Availability  against Release material you maintain option 3 No release if parts are missing. This way you can achieve this. If there are other components which has stock on Maint order then delete the un-available material from maint order then it will allow you to release the order.
    Hope availability check rule is maintained on material master.
    Hope it helps.
    Regards,
    N.Nagaraju

  • Runtime Error during Phase Start Data Selection

    Hello Forums,
    We are using TDMS (2006_1_700) to extract a year's worth data from one client into a new client on the same ERP EhP4 system.
    All the systems - central, sender and receiver are at the same DMIS levels(SP16) and all necessary notes have been applied.
    During the Step 'Start Data Selection' of the Data Transfer Phase, we see around 60 of the ~12000 sub tasks abort with the below error:
    Batch job for access plan calculation in sender system ended with errors
    Message no. DMC_UTIL_MSG021
    Diagnosis
    The access plan calculation was executed as a background job in the sender system. In this background job, an error occurred.
    Procedure
    Check if a short dump occurred in the sender system while the access plan was calculated. If existing, this short dump contains further information about the cause of the problem.
    A frequent error is that selection criteria for data reduction (for example selection groups) are wrongly defined which causes the database access that consideres these selection criteria to fail.
    The corresponding dump in the Sender system is as below:
    Runtime Errors         SAPSQL_WHERE_PARENTHESES
    Exception              CX_SY_DYNAMIC_OSQL_SYNTAX
    Error analysis                                                                                |
    |    An exception occurred that is explained in detail below.                                      |
    |    The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not                |
    |     caught in                                                                                |
    |    procedure "/1CADMC/DMCACS00P000000001" "(FUNCTION)", nor was it propagated by a               |
    |     RAISING clause.                                                                              |
    |    Since the caller of the procedure could not have anticipated that the                         |
    |    exception would occur, the current program is terminated.                                     |
    |    The reason for the exception is:                                                              |
    |    The current ABAP program has tried to execute an Open SQL statement                           |
    |    which contains a dynamic condition. The part of the condition specified                       |
    |    at runtime is incorrectly parenthesized.   
    Please suggest in case any of you have encountered similar error and possible resolution.
    Thanks in advance,
    Srikishan

    Hi Suman,
    Thanks a ton. I somehow missed this when searching on the SMP.
    I will implement the steps and post it back by tomorrow.
    Regards,
    Srikishan

  • Runtime error in extractor enhancement

    Hi,
    I need to enhance the extractor 0WBS_ELEMT_ATTR with an additional field. The field is a Z field from the table PRPS.
    Now PRPS is a base table for the extractor for this extractor, so simply adding this field into the append structure should suffice.
    However, when I do this the extractor gives the following runtime error:
    Syntax error in program "SAPLPSBW "
    Component called ZZSO already exists.
    The error is in the function call  "e_fname".
    I have found that the same Z field is used in another structure CNCI_PRPS. Could this be leading to the error?
    Please let me know if any of you have any insights as to why this problem might be occurring.
    TIA,
    Amrita

    Hi,
    In my case the problem was caused because the same ZZ Field was used in two structures.
    One for ECC and one for BI. This was causing some interference.
    To solve this I changed the field name in my extract structure to ZZZSO and populated it via a CMOD routine.
    Hope this helps.
    Amrita

  • Runtime error during opening a process chain in rspcm

    Hello,
    i created a process chain just a simple one which loads Data from the DataSource into a DSO and then into a InfoCube.
    I executed this processchain without activiating my Initial-Request in the DSO.
    So i got a hanging Request there, i deleted all Requests from all objects in this processchain. Still had this hanging Request, so i deleted this one Request from the RSEQDONE. Now my processchain is working, but it takes very long to open it when i am in the RSPCM or i even get a runtime error.
    Any suggestions?

    Regarding RSPCM you better to check the oss notes which are shared by Michael devine.
    Coming to your issue, if you have loading huge data then better to increase your wait time of your info pack load.
    go to your info pack --> menu scheduler-->Time out time, increase as you need.
    if your doing full loads, please use proper selections and split your load as small chunks.
    increase packet sizes and parallel settings to speed up your load.

  • ABAP runtime errors during customer extension to other company code

    Hi,
    I have created one customer in company code 1111 with tcode XD01.
    When i am trying to create the same customer in the other company codes 2222,3333, and 4444, with tcode FD15, system is giving runtime errors like below.
    The following syntax error occurred in the program RFBIDE20             
    "Field "BSZA1_D0100-MOB_NUMBER" is unknown. It is neither in one of the"
    Error in ABAP application program.                                                                               
    The current ABAP program "RFBIDE10" had to be terminated because one of the
    statements could not be executed
    *This is probably due to an error in the ABAP program *
    Could anyone help me out in this regard.
    Thanks,
    Srinu.

    Hi
    Check SAP Note - 757821
    Thank You,

  • Portal Runtime error during 1, 2, 3 Drag & Relate?

    Hi,
    I have successfully install SR1 version of the EP6.  I am attempting to complete the "1, 2, 3 Drag&Relate" weblog.  During one of the steps you have to go to User Administration > User Mapping to set the Everyone group user mapping.
    I am using sa id and the password I set during my SQL installation.
    As I click save button after entering the input I get this error:
    Portal Runtime Error
    An exception occurred while processing a request for:
    iView:
    pcd:portal_content/administratrator/super_admin/super_admin_role/com.sap.portal.user_administration/com.sap.portal.user_mapping/com.sap.portal.userMappingAdmin/com.sap.portal.userMappingAdmin
    Component Name: com.sap.portal.usermanagement.admin.UserMappingAdmin
    User Mapping not fully available..
    Exception id: 2:07_11/01/2005_0001_4582650
    See the details for the exception ID in the log file.
    Any ideas why this error is occuring?
    Thanks,
    Jin Bae

    Hi Jin,
    I think SAP note number 796540 will be helpfull to you.
    It was known User Management issue which is not connected to any Unification feature.
    Personal advice: try to restart Portal server.
    Regards,
    Julia

  • Runtime Error during FileUpload to KM through webdynpro java

    Hi All,
    When i try to upload a file using webdynpro java. I was using referring this blog.
    /people/rohit.radhakrishnan/blog/2005/05/27/uploading-files-to-km-repository-using-webdynpro-apis
    But when i deploy my application, it throws me a runtime error
    " java.lang.NoClassDefFoundError: com/sapportals/wcm/repository/IResourceContext".
    I have given the sharing reference as "Portal:sap.com/com.sap.km.aaplication". in webdynpro reference.  and have added all the required jar files. What else needs to be done for this. Can anyone please help me out in this issue?
    Regards,
    Divya

    Please notice that this is case sensative-
    "PORTAL:sap.com/com.sap.km.application"
    Edit - I also see that you have two a instead of two p - please check for spelling errors
    Edited by: Aviad Levy on Feb 4, 2008 9:16 AM

  • Getting runtime error during billing vf01

    Hello,i was doing billing vf01 getting runtime error after saving. what shud i do.The error says "SAPSQL_INVALID_FIEDNAME"CX_SY_DYNAMIC_OSQL_SEMANTIC SC"SAPLV61Z" or "LV61ZUQ1""SEL_KONDTAB".
    This is what i got in the error, in "what shud be done" title of the error.kindly suggest to clear out this problem.

    Hi Ramya,
    I am assuming you hv implemented your own function module in INCLUDE LV61ZUQ1. During VF01, SAP has detected at least 1 fieldname which does not exist in your ABAP codes/Select statement. This could happen, if for example a new field  has been implemented in a structure/trans. table or new fields added to field catalogs, but has not been successfuly generated/SAP stored the info structure incorrectly.
    If that's the case, the best way is to delete the field and re-generate, or if you added a field to field catalog, delete field in catalog then add, re-generate.
    Cheers,
    Benny Andre

Maybe you are looking for