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

Similar Messages

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

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

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

IDoc error In case of ERS procedure, please enter terms of payment

Hi,
I tried to use BAPI_PO_CREATE1 to post purchase order. However, I encountered this error.
IDoc error In case of ERS procedure, please enter terms of payment
I passed the payment term in IDOC PORDCH. Segment E1BPMEPOHEADER-PMTTRMS has value filled out. This value is passed into the BAPI correctly but for some reasons, it got cleared out in the BAPI. Any ideas or suggestions would be greatly appreciated.
Thanks

Check
BAPI_PO_CREATE1 - E 06 436 In case of account assignment

IDoc Errors in ECC

Hi Experts,
what kind of IDoc Errors can occur in ECC for the scenario :
ECC sending PO to Ariba(E-commerce hub, using third party adapter) and in receiving back Order confirmation from it.
Thank you,
MK

Hi,
This depends on the design and landscape and also Disaster Recovery or High Availability Plan.
some hints:
1. Connection Problem: Because of timeout , unavailability of the Receiver system.
2. Data Problem may cause you the error in IDoC posting [ probably functional/Business Team should look into this]
3. User ID and Password Maintenance - it may hit sometimes
4. If any pre-requisite process is required to process this IDoC, then problem in the pre-requisite process will lead the problem
these all kind of problems you may face..
Rgds , Moorthy

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.

IDoc Error 51 - Make Entry in All Required Fields

hi,
I am using a scenario where an idoc is being posted into an R/3 system from a legacy application. For some reason I keep getting Idoc error 51 (Document not posted).
Once I drill down further, the specific error states "Make entry in all required fields". Have checked to make sure all mandatory fields have been mapped and proper constant values have been specified.
But cannot seem to get rid of the problem. Could anybody help out in determining how else to troubleshoot this and identify the possible cause?
thx,
Manpreet

Manpreet,
What IDoc Type you are trying to post ? One way is debugging the inbound function module using WE19. The second option is talking to a functional consultantor who worked, what fields are needed for that particular IDoc.
I wouldn't care much about whether the IDoc is posted or not because, it is the ABAP ALE/EDI consultant's job to do that. The only way XI Developer is concerned is when it is not posting, ABAPer would tell what's missing.
Hope this info helps.
regards
SKM

File to IDOC - Error Inbound -56

Hi,
I am doing file to Idoc. (CREMAS01).. My scenario in
RWB is successful. But in R/3 it is shwoing IDOC
error :"EDI: Partner profile inbound not available".
I created Partner Profile in R/3(logical name of BS-
sender file). Still is shwoing Error.
Regards,
Mukharji
Message was edited by: Mukharji T

Hi Mukharji,
I hereunder give you the step by step procedure for File to IDOC scenario. Cross check whether you have done all these:-
SLD
1) Create a Product/Software Component
2) Technical System pointing to R/3 system
3) Business System for the above technical system
In the Repository
1) Import the Software component created in the sld
2) Create a namespace,
3) import the idoc and then create sender data type/message type etc and mapping
4) Mapping Rules is depends on the requirement
In the Directory
1) Create a Scenario /import the business system
2) Create Receiver/Interface determination
3) Create communication channels for sender and receiver
4) Sender Agreeement and Receiver Agreement.
Then the file adapter configuration is depend on the input file format.
Also you need to have Logical destionation created in the XI , and the IDX1 entry
In R/3 Port, Partner profiles etc should be created
Have a look into this document~
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
While doing an File -> XI -> IDoc scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you will need a sender agreement for the file.
4. In this configuration note that you will also need a receiver agreement for the IDOC.
For any File -> XI -> IDoc scenario ref:
/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
Hope this helps you.
Regards.
Praveen

Incoming IDOC Error "No batch input data from the screen SAPMV45A 4001"

Hello ,
The Incoming IDOC with Message type 'ORDERS' is triggering the error message "No batch input data from the screen SAPMV45A 4001" with message no 00344 . There is an SAP note 785000 to handle this type of error message which has been already implemented. Still we are encountering few IDOC error's at the time of sales order creation. The IDOC reaches status 51 throwing the error which is again reprocessed through BD87 .
We are unable to replicate the similar scenerio in Development & Testing systems as it works fine.
Can any one kindly advise how to eliminate the error "No batch input data from the screen SAPMV45A 4001" message at the time of Incoming IDOC processing.
Thanks in advance.
Best Regards
Sateesh

Dear Sateesh
Check this link where the same topic was discussed
[ VA01/VA02: batch-input error in IDoc processing|http://www.sapfans.com/forums/viewtopic.php?f=21&t=313032]
thanks
G. Lakshmipathi

IDOC error while receiving

Hi Friends,
In my scenario, I have to receive P.O. message from partner in to my R/3 system.
I am using PI 7.1
When partner is sending me message I am getting error , "Only asynchronous processing supported for IDoc adapter outbound processg" in SXMB_MONI
I tried to find solution on sdn, and I got 2 related foroum,
Idoc Error
Re: No receiver could be determined. (File to Idoc)
But from this also I am not sure hw can i solve this error.
Please Suggest.
Thanks & Regards,
Brijesh Soni

Hi
For Error Only asynchronous processing supported for IDoc adapter outbound
IDOC adapter support asynchronous only,
Check Quality of Service in your sender adapter. Should be EO or EOIO, not BE.
This thread had same problem and resolved :
Re: No receiver could be determined. (File to Idoc)
In Your case QOS is BE. Plz check in your CC if and BE is by default..
If you use BE, HTTP expects a Response back and as IDOC does not support BE, you go the earlier error.
http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 21, 2009 3:14 PM

Thousands of IDOC Errors

Hi there,
I have recently configured workflow using SWU3 - Now suddenly there are about 10 000 new work items in everyones inbox - All related to IDOC errors.
I have made sure that the workflow administrator is set to a specific user, and in WE46, the IDOC administrator is also set.
Most of the wor-items are back-dated to about a year ago, way before the workflow was configured.
Firstly, why are all these appearing now?
Secondly, how can I get rid of them, or at least isolate them into only one persons inbox?
This is on our test system, so there is no need to investigate any idoc errors...

This is happening because you have made some program run in background while configuring SWU3 most probably the deadline program.
You can get rid of them by checking the Workflow Log and then investigating from where agents are getting determined and accordingly changing the agents to a particular user Id.
Reward points if useful

IDOC Error V1 042 - Sales document X is currently being processed by user X

Hello Experts,
I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
I added a couple of minutes of wait time between the file processing but that did not help.
Please let me know if you have faces same situation and what solution did you apply.
Regards,
PS

Hopefully you have fixed this by now, but for anyone else who might be looking at this problem. We had this problem and we had the 2 programs check to see if the other was already runing. If so the program would submit itself for a number of minutes, different for both programs, and then exit. We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit. This was necessary because re-scheduling could put a program in conflict with itself. I hope that this may help someone. We used the join V_OP and searched for the program name, not the job name.
Kevin

IDOC error in production server

Hi everyone,
I'm getting this error, when users trigger an Idoc:
Error while writing IDoc to file
Message no. EA084
Diagnosis
The IDoc was to be written to file
cocca3301\interface\output_idocs\1120549.txt
That was not possible because no authorization for writing to this file.
Procedure
Please inform your system administration.
Anyone has seen this before? in development and quality servers didn't happen this...
Thanks in advance. Helpful answers will be rewarded.

Not at all, I was talking with basis administrators about this problem for a long time. I'm pretty sure that it's all about folder permission. I think it's a matter of system, not SAP. But they said that's not the problem... I'm not 100% confident with that answer.
But, in order to keep idocs running, i found program RBDAGAIN, that reprocess the failed idocs. I put it into a job every 30 minutes. That solves my problem "temporary", until i solve the real problem.
I advice you to talk with your system administrator and/or basis, and check the group permission for the folder you are trying to put your files. If it works, please let me know.

Missing IDoc and recurring IDoc errors

Hi,
I would like to ask for a help or any ideas on below case.
We encountered almost everyday a number of generated IDoc errors and the number increases everyday. All of these IDocs has Status "51" (application document not posted) and description "EDI: IDoc 63120 does not exist, please check data".
This IDoc errors does not happen before. It only started when the IDoc 63120 was missing and we can't find it already. We don't know why this is missing and we really need to get rid of these recurring IDoc errors whcih increases almost everyday.
Your response will be helpful in solving my problem.
Thanks in advance!

Hi Juan Francisco Zurita Duque
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
Use
Sold-to party number sent in by the customer in delivery schedules.
Use
The system uses this number to automatically determine the ship-to party.
Every thing good for ORDRE05 IN ECC6.0
Check your config settign related to Message type and idoc type.....once again.....
RR

INVOIC02 Idoc error ME708

Similar Messages

Maybe you are looking for