IDOC_INPUT_INVOIC_MRM or IDOC_INPUT_INVOIC_MM

Which one do you prefer for create invoice like MIRO. Also where can i find an example for these IDOCs structures. ( EDIDD, EDIDC ) .
Thanks

Hi ,
Go to Transaction We02--> execute it will show all Indound and Outbound Idocs..
Expand Inbound idocs and see the EDIDC and EDIDD structures and data.
and generally for MIRO transaction to create Invoice idoc 'IDOC_INPUT_INVOIC_MRM' is used.
Prabhudas

Similar Messages

Inbound for idoc INVOIC

Hi
Can anyone tell me, what inbound function module should be given for Idoc type INVOIC.
Thanks

Hi Niranjana,
Check the function modules IDOC_INPUT_INVOIC_FI,IDOC_INPUT_INVOIC_MRM and IDOC_INPUT_INVOIC_MM
Regards,
Soumya.

ASAP:Doubt in Idoc segment

Hi in the INVOIC idoc in the segment E1EDP19 there is a field called Ktext which specifies idoc short text.From which part of invoice the text is getting populated.Please help

Hi Hema,
Have you checked in the debugging mode in the T-code WE19.
Im not sure which invoice you are referring, but there are 3 process codes INVF, INVL and INVM and inbound function modules IDOC_INPUT_INVOIC_FI, IDOC_INPUT_INVOIC_MRM, and IDOC_INPUT_INVOIC_MM
using this segment E1EDP19.
I'm not sure whether you people have created any custom IDoc and custom FM to post the document.
Hence you can test the idoc number and put the break point in the correct FM as per ur scenario and see how that segment is populating.
I hope this may help u to identify the issue.
Regards,
Naveen Veshala

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

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

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

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

IDOC_INPUT_INVOIC_MRM URGENT ERROR plz help

hello expert im using IDOC_INPUT_INVOIC_MRM to create Idoc.
im facing a problem. the docnum in EDIDC and EDIDD is not generated.
it always equal to 00000000000000 so the program cant create the idoc.
do you have any idea plzz, it s urgent im facing the prob since 3 days.

You should not be calling this FM directly. You should be using the following functions: -
'IDOC_INBOUND_WRITE_TO_DB'
'IDOC_START_INBOUND'
SAP will then use the partner profiles to process the IDoc.

Function module not allowed: IDOC_INPUT_INVOIC_MRM in 4.6C

Hi All,
I am working on SAP 4.6C, I am trying to post an idoc through WE19 and using message type INVOIC and basic type - INVOIC02. Also, we are using the process code - INVL which using the function IDOC_INPUT_INVOIC_MRM.
While trying to post an MM Invoice after entering all the parameters in WE19, the IDoc in status 51.
Also, the error message states that "Function module not allowed: IDOC_INPUT_INVOIC_MRM". Since it is a standard function module, I donu2019t know how to get to solve the problem.
Thanks in advance.
Regards,
Nagarajan

Hi Nagaraju ,
Make Entries in WE57 . To make entries in this Take help of WE42-Inbound process code INVL .If u did not have the entries then it causes this error .After logging ur entry Check in table EDIFCT.
Hope this helps .
Rgds
Sree . M

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

User exit in IDOC_INPUT_INVOIC_MRM?

We are using IDOC_INPUT_INVOIC_MRM to post invoice. Our input idoc will have custom segments where customer purchase order number will be stored. This customer PO number is not equivalent to SAP PO number, but can be related to custom (zz field) in EKKO.
My requirement is to translate this customer PO number to SAP PO number ..
1) Is user exit EXIT_SAPLMRMH_011 a good place to update the E1EDP02 (the appropriate qualifier 001) with the SAP PO number? My only concern in doing it here, we may need to actually tamper with IDOC data and insert segments (so not comfortable with this option)..
2) or have the vendors populate the customer PO number populated in E1EDP02 segment (qualifier 002) instead of custom segment .. And use the same user exit to update the E1EDP02 segment with SAP PO number. This involves modification of IDOC data also (but no insert involved).
the following step in IDOC_INPUT_INVOICE_MRM requires the PO number. Thatz why I want to get the SAP PO number so early and not in later user exits where I can directly update the FRSEG internal tables.
     PERFORM po_data_prefetch
        TABLES idoc_status
               idoc_data
        CHANGING mrm_subrc.
Do you guys think it is the good alternative? or What do you guys think is a better approach? Thank

Option 1 is not too uncommon to do with IDOC user exits. In fact in some of the user exits, we wiped out entire segments and added new ones for some business reasons. So I suggest not to rule out the option 1 entirely. The problem with option 2 is that you are dealing with external entities(your vendors) to provide you with the information. These external entities are not under your control. If you ask even one vendor to change, they may have to go through their own development life cycle and test cycle before even they can provide the information you need. Some influential vendors might even refuse to do it because they may be using the same EDI message program for several of their partners. Thay cannot change it just for your sake. So imagine if you to ask ten vendors to change. That will add more delay to your timeline.
Regards,
Srinivas

Urgent!!!! EDI- Invoice Verification - MRHR( INVL ) - IDOC_INPUT_INVOIC_MRM

Hi all,
I'm facing an error while uploading a EDI format
flat file into SAP.
An Idoc gets generated and the status error message number is 51 : and it tells that IDOC_INPUT_INVOIC_MRM
NOT ALLOWED.
The Basic Type is INVOIC02
The message type is INVOIC
The Process code is INVL
Inside the process code the Identification contains the function module : IDOC_INPUT_INVOIC_MRM
Pls help.

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

BADi or Enhancement Spot in IDOC_INPUT_INVOIC_MRM

Hi,
Can anyone please let me know whether there is any BADI or Enhancement spot in the Function Module: IDOC_INPUT_INVOIC_MRM to change the BKPF-XBLNR (Reference field).
This is used for Inbound Idoc:
Message Type: INVOIC
Basic Type: INVOICE02
Process Code: INVL.
I go the user exit to change but I am looking for BADI or Enhancement Spot.
Thanks and Regards,
Shravan G.

Answered

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

IDOC_INPUT_INVOIC_MRM or IDOC_INPUT_INVOIC_MM

Similar Messages

Maybe you are looking for