Posting by IDOC_INPUT_INVOIC_MRM

Hi All,
We want to add 2 line items to the posting done by
IDOC_INPUT_INVOIC_MRM in the same way that we do by MIRO in tab 'G/L account', one line item will be the a debit to the purchasing account and the other one credit to the Reflection account both with the same amount. Do you know which structures in the idoc shoul be filled?. I am not expert with idocs however if you have documentation of how the structures should be filled for this specific case will be helpful.
The idoc has this setting
Direction         2
Basic type        INVOIC01
Extension
Message type      INVOIC
Partner no.       448737
Partn.Type        LI
Port              SAPX1C
Many thanks in advance.
Edited by: Miguel Torres on Jul 24, 2008 7:01 AM

Hi,
Many thanks for your quick response, for me this is enough I will contact to the developer.
I would like to share also the information from SAP.
Hi Ms. F. Finance
This functionality is not available as standard. However, from release
470, you can use customer exit CUSTOMER_FUNCTION_15 for
direct posting to the G/L account or material account.
Please have a look at attached note 427137.
So I think that we need to add this information using this exit. I will try and let you know the result.
Thanks again.

Similar Messages

Using MRM_INVOICE_CHANGE

Hi All,
Can anybody please explain me the usage of the function module MRM_INVOICE_CHANGE ? I want to change the Detail\Header text (Field : BKTXT) of an invoice after invoice is created.
I am passing the parameter I_AKTTYP = 'V', and passing the header data to C_RBKPV. What should be passed to the parameter FCODE ? What ever fields I am passing, Its giving error "The field <field name> Cannot be changed.-" during syntax check.
Please Help.
--Krishna

Hi Christian,
     Thank you for your reply.
     My doubt is with regards to MM invoices through EDI. IDOCs are posted using IDOC_INPUT_INVOIC_MRM and after the processing the detail\header text need to be changed depending on blocking reasons..
    I was using a user exit just before document save, but after that the header text is geting cleared.
Regards,
Krishna

Post non PO invoice line items using INVOIC01 and FM IDOC_INPUT_INVOIC_MRM

hello there SAP folks,
Have an interesting question for all of you. We currently have a partner through whom we use the IDOC_INPUT_INVOIC_MRM Function module to pass invoices. Now there are multiple line items some times [multi E1EDP01 / E1EDP02] segments which all refer to the same PO but to different line items on the PO. Now all that is well.
For one particular partner we now have the following requirement. We are going to have the same condition as above, with the added condition that there are going to be some invoice line items with no reference to a PO. the reason is that the vendor is going to calculate the different taxes and send them to us. so when we post the invoice :
we will now have
31 Vendor
40 GR/IR
40 Tax 1
40 Tax 2
50 Tax 3 offset
instead of
31 vendor
40 GR/IR
to deal with the new situation I tried adding having the following
first E1EDP02 is going to refer to the PO using qualifier 001, but second E1EDP02 [for tax] s not going to have a qualifier 001. When I do that i get a missing belnr (001) and zeile (001) error.the exact error message is the following
Required field BELNR(001) is missing in segment E1EDP02
Required field ZEILE(001) is missing in segment E1EDP02
Message no. FD070
Now to bypass that, I added the 001 qualifier for the second E1EDP02 [tax part] and now the error that I get is either the PO is duplicated or if i put some dummy PO number, then it says PO cannot be found.
=======
so the question is how is it possible to post 4 items in the idoc , with one being a PO reference and 3 non PO reference using INVOIC01 and IDOC_INPUT_INVOIC_MRM
I also have to add that it is possible to add a non PO items to the MM invoice in MIRO by entering the additional tax lines using the g/l account tab next to the PO reference tab.

nvm.
Edited by: D N on Dec 16, 2008 2:10 PM

Incoming invoice post via INVOIC01 (IDOC_INPUT_INVOIC_MRM)

Dear all,
We are trying to post an incoming supplier invoice against a PO via IDOC INVOIC01 (IDOC_INPUT_INVOIC_MRM).
We were able to identify all technically required fields to post the invoice.
However, we have some difficulties:
1). How can we enrich the text field which is in the header of the MM invoice ? (transaction MIR4, tab Basic data, field "text")
2). In the FI document (BSEG/BKPF table; FI document that can be viewed through transaction FB03), there are fields like XREF1, XREF2 and XREF3, is there any possibility to have these fields filled through the IDOC?
Many thanks in advance!
Best regards

Option #1 is to use INVOIC01. The configuration for INVOIC01 is present in the standard system for MM invoices through ECC 6.0.
Option #2 is to add the ALE config to allow use of INVOIC02 with IDOC_INPUT_INVOIC_MRM. We have just done this ourselves because we want to use the same IDoc for both our FI and MM invoices, and it seems to be working OK thus far. The configuration to use INVOIC02 for MM invoices is not in the default system up through ECC 6.0.
To do option #2, call transaction WE57 - "IDoc: Assigment of Function Module to Logical Message and IDoc Type"
You will need authorizations to assign a package to this -- it is transportable config.
Function module: IDOC_INPUT_INVOIC_MRM
Function type: Function module
Basic type: INVOIC02
Message Type: INVOIC
Message Variant: MM
Object Type: BUS2081
Direction: Inbound
Description: Invoice/Billing Document
Name: Incoming Invoice
(This is a copy of the default config for INVOIC01, changing the IDoc type to INVOIC02.)
Save, assign to the appropriate package for transport. This configuration is cross-client, so do it once in your development client and it's active in all clients on that instance.
And that's it! Do everything else the same as you would with INVOIC01. (Just keep in mind that not all of the segments you use for FI invoices work exactly the same way in MM invoices -- some of the segment qualifiers are different despite trying to define the same business fields...)
--Dan King
SAP NetWeaver Integration Architect
Capgemini

Planned delivery cost posting in MIRO through IDOC_INPUT_INVOIC_MRM

Hi Experts
I came to know from the OSS Note 119092 that the planned delivery costs can not be posted for logistics(MM) incoming invoice throgh inbounf Function Module IDOC_INPUT_INVOIC_MRM.
I just want to know whether this problem is rectified in ECC 6.0 or still this problem exists?
Awaiting for your earliest response.
Regards
Mohamed

Hi,
There is a modification note that is released.
1386272 EDI: Planned delivery costs..
If you require this functionality please raise a message with SAP..
Since this is a Pilot note release for few customers.
regards,
Lalita

IDOC_INPUT_INVOIC_MRM posting date

Hi,
I have a SD invoice which as an IDOC message IDOC_INPUT_INVOIC_MRM.
This IDOC posts an Invoice in transaction MIR4.
My problem is the SD Invoice date is not transferred to MM invoice date (posting date).
For example I have SD Invoice date: 01/11/2009 but the IDOC creates the MM invoice with posting date equal to actual date (date for IDOC processing).
Do you Know how can I manipulate this date?
I tried to manipulate in IDOC segments but I couldn't.
Thanks,
SF

I have the user exit ZXEDFU02 and ZXM08U22.
But my problem is how to manipulate this date?
Because in transaction WE19 when I see the dates in segment I don´t see any date = 04.11.2009.
I tried to manipulate all dates that appear in WE19 and anyone intgrates in MM posting date.
Thanks,
SF

Error getting while posting an Invoice.

Hi Experts,
I am getting the required purchase order data from the third party system. PI person is picking the data from the third party system and formating in the segments of IDOC format.
I am picking the data and using the standard FM "CALL FUNCTION 'IDOC_INPUT_INVOIC_MRM'" and posting the Invoice in ECC 6.0 System.
But i am getting an error message "Price too low (below tolerance limit of 50.00 CAD )" . I had a discussion with my Functional MM consultant, but they were able to process an invoice for the PO and also reversed the same.
Please help, if i am trying to do through IDOC method, it is not able to post the invoice but getting an error "Price too low (below tolerance limit of 50.00 CAD )" .
Thanks
Sunil Kumar

Hi Chintan,
But when my functional consultant was able to process same PO, by using the MIRO transaction and he was able reversal the same Invoice..
The Functional Consultant gave me the amount and input details.. (He was able to using the standard transaction MIRO) Which i am hardcoding through the segments which are mandatory.
When i try to do it through the IDOC process, where i am currently hardcording few values in the segments in we19 transaction and execute the same.
Please let me know if there is any other process.
Thanks
Sunil Kumar

Generate 2 line items with posting keys in same table while using FM .

Dear Expert ,
For T-code f-65 ,I have to park a FI Document .i tried with PRELIMINARY_POSTING_FB01 for parked Document . But i am not successfully park the document .
with the help of F-65 the data Segregate between Tables VBSEGS and VBSEGD with respecting Posting key . but with this Fm entire entry is displaying in table VBSEGS .For example it generated two line items with posting keys '15' and '40' and these both are displayed in VBSEGS whereas posting key '15' has to be displayed in VBSEGD.
when i check this Document in FBV0 Error reflect " G/L Account 0012000 1001 Does not Exist ".
Here my code -
DATA:   XT_BKPF LIKE BKPF OCCURS 0 WITH HEADER LINE ,
        XT_BSEG LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEG1 LIKE BSEG OCCURS 0 WITH HEADER LINE ,
        XT_BSEC LIKE BSEC OCCURS 0 WITH HEADER LINE ,
        XT_BSET LIKE BSET OCCURS 0 WITH HEADER LINE ,
        XT_BSEZ LIKE BSEZ OCCURS 0 WITH HEADER LINE ,
        XT_BKORM LIKE BKORM OCCURS 0 WITH HEADER LINE ,
        XT_THEAD LIKE THEAD OCCURS 0 WITH HEADER LINE ,
        XT_SPLTTAB LIKE ACSPLT OCCURS 0 WITH HEADER LINE ,
        XT_SPLTWT LIKE WITH_ITEMX OCCURS 0 WITH HEADER LINE .
DATA :    XTEXT_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XTEXT_ITEM_UPDATE LIKE BOOLE-BOOLE VALUE SPACE,
          XI_UF05A LIKE UF05A,
          XI_XCMPL TYPE XFELD VALUE 'X',
          XFS006_FB01 LIKE FS006 ,
          XI_TCODE LIKE T020-TCODE VALUE 'F-65',
          XI_PARGB LIKE RF05A-PARGB        ,
          XI_TCODE_INT TYPE TCODE           .
DATA P_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
XT_BKPF-BUKRS     =     'CP01'.
XT_BKPF-GJAHR     =     2011.
XT_BKPF-BLART     =     'DZ'.
XT_BKPF-BLDAT     =     SY-DATUM.
XT_BKPF-BUDAT     =     SY-DATUM.
XT_BKPF-MONAT     =     '06'.
XT_BKPF-CPUDT     =     SY-DATUM.
XT_BKPF-WWERT     = SY-DATUM.
XT_BKPF-USNAM     =     'ABAPER'.
XT_BKPF-TCODE     =     'F-65'.
APPEND XT_BKPF.
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '001'.
XT_BSEG-BSCHL = '40'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'S' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = '241000'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
Vendor line item - required even for header only - BSEG table
XT_BSEG-BUKRS     =     'CP01'.
XT_BSEG-GJAHR     =     '2011'.
XT_BSEG-BUZEI = '002'.
XT_BSEG-BSCHL = '15'.
XT_BSEG-KOART = 'S'.
XT_BSEG-SHKZG = 'H' .
XT_BSEG-GSBER     =     'CPLN'.
XT_BSEG-BUPLA = 'CP01'.
XT_BSEG-WRBTR     =     10000.
XT_BSEG-PSWSL = 'INR'.
XT_BSEG-ZUONR = 'CH. 123456'.
XT_BSEG-HKONT = 'PC04000001'.
APPEND XT_BSEG .
CLEAR XT_BSEG.
CALL FUNCTION 'PRELIMINARY_POSTING_FB01'
   EXPORTING
     TEXT_UPDATE            = XTEXT_UPDATE
     TEXT_ITEM_UPDATE       = XTEXT_ITEM_UPDATE
I_UF05A                =
     I_XCMPL                = XI_XCMPL
FS006_FB01             =
      I_TCODE                = XI_TCODE
I_PARGB                =
I_TCODE_INT            =
IMPORTING
    XEPBBP                 = CHECK_A
    TABLES
      T_BKPF                 = XT_BKPF
      T_BSEG                 = XT_BSEG
      T_BSEC                 = XT_BSEC
      T_BSET                 = XT_BSET
      T_BSEZ                 = XT_BSEZ
T_BKORM                =
T_THEAD                =
T_SPLTTAB              =
T_SPLTWT               =
          EXCEPTIONS
            ERROR_MESSAGE = 1.
P_RETURN-ID         = SY-MSGID.
P_RETURN-TYPE       = SY-MSGTY.
P_RETURN-NUMBER     = SY-MSGNO.
APPEND P_RETURN.
     p_return-MESSAGE_V1 = XSYMSGV.
IF SY-SUBRC = 0.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = 'X'.
ENDIF.
WRITE :/ sy-subrc , sy-MSGV1 .
Thanks ,
Ashish Gupta

Hi Raghuram,
I found a very important SAP Note 103051, details are below.
An IDoc processed by function module IDOC_INPUT_INVOIC_MM (of category INVOIC01) must not refer to the same purchase order item in several invoice items. This is also valid if for a goods receipt-related invoice verification several delivery notes belong to the same purchase order item.
Depending on the system settings and the situation, various error messages can occur (for example, FD240 'Order item ... selected more than once' or M8050 'Balance not zero: & debits: & credits: &').
In this situation module IDOC_INPUT_INVOIC_MRM generates error message M8321 'Document contains same order item more than once'.
For example, this situation occurs if you work with individual batch valuation and the SD billing document executes a batch split for different batches which belong to the same purchase order item and delivery.
Other terms
INVOIC, SAPLIEDI, M8047, M8, 321
Reason and Prerequisites
This is because of the program design.
Solution
There is no solution for IDOC_INPUT_INVOIC_MM.
Module IDOC_INPUT_INVOIC_MRM (only as of Release 4.0) for the logistics invoice verification can distinguish different goods receipts by means of the delivery note number. For this purpose, GR-related invoice verification must be active.
Owing to this symptom, billing documents for single batch valuation with batch split cannot be settled in MM-EDI inbound processing. The settlement generates exactly the situation described (several invoice items for the same purchase order item). In this case, the only solution is to deactivate the billing of the batch sub-items in SD Customizing and to calculate the main item only.
Hope this helps.
Reward if helpful.
Thanks

Validation of vendor material number in IDOC_INPUT_INVOIC_MRM

Hi folks,
Scenario: Inbound EDI vendor invoices received as IDOCs.
I'm using Logistics Invoice Verification process code INVL to receive and post vendor invoices on to the ERP2004 release of R/3.
I have purchasing info records setup with the vendor material number.
When I process an inbound vendor invoice, I can put in a customer material number i.e. a material number existing in material master in E1EDP19-IDTNR with qualifier E1EDP19-QUALF = 001. When I do this, R/3 checks that the material number is valid and refuses to post an invoice if the material number is invalid - this is good.
This means that the EDI program parameters with the 'Check Material Number' enabled is working as expected.
Now when I only have a vendor material number i.e. E1EDP19-QUALF = 002 an E1EDP19-IDTNR = vendor part number, R/3 posts the invoice even if the vendor part number is invalid - IDOC_INPUT_INVOIC_MRM does not seem to be validating the vendor part number. The document posts whether I use a valid vendor part number or an invalid one - what am I missing?
Satish

I can answer by words of Axel Angeli - top level SAP R/3 consultant and R/3 cross-application development coach, the author of classic book "SAP R/3 Guide to EDI, ALE and Interfaces":
"SAP R/3 delivers a serious of predefined EDI programs. Many project administrators see them as standards which should not be manipulated or modified. The truth is, that these IDoc processing functions are recommendations and example routines, which can be replaced by own routines in customizing."
and
"SAP R/3 is delivered with a series of predefined IDoc types and corresponding handler function modules.
Some of the handler programs have been designed with user-exits where a developer can implement some data post-processing or add additional information to an IDoc.
You must always see those programs as examples for IDoc handling. If the programs already do what you want, it is just fine. But you should never stick to those programs too long, if you need different data to be sent."
So now you can feel free to customize
Regards,
Maxim.

Posting Program for Incoming Invoice

Hello,
I have a requirement to develop an Inbound Interface for Incoming Vendor Invoice which needs to be posted into SAP. Is IDOC_INPUT_INVOIC_MM the Posting Function Module which is used for this Purpose? Or do I need to develop a Custom Posting Program for Posting Invoices in MIRO? Please suggest the available BAPIs & FMs for MIRO Transaction if I need to go for a Custom Development.
Thanks,
Venkata Phani Prasad K.

Hi,
The posting program for Posting an Vendor Invoice is IDOC_INPUT_INVOIC_MRM which is associated with the process code INVL.
I have used the above FM only to post the Vendor invoice idocs and it was successful.
Thanks,
Mahesh.

Invoice Type not being Updated while Posting INVOIC01 - Incoming Invoice

Hello,
I am trying to Post Incoming Vendor Invoice in to SAP using INVOIC01 and IDOC_INPUT_INVOIC_MRM Function Module. I am adding values INVO for Invoice, CRMO for Credit Memo in the Field E1EDK01-BSART to Post the Invoice with different Invoice Types. However, the Invoice for the PO gets Posted only as Invoice, no matter what I populate in the Segment Field E1EDK01-BSART. What could be the issue? Please let me know.
Thank You,
Venkata Phani Prasad K.

This issue has been Resolved. A Sub routine MRM_DOCUMENT_COMPLETE is called in the Function Module IDOC_INPUT_INVOIC_MRM in which the value of the USING Parameter MRM_RBKPV-TCODE is being hard coded to MR1M. Since I am using a Z-Version of this Function Module, I've changed the value of the above field to MIRO after the Subroutine call which solved the issue.
MRM_RBKPV-TCODE = 'MIRO'.
The Values to be Passed to the Field BSART in the Segment E1EDK01 are
E1EDK01-BSART = 'INVL' - For Invoice
E1EDK01-BSART = 'CRME' - For Credit Memo
Thanks,
Venkata Phani Prasad K

Generated EDI message when the invoice is posted.

Hi!!!,
We are implementing a process to receive electronic invoice, we are using the FM. IDOC_INPUT_INVOIC_MRM to process the IDOC with the invoice, so we need to confirm the reception of the invoice using an output idoc when the invoice is post. Anybody know some way to customizing this confirming message using EDI? we would like to send the message when the invoice is posted (we need to use IDOC to send the confirmation)
Thanks for your help!!!

Hi,
How you are creating invoice?
Creating based on data coming from Idoc or sending Invoice data as Idoc.
please elaborate.
Regards,
Bhavana.

Prevent withholding tax posting within EDI

We currently use extended withholding tax and have been for some time. We wish to start posting invoices via EDI idoc processing. Withholding tax should not be posted on all invoices for a vendor based on the type of purchase. For example, this is dependant on whether a good or service is purchased. These would all be purchase order invoices. Is there a way to automatically determine whether WT posting occur at invoice posting? I've not found any way to config/setup the PO influence this WT posting automatically based on this type of purchase.

Hi William,
I would suggest you ask your abaper to put in a code by specifying that, if it is a purchase order invoice, don't use WT. For instance, in my personal case, I wanted all edi invoices to post to invoicing party(PI) so I had our abaper put in a code for us which works perfectly.
Just to add, the code was written into this function module: IDOC_INPUT_INVOIC_MRM I don't know if you're using the same though.
Regards,
Elias
Edited by: Elias Akorli on Mar 25, 2010 10:13 AM

IDOCs processing - MM or FI invoice - if docum is complete- post else park

Hello,
i load xml file into idoc (edi_data_incoming) - in the file are MM and FI invoices. But now i need to process these idocs. If idoc could be posted (idoc has every mandatory data) then post idoc else park document. I need to know how to check (decide) when i can post document and when park. For posting i would use these FM:
IDOC_INPUT_INVOIC_FI
IDOC_INPUT_INVOIC_MRM.
1)Do these FM have any simulation of posting? Then i am able to decide when should i post and when should i only park document.
2)what FM use for parking MM and FI invocices - IDOCs?
What is your idea?
Thanks

check and apply SAP Note 501524

How to park the invoice using 'IDOC_INPUT_INVOIC_MRM' ....

Hi All,
I am using FM 'IDOC_INPUT_INVOIC_MRM' for parking the incoming (Idoc) invoices.
But FM   IDOC_INPUT_INVOIC_MRM   directly posts the invoices. I think is by default from SAP.(not sure)
Can you Pls help me on this issue.
Thanks.

Thanks for ur help
g_fl_adspc_park_document = A will park the document
g_fl_adspc_park_document = 5 will post the document
I have few questions.
1. The status variable 'i_rbstat_new' is not exported in the Standard SAP code. It will be difficult to change.
   Is there any NOTE?
Include:LMRMHF1E
----- Aufruf Create-Baustein zur Erzeugung des Rechnungsbelegs -
CALL FUNCTION 'MRM_INVOICE_CREATE'
       EXPORTING
            i_rbkpv               = i_rbkpv
            i_edi_korrkz          = i_korrkz
            i_fix_payment_terms   = f_fix_payment_terms
            i_fix_quantity_amount = 'X'
            i_transfer_price      = e_transfer_price
       IMPORTING
            e_belnr               = e_belnr
            e_gjahr               = e_gjahr
       TABLES
            t_frseg               = t_frseg
       EXCEPTIONS
            error_message         = 4
            OTHERS                = 8.
2. In FM 'MRM_INVOICE_CREATE' i_rbstat_new is by default 5.
    I think we need to set the status to 'A' in FM 'MRM_INVOICE_CREATE' .
    Can you sugest any function exit.
Thank you....

Posting by IDOC_INPUT_INVOIC_MRM

Similar Messages

Maybe you are looking for