Inbound idoc payext error 51 In House Cash

Hi
I have an inbound idoc PAYEXT PEXC with status 51 and error message " No parameters found for: IHC H EUR" Message no. IHC205 ". second error message: "Creation of header data failed msg IHC 196" this error has also status 51.
IHC is the bank area, H is a payment method (cheques) that I do not use in IHC and does not exist in FBZP.
The idoc has basic type PEXR2002. segment 26.
Any hint how to solve or debug?

Hi Sreeram,
I made the configuration for Posting accounts as per your advise. 'Now I am getting another error message as shown below
Creation of individual payment requests failed
Message no. IHC197
Partner number of account type is invalid
Message no. IHC000
What does this mean and what is the remedy for this?
Thanks
Kalyan

Similar Messages

  • Inbound idoc with error status 52 messege type hrmd_a07

    i have an inbound idoc with status 52
    error messege : Object 01 ,P ,00056786 does not exist: infotype 0302 cannot be created
                             Object 01 ,P ,00056786 does not exist: infotype 0006 cannot be created
    i debugged but i haven't find out the reason
    am updating 0000,0001,0002,0003,0006 infotypes

    Hi rahul,
    Need to check the address filed (0006) for BP mapped to postion (00056786)
    Infotype 0302 (Additional Actions) :
    Infotype 0302 is not maintained directly and is automatically updated by Infotype 0000 .
    The additional actions Infotype (0302) is of time constraint 3 (gaps and overlaps).
    Specifically in some cases if we want to have a non status-changing Action on the same day where already a personnel action is existing at that time we can activate the Infotype 302 by executing Report RPUEVSUP.
    please check and let me know . I think it will be helpfull
    Thanks and Regards,
    Krishna

  • Inbound IDOC process error

    Hi
    While an Inbound is being processed it is not behaving as per the design and if the same type of idoc is reprocessed through BD87 is it behaving as per the design.
    In detail, the idoc will create a purchase order based on reservation number in R/3 and the quantity needs to be checked against the availability. If the quantity is more in the idoc counting all line items of idoc segments it should not be posted giving that the quantity is not available. If it is automated it is not checking, but while testing on creation of an inbound idoc and reprocessed the validation is happenning.
    So, please help me in understanding as why the idoc is not getting validated when it is automated ans whne it is reprocessed through BD87 it is getting validated.
    Thanks
    Shankar

    Hi Shankar,
    how do you notice that your code is not executed.
    Usually I would say it should.
    Therefore I recommended to implement an infinite loop to make sure that it is really not executed.
    By the way...where did you implement your coding?
    Best regards,
    Oliver
    Edited by: Oliver Hütköper on Aug 12, 2011 8:45 AM

  • Inbound IDOC processing, error duplicate key

    We want to retrieve certain order-idocs in our system, before they are processed, to change AND insert segment data.
    Flow we use in our current program
    - DOC_STATUS_WRITE_TO_DATABASE
    to change the status of the idoc (ok) (status 69)
    - EDI_DOCUMENT_OPEN_FOR_EDIT (ok)
    - EDI_CHANGE_DATA_SEGMENTS (ok)
    - EDI_DOCUMENT_CLOSE_EDIT => not ok
    This program gives SAPSQL error
    Via debugging, we see that a new idoc number is
    called (save as backup idoc ?), but we want the
    current IDOC to be processed.
    The system wants to insert in EDID4 => dump :
    "Use an ABAP/4 Open SQL array insert only if you
    are sure that none of the records passed already
    exists in the database."
    ( I prefer to use these standard functions, in stead of just deleting and inserting into "EDID4" )
    regards,
    answers will be rewarded.
    code extract
    INCLUDE ZBE01458_TOP.
    INITIALIZATION.
    V_EDIT_STATUS = '69'.
    V_PROCESSED_STATUS = '32'.
    start-of-selection.
    clear t_edidc. refresh t_edidc.
    SELECT * FROM EDIDC into table t_edidc
    WHERE DOCNUM in S_docnum
    and mestyp in S_mestyp
    and idoctp in S_idoctp
    and credat in S_credat
    and rcvpor in S_rcvpor
    and rcvprt in S_rcvprt
    and rcvprn in S_rcvprn
    and sndpor in S_sndpor
    and sndprt in S_sndprt
    and sndprn in S_sndprn
    and status in S_status.
    loop at t_edidc.
    move t_edidc-docnum to v_docnum.
    refresh v_status.
    V_STATUS-docnum = V_DOCNUM.
    V_STATUS-status = V_EDIT_STATUS.
    clear EDIDS.
    select single * from EDIDS where docnum = v_docnum.
    if sy-subrc = 0.
    MOVE EDIDS-STACOD to V_STATUS-STACOD.
    endif .
    APPEND V_STATUS.
    PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
    changing part for DEDIDD "idoc data
    PERFORM OPEN_IDOC_FOR_CHANGE.
    PERFORM CHANGE_IDOC.
    PERFORM CLOSE_IDOC_FOR_CHANGE.
    refresh v_status.
    V_STATUS-docnum = V_DOCNUM.
    V_STATUS-status = V_PROCESSED_STATUS.
    APPEND V_STATUS.
    PERFORM CHANGE_IDOC_STATUS tables V_STATUS
    USING V_DOCNUM.
    endloop.
    *& Form OPEN_IDOC_FOR_CHANGE
    text
    --> p1 text
    <-- p2 text
    FORM OPEN_IDOC_FOR_CHANGE.
    CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
    EXPORTING
    DOCUMENT_NUMBER = V_DOCNUM
    ALREADY_OPEN = 'N'
    IMPORTING
    IDOC_CONTROL =
    TABLES
    IDOC_DATA = DEDIDD
    EXCEPTIONS
    DOCUMENT_FOREIGN_LOCK = 1
    DOCUMENT_NOT_EXIST = 2
    DOCUMENT_NOT_OPEN = 3
    STATUS_IS_UNABLE_FOR_CHANGING = 4
    OTHERS = 5
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM. " OPEN_IDOC_FOR_CHANGE
    *& Form CHANGE_IDOC
    text
    --> p1 text
    <-- p2 text
    FORM CHANGE_IDOC.
    CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
    TABLES
    IDOC_CHANGED_DATA_RANGE = DEDIDD
    EXCEPTIONS
    IDOC_NOT_OPEN = 1
    DATA_RECORD_NOT_EXIST = 2
    OTHERS = 3.
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM. " CHANGE_IDOC
    *& Form CLOSE_IDOC_FOR_CHANGE
    text
    --> p1 text
    <-- p2 text
    FORM CLOSE_IDOC_FOR_CHANGE.
    CLEAR t_EDI_DS40.
    t_edi_ds40-docnum = v_docnum.
    t_edi_ds40-status = '51'.
    t_edi_ds40-repid = sy-repid.
    t_edi_ds40-tabnam = 'EDI_DS'.
    t_edi_ds40-mandt = sy-mandt.
    t_edi_ds40-stamqu = 'SAP'.
    t_edi_ds40-stamid = 'B1'.
    t_edi_ds40-stamno = '999'.
    t_edi_ds40-stapa1 = 'Changes made to idoc ...'.
    t_edi_ds40-stapa2 = t_new_kunnr.
    t_edi_ds40-logdat = sy-datum.
    t_edi_ds40-logtim = sy-uzeit.
    APPEND t_edi_ds40.
    CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
    EXPORTING
    DOCUMENT_NUMBER = V_DOCNUM
    DO_COMMIT = 'X'
    DO_UPDATE = 'X'
    WRITE_ALL_STATUS = 'X'
    TABLES
    STATUS_RECORDS = t_EDI_DS40
    EXCEPTIONS
    IDOC_NOT_OPEN = 1
    DB_ERROR = 2
    OTHERS = 3
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ENDFORM. " CLOSE_IDOC_FOR_CHANGE
    *& Form CHANGE_IDOC_STATUS
    text
    --> p1 text
    <-- p2 text
    FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
    USING P_DOCNUM.
    CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
    EXPORTING
    IDOC_NUMBER = p_docnum
    IDOC_OPENED_FLAG = ' '
    NO_DEQUEUE_FLAG = 'X'
    IMPORTING
    IDOC_CONTROL =
    TABLES
    IDOC_STATUS = P_IDOC_STATUS
    EXCEPTIONS
    IDOC_FOREIGN_LOCK = 1
    IDOC_NOT_FOUND = 2
    IDOC_STATUS_RECORDS_EMPTY = 3
    IDOC_STATUS_INVALID = 4
    DB_ERROR = 5
    OTHERS = 6
    IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    else.
    commit work.
    ENDIF.
    ENDFORM. " CHANGE_IDOC_STATUS

    Urmila,
    I tried this sequence : code extract follows...
    I got the duplicate key errors again.
    what about delete first and then insert again in EDID4 table ?
    source code extract:
    INCLUDE ZBE01458_TOP.
    INITIALIZATION.
      V_EDIT_STATUS = '69'.
      V_PROCESSED_STATUS = '32'.
      V_SAPCODE = 'SAPE0184'.
    start-of-selection.
      clear t_edidc. refresh t_edidc.
      SELECT  * FROM  EDIDC into table t_edidc
             WHERE  DOCNUM  in S_docnum
               and  mestyp  in S_mestyp
               and  idoctp  in S_idoctp
               and  credat  in S_credat
               and  rcvpor  in S_rcvpor
               and  rcvprt  in S_rcvprt
               and  rcvprn  in S_rcvprn
               and  sndpor  in S_sndpor
               and  sndprt  in S_sndprt
               and  sndprn  in S_sndprn
               and  status  in S_status.
      loop at t_edidc.
        move t_edidc-docnum to v_docnum.
        move-corresponding T_EDIDC to WA_EDIDC.
        V_STA-docnum      = v_docnum.
        V_STA-status      = '51'.
        V_STA-repid       = sy-repid.
        V_STA-tabnam      = 'EDI_DS'.
        V_STA-mandt       = sy-mandt.
        V_STA-stamqu      = 'SAP'.
        V_STA-stamid      = 'B1'.
        V_STA-stamno      = '999'.
        V_STA-stapa1      = 'Changes made to idoc ...'.
    t_edi_ds40-stapa2      = t_new_kunnr.
        V_STA-logdat      = sy-datum.
        V_STA-logtim      = sy-uzeit.
        V_STA-STACOD       =  V_SAPCODE.
        PERFORM OPEN_FOR_PROCESS.
        PERFORM SET_IDOC_STATUS USING V_DOCNUM V_STA.
        PERFORM CLOSE_IDOC_FOR_PROCESS.
        PERFORM OPEN_IDOC_FOR_CHANGE.
        PERFORM PROCESS_IDOC_STRUCTURE.
        PERFORM CHANGE_IDOC.
        PERFORM CLOSE_IDOC_FOR_CHANGE.
       refresh v_status.
       V_STATUS-docnum = V_DOCNUM.
       V_STATUS-status = V_EDIT_STATUS.
       V_STATUS-STACOD = V_SAPCODE.
       clear EDIDS.
       select single * from EDIDS where docnum = v_docnum.
       if sy-subrc = 0.
        MOVE EDIDS-STACOD to V_STATUS-STACOD.
       endif .
       APPEND V_STATUS.
       PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING  V_DOCNUM.
      endloop.
    *&      Form  OPEN_IDOC_FOR_CHANGE
          text
    -->  p1        text
    <--  p2        text
    FORM OPEN_IDOC_FOR_CHANGE.
      CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
         DOCUMENT_NUMBER                     = V_DOCNUM
      ALREADY_OPEN                        = 'N'
    IMPORTING
       IDOC_CONTROL                        = WA_EDIDC
       TABLES
         IDOC_DATA                           = DEDIDD
      EXCEPTIONS
        DOCUMENT_FOREIGN_LOCK               = 1
        DOCUMENT_NOT_EXIST                  = 2
        DOCUMENT_NOT_OPEN                   = 3
        STATUS_IS_UNABLE_FOR_CHANGING       = 4
        OTHERS                              = 5
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " OPEN_IDOC_FOR_CHANGE
    *&      Form  CHANGE_IDOC
          text
    -->  p1        text
    <--  p2        text
    FORM CHANGE_IDOC.
      CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                IDOC_CHANGED_DATA_RANGE = DEDIDD
           EXCEPTIONS
                IDOC_NOT_OPEN           = 1
                DATA_RECORD_NOT_EXIST   = 2
                OTHERS                  = 3.
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " CHANGE_IDOC
    *&      Form  CLOSE_IDOC_FOR_CHANGE
          text
    -->  p1        text
    <--  p2        text
    FORM CLOSE_IDOC_FOR_CHANGE.
      CLEAR t_EDI_DS40.
      t_edi_ds40-docnum      = v_docnum.
      t_edi_ds40-status      = '69'.
      t_edi_ds40-repid       = sy-repid.
      t_edi_ds40-tabnam      = 'EDI_DS'.
      t_edi_ds40-mandt       = sy-mandt.
      t_edi_ds40-stamqu      = 'SAP'.
      t_edi_ds40-stamid      = 'B1'.
      t_edi_ds40-stamno      = '999'.
      t_edi_ds40-stapa1      = 'Changes made to idoc ...'.
    t_edi_ds40-stapa2      = t_new_kunnr.
      t_edi_ds40-logdat      = sy-datum.
      t_edi_ds40-logtim      = sy-uzeit.
      APPEND t_edi_ds40.
      CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
           EXPORTING
                DOCUMENT_NUMBER  = V_DOCNUM
                DO_COMMIT        = 'X'
                DO_UPDATE        = 'X'
                WRITE_ALL_STATUS = 'X'
           TABLES
                STATUS_RECORDS   = t_EDI_DS40
           EXCEPTIONS
                IDOC_NOT_OPEN    = 1
                DB_ERROR         = 2
                OTHERS           = 3.
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " CLOSE_IDOC_FOR_CHANGE
    *&      Form  CHANGE_IDOC_STATUS
          text
    -->  p1        text
    <--  p2        text
    FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
    USING P_DOCNUM.
      CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
    EXPORTING
      IDOC_NUMBER                     = p_docnum
            IDOC_OPENED_FLAG                = ' '
            NO_DEQUEUE_FLAG                 = 'X'
          IMPORTING
            IDOC_CONTROL                    =
    TABLES
      IDOC_STATUS                     = P_IDOC_STATUS
          EXCEPTIONS
            IDOC_FOREIGN_LOCK               = 1
            IDOC_NOT_FOUND                  = 2
            IDOC_STATUS_RECORDS_EMPTY       = 3
            IDOC_STATUS_INVALID             = 4
            DB_ERROR                        = 5
            OTHERS                          = 6
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      else.
        commit work.
      ENDIF.
    ENDFORM.                    " CHANGE_IDOC_STATUS
    *&      Form  OPEN_FOR_PROCESS
          text
    -->  p1        text
    <--  p2        text
    FORM OPEN_FOR_PROCESS.
      CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_PROCESS'
        EXPORTING
      DB_READ_OPTION                 = DB_READ
          DOCUMENT_NUMBER                = V_DOCNUM
      ENQUEUE_OPTION                 = SYNCHRONOUS
    IMPORTING
       IDOC_CONTROL                   = WA_EDIDC
    EXCEPTIONS
      DOCUMENT_FOREIGN_LOCK          = 1
      DOCUMENT_NOT_EXIST             = 2
      DOCUMENT_NUMBER_INVALID        = 3
      DOCUMENT_IS_ALREADY_OPEN       = 4
      OTHERS                         = 5
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " OPEN_FOR_PROCESS
    *&      Form  SET_IDOC_STATUS
          text
    -->  p1        text
    <--  p2        text
    FORM SET_IDOC_STATUS USING P_DOCNUM P_STA.
      CALL FUNCTION 'EDI_DOCUMENT_STATUS_SET'
        EXPORTING
          DOCUMENT_NUMBER               = P_DOCNUM
          IDOC_STATUS                   = P_STA
    IMPORTING
       IDOC_CONTROL                  = WA_EDIDC
    EXCEPTIONS
      DOCUMENT_NUMBER_INVALID       = 1
      OTHER_FIELDS_INVALID          = 2
      STATUS_INVALID                = 3
      OTHERS                        = 4
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " SET_IDOC_STATUS
    *&      Form  CLOSE_IDOC_FOR_PROCESS
          text
    -->  p1        text
    <--  p2        text
    FORM CLOSE_IDOC_FOR_PROCESS.
      CALL FUNCTION 'EDI_DOCUMENT_CLOSE_PROCESS'
        EXPORTING
          DOCUMENT_NUMBER           = V_DOCNUM
      BACKGROUND                = NO_BACKGROUND
      NO_DEQUEUE                = ' '
    IMPORTING
       IDOC_CONTROL              = WA_EDIDC
    EXCEPTIONS
      DOCUMENT_NOT_OPEN         = 1
      FAILURE_IN_DB_WRITE       = 2
      PARAMETER_ERROR           = 3
      STATUS_SET_MISSING        = 4
      OTHERS                    = 5
      IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " CLOSE_IDOC_FOR_PROCESS

  • IHC0: IDOC PAYEXT error No parameters found for: bank area IHC H EUR IHC205

    Hello
    I created with F110 an payment run for an external invoice. In transaction IHC0 I can see the payment order. When I post the payment order an outbound idoc is created but ended with status 51 and error " No parameters found for: IHC H EUR" Message no. IHC205 ".
    What customizing in IMG Account Management is wrong?
    Is it possible to debug the idoc in WE19? I want to see where the messageIHC205 is generated (select from which table?). The wrong payment method H has been determined, it should be another payment method.  In function module " FI_EDI_PAYEXT_PEXR2001_OUT " I inserted a breakpoint but the system did not stop there.

    Hi Sreeram,
    I made the configuration for Posting accounts as per your advise. 'Now I am getting another error message as shown below
    Creation of individual payment requests failed
    Message no. IHC197
    Partner number of account type is invalid
    Message no. IHC000
    What does this mean and what is the remedy for this?
    Thanks
    Kalyan

  • Inbound Idoc[INVOIC[ - Error

    Hi,
    When I try to post the incoming IDoc INVOIC01 with Message Type - INVOIC and Process Code - INVL
    there always error :- 51 with "message no EA 066, message from Idoc
    processing can be found in application log."
    Does anybody know how to set in the system to made the INVOIC work?
    Thanks.

    Hi,
    sure we know
    1. open the application log and check for errors there and correct them
    (either from SLG1 or from IDOC status record)
    2. processing of the invoic idoc is also described in step by step in my book:
    http://www.sap-press.com/products/Mastering-IDoc-Business-Scenarios-with-SAP-NetWeaver-PI.html
    chapter: .. Logistic Invoice Verification
    Regards,
    Michal Krawczyk

  • Inbound idoc error in 51 Status of at least one serial number of item

    Dear Experts,
    There is one inbound IDOC which is in error with status 51 showing error Status of at least one serial number of item  is not allowed.
    Can you please advice why this error is coming.
    Thanks & Regards,
    Nikhil Kanegaonkar.

    An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
    http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
    http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
    Edited by: Krupaji on May 6, 2011 2:38 PM

  • Inbound IDOC & Comminication in Nomination

    We have a scenario on the Mining industry where we created nomination (T Cd : O4NSN ) for transport of coal by railways . The outbound communication  IDOC was successfully sent to a Transport Agency and is reflected in the u201C Communication Tabu201D of the Nomination.
    I am getting following issues :
    1. Subsequently , the Transporter/railways has send a back a communication via incoming Idoc which fails with following Eror Message : EDI: Partner profile not available
    We have tried to create the partner function for processing of Inbound Idoc with following data .
    Message type     : OIJ_NOM_COMM
    Basic Type     : OIJ_NOM_DETAIL01
    Partner Type     : KU
    Can you please inform me the approriate Process Code for the inbound IDOC ?
    2. Also I have noticed that that  During Outbound Communication to the transporter the u201CActionu201D (Communication Tab of Nomination) field idicates as  u201C Current Itemu201D. But my understanding is that it should  show status : u201C New entry sentu201D .
    Can you please guide on how I can define the partner function and resolve these issues .

    An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
    http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
    http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
    Edited by: Krupaji on May 6, 2011 2:38 PM

  • Payment requests created from In-House Cash - error with PAYEXT IDOC

    Hello -
    I am getting getting a '51' error with my inboud PAYEXT IDOC and the payment request cannot be created and the IDOC error is : Error creating the payment requests - no valid payment method available.  
    I have checked the Route process config in IHC and it looks good (or I think so).  I then checked the IHC config: Set Up of payment request for inbound IDOC in FI and am wondering about the Processing Parameters set up.  In this config, I see 2 payment methods field (Payment Method for This Payment) and (List of the Payment Methods to be Considered).   Can somebody tell me what's the difference between these two fields and since my payment method is not in the List of PM to be considered, could that be causing my erorr?
    Any guidance would greatly be appreciated.
    Thanks
    Becky

    Hi Odaiah
    I am in ECC 5.0 and when I view IMG activity IHC_VC_INB_CUST, there's a field called:
    Payment Method for This Payment(Payment method used to settle open items)
    and another field called List of the Payment Methods to be Considered.
    The invoice was paid via payment method 'W' and in our system, we are using IHC to make payments on behalf.  So after running F110 for payment method 'W', the IDOC gets created and sent to IHC to process.  IHC will then create the payment request (IDOC PAYEXT) which will then get process by F111.  Since the IDOC is failing, the payment request is not getting created.   You mentioned to get an ABAPer to throw in debug, I would love to but does not know the program that this process is running through. I tried putting it in debug from WE02 (IDOC processing) but with no success.
    Becky

  • Segment E1IDBW1 is missing for the inbound idoc type PAYEXT

    Hello,
    the above segment is missing in the inbound idoc - basic type pexr2002.
    I have checked in TC-we30 and its available there.
    but still the idoc is getting generated without this segment.
    can someone suggest.
    thanks
    Arun

    Hi All,
    I have a similar query to that of Penny. We are able to get the standard IDOC to generate with segment E1IDBW1. It contains the standard fields INPWEEMP, INPWTXT1, INPWTXT2. However, we have a requirement to manipulate the standard contents of these fields. We wanted to use user exit EXIT_SAPLIEDP_002 to do this.
    I have maintained user exit EXIT_SAPLIEDP_002 but when we enter this on creation of the IDOC the segment E1IDBW1 does not seem to be available in table EDIDD_TABLE for manipulation. Can you advise please if (1) you were able to get E1IDBW1 available to edit in exit EXIT_SAPLIEDP_002  and (2) were you able to manipulate the contents of INPWTXT1, INPWTXT2 etc?
    We have done the following steps:
    - BTE 2441 is available on our release
    - house bank has been setup as an In House Cash Center which allows E1IDBW1 to be generated
    - entry has been maintained in table FEDICUS with Message Type = PAYEXT, BasicType = PEXR2002, Extension = Blank, Seg Type = E1IDBW1
    - code maintained in ZXF08U04
    The system enters ZXF08U04 but E1IDBW1 is not available there for manipulation.
    Can you advise what we might be missing please?
    Thanks and regards
    Mike

  • Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

    Hello,
    I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
    While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
    Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
    Appreciate your inputs on this.
    Thanks and Regards
    Mohammed Roshan

    Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
    Could it be an issue with e Update rule in this Infostructire S008
    Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
    "Maintenance of SAP standard updates not allowed"
    Kindly advice
    Thanks and Regards
    Mohammed Roshan

  • Scheduling agreement inbound idoc error.

    Hi Experts,
    I am creating an Scheduling Agreement with DELFOR02 inbound idoc, while creation the Scheduling Agreement system is giving error regarding Scheduling Agreement not found. In fact I have create the Scheduling agreement by T-code VA31. And I check the table VLPKM, there are relevant record stored.
    Then I maintain the view V_T663A to not check everything when inbound idoc recevie. and tried agan in t-code BD87. the system give me another message Make an entry in all required fields.
    How can I handle these error messages?
    Thanks..
    Regards....

    Does any one has ideas for that?
    Thanks.

  • Error while trying to post inbound idoc of message type COND_A

    Hi,
    I am getting error while trying to post inbound idoc of message type COND_A.
    If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
    and if providing value in above fields then dump is coming.
    How to solve ?
    Plz do reply
    Thanks
    Mohit

    I do not see any reason why you would need to use COND_A04  if COND_A01 is working.
    What if you could get COND_A04 to post and you would face the same result as in COND_A01?
    If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
    For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
    fixed a situation where the vendor number was not validated.

  • 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

Maybe you are looking for

  • Display in editable alv grid.

    Hi, This is my source code of uploading excel into sap and displaying the list.Please give the code for displaying the excel  data in editable alv. <<The code came from [here|https://wiki.sdn.sap.com/wiki/display/Snippets/ABAP-UploaddatafromExceltoSa

  • Apple tv  2 - resolution problem: 480p instead of 720p

    Hi, my ATV2 is hooked to my Onkyo TX-SR508 via HDMI, wich is hooked to my Optoma HD65 projector via HDMI. unfortunately my ATV2 is only outputting 480p! Strangely when ATV2 is booting, it shows the apple logo in 720p, but when the menu comes on it is

  • Color correction with .mts files

    Hi,I´m editing .mts files in premiere pro, but I want to do the color correction in a diferent program, but since must of the programs don´t support mts files, what would you recomend? after that, I want to get back to premiere to finish my worflow,

  • Dialog not visible from sidekick when using dialog participant step

    I am using the Out of the box dialog participant step in my workflow. I have created a dialog and using in the dialog participant step. When i start the workflow, the dialog is only available/visible when I complete the task from inbox and not visibl

  • How to copy sequence from one project to another

    I have a corrupt project file.  My DIT on set opened many files in Resolve and afterwards created a PP for me organizing all the takes etc.  So, when I opened his Premiere Pro project, Speed Grade was the default software to open the Premiere project