Comparing INVOIC01 and INVOIC02 IDOCs

Hi All,
In my project, currently INVOIC01 type IDOCs are being used.
There is a requirement to use INVOIC02 type IDOCs instead of INVOIC01 type IDOCs.
To achieve this, I need to compare the structure of INVOIC01 and INVOIC02 IDOCs.Can you please suggest a way of doing this?
Is there a standard SAP tool which can do this?
Any pointers in this regard will be highly appreciated and suitably rewarded.
Regards,
Som S

Som,
I realize this is an old post but thought I'd try.
I'm in a similar situation where I need to understand the differences between invoic01 and invoic02 and I'd like to see how successful you were with your attempt to do a comparison and what differences you found.
Sandra

Similar Messages

INVOIC02 Idoc error ME708

Hi,
I am using IDoc INVOIC02 to create invoices relating to purchase orders. Some of the IDocs are in error with message ME708 e.g. "Item 00001 for purchasing document 4900006028 not selectable". What does this mean? I have tried comparing entries in tables EKKO and EKPO for the affected orders and haven't seen any significant differences.
Many thanks in advance,
Peter

Hi Peter Applestone,
I want of your guidence. This is related to thread INVOIC02 you posted long back. As you are actively working on this i take liberty to post this.
I am also working on this Invoice receipt thru EDI-IDoc. I have configured the same way you have explained below. Those steps were really helpful. But i am always getting the error again and again. The error is:
Customer , Vendor XXXXXXX not known
Message no. FD110
I have tried to trigger IDocs using basic types INVOIC01 and INVOIC02. But all in vain.
Please rush your answer, Peter !!
Cheers
Maruthi
your message----
Re: INVOIC02
1) In OBCA, maintain an external company code for each of the SAP company codes used in table T001. Although the field called "Company code name in the invoice" is a free text field, it must be identical (it is case sensitive too!!) to the value in the Idoc segment E1EDKA1 with qualifier RE.
2) In OBCB, set up a relationship between each SAP company code and the vendor reconciliation account. Specify a goods/services number of *
3) In OBCC, you can maintain additional account assignment details
4) In OBCD, maintain the name of the tax code from the external system and the SAP tax codes - even if you don't need to actually change the values between the systems. Maintain a tax type and rate for each country's tax codes you intend to use. These match up with the values in the Idoc segment E1EDP04.
5) In OBCE, maintain the posting keys and document types for each company code. This is where the invoice document type is taken from. There are some other interesting flags here, such as park document and create a BDC session - I've played around with the parking flag but the invoice was always posted!
Finally, make sure that your partner profile for the external system in WE20 has a process code INVL and calls function module IDOC_INPUT_INVOIC_MRM (as I was initially using INVF!)
Hopes this helps everyone as it took me 3 weeks to work out!!
Peter

Invoice Posting using INVOIC02 Idoc for PO and Non-Po based invoices

Hi All,
We have a problem regarding posting Invoices using Idocs.
We have po and non-po invoices coming frm thirdparty in the form of idoc files.
We need a clarification whether Invoic02 idoc can handle both Po and Non Po Based invoices or threre are seperate idoc types or message types for Po and Non Po Invoices.
Could any one give some inputs on Partner Profiles also for this senario.
Please kindly reply as early as possible.
Regards
Anil Kumar K

Hi
I Got your name from this site.I would be very thankful if you can help me here.I am designing a EDI based invoice LIV.Is it possible to post some charges which are without PO reference but are coming in Vendor Invoices.Is it possible to post these kind of charges with EDI message INOIC01 or we have to post through FI posting.If possible through EDI in which segment of IDOC we will enter these charges with amt.Also is it possible to post credit memo also with EDI
Thanks
Sanjeev

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

INVOIC02 Idoc

Hi,
I am trying to create an invoice linked to a PO using inbound INVOIC02 IDocs.
I am getting an error message "Formatting error in the field BKPF-BLART; see next message". This is puzzling me as BLART does not exist in any segment and there are no further error messages. I have populated the header segment with BSART = "INVO".
In vain, I have tried using output determination to automatically output an INVOIC02 IDoc when I create one manually in MIRO, in the hope I can just change the ports to post it back in with a new ID. I have set up the condition records OK, such that a message entry automatically appears when I create the invoice with the vendor in the condition record. I have set it to process immediately. When I save the invoice, no IDoc gets created (I have done something similar for POs and that works OK). I have even tried using program RSNAST00 to kick it off, but that doesn't do anything either.
Useful answers to either problem will be rewarded. Many thanks in advance,
Peter

The error message is caused by missing EDI configuration. In order to post invoices successfully using inbound INVOIC02 IDocs, it is necessary to maintain configuration using transactions OBCA, OBCB, OBCC, OBCD and OBCE (these can also be accessed through SPRO under Financial Accounting - Accounts Receivable and Accounts Payable - Business Transactions - Incoming Invoices/Credit Memos - EDI).
1) In OBCA, maintain an external company code for each of the SAP company codes used in table T001. Although the field called "Company code name in the invoice" is a free text field, it must be identical (it is case sensitive too!!) to the value in the Idoc segment E1EDKA1 with qualifier RE.
2) In OBCB, set up a relationship between each SAP company code and the vendor reconciliation account. Specify a goods/services number of *
3) In OBCC, you can maintain additional account assignment details
4) In OBCD, maintain the name of the tax code from the external system and the SAP tax codes - even if you don't need to actually change the values between the systems. Maintain a tax type and rate for each country's tax codes you intend to use. These match up with the values in the Idoc segment E1EDP04.
5) In OBCE, maintain the posting keys and document types for each company code. This is where the invoice document type is taken from. There are some other interesting flags here, such as park document and create a BDC session - I've played around with the parking flag but the invoice was always posted!
Finally, make sure that your partner profile for the external system in WE20 has a process code INVL and calls function module IDOC_INPUT_INVOIC_MRM (as I was initially using INVF!)
Hopes this helps everyone as it took me 3 weeks to work out!!
Peter

Mapping of inbound INVOIC02 iDoc Segment to MIRO/MIR7 Header Text? Help!

Hi Experts,
I need to map a field from the inbound INVOIC02 idoc to the header text field. This field is TABLE:INVFO;(Struct)Field:SGTXT as shown in MIR7. I thought that segments E1EDPT1 & E1EDPT2 would map to this field but it is not showing up in the processed invoice. Is there a segment/field in INVOIC02 that maps to this field?
Thanks,
Doug

Hi,
Try like this
Ledger                        Ledger
       EqualS------------OR            EqualS------------OR EqualS------------OR   EqualS------------OR----Not---
Constant(460050)       Constant(471000)          Constant(420600)       Constant(472150)
and   Brand-------
                EqualS--CreateIF-----Target Brand
Constant(75999)
Thanks!

INVOIC02 IDOC E1EDKA1 PARVW value meaning

I checked WE60 documentation and cannot determine what the meaning of
/INVOIC02/IDOC/E1EDKA1/PARVW = "EN"
I am tasked with setting up a new mapping rule and am trying to correlate the IDOC E1EDKA1 vendor numbers to the PO and Invoice values. WE60 has all other PARVW values documented but this one. Is there another way to determine what Invoice field is used to populate this value so I can correlate the data value?

Hi Bryan,
           As far i know the PARVW will not be having value "EN" , the abbrevation of EN is "English" which will be sent in the field /INVOIC02/IDOC/E1EDKA1/SPRAS [Language Key].
           The Values generated in PARVW will be LF or RS , so this seems to be a wrong data entry and you can avoid this.
           For PARVW you also refer this page
[http://help.sap.com/saphelp_di46c2/helpdata/EN/44/f50abfea3b11d194dc0000e83dd751/content.htm]
-Muru

VAT currency code in INVOIC02 idoc

Hi experts,
Anyone know if there are a field in the INVOIC02 idoc where I can specify the currency of the VAT.
If for example we are invoices in EUR and need to report tax in SEK, where in the idoc do I tell the system that my VAT amount are in SEK?
best regards,
Glenn Karlsson

according to the docu, the VAT amount is in document currency
http://help.sap.com/saphelp_di46c2/helpdata/EN/44/f50abfea3b11d194dc0000e83dd751/content.htm
I have heared about this requirement with VAT amount in local currency, however I have not seen a solution yet.
MAybe you should ask SAP directly (dont forget to post the answer here)

AUGRU in INVOIC02 IDOC?

Hello everyone,
I am trying to find a way to identify certain INVOIC02 IDOCs in the middleware based on the order reason (VBAK-AUGRU) of the sales order the invoices (billing documents) were created for. The requirement is to use the standard INVOIC02 IDOC and the standard function module for outbound processing.
When I look at the structure of the INVOIC02 I can see that it has a field AUGRU in segment E1EDK01. The question is now, whether this will have the same content as VBAK-AUGRU.
The obvious thing to do would be of course to just test it in the system, but this is not an option currently.
Thanks for your help,
Thomas

Hi Sharadha,
There is no corresponding fields to map the specified fields. For this you need to extend the standard Idoc and specify these fields in extented version of the Idoc.
I hope this will help you.

How to find the appropriate user exit for invoic02 idoc in idoc_output_invo

Hi all,
I am new to this community p
i have issue regarding the How to find the appropriate user exit for invoic02 idoc in idoc_output_invoic function module.........
thanks,

Hi ,
welcome to SDN.
You can select the appropriate Customer exit accrding to the available parameters .
The list of exits available are
EXIT_SAPLVEDF_001
EXIT_SAPLVEDF_002
EXIT_SAPLVEDF_003
EXIT_SAPLVEDF_004
For Example , if you want to modify the Idoc data(EDIDD) you have to use the EXIT_SAPLVEDF_002. accodingly you can select the user exit according to the avaialable parametres.Use Table MODSAP fto get the Enhancement name.
Hope this Helps
Rgds
Sree
Edited by: Sree on Jul 23, 2010 12:11 PM

Sender and Receiver IDOC config Settings

Guys I have just come up with this document as a quick reference guide to enable me to be able to configure IDOC scenarios quickly and efficiently. Couls you please let me know if this looks ok and all is in the correct order.
Quick Guide to Scenarios
Note A Ports only purpose is to allow either the SAP R/3 Backend system to establish an RFC connection with XI or allow the XI to establish an RFC Connection with the Receiver SAP R/3 system.
Note An RFC Destinations purpose is to: A) Communicate with the SAP system
B) Pull metadata from either the Sender/Receiver SAP R/3 System or another reference system that contains the same IDOC.
Sender IDOC Scenario
When configuring an IDOC Sender adapter there are a few things that you need to configure before you even start with the Config Directory itself.
Because IDOC Adapter resides on the ABAP stack no sender agreement or sender Comm Channel is necessary
Your main configuration is in R/3. You configure R/3 to send the IDOC to XI so hence you dont need an IDOC Adapter or Comm Channel.
1. You need to define an RFC destination to XI in the R/3 Backend system. (SM59). This RFC destination is used to retrieve the IDOC metadata from the sender system. The IDOC adapter needs these metadata to create the corresponding IDOC-XML message from the RFC stream.
2. Assign the destination to a Port in the R/3 Backend system (WE21)
3. Define your Partner Profiles for the IDOC you are trying to send and Reference that Port there as well (WE20)
Based on the above conditions, you do not need a Sender Comm Channel for IDOC or a Sender Agreement for the business scenario. Your only configuration in the Config Directory is to define R/3 as a Business System (no Comm Channel) and define the Receiver Business System along with the Receiver Determination, Interface Determination and Receiver agreement.
I'm not sure if this step is necessary in the sender IDOC scenario -
In XI box you must also define the ports in IDX1 which allows you to establish an RFC connection to pull the metadata in from the backend system, by specifying the RFC destination from where you want to get the info from. This system is defined by the sender port and the client in the IDOC control record. It is either the sender SAP system or an SAP reference system.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Receiver IDOC
When you receive an IDOC things are a little more complex. You do need a Sender agreement and Comm Channel defined. Again there is much to be done in XI and the R/3 Receiver system before you get to the configuration of the Config Directory.
1. In XI you must configure the RFC destination which enables XI to communicate with the Target System (SM59)
2. In XI you must then create the port which allows you to establish an RFC Connection. In this port you define the RFC destination you previously defined. (IDX1)
3. You then must also ensure that a Partner Profile has been established in the Target system which allows XI to send IDOCs to the Target system. (WE20)
Once the above is completed you can then continue to configure your IDOC scenario in the Config directory. In your Receiver Adapter you reference both the Port and RFC destination that you just established along with the Release which is to be the Target systems release. You must also specify an Interface version which again is the Target systems version.
There are certain cases which you also need to use IDX2 (Cache). XI itself does need the IDOC metadata to execute the interface but it can usually use IDX1 to pull this data either from the SAP R/3 system or an equivalent reference system. However if there is already cached metadata and the IDOC has changed then IDX1 will not execute. In this instance you can pull this metadata manually using IDX2 (XI Box).
Apart from the above the rest of the steps in the Config Directory are as normal.
Message was edited by:
 Alex Ong

Hi,
As per my knowledge you need to configure port in IDXI in XI to pull the metadata.
Its a mandatory step to pull the metadata whatever be scenario like whether you are sending an IDoc or receiving an IDoc.
So please configure RFC destination, IDX1 and IDX2 in XI side.
Only after pulling the IDoc metadata you can proceed with any of the IDoc scenario.
Whenever there a IDoc is changed you need to delete the previous metadata and pull it again. In such situations you can use the already existing port in IDX1.
Hope this helps you out.
Thanks and Regards,
Vineetha

INVOIC02 IDoc - data mapping

Does the following attributes exist in the standard INVOIC02 Idoc:
Contract Date
Contract Type
Delivery Date
Shipping Point
Shipping Condintion
Transport Method
Thanks,
Faisal

Please check for the fields in IDOC documentation using Transaction WE60.
Thanks.

How to compare date and time together

Hi,
How to compare Date and Time together?
For example in a database table there are two fields rundate and runtime. I want to compare these two with perticular date and time in the program. Like, I want to pull all the records where the records's date and time are less than a perticular date and time in the program.
Hope the question is clear...
Thanks.
Kavita

Hi Kavita
There is no as such Date and Time Comparision FM in Standard SAP But You can define your own like this
FUNCTION ZAV4_COMPAREDATETIME.
""Lokale Schnittstelle:
*" IMPORTING
*" REFERENCE(DATE1) TYPE DATS
*" REFERENCE(TIME1) TYPE TIMS
*" REFERENCE(DATE2) TYPE DATS
*" REFERENCE(TIME2) TYPE TIMS
*" EXPORTING
*" VALUE(TWOISMORETOPICAL) TYPE C
twoismoretopical = ''.
if date2 > date1.
 twoismoretopical = 'X'.
else.
 if date2 = date1 and time2 > time1.
 twoismoretopical = 'X'.
 endif.
endif.
ENDFUNCTION.
Regards
Mithlesh

HT201320 I have IOS 7 5S and using mail. Receiving works great. Sending mail will not work. Using Centurylink. On my IOS 6 Iphone 4 it works great. Compared settings and they are identical. Now what?

I have IOS 7 5S and using mail. Receiving works great. Sending mail will not work. Using Centurylink. On my IOS 6 Iphone 4 it works great. Compared settings and they are identical. Now what?

Well, this is a recurring issue for many users...a small percentage of users but still a bug. Report the issue here to Apple: www.apple.com/feedback
iOS7.0.3 will be released next week, which as of now, I know is primarily for an iMessage but hopefully it will clear up some of these email issues some are also having.

Differences between rfc and ale/idoc.

hi ..
       will u please send the differences between rfc and ale/idoc's.

Hi,
Please reward with points if helpful................
ALE is SAP proprietary technology that enables data communications between two or more SAP R/3 systems and/or R/3 and external systems. There are three layers in ALE system: application services, distribution services, and communication services.
For communication services, ALE performs a Remote Function Call (RFC) using the port definition and RFC destination specified by the customer model. RFC is used to communicate between applications of different systems in the SAP environment includes connections between SAP systems as well as between SAP systems and non-SAP systems. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system.
Means of creating and operating distributed applications.
The purpose of Application Line Enabling is to guarantee a distributed, but integrated, R/3 installation. This involves business-controlled message exchange with consistent data across loosely linked SAP applications.
Application integration is achieved not via a central database, but via synchronous and asynchronous communication.
Application Link Enabling comprises the following three layers:
application services
distribution services
communication services
Two Development Models
     Distribution using BAPIs
     Distribution using Message type
The programming model "Distribution using message types" contains the definitions of message types and IDoc types and the ABAP code for processing inbound and outbound IDocs.
Defining message types and IDoc types:
If you want to create message type enhancements for master data distribution, you also have to create a new message type for each enhancement.
The ALE interface does not allow you to create different segment data for different IDoc types for the same message type.
Writing ABAP code:
         Outbound Processing
           Inbound Processing
You can find information on other ALE functions under:
                               Master Data Distribution
                              Communicating with Non-R/3 Systems
1. The Remote Function Call facility allows you to call an R/3 Function module on a remote machine.
2. To communicate between two R/3 Systems and also with an External System. External Application program also can call these function module for integration.
3. RFC or sRFC - Synchronous RFC
                 aRFC - Asynchronous RFC
                  tRFC - Transactional RFC
                  qRFC - Queued RFC (I.e. Serialization of tRFC)
Types of RFC Call
Synchronous
CALL FUNCTION Func Destination Dest
CALL FUNCTION func DESTINATION 'NONE' ...
CALL FUNCTION func DESTINATION BACK' ...
Asynchronous
CALL FUNCTION func STARTING NEW TASK taskname
PERFORMING form ON END OF TASK
RECEIVE RESULTS FROM FUNCTION func
Thanks
sivaparvathi

Comparing INVOIC01 and INVOIC02 IDOCs

Similar Messages

Maybe you are looking for