Dump while testing Idoc from WE19-OBJECTS_OBJREF_NOT_ASSIGNED

Hi Experts,
I am trying to Post inbound PO idoc from we19 tcode.
MessageType:PORDCR1
Idoctype:PORDCR102
FM:BAPI_IDOC_INPUT1
while testing this Idoc it is going dump.
Runtime Errors     :    OBJECTS_OBJREF_NOT_ASSIGNED
Short text            :    Access via 'NULL' object reference not possible.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "PROCESS_COMPONENTS" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "L_ITEM").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
Could you plz suggest how to resolve this issue.
regards,
Bhuvan.

Hi,
Please implement the OSS Note 1409498 (Relavent to your problem).
I am sure it will resolve your issue.
If not solving your than You can serch for relavent SAP note on SAP serivce market place.
Regards,
Lokesh.
Edited by: Lokesh Tarey on Apr 15, 2010 2:31 PM
Edited by: Lokesh Tarey on Apr 15, 2010 2:33 PM

Similar Messages

  • "An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

    Hi all,
    While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
    Only a particular Idoc type is having this issue.
    Below are the checks done before posting this query:
    1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
    2. Reloaded the meta data in PI for  the particular Idoc type in issue.
    3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
    4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
    5. Restarted the inboundRA service in PI AEX.
    Is there anything still missing. What could be root cause of this issue.
    If anyone has encountered it before, pleases share the resolution.
    Thank you
    Younus

    Hi Amit,
    Thanks for the reply. Log viewer doesn't provide much help on the error.
    The error desc says
    "JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
    regards,
    Younus

  • Regarding Short Dump While loading data from DB Connect

    Dear All,
    We are having an issue of getting short dump while loading data from DB Connect to BW. We were able to load the data into BW Dev using the same data source without any problem. Whereas in Production, I am getting the following error:
    Runtime Error          PERFORM_CONFLICT_TAB_TYPE  
    Except.                   CX_SY_DYN_CALL_ILLEGAL_TYPE
    What could be the reason for the error that I am getting

    hi,
    Refer Note 707986 - Writing in trans. InfoCubes: PERFORM_CONFLICT_TAB_TYPE
    Summary
    Symptom
    When data is written to a transactional InfoCube, the termination PERFORM_CONFLICT_TAB_TYPE occurs. The short dump lists the following reasons for the termination:
    ("X") The row types of the two tables are incompatible.
    ("X") The table keys of the two tables do not correspond.
    Other terms
    transactional InfoCube, SEM, BPS, BPS0, APO
    Reason and Prerequisites
    The error is caused by an intensified type check in the ABAP runtime environment.
    Solution
    Workaround for BW 3.0B (SP16-19), BW 3.1 (SP10-13)
    Apply the attached correction instructions.
    BW 3.0B
    Import Support Package 20 for 3.0B (BW3.0B Patch20 or SAPKW30B20) into your BW system. The Support Package is available oncenote 0647752 with the short text "SAPBWNews BW3.0B Support Package 20", which describes this Support Package in more detail, has been released for customers.
    BW 3.10 Content
    Import Support Package 14 for 3.10 (BW3. 10 Patch14 or SAPKW31014) into your BW system. The Support Package is available once note 0601051 with the short text "SAPBWNews BW 3.1 Content Support Package 14" has been released for customers.
    BW3.50
    Import Support Package 03 for 3.5 (BW3.50 Patch03 or SAPKW35003) into your BW system. The Support Package is available once note 0693363 with the short text "SAPBWNews BW 3.5 Support Package 03", which describes this Support Package in more detail, has been released for customers.
    The notes specified may already be available to provide advance information before the Support Package is released. However, in this case, the short text still contains the term "Preliminary version" in this case.
    Header Data
    Release Status: Released for Customer
    Released on: 18.02.2004 08:11:39
    Priority: Correction with medium priority
    Category: Program error
    Primary Component: BW-BEX-OT-DBIF Interface to Database
    Secondary Components: FIN-SEM-BPS Business Planning and Simulation
    Releases
    Software
    Component Release From
    Release To
    Release And
    subsequent
    SAP_BW 30 30B 30B
    SAP_BW 310 310 310
    SAP_BW 35 350 350
    Support Packages
    Support
    Packages Release Package
    Name
    SAP_BW_VIRTUAL_COMP 30B SAPK-30B20INVCBWTECH
    Related Notes
    693363 - SAPBWNews BW SP03 NW'04 Stack 03 RIN
    647752 - SAPBWNews BW 3.0B Support Package 20
    601051 - SAPBWNews BW 3.1 Content Support Package 14
    Corrections Instructions
    Correction
    Instruction Valid
    from Valid
    to Software
    Component Ref.
    Correction Last
    Modifcation
    301776 30B 350 SAP_BW J19K013852 18.02.2004 08:03:33
    Attributes
    Attribute Value
    weitere Komponenten 0000031199
    Thanks
    (Activate ODS/Cube and Transfer rules again..)

  • Getting error code 37 while sending IDOC via WE19

    Hello experts,
    I am facing a very unlikely error which is preventing me from testing my scenario.
    I dont have XI quality server and hence I am using my development server as both dev and quality. Hence I need to connect both dev and quality SAP R/3 system to my XI dev system. While I have done all the configurations in my XI and both SAP R/3 systems, its giving me error when i am trying to send IDOC from quality system.
    In quality R/3 i have done the following:
    1) Created RFC for my XI dev server
    2) Created port for this RFC
    3) Created partner profile adding all required IDOCS in the outbound parameters
    4) Created distribution channel for all the idocs
    In XI dev system i have done the following:
    1) Created RFC for both dev and quality of R/3
    2) Created port for both the RFCs
    3) Maintained the IDOC metadata for both the ports
    Now when I am pusing IDOC via dev of r/3 (we19) is working fine but when I am doing the same from quality of r/3 its giving me status code of idoc as 37 that says "An error was identified in the control record while adding an IDoc. The sender port SAPQTY_510 is invalid."
    But I have created this sender port SAPQTY_510 in my XI dev system and have also maintained the idoc metadata. I dont know why this error is coming.
    Can anyone please point out what mistake i have done or if i missed sometig as I am trying to connect 2 r/3 systems to one XI system.
    Its really urgent hence your help will be highly apreciated.
    Thanks,
    Yash

    hi yash,
    where you created SAPQTY_510 ,it should be created in R/3 Quality RFC destinations.
    In XI DEV create port like SAPxxx WHERE xxx is SID of quality system.
    actually we are getting confused.
    i guess you used same name SAPQTY_510 in quality R/3 and XI DEV .
    In error it says sender port SAPQTY_510  is invalid mean port of Source not XI DEV(receiver).
    just try to use some other name say SAPXXX_QUA and confirm the error.
    when IDOC is sent to XI DEV  ,port of  XIDEV  SAPQTY_510 has nothing to play any role .
    just check whether rfc destination of sender port (QUALITY R/3)you used is of type 3.
    so please check at which port error is coming.
    Thanks & Regards,
    Rama Krishna
    Edited by: rama krishna talluri on Mar 5, 2008 10:02 AM

  • Error while pushing idocs from SAP to XI

    Dear All,
    For doing ALE configurations for pushing IDOC's from SAP to XI, I am following the following blog posted on SDN:
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    I am able to create the  model view distribution successfully but when I am clicking on EDIT --> MODEL VIEW --> DISTRIBUTE (which is one of the steps mentioned in the blog), I am getting an error tht
    <b>Target system XIDEV       Communication error occurred
                                              User is locked. Please notify the person responsible</b>
    please tell me what is the error ie which user is locked and how should i proceed now.
    Waiting for your reply.
    Warm regards,
    N.Jain

    hi krishnamoorthy,
    i hve created one RFC in my R/3 system which is pointing to Xi-DEV. So, in the RFC I have used my XI user id & password for loging and the RFC is wrking fine when I am testing tht. I have used my id "XISUPER" in that RFC and it is not locked in XI-DEV. I have not used user id "XI_APPLUSER" anywhere.
    Please suggest.
    Warm Regards,
    N.Jain

  • Dump while downloading data from Application Server File in 4.6 system

    Hi,
    When we are trying to upload data from Application Server to internal table using dataset statements, it is resulting in a dump. System we are using is 4.6c.
    When we faced similar kind of issue in ECC version, we have used the statement, Ignoring Conversion Errors.
    Please let me know how to handle this situation in 4.6 System.
    Thanks for your inputs.
    Regards,
    Phani

    Hi All,
    I am sorry. My question was wrong. It should be while uploading data from internal table to application server, if there are any special characters, it is going to dump.
    I will let you know the dump details and code at the earliesst.
    Sorry and Thanks again for your prompt response.
    Regards,
    Phani.

  • ABAP Dump while using "Upload from clipboard"

    Hi,
    We are facing ABAP dump when using "upload from clipboard" funciton without any data on the clipboard.
    "Upload data" is working fine if some data exists on the clipboard. If in case of no data on the clipboard, it is leading to an ABAP dump.
    Appreciate if anyone could point some OSS note or any solution if you've already faced this issue.
    This is happening in our BW system with SAP_BASIS "SAPKB62018" and SAP_ABA "SAPKA62018".
    Same thing happens in our BW test systems which are upgraded to the latest support pack.
    Following is the error analysis
    Error analysis                                                                               
    A RAISE statement in the program "CL_GUI_FRONTEND_SERVICES======CP " raised the        
    exception                                                                             
    condition "CNTL_ERROR".                                                                
    Since the exception was not intercepted by a superior program                          
    in the hierarchy, processing was terminated.                                                                               
    Short description of exception condition:                                                                               
    For detailed documentation of the exception condition, use                             
    Transaction SE37 (Function Library). You can take the called                           
    function module from the display of active calls.                                      
    How to correct the error                                                                               
    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:                                                                               
    "RAISE_EXCEPTION" C                                                                    
    "CL_GUI_FRONTEND_SERVICES======CP " or "CL_GUI_FRONTEND_SERVICES======CM00T "          
    "CLIPBOARD_IMPORT"

    Hi,
    When you say 'We are facing ABAP dump when using "upload from clipboard" funciton without any data on the clipboard.', are you using this in a custom program and are you running your custom program in the background?
    From the error you mentioned, to me it looks like you had a control error and controls are for foreground, online process and not suitable for background processing. Same argument holds good for most of the enjoy SAP transactions when you try to do BDC, they will give you a similar error if you hit the piece of code where controls are used.
    Controls are created on the desktop of the user and in background this is not possible.
    Please let me know if this is the reason.
    Srinivas

  • Time Out Dump while extracting data from table CKIS

    Dear Friends,
    I am getting TIme Out dump for the below code, while extracting data from table CKIS.
    Table CKIS doesn't have any Indexes. Please guide me to resolve this.
    Regards,
    Viji.
    form get_keko_ckis.
      SELECT kalnr kalka kadky tvers bwvar matnr werks kokrs
             FROM keko
             INTO TABLE i_keko1
             FOR ALL ENTRIES IN i_final_modify
                 WHERE matnr = i_final_modify-main_f
                   AND werks = p_werks
                   AND kokrs = p_kokrs
                   AND kadat = p_kadat
                   AND bidat = p_bidat
                   AND bwdat = p_bwdat.
      IF sy-subrc = 0.
        SORT i_keko1 BY kalnr kalka kadky tvers bwvar.
        SELECT kalnr kalka kadky tvers bwvar posnr typps kstar
               matnr menge gpreis
               FROM ckis
               INTO TABLE i_ckis_temp
               FOR ALL ENTRIES IN i_keko1
               WHERE kalnr = i_keko1-kalnr
                 AND kalka = i_keko1-kalka
                 AND kadky = i_keko1-kadky
                 AND tvers = i_keko1-tvers
                 AND bwvar = i_keko1-bwvar.
            IF sy-subrc = 0.
              SORT i_ckis_temp BY kalnr kalka kadky tvers bwvar.
              LOOP AT i_ckis_temp INTO wa_ckis_temp.
                wa_ckis-kalnr  = wa_ckis_temp-kalnr.
                wa_ckis-kadky  = wa_ckis_temp-kadky.
                wa_ckis-posnr  = wa_ckis_temp-posnr.
                wa_ckis-typps  = wa_ckis_temp-typps.
                wa_ckis-kstar  = wa_ckis_temp-kstar.
                wa_ckis-matnr1 = wa_ckis_temp-matnr1.
                wa_ckis-menge  = wa_ckis_temp-menge.
                wa_ckis-gpreis = wa_ckis_temp-gpreis.
              CLEAR wa_keko1.
              READ TABLE i_keko1 INTO wa_keko1
                                 WITH KEY kalnr = wa_ckis_temp-kalnr
                                          kalka = wa_ckis_temp-kalka
                                          kadky = wa_ckis_temp-kadky
                                          tvers = wa_ckis_temp-tvers
                                          bwvar = wa_ckis_temp-bwvar
                                          BINARY SEARCH.
                 IF sy-subrc = 0.
                    wa_ckis-matnr = wa_keko1-matnr.
                    wa_ckis-werks = wa_keko1-werks.
                 ENDIF.
                 APPEND wa_ckis TO i_ckis.
                 CLEAR: wa_ckis_temp, wa_ckis.
              ENDLOOP.
            ENDIF.
        REFRESH: i_keko1, i_ckis_temp.
      ENDIF.
    endform.                    " get_keko_ckis

    Hi Try minimising the conditions in where clause
         SELECT fields..... FROM CKIS
         WHERE KALNR = KEKO-KALNR AND
                      KADKY = KEKO-KADKY AND
                      TVERS = KEKO-TVERS AND
                      TYPPS = 'M'.
        after this, deleting unwanted records from internal table as per pending conditions...
    Regds,
    Anil

  • Getting Error in SM58 and IDX2 while using IDOC from

    Dear All,
    Getting error when trying to send FIDCCP02 Idoc from ECC to PI system.
    "Basic Type 'FIDCCP02' is unknown"
    Getting the same error while trying to import metadata using IDX2 from PI side.
    All connections and distribution model are created.
    Please help
    Regards

    hey,
    I checked all config again but getting error while checking ocnsistency in BDM5 on ECC system(E1Q).
    It is failing when the messge type FIDCC1 reaches PI QA (X1Q) system and the error states
    Message type FIDCC1 is not defined
    Please check last line of below message:
    E1QCLNT001     Checks in own system E1QCLNT001          
         Message type     @08\QCheck OK@     Message type FIDCC1 is defined
         Segment filtering     @08\QCheck OK@     No segment filtering
         Conversions     @08\QCheck OK@     No conversion
         Partner profile     @08\QCheck OK@     Partner profile has been created
                                      @08\QCheck OK@     .....Port PI_QA
              @08\QCheck OK@     .....Port PI_QA
              @08\QCheck OK@     .....Packet size 0001
              @08\QCheck OK@     .....Basis type FIDCCP02
              @08\QCheck OK@     .....enhancement
         Port     @08\QCheck OK@     Port PI_QA : To PI Quality System
              @08\QCheck OK@     .....Port type: Transactional RFC
              @08\QCheck OK@     .....port version 3: IDoc record types from Version 4.0 onwards
              @08\QCheck OK@     .....Logical address (destination) X1QCLNT001
         Logical address (destination)     @08\QCheck OK@     Logical address (destination) X1QCLNT001 is defined
    X1QCLNT001     Checks in partner system X1QCLNT001          
         Check of own logical system     @08\QCheck OK@     Own logical system is X1QCLNT001
              @08\QCheck OK@     Logical system is the same as the target address
                       Message Type     *@0A\QCheck resulted in error@*     Message type FIDCC1 is not defined
    When I am clicking on error it is taking to WE81 on PI side.
    So do I need to add this message type in PI system as it is present in ECC side?
    Thanks
    Edited by: Chanakya Sharma on Dec 10, 2010 12:10 PM

  • How to configure, push and test Idoc from XI to R/3

    Assuming mapping between imported Idoc and some file structure is fine ,I have to configure XI and R/3 for pushing Idocs from Xi to r/3. I have to make sure they talk.
    -I have done this long time ago for pushing Idocs from R/3 to XI but I wonder if it is same procedure or it is different ?
    -Can someone tell me  - how to configure both for this purpose partner profiles , logical systems etc ?
    -And also after configurations , how I can check if Idocs is received from Xi and the entire process is successful?
    -does it make difference the type of Idocs during the configurations?
    -Are the test for success same for all type Idocs?
    Thanks all !
    Jon

    Here are the steps:
    ===========================
    First - Maintain the Sender R/3 System:
    SM59 : Create a RFC destination to XI
    WE21 : Create a TRFC Port ->Specify the RFC Destination Created
    BD54 : Create a Logical System for the Idoc Receiver
    WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
    Second - Log on to XI System:
    SM59 : RFC Destination for Sender System
    IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
    IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
    To Enable Acknowledgement:
    SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
    Category: RUNTIME
    Parameters: ACK_SYSTEM_FAILURE
    Current Value: 1
    Additional References
    Ale Configuration for pushing Idocs form SAP to XI
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

  • Short Dump while loading Delta from ODS to ODS

    Hi Experts,
    I have run into a short dump error while loading delta from one ODS to another via a process chain.
    Following is the error message:
    Error analysis                                                                               
    Short text of error message:                                                                 
        Request 0000259294 is not completely activated. Please activate it again                     
    Technical information about the message:                                                     
         Diagnosis                                                                               
    Activation of request 0000259294 has terminated, or is not yet                          
             complete.                                                                               
    System response                                                                               
    Procedure                                                                               
    If the process has terminated, all of the requests that the system                      
             was unabe to activate in the most recent activation process have to                     
             be reactivated before the new requests can be activated.                                
             If you are not able to carry out this activation step, delete the                       
             relevant requests from the administration of the ODS object (on the                     
             Requests tabstrip).                                                                     
         Procedure for System Administration                                                         
        Message classe...... "RSM1"                                                                  
        Number.............. 180                                                                     
        Variable 1.......... 0000259294                                                              
        Variable 2.......... " "                                                                     
        Variable 3.......... " "                                                                     
        Variable 4.......... " "                                                                     
        Variable 3.......... " "                                                                     
        Variable 4.......... " "                                                                     
    Can someone help me resolve this?
    Thank you

    Check the status of request SID 259294  in ODS, whether the Activation got completed or not. If not wait till the activation completes.
    If there is any problem in the activation process, correct that complete the activation process and load the ne request that you want to load..
    Regards
    VJ

  • How to send multiple idocs from WE19?

    How to send 100 IDocs at  a time using We19?
    in other words, can we generate 100 IDocs from a single Idoc using We19
    Thanks,
    Ven

    Hi Venkat,
    Check program RSEOUT00.
    Hope this helps.
    Regards
    Lakshman

  • Unable to send idoc from WE19 Transaction

    Hello All
         I am working on Idoc to file. When i am triggring from WE19 i am getting error IDoc 0000000000712906 was saved but cannot or should not be sent. How can i resolve this problem
    Edited by: venkat k on Jun 14, 2008 6:05 PM

    You need to give more information.
    - Logfiles
    - What kind of connection between R/3 and XI/PI
    - More description of the error

  • Error while creating IDOC from payment run

    Dear All,
    I 've alredy done all EDI settings for creating IDOC from payment run. But system in not generating IDOC as end with a result as "House bank is not designated as a EDI Partner'.
    Please suggest how to define house bank as a EDI partner.
    Regards,
    Subhash

    From We20 u have to create the partner profile for the bank u r using in ur transaction. In we20 select the partner type B (Bank) and as Partner no give ur bank numbrer.
    Regards,
    Joy.

  • While Posting IDOC  from XI to R/3 Message Type needs to be changed

    We are doing mapping IN XI. For one condition we want Message Type to be ORDERS and for one condition we want Message Type to be ORDERSCHG
    when posting IDOC from XI to R/3.
    Pls revert anybody asap.
    Regards

    Hi,
    >>>>It means I need to create two Interface Mappings for the same message mapping and then I can use the Interface Determination . Am I right.
    no, you need two message mapping
    and two interface mappings
    file - orders.orders05
    file - ordrchg.order05
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Maybe you are looking for

  • Data recovery from failed HDD in my 2.16 Core 2 Duo black case?

    I have a question mark upon startup and the OS never launches, and I tried using a new 10.6 DVD to install the OS again and use the utilities on the DVD. I quickly saw there was no recognition of the HDD. I ordered and am installing a new 320GB 7200

  • This entry already exists in the following tables 'Deposit' (ODPS)(ODBC -02

    My client gets this message when she tries to do a deposit.  She was fine up until 2/13 and this week, this has started to happen.  Any suggestions that I can look for This entry already exists in the following tables 'Deposit' (ODPS)(ODBC -2035) [Me

  • Root.sh hangs in CRS install on first node

    Hi all, I am installing CRS 10.2.0 in RHEL 5 on VMWARE.when It is asking for two scripts(oraInstRoot.sh and root.sh) as a root user.First script completes with out any error on both nodes while root.sh script hangs in first node at line Startup will

  • Selling to employees

    Hi, I want to use the employee number (HR code) as a payer in the sales document, I changed the partner function (PY) to be PE instead of KU but the payer is empty in the billing tab of the sales document!!! Any ideas?? Thanks Mostafa

  • Connecting ASA from inside of the network

    The LAN has 10.10.10.0/24 ip pool and ASA has 10.10.11.0/24 pool. When i connect to the ASA from the inside of the network , i can't get to any node in the network but i can when i am outside of the network. I need to connect to all nodes even when I