Error in Testing Inbound  Idoc PORDCR102

Hi,
I am creating  purchase order using message type PORDCR1.
I have done the partner profile entry and Process code is 'BAPI'.
while testing the Inbound Idoc PORDCR102 using WE19.
I am passing the Control Record and the data record Information.
But when I am executing it in forground it is giving me Dump and IDOC remains in status 62.
<b>Error is :-</b>
<i>Access via 'NULL' object reference not possible.</i>
<b>Error analysis</b>
    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 RAISIN
     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.
I verified the data by creating the Purchase order using BAPI_PO_CREATE1, purchase order is successfully created.
Do Anyone have done a similar testing for message type PORDCR1, please give me your suggestions.
Thanks
Monika.

Hi Shankar,
check whther u r using the correct function module for correct message type.
anyway check the following configurations for an inbound idoc.
1>we81
2>we31
3>we30
4>bd51
5>we57
6>we42
7>we20
Regards,
Nagaraj

Similar Messages

  • Error while testing Inbound Idoc

    The error message "Interface for function Z***** is incorrect*." is shown while trying to test an incoming IDOC in we19.
    PL HELP!!!!!!!
    The procedure followed by me was,
    WE31 created custom segments,
    WE30 Created custom basic type,
    we81  Custom message type,
    se37 function module,
    we82,
    we57,
    bd51,
    we42,
    bd67,
    we20,
    Am not able to figure out why exactly is the error message being shown.
    please tell me if a step was missed or what the possible error is, I think the parameters of function module are correct....

    Hi friend,
    if it is help full please give max reward point.
    Standard program, RBDMOIND is scheduled or executed online to determine whether the communication was successful. If IDoc is Dispatched to destination system, RBDMOIND updates the status of the IDoc to 12 (Dispatched OK), Otherwise remains in status 03.
    Two programs enable cross-system reporting:
    &#61656;     RBDSTATE: It reports the status of the incoming IDocs to sending system, using ALEAUD message and ALEAUD01 IDoc
    &#61656;     RBDAUD01: It executed on sending system to analysis the audit log and display the output as a report          
    IDoc Status in Receiving System          IDoc status in Sending System via ALEAUD
    53 – Application docu posted     =>     41 – Application docu created in receiving sys
    51 – Error: Application docu      =>     39 – IDoc in receiving sys. Status repeated
         not posted                         each time RBDSTATE runs.
    68 – Error: No further processing     =>     40 – Application docu not created
    ALE Auditing
    BDM7          =>     ALE Audit: Statistical Analysis
    BDM8          =>     ALE Audit: Sending the Confirmations
    RBDSTATE     =>     Run on Receiving System to return Audit Message

  • System dump whiling testing Inbound IDoc for BOMMAT(Bill of material)

    HI Experts,
    I m testing Inbound IDoc from T-Code 'we19' using logical system 'BOMMAT' .System is giving a dump with error"Field Symbol has not yet been assigned". while testing t_code 'we02' A IDoc is genreted with warning with status 64 with error 'No filters , No conversion , No version change . Please suggest some solution.
    Thanks
    Ravinder Singh

    Hi,
    Check the data in the idoc.
    This dump might happen due to numeric field you might have passed the character value. check throughly.
    Regards,
    Shanmugavel chandrasekaran

  • Testing Inbound Idocs

    Hi All!
    I am trying to fix an inbound Idoc program that is erroring in our testing environment with a REALLY big IDoc.  I need to move this IDoc to our development environment in order to be able to accurately fix the program.
    Is there any way to move an inbound IDoc from one environment to another without manually re-creating it or having to create an outbound IDoc process of some sort?
    Help is MUCH appreciated - thanks!
    Abby

    Try out this
    On the source system
    Go to WE19 - > IDoc -> Test Inbound IDoc ->Inbound File
    Here enter application server path like
    /appl/interfaces/MDDC/MLGA01
    Also Uncheck the check box Start IDoc inbound processing of file imm.
    On the target system
    Go to WE16
    Give the same application server file name in Directory + File name
    In Port give EDIPORT  and run it.  
    This will create an IDoc
    Regards
    Kesava
    Message was edited by:
            Kesava Chandra Rao

  • Error in number range while testing inbound idoc via we19

    hi all,
    i have done all configurations but while testing the inbound idoc via we19 i am getting an error 'error in assigning number to idoc'..i checked and found that the number range object for idoc is edidoc in it number interval is defined from 1 to 99
    i dont think that anything is wrong with the number object..
    Can u tell me how dow i eliminate this error?

    Increase Higher limit the reason is when you look at current idoc number ( This idoc number already exists ) ,it will not create new idoc number.
    System will get the number from SNRO Based on IDOC Object.
    Just look at EDIDC and see the current idoc number.
    Simple example :
    I have one number - 100 ,it is already exists in database,if i insert same record to the database ,did system will accept ?
    Thanks
    Seshu

  • 'Purchasing document does not exist' error while testing Inbound PO Idoc

    Hi experts,
    i am working on Inbound PO Idoc scenario. I am testing Idoc in WE19 with ORDRSP mesage type.
    Idoc type:ORDERS05
    Process code:ORDR
    FM:IDOC_INPUT_ORDRSP
    while trying to create PO it is giving an error 'Purchasing document does not exist' in we05.
    please suggest me how to resolve this???
    Regards,
    Bhuvan.

    Hi,
    first time i am testing this IDoc and i don't find any field in Idoc structure to provide purchase order value.
    any more inputs plz??
    regards,
    bhuvan.

  • Urgent help required : Batch processing error of an inbound idoc

    hi,
       i have a problem while posting an idoc to the GL(FB01).
    i'm using an Inbound idoc message type : ACC_GL_POSTING
    idoc type : ACC_GL_POSTING01.
    Process code : BAPI.
    In the transaction code OBA7 i have enabled a particular document type as BATCH INPUT ONLY.
    i have set the option " Trigger by background program" in the partner profile (we20).
    while testing the process i'm getting the error "Document type -- is only defined for batch input".
    how can i overcome this error? can idocs be used to post for transaction that are batch enabled . plz help me.
    with regards.
    T.Jeyagopi.

    Jeyagopi,
    There are different types of Data loading into SAP.
    BATCH INPUT / BDC / IDOC / BAPI etc. BATCH INPUT are standard programs that take the data and update SAP. I don't think that is same as batch processing of IDOC.
    You might want to remove the setting of batch input, retain the batch processing in WE20 and try it out.
    In my opinion it should work.
    Regards,
    Ravi
    Note : Please reward points for the posts that help you.

  • Error in testing an idoc -Trans. XK01 : CoCde not entered; company code are

    Hi
    I am getting the following error when i am trying to test a idoc thru we 19.
    The message type is CREMAS and it is an inbound idoc ,I am testing the function module
    idoc_input_creditor .
    Trans. XK01 : CoCde not entered; company code area not being edited
    I have entered   the company code in E1LFBWM segment  but still getting the same error .
    Can some one advise how this error can be solved
    Thanks in advance
    Anjali

    Hi ,
    Have you entered Company code value in all the required segments ? Like E1LFB1M , E2LFB5M..
    Regards,
    Deepthi

  • Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

    Hello,
    I have a inbound Idoc of type HRMD_A (basistype  HRMD_A07) which is processed by Function module (FM)  IDOC_INPUT_HRMD with  proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
    Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty)  When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
    Return and Return1
    of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
    CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
              EXPORTING
                pernr                          = ins_objects-objid       "#EC DOM_EQUAL
                actio                           = 'INS'
                tclas                           = tclas
                dialog_mode               = dial_mode
                luw_mode                  = '0'
                no_existence_check = $cross
                no_enqueue              = $cross
              IMPORTING
                return1                       = return
                hr_return                    = hr_return
              TABLES
                proposed_values    = proposed_values.
            REFRESH proposed_values.
         IF hr_return-msgty = 'E'.                           "note 984409
          CLEAR protocol_error.
          protocol_error-msgty  = hr_return-msgty.
          protocol_error-msgid  = hr_return-msgid.
          protocol_error-msgno  = hr_return-msgno.
          protocol_error-msgv1  = hr_return-msgv1.
          protocol_error-msgv2  = hr_return-msgv2.
          protocol_error-msgv3  = hr_return-msgv3.
          protocol_error-msgv4  = hr_return-msgv4.
          READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
                                           infty = hr_return-infty
                                           subty = hr_return-subty.
          protocol_error-segnum = t_hrobjinfty-segnum.
          protocol_error-routid = 'create_prf_pa_pb_object'
    As mentioned above, the error message is only placed in the parameters Return and Return1  and not in HR_RETURN.please read the first reply

    Hi,
    I think you have preety much done from your end itself .
    Could you please tell me what you got in this parameters:
         protocol_error-msgty  = hr_return-msgty.
          protocol_error-msgid  = hr_return-msgid.
          protocol_error-msgno  = hr_return-msgno.
          protocol_error-msgv1  = hr_return-msgv1.
          protocol_error-msgv2  = hr_return-msgv2.
          protocol_error-msgv3  = hr_return-msgv3.
          protocol_error-msgv4  = hr_return-msgv4.
    It may help us to track down the issue in more better way .
    Thanks!

  • B1358 error while posting inbound idoc with a FM

    Hi
    We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
    The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
    No status record was passed to ALE by the application
    Message no. B1358
    Diagnosis
    The application failed to return a status record to the ALE layer after the IDoc was processed.
    This is due to an error in the application function module which processed the inbound IDoc.
    Procedure
    If you wrote the application function module yourself, you need to change the program.
    If the function module in question is a standard application function module, you should consult SAP.
    Note: we are using a custom function module
    regards
    krishna

    Hi Krishna,
    I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
    Please check out the programming guidelines in the SAP Online Help under:
    <a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
    Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
    Best regards,
    SIlvia

  • How to Test, Inbound idoc ,with out the Sender System, using a Text File

    Hi Guru's .
    we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
    on the same client.
    we wanted to test this idoc with text file from our local machine.
    Can anyone give us detail steps.like how to create  File layout
    with Segment name,and values for the fields.how to pass this file to the system.
    Thanks in advance.

    Hi Aparna.
    My requirement is to test the idoc with Inbound File.
    Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
    when i am trying to do this syst complaing about
    Partner Profile not available, and some times
    port not available. and some  times with
    'No further processing defined'.
    but i maintained part profiles and port perfectly.
    Can you help me in testing with test 'File' port.

  • Error while posting Inbound Idocs-"EDI: Partner profile not available"

    Hi,
    I am getting the error "EDI: Partner profile not available" Status -56 while creating inboud Idocs.
    I have done the following steps so far
    1.Created IDOC basic Type and Message Type. (Custom)
    2. Created process code to process the IDOC.
    3. Use the FM IDOC_INBOUND_WRITE_TO_DB to create the inbound IDOC.
    4. Use the FM IDOC_START_INBOUND to process the IDOC.
        Is ther anything else that i have to do inorder to post the idoc sucessfully.
    Thanks in advance
    -Nishant
    Edited by: nishant patel on Nov 13, 2009 10:35 AM
    Edited by: nishant patel on Nov 13, 2009 10:41 AM

    Hi,
    Check in WE20 if the partner profile is configured for the idoc type and the message type. That might be the cause of the error.
    Also make sure the same partner profile details are sent to the control record. Partner profile details are stored in the table EDP13.
    Hope this helps
    Regards
    Shiva

  • Handling of Error(s) for Inbound IDOCs

    Hi Gurus,
      I have an requirement where we need to handle and correct the error if inbound IDOC fails. This inbound will be for Account Document posting.
    Please let me know how to handle this issue.
    Thanks in advance.
    Regards,
    Gajanan

    <b>Hi,
    smells like workflow task.
    DI Information
    Message type
    INVOIC
    IDOC type
    INVOIC01, INVOIC02
    X12 transaction set
    810
    Edifact message type
    INVOIC
    Workflow in case of error
    TS 0000 8056</b>
    Executable program
    IDOC_INPUT_INVOIC_FI
    Regards,
    Clemens

  • Error while testing Inbound INVOIC with we19

    Hello Friends,
    I want to test inbound invoic with we19.
    I get now the mistake : external sender not avaiable (status 51) (translated from the german : Externer Sender wurde nicht angegeben).
    I guess the INVOIC-Idoc ist correct.
    Whal could it be?
    thanks and best regards

    Hi Check the following config
    Data Transfer(System Settings for Idoc Interface
    Define Conversion of External Item Identification
    Basic Settings for Document Transfer
    Also check the partner profile and check if you have additional segments for item data. If yes then maintain it Document transfer from external system
    Hths
    Saj

  • Testing Inbound IDoc via WE19...

    Hi,
    I am trying to learn IDOCs via WE19.
    I just took a sample IDOC from WE02 and tried to test in WE19.
    I am trying to understand what do we mean by following:
    1) Process Inbound IDOC via file ?
    2) Process Inbound IDOC via function module ?
    Regards,
    Rajesh,

    Rajesh,
    Go thru this link
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

Maybe you are looking for