Skip to Content
avatar image
Former Member

Testing Inbound IDOCS in WE19 for Invoice

I am working on a EDI project to create SAP invoice(MIRO) from vendor file.
Vendor will send invoice to middleware team, and they will create the idoc and send to SAP.

I have created all the necessary configurations with partner profiles and ports and I would like to test the inbound INVOIC02 type in WE19 manually but there are just too many segments and fields for me to know which fields needs to be filled in create an invoice.

anybody know where I can find a sample for inbound invoice? I can't seem to find anything.

thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Aug 11, 2017 at 07:32 AM

    Hi

    For the INVOIC IDOC, there is a process code INVL that corresponds to the FM IDOC_INPUT_INVOIC_MRM

    OR the process code INVF and FM IDOC_INPUT_INVOIC_FI can be checked

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I have my profile mapped to process code INVL. The problem I am having is that we dont have any idocs to test manually.

      I would like to create a Idoc manually in WE19 to test if I can post invoice in sap.

      as you know there are alot of segment types and fields that needs to be filled in . I dont know which fields needs to be filled in to post the invoice. ( ex. segment type E1EDK01) .

  • avatar image
    Former Member
    Aug 10, 2017 at 03:06 PM

    Do you have existing processes in the production system that use this IDoc? If so you could download a sample as a flat file, upload it to the application server of your test system and use the "file as template" option in WE19 to have something you can start with.

    There is no standard SAP tool to perform the IDoc download but every client I have worked for had a custom program for that job - just do a where-used for function IDOC_READ_COMPLETELY and you should find at least one :-)

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      If you have never used the IDoc, then indeed generating an outbound IDoc might give you an idea what to look for. Typical segments that you'll need and some common fields of their.

      E1EDK01

      • CURCY
      • HWAER
      • WKURS
      • ZTERM
      • KUNDEUINR
      • EIGENUINR
      • BSART
      • BELNR
      • NTGEW
      • BRGEW
      • GEWEI
      • RECIPNT_NO
      • FKTYP

      E1EDKA1 for Sold-to, Ship-to, Bill-to, Payer, Invoicing Party

      • PARVW
      • PARTN
      • LIFNR
      • NAME1
      • NAME2
      • STRAS
      • PFACH
      • ORT01
      • PSTLZ
      • PSTL2
      • LAND1
      • TELF1
      • TELFX
      • TELTX
      • SPRAS
      • SPRAS_ISO

      E1EDK02 for all the reference numbers that you need (check domain values of field QUALF)

      • QUALF
      • BELNR
      • DATUM

      E1EDK03 for every reference date that you need

      E1EDK04 for VAT

      E1EDK17 for your delivery terms

      E1EDK18 for your payment terms

      E1EDK28 for your bank details

      E1EDK14 for every org value that you want to include - typically at least sales org, dc, division, company code and billing type

      E1EDP01 for every invoice line item

      • POSEX
      • MENGE
      • MENEE
      • PMENE
      • VPREI
      • PEINH
      • NTGEW
      • GEWEI
      • PREIS
      • BRGEW
      • PSTYV
      • WERKS

      E1EDP02 for every line item reference - typically at least the PO number

      E1EDP03 for every line item date you need

      E1EDP19 for every material number reference you need

      E1EDP26 for every monetary amount you need

      E1EDP05 for any item conditions to be passed

      E1EDP04 for line level VAT

      E1EDS01 for any sums you need