Steer valuation type in inbound IDOC INVOIC

We are working with batch management.
When a purchase order is partially delivered, we need to make sure that the incoming vendor invoice (via IDOC type INVOIC) is linked to the correct valuation type.
I can steer the PO number en PO item line.
Is it also possible to have the valuation type in this iDOC?
Or do we need to do something else to book the costs to a certain valuation type?

Hi,
unfortunately it is not possible.
You might use Segment E1EDP02 with Qualifier = '016', and add Delivery Note into E1EDP02-BELNR.
this could be a 1:1 linkage between partial delivery and its invoice.
br,G

Similar Messages

  • Valuation type, batch and Idoc

    Hi guys,
    I am creating PO where I am not able to maintain valuation type and batch simultaneouly and Idoc is not created. Output type is maintained for EDI.
    I am wondering that is there configuration that valuation type and batch is maintained together
    Thanks & regards
    sanjay patil

    Hi,
    You have to configure Split valuation and Batch Managment while creating  Material master ,then create a P.O.
    G.Ganesh Kumar

  • 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 to post goods receipt with inbound delivery as reference

    Kindly let me know the message and IDOC type for
    Inbound IDOC to POST GOODS RECEIPT  with inbound delivery as reference
    I tried using WMMBXY but it didn;t work.
    Pls let me know asap.Your help is appreciated.
    Thanks and Regards
    Priti
    Edited by: Priti Adukia on Feb 11, 2008 4:48 AM

    Hi Nicole,
    What I've to do is quite the same as the case. Outbound and Inbound are in the same SAP system. If I've good understanding, I must set partner profile as follows :
    INBOUND - Parter LI with
                            Message DESADV
                            Operation code DELS
    OUTBOUND - Partner KU
                            Message DESADV
                            Operation code ???
    Please advise
    Suchart

  • Inbound IDoc using LSMW

    Hi..
    I am trying To Upload customer master data using LSMW with IDOc.
    I am debugging the Inbound IDoc Using BD87 and INPUT_METHOD = 'A'
    One segment E1KNB1M data is not passed to transaction 'XD01'  due that my company code data is not updated
    Pls tell me how to pass segment E1KNB1M data to transaction.
    I am using Message type :  /SAPSLL/DEBMAS_SLL
               Idoc type    :  Debmas03
            Function Module  : IDOC_INPUT_DEBITOR

    Hi Rishi,
         Thanks for the document. But the document mainly concentrates on LSMW(I'm aware of generic LSMW with BDC), it doesn't explain the inbound IDoc, segment merging, Creation of partner function or Message and Basic types WRT inbound IDoc. Please send any document with that relevance.
    Kiran

  • Standard IDoc Type for Inbound NonPO Vendor Invoices - FB60

    What should be the perfect standard IDoc Type for Inbound NonPO Vendor Invoice posting. Tcode FB60.
    I found IDoc Type FIDCCP02 but the Function Module 'IDOC_INPUT_FIDCC2' for FIDCCP02 is not released.
    In the same way many other standard function modules like - IDOC_INPUT_ACLPAY, IDOC_INPUT_FIDCCH, IDOC_INPUT_ACC_INVOICE_RECEIPT and few more are not released.
    My question : If at all I have to use standard IDoc Type, Message type and Function module (Released) for Inbound NonPO Vendor Invoices, then what should be the solution from SAP ?
    Thanks,
    Veeru.

    Hi,
    IDOC_INPUT_FIDCC2 for FIDCCP02 works for us in ECC6.0
    If you want Automatic tax calculation functionality using FIDCCP02.. then FIDCC2 is not correct message type for you. In that case you should probably go for :
    Msg: INVOIC
    Basic type: INVOIC02
    FM: IDOC_INPUT_INVOIC_FI
    Process code: INVF
    Thanks,
    Kumar

  • Inbound Idoc type for posting Non-PO Invoice

    Hi,
    I am looking for an inbound Idoc type to post Non-PO Invoice.  The Idoc types INVOIC01 and INVOIC02 helps me to post the invoice with reference to PO.  But I am looking for the Idoc type to post the invoices without reference to PO i.e., For example to post the transaction FB60 (Enter vendor invoice without ref to purchase order).
    with regards,
    suresh

    Hello Deep,
    I know it might be quite late for you for this answer, nevertheless I will write that, because there are lots of question like yours. bapi_incominginvoice_park is also a suitable bapi for you. All you need to do is call it this way:
    data: headerdata like bapi_incinv_create_header value is initial,
            table_item type table of bapi_incinv_create_item,
            gl_account like bapi_incinv_create_gl_account,
            table_gl type table of bapi_incinv_create_gl_account.
    * fill headerdata and table_gl, leaving table_item empty
    CALL FUNCTION 'BAPI_INCOMINGINVOICE_PARK'
        EXPORTING
          HEADERDATA                = HEADERDATA
    *   ADDRESSDATA               =
        IMPORTING
          INVOICEDOCNUMBER          = lv_docnr
          FISCALYEAR                = lv_year
        TABLES
          ITEMDATA                  = table_item
    *      ACCOUNTINGDATA            = table_acc
          GLACCOUNTDATA             = table_gl
    *   MATERIALDATA              =
    *      TAXDATA                   = table_tax
    *   WITHTAXDATA               =
    *   VENDORITEMSPLITDATA       =
          RETURN                    = lt_return.
    This works perfectly for me, creating a mir7 document without refering to a PO. The trick here is to fulfill the glaccountingdata importing table while leaving itemdata empty.

  • Standard IDocs for Inbound Sales Invoice

    Hi All,
    Beginner in the forum.
    I have a requirement to develop an IDoc interface for Sales Invoice. I am not sure about the Basic IDoc Type, Message Type and Inbound Function Module to be used.
    I can see Basic Types INVOIC02/01 and Message Type INVOIC. And the Function Modules IDOC_INPUT_INVOIC_FI and IDOC_INPUT_INVOIC_MM assigned in WE57. As my requirement is in SD perspective, I am little confused which one to use.
    Any pointer would be helpful.
    Thanks in Advance,
    Khanshi

    Sales invoices are generated referencing existing orders and deliveries through VF01 or VF04. Most if not all data for creating the invoice comes from the existing order/delivery documents (except may be freight costs etc which are know only during invoice time). So there is no standard IDoc (as most data for creating sales invoice is already there in SAP in the form of reference delivery/order) to create a Sales invoices. Sales invoices created through VF01/VF04 are outbound and can trigger INVOIC message type IDoc through IDOC_OUTPUT_INVOIC which is sent from SAP to the customer for billing purposes.
    The IDOC_INPUT_INVOIC_FI and IDOC_INPUT_INVOIC_MM are for creating inbound vendor FI invoice (like that created by FB60) and MM vendor invoice (like that created by MIRO) respectively.
    If you want to create a sales invoice through BAPI the below modules are available but I am sure there isn't a standard IDoc function to post a inbound INVOIC IDoc to customer/sales invoice. These BAPIs will of course require you to input the reference document (delivery or order) to create the invoice.
    BAPI_BILLINGDOC_CREATE
    BAPI_BILLINGDOC_CREATEFROMDATA
    BAPI_BILLINGDOC_CREATEMULTIPLE
    Best regards,
    Vishnu Tallapragada

  • Invoic inbound IDOC error.Please help!

    Hello:
       When I posted AP document by IDOC triggerred by output RD04 in billing document, this inbound idoc always failed with error message:The transaction was terminated by the user.
      My message type is INVOIC.
      Do you know why this error happened?
    Thanks

    message is "You are not authorized to use Transaction FB01".So I am wondering if the error message "The transaction was terminated by the user" is also caused by authorization problem.
    It seems yes. Why dont you try with proper authorization?
    Reddy

  • Inbound idoc failure(vendor invoice not posted)

    Hi All,
    we have two SAP systems. SAP A and SAP B.
    SAP A is the vendor for SAP B system we have created a sales order/delivery/out bound invoice in SAP A system.The sales order has BOM material with main item and sub items. We have the same material master data and BOM master data in system A and system B since we are following split architecture.
    The outbound invoice(with main and sub item) in system A has generated an outbound idoc and the idoc has gone to SAP
    system B. There are the usual segments like E1EDP01 for main item and another E1EDp01 for the sub itmes in the outbound
    idoc.The message type is INVOIC and basic type INVOIC02 with no extension.
    In system B, the inbound idoc (coming from system A) has failed giving the error message "higher level items not allowed". The
    segment E1EDP01 for sub item is highlighted in red ! basically the inbound idoc in sap system B is posting a vendor
    invoice since the inbound idoc in B is calling the FM IDOC_INPUT_INVOIC_MRM... I think this is doing vendor invoice
    verification.
    I have checked in system A, all is ok and the outbound idoc is ok but the issue is in sap system B, the inbound idoc has failed
    with message "higher level items not allowed". The segment E1EDP01 for sub item is highlighted in red in inbound idoc in
    system B. The segments are the same for inbound idoc in B and outbound idoc in A.
    Can someone pls tell what is wrong in system B.(config or data issue) as we are managing both systems.
    regds

    Hi,
    I am not sure if we can send both main  and sub items thorugh inbound invocie idoc to create vendor invoice.
    you can try to post the idoc by removing main items from the IDoc in WE19.
    one more thing you should aware is you are not allowed to to create two E1EDP01 segements for the same PO item(E1EDP02).
    check this as well.
    Regds,

  • INVOIC Inbound IDOC automatically getting triggered during O/B

    Hi Experts,
          As per the req of our client, we are planning to send the sales invoice details to customer by INVOIC IDOC message type. We mapped the fields and tried to execute the INVOIC.
    During execution we noticed that, when ever one "Outbound" IDOC sent then immediatly another one "Inbound" IDOC is getting generated and its going to an error message.
               For example, INVOIC IDOC message type is getting generated for "Outbound" for the customer partner profile we maintained. Immediatly another one "Inbound" IDOC is getting generated for the "Logical system" (Partner type LS). But for this partner we didnt maintained any "partner profiles" in WE21. Even then one IDOC is getting generated with error.
    Any expert feedback on this will help us to resolve our issue
    Regards,
    Nag

    Better check the BD64 and WE20 settings...
    Check whether inbound is defined for any other partner profile...
    Also in WE21 what is the port that is used which is given as the o/p of the outbound idoc in WE20 config...

  • 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.

  • Inbound IDOC error while processing Invoice

    Hi All,
    I received the following error while processing an Invoice on an inbound IDOC:
    <b>Field BSEG-MEINS - does not exist in the screen SAPMF05A 0300</b>
    Message no. 00349
    <b>Diagnosis</b>
    The specified field does not exist on the screen
    <b>Procedure</b>
    Check your batch input data
    Any assistance will be greatly appreciated.
    Thanks, Inno

    Hi
    Please check which G/L Accounts were involved and verify that the Field BSEG-MEINS was set to 'optional' in Transaction OB14. The correct Field Status Variant
    for the Company Code can be viewed with Transaction OBY6 and the Field
    Status Group for G/L Account can be found with Transaction FS00 under
    the Create/bank/inter Tab. This should eliminate the Error 00 349.
    Regards
    Javier

  • Message type is not populating in the Inbound idoc control record

    Hi,
    I have created an Inbound Idoc function module and have done the necessary Idoc settings. But, while testing in WE19, I observed that control record is not getting populated with message type and it is dumping.
    The settings which I have done in WEDI as follows:
    1. Created Idoc segments with necessary fields and released
    2. Created Idoc type for the segment type
    3. Created message type
    4. Assigned message type to basic type
    5. In the inbound processing settings,
       filled the ALE attributes with the Idoc function module name and input value '0'
    6. Assigned FM to basic type and message type
    7. Created process code and assigned the process code to message type
    Please let me know, the reason for the message type not populating in the control record. Useful answers will be surely rewarded.
    Best Regards,
    Mallika

    Hi,     
    Maintain partner profile (Transaction code WE20) for the message type you defined in WE81 and put your process code in partner profile and check your logical system settings also in transaction SALE.
    Thanks
    Rahul

  • Inbound IDOC basic type HRMD_A07: Why no validation available?

    I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.  
    Filled the following fields in the IDOC segments:
    E1PLOGI
    plvar=01, otype=P, objid=00000001, opera=I
    E1PITYP
    plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
    E1P0000
    pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
    E1PITYP
    plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
    E1P0001
    pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
    Please help me out in case I am missing something. Thanks.

    Additional Info:
    In WE21 at the TRFC Port, it is possible to set this Option:
    Send Only Fields of Selected Segment Version
    The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
    But if we are using an reduced message type, all fields of the newest release are in the segement.
    The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
    But it is never called when createing an material IDOC with BD10.
    Bug or feature?
    Kind regards
    Manuel

Maybe you are looking for