Pc00_m99_URMR - Runtime Error CONNE_IMPORT_WRONG_STRUCTURE in ECC 6.0

My functional people are getting this error along with CX_SY_IMPORT_MISMATCH_ERROR. The problem is occurring in CL_HR_PAY_RESULT_US - IMPORT_FROM_TABLE. The reason for the exception is:
When attempting to import data, the structure of the complex object "COSTS" was not compatable with the target object. The error occurred with component no. 21.
I looked back at our 470 version program and this parameter was not used in it so SAP has added it and evidently typed it wrong. I've looked for SAP notes, but so far haven't found one that looks like it applies. Has anybody else run into this error?

I have came across with a similar in MIGO.
The data you are trying to import was saved in a different structure as mentioned in the DUMP .
Old data cannot be imported since the new structure was changed in a deep level.
Sorry

Similar Messages

Runtime Error in VL01N after upgrade from 4.6c to ECC 6.0

hi,
   We are doing a upgrade project from 4.6c to ECC 6.0 and when we are running the VL01n tcode and as soon as we hit enter in easy access screen its throwing a runtime error as " The key of internal table "XLIPS" contains components of type 'X' or "XSTRING". The "READ TABLE XLIPS" statement is not permitted for such tables in a unicode context'. The xlips is declared as:
DATA: BEGIN OF XLIPS OCCURS 15.
INCLUDE STRUCTURE LIPSVB.
DATA: END OF XLIPS.
so i have checked the lipsvb structure in that i dont find the key fields of type X or XSTRING all are of type CHAR 4. this LIPSVB is the Reference structure for XLIPS and YLIPS.
THANKS IN ADVANCE.

Please see the Patch level of the SD, FI ,etc...
and apply it   the basis   should   find it out .... for ECC6.0   then minimum level of patches should be   upgraded.
please ,login to help.sap.com ... there in the search see the document   of the pateches for the   ECC6.0 for SD & FI ... like wise for all Modules ....
Reward points if it is usefulll ...
Girish

SAPLFAGL_ITEMS_SELECT runtime error in FAGLL03 after ECC EHP 7 upgrade

Hi all,
We have recently upgraded to SAP ECC to EHP7, after this we are getting SAPLFAGL_ITEMS_SELECT runtime error in FAGLL03 report.
Runtime error is not about a time out
I have searched for a note but could not find any on this problem.
Information on where terminated
    The termination occurred in ABAP program "SAPLFAGL_ITEMS_SELECT", in
"FAGL_GET_ITEMS_BSEG". The main program
    was "FAGL_ACCOUNT_ITEMS_GL ".
    In the source code, the termination point is in line 412 of (Include)
    program "LFAGL_ITEMS_SELECTU08".
Thanks in advance,

Hi,
Check this SAP note1578577 - FAGLL03: Dump DBIF_RSQL_INVALID_RSQL. Another one is 1728986. Cannot check further as I am not aware of exact patch level.
If this does not help kindly raise it to SAP as dump is in standard object.
Regards,
Anand Raichura

Runtime Error in MIGO after upgrade from 4.6c to ECC 6.0

hi,
    We are doing a upgrade project from 4.6c to ECC 6.0 and when we are posting the MIGO a runtime error is occuring from the method
"IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE" which is
in the class "ZCL_IM_MMIM_STK_TRANSFER".
The error is as follows :
method IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE
>>>>>CALL FUNCTION 'Z_MM_STK_TSFR'
TABLES
T_XMKPF = XMKPF
T_XMSEG = XMSEG.
END METHOD.
the errror is showing at function 'Z_MM_STK_TSFR'   .
I would be happy if anyone could give any inputs i hav also put chek in unicode in attributes in main program however still the error is arising.
thanks in advance

hi,
     thanks for the inputs i have done the syntax check on the main program and the FM the error which is coming is Field "ENJPREVIEW" is unknown. its neither in one of the specified tables nor defined by a DATA 'statement' . THis error is showing in the include LMEDRUCKF1K.
Thanks in advance

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 in activation BADI (CX_HRPA_INVALID_PARAMETER)

In activation BADI i get a runtime error using 'HR_INFOTYPE_OPERATION'
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not
caught in
procedure "RESOLVE_EXCEPTION" "(FORM)", 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:
Ongeldige parameter EXCEPTION waarde
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_HRPA_VIOLATED_PRECONDITION", which was raised in the
program "CL_HRPA_MASTERDATA_FACTORY====CP",
specifically in line 6 of the (include) program
"CL_HRPA_MASTERDATA_FACTORY====CM004".
The cause of the exception was:
Niet aan voorwaarde voldaan
DATA: personaldatakey   TYPE bapipakey.
DATA: return            TYPE bapireturn1.
DATA: l_p0025           TYPE p0025.
DATA: l_citem           TYPE t71adm09-citem.
DATA: l_resultaat(2)    TYPE n.
l_p0025-pernr = p0759-pernr.
Begindatum is begindatum binnengekomen IT0759 record - 1 jaar
    CALL FUNCTION 'RP_CALC_DATE_IN_INTERVAL'
      EXPORTING
        date      = p0759-begda
        days      = 0
        months    = 0
        signum    = '-'
        years     = 1
      IMPORTING
        calc_date = l_p0025-begda.
Einddatum is 31 december van het jaar binnegkomen IT0759
    CONCATENATE: p0759-endda(04) '1231' INTO l_p0025-endda.
    l_p0025-infty = '0025'.
    IF p0759-cpamt >= 100.
*GENERATE ERROR
    ELSE.
      l_resultaat = p0759-cpamt.
     IF l_resultaat < 10.
       CONCATENATE '0' l_resultaat INTO l_p0025-krt01.
     ELSE.
     l_p0025-krt01 = l_resultaat.
     ENDIF.
write data
      CLEAR: return, personaldatakey.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '0025'
          number        = l_p0025-pernr
          validityend   = l_p0025-endda
          validitybegin = l_p0025-begda
          record        = l_p0025
          operation     = 'INS'
          nocommit      = ''
          tclas         = 'A'
        IMPORTING
          return        = return
          key           = personaldatakey
        EXCEPTIONS
          OTHERS        = 0.
      IF NOT return-number IS INITIAL.
GENERATE ERROR
      ELSE.
        is_ok = 'X'.
        process_standard = 'X'.
      ENDIF.

Hello Richard
The exception is raised in method SET_FRAMEWORK of class CL_HRPA_MASTERDATA_FACTORY. Perhaps the SAP note mentioned in the coding (on ECC 6.0) may be useful:
METHOD set_framework.
IF a_is_initialized = true.
*   This indicates some complex problem which often can be easily
*   fixed. For details see NOTE 493984 (2003).
    RAISE EXCEPTION TYPE cx_hrpa_violated_precondition. " line 6
ELSE.
    CALL METHOD delayed_constructor
      EXPORTING
        read_infotype     = read_infotype
        masterdata_buffer = masterdata_buffer
        additional_buffer = additional_buffer
        legacy_mode       = legacy_mode.
ENDIF.
ENDMETHOD.
Regards
Uwe

Runtime error while activating LO Datasource in Source System

Hi Gurus,
I have followed the below steps to activate the SD related LO extractor in ECC
1. RSA5 --> Select all the 2LIS_11,12&13 data source and activate
2. LBWE --> Choose the 2LIS_11,12&13 data source and activate.
Upon execution of the second step , the system return me the following runtime error
Runtime Errors         DDIC_TYPE_INCONSISTENCY
Date and Time          07.07.2011 10:14:29
Short text
     Inconsistency in the Dictionary for the structure "MCQALSB".
What happened?
     Error in the SAP kernel.
     The current ABAP "SAPLMCEX" program had to be terminated because the
     ABAP processor detected an internal system error.
Error analysis
     There is an internal system error.
     eliminated with ABAP/4.
Trigger Location of Runtime Error
     Program                                 SAPLMCEX
     Include                                 LMCEX$04
     Row                                     26
With this error i cant proceed to activate any of the LO data source
Please help
Thanks in advance

The table MCQALSB need to be activated in SE11 and LBWE works fine

Runtime error - FBL1N - vendor balance with customer line item

Hi gurus,
One scenario where i have assign vendor as customer & customer as vendor in vendor & customer data. also make tick mark for both clearing with vendor & customer.
when i see the customer report with vendor item it shows me the customer & vendor dues but when i tried to see the vendor balance with customer line item it gives dump error.
Runtime Errors         PERFORM_NOT_FOUND
Exception              CX_SY_DYN_CALL_ILLEGAL_FORM
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FORM', was
     not caught in
    procedure "%_LDB_CALLBACK" "(FORM)", 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 program "RSDBRUNT" is meant to execute an external PERFORM,
    namely the routine "CB_DDF_GET_KNA1 " of the program "RFITEMAP ", but
    this routine does not exist.
    This may be due to any of the following reasons:
    1. One of the programs "RSDBRUNT" or "RFITEMAP " is currently being developed.
    The name "CB_DDF_GET_KNA1 " of the called routine may be incorrect, or
    the routine "CB_DDF_GET_KNA1 " is not yet implemented in the program "RFITEMAP
    2. If the program SAPMSSY1 is involved in the runtime error, one of
    the function modules called via RFC is not flagged as remote-capable.
    (see Transaction SE37 Goto -> Administration -> RFC flag)
    3. There is an inconsistency in the system. The versions of the
    programs "RSDBRUNT" and "RFITEMAP " do not match.
Warm regards,
Dhananjay R.

Hi martin
still problem was not solved. actually i am working on ECC 6.0 & not required to implement the sap note on development. i had done the configuration in vendor master & customer master for clearing.
please suggest me.....what to do ?
Than'x
Dhananjay R

Webdynpro application runtime error CX_FQDN

Hi experts,
I am encountering following error when running a sample webdynpor application from SE80. I have included details of my Hosts file entries and profile parameter in the details below.
My SAP system is installed on my desktop computer as a standalone on a wrkgroup. Name of the host is 'ecc6'.
Step by step instructions preferably with some example will be greatly appreciated.
Thanks in advance. AP
What has happened?
The URL http://ecc6:8006/sap/bc/webdynpro/sap/z_tutorial_1 was not called due to an error.
Note
The following error text was processed in the system ECC : Die URL enthält keine vollständige Domainangabe (ecc6 statt ecc6.).
The error occurred on the application server ecc6_ECC_06 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
ST22 dump is:
Runtime Errors         UNCAUGHT_EXCEPTION
Exception              CX_FQDN
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_FQDN', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
    Die URL enthält keine vollständige Domainangabe (ecc6 statt
    ecc6.).
System environment
    SAP-Release 700
    Application server... "ecc6"
    Network address...... "192.168.100.1"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "4x Intel 801686"
    Character length.... 16 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "ECC6"
    Database type..... "ORACLE"
    Database name..... "ECC"
    Database user ID.. "SAPSR3"
User and Transaction
    Client.............. 001
    User................ "SAPUSER"
    Language Key........ "E"
    Transaction......... " "
    Program............. "CX_FQDN=======================CP"
    Screen.............. "SAPMHTTP 0010"
    Screen Line......... 2
    Information on Caller ofr "HTTP" Connection:
    Plug-in Type.......... "HTTP"
    Caller IP............. "192.168.100.1"
    Caller Port........... 8006
    Universal Resource Id. "/sap/bc/webdynpro/sap/z_tutorial_1"
Information on where terminated
    Termination occurred in the ABAP program "CX_FQDN=======================CP" -
     in "CHECK".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 10
    of the (Include) program "CX_FQDN=======================CM002".
Entries in C:WINDOWSsystem32driversetchosts
127.0.0.1                 localhost
192.168.100.1     ecc6
Instance Profile in SAP transaction RZ10 is ECCDVEBMGS06_ECC6_
            Parameter Name                                      Parameter value
login/no_automatic_user_sapstar                      0
login/system_client                                            001
SAPSYSTEMNAME                                           ECC
SAPGLOBALHOST                                           ecc6
SAPSYSTEM                                                    06
INSTANCE_NAME                                             DVEBMGS06
DIR_CT_RUN                                                 $(DIR_EXE_ROOT)$(OS_UNICODE)NTI386
DIR_EXECUTABLE                                         $(DIR_INSTANCE)exe
PHYS_MEMSIZE                                             512
rdisp/wp_no_dia                                             6
rdisp/wp_no_btc                                            3
icm/server_port_0                                          PROT=HTTP,PORT=80$$
ms/server_port_0                                          PROT=HTTP,PORT=81$$
rdisp/wp_no_enq                                   1
rdisp/wp_no_vb                                    1
rdisp/wp_no_vb2                                  1
rdisp/wp_no_spo                                   1
DIR_CLIENT_ORAHOME                              $(DIR_EXECUTABLE)

HI ,
SAP has recommended it like that
for accessing SAP web dynpro abap application you have to give the full FQDN i.e. host name with domain.
simply hostname alone wont work.
http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/content.htm
Pls go through the link.This mite help
Thanks,
Aditya.

Runtime Error COMPUTE_BCD_OVERFLOW in co02

Hi guys.
I am getting the runtime error Overflow during the arithmetical operation (type P) in program "SAPLCK21" when saving via co02.
This error occurs in the Production system but not in the test system for the same Production Order.
Thanks in advance.

I have gone through the specified notes.They are not applicable to our system release 605.
(For added information: we have recently upgraded SAP from 4.7 to ECC 6.0 EHP5)
The issue is happening only for a specific raw material 159085420000.
We have a test system QAS which is a copy of Production (live) system.
In QAS, if this material is added to any production order, it is getting saved without any issues.
But in PRD, it is causing the run time error when it is added to any Production Order.
Also the MM master data for the material 159085420000 is exactly the same in both QAS and PRD.
Also
The Base Unit of measure for the material is kg.
I am using the same unit. While saving (via co02), it throws the run time error from the form price_of_purchase_info_record.
If I change the unit to MT (alternative unit of measure) in co02, it is getting saved without any issues.
Edited by: kapmsd on Jan 23, 2012 6:48 AM
Edited by: kapmsd on Jan 24, 2012 6:29 AM

RSIMPCURR: Runtime error while executing

Hi Everyone,
I want to create a process chain to transfer global settings from my ECC system to the BI system. For this purpose I was checking the ABAP program RSIMPCURR which is used to transfer the currecny exchange rates. But when this program is executed, it throws a runtime error and ends with a dump.
Here's a snippet of the ABAP dump:
151   CALL FUNCTION 'RSAR_DESTINATION_GET'
152     EXPORTING
153       i_logsys      = l_source
154     IMPORTING
155       e_destination = l_destination
156     EXCEPTIONS
157       not_exist     = 1
158       OTHERS        = 2.
159   IF sy-subrc <> 0.
' >>>>>     MESSAGE x000(rh).
161   ENDIF.
162
The thing is, when I manually transfer the currencies from the RSA1 > Source system screen, I'm not facing any issues. Its only while executing the program that I get the dump.
Any suggestions?
Thanks,
Ram

Hi,
I don't think this is a resource issue, because the global settings get transferred when I do it from RSA1 > Source system.
Also the FM 'RSAR_DESTINATION_GET' is the one that throws the exception 'Cannot find destination'. I think this is because I cannot enter the Source System in the program parameters because it is disabled. The other parameters (like 'Exchange Rate type' and 'Changes since') are not disabled and I'm able to enter the selections into those.
Is there anyway that I can enable the source-system box and provide my source system as a location extract the currencies?

Runtime error: CX_SHM_OUT_OF_MEMORY

Hello Experts,
I have opened one program in SE38 in Quality system which contains so many routines.I need to check the source code of a routine say ZTEST.
For that i have double clicked on the name of routine(eg. Perform ZTEST).But am getting below runtime error.
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_SHM_OUT_OF_MEMORY
This is happenning irrespective of Users and Programs.(Both Standard and Customized programs)
But am able to view the source code of routine by double clicking on the routine name in Development system.
I have checked the profile parameter abap/shared_objects_size_MB which is same for both Development and Preproduction system.Could you please let me know why this is happening?Do I need to restart the SAP system.
Platform:
SAP ECC 6.0,UNIX,ORACLE
Thanks & Regards,
Gopi L.

Check
Note 1322182 - Memory consumption of ABAP Shared Objects
the default value is usually too low.
Markus

Dynamic table runtime error

Hi everyone.
We are working on upgrading from 4.6c to ECC 6.0 and I've run into a programming problem.
I have a class that I use to convert any internal table based on a dictionary structure to a comma-separated text file. For the most part, I use the dynamic table techniques that are easy to find here and in other code forums.
In 6.0 I can not get it to work. The value assignment of the input table to the field-symbol for the dynamic table causes a "OBJECTS_TABLES_NOT_COMPATIBLE" runtime error. So far what I can find on this error specific to dynamic tables is related to BW and/or PI. And I can't seem to find any alternative ways of dealing with dynamic tables. In debug I can see that decimal number fields in the dynamic table have a different length than what's in the dictionary.
Any help or ideas would be greately appreciated.
Here is part of the method that converts the itab to an dynamic internal table, then creates a csv record for each record (I've hilighted the line that causes the dump) :
Get the structure of the table.
ref_table_des ?=
      cl_abap_typedescr=>describe_by_name( i_structure ).
idetails[] = ref_table_des->components[].
loop at idetails into xdetails.
    clear xfc.
    xfc-fieldname = xdetails-name .
    xfc-datatype = xdetails-type_kind.
    xfc-inttype = xdetails-type_kind.
    xfc-intlen = xdetails-length.
    xfc-decimals = xdetails-decimals.
    append xfc to ifc.
endloop.
Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
               exporting
                  it_fieldcatalog = ifc
               importing
                  ep_table        = dy_table.
assign dy_table->* to <dyn_table>.
Create dynamic work area and assign to FS
create data dy_line like line of <dyn_table>.
assign dy_line->* to <dyn_wa>.
put data into the dynamic table
<dyn_table> = it_data[].    "<<==the runtime error happens on this line
loop at <dyn_table> into <dyn_wa>.
    clear: l_fdata, l_data.
    do.
      l_index = sy-index.
      assign component l_index
         of structure <dyn_wa> to <dyn_field>.
      if sy-subrc <> 0.
        exit.
      endif.
      read table ifc into xfc index l_index.
      if xfc-inttype = 'D'.
*etc...
Thank you,
- George

Hi,
For Dynamic internal table.u check SM30 Transaction.ther is one simple way to find the code in debugging.
if not possible i will send code which is relatd to dynamic table .
*&      Form get_table_structure
*       Get structure of an SAP table
form get_table_structure.
data : it_tabdescr type abap_compdescr_tab,
         wa_tabdescr type abap_compdescr.
data : ref_table_descr type ref to cl_abap_structdescr.
* Return structure of the table.
ref_table_descr ?= cl_abap_typedescr=>describe_by_name( p_table ).
it_tabdescr[] = ref_table_descr->components[].
loop at it_tabdescr into wa_tabdescr.
    clear wa_fieldcat.
    wa_fieldcat-fieldname = wa_tabdescr-name .
    wa_fieldcat-datatype = wa_tabdescr-type_kind.
    wa_fieldcat-inttype   = wa_tabdescr-type_kind.
    wa_fieldcat-intlen    = wa_tabdescr-length.
    wa_fieldcat-decimals = wa_tabdescr-decimals.
    append wa_fieldcat to it_fieldcat.
endloop.
endform.                    "get_table_structure
*&      Form create_itab_dynamically
*   Create internal table dynamically
form create_itab_dynamically.
* Create dynamic internal table and assign to Field-Symbol
call method cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = it_fieldcat
    IMPORTING
      ep_table        = dyn_table.
assign dyn_table->* to <fs_table>.
* Create dynamic work area and assign to Field Symbol
create data dyn_line like line of <fs_table>.
assign dyn_line->* to <fs_wa>.
endform.                    "create_itab_dynamically
Edited by: subrahmanyam24 on Nov 18, 2010 5:12 AM
Edited by: subrahmanyam24 on Nov 18, 2010 5:15 AM

Runtime Error in ECC6 - for t-code PPOCE

HI Gurus!
at my client site , we have upgraded 4.7 to ECC6. Now functional consultants are testing the system.When HR consultant working on PPOCE t-code ,the patch no of SAP HR - 0007. its giving runtime error.
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Except.     CX_SY_CREATE_DATA_ERROR          Date and Time                    19.08.2008     14:42:44
Short text
CREATE DATA: The specified type "HRP1680" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRHDB" 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_DATA_ERROR', was not caught in
procedure "FILL_I777D" "(FORM)", 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 type "HRP1680" at CREATE DATA is no valid data type.
The type is either unknown or an object type.
Missing RAISING Clause in Interface
Program     SAPLRHDB
Include     LRHDBF00
Row     177
Module type (FORM)
Module Name FILL_I777D
Trigger Location of Exception
Program     SAPLRHDB
Include     LRHDBF00
Row     308
Module type(FORM)
Module Name     FILL_I777D
Source Code Extract
Line          SourceCde
278          **                HEADER   = FI_HEADER                    "ANDBCEK008264
279          **           TABLES                                       "ANDBCEK008264
280          **                FIELDTAB = FI_TAB                       "ANDBCEK008264
281          **           EXCEPTIONS                                   "ANDBCEK008264
282          **                OTHERS   = 4.                           "ANDBCEK008264
283          *                                                         "ANDBCEK008264
284          *      CALL FUNCTION 'DDIF_FIELDINFO_GET'                 "ANDBCEK008264
285          *           EXPORTING                                     "ANDBCEK008264
286          *                tabname        = fi_tabname              "ANDBCEK008264
287          **               FIELDNAME      = ' '                     "ANDBCEK008264
288          **               LANGU          = SY-LANGU                "ANDBCEK008264
289          **               LFIELDNAME     = ' '                     "ANDBCEK008264
290          **               ALL_TYPES      = ' '                     "ANDBCEK008264
291          *           IMPORTING                                     "ANDBCEK008264
292          *                x030l_wa       = fi_header               "ANDBCEK008264
293          **               DDOBJTYPE      =                         "ANDBCEK008264
294          **               DFIES_WA       =                         "ANDBCEK008264
295          **          TABLES                                        "ANDBCEK008264
296          **               DFIES_TAB      =                         "ANDBCEK008264
297          *          EXCEPTIONS                                     "ANDBCEK008264
298          *               not_found      = 1                        "ANDBCEK008264
299          *               internal_error = 2                        "ANDBCEK008264
300          *               OTHERS         = 3.                       "ANDBCEK008264
301          *
302          *      IF sy-subrc EQ 0.
303          *        i777d-tbtab_tabof = fi_header-tablen - tabnr_intlen.
304          *        i777d-pnnnn_tabof = i777d-tbtab_tabof - 8.
305          *      ENDIF.
306
307          *      ASSIGN char TO <any_field> CASTING TYPE (fi_tabname). "ANDDDIF
>>>>>                create data anyfield type (fi_tabname).                "ANDUNI
309                assign anyfield->* to <any_field>.                     "ANDUNI
310
311          *     we need a character view of <any_field> !!!            "ANDUNI
312                assign <any_field> to <char_field> casting type c.     "ANDUNI
313
314          *      DESCRIBE FIELD <any_field> LENGTH tablength            "ANDDDIF
315          *                                 IN BYTE MODE.               "ANDDDIF
316
317                DESCRIBE FIELD <char_field> LENGTH tablength           "ANDUNI
318                                            IN CHARACTER MODE.         "ANDUNI
319
320                <i777d>-tbtab_tabof = tablength - tabnr_intlen.        "ANDDDIF
321                <i777d>-pnnnn_tabof = <i777d>-tbtab_tabof - 8.         "ANDDDIF
322
323             ENDIF.
324              IF <i777d>-ext_infty NE space.                             "VWMEXT
325                READ TABLE i77id
326                     WITH KEY infty = <i777d>-infty
327                     BINARY SEARCH.

Hi Ramesh,
i have check the table HRP1680 in SAP4.7c but in ECC 6 it is not there. So i have create that table. Is it Info-type? or i have apply OSS notes.
regards
Rahul

Runtime Error in HR module t-code PPOCE [upgraded 4.7 to ECC6]

HI Gurus!
at my client site , we have upgraded 4.7 to ECC6. Now functional consultants are testing the system.When HR consultant working on PPOCE t-code ,the patch no of SAP HR - 0007. its giving runtime error.
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Except.     CX_SY_CREATE_DATA_ERROR          Date and Time                    19.08.2008     14:42:44
Short text
CREATE DATA: The specified type "HRP1680" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLRHDB" 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_DATA_ERROR', was not caught in
procedure "FILL_I777D" "(FORM)", 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 type "HRP1680" at CREATE DATA is no valid data type.
The type is either unknown or an object type.
Missing RAISING Clause in Interface
Program     SAPLRHDB
Include     LRHDBF00
Row     177
Module type (FORM)
Module Name FILL_I777D
Trigger Location of Exception
Program     SAPLRHDB
Include     LRHDBF00
Row     308
Module type(FORM)
Module Name     FILL_I777D
Source Code Extract
Line          SourceCde
278          **                HEADER   = FI_HEADER                    "ANDBCEK008264
279          **           TABLES                                       "ANDBCEK008264
280          **                FIELDTAB = FI_TAB                       "ANDBCEK008264
281          **           EXCEPTIONS                                   "ANDBCEK008264
282          **                OTHERS   = 4.                           "ANDBCEK008264
283          *                                                         "ANDBCEK008264
284          *      CALL FUNCTION 'DDIF_FIELDINFO_GET'                 "ANDBCEK008264
285          *           EXPORTING                                     "ANDBCEK008264
286          *                tabname        = fi_tabname              "ANDBCEK008264
287          **               FIELDNAME      = ' '                     "ANDBCEK008264
288          **               LANGU          = SY-LANGU                "ANDBCEK008264
289          **               LFIELDNAME     = ' '                     "ANDBCEK008264
290          **               ALL_TYPES      = ' '                     "ANDBCEK008264
291          *           IMPORTING                                     "ANDBCEK008264
292          *                x030l_wa       = fi_header               "ANDBCEK008264
293          **               DDOBJTYPE      =                         "ANDBCEK008264
294          **               DFIES_WA       =                         "ANDBCEK008264
295          **          TABLES                                        "ANDBCEK008264
296          **               DFIES_TAB      =                         "ANDBCEK008264
297          *          EXCEPTIONS                                     "ANDBCEK008264
298          *               not_found      = 1                        "ANDBCEK008264
299          *               internal_error = 2                        "ANDBCEK008264
300          *               OTHERS         = 3.                       "ANDBCEK008264
301          *
302          *      IF sy-subrc EQ 0.
303          *        i777d-tbtab_tabof = fi_header-tablen - tabnr_intlen.
304          *        i777d-pnnnn_tabof = i777d-tbtab_tabof - 8.
305          *      ENDIF.
306
307          *      ASSIGN char TO <any_field> CASTING TYPE (fi_tabname). "ANDDDIF
>>>>>                create data anyfield type (fi_tabname).                "ANDUNI
309                assign anyfield->* to <any_field>.                     "ANDUNI
310
311          *     we need a character view of <any_field> !!!            "ANDUNI
312                assign <any_field> to <char_field> casting type c.     "ANDUNI
313
314          *      DESCRIBE FIELD <any_field> LENGTH tablength            "ANDDDIF
315          *                                 IN BYTE MODE.               "ANDDDIF
316
317                DESCRIBE FIELD <char_field> LENGTH tablength           "ANDUNI
318                                            IN CHARACTER MODE.         "ANDUNI
319
320                <i777d>-tbtab_tabof = tablength - tabnr_intlen.        "ANDDDIF
321                <i777d>-pnnnn_tabof = <i777d>-tbtab_tabof - 8.         "ANDDDIF
322
323             ENDIF.
324              IF <i777d>-ext_infty NE space.                             "VWMEXT
325                READ TABLE i77id
326                     WITH KEY infty = <i777d>-infty
327                     BINARY SEARCH.
i have check the table HRP1680 in SAP4.7c but in ECC 6 it is not there. So i have create that table. Is it Info-type? or i have apply OSS notes.
regards
Rahul
Edited by: rahul deshmukh on Aug 20, 2008 11:52 AM

Hello,
I receive the same error when trying to change records of an infotype. Did you find a solution to this problem? I know your message is from 2008, but maybe you remember what you did to solve it
Thank you!
Iuliana

Pc00_m99_URMR - Runtime Error CONNE_IMPORT_WRONG_STRUCTURE in ECC 6.0

Similar Messages

Maybe you are looking for