BP Relationship dump

Hello!
Im facing a problem. If I try to see a BP's relationship view, I get a Short Dump.
In case if the BUT050 table containing the relationship datas, its working correctly. So, I only get the error, when the BP hasn't got relationship data.
But on the other hand, if i would like to create a new a BP, when I'll clicking on the Relationship button, I also get the dump.
Please, HELP!

Hi,
Please mention which CRM version you are using. From SAP CRM 2007, SAPGUI is not supported for transactions other than SPRO settings.
If you are using SAPGUI for CRM 2007 or CRM7.0, I would recommend you to use new CRM WebUI to create or edit BP. You can do creating masterdata with superuser/power user.
Hope this helps!
Regards,
Chethan

Similar Messages

  • Identify the relationship for the follwing fields

    Hi experts,
    I have to develop a report which is taking input as : -
    1.matnr (material number)
    2.werks (plant)
    3.stlan (BOM usage)
    4. stlal (alternative)
    And I need the output as : -
    AENNR (ECR : engg change request)
    I am unable to identify the relationships between these fields, plz suggest me the best ways to do this..
    Thanks in advance
    Gaurav
    Moderator message : Spec-dumping not allowed. Read forum rules before posting. Thread locked.
    Edited by: Vinod Kumar on Jul 5, 2011 2:11 PM

    after getting the records to internal table write the statement
    delete adjacent duplicate ................... before that write sort stament also......
    Deleting Adjacent Duplicate Entries
    To delete adjacent duplicate entries use the following statement:
    DELETE ADJACENT DUPLICATE ENTRIES FROM <itab>
                                      [COMPARING <f1> <f 2> ...
                                                 |ALL FIELDS].
    The system deletes all adjacent duplicate entries from the internal table <itab>. Entries are duplicate if they fulfill one of the following compare criteria:
    Without the COMPARING addition, the contents of the key fields of the table must be identical in both lines.
    If you use the addition COMPARING <f1> <f 2> ... the contents of the specified fields <f 1 > <f 2 > ... must be identical in both lines. You can also specify a field <f i > dynamically as the contents of a field <n i > in the form (<n i >). If <n i > is empty when the statement is executed, it is ignored. You can restrict the search to partial fields by specifying offset and length.
    If you use the addition COMPARING ALL FIELDS the contents of all fields of both lines must be identical.
    You can use this statement to delete all duplicate entries from an internal table if the table is sorted by the specified compare criterion.
    If at least one line is deleted, the system sets SY-SUBRC to 0, otherwise to 4.

  • Error in HRPAD31 ( Short dump Analysis )

    Hi friends,
    When i am changing the existing qualification or adding new qualification it is showing this error in short dump
    Pls advise me if there is some relationship i am missing in 031 ?
    here is the description of short dump
    Runtime Error  DBIF_RSQL_SQL_ERROR 
    Exception        CX_SY_OPEN_SQL_DB                                   
    Occurred on     10.09.2008 at   10:48:39                                                                               
    An SQL error occurred when accessing a table.                                                                               
    What happened?                                                                               
    What can you do?                                                                               
    Make a note of the actions and input which caused the error.                                                                               
    To resolve the problem, contact your SAP system administrator.                                                                               
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer   
    termination messages, especially those beyond their normal deletion        
    date.                                                                               
    Error analysis                                                                               
    An exception occurred. This exception is dealt with in more detail below   
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB',  wasneither                                                                   
    caught nor passed along using a RAISING clause, in the procedure"ADATA_DB" "FORM)"                                                                  
    Since the caller of the procedure could not have expected this exception to occcur, the running program was terminated.                                 
    The reason for the exception is:                                                                               
    How to correct the error                                                                               
    The exception must either be prevented, caught within the procedure "ADATA_DB" 
    "(FORM)", or declared in the procedure's RAISING clause.                       
    To prevent the exception, note the following:                                  
    Database error text........: "ORA-01653: unable to extend table SAPR3.HRPAD31 by 80 in tablespace PSAPSTABD"        
    Internal call code.........: "RSQL/INSR/HRPAD31"                
    Please check the entries in the system log (Transaction SM21).                                                                               
    You may able to find an interim solution to the problem           
    in the SAP note system. If you have access to the note system yourself, use the following search criteria:                                                                               
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                                       
    "SAPLRHAP" or "LRHAPF1K"                                                       
    "ADATA_DB"                                                                     
    System environment                                                                               
    SAP Release.............. "620"                                                                               
    Application server....... "Development"                                    
    Network address.......... "200.200.200.10"                             
    Operating system......... "Windows NT"                                 
    Release.................. "5.2"                                        
    Hardware type............ "2x IA64 Level 3"                            
    Character length......... 8 Bits                                       
    Pointer length........... 64 Bits                                      
    Work process number...... 1                                            
    Short dump setting....... "full"                                                                               
    Database server.......... "Development"                                    
    Database type............ "ORACLE"                                     
    Database name............ "VC3"                                        
    Database owner........... "SAPR3"                                                                               
    Character set............ "English_United State"                                                                               
    SAP kernel............... "640"                                        
    Created on............... "Aug 16 2007 23:23:39"                       
    Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version......... "OCI_920_SHARE "                                                                               
    Patch level.............. "196"                                        
    Patch text............... " "                                                                               
    Supported environment....                                              
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 
    User, transaction...                                                                               
    Client.............. 600                                                      
    User................ "HUSER"                                                
    Language key........ "E"                                                      
    Transaction......... "PP01 "                                                  
    Program............. "SAPLRHAP"                                               
    Screen.............. "MP100100 6000"                                          
    Screen line......... 16                                                                               
    Information on where terminated                                                                               
    The termination occurred in the ABAP program "SAPLRHAP" in "ADATA_DB".        
    The main program was "MP100100 ".                                                                               
    The termination occurred in line 57 of the source code of the (Include)  program LRHAPF1K"                                                           
    of the source code of program "LRHAPF1K" (when calling the editor 570).       
    Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
    the  procedure "ADATA_DB" "(FORM)" but was not handled locally, not declared in the RAISING clause of the procedure.                                              
    The procedure is in the program "SAPLRHAP ". Its source code starts in line 8  of the (Include) program "LRHAPF1K ".                                                                               
    PLS LET ME KNOW IF I NEED TO CHECK ALL MY CONFIGURATION ?

    Hi Ted,
    It is working, i just logged off and logged in. Now there is no error.
    Thanks for all your support. I am struggling on this isse from 3 days and could not sort it out.
    I appreciate on more time for your knowledge.
    I have rewarded the points also....  
    Regards
    HR user

  • Dump while Executing DTP

    Hi All,
    In process chain, While executing DTP( from PSA to ZINFOOBJECT-Master data), I am getting the following ABAP Dump:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    The internal table "???" could not be further extended. To enable
    error handling, the table had to be delete before this log was written.
    As a result, the table is displayed further down or, if you branch to
    the ABAP Debugger, with 0 rows.
    At the time of the termination, the following data was determined for
    the relevant internal table:
    Memory location: "Session memory"
    Row width: 5356
    Number of rows: 0
    Allocated rows: 138348
    Newly requested rows: 2 (in 69173 blocks)
    How to correct the error
        The amount of storage space (in bytes) filled at termination time was:
        Roll area...................... 416432
        Extended memory (EM)........... 2002720576
        Assigned memory (HEAP)......... 1999932640
        Short area..................... " "
        Paging area.................... 24576
        Maximum address space.......... 4294967295
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "TSV_TNEW_PAGE_ALLOC_FAILED" " "
        "SAPLRSSTATMAN" or "LRSSTATMANU12"
        "RSSTATMAN_UPDATE_DATASTATE_EXT"
    Could any one suggest solution
    Thanks and Regards,
    Umakanth Jaldu

    Hi Ramanm
    Please suggest how to do repair custom info object in RSRV and the info object is loading from two different dtps and both dtps are failing because of same error.The process of DTP is showing but not moving to next process type.
    Dump:
    Runtime Errors         TSV_TNEW_PAGE_ALLOC_FAILED
    Date and Time          31.03.2015 22:19:53
    |Short text                                                                                        |
    |    No more storage space available for extending an internal table.                              |
    |What happened?                                                                                    |
    |    You attempted to extend an internal table, but the required space was                         |
    |    not available.                                                                                |
    |What can you do?                                                                                  |
    |    Note which actions and input led to the error.                                                |
    |                                                                                                  |
    |    For further help in handling the problem, contact your SAP administrator                      |
    |    .                                                                                             |
    |                                                                                                  |
    |    You can use the ABAP dump analysis transaction ST22 to view and manage                        |
    |    termination messages, in particular for long term reference.                                  |
    |                                                                                                  |
    |    Try to find out (e.g. by targetted data selection) whether the                                |
    |    transaction will run with less main memory.                                                   |
    |                                                                                                  |
    |    If there is a temporary bottleneck, execute the transaction again.                            |
    |    -                                                                                             |
    |                                                                                                  |
    |    If the error persists, ask your system administrator to check the                             |
    |    following profile parameters:                                                                 |
    |                                                                                                  |
    |    o  ztta/roll_area            (1.000.000 - 15.000.000)                                         |
    |           Classic roll area per user and internal mode                                           |
    |           usual amount of roll area per user and internal mode                                   |
    |    o  ztta/roll_extension       (10.000.000 - 500.000.000)                                       |
    |           Amount of memory per user in extended memory (EM)                                      |
    |    o  abap/heap_area_total      (100.000.000 - 1.500.000.000)                                    |
    |           Amount of memory (malloc) for all users of an application                              |
    |           server. If several background processes are running on                                 |
    |           one server, temporary bottlenecks may occur.                                           |
    |           Of course, the amount of memory (in bytes) must also be                                |
    |           available on the machine (main memory or file system swap).                            |
    |           Caution:                                                                               |
    |           The operating system must be set up so that there is also                              |
    |           enough memory for each process. Usually, the maximum address                           |
    |           space is too small.                                                                    |
    |           Ask your hardware manufacturer or your competence center                               |
    |           about this.                                                                            |
    |           In this case, consult your hardware vendor                                             |
    |    abap/heap_area_dia:        (10.000.000 - 1.000.000.000)                                       |
    |           Restriction of memory allocated to the heap with malloc                                |
    |           for each dialog process.                                                               |
    |    Parameters for background processes:                                                          |
    |    abap/heap_area_nondia:        (10.000.000 - 1.000.000.000)                                    |
    |           Restriction of memory allocated to the heap with malloc                                |
    |           for each background process.                                                           |
    |    Other memory-relevant parameters are:                                                         |
    |    em/initial_size_MB:         (35-1200)                                                         |
    |           Extended memory area from which all users of an                                        |
    |           application server can satisfy their memory requirement.                               |
    |Error analysis                                                                                    |
    |    The internal table "???" could not be further extended. To enable                             |
    |    error handling, the table had to be delete before this log was written.                       |
    |    As a result, the table is displayed further down or, if you branch to                         |
    |    the ABAP Debugger, with 0 rows.                                                               |
    |                                                                                                  |
    |    At the time of the termination, the following data was determined for                         |
    |    the relevant internal table:                                                                  |
    |                                                                                                  |
    |    Memory location: "Session memory"                                                             |
    |    Row width: 5356                                                                               |
    |    Number of rows: 0                                                                             |
    |    Allocated rows: 138348                                                                        |
    |    Newly requested rows: 2 (in 69173 blocks)                                                     |
    |How to correct the error                                                                          |
    |    The amount of storage space (in bytes) filled at termination time was:                        |
    |                                                                                                  |
    |    Roll area...................... 416432                                                        |
    |    Extended memory (EM)........... 2002720576                                                    |
    |    Assigned memory (HEAP)......... 1999932640                                                    |
    |    Short area..................... " "                                                           |
    |    Paging area.................... 24576                                                         |
    |    Maximum address space.......... 4294967295                                                    |
    |                                                                                                  |
    |    If the error occures in a non-modified SAP program, you may be able to                        |
    |    find an interim solution in an SAP Note.                                                      |
    |    If you have access to SAP Notes, carry out a search with the following                        |
    |    keywords:                                                                                     |
    |                                                                                                  |
    |    "TSV_TNEW_PAGE_ALLOC_FAILED" " "                                                              |
    |    "SAPLRSSTATMAN" or "LRSSTATMANU12"                                                            |
    |    "RSSTATMAN_UPDATE_DATASTATE_EXT"                                                              |
    |                                                                                                  |
    |    If you cannot solve the problem yourself and want to send an error                            |
    |    notification to SAP, include the following information:                                       |
    |                                                                                                  |
    |    1. The description of the current problem (short dump)                                        |
    |                                                                                                  |
    |       To save the description, choose "System->List->Save->Local File                            |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    2. Corresponding system log                                                                   |
    |                                                                                                  |
    |       Display the system log by calling transaction SM21.                                        |
    |       Restrict the time interval to 10 minutes before and five minutes                           |
    |    after the short dump. Then choose "System->List->Save->Local File                             |
    |    (Unconverted)".                                                                               |
    |                                                                                                  |
    |    3. If the problem occurs in a problem of your own or a modified SAP                           |
    |    program: The source code of the program                                                       |
    |       In the editor, choose "Utilities->More                                                     |
    |    Utilities->Upload/Download->Download".                                                        |
    |                                                                                                  |
    |    4. Details about the conditions under which the error occurred or which                       |
    |    actions and input led to the error.                                                           |
    |                                                                                                  |
    |System environment                                                                                |
    |    SAP-Release 701                                                                               |
    |                                                                                                  |
    |    Application server... "sapXXXa1"                                                              |
    |    Network address...... "10.10.29.72"                                                           |
    |    Operating system..... "AIX"                                                                   |
    |    Release.............. "7.1"                                                                   |
    |    Hardware type........ "00CB77444C00"                                                          |
    |    Character length.... 16 Bits                                                                  |
    |    Pointer length....... 64 Bits                                                                 |
    |    Work process number.. 4                                                                       |
    |    Shortdump setting.... "full"                                                                  |
    |                                                                                                  |
    |    Database server... "sXXX341.sac.XXX"                                                     |
    |    Database type..... "ORACLE"                                                                   |
    |    Database name..... "XXX"                                                                      |
    |    Database user ID.. "SAPSR3"                                                                   |
    |                                                                                                  |
    |    Terminal.......... "GSSM0510"                                                                 |
    |                                                                                                  |
    |    Char.set.... "C"                                                                              |
    |                                                                                                  |
    |    SAP kernel....... 720                                                                         |
    |    created (date)... "Feb 10 2014 21:43:58"                                                      |
    |    create on........ "AIX 2 5 00092901D600"                                                      |
    |    Database version. "OCI_102, 11.2.0.2.0, V1, default"                                          |
    |                                                                                                  |
    |    Patch level. 525                                                                              |
    |    Patch text.. " "                                                                              |
    |                                                                                                  |
    |    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"               |
    |    SAP database version. 720                                                                     |
    |    Operating system..... "AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7"                                    |
    |                                                                                                  |
    |    Memory consumption                                                                            |
    |    Roll.... 416432                                                                               |
    |    EM...... 2002720576                                                                           |
    |    Heap.... 1999932640                                                                           |
    |    Page.... 24576                                                                                |
    |    MM Used. 3938002576                                                                           |
    |    MM Free. 59192960                                                                             |
    |User and Transaction                                                                              |
    |    Client.............. 100                                                                      |
    |    User................ "XXXX"                                                               |
    |    Language Key........ "E"                                                                      |
    |    Transaction......... " "                                                                      |
    |    Transactions ID..... "551B198729F80700E10080000A0A1D12"                                       |
    |                                                                                                  |
    |    Program............. "SAPLRSSTATMAN"                                                          |
    |    Screen.............. "SAPLRSBM_REQUEST_GUI 0300"                                              |
    |    Screen Line......... 5                                                                        |
    |                                                                                                  |
    |    Information on caller of Remote Function Call (RFC):                                          |
    |    System.............. "XXX"                                                                    |
    |    Database Release.... 701                                                                      |
    |    Kernel Release...... 720                                                                      |
    |    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)                            |
    |    Call Type........... "synchronous and non-transactional (emode 0, imode 0)"                   |
    |    Inbound TID.........." "                                                                      |
    |    Inbound Queue Name..." "                                                                      |
    |    Outbound TID........." "                                                                      |
    |    Outbound Queue Name.." "                                                                      |
    |                                                                                                  |
    |    Client.............. 100                                                                      |
    |    User................ "XXXX"                                                               |
    |    Transaction......... "RSA1"                                                                   |
    |    Call Program........."SAPLRSM1"                                                               |
    |    Function Module..... "RSS2_CALL_FCODE_EMPTY_GLOBALS"                                          |
    |    Call Destination.... "NONE"                                                                   |
    |    Source Server....... "sapXXXa1_XXX_12"                                                        |
    |    Source IP Address... "10.10.29.72"                                                            |
    |                                                                                                  |
    |    Additional information on RFC logon:                                                          |
    |    Trusted Relationship " "                                                                      |
    |    Logon Return Code... 0                                                                        |
    |    Trusted Return Code. 0                                                                        |
    |                                                                                                  |
    |    Note: For releases < 4.0, information on the RFC caller are often                             |
    |    only partially available.                                                                     |
    |Information on where terminated                                                                   |
    |    Termination occurred in the ABAP program "SAPLRSSTATMAN" - in                                 |
    |     "RSSTATMAN_UPDATE_DATASTATE_EXT".                                                            |
    |    The main program was "SAPMSSY1 ".                                                             |
    |                                                                                                  |
    |    In the source code you have the termination point in line 306                                 |
    |    of the (Include) program "LRSSTATMANU12".                                                     |
    |Source Code Extract                                                                               |
    |Line |SourceCde                                                                                   |
    |  276|       l_s_ext_db-records_techok  <> l_s_ext-records_techok.                                |
    |  277|      l_s_ext-ts_tech_changed = l_timestamp.                                                |
    |  278|      l_s_ext-ts_data_changed = l_timestamp.                                                |
    |  279|      l_changed = 'X'.                                                                      |
    |  280|    else.                                                                                   |
    |  281|      l_s_ext-ts_tech_changed = l_s_ext_db-ts_tech_changed.                                 |
    |  282|    endif.                                                                                  |
    |  283|    if l_s_ext-requests_techok = 0.                                                         |
    |  284|      clear l_s_ext-ts_tech_changed.                                                        |
    |  285|    endif.                                                                                  |
    |  286|                                                                                            |
    |  287|    if l_s_ext_db-requests_error <> l_s_ext-requests_error  or                              |
    |  288|       l_s_ext_db-records_error  <> l_s_ext-records_error.                                  |
    |  289|      l_s_ext-ts_error_changed = l_timestamp.                                               |
    |  290|      l_s_ext-ts_data_changed  = l_timestamp.                                               |
    |  291|      l_changed = 'X'.                                                                      |
    |  292|    else.                                                                                   |
    |  293|      l_s_ext-ts_error_changed = l_s_ext_db-ts_error_changed.                               |
    |  294|    endif.                                                                                  |
    |  295|    if l_s_ext-requests_error = 0.                                                          |
    |  296|      clear l_s_ext-ts_error_changed.                                                       |
    |  297|    endif.                                                                                  |
    |  298|                                                                                            |
    |  299|    if l_s_ext_db-requests_all <> l_s_ext-requests_all or                                   |
    |  300|       l_s_ext_db-records_all  <> l_s_ext-records_all.                                      |
    |  301|      l_s_ext-ts_data_changed = l_timestamp.                                                |
    |  302|      l_changed = 'X'.                                                                      |
    |  303|    endif.                                                                                  |
    |  304|                                                                                            |
    |  305|    l_t_part[] = i_t_part[].                                                                |
    |>>>>>|    sort l_t_part by timestamp_verb descending.                                             |
    |  307|    read table l_t_part into l_s_part index 1.                                              |
    |  308|    l_s_ext-ts_last_request = l_s_part-timestamp_verb.                                      |
    |  309|    l_s_ext-last_request    = l_s_part-partnr.                                              |
    |  310|    if l_s_ext_db-ts_last_request <> l_s_ext-ts_last_request or                             |
    |  311|       l_s_ext_db-last_request  <> l_s_ext-last_request.                                    |
    |  312|      l_s_ext-ts_data_changed = l_timestamp.                                                |
    |  313|      l_changed = 'X'.                                                                      |
    |  314|    endif.                                                                                  |
    |  315|    if l_changed = 'X'.                                                                     |
    |  316|      modify rsmdatastate_ext from l_s_ext.                                                 |
    |  317|    endif.                                                                                  |
    |  318|  endif.                                                                                    |
    |  319|                                                                                            |
    |  320|  if not ( i_dta_type = rsstm_c_types-psa_new or                                            |
    |  321|           i_dta_type = rsstm_c_types-psa_old ).                                            |
    |  322|    call function 'RSM_LAST_CHANGE_CHECK_UPDATE'                                            |
    |  323|      exporting                                                                             |
    |  324|        i_dta   = i_dta(30)                                                                 |
    |  325|        i_tstmp = l_s_ext-ts_data_changed.                                                  |
    |
    |Active Calls/Events                                                                               |
    |No.   Ty.          Program                             Include                             Line   |
    |      Name                                                                                        |
    |   16 FUNCTION     SAPLRSSTATMAN                       LRSSTATMANU12                         306  |
    |      RSSTATMAN_UPDATE_DATASTATE_EXT                                                              |
    |   15 FORM         SAPLRSM1                            LRSM1U23                              768  |
    |      RSM1_UPDATE_RSMDATASTATE                                                                    |
    |   14 FORM         SAPLRSM1                            LRSM1F08                             5520  |
    |      RSM1_INIT_PARTTAB                                                                           |
    |   13 FORM         SAPLRSM1                            LRSM1U23                              187  |
    |      RSSM_UPDATE_RSMDATASTATE                                                                    |
    |   12 FUNCTION     SAPLRSM1                            LRSM1U23                              139  |
    |      RSSM_UPDATE_RSMDATASTATE                                                                    |
    |   11 METHOD       CL_RSSM_STATMAN===============CP    CL_RSSM_STATMAN===============CM00L    15  |
    |      CL_RSSM_STATMAN=>IF_RSBK_REQUEST_OBSERVER~AFTER_FINAL_STATE_TRANSITION                      |
    |   10 METHOD       CL_RSBK_REQUEST_STATE=========CP    CL_RSBK_REQUEST_STATE=========CM01S    13  |
    |      CL_RSBK_REQUEST_STATE=>AFTER_FINAL_STATE_TRANSITION                                         |
    |    9 METHOD       CL_RSBK_REQUEST===============CP    CL_RSBK_REQUEST===============CM00H    11  |
    |      CL_RSBK_REQUEST=>IF_RSBK_REQUEST~SET_USTATE_RED                                             |
    |    8 FORM         SAPLRSBM_REQUEST_GUI                LRSBM_REQUEST_GUIF01                   26  |
    |      SET_USTATE_300                                                                              |
    |    7 MODULE (PAI) SAPLRSBM_REQUEST_GUI                LRSBM_REQUEST_GUII01                  122  |
    |      USER_COMMAND_0300                                                                           |
    |    6 MODULE (PAI) SAPLRSBM_REQUEST_GUI                LRSBM_REQUEST_GUII01                   70  |
    |      USER_COMMAND_100                                                                            |
    |    5 FUNCTION     SAPLRSBM_REQUEST_GUI                LRSBM_REQUEST_GUIU01                   24  |
    |      RSBM_SHOW_REQUEST                                                                           |
    |    4 FUNCTION     SAPLRSS2                            LRSS2U26                               39  |
    |      RSS2_CALL_FCODE_EMPTY_GLOBALS                                                               |
    |    3 FORM         SAPLRSS2                            LRSS2U26                                1  |
    |      RSS2_CALL_FCODE_EMPTY_GLOBALS                                                               |
    |    2 FORM         SAPMSSY1                            SAPMSSY1                               85  |
    |      REMOTE_FUNCTION_CALL                                                                        |
    |    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30  |
    |      %_RFC_START                                                                                 |
    Please advise me,
    Thanks and Regards,
    Uma

  • Adding new fields to business partner relationship

    Hi all,
    We are trying to add new fields to business partneru2019s relationship using EEWB. We are adding 4 new fields when relationship type is "Is shareholder of", so we have created a new project at transaction EEWB and then a new extension and the wizard is started. At the wizard, we have define the 4 new fields with cardinality 1:1 and time dependent without gaps.
    Also we have done all the extension setup, so the new fields only appears when that relationship is created and we can fill the new fields.
    The problem that we have is that every time that you create a new relationship type "Is shareholder of", even if you fill the new fields or not, the system spend more than one hour to save the data, having also a "STACK_STATE_NO_ROLL_MEMORY" dump... It seems that the system goes inside a loop that never ends, but we haven't change any function, because the standard functionality is enough for us.
    Any help on how to proceed?
    Thanks in advance!!

    Please, anyone can help?
    Thanks!!

  • How to do changeover of relationship types in BOR ???

    At our site, the method display_attachment of cl_gos_document service short dumps.  The short dump message says that the BOR relationship type "ATTA" is no longer supported, and that this is due to an "incomplete changeover" of BOR relationships at this site.
    I have a customer message into SAP, but I'm wondering if anyone has been thru this before at their site and knows what to do.
    Uwe - I suspect this may be related to the other problem we're talking about regarding the cl_bds_document_set call.
    djh

    At our site, the method display_attachment of cl_gos_document service short dumps.  The short dump message says that the BOR relationship type "ATTA" is no longer supported, and that this is due to an "incomplete changeover" of BOR relationships at this site.
    I have a customer message into SAP, but I'm wondering if anyone has been thru this before at their site and knows what to do.
    Uwe - I suspect this may be related to the other problem we're talking about regarding the cl_bds_document_set call.
    djh

  • Reporting services with R2 on DPM2012 - Could not establish trust relationship for the SSL/TLS secure channel

    Hi everyone,
    A somewhat similar question has been asked before by others but none of the answers given has helped me.I am attempting a DPM 2012 installation, which is failing at the "deploying reports" stage.My analysis of logs seems to point me in the direction of an SSL
    error, which does not make sense since the configuration files say SSL is disabled (or at least, should be).
    Here are the symptoms:
    1.I am able to browse http://FQDN/Reports_MSDPM2012 folder from internet explorer
    2.I am also able to browse http://FQDN/ReportServer_MSDPM2012 from internet explorer
    3.The information given in the logs and relevant config files is shown below:
    <<RSREPORTSERVER.CONFIG>>
    <ConnectionType>Default</ConnectionType>
    <LogonUser></LogonUser>
    <LogonDomain></LogonDomain>
    <LogonCred></LogonCred>
    <InstanceId>MSRS10_50.MSDPM2012</InstanceId>
    <InstallationID>{d9b1c335-5842-4a81-9148-79184c38bf09}</InstallationID>
    <Add Key="SecureConnectionLevel" Value="0"/>
    <Add Key="CleanupCycleMinutes" Value="10"/>
    <Add Key="MaxActiveReqForOneUser" Value="20"/>
    <Add Key="DatabaseQueryTimeout" Value="120"/>
    <Add Key="RunningRequestsScavengerCycle" Value="60"/>
    <Add Key="RunningRequestsDbCycle" Value="60"/>
    <Add Key="RunningRequestsAge" Value="30"/>
    <Add Key="MaxScheduleWait" Value="5"/>
    <Add Key="DisplayErrorLink" Value="true"/>
    <Add Key="WebServiceUseFileShareStorage" Value="false"/>
    <!--  <Add Key="ProcessTimeout" Value="150" /> -->
    <!--  <Add Key="ProcessTimeoutGcExtension" Value="30" /> -->
    <!--  <Add Key="WatsonFlags" Value="0x0430" /> full dump-->
    <!--  <Add Key="WatsonFlags" Value="0x0428" /> minidump -->
    <!--  <Add Key="WatsonFlags" Value="0x0002" /> no dump-->
    <Add Key="WatsonFlags" Value="0x0428"/>
    <Add Key="WatsonDumpOnExceptions" 
    4.The DPM log file still appears to be using SSL even though i used reporting services configuration to remove SSL bindings:
    running.Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.BackEndErrorException: exception ---> Microsoft.Internal.EnterpriseStorage.Dls.Setup.Exceptions.ReportDeploymentException:
    exception ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.WebException: The underlying connection was closed: Could
    not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException:
    The remote certificate is invalid according to the validation procedure.
       at System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest,
    Exception exception)
    5:I do have an SCCM site on the default web site used by SMS clients but on different ports
    I am stumped.Somebody please give some advice
    Thank you

    Hi
    This is an old post but did you come right?

  • Getting Dump CALL_FUNCTION_SYSCALL_ONLY

    Hi Expert ,
    while finished the   SM:SELFDIAGNOSIS  this job in Solution manager system so in that moment i'm getting a CALL_FUNCTION_SYSCALL_ONLY dump in quality server.
    Runtime Errors         CALL_FUNCTION_SYSCALL_ONLY
    Date and Time          25.08.2011 01:43:31
         Short text
             You are not authorized to logon to the target system (error code 0).
         What happened?
             Error in the ABAP Application Program
             The current ABAP program "SAPLSYST" had to be terminated because it has
             come across a statement that unfortunately cannot be executed.
         What can you do?
             Note down which actions and inputs caused the error.
             To process the problem further, contact you SAP system
             administrator.
             Using Transaction ST22 for ABAP Dump Analysis, you can look
             at and manage termination messages, and you can also
             keep them for a long time.
         Error analysis
             RFC calls (Remote Function Calls) were sent with the invalid user
             ID "DDIC ". The receiving system regarded the first call as a system
             call and therefore accepted it without a valid user ID.
             However, the last call was to an external function module and
             was thus rejected.
             The action was carried out by caller "DDIC " with client 100 from within
             system "SOL " and transaction " ".
         How to correct the error
             In the trusted relation, a logon failure can be caused either by the
             fact that the entered security key for system "SOL " is invalid or that the
              trusted system data has lost its validity due to a timeout.
             The error code of the trusted system was 2.
             Meaning:
               0    Correct logon as trusted system mode
               1 No trusted system entry for the caller system "SOL " or the
                    security key entry for system "SOL " is invalid
               2 User "DDIC " has no RFC authorization (authorization object
                    S_RFCACL) for caller "DDIC " with client 100.
               3    The timestamp of the logon data is invalid
             The error code of the SAP logon procedure was 0.
             Meaning:
               0    Logon was correct
               1    Wrong password or invalid user ID
               2    User is locked
               3    Too many logon attempts
    Runtime Errors         CALL_FUNCTION_SYSCALL_ONLY
    D     ate and Time          25.08.2011 01:43:31     
               5    Error in authorization buffer (internal error)
               6    No external user check
               7    Invalid user type
               8    Validity period of user exceeded
         System environment
             SAP-Release 701
             Application server... "QAserver"
             Network address...... "192.168.1.6"
             Operating system..... "AIX"
             Release.............. "6.1"
             Hardware type........ "000A154AD400"
             Character length.... 16 Bits
             Pointer length....... 64 Bits
             Work process number.. 0
             Shortdump setting.... "full"
             Database server... "QAserver"
             Database type..... "DB6"
             Database name..... "QAS"
             Database user ID.. "SAPQAS"
             Terminal.......... " "
             Char.set.... "C"
             SAP kernel....... 701
             created (date)... "Sep 23 2010 21:55:35"
             create on........ "AIX 2 5 00CB5A5B4C00"
             Database version. "DB6_81 "
             Patch level. 111
             Patch text.. " "
             Database............. "DB6 08.02., DB6 09."
             SAP database version. 701
             Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7"
             Memory consumption
             Roll.... 16192
             EM...... 4189848
             Heap.... 0
             Page.... 0
             MM Used. 1226088
             MM Free. 2961160
         User and Transaction
             Client.............. 000
             User................ "SAPSYS"
             Language Key........ "E"
             Transaction......... " "
             Transactions ID..... "858DCEE0F1E5F1B3AAFCE61F137E15A3"
             Program............. "SAPLSYST"
             Screen.............. "SAPMSSY1 3004"
             Screen Line......... 2
    Runtime Errors         CALL_FUNCTION_SYSCALL_ONLY
    D     ate and Time          25.08.2011 01:43:31     
             Information on caller of Remote Function Call (RFC):
             System.............. "SOL"
             Database Release.... 701
             Kernel Release...... 701
             Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
             Call Type........... "synchron and non-transactional (emode 0, imode 0)"
             Inbound TID.........." "
             Inbound Queue Name..." "
             Outbound TID........." "
             Outbound Queue Name.." "
             Client.............. 100
             User................ "DDIC"
             Transaction......... " "
             Call Program........."CL_DSMOP_RFC_WATCHER==========CP"
             Function Module..... "RFCPING"
             Call Destination.... "SM_QASCLNT100_TRUSTED"
             Source Server....... "solid_SOL_01"
             Source IP Address... "192.168.1.2"
             Additional information on RFC logon:
             Trusted Relationship "X"
             Logon Return Code... 0
             Trusted Return Code. 2
             Note: For releases < 4.0, information on the RFC caller are often
             only partially available.
         Information on where terminated
             Termination occurred in the ABAP program "SAPLSYST" - in "TABLE_COMPRESS".
             The main program was "SAPMSSY1 ".
             In the source code you have the termination point in line 67
             of the (Include) program "SAPMSSY1".
         Source Code Extract
         Line     SourceCde
            37     endmodule.
            38     
            39     module %_rfcdia_call output.
            40         "Do not display screen !
            41         call 'DY_INVISIBLE_SCREEN'.
            42         perform remote_function_diacall.
            43     endmodule.
            44     
            45     module %_cpic_start.
            46       if sy-xprog(4) = '%RFC'.
            47         perform remote_function_call using rfctype_external_cpic.
            48       else.
            49         call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
            50         perform cpic_call using convid.
            51       endif.
            52     endmodule.
            53     
            54     
    Runtime Errors         CALL_FUNCTION_SYSCALL_ONLY
    D     ate and Time          25.08.2011 01:43:31     
            55     form cpic_call using convid type c.
            56       communication send id convid buffer header.
            57       if sy-subrc eq 0.
            58         perform (sy-xform) in program (sy-xprog).
            59       else.
            60         message a800.
            61       endif.
            62     endform.
            63     
            64     form remote_function_call using value(type).
            65       data rc type i value 0.
            66       do.
         >>>>>         call 'RfcImport' id 'Type' field type.
            68         if sy-xprog = 'JAVA'.
            69           system-call plugin
            70                       id 'JAVA' value 'FORW_JAVA'
            71                       id 'RC'   value rc.
            72     *   if there is no rollout on the JAVA side which
            73     *   rolls both, JAVA and ABAP, we return to the
            74     *   C-Stack and reach this point
            75     
            76     *   in case there was an rollout, the ABAP-C stack is lost
            77     *   and we jump direkt to this point
            78     
            79     *   here we trigger the rollout on this Abap side with
            80     *   the following statement
            81           system-call plugin
            82                       id 'JAVA' value 'ROLL_OUT'
            83                       id 'RC'   value rc.
            84         else.
            85           perform (sy-xform) in program (sy-xprog).
            86           rsyn >scont sysc 00011111 0.
         Contents of system fields
         Name     Val.
         SY-SUBRC     0
         SY-INDEX     2
         SY-TABIX     0
         SY-DBCNT     1
         SY-FDPOS     0
         SY-LSIND     0
         SY-PAGNO     0
         SY-LINNO     1
         SY-COLNO     1
         SY-PFKEY     
         SY-UCOMM     
         SY-TITLE     CPIC and RFC Control
         SY-MSGTY     
         SY-MSGID     
         SY-MSGNO     000
         SY-MSGV1     
         SY-MSGV2     
         SY-MSGV3     
         SY-MSGV4     
         SY-MODNO     0
         SY-DATUM     20110825
         SY-UZEIT     014330
         SY-XPROG     SAPLSYST
    Runtime Errors         CALL_FUNCTION_SYSCALL_ONLY
    D     ate and Time          25.08.2011 01:43:31     
         SY-XFORM     RFCPING
         Active Calls/Events
         No.   Ty.          Program                             Include                             Line
               Name
             2 FORM         SAPMSSY1                            SAPMSSY1                               67
               REMOTE_FUNCTION_CALL
             1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
               %_RFC_START
         Chosen variables
         Name
             Val.
         No.          2     Ty.      FORM
         Name      REMOTE_FUNCTION_CALL
         %_DUMMY$$
             0000
             0000
             2222
             0000
         SY-REPID
             SAPMSSY1
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
             5454555322222222222222222222222222222222
             310D339100000000000000000000000000000000
         SYST-REPID
             SAPMSSY1
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
             5454555322222222222222222222222222222222
             310D339100000000000000000000000000000000
         HEADER
             000000000000
             000000000000
         TYPE
             3
             0000
             0003
         SY-XPROG
             SAPLSYST
             0000000000000000000000000000000000000000
             0000000000000000000000000000000000000000
             5454555522222222222222222222222222222222
             310C393400000000000000000000000000000000
         %_ARCHIVE
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    Runtime Errors         CALL_FUNCTION_SYSCALL_ONLY
    D     ate and Time          25.08.2011 01:43:31     
         RC
             0
             0000
             0000
         SY-XFORM
             RFCPING
             000000000000000000000000000000
             000000000000000000000000000000
             544544422222222222222222222222
             26309E700000000000000000000000
         %_SPACE
             0
             0
             2
             0
         No.          1     Ty.      MODULE (PBO)
         Name      %_RFC_START
         %_PRINT
                 000                                                                                0###
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
             2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
             0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
         RFCTYPE_INTERNAL
             3
             0000
             0003
         Internal notes
             The termination was triggered in function "PrepareSignOnRabax"
             of the SAP kernel, in line 5385 of the module
              "//bas/701_REL/src/krn/rfc/abrfcfun.c#13".
             The internal operation just processed is "CALY".
             Internal mode was started at 20110825014330.
             The called function module was "RFCPING ".
             Caller system......: "SOL "
             Caller.............: "DDIC "
             Caller client......: 100
             RFC user ID........: "DDIC "
             RFC client.........: 100
             Transaction code...: " "
             Logon return code..: 0
             Trusted return code: 2
             Note: For releases < 4.0, information on the caller may not exist
         Active Calls in SAP Kernel
         Lines of C Stack in Kernel (Structure Differs on Each Platform)
         => 64 bit R/3 Kernel
         => 64 bit AIX Kernel
         => Heap limit      = unlimited
         => Stack limit     = 4294967296
         => Core limit      = 1073741312
         => File size limit = unlimited
    Runtime Errors         CALL_FUNCTION_SYSCALL_ONLY
    D     ate and Time          25.08.2011 01:43:31     
         => Heap address  = 0x0x11cd64d20
         => Stack address = 0xfffffffffff4850
         => Stack low     =  0xfffffffffff4850
         => Stack high    =  0xffffffffffff810
         => Stack Trace:
              AixStack() at 0x10007fd28
              CTrcStack2() at 0x10007fe20
              rabax_CStackSave__Fv() at 0x100068b10
              ab_rabax() at 0x1000650a4
              PrepareSignOnRabax() at 0x100e3beb0
              ab_rfcimport() at 0x100e3a7e4
              ab_jcaly__Fv() at 0x10005aeb8
              ab_extri__Fv() at 0x10052701c
              ab_xevent__FPCUs() at 0x100a31b84
              ab_dstep() at 0x100805368
              dynpmcal() at 0x100d7f2b4
              dynppbo0() at 0x100d7cdf8
              dynprctl() at 0x100d84bc4
              dynpen00() at 0x100d786a8
              Thdynpen00() at 0x10009b01c
              TskhLoop() at 0x10009ffa8
              ThStart() at 0x1000b7dd0
              DpMain() at 0x1015518ec
              nlsui_main() at 0x101a4b620
         List of ABAP programs affected
         Index     Typ     Program     Group     Date     Time     Size     Lang.
              0     Prg     SAPMSSY1          0     11.04.2005     09:27:15         21504     E
              1     Prg     SAPLSRFC          1     17.12.2008     07:36:53         43008     E
              2     Prg     SAPRFCSL          0     13.02.2005     17:31:45         17408     E
              3     Typ     RFCSYSACL          0     13.02.2005     17:31:45          7168     
              4     Prg     SAPLSYST          4     29.11.2010     01:19:16         35840     E
              5     Typ     SYST          0     09.09.2004     14:18:12         31744     
         Directory of Application Tables
         Name                                     Date       Time       Lngth
             Val.
         Program      SAPMSSY1
         SYST                                       .  .       :  :     00004612
             \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0\0
         Program      SAPRFCSL
         RFCSYSACL                                  .  .       :  :     00001760
             SOL                             QAS
    Please assist me asap.
    Regards
    Shubh
    Edited by: Shiv ji Mishra on Sep 17, 2011 9:38 AM

    Hello,
    It seems some trusted RFC issue. Check the RFCs, somewhere it might be possible that the DDIC user is being used and it doesn't have proper RFC authorization. Try to use some different user.
    See the extract from the dump
    The action was carried out by caller "DDIC " with client 100 from within system "SOL " and transaction " ". How to correct the error In the trusted relation, a logon failure can be caused either by the fact that the entered security key for system "SOL " is invalid or that the trusted system data has lost its validity due to a timeout. The error code of the trusted system was 2. Meaning: 0 Correct logon as trusted system mode 1 No trusted system entry for the caller system "SOL " or the security key entry for system "SOL " is invalid 2 User "DDIC " has no RFC authorization (authorization object S_RFCACL) for caller "DDIC " with client 100
    Thanks

  • ABAP Dump GETWA_NOT_ASSIGNED_RANGE for program /SDF/CL_EM_DUMP_COLLECTOR=====CP

    Hello,
    I am getting ABAP runtime error GETWA_NOT_ASSIGNED_RANGE every 10 minutes in my ECC Production system. This dump is occurring for program /SDF/CL_EM_DUMP_COLLECTOR=====CP with short text as "Field symbol is not assigned".
    Error Analysis:
    "A field symbol that was not assigned was accessed
    (data segment no. "-1").
    The field symbol is no longer assigned because there was an attempt
    makde previously in a Unicode program to set the field symbol using
    ASSIGN with offset and/or length specification. Here, the memory
    addressed by the offset/length specification was not within the
    allowed area."
    Information on where terminated:
    "Termination occurred in the ABAP program "/SDF/CL_EM_DUMP_COLLECTOR=====CP" -
         in "GET_FIELDTABLE".
        The main program was "SAPMSSY1 ".
        In the source code you have the termination point in line 51
        of the (Include) program "/SDF/CL_EM_DUMP_COLLECTOR=====CM005"."
    Server-Side Connection Information:
    "Information on caller of Remote Function Call (RFC):
        System.............. "Solution Manager"
        Installation Number. " "
        Database Release.... 702
        Kernel Release...... 720
        Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
        Call Type........... "synchronous and non-transactional (emode 0, imode 0)"
        Inbound TID.........." "
        Inbound Queue Name..." "
        Outbound TID........." "
        Outbound Queue Name.." "
        Client.............. Prod Client
        User................ "SolMan user"
        Transaction......... " "
        Call Program........."SAPLE2EEM_DATA_COLLECTION"
        Function Module..... "/SDF/E2EEM_GET_DATA"
        Call Destination.... "SM_<ECC_PROD>_READ"
        Source Server....... "Solution Manager"
        Source IP Address... "Solution Manager"
        Additional information on RFC logon:
        Trusted Relationship " "
        Logon Return Code... 0
        Trusted Return Code. 0"
    I searched for SAP notes and other SCN discussion but could not find relevant information. Can someone please assist me? Thanks.
    Tanay

    Hi Srivastava,
    What process or transaction you are executing, when you got this dump, please share the detail.
    In SAP there so many areas where we can have this ABAP dump, please also share the snap shot in ST22 " How to Correct" part of dump which carries the exact program name e.g. in below snapshot program name, short text, etc  is given to search SAP note.
    Please also refer to the following sap notes:
    1840910 - Dump CHECK_SELOPT_ILLEGAL_SIGN
    1729771 - Collective corrections as of ST-PI 2008_1 SP06
    1011229 - ST-PI: Corrections for E2E Diagnostics
    Regards
    Javed

  • Regarding EXPORT_COMPRESS_ERROR ABAP dump

    Hello Experts,
    In our BI System, we are getting EXPORT_COMPRESS_ERROR ABAP dump. And not able to find out any SAP notes regarding this dump.
    Waiting for your kind response.
    Runtime Errors         EXPORT_COMPRESS_ERROR
    Date and Time          11.04.2008 16:40:42
    Short text
    Internal error when compressing data.
    What happened?
    Error in the SAP kernel.
    The current ABAP "SAPLRSDRI_SERVICES" program had to be terminated because the
    ABAP processor detected an internal system error.
    In the EXPORT TO DATABASE statement, an internal error occurred
    when compressing data.
    What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
    Error analysis
    There is an internal system error.
    eliminated with ABAP/4.
    Last error logged in SAP kernel
    Component............ "EM"
    Place................ "SAP-Server u962004s_P38_67 on host u962004s (wp 23)"
    Version.............. 37
    Error code........... 7
    Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "
    Description.......... " "
    System call.......... " "
    Module............... "emxx.c"
    Line................. 1881
    The error reported by the operating system is:
    Error number..... " "
    Error text....... " "
    How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "EXPORT_COMPRESS_ERROR" " "
    "SAPLRSDRI_SERVICES" or "LRSDRI_SERVICESF01"
    "DATA_WRAP_UC"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
    In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    System environment
    SAP-Release 700
    Application server... "u962004s"
    Network address...... "10.200.230.110"
    Operating system..... "HP-UX"
    Release.............. "B.11.23"
    Hardware type........ "ia64"
    Character length.... 8 Bits
    Pointer length....... 64 Bits
    Work process number.. 23
    Shortdump setting.... "full"
    Database server... "u962004s"
    Database type..... "ORACLE"
    Database name..... "P38"
    Database user ID.. "SAPP38"
    Char.set.... "de_DE.iso88591"
    SAP kernel....... 700
    created (date)... "Dec 30 2007 21:06:56"
    create on........ "HP-UX B.11.23 U ia64"
    Database version. "OCI_102 (10.2.0.2.0) "
    Patch level. 141
    Patch text.. " "
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "HP-UX B.11"
    Memory consumption
    Roll.... 6219104
    EM...... 2291965488
    Heap.... 2302579280
    Page.... 16384
    MM Used. 4399764848
    MM Free. 194652624
    User and Transaction
    Client.............. 100
    User................ "K59461"
    Language Key........ "D"
    Transaction......... " "
    Transactions ID..... "47FF35AD14F65486E10000000AC8E66E"
    Program............. "SAPLRSDRI_SERVICES"
    Screen.............. "SAPMSSY1 3004"
    Screen Line......... 2
    Information on caller of Remote Function Call (RFC):
    System.............. "P38"
    Database Release.... 700
    Kernel Release...... 700
    Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
    Call Type........... "asynchron with reply and non-transactional (emode 0,
    imode 0)"
    Inbound TID.........." "
    Inbound Queue Name..." "
    Outbound TID........." "
    Outbound Queue Name.." "
    Client.............. 100
    User................ "K59461"
    Transaction......... " "
    Call Program........."SAPLZ_ZOP01_VCUBES"
    Function Module..... "RSDRI_INFOPROV_READ_RFC"
    Call Destination.... "NONE"
    Source Server....... "u962004s_P38_67"
    Source IP Address... "10.200.230.110"
    Additional information on RFC logon:
    Trusted Relationship " "
    Logon Return Code... 0
    Trusted Return Code. 0
    Note: For releases < 4.0, information on the RFC caller are often
    only partially available.
    Information on where terminated
    Termination occurred in the ABAP program "SAPLRSDRI_SERVICES" - in
    "DATA_WRAP_UC".
    The main program was "SAPMSSY1 ".
    In the source code you have the termination point in line 194
    of the (Include) program "LRSDRI_SERVICESF01".
    Source Code Extract
    Line
    SourceCde
    164
    165
    CLEAR: l_string.
    166
    167
    CALL METHOD cl_abap_container_utilities=>fill_container_c
    168
    EXPORTING
    169
    im_value     = <l_s_data>
    170
    IMPORTING
    171
    ex_container = l_string.
    172
    173
    PERFORM wrap_str_to_c255
    174
    USING    l_string
    175
    CHANGING e_t_outdata.
    176
    177
    ENDLOOP.
    178
    179
    ENDFORM.                    " data_wrap_std
    180
    181
    *&      Form  data_wrap_uc
    182
    183
          text
    184
    185
         -->P_I_T_DATA  text
    186
         <--P_E_OUTDATA_UC  text
    187
    188
    FORM data_wrap_uc
    189
    USING    i_t_data      TYPE STANDARD TABLE
    190
    i_compress    TYPE rs_bool
    191
    CHANGING e_outdata_uc  TYPE xstring.
    192
    193
    IF i_compress = rs_c_true.
    >>>>>
    EXPORT rsdri = i_t_data
    195
    TO DATA BUFFER e_outdata_uc
    196
    COMPRESSION ON.
    197
    ELSE.
    198
    EXPORT rsdri = i_t_data
    199
    TO DATA BUFFER e_outdata_uc
    200
    COMPRESSION OFF.
    201
    ENDIF.
    202
    203
    IF sy-subrc <> 0.
    204
       RAISE conversion_error.
    205
    ENDIF.
    206
    207
    ENDFORM.                    " data_wrap_uc
    208
    209
    210
    FORM data_wrap_250
    211
    212
    213
    Contents of system fields
    Name
    Val.
    SY-SUBRC
    0
    SY-INDEX
    1
    SY-TABIX
    0
    SY-DBCNT
    1
    SY-FDPOS
    25
    SY-LSIND
    0
    SY-PAGNO
    0
    SY-LINNO
    1
    SY-COLNO
    1
    SY-PFKEY
    SY-UCOMM
    SY-TITLE
    CPIC- und RFC-Steuerung
    SY-MSGTY
    E
    SY-MSGID
    BL
    SY-MSGNO
    209
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO
    0
    SY-DATUM
    20080411
    SY-UZEIT
    163555
    SY-XPROG
    SAPLRSDRI
    SY-XFORM
    RSDRI_INFOPROV_READ_RFC
    Active Calls/Events
    No.   Ty.          Program                             Include                             Line
    Name
    7 FORM         SAPLRSDRI_SERVICES                  LRSDRI_SERVICESF01                    194
    DATA_WRAP_UC
    6 FUNCTION     SAPLRSDRI_SERVICES                  LRSDRI_SERVICESU04                     29
    RSDRI_DATA_WRAP
    5 FORM         GP49E5DYREKDNLT28VWMJJ5FAZY         GP49E5DYREKDNLT28VWMJJ5FAZY           199
    INFOPROV_READ_RSDRI
    4 FUNCTION     SAPLRSDRI                           LRSDRIU02                             153
    RSDRI_INFOPROV_READ_RFC
    3 FORM         SAPLRSDRI                           LRSDRIU02                               1
    RSDRI_INFOPROV_READ_RFC
    2 FORM         SAPMSSY1                            SAPMSSY1                               85
    REMOTE_FUNCTION_CALL
    1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
    %_RFC_START
    Chosen variables
    Name
    Val.
    No.       7 Ty.          FORM
    Name  DATA_WRAP_UC
    SYST-REPID
    SAPLRSDRI_SERVICES
    5454554545545544452222222222222222222222
    310C23429F352693530000000000000000000000
    I_COMPRESS
    X
    5
    8
    RS_C_TRUE
    X
    5
    8
    SY
    ###############################################################################À##############
    0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
    0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
    I_T_DATA
    Table IT_4214[3004988x1456]
    PROGRAM=GP49E5DYREKDNLT28VWMJJ5FAZYFORM=INFOPROV_READ_RSDRIDATA=L_T_DATA
    Table reference: 245
    TABH+  0(20) = C0000005B3A98DB0000000000000000000000000
    TABH+ 20(20) = 000000F500001076002DDA3C000005B0FFFFFFFF
    TABH+ 40(16) = 0400002A00000B10000824C401800000
    store        = 0xC0000005B3A98DB0
    ext1         = 0x0000000000000000
    shmId        = 0     (0x00000000)
    id           = 245   (0x000000F5)
    label        = 4214  (0x00001076)
    fill         = 3004988 (0x002DDA3C)
    leng         = 1456  (0x000005B0)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000040
    occu         = 8     (0x00000008)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 8     (cmpManyEq)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000009BB9B2090
    pgHook       = 0x600000008EAEC160
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 3503  (0x00000DAF)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 3014656 (0x002E0000)
    lineAlloc    = 3004992 (0x002DDA40)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = Not allocated
    collHook     = Not allocated
    ext2         = Not allocated
    >>>>> 2nd level extension part <<<<<
    tabhBack     = Not allocated
    delta_head   = Not allocated
    pb_func      = Not allocated
    pb_handle    = Not allocated
    %_DUMMY$$
    2222
    0000
    E_OUTDATA_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    SYST
    ###############################################################################À##############
    0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
    0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
    No.       6 Ty.          FUNCTION
    Name  RSDRI_DATA_WRAP
    I_COMPRESS
    X
    5
    8
    I_RESULT250
    2
    0
    I_T_DATA
    Table IT_4214[3004988x1456]
    I_UNICODE_RESULT
    X
    5
    8
    E_OUTDATA_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    E_T_OUTDATA
    Table[initial]
    E_T_OUTDATA250
    Table[initial]
    RS_C_FALSE
    2
    0
    SY-REPID
    SAPLRSDRI_SERVICES
    5454554545545544452222222222222222222222
    310C23429F352693530000000000000000000000
    No.       5 Ty.          FORM
    Name  INFOPROV_READ_RSDRI
    SY-SUBRC
    0
    0000
    0000
    SY-REPID
    GP49E5DYREKDNLT28VWMJJ5FAZY
    4533434554444453355444344552222222222222
    7049554925B4EC42867DAA561A90000000000000
    SY
    ###############################################################################À##############
    0000000000000000000000000000000000000000000000010000000000000000000000000000000C00000000000000
    0001000000000000000000000000000000000000000100090001000000010000000000000000002000000000000000
    %_DUMMY$$
    2222
    0000
    %_SPACE
    2
    0
    SYST-REPID
    GP49E5DYREKDNLT28VWMJJ5FAZY
    4533434554444453355444344552222222222222
    7049554925B4EC42867DAA561A90000000000000
    I_OUTU
    X
    5
    8
    RS_C_TRUE
    X
    5
    8
    L_T_DATA
    Table IT_4214[3004988x1456]
    E_RFCOUT_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    I_S_RFCMODE
    0.0.0.1.
    22222222222222222222222222222222222222220000
    00000000000000000000000000000000000000000000
    I_S_RFCMODE-RFC_RECEIVER
    222222222222222222222222222222
    000000000000000000000000000000
    E_EOD
    X
    5
    8
    I_S_RFCMODE-ID
    2222222222
    0000000000
    No.       4 Ty.          FUNCTION
    Name  RSDRI_INFOPROV_READ_RFC
    I_AUTHORITY_CHECK
    R
    5
    2
    I_CURRENCY_CONVERSION
    X
    5
    8
    I_DEBUG
    2
    0
    I_FILENAME
    222222222222222222222222222222222222222222222222222222222222
    000000000000000000000000000000000000000000000000000000000000
    I_INFOPROV
    B100_CB3E
    433354434222222222222222222222
    2100F3235000000000000000000000
    I_MAXROWS
    0
    0000
    0000
    I_READ_ODS_DELTA
    2
    0
    I_REFERENCE_DATE
    20080411
    33333333
    20080411
    I_RESULTTYPE
    U
    5
    5
    I_ROLLUP_ONLY
    X
    5
    8
    I_SAVE_IN_FILE
    2
    0
    I_SAVE_IN_TABLE
    2
    0
    I_S_RFCMODE
    0.0.0.1.
    22222222222222222222222222222222222222220000
    00000000000000000000000000000000000000000000
    I_TABLENAME
    222222222222222222222222222222
    000000000000000000000000000000
    I_USE_AGGREGATES
    X
    5
    8
    I_USE_DB_AGGREGATION
    X
    5
    8
    E_AGGREGATE
    B100_CB3E$X
    433354434252222222222222222222
    2100F3235480000000000000000000
    E_END_OF_DATA
    X
    5
    8
    E_RFCDATA_UC
    ÿ#######1100####ÒWÜ#####°ï6=³$Ç~ßsæ#ä5L#¼ -^##há#°#!&ß3#ð#ô#Á#p6##Òâ¬###Å#.À#6²aÀ#kÀ6´1ÀOp##ú#
    F000008033330000D5D01190BE33B2C7D7E8E348BA25816E8B822D30F8F1C07321DEA019C12C93B6C86C3B3C4700F0
    F61122001100000027C52FD20F6D347EF36545C1C0DE008100016F3B064D13063B22C59855E056210BB06410F019A0
    E_SPLIT_OCCURRED
    2
    0
    E_T_FIELD[]
    Table IT_4[180x40]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_FIELD
    Table reference: 4
    TABH+  0(20) = C0000005B3902040C0000005B38D281000000000
    TABH+ 20(20) = 0000000400000004000000B400000028FFFFFFFF
    TABH+ 40(16) = 0400000100000F700010249401800000
    store        = 0xC0000005B3902040
    ext1         = 0xC0000005B38D2810
    shmId        = 0     (0x00000000)
    id           = 4     (0x00000004)
    label        = 4     (0x00000004)
    fill         = 180   (0x000000B4)
    leng         = 40    (0x00000028)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000060
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000005B39020A0
    pgHook       = 0xC0000005B38FC770
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 16    (0x00000010)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 304   (0x00000130)
    lineAlloc    = 304   (0x00000130)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D27A0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2740
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    E_T_RFCDATA[]
    Table IT_5[0x256]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_RFCDATA
    Table reference: 5
    TABH+  0(20) = 0000000000000000C0000005B38D292000000000
    TABH+ 20(20) = 00000005000000050000000000000100FFFFFFFF
    TABH+ 40(16) = 0400000100000E580010249401800000
    store        = 0x0000000000000000
    ext1         = 0xC0000005B38D2920
    shmId        = 0     (0x00000000)
    id           = 5     (0x00000005)
    label        = 5     (0x00000005)
    fill         = 0     (0x00000000)
    leng         = 256   (0x00000100)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000055
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D28B0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2850
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    E_T_RFCDATAV[]
    Table IT_6[0x100]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_E_T_RFCDATAV
    Table reference: 6
    TABH+  0(20) = 0000000000000000C0000005B38D2A3000000000
    TABH+ 20(20) = 00000006000000060000000000000064FFFFFFFF
    TABH+ 40(16) = 0400000100000F000010249401800000
    store        = 0x0000000000000000
    ext1         = 0xC0000005B38D2A30
    shmId        = 0     (0x00000000)
    id           = 6     (0x00000006)
    label        = 6     (0x00000006)
    fill         = 0     (0x00000000)
    leng         = 100   (0x00000064)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000058
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D29C0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2960
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_RANGE[]
    Table IT_0[24x153]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_RANGE
    Table reference: 0
    TABH+  0(20) = C0000005B38C97E0C0000005B38C97A000000000
    TABH+ 20(20) = 00000000000000000000001800000099FFFFFFFF
    TABH+ 40(16) = 04000001000004B80010249421800000
    store        = 0xC0000005B38C97E0
    ext1         = 0xC0000005B38C97A0
    shmId        = 0     (0x00000000)
    id           = 0     (0x00000000)
    label        = 0     (0x00000000)
    fill         = 24    (0x00000018)
    leng         = 153   (0x00000099)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000011
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 1
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000005B38C9840
    pgHook       = 0xC0000005B38CA1F0
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 2     (0x00000002)
    refCount     = 1     (0x00000001)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 48    (0x00000030)
    lineAlloc    = 48    (0x00000030)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 3     (0x00000003)
    >>>>> 1st level extension part <<<<<
    regHook      = 0xC0000005B3AB3F70
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38C9730
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38C96D0
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_REQUID[]
    Table IT_7[0x12]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_REQUID
    Table reference: 7
    TABH+  0(20) = 0000000000000000C0000005B38D2B4000000000
    TABH+ 20(20) = 0000000700000007000000000000000CFFFFFFFF
    TABH+ 40(16) = 04000001000006780010249401800000
    store        = 0x0000000000000000
    ext1         = 0xC0000005B38D2B40
    shmId        = 0     (0x00000000)
    id           = 7     (0x00000007)
    label        = 7     (0x00000007)
    fill         = 0     (0x00000000)
    leng         = 12    (0x0000000C)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000019
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = Not allocated
    pghook       = Not allocated
    idxPtr       = Not allocated
    shmTabhSet   = Not allocated
    id           = Not allocated
    refCount     = Not allocated
    tstRefCount  = Not allocated
    lineAdmin    = Not allocated
    lineAlloc    = Not allocated
    shmVersId    = Not allocated
    shmRefCount  = Not allocated
    shmIsReadOnly = Not allocated
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38D2AD0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38D2A70
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_RTIME[]
    Table IT_1[3x121]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_RTIME
    Table reference: 1
    TABH+  0(20) = C0000005B38CB680C0000005B38CB64000000000
    TABH+ 20(20) = 00000001000000010000000300000079FFFFFFFF
    TABH+ 40(16) = 04000001000005980010249401800000
    store        = 0xC0000005B38CB680
    ext1         = 0xC0000005B38CB640
    shmId        = 0     (0x00000000)
    id           = 1     (0x00000001)
    label        = 1     (0x00000001)
    fill         = 3     (0x00000003)
    leng         = 121   (0x00000079)
    loop         = -1    (0xFFFFFFFF)
    xtyp         = TYPE#000015
    occu         = 16    (0x00000010)
    access       = 1     (ItAccessStandard)
    idxKind      = 0     (ItIndexNone)
    uniKind      = 2     (ItUniqueNon)
    keyKind      = 1     (default)
    cmpMode      = 2     (cmpSingleMcmpR)
    occu0        = 1
    groupCntl    = 0
    rfc          = 0
    unShareable  = 0
    mightBeShared = 0
    sharedWithShmTab = 0
    isShmLockId  = 0
    gcKind       = 0
    isUsed       = 1
    isCtfyAble   = 1
    >>>>> Shareable Table Header Data <<<<<
    tabi         = 0xC0000005B38CB6E0
    pgHook       = 0x0000000000000000
    idxPtr       = 0x0000000000000000
    shmTabhSet   = 0x0000000000000000
    id           = 3     (0x00000003)
    refCount     = 0     (0x00000000)
    tstRefCount  = 0     (0x00000000)
    lineAdmin    = 16    (0x00000010)
    lineAlloc    = 16    (0x00000010)
    shmVersId    = 0     (0x00000000)
    shmRefCount  = 1     (0x00000001)
    >>>>> 1st level extension part <<<<<
    regHook      = 0x0000000000000000
    collHook     = 0x0000000000000000
    ext2         = 0xC0000005B38CB5D0
    >>>>> 2nd level extension part <<<<<
    tabhBack     = 0xC0000005B38CB570
    delta_head   = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
    pb_func      = 0x0000000000000000
    pb_handle    = 0x0000000000000000
    I_T_SFC[]
    Table IT_2[17x52]
    FUNCTION-POOL=RSDRIFORM=RSDRI_INFOPROV_READ_RFCDATA=%_%_I_T_SFC
    Table reference: 2
    TABH+  0(20) = C0000005B38CBFA0C0000005B38CBF6000000000
    TABH+ 20(20) = 00000002000000020000001100000034FFFFFFFF
    TABH+ 40(16) = 0400000100000DB00010249401800000
    store        = 0xC0000005B38CBFA0
    ext1         = 0xC0000005B38CBF60
    shmId        = 0     (0x00000000)
    i

    Hello,
    did you resolve the problem ?
    Please tell me how if it's resolved.
    Best Regards

  • Exists some problem with auto-relationship?

    Hi all,
    I'm getting the following exception when I make deploy.
    [14/May/2003:12:23:28] FINE ( 3132): Field: atributos
    [14/May/2003:12:23:28] FINE ( 3132): Field: coluna br.com.inttegra.infra.bean.tabela.ColunaTabelaLocal
    [14/May/2003:12:23:28] FINE ( 3132): -Methods: getColuna setColuna
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.tabela.ColunaTabelaEJB_849864039_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.tabela.ColunaTabelaEJB_849864039_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): manySide: false
    [14/May/2003:12:23:28] FINE ( 3132): Field: thisRelationshipFieldWasGeneratedByTheNameMapper67
    [14/May/2003:12:23:28] FINE ( 3132): Field: classe br.com.inttegra.infra.bean.classes.ClassesLocal
    [14/May/2003:12:23:28] FINE ( 3132): -Methods: getClasse setClasse
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.classes.ClassesEJB_413640801_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.classes.ClassesEJB_413640801_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): manySide: false
    [14/May/2003:12:23:28] FINE ( 3132): Field: thisRelationshipFieldWasGeneratedByTheNameMapper71
    [14/May/2003:12:23:28] FINE ( 3132): Finder: ejbFindByPrimaryKey
    [14/May/2003:12:23:28] FINE ( 3132): Finder: ejbFindAll
    [14/May/2003:12:23:28] FINER ( 3132): EJBQLC compile query
    Bean: ParseAtributo
    Method: java.util.Collection findAll()
    EJBQL: select object(pa) from ParseAtributoEJB pa
    [14/May/2003:12:23:28] FINER ( 3132): EJBQLC start syntax analysis
    [14/May/2003:12:23:28] FINEST ( 3132): EJBQLC dump tree (AST)
    QUERY [61, (0/0), null]
    from [5, (1/19), null]
    RANGE [62, (0/0), null]
    ParseAtributoEJB [46, (1/24), null]
    pa [46, (1/41), null]
    select [4, (1/1), null]
    object [8, (1/8), null]
    pa [46, (1/15), null]
    WHERE [6, (0/0), null]
    TRUE [10, (0/0), null]
    [14/May/2003:12:23:28] FINER ( 3132): EJBQLC start semantic analysis
    [14/May/2003:12:23:28] FINEST ( 3132): EJBQLC dump tree (typed AST)
    QUERY [61, (0/0), null]
    from [5, (1/19), null]
    RANGE [62, (0/0), null]
    ParseAtributoEJB [68, (1/24), ParseAtributo]
    pa [67, (1/41), ParseAtributo]
    select [4, (1/1), null]
    object [8, (1/8), ParseAtributo]
    pa [66, (1/15), ParseAtributo]
    WHERE [6, (0/0), null]
    TRUE [10, (0/0), boolean]
    [14/May/2003:12:23:28] FINER ( 3132): EJBQLC start code generation
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.parse.ParseAtributoEJB789766943_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.parse.ParseAtributoEJB789766943_JDOState
    [14/May/2003:12:23:28] FINER ( 3132): EJBQLC result JDOQLElements(candidateClass: br.com.inttegra.infra.bean.parse.ParseAtributoEJB789766943_JDOState, filter: true, result: this, resultType: br.com.inttegra.infra.bean.parse.ParseAtributoEJB789766943_JDOState, isPCResult: true)
    [14/May/2003:12:23:28] FINE ( 3132): Selectors: 0
    [14/May/2003:12:23:28] FINE ( 3132): CreateMethod: br.com.inttegra.infra.bean.parse.ParseAtributoEJBcreate
    [14/May/2003:12:23:28] FINE ( 3132): ejbCreateMethod: ejbCreate
    [14/May/2003:12:23:28] FINE ( 3132): ejbPostCreateMethod: ejbPostCreate
    [14/May/2003:12:23:28] FINE ( 3132): Processing method: unsetEntityContext
    [14/May/2003:12:23:28] FINE ( 3132): Known method: null
    [14/May/2003:12:23:28] FINE ( 3132): Found method: public void br.com.inttegra.infra.bean.parse.ParseAtributoEJB.unsetEntityContext()
    [14/May/2003:12:23:28] FINE ( 3132): Processing method: ejbRemove
    [14/May/2003:12:23:28] FINE ( 3132): Known method: null
    [14/May/2003:12:23:28] FINE ( 3132): Found method: public void br.com.inttegra.infra.bean.parse.ParseAtributoEJB.ejbRemove() throws javax.ejb.RemoveException,javax.ejb.EJBException
    [14/May/2003:12:23:28] FINE ( 3132): Processing method: beforeCompletion
    [14/May/2003:12:23:28] FINE ( 3132): Known method: null
    [14/May/2003:12:23:28] FINE ( 3132): Processing method: ejbLoad
    [14/May/2003:12:23:28] FINE ( 3132): Known method: null
    [14/May/2003:12:23:28] FINE ( 3132): Found method: public void br.com.inttegra.infra.bean.parse.ParseAtributoEJB.ejbLoad() throws javax.ejb.EJBException,java.rmi.RemoteException
    [14/May/2003:12:23:28] FINE ( 3132): Processing method: ejbStore
    [14/May/2003:12:23:28] FINE ( 3132): Known method: null
    [14/May/2003:12:23:28] FINE ( 3132): Found method: public void br.com.inttegra.infra.bean.parse.ParseAtributoEJB.ejbStore() throws javax.ejb.EJBException,java.rmi.RemoteException
    [14/May/2003:12:23:28] FINE ( 3132): Processing method: jdoCleanAllRefs
    [14/May/2003:12:23:28] FINE ( 3132): Known method: null
    [14/May/2003:12:23:28] FINE ( 3132): Processing method: setEntityContext
    [14/May/2003:12:23:28] FINE ( 3132): Known method: null
    [14/May/2003:12:23:28] FINE ( 3132): Found method: public void br.com.inttegra.infra.bean.parse.ParseAtributoEJB.setEntityContext(javax.ejb.EntityContext)
    [14/May/2003:12:23:28] FINE ( 3132): pkfield: idParseAtributo
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.parse.ParseAtributoEJB789766943_JDOState
    [14/May/2003:12:23:28] FINEST ( 3132): TP PCClassGen: generating 'br/com/inttegra/infra/bean/parse/ParseAtributoEJB789766943_JDOState'...
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.parse.ParseEJB_1482881505_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.tabela.ColunaTabelaEJB_849864039_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.classes.ClassesEJB_413640801_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.parse.ParseEJB_1482881505_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.tabela.ColunaTabelaEJB_849864039_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.classes.ClassesEJB_413640801_JDOState
    [14/May/2003:12:23:28] FINEST ( 3132): TP PCClassGen: DONE generating 'br/com/inttegra/infra/bean/parse/ParseAtributoEJB789766943_JDOState'...
    [14/May/2003:12:23:28] FINE ( 3132): gen file in /u03/dds/dds/var/opt/SUNWappserver7/domains/domainCronos/ServerNC/generated/ejb/j2ee-modules/NC
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.identificacao.IdentificacaoEJB_1068400097_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): ##### PCImplClass Name is br.com.inttegra.infra.bean.resposta.RespostaEJB670563865_JDOState
    [14/May/2003:12:23:28] FINE ( 3132): listCmrs identificacoes parse resposta
    [14/May/2003:12:23:28] FINE ( 3132): persistentClass br.com.inttegra.infra.bean.identificacao.IdentificacaoEJB
    [14/May/2003:12:23:28] SEVERE ( 3132): JDOCodeGenerator: Caught Exception in generating CMP:
    javax.ejb.EJBException: CMRFieldInfo not found for field identificacaoPai
    at com.sun.enterprise.deployment.PersistenceDescriptor.getCMRFieldInfoByName(PersistenceDescriptor.java:262)
    at com.iplanet.ias.persistence.internal.model.ejb.util.NameMapper.getRelatedEjbDescriptor(NameMapper.java:368)
    at com.iplanet.ias.persistence.internal.model.ejb.util.NameMapper.getEjbNameForLocalInterface(NameMapper.java:297)
    at com.sun.jdo.spi.persistence.support.ejb.model.util.NameMapper.getPersistenceClassForLocalInterface(NameMapper.java:284)
    at com.sun.jdo.spi.persistence.support.ejb.model.DeploymentDescriptorModel.getFieldType(DeploymentDescriptorModel.java:503)
    at com.sun.jdo.api.persistence.model.util.ModelValidator.shouldBeRelationship(ModelValidator.java:2377)
    at com.sun.jdo.api.persistence.model.util.ModelValidator.isLegalRelationship(ModelValidator.java:2384)
    at com.sun.jdo.api.persistence.model.util.ModelValidator.getFieldsValidationList(ModelValidator.java:325)
    at com.sun.jdo.api.persistence.model.util.ModelValidator.getBasicValidationList(ModelValidator.java:167)
    at com.sun.jdo.api.persistence.model.util.ModelValidator.getFullValidationList(ModelValidator.java:183)
    at com.sun.jdo.api.persistence.model.util.ModelValidator.fullValidationCheck(ModelValidator.java:131)
    at com.sun.jdo.api.persistence.model.Model.validate(Model.java:1592)
    at com.iplanet.ias.persistence.internal.ejb.ejbc.JDOCodeGenerator.validate(JDOCodeGenerator.java:189)
    at com.iplanet.ias.persistence.internal.ejb.ejbc.JDOCodeGenerator.generate(JDOCodeGenerator.java:225)
    at com.iplanet.ias.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:155)
    at com.iplanet.ias.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1029)
    at com.iplanet.ias.deployment.backend.EJBCompiler.preDeployModule(EJBCompiler.java:464)
    at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:181)
    at com.iplanet.ias.deployment.backend.EjbModuleDeployer.runEJBC(EjbModuleDeployer.java:246)
    at com.iplanet.ias.deployment.backend.EjbModuleDeployer.deploy(EjbModuleDeployer.java:128)
    at com.iplanet.ias.deployment.backend.ModuleDeployer.doRequest(ModuleDeployer.java:77)
    at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployEJBJarModuleArchiveOrDirectory(ManagedServerInstance.java:890)
    at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployEJBJarModule(ManagedServerInstance.java:841)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
    at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
    at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.callInvoke(AdminAPIEntryServlet.java:217)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.callMBean(AdminAPIEntryServlet.java:176)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.doGet(AdminAPIEntryServlet.java:101)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.doPost(AdminAPIEntryServlet.java:83)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
    at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
    at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
    at org.apache.catalina.core.S
    [14/May/2003:12:23:28] WARNING ( 3132): DPL5035:Error while running ejbc
    com.iplanet.ias.deployment.backend.IASDeploymentException: Fatal Error from EJB Compiler -- -- Error while processing CMP beans.
    at com.iplanet.ias.deployment.backend.EJBCompiler.wrapException(EJBCompiler.java:589)
    at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:186)
    at com.iplanet.ias.deployment.backend.EjbModuleDeployer.runEJBC(EjbModuleDeployer.java:246)
    at com.iplanet.ias.deployment.backend.EjbModuleDeployer.deploy(EjbModuleDeployer.java:128)
    at com.iplanet.ias.deployment.backend.ModuleDeployer.doRequest(ModuleDeployer.java:77)
    at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployEJBJarModuleArchiveOrDirectory(ManagedServerInstance.java:890)
    at com.iplanet.ias.admin.server.core.mbean.config.ManagedServerInstance.deployEJBJarModule(ManagedServerInstance.java:841)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.iplanet.ias.admin.server.core.jmx.Introspector.invokeMethodOn(Introspector.java:188)
    at com.iplanet.ias.admin.server.core.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:137)
    at com.iplanet.ias.admin.server.core.jmx.ASMBeanServerImpl.invoke(ASMBeanServerImpl.java:222)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.callInvoke(AdminAPIEntryServlet.java:217)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.callMBean(AdminAPIEntryServlet.java:176)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.doGet(AdminAPIEntryServlet.java:101)
    at com.iplanet.ias.admin.server.core.servlet.AdminAPIEntryServlet.doPost(AdminAPIEntryServlet.java:83)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
    at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
    at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
    at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
    at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
    at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:157)
    at com.iplanet.ias.web.WebContainer.service(WebContainer.java:598)
    Caused by: com.iplanet.ias.ejb.codegen.CmpCompilerException: Error while processing CMP beans.
    at com.iplanet.ias.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:198)
    at com.iplanet.ias.ejb.codegen.IASEJBC.ejbc(IASEJBC.java:1029)
    at com.iplanet.ias.deployment.backend.EJBCompiler.preDeployModule(EJBCompiler.java:464)
    at com.iplanet.ias.deployment.backend.EJBCompiler.compile(EJBCompiler.java:181)
    ... 30 more
    Caused by: javax.ejb.EJBException: CMRFieldInfo not found for field identificacaoPai
    at com.iplanet.ias.persistence.internal.ejb.ejbc.JDOCodeGenerator.generate(JDOCodeGenerator.java:264)
    at com.iplanet.ias.ejb.codegen.CmpCompiler.compile(CmpCompiler.java:155)
    ... 33 more
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: get connection
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: create connection
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: opening socket to [192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: server suggested 127.0.0.1:62189
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: using 192.168.200.9:0
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: create call context
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: outbound call: [endpoint:[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5](remote),objID:[0:0:0, 2]] : sun.rmi.transport.DGCImpl_Stub[0:0:0, 2]: java.rmi.dgc.Lease dirty(java.rmi.server.ObjID[], long, java.rmi.dgc.Lease)
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: write remote call header...
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: getting output stream
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: execute call
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: getting input stream
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: name = "java.rmi.dgc.Lease", codebase = ""
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: class "java.rmi.dgc.Lease" found via codebase, defined by null
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: name = "java.rmi.dgc.VMID", codebase = ""
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: class "java.rmi.dgc.VMID" found via codebase, defined by null
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: name = "[B", codebase = "" 
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: class "[B" found via codebase, defined by null 
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: name = "java.rmi.server.UID", codebase = ""
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: (thread context class loader: sun.misc.Launcher$AppClassLoader@a56a7c)
    [14/May/2003:12:23:33] FINER ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: class "java.rmi.server.UID" found via codebase, defined by null
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: free connection (reuse = true)
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: reuse connection
    [14/May/2003:12:23:33] FINE ( 3132): RMI RenewClean-[192.168.200.9:40873,com.iplanet.ias.admin.server.core.channel.LocalRMIClientSocketFactory@6fdca5]: create reaper
    my ejb-jar:
              <ejb-relation>
                   <ejb-relation-name>Identificacao-Identificacoes</ejb-relation-name>
                   <ejb-relationship-role>
                        <ejb-relationship-role-name>Identificacao-has-identificacoes</ejb-relationship-role-name>
                        <multiplicity>One</multiplicity>
                        <relationship-role-source>
                             <ejb-name>Identificacao</ejb-name>
                        </relationship-role-source>
                        <cmr-field>
                             <cmr-field-name>identificacoes</cmr-field-name>
                             <cmr-field-type>java.util.Collection</cmr-field-type>
                        </cmr-field>
                   </ejb-relationship-role>
                   <ejb-relationship-role>
                        <ejb-relationship-role-name>identificacoes-owned-by-Identificacao</ejb-relationship-role-name>
                        <multiplicity>Many</multiplicity>
                        <relationship-role-source>
                             <ejb-name>Identificacao</ejb-name>
                        </relationship-role-source>
                        <cmr-field>
                             <cmr-field-name>identificacaoPai</cmr-field-name>
                        </cmr-field>
                   </ejb-relationship-role>
              </ejb-relation>
    my sun-cmp-mappgins
                   <cmr-field-mapping>
                        <cmr-field-name>resposta</cmr-field-name>
                        <column-pair>
                             <column-name>IDENTIFICACAO.ID_RESPOSTA</column-name>
                             <column-name>RESPOSTA.ID_RESPOSTA</column-name>
                        </column-pair>
                   </cmr-field-mapping>
                   <cmr-field-mapping>
                        <cmr-field-name>identificacaoPai</cmr-field-name>
                        <column-pair>
                             <column-name>IDENTIFICACAO.ID_IDENTIFICACAO_PAI</column-name>
                             <column-name>IDENTIFICACAO.ID_IDENTIFICACAO</column-name>
                        </column-pair>
                   </cmr-field-mapping>
                   <cmr-field-mapping>
                        <cmr-field-name>identificacoes</cmr-field-name>
                        <column-pair>
                             <column-name>IDENTIFICACAO.ID_IDENTIFICACAO</column-name>
                             <column-name>IDENTIFICACAO.ID_IDENTIFICACAO_PAI</column-name>
                        </column-pair>
                   </cmr-field-mapping>
                   <cmr-field-mapping>
                        <cmr-field-name>parse</cmr-field-name>
                        <column-pair>
                             <column-name>IDENTIFICACAO.ID_PARSE</column-name>
                             <column-name>PARSE.ID_PARSE</column-name>
                        </column-pair>
                   </cmr-field-mapping>
    somebody already got this exception?

    This question is identical to the thread=19208 and 19209.
    Please do not duplicate the threads.
    Regards,
    Marina

  • How to delete a Contact Relationship in BADI

    Hi,
    I have a requirement where I need to delete Contact Person's relationship -  BUR001 with the Account he is associated with. This should be done in a BADI implementation when the user changes the status of the Contact Person and clicks on SAVE on WebUI.
    Initially I tried to delete the Contact Person relationship using the FM: BAPI_BUPR_RELATIONSHIP_DELETE which actually resulted in a DUMP error on WebUI in runtime because that FM was trying to interrupt a COMMIT. So I tried to find few MAINTAIN FMs which can solve this issue , as COMMIT anyways happens later internally.
    I found this FM: BUB_BUPA_RELATION_MODIFY which takes BUT050 structure and the action as input. Below is the Code snippet of the FM i used:
    CALL FUNCTION 'BUB_BUPA_RELATION_MODIFY'
       EXPORTING
                 is_but050 = ls_but050
                 iv_aktyp   = '06'.            " 06 means delete action
    Now the Contact has been successfully saved but the Contact Relationship is not deleted.
    Please let me know if anyone has got a solution for this.
    Thanks,
    San

    Any idea on this query?

  • CL_RSPLS_CR_CONTROLLER method inner join short dump

    Hi guys,
    i have characteristic relationship usage but i created a new concept for characteristic combinations creation. We have one table with all characteristics are maintained We want to use one single table to maintain all relations. The class created with the create method implemented is working and we do have the right entries in table c_th_chas. This table then goes into standard coding and is transformed. Afterwards  method complete_combis is executed and within this method there is the method INNER_JOIN_steps. There method INNER_JOIN is executed. And this is thge method which dumps because method INNER_JOIN has a part beggining with the comment intersection of characteristics is empty, so build the cart.product.. From 13 characetristics in the table 6 are filled and 7 are empty . Maybe 8 times i am able to to run the loop but then the values of the tables is increasing immensly and a short time is thrown with no more internal table space... --> no more memory.
    The problem seems to be the empty characetristics and the building of the cart. product. The command
      INSERTc_s_chas INTO TABLE e_th_chas.
    is to much for over 10 Mio records and a short dump is thrown.
    Is there any workaround for this problem? Can someone give me a hint.
    Thanks and regards,
    Murat

    Hi Gregor,
    thank you for your very helpful answer. With ticking this flag no automatic combinations were created and the wished characetristic relations were displayed. But after ticking this flag other workbooks crashed of invalid combinations which worked fine before witout the characteristic relationship class activation. The issue is as following:
    i have a lot of characteristics in the realtime planning cube. My intention was to make one big table with most of the characteristics in it to build characteristic relations. At the moment we do have some tables and maintaining them gets komplex. One table i for all is the target.We have workbooks where we dont want use characteristic relations so we have a characetristic embedded in constant selections (structure) in the query and other characteristics with Access Type for Result Values in Master Data and Filter Value Selection Durinbg Query Execution with Values in Master data Table. For these workbooks i dont want characteristic relationships but we also have the opposite queries with characetreistics with ACCESS Type for Result Values with CHARACTERISTIC RELATIONSHIP and Filter value Selection During Query execution with CHARACTERISTIC RELATIONSHIP. In these workbooks i want to use characetristic relationships and the table in the others not. Now  the wueries where i want to use CRRs are correct but at the other workbooks also the table and CRR class is executed but i dont want them to get restricted by CRRS and also there is no characetristic using ACCESS Type for Result Values with CHARACTERISTIC RELATIONSHIP and also Filter value Selection During Query execution with CHARACTERISTIC Relationdships.
    But despite why is CRR class executed. How can i solve it?
    I would appreciate if you or someone  could suggest me something here.
    Thanks and kind regards,
    Murat

  • Middleware: Changed partner function in R/3, appends relationship in CRM

    Hi Group
    Partner functions in R/3 are mapped as relationship categories in CRM and the transfer is happening through middleware.
    However if I change the BP for an existing partner function in R/3, it is not changing the BP in corresponding relationship in CRM.Instead it is adding a new relationship category.
    Ex.
    - An account in R/3 has a partner function "Sold to Party" as  BP Id "1234". This does create a relationship category in CRM "has sold to party" with BP Id 124.    -- Works fine. No issues.-
    - Later if I "change" the BP id 1234 to a new BP Id "5678" in R/3 for Sold to Party partner function, it does not update the relationship category in CRM. Instead it adds a new relationship category for "Sold to Party" with BP Id 5678.   ISSUE.
    We dont want to create a new relationship, instead we would like to update the relationship for new BP Id.
    If anyone has any any clue how to resolve this, please share your thoughts. It is a very critical requirement.
    Answer will be suitably rewarded with points.
    Thanks & Regards
    Vishal Mani

    Hi Michael,
    Thanks for asking . This Dinesh ( Vishal's colleague ) ..We found that the Dumps are because of the implmentation of the SAP Note 497146 which provides a enhancement to the existing FM BUPA_MWX_BDOC_MAP_REL_CENTRAL . This is throwing the short dump.
    We raised a OSS message and SAP replied back saying the behivour of the sytsem is as per standard and its not a bug .
    Can you please us to achive the following !!
    We want to avoid the replication of BP relationship ( sold to party to Z Custom A/c group  ) which does not have a Sales area ? Do  you know a BADI which can help us to achive this functionility ??
    I mean we want a control of the BP releationship replication via Middleware using BADI  .. Can you please help us here . Also please provide any list of BADIs which can help us on this ?
    Please get back at the earliiest , as we have a Go-live tommorow .
    Thanks and Regards
    Dinesh

  • Interactive Report- short dump

    Hi Experts,
    I have developed two tables and joined them through foreign key relationship.( activated and entered  data)
    and i wrote code for interactive report.
    On executing code, I am getting data for basic list but if i click for secondary list, it's going to dump.
    but if i use same code on changing tables and fields, it's working properly.
    what is the solution for this?
    Edited by: kalandar on Dec 4, 2009 8:13 AM

    hi,
    can we get the code to see where the problem cud be.....
    thanks,
    Sid

Maybe you are looking for