Business Content Activation - run time error

Hi guys,
We were at plugin 2002.1. We installed PI 2002.2 and PI 2003.1 on top of it.
After the plug-in upgrade, we are at support pack 9 for SAP-BW and 13 for BI-Content. For aba and basis, we are at 620 and support pack 32.
As part of the regression testing after the 2003.1 plugin upgrade, we found out that the business content activation abends with the following run time error.
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
Looks like it is trying to insert into table RSOLTPSOURCEFIET and the row already is existing. I thought the activation process is supposed to update something if it is already out there.
If we just select the 'only necessary', the activation goes through ok, but if we select 'before and after in the data flow', we get this abend.
Any clues???
Best regards,
makaleem

Hi Seow,
This is how I resolved it. I looked at the ST22 closely and one of the messages indicated that the number range is missing in tran SNRO for an infoObject. I created an entry for that infoobject using SNRO and tried activation and it worked.
When we created an OSS for SAP to look into it, they recommended the following two things. I tried these two but it did not work. I am mentioning them below just in case they may help you.
1) Sometimes there is inconsistency in the content cache when trying to activate objects and we have to delete the repository cache. To delete the repository cache, go to RSA1 ---> Business Content -
> Extras ---> Delete Rep Cache
2) Execute SAP_DROP_TMPTABLES program for types 1,2,3 and 6.
If this helps, don't forget to assign points.
Abdul

Similar Messages

  • Run time error while activating the Transfer Rules

    Hi,
    Error when activating Transfer rules for Infosource :
    0FI_GL_1 -
    (General ledger: Transaction figures)
    Run time error : ASSERTION FAILED
    Transfer rules traffic light is in Green. But when i am trying to activate the Transfer rules, its giving Run time error.
    Thanks,
    Kishore

    Hi,
    As mentioned in the note 939383 , either Import Support Package 08 for SAP NetWeaver 2004s BI (BI Patch08 or SAPKW70008) into your BI system or do correction instructions given in the note.
    It is always better to import the latest patches avialble in service market to avoid this type of problems.
    Also see tha note 1010672 amd check whether it is applicable to your problem.
    With rgds,
    Anil Kumar Sharma .P
    Message was edited by:
            Anil Kumar Sharma

  • Run-time error '429':Active X component can not create an object

    Hi Folks,
    I am using some VBA code to run logic in BPC for Excel. When i try to click on VBA button, It's giving the below error.However when i am trying to execute same from server it is working fine. Accessing from BPC client only we are facing this problem.
    Code have no issues. Is there any specific thing need to mentioned in client when we use VBA programming? Basically we used the VBA program to create the id's in BPC for Excel. So that it will automatically created on fly. Testing was fine interms of working in Server.
    " Run-time error '429':Active X component can not create an object ."

    Hi,
    Are you trying to add a member into the dimension from excel? As you said that this has been already tested in the server and is working fine, I believe, you have taken care of everything.
    Now, coming to the point, when you are adding a member in the membersheet, you need to process the dimension. This requires the admin rights. So, please check the task profile of the user ID, with which you are trying from your system. This user ID should be the primary admin.
    Hope this helps.
    Additionally, can you please elaborate on the steps on what you followed for adding a member from the excel directly?

  • Run time error '429' Active X component can't create object

    Hi,
    After installation of BI+, when i am trying to start the Financial reporting studio, I am the error'429' " run time error Active X component can't create object.
    I thought of stoping and stating the BI+ Core Services it is not allowing me to do that,
    Could you please help me in the installation BI+
    thanks,
    sudhakar

    Hi Johan,
    BI core services up and running, but still it is giving " cannot connect to GSM server server name"
    all the configaration went with green, Could please let me know other oprions or where I can find the error.
    Please let us know possible mistakes, I will try that options,
    thanks a lot John
    thanks,
    sudhakar

  • Run time error '429' Active X Componenet can't create object

    Hi,
    We are getting this error "Run time error '429' Active X Componenet can't create object" when we open the Input templates.
    No drop down of the Dimension members is  appearing.
    Please help.
    Reagrds,
    Anita

    Hi Anita,
    Please try imeplenting SAP Note: 1508168. Hope this helps.
    Rgds,
    Poonam

  • Run time error

    Dear All,
    During the transaction /n/sapapo/ccr (Reconsilation of transaction data) in client SCP 950, system displays the run time error which are attached herewith.
    This is the activity a used to execute regularly (Daily) and first time i recieved this message - -
    Runtime Errors         ASSERTION_FAILED                                                            
    Date and Time          13.07.2007 10:13:37                                                         
    ShrtText                                                                               
    The ASSERT condition has been violated.                                                       
    What happened?                                                                               
    In the current application program, the system recognized a situation                         
        involving the ASSERT statement that should not occur. A runtime error                         
        occurred, either because there was no activation ID entered or because                        
        the ID of the activation mode used was set to "Cancel.                                        
    What can you do?                                                                               
    Print out the error message (using the "Print" function)                                      
        and make a note of the actions and input that 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.                                                                               
    is especially useful if you want to keep a particular message.                                                                               
    Error analysis                                                                               
    The following activation ID was used: "No checkpoint group specified"                                                                               
    If the FIELDS addition was used with this ASSERT statement, the content                       
        of the first 8 fields is as follows:                                                          
        " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    " (not used) "                                                                               
    How to correct the error                                                                               
    Probably the only way to eliminate the error is to correct the program.                                                                               
    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:                                                                               
    "ASSERTION_FAILED" C                                                                               
    "/SAPAPO/SAPLTIMESTAMP" or "/SAPAPO/LTIMESTAMPU08"                                            
        "/SAPAPO/TIMESTAMP_DIFFERENCE"                                                                
        If you cannot solve the problem yourself and you wish to send                                 
        an error message to SAP, include the following documents:                                                                               
    1. A printout of the problem description (short dump)                                         
           To obtain this, select in the current display "System->List->                              
           Save->Local File (unconverted)".                                                                               
    2. A suitable printout of the system log                                                      
           To obtain this, call the system log through transaction SM21.                              
           Limit the time interval to 10 minutes before and 5 minutes                                 
           after the short dump. In the display, then select the function                             
           "System->List->Save->Local File (unconverted)".                                                                               
    3. If the programs are your own programs or modified SAP programs,                            
           supply the source code.                                                                    
           To do this, select the Editor function "Further Utilities->                                
           Upload/Download->Download".                                                                               
    4. Details regarding the conditions under which the error occurred                            
           or which actions and input led to the error.                                               
    System environment                                                                               
    SAP Release.............. "640"                                                                               
    Application server....... "scmprd"                                                            
        Network address.......... "172.16.10.47"                                                      
        Operating system......... "AIX"                                                               
        Release.................. "5.3"                                                               
        Hardware type............ "0002BFAAD700"                                                      
        Character length......... 16 Bits                                                             
        Pointer length........... 64 Bits                                                             
        Work process number...... 0                                                                   
        Short dump setting....... "full"                                                                               
    Database server.......... "scmprd"                                                            
        Database type............ "ORACLE"                                                            
        Database name............ "SCP"                                                               
        Database owner........... "SAPSCP"                                                                               
    Character set............ "C"                                                                               
    SAP kernel............... "640"                                                               
        Created on............... "Jan 18 2006 20:47:39"                                              
        Created in............... "AIX 1 5 00538A4A4C00"                                              
        Database version......... "OCI_920 "                                                                               
    Patch level.............. "109"                                                               
        Patch text............... " "                                                                               
    Supported environment....                                                                     
        Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE                        
         10.2.0.."                                                                               
    SAP database version..... "640"                                                               
        Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"                                                                               
    Memory usage.............                                                                     
        Roll..................... 16192                                                               
        EM....................... 196923232                                                           
        Heap..................... 0                                                                   
        Page..................... 98304                                                               
        MM Used.................. 186636840                                                           
        MM Free.................. 1895288                                                             
        SAP Release.............. "640"                                                                               
    User and Transaction                                                                               
    Client.............. 950                                                                      
        User................ "SCMATP"                                                                 
        Language key........ "E"                                                                      
        Transaction......... "/SAPAPO/CCR "                                                           
        Program............. "/SAPAPO/SAPLTIMESTAMP"                                                  
        Screen.............. "SAPMSSY0 1000"                                                          
        Screen line......... 6                                                                        
    Information on where terminated                                                                   
        The termination occurred in the ABAP program "/SAPAPO/SAPLTIMESTAMP" in                       
         "/SAPAPO/TIMESTAMP_DIFFERENCE".                                                              
        The main program was "/SAPAPO/CIF_DELTAREPORT3 ".                                                                               
    The termination occurred in line 61 of the source code of the (Include)                       
         program "/SAPAPO/LTIMESTAMPU08"                                                              
        of the source code of program "/SAPAPO/LTIMESTAMPU08" (when calling the editor                
         610).                                                                               
    Source Code Extract                                                                               
    Line  SourceCde                                                                               
    31     lv_time_int_low      TYPE i,                                                            
       32     lv_timediff_int      TYPE i,                                                            
       33     lv_datediff_int      TYPE i,                                                            
       34     lv_time              TYPE t,                                                            
       35     ls_time              TYPE tstr_timestr.                                                 
       36                                                                               
    37 * check timestamp parameter                                                                 
       38 * ASSERT NOT iv_timestamp_high IS INITIAL.                                                  
       39 * ASSERT NOT iv_timestamp_low  IS INITIAL.                                                  
       40 * ASSERT iv_timestamp_low <= iv_timestamp_high.                                             
       41   IF iv_timestamp_high IS INITIAL                                                           
       42   OR iv_timestamp_low  IS INITIAL.                                                          
       43     RAISE invalid_parameter.                                                                
       44   ENDIF.                                                                               
    45   IF iv_timestamp_high < iv_timestamp_low.                                                  
       46     RAISE invalid_parameter.                                                                
       47   ENDIF.                                                                               
    48                                                                               
    49 * prepare timestamps                                                                        
       50 * .. split into date and time integers                                                      
       51   ls_timestamp_high = iv_timestamp_high.                                                    
       52   lv_date_int_high  = ls_timestamp_high-date.                                               
       53   lv_time_int_high  = ls_timestamp_high-time.                                               
       54   ls_timestamp_low  = iv_timestamp_low.                                                     
       55   lv_date_int_low   = ls_timestamp_low-date.                                                
       56   lv_time_int_low   = ls_timestamp_low-time.                                                
       57                                                                               
    58 * .. calc date diff                                                                         
       59 * .. check against max. allowed integer difference                                          
       60   lv_datediff_int = lv_date_int_high - lv_date_int_low.                                     
    >>>>>   ASSERT lv_datediff_int <= lc_datediff_intmax.                                             
       62                                                                               
    63 * calc time diff                                                                               
    64   lv_timediff_int = lv_time_int_high - lv_time_int_low.                                     
       65   IF lv_timediff_int < 0.                                                                   
       66     ADD 86400 TO lv_timediff_int.                                                           
       67     SUBTRACT 1 FROM lv_datediff_int.                                                        
       68   ENDIF.                                                                               
    69                                                                               
    70 * calc total duration                                                                       
       71   lv_duration_int = lv_datediff_int * 86400 + lv_timediff_int.                              
       72   lv_time = lv_timediff_int.                                                                
       73   ls_time = lv_time.                                                                        
       74   ls_duration-hours   = lv_duration_int DIV 3600.                                           
       75   ls_duration-minutes = ls_time-minute.                                                     
       76   ls_duration-seconds = ls_time-second.                                                     
       77                                                                               
    78   ev_duration_packed  = ls_duration.                                                        
       79   ev_duration_integer = lv_duration_int.                                                    
       80 ENDFUNCTION.                                                                               
    Contents of system fields                                                                         
    Name     Val.                                                                               
    SY-SUBRC 0                                                                               
    SY-INDEX 0                                                                               
    SY-TABIX 1                                                                               
    SY-DBCNT 1                                                                               
    SY-FDPOS 6                                                                               
    SY-LSIND 0                                                                               
    SY-PAGNO 0                                                                               
    SY-LINNO 1                                                                               
    SY-COLNO 1                                                                               
    SY-PFKEY                                                                               
    SY-UCOMM                                                                               
    SY-TITLE CIF - Comparison/Reconciliation of Transaction Data                                      
    SY-MSGTY                                                                               
    SY-MSGID                                                                               
    SY-MSGNO 000                                                                               
    SY-MSGV1                                                                               
    SY-MSGV2                                                                               
    SY-MSGV3                                                                               
    SY-MSGV4                                                                               
    Active Calls/Events                                                                               
    No.   Ty.          Program                             Include                             Line   
          Name                                                                               
    5 FUNCTION     /SAPAPO/SAPLTIMESTAMP               /SAPAPO/LTIMESTAMPU08                  61  
          /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
        4 FORM         /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3F17                349  
          COMPARE_ORDER_HEADER                                                                        
        3 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U03                125  
          /SAPAPO/CIF_DELTA3_COMP_ORDER                                                               
        2 FUNCTION     /SAPAPO/SAPLCIF_DELTA3              /SAPAPO/LCIF_DELTA3U01                871  
          /SAPAPO/CIF_DELTA3_COMP                                                                     
        1 EVENT        /SAPAPO/CIF_DELTAREPORT3            /SAPAPO/CIF_DELTAREPORT3              189  
          START-OF-SELECTION                                                                          
    Chosen variables                                                                               
    Name                                                                               
    Val.                                                                               
    No.       5 Ty.          FUNCTION                                                                 
    Name  /SAPAPO/TIMESTAMP_DIFFERENCE                                                                
    IV_TIMESTAMP_HIGH                                                                               
    #q1###                                                                               
    02073899                                                                               
    2001125C                                                                               
    IV_TIMESTAMP_LOW                                                                               
    ##q!####                                                                               
    00720899                                                                               
    2011125C                                                                               
    EV_DURATION_INTEGER                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    EV_DURATION_PACKED                                                                               
    000000                                                                               
    00000C                                                                               
    SYST-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_SPACE                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    LS_TIMESTAMP_HIGH                                                                               
    22000713182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    22000713182959                                                                               
    LV_DATE_INT_HIGH                                                                               
    803363                                                                               
    0042                                                                               
    0C23                                                                               
    LS_TIMESTAMP_HIGH-DATE                                                                               
    22000713                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    22000713                                                                               
    LV_TIME_INT_HIGH                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_HIGH-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    LS_TIMESTAMP_LOW                                                                               
    20071210182959                                                                               
    00000000000000                                                                               
    00000000000000                                                                               
    33333333333333                                                                               
    20071210182959                                                                               
    LV_DATE_INT_LOW                                                                               
    733021                                                                               
    0025                                                                               
    0BFD                                                                               
    LS_TIMESTAMP_LOW-DATE                                                                               
    20071210                                                                               
    00000000                                                                               
    00000000                                                                               
    33333333                                                                               
    20071210                                                                               
    LV_TIME_INT_LOW                                                                               
    66599                                                                               
    0002                                                                               
    0147                                                                               
    LS_TIMESTAMP_LOW-TIME                                                                               
    182959                                                                               
    000000                                                                               
    000000                                                                               
    333333                                                                               
    182959                                                                               
    SY-UNAME                                                                               
    SCMATP                                                                               
    000000000000                                                                               
    000000000000                                                                               
    544455222222                                                                               
    33D140000000                                                                               
    SCREEN-INPUT                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LV_DATEDIFF_INT                                                                               
    70342                                                                               
    001C                                                                               
    0126                                                                               
    LV_TIMEDIFF_INT                                                                               
    0                                                                               
    0000                                                                               
    0000                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    SY-REPID                                                                               
    /SAPAPO/SAPLTIMESTAMP                                                                         
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254545444554452222222222222222222                                                      
        F31010FF310C49D5341D00000000000000000000                                                      
    %_DUMMY$$                                                                               
    0000                                                                               
    0000                                                                               
    2222                                                                               
    0000                                                                               
    No.       4 Ty.          FORM                                                                     
    Name  COMPARE_ORDER_HEADER                                                                        
    SYST-REPID                                                                               
    /SAPAPO/SAPLCIF_DELTA3                                                                        
        0000000000000000000000000000000000000000                                                      
        0000000000000000000000000000000000000000                                                      
        2545454254544445444543222222222222222222                                                      
        F31010FF310C396F45C413000000000000000000                                                      
    GC_APPEND_MODE                                                                               
    3                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    3                                                                               
    LS_FIELDS_TO_COMPARE-DUEDATE                                                                      
        X                                                                               
    0                                                                               
    0                                                                               
    5                                                                               
    8                                                                               
    SYST                                                                               
    #######################################&#332;###############################################&#19800; C#&#1280;##
        0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
        000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000500
        0000000000000000000000000000000800000004000000000000000000000000000000000000010900000005240000
        0000010200000000000001060100010C0000000C0000000002000000000000000000000000000B000001000803000C
    LS_APO_ORDER-ORDTYPE                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    GC_PLANNED_ORDER                                                                               
    5                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    5                                                                               
    LS_R3_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_ORDER_STATUS_NO_CONF                                                                               
    1                                                                               
    0                                                                               
    0                                                                               
    3                                                                               
    1                                                                               
    LS_APO_ORDER-STATUSCNF                                                                               
    0                                                                               
    0                                                                               
    2                                                                               
    0                                                                               
    GC_PRED_OUT_DEL                                                                               
    A                                                                               
    0                                                                               
    0                                                                               
    4                                                                               
    1                                                                               
    GC_TND_DELETE                                                                               
    CN                                                                               
    00                                                                               
    00                                                                               
    44                                                                               
    3E                                                

    Dear Sajit,
    Go through the following OSS Notes:
    <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=901957&_NLANG=E">901957</a>, <a href="https://websmp110.sap-ag.de/form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1036880&_NLANG=E">1036880</a>, <a href="https://websmp110.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1067414&_NLANG=E">1067414</a>
    Regards,
    Naveen.

  • Run time error while create Vendor master via MK01

    Dear Experts,
    when i try to create vendor master by MK01.....system throws run time error as below:
    "The exception 'CX_BADI_MULTIPLY_IMPLEMENTED' was raised, but it was not caught
    anywhere along
    the call hierarchy.
    Since exceptions represent error situations and this error was not
    adequately responded to, the running ABAP program
    'CVI_MAP_TITLE=================CP' has to be
    terminated."
    My current system is ECC 6 along with DBM. Business partner configuration is activated in the current system. I am getting this error after BP configuration. Could you please help me to fix this issue?.......Is it due to configuration or a dump from abap program?
    Regards
    Vetrivelan

    Hii,
       please search sdn before posting the threads.
    check these  links, it may help u............
    Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
    Short Dump - CX_BADI_MULTIPLY_IMPLEMENTED - BADI Q1SR1
    CX_BADI_NOT_IMPLEMENTED
    thanks.

  • Run time error QA32 of QM

    We are geting following run time error when executeing QA32 t-code of QM , error as follows ,
    Error analysis
    After a specific time, the program is terminated to make the work area
    available to other users who may be waiting.
    This is to prevent a work area being blocked unnecessarily long by, for
    example:
    - Endless loops (DO, WHILE, ...),
    - Database accesses with a large result set
    - Database accesses without a suitable index (full table scan)
    The maximum runtime of a program is limited by the system profile
    parameter "rdisp/max_wprun_time". The current setting is 600 seconds. If this
    time limit is
    exceeded, the system attempts to cancel any running SQL statement or
    signals the ABAP processor to stop the running program. Then the system
    waits another 60 seconds maximum. If the program is then still active,
    the work process is restarted.
    How to correct the error
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".
    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
    Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
    (for example);
    - Database has unsuitable index: Check index generation.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    Runtime Errors TIME_OUT
    Date and Time 30.06.2009 10:17:31
    Short dump has not been completely stored (too big)
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "TIME_OUT" " "
    "SAPLBSVA" or "LBSVAU14"
    "STATUS_PRE_READ"
    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... "GALT"
    Network address...... "202.54.13.238"
    Operating system..... "Windows NT"
    Release.............. "5.2"
    Hardware type........ "2x Intel 80686"
    Character length.... 8 Bits
    Pointer length....... 32 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "GALT"
    Database type..... "ORACLE"
    Database name..... "PRD"
    Database user ID.. "SAPSR3"
    Char.set.... "English_United State"
    SAP kernel....... 700
    created (date)... "Oct 13 2006 00:08:41"
    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
    Database version. "OCI_10201_SHARE (10.2.0.1.0) "
    Patch level. 80
    Patch text.. " "
    Runtime Errors TIME_OUT
    Date and Time 30.06.2009 10:17:31
    Short dump has not been completely stored (too big)
    Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
    SAP database version. 700
    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
    Memory consumption
    Roll.... 8112
    EM...... 16724736
    Heap.... 0
    Page.... 450560
    MM Used. 6688784
    MM Free. 626280
    User and Transaction
    Client.............. 400
    User................ "MGMTSER"
    Language key........ "E"
    Transaction......... "QA11 "
    Program............. "SAPLBSVA"
    Screen.............. "SAPMQEVA 0200"
    Screen line......... 41
    Information on where terminated
    Termination occurred in the ABAP program "SAPLBSVA" - in "STATUS_PRE_READ".
    The main program was "SAPMQEVA ".
    In the source code you have the termination point in line 61
    of the (Include) program "LBSVAU14".
    Source Code Extract
    Line SourceCde
    31
    32 OBJNR_TAB[] = JSTO_PRE_TAB[].
    33
    34 * Merken: jeweils bisherige Anzahl Einträge im Puffer
    35 DESCRIBE TABLE JSTO_BUF LINES JSTO_BUF_LINES.
    36 DESCRIBE TABLE JEST_BUF LINES JEST_BUF_LINES.
    37 DESCRIBE TABLE OBJNR_TAB LINES OBJNR_TAB_LINES. "Note978655
    38 ADD 1 TO JSTO_BUF_LINES.
    39
    40 l_percentage = OBJNR_TAB_LINES * 100 / JSTO_BUF_LINES. "Note978655
    41 * Small number of object numbers to be read, insert records "Note978655
    42 * sequentially to avoid expensive SORT on JSTO_BUF,JEST_BUF "Note978655
    43 IF ( l_percentage <= 1 OR OBJNR_TAB_LINES < 20 ) AND "Note978655
    44 get_change_documents IS INITIAL. "Note978655
    45 LOOP AT objnr_tab. "Note978655
    46 SELECT * FROM JSTO CLIENT SPECIFIED "Note978655
    47 FOR ALL ENTRIES IN OBJNR_TAB "Note978655
    48 WHERE MANDT EQ CLIENT "Note978655
    49 AND OBJNR = OBJNR_TAB-OBJNR. "Note978655
    50 READ TABLE JSTO_BUF WITH KEY MANDT = JSTO-MANDT "Note978655
    51 OBJNR = JSTO-OBJNR "Note978655
    52 BINARY SEARCH. "Note978655
    53 IF SY-SUBRC <> 0. "Note978655
    Runtime Errors TIME_OUT
    Date and Time 30.06.2009 10:17:31
    Short dump has not been completely stored (too big)
    54 JSTO_BUF = JSTO. "Note978655
    55 CLEAR JSTO_BUF-MOD. "Note978655
    56 JSTO_BUF-STSMA_OLD = JSTO_BUF-STSMA. "Note978655
    57 INSERT JSTO_BUF INDEX SY-TABIX. "Note978655
    58 ENDIF. "Note978655
    59 ENDSELECT. "Note978655
    60 "Note978655
    >>>>> SELECT * FROM JEST CLIENT SPECIFIED "Note978655
    62 FOR ALL ENTRIES IN OBJNR_TAB "Note978655
    63 WHERE MANDT EQ CLIENT "Note978655
    64 AND OBJNR = OBJNR_TAB-OBJNR. "Note978655
    65 READ TABLE JEST_BUF WITH KEY MANDT = JEST-MANDT "Note978655
    66 OBJNR = JEST-OBJNR "Note978655
    67 STAT = JEST-STAT "Note978655
    68 BINARY SEARCH. "Note978655
    69 IF SY-SUBRC <> 0. "Note978655
    70 JEST_BUF = JEST. "Note978655
    71 CLEAR JEST_BUF-MOD. "Note978655
    72 JEST_BUF-INACT_OLD = JEST_BUF-INACT. "Note978655
    73 INSERT JEST_BUF INDEX SY-TABIX. "Note978655
    74 ENDIF. "Note978655
    75 ENDSELECT. "Note978655
    76 ENDLOOP. "Note978655
    77 CLEAR: JSTO_BUF,JEST_BUF. "Note978655
    78 EXIT. "Note978655
    79 ENDIF. "Note978655
    80
    Contents of system fields
    Name Val.
    SY-SUBRC0
    SY-INDEX0
    SY-TABIX15
    SY-DBCNT15
    SY-FDPOS1
    SY-LSIND0
    SY-PAGNO0
    SY-LINNO1
    SY-COLNO1
    SY-PFKEYA101
    SY-UCOMMBU
    SY-TITLE Record Usage Decision: Characteristic Overview
    SY-MSGTY
    SY-MSGID
    SY-MSGNO000
    SY-MSGV1
    SY-MSGV2
    SY-MSGV3
    SY-MSGV4
    SY-MODNO0
    SY-DATUM20090630
    SY-UZEIT101723
    SY-XPROGSAPLQAMB
    SY-XFORMCONVERSION_EXIT
    Edited by: Raghavendra Balegar on Jul 3, 2009 12:21 PM

    No Dear,
    Not at all. I think it should work for atleast one month period.
    But sometimes depending on the database size and hardware, this criteria can vary.
    Regds,
    Anil

  • Run time error during transcation execution in ECC 6.0

    Dear All,
    Working on ECC 6.0; Activated the Business Function, and  any transaction that is run, we face the Run time error as follows:
    Category : Internal Kernal Error
    Runtime Errors : DDIC_TYPE_INCONSISTENCY

    from OSS Note 1049251 - Activate Enterprise Extensions in the switch framework
    2. Prerequisite for activation
    Unable to deactivate
               Before you activate Enterprise Extensions, note it is not possible to deactivate these extensions. Furthermore, not every Enterprise Extension is compatible with every Industry Extension. If you have activated an industry solution (known as a "Business Function Set") in your system, refer to the notes on how to activate the industry to find out if there are any restrictions regarding specific Enterprise Extensions.

  • ABAP Run time error when display the Customs Export declarations

    Hi,
    I'm receiving ABAP Run time error when display the Customs Exp. Declarations Under SAP Customs Processing -> Customs Processing - Import / Export -> Monitoring.
    Error messaging point to Function Module - /SAPSLL/CUHD_LOAD_SELECTION.
    While debugging we found that Primary Key of the below structures are not the same
    lt_corpar                              type      /sapsll/corpar_t
    lt_corpar_ht       type      /sapsll/corpar_k02_ht
    Does anyone has the SAP Notes or solution to this issue other than changing the structures manually. I'm not sure about the impact if i change manually
    Error message short details
    Termination occurred in the ABAP program "/SAPSLL/SAPLCUHD_SELECTION" - in
         "/SAPSLL/CUHD_LOAD_SELECTION".
        The main program was "/SAPSLL/CULO_DISPLAY_CUS_EXP ".
        In the source code you have the termination point in line 144
        of the (Include) program "/SAPSLL/LCUHD_SELECTIONU01".
    We are on GTS Release 8.0 and Support Package SAPK-80014INSAPSLL (Support pack level 14).
    Regards,
    Pradeep Maddi

    Hi,
    I have implemented SAP Note 1531799, but it hasn't resolved the current issue.
    For Our GTS instance, there are 2 Feeder Systems (ECC) attached, but document transfer in one of the system has not been activated. Both having the same partner functions ( We copied the sandbox into 2 different instances for different business Testings and now these 2 instances attached to GTS for testing). These feeder systems have different Logical system names and Logical system groups.
    Recently i have implemented SAP Corrections manually for one the issue, Please see below thread for the detail information
    Proforma Invoice not transferred to GTS
    After implementing the corrections, i have created Pro-forma invoice in ECC system. When i tried to display, i'm facing the ABAP Dump issues.
    Error details
    Runtime Errors         ITAB_DUPLICATE_KEY
    ABAP Program           /SAPSLL/SAPLCUHD_SELECTION
    Application Component  SLL-LEG
    You tried to insert an entry into table  "\FUNCTION=/SAPSLL/CUHD_LOAD_SELECTION\DATA=LT_CORPAR_HT". However, updating the unique table key "PRIMARY_KEY" resulted in a duplicate entry. The key concerned may be either the primary key or a secondary key.
    Regards,
    Pradeep

  • Interface Mapping run time error...java.lang.nullpointerException  thrown

    Hi,
    I am trying to create a simple f2f scenairo and when I tested the configuration xi throws this message as :
    Interface Mapping run time error...java.lang.nullpointerException  thrown during application mapping.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:TimeSent>2007-01-09T03:43:49Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Service>CAMEL_BS_01</SAP:Service>
      <SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="" scheme="" />
      <SAP:Service>Camel_BService_01</SAP:Service>
      <SAP:Interface namespace="http://kia.com/fiel2file">Target01_MI</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>j5qiPBwVPU2yonkPwhdt/g==</SAP:ObjectId>
      <SAP:SWCV>tR26oJ7nEdu5oM/vCXwv+g==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="http://kia.com/fiel2file">Source01_MI</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_Equipment_MM_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_Equipment_MM_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2007-01-09T03:43:49Z" wasRead="false">
      <SAP:Engine type="AE">af.pi7.gbdci550</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2007-01-09T03:43:50Z" wasRead="false">
      <SAP:Engine type="IS">is.03.gbdci550</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>9E0AD300-9F93-11DB-8770-000D60514DD2</SAP:MessageId>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20070108</SAP:Date>
      <SAP:Time>224350</SAP:Time>
      <SAP:Host>gbdci550</SAP:Host>
      <SAP:SystemId>PI7</SAP:SystemId>
      <SAP:SystemNr>03</SAP:SystemNr>
      <SAP:OS>AIX</SAP:OS>
      <SAP:DB>DB6</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>014</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>PIAFUSER</SAP:User>
      <SAP:TraceLevel>1</SAP:TraceLevel>
      <SAP:LogSeqNbr>002</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId>
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService>
      <SAP:QIdInternal>XBTOW0__0001</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="200">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">097C2FFA403445A30F7600CE</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>168</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>2608</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>168</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>67</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Sender_Agreement_GUID>49574D50A74F3F5D902E20831759594C</SAP:Sender_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.025474</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.064329</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.067038</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.085552</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.085573</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.472198</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.473649</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.483159</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.483341</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.48668</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.486921</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.49182</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.491835</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="gbdci550">20070109034350.720028</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="gbdci550">20070109034350.721545</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</Trace>
      <Trace level="1" type="T">Party normalization: receiver</Trace>
      <Trace level="1" type="T">Receiver scheme external =</Trace>
      <Trace level="1" type="T">Receiver agency external =</Trace>
      <Trace level="1" type="T">Receiver party external =</Trace>
      <Trace level="1" type="T">Receiver party normalized =</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 9E0AD3009F9311DB8770000D60514DD2</Trace>
      <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0008</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0008</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      </Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">number of receivers: 1</Trace>
      <Trace level="1" type="T">Single-receiver split case</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOW0__0001</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Persisting single message for post-split handling</Trace>
      <Trace level="1" type="T" />
      <Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = PI7</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2007-01-09T03:43:50Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
      <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Interface Mapping http://kia.com/fiel2file Equipment_IM_Outbound</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_Equipment_MM_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_Equipment_MM_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:403) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code)) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:Equipment_MT/MaterialNumber. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java(Compiled Code)) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:398) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:141) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:102) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor291.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java(Compiled Code)) at $Proxy184.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java(Compiled Code)) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code)) at java.lang.reflect.Method.invoke(Method.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java(Compiled Code)) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.listen(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.work(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.loop(JCO.java(Compiled Code)) at com.sap.mw.jco.JCO$Server.run(JCO.java:8044) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java(Compiled Code)) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java(Compiled Code))</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
    - <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
    - <SAP:Payload xlink:href="cid:[email protected]">
      <SAP:Name>MainDocument</SAP:Name>
      <SAP:Description />
      <SAP:Type>Application</SAP:Type>
      </SAP:Payload>
      </SAP:Manifest>
      </SOAP:Body>
      </SOAP:Envelope>
    Please I request to give me some hint how to troubleshoot this issue.
    Thanks a lot,
    Srujan

    Hi, i have the same type of error when testing configuration, but it seems that the mapping even doesn't start :
    i'm creating an EBP to XCBL scenario, so it's a RFC->XI->XCBL 3.5
    Here is the Java exception
    Mappage d'interface
    Can someone be helpful for that ?
    Regards
    Laurent
    Message was edited by:
            Laurent Gitton

  • Run-Time error '-2147417848 (80010108) in Crystal Report on SAP BW Query

    I have installed Crystal Report 2008 SP1 and the Business Objects Integration kit for 3.1 but when I try to create a report on top of an SAP BW query using the toolbar, after entering the logon parameters for SAP BW, I get a error message :
    Run-Time error '-2147417848 (80010108)
    Automation error
    The object invoked has disconnected from its clients.
    CR exits after this error message.
    I have tried uninstalling the Kit and CR, cleaning up the registry, and installing it again and still got this error message - It is the same for all my SAP BWs.
    Anyone ever had this?
    Thank you,
    R.

    Is this still an issue?

  • Xml Publisher  run time error '5148'

    Dear
    I am using XML publisher to convert data in excel from the oracle,so first i have generated data in xml by report builder and open xml file in Word document through >template builder >data > load xml data,it's find but i use insert menu and select all field then it give message which i have mentioned below,
    run time error '5148'
    The number must be between 1 to 63
    I think, is it column limitation because i have done this activity later but right now i have added more column so may be that's why it is showing the error but my client need to show data in excel,so how i can fulfill this requirement,is there any other solution ?
    Please help on this regard. thanks in advance.

    Just for future poor souls who may be pulling their hair out over the same issue, I eventually got to the bottom of this cryptic error message.
    Do not try to import all your fields at once if your group has over 63 of them, as it will fail.
    If you use the Insert Table option, and try to put all the fields in at once, it will give you a more meaningful message, and the one it SHOULD have given you in the first place, which is "A table cannot contain more than 63 columns".
    So - Import them, a few at a time. Then move them all into one group and you're good to go.

  • Run-time error "PXA_NO_SHARED_MEMORY" occurred

    Hi All,
    My production system is running fine. And when i check SM21 I saw a lot of error message Run-time error "PXA_NO_SHARED_MEMORY" occurred and Run-time error "SYSTEM_NO_ROLL" occurred. However I can't see any error in ST22. I had read sap note 307976. And dont know when I restart the SAP services is it will be fine?
    trc file: "dev_w0", trc level: 1, release: "640"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, M

    B Mon Feb 22 08:13:29 2010
    B  create_con (con_name=R/3)
    B  Loading DB library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' ...
    B  Library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' loaded
    B  Version of 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll' is "640.00", patchlevel (0.58)
    B  New connection 0 created
    M sysno      00
    M sid        PRD
    M systemid   560 (PC with Windows NT)
    M relno      6400
    M patchlevel 0
    M patchno    58
    M intno      20020600
    M make:      multithreaded, ASCII
    M pid        2440
    M
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2440) [dpxxdisp.c   1160]
    I  MtxInit: -2 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpShMCreate: sizeof(wp_adm)          11592     (828)
    M  DpShMCreate: sizeof(tm_adm)          2219848     (11044)
    M  DpShMCreate: sizeof(wp_ca_adm)          18000     (60)
    M  DpShMCreate: sizeof(appc_ca_adm)     6000     (60)
    M  DpShMCreate: sizeof(comm_adm)          192000     (384)
    M  DpShMCreate: sizeof(vmc_adm)          0     (320)
    M  DpShMCreate: sizeof(wall_adm)          (22440/34344/56/100)
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 047D0040, size: 2510384)
    M  DpShMCreate: allocated sys_adm at 047D0040
    M  DpShMCreate: allocated wp_adm at 047D17A8
    M  DpShMCreate: allocated tm_adm_list at 047D44F0
    M  DpShMCreate: allocated tm_adm at 047D4518
    M  DpShMCreate: allocated wp_ca_adm at 049F2460
    M  DpShMCreate: allocated appc_ca_adm at 049F6AB0
    M  DpShMCreate: allocated comm_adm_list at 049F8220
    M  DpShMCreate: allocated comm_adm at 049F8238
    M  DpShMCreate: allocated vmc_adm_list at 04A27038
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 04A27060
    M  DpShMCreate: allocated wall_adm at 04A27068
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.

    M Mon Feb 22 08:13:30 2010
    M  calling db_connect ...
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'D:\usr\sap\PRD\SYS\exe\run\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      58
    C    patchcomment MSSQL: Workaround for SQL2005 change in RpcNexecInsert (814383)
    C  np:(local) connection used on PKG-PRD
    C  CopyLocalParameters: dbuser is 'prd'

    C Mon Feb 22 08:13:31 2010
    C  Provider SQLNCLI could not be initialized. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: MARS property was not set.
    C  Provider Release:08.50.1022
    C  Provider SQLNCLI could not be initialized. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: MARS property was not set.

    C Mon Feb 22 08:13:42 2010
    C  Cache sizes: header 52 bytes, 20000 names (26720000 bytes), 1000 dynamic statements (5432000 bytes), total 32152052 bytes
    C  Using shared procedure name cache PKG-PRD_PRDPRD_PRD_MEM initialized by another process.
    C  Connected to db server : [PKG-PRD] server_used : [np:(local)], dbname: PRD, dbuser: prd
    C  pn_id:PKG-PRD_PRDPRD_PRD
    C  Not using MARS (on sql 8.0)
    B  Connection 0 opened (DBSL handle 0)
    B  Wp  Hdl ConName          ConId     ConState     TX  PRM RCT TIM MAX OPT Date     Time   DBHost         
    B  000 000 R/3              000000000 ACTIVE       NO  YES NO  000 255 255 20100222 081330 PKG-PRD        
    C  The IRow interface is supported by this OLEDB provider
    M  db_connect o.k.

    I Mon Feb 22 08:14:02 2010
    I  MtxInit: 0 0 0
    M  SHM_PRES_BUF               (addr: 09E50040, size: 4400128)
    M  SHM_ROLL_AREA          (addr: 12510040, size: 262144000)
    M  SHM_PAGING_AREA          (addr: 617B0040, size: 113246208)
    M  SHM_ROLL_ADM               (addr: 0A290040, size: 2616690)
    M  SHM_PAGING_ADM          (addr: 0A510040, size: 525344)
    M  ThCreateNoBuffer          allocated 320144 bytes for 1000 entries at 0A5A0040
    M  ThCreateNoBuffer          index size: 3000 elems
    M  ThCreateVBAdm          allocated 7424 bytes (50 server) at 0A5F0040
    X  EmInit: MmSetImplementation( 2 ).
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    X  ES initialized.
    B  db_con_shm_ini:  WP_ID = 0, WP_CNT = 14
    B  dbtbxbuf: Buffer TABL  (addr: 103500C8, size: 30000128, end: 11FEC4C8)
    B  dbtbxbuf: Buffer TABLP (addr: 0E5200C8, size: 10240000, end: 0EEE40C8)
    B  dbexpbuf: Buffer EIBUF (addr: 0EF000D0, size: 4194304, end: 0F3000D0)
    B  dbexpbuf: Buffer ESM   (addr: 0F3100D0, size: 4194304, end: 0F7100D0)
    B  dbexpbuf: Buffer CUA   (addr: 0F7200D0, size: 3072000, end: 0FA0E0D0)
    B  dbexpbuf: Buffer OTR   (addr: 0FA100D0, size: 4194304, end: 0FE100D0)
    M  rdisp/reinitialize_code_page -> 0
    M  icm/accept_remote_trace_level -> 0
    M  rdisp/no_hooks_for_sqlbreak -> 0
    C  Provider SQLNCLI could not be initialized. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: MARS property was not set.
    S  *** init spool environment
    S  initialize debug system
    T  Stack direction is downwards.
    T  debug control: prepare exclude for printer trace
    T  new memory block 120D8040
    S  spool kernel/ddic check: Ok
    S  using table TSP02FX for frontend printing
    S  1 spool work process(es) found
    S  frontend print via spool service enabled
    S  printer list size is 150
    S  printer type list size is 50
    S  queue size (profile)   = 300
    S  hostspool list size = 3000
    S  option list size is 30
    S      found processing queue enabled
    S  found spool memory service RSPO-RCLOCKS at 121F0098
    S  doing lock recovery
    S  setting server cache root
    S  found spool memory service RSPO-SERVERCACHE at 121F03E0
    S    using messages for server info
    S  size of spec char cache entry: 165020 bytes (timeout 100 sec)
    S  size of open spool request entry: 1152 bytes
    S  immediate print option for implicitely closed spool requests is disabled

    A  -PXA--
    A  PXA INITIALIZATION
    A  PXA: Fragment Size too small: 107 MB, reducing # of fragments
    A  System page size: 4kb, admin_size: 13396kb.
    A  Attached to PXA (address 21F30040, size 440000K)
    A  abap/pxa = shared protect gen_remote
    A  PXA INITIALIZATION FINISHED
    A  -PXA--

    C  The IRow interface is supported by this OLEDB provider
    B  dbtran INFO (init_connection '<DEFAULT>' [MSSQL:640.00]):
    B   max_blocking_factor =  50,  max_in_blocking_factor      = 255,
    B   min_blocking_factor =   5,  min_in_blocking_factor      =  10,
    B   prefer_union_all    =   1,  prefer_union_for_select_all =   0,
    B   prefer_fix_blocking =   0,  prefer_in_itab_opt          =   0,
    B   convert AVG         =   1,  alias table FUPD            =   0,
    B   escape_as_literal   =   0,  opt GE LE to BETWEEN        =   0,
    B   select *            =0x00,  character encoding          =SBCS / []:X,
    B   use_hints           = abap->1, dbif->0x1, upto->0, rule_in->0,
    B                         rule_fae->0, concat_fae->0, concat_fae_or->0

    A Mon Feb 22 08:14:03 2010
    A  ABAP ShmAdm attached (addr=53EC5000 leng=20955136 end=552C1000)
    A  >> Shm MMADM area (addr=5422D180 leng=134720 end=5424DFC0)
    A  >> Shm MMDAT area (addr=5424F000 leng=17244160 end=552C1000)
    A  RFC Destination> destination pkg-prd_PRD_00 host pkg-prd system PRD systnr 0 (pkg-prd_PRD_00)
    A  RFC Options> H=pkg-prd,S=00
    A  RFC FRFC> fallback activ but this is not a central instance.
    A   
    A  RFC rfc/signon_error_log = -1
    A  RFC rfc/dump_connection_info = 0
    A  RFC rfc/dump_client_info = 0
    A  RFC rfc/cp_convert/ignore_error = 1
    A  RFC rfc/cp_convert/conversion_char = 23
    A  RFC rfc/wan_compress/threshold = 251
    A  RFC rfc/recorder_pcs not set, use defaule value: 1
    A  RFC rfc/delta_trc_level not set, use default value: 0
    A  RFC rfc/no_uuid_check not set, use default value: 0
    A  RFC abap/SIGCHILD_default not set, use default value: 0
    A  RFC Method> initialize RemObjDriver for ABAP Objects
    A  Hotpackage version: 49
    M  ThrCreateShObjects          allocated 14604 bytes at 0FFD0040

    N Mon Feb 22 08:14:05 2010
    N  SsfSapSecin: putenv(SECUDIR=D:\usr\sap\PRD\DVEBMGS00\sec): ok

    N  =================================================
    N  === SSF INITIALIZATION:
    N  ===...SSF Security Toolkit name SAPSECULIB .
    N  ===...SSF trace level is 0 .
    N  ===...SSF library is D:\usr\sap\PRD\SYS\exe\run\sapsecu.dll .
    N  ===...SSF hash algorithm is SHA1 .
    N  ===...SSF symmetric encryption algorithm is DES-CBC .
    N  ===...sucessfully completed.
    N  =================================================
    N  MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
    N  MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
    W  =================================================
    W  === ipl_Init() called
    W    ITSP Running against db release 620!
    W    ITSP Disable Kernel Web GUI functionality
    W  === ipl_Init() returns 2, ITSPE_DISABLED: Service is disabled (sapparam)
    W  =================================================

    E Mon Feb 22 08:14:39 2010
    E  Replication is disabled

    C Mon Feb 22 08:15:00 2010
    C  sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC CACHEPROFILE.
    C  Procname: [No proc]

    C Mon Feb 22 08:15:01 2010
    C  statement rerun with user dbo was successful, you can ignore the preceeding message

    C Mon Feb 22 08:16:27 2010
    C  Provider SQLNCLI could not be initialized. See note #734034 for more information.
    C  Using provider SQLOLEDB instead.
    C  OpenOledbConnection: MARS property was not set.

    S Mon Feb 22 08:19:23 2010
    S  found spool memory service RSPO-ACTIONS at 121F4C68

    A Mon Feb 22 08:19:55 2010
    A  TH VERBOSE LEVEL FULL
    M  ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   12304]
    C  Rollback Work (0)

    A Mon Feb 22 08:19:59 2010
    A  Mon Feb 22 08:19:59 2010

    A  ABAP/4 Program /SDF/SAPLRI_SQLSERVER                   .
    A  Source /SDF/LRI_SQLSERVERU02                    Line 264.
    A  Error Code CALL_FUNCTION_CONFLICT_LENG.
    A  Module  $Id: //bas/640_REL/src/krn/runt/abfunc.c#14 $ SAP.
    A  Function FuncParams Line 2906.
    C  Rollback Work (0)

    C Mon Feb 22 08:20:00 2010
    C  sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC loginfo.
    C  Procname: [No proc]

    C Mon Feb 22 08:20:01 2010
    C  statement rerun with user dbo was successful, you can ignore the preceeding message

    C Mon Feb 22 08:20:07 2010
    C  sloledb.cpp [ParamStmtExec,line 12251]: Error/Message: (err 50000, sev 0), Table not found.
    C  Procname: [##Y3PKG_PRDprd00000024400000003365081342]
    C  ParamStmtExec failed.  HR 80040e14 DBSL retcode 99. stmt: [sap_get_table_size_info 'syscomments', 'prd', 'PRD'
    C  /* R3:CL_SQL_RESULT_SET=============CP:234 T: */
    C  ]
    C  Conn_i:2 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 222194
    C  dbdsmss: DBSL99 SQL50000
    C  Table not found.
    B  ***LOG BY2=> sql error 50000      performing FET        [dbds#3 @ 592] [dbds    0592 ]
    B  ***LOG BY0=> Table not found. [dbds#3 @ 592] [dbds    0592 ]
    B  ***LOG BY1=> sql error 50000      [dbacds#2 @ 1187] [dbacds  1187 ]

    B Mon Feb 22 08:26:10 2010
    B  dbmyclu : info : my major identification is 3232261128, minor one 0.
    B  dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.
    B  dbmyclu : info : my uuid is 31B87DDDE43B904B955F2E6B45F604BE.
    B  dbmyclu : info : current optimistic cluster level: 3
    B  dbmyclu : info : pessimistic reads set to 2.
    N  login/password_change_for_SSO : 1 -> 1

    B Mon Feb 22 08:32:54 2010
    B  table logging switched off for all clients

    M Mon Feb 22 08:45:50 2010
    M  PfHIndInitialize: memory=<60720150>, header=<60720150>, records=<60720180>

    S Mon Feb 22 08:55:52 2010
    S  handle memory type is RSTSPROMMM

    M Mon Feb 22 09:18:08 2010
    M  *** ERROR => NiProcMsg: rc=-104 (NIEROUT_SNC_FAILURE) from router [nibuf.c      423]
    M  *** ERROR => MsIAttachEx: NiBufConnect to /H/192.168.100.7/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001/sapmsOSS failed (rc=NIEROUT_SNC_FAILURE) [msxxi.c      633]
    M  *** ERROR => LgIAttach: MsAttach (rc=NIEROUT_SNC_FAILURE) [lgxx.c       2984]
    M  *** ERROR => LgIGroup: LgIAttach(rc=-101) [lgxx.c       3504]
    A  TH VERBOSE LEVEL FULL

    M Mon Feb 22 09:18:28 2010
    M  *** ERROR => NiProcMsg: rc=-104 (NIEROUT_SNC_FAILURE) from router [nibuf.c      423]
    M  *** ERROR => MsIAttachEx: NiBufConnect to /H/192.168.100.7/S/sapdp99/H/194.39.131.34/S/sapdp99/H/oss001/sapmsOSS failed (rc=NIEROUT_SNC_FAILURE) [msxxi.c      633]
    M  *** ERROR => LgIAttach: MsAttach (rc=NIEROUT_SNC_FAILURE) [lgxx.c       2984]
    M  *** ERROR => LgIGroup: LgIAttach(rc=-101) [lgxx.c       3504]
    A  TH VERBOSE LEVEL FULL

    C Mon Feb 22 10:01:09 2010
    C  Rollback Work (0)

    A Mon Feb 22 10:18:24 2010
    A  TH VERBOSE LEVEL FULL
    M  ***LOG R68=> ThIRollBack, roll back () [thxxhead.c   12304]
    C  Rollback Work (0)

    A Mon Feb 22 10:18:26 2010
    A  Mon Feb 22 10:18:26 2010

    A  ABAP/4 Program /SDF/SAPLRI_SQLSERVER                   .
    A  Source /SDF/LRI_SQLSERVERU02                    Line 264.
    A  Error Code CALL_FUNCTION_CONFLICT_LENG.
    A  Module  $Id: //bas/640_REL/src/krn/runt/abfunc.c#14 $ SAP.
    A  Function FuncParams Line 2906.
    C  Rollback Work (0)
    C  sloledb.cpp [DoDbcc,line 2930]: Error/Message: (err 2571, sev 0), User 'prd' does not have permission to run DBCC loginfo.
    C  Procname: [No proc]
    C  statement rerun with user dbo was successful, you can ignore the preceeding message

    C Mon Feb 22 10:18:29 2010
    C  sloledb.cpp [ParamStmtExec,line 12251]: Error/Message: (err 50000, sev 0), Table not found.
    C  Procname: [##Y3PKG_PRDprd00000024400000012657081342]
    C  ParamStmtExec failed.  HR 80040e14 DBSL retcode 99. stmt: [sap_get_table_size_info 'syscomments', 'prd', 'PRD'
    C  /* R3:CL_SQL_RESULT_SET=============CP:234 T: */
    C  ]
    C  Conn_i:2 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 222194
    C  dbdsmss: DBSL99 SQL50000
    C  Table not found.
    B  ***LOG BY2=> sql error 50000      performing FET        [dbds#3 @ 592] [dbds    0592 ]
    B  ***LOG BY0=> Table not found. [dbds#3 @ 592] [dbds    0592 ]
    B  ***LOG BY1=> sql error 50000      [dbacds#2 @ 1187] [dbacds  1187 ]
    Could anybody advice me on this
    Regards,
    Zul

    Hi,
    I hope 440000 will not the cause,
    this might occur due to many reasons,
    1. make sure you have all the components(Applications,OSlevel,DBlevel) are at same level in entire the landscape.
    2. you can observe the evenlogs at OSlevel to get the error information pointing to. Also check for the dumps/logs(work direcotry).
    3. if not, can open SAP message.
    regards
    Nagaraju

  • Run time error while closing the CRM Order using BAPI

    Hi Experts,
    Need your invaluable suggestions here.Apologies for the lengthy mail, intention is to give clear idea of the issue.
    I am facing an issue while closing the CRM orders. According to our business process, when an issue is solved we will keep the order in resolved status only. We will not directly close the order from the CRM tool, instead we have created a custom program for the same purpose.
    For the custom program we will give input as the order number and execute it, this will close the order.
    Here close the order means assigning it to Close status as well assign the reason code.
    We have created some reason codes for closed status.
    So when the program is run the Order moves from resolved status to closed status along with reason code.
    But of late we are facing some problems with this program, it is giving run time error for some CRM orders.
    Run time error message : The ABAP/4 Open SQL array insert results in duplicate database records.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "CRM_SERVICE_OS_UPD_OST_DU" "(FUNCTION)", nor was it propagated by a RAISING clause.
    Please find my code which have used in the custom program
    Closing the resolved SOs in the system
        CALL FUNCTION 'CRM_STATUS_CHANGE_EXTERN_OW'
            EXPORTING
              objnr                     = iv_guid
              user_status          = lc_status_closed
           EXCEPTIONS
             object_not_found          = 1
             status_inconsistent       = 2
             status_not_allowed       = 3
             OTHERS                        = 4.
        IF sy-subrc <> 0.
          WRITE :  'Error at maintaining status'.
        ENDIF.
    Set reason code
    build lt_subject
        ls_subject-ref_guid = iv_guid.
        ls_subject-katalogart = 'A2'.
        ls_subject-codegruppe = 'ZR000003'.
        ls_subject-code       = 'ZR33'.                      " Reason code
        ls_subject-mode       = 'A'.
        APPEND ls_subject TO lt_subject.
    build lt_ossset
        ls_osset-ref_guid        = iv_guid.
        ls_osset-subject_profile = 'ZREASON03'.
        ls_osset-profile_type    = 'G'.
        ls_osset-subject         = lt_subject.
        APPEND ls_osset TO lt_osset.
    build lt_service_os
        ls_service_os-ref_guid  = iv_guid.
        ls_service_os-ref_kind  = 'A'.
        ls_service_os-osset     = lt_osset.
        APPEND ls_service_os TO lt_service_os.
    build lt_input_fields
        REFRESH: lt_input_fields, lt_field_names.
        CLEAR  : ls_input_fields, ls_field_names.
        ls_field_names-fieldname    = 'CODE'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'CODEGRUPPE'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'KATALOGART'.
        APPEND ls_field_names TO lt_field_names.
        ls_field_names-fieldname    = 'SERVICE_PROFILE'.
        APPEND ls_field_names TO lt_field_names.
        ls_input_fields-ref_guid    = iv_guid.
        ls_input_fields-ref_kind    = 'A'.
        ls_input_fields-objectname  = 'SERVICE_OS'.
        ls_input_fields-field_names = lt_field_names.
        APPEND ls_input_fields TO lt_input_fields.
         CALL FUNCTION 'CRM_ORDER_MAINTAIN'
          EXPORTING
            it_service_os     = lt_service_os
          CHANGING
            ct_input_fields   = lt_input_fields
          EXCEPTIONS
            error_occurred    = 1
            document_locked   = 2
            no_change_allowed = 3
            no_authority      = 4
            OTHERS            = 5.
        IF sy-subrc <> 0.
          WRITE :  'Error at maintaining reason'.
        ENDIF.
        CALL FUNCTION 'CRM_ORDER_SAVE'
          EXPORTING
            it_objects_to_save   = lt_header_guid
            iv_update_task_local = lv_update_task_local
          IMPORTING
            et_saved_objects     = lt_saved_objects
          EXCEPTIONS
            document_not_saved   = 1
            OTHERS               = 2.
        IF sy-subrc <> 0.
          WRITE : 'Error at saving'.
        ELSE.
          WRITE : 'Successfully Closed'.
          COMMIT WORK AND WAIT.
        ENDIF.
    Run time error is coming at COMMIT WORK AND WAIT statement.
    Please let me know any corrections are required in the above program.
    When I analyzed the run time error I have found that it trying to insert the record in CRMD_SRV_OSSET for that CRM order, but already one record is present in the table for the same CRM order number.
    For most of the CRM orders there is no entry in this table so they are closing successfully but for a few orders for which there is an entry we are getting the above run time error.
    There is nothing wrong with the orders which have an entry already in the table CRMD_SRV_OSSET, I need to close these kind of orders with out run time error.
    Kindly provide your feedback.

    Hi Dinakar,
    You posted this in APO PPDS forum. This question should go to PP forum where someone could answer it.
    Please close this thread and open a new thread in PP forum so that you could get help quickly from the relevant experts.
    Regards - Pawan

Maybe you are looking for