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

Similar Messages

Idoc INVOIC - error Tax entry not possible in this item - Message no. FF724

Hello,
I have an idoc in error with the following error message.
In the idoc type INVOIC
Segment E1EDK04:
MWSKZ     N1     VAT indicator
MSATZ     19.000     VAT rate
MWSBT     20.52     Value added tax amount
In OBCD
Partn.Type PartnerNo Tax type Tax rate Cty Tx
LI         FNISL     N1       19.000       V2
Input tax N6 is defined in the system with rate 19.000%
Direction         2     Inbox
Current status    51
Basic type        INVOIC01
Extension
Message type      INVOIC
Partner No.       FNISL
Partn.Type        LI
Tax entry not possible in this item
Message no. FF724
Diagnosis
You can not enter a tax amount in this item since, due to the posting amount entered and the tax code, a total tax amount of zero has been calculated.
This could either be due to the fact that the tax code has been defined with a value of 0%, or because the posting amount entered (that is, the tax base) is too small.
Example:
With a tax rate of 15%, a tax amount greater than zero will only be achieved with a base amount greater than 0.04. With values of 0.03 and less, it is therefore not possible to enter a tax amount.
Procedure
Only enter tax amounts in conjunction with tax codes for which a percentage rate not equal to zero has been defined. Make sure that in documents with several G/L account items you enter the total tax amount in an item with a sufficiently high posting amount.
do you have an idea to solve it?
Regards
Arnaud

Message no. FF724
Check note 681538
thanks
G. Lakshmipathi

Inbound idoc with error status 52 messege type hrmd_a07

i have an inbound idoc with status 52
error messege : Object 01 ,P ,00056786 does not exist: infotype 0302 cannot be created
Object 01 ,P ,00056786 does not exist: infotype 0006 cannot be created
i debugged but i haven't find out the reason
am updating 0000,0001,0002,0003,0006 infotypes

Hi rahul,
Need to check the address filed (0006) for BP mapped to postion (00056786)
Infotype 0302 (Additional Actions) :
Infotype 0302 is not maintained directly and is automatically updated by Infotype 0000 .
The additional actions Infotype (0302) is of time constraint 3 (gaps and overlaps).
Specifically in some cases if we want to have a non status-changing Action on the same day where already a personnel action is existing at that time we can activate the Infotype 302 by executing Report RPUEVSUP.
please check and let me know . I think it will be helpfull
Thanks and Regards,
Krishna

Inbound idoc payext error 51 In House Cash

Hi
I have an inbound idoc PAYEXT PEXC with status 51 and error message " No parameters found for: IHC H EUR" Message no. IHC205 ". second error message: "Creation of header data failed msg IHC 196" this error has also status 51.
IHC is the bank area, H is a payment method (cheques) that I do not use in IHC and does not exist in FBZP.
The idoc has basic type PEXR2002. segment 26.
Any hint how to solve or debug?

Hi Sreeram,
I made the configuration for Posting accounts as per your advise. 'Now I am getting another error message as shown below
Creation of individual payment requests failed
Message no. IHC197
Partner number of account type is invalid
Message no. IHC000
What does this mean and what is the remedy for this?
Thanks
Kalyan

Inbound IDOC process error

Hi
While an Inbound is being processed it is not behaving as per the design and if the same type of idoc is reprocessed through BD87 is it behaving as per the design.
In detail, the idoc will create a purchase order based on reservation number in R/3 and the quantity needs to be checked against the availability. If the quantity is more in the idoc counting all line items of idoc segments it should not be posted giving that the quantity is not available. If it is automated it is not checking, but while testing on creation of an inbound idoc and reprocessed the validation is happenning.
So, please help me in understanding as why the idoc is not getting validated when it is automated ans whne it is reprocessed through BD87 it is getting validated.
Thanks
Shankar

Hi Shankar,
how do you notice that your code is not executed.
Usually I would say it should.
Therefore I recommended to implement an infinite loop to make sure that it is really not executed.
By the way...where did you implement your coding?
Best regards,
Oliver
Edited by: Oliver Hütköper on Aug 12, 2011 8:45 AM

Idoc INVOIC error Baseline date for payment does not exist

Dear All,
I am facing the following error message when processing an idoc to do an MM invoice reception (operation similar to a MIRO).
The payment term is correctly maintained in the purchase order.
Idoc message type INVOIC MM.
Baseline date for payment does not exist
Message no. M8356
Diagnosis
You have tried to post a document without a baseline date for payment.
The system will not allow you to do this.
Check the purchase order. No terms of payment have been entered in the document header or no suggestion has been defined in Customizing for the baseline date for payment for the terms of payment entered.
If you get the error message during automatic settlement of planned delivery costs, maintain the term of payment in the master record (Payment Transactions, Financial Accounting) for the freight vendor or use the Business Add-In MRM_ERS_HDAT_MODIFY to determine the term of payment.
Regards
Arnaud

Hello,
Date for starting the calculation of the baseline date is indeed managed in the TC OME2 (document date, posting date, etc..).
In my project, there is already some companies using payment term N60N, so it should be possible to continue using it.
I solved this issue by putting a payment term in the vendors master data (company & purchasing views) and also in the customers views (company / sales orga) otherwise the structure of the idoc is different.
Thanks anyway for your input.
Keep in touch.
Regards
Arnaud

Inbound IDOC processing, error duplicate key

We want to retrieve certain order-idocs in our system, before they are processed, to change AND insert segment data.
Flow we use in our current program
- DOC_STATUS_WRITE_TO_DATABASE
to change the status of the idoc (ok) (status 69)
- EDI_DOCUMENT_OPEN_FOR_EDIT (ok)
- EDI_CHANGE_DATA_SEGMENTS (ok)
- EDI_DOCUMENT_CLOSE_EDIT => not ok
This program gives SAPSQL error
Via debugging, we see that a new idoc number is
called (save as backup idoc ?), but we want the
current IDOC to be processed.
The system wants to insert in EDID4 => dump :
"Use an ABAP/4 Open SQL array insert only if you
are sure that none of the records passed already
exists in the database."
( I prefer to use these standard functions, in stead of just deleting and inserting into "EDID4" )
regards,
answers will be rewarded.
code extract
INCLUDE ZBE01458_TOP.
INITIALIZATION.
V_EDIT_STATUS = '69'.
V_PROCESSED_STATUS = '32'.
start-of-selection.
clear t_edidc. refresh t_edidc.
SELECT * FROM EDIDC into table t_edidc
WHERE DOCNUM in S_docnum
and mestyp in S_mestyp
and idoctp in S_idoctp
and credat in S_credat
and rcvpor in S_rcvpor
and rcvprt in S_rcvprt
and rcvprn in S_rcvprn
and sndpor in S_sndpor
and sndprt in S_sndprt
and sndprn in S_sndprn
and status in S_status.
loop at t_edidc.
move t_edidc-docnum to v_docnum.
refresh v_status.
V_STATUS-docnum = V_DOCNUM.
V_STATUS-status = V_EDIT_STATUS.
clear EDIDS.
select single * from EDIDS where docnum = v_docnum.
if sy-subrc = 0.
MOVE EDIDS-STACOD to V_STATUS-STACOD.
endif .
APPEND V_STATUS.
PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
changing part for DEDIDD "idoc data
PERFORM OPEN_IDOC_FOR_CHANGE.
PERFORM CHANGE_IDOC.
PERFORM CLOSE_IDOC_FOR_CHANGE.
refresh v_status.
V_STATUS-docnum = V_DOCNUM.
V_STATUS-status = V_PROCESSED_STATUS.
APPEND V_STATUS.
PERFORM CHANGE_IDOC_STATUS tables V_STATUS
USING V_DOCNUM.
endloop.
*& Form OPEN_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM OPEN_IDOC_FOR_CHANGE.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
ALREADY_OPEN = 'N'
IMPORTING
IDOC_CONTROL =
TABLES
IDOC_DATA = DEDIDD
EXCEPTIONS
DOCUMENT_FOREIGN_LOCK = 1
DOCUMENT_NOT_EXIST = 2
DOCUMENT_NOT_OPEN = 3
STATUS_IS_UNABLE_FOR_CHANGING = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " OPEN_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC.
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
TABLES
IDOC_CHANGED_DATA_RANGE = DEDIDD
EXCEPTIONS
IDOC_NOT_OPEN = 1
DATA_RECORD_NOT_EXIST = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CHANGE_IDOC
*& Form CLOSE_IDOC_FOR_CHANGE
text
--> p1 text
<-- p2 text
FORM CLOSE_IDOC_FOR_CHANGE.
CLEAR t_EDI_DS40.
t_edi_ds40-docnum = v_docnum.
t_edi_ds40-status = '51'.
t_edi_ds40-repid = sy-repid.
t_edi_ds40-tabnam = 'EDI_DS'.
t_edi_ds40-mandt = sy-mandt.
t_edi_ds40-stamqu = 'SAP'.
t_edi_ds40-stamid = 'B1'.
t_edi_ds40-stamno = '999'.
t_edi_ds40-stapa1 = 'Changes made to idoc ...'.
t_edi_ds40-stapa2 = t_new_kunnr.
t_edi_ds40-logdat = sy-datum.
t_edi_ds40-logtim = sy-uzeit.
APPEND t_edi_ds40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
EXPORTING
DOCUMENT_NUMBER = V_DOCNUM
DO_COMMIT = 'X'
DO_UPDATE = 'X'
WRITE_ALL_STATUS = 'X'
TABLES
STATUS_RECORDS = t_EDI_DS40
EXCEPTIONS
IDOC_NOT_OPEN = 1
DB_ERROR = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CLOSE_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC_STATUS
text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
USING P_DOCNUM.
CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
EXPORTING
IDOC_NUMBER = p_docnum
IDOC_OPENED_FLAG = ' '
NO_DEQUEUE_FLAG = 'X'
IMPORTING
IDOC_CONTROL =
TABLES
IDOC_STATUS = P_IDOC_STATUS
EXCEPTIONS
IDOC_FOREIGN_LOCK = 1
IDOC_NOT_FOUND = 2
IDOC_STATUS_RECORDS_EMPTY = 3
IDOC_STATUS_INVALID = 4
DB_ERROR = 5
OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
else.
commit work.
ENDIF.
ENDFORM. " CHANGE_IDOC_STATUS

Urmila,
I tried this sequence : code extract follows...
I got the duplicate key errors again.
what about delete first and then insert again in EDID4 table ?
source code extract:
INCLUDE ZBE01458_TOP.
INITIALIZATION.
V_EDIT_STATUS = '69'.
V_PROCESSED_STATUS = '32'.
V_SAPCODE = 'SAPE0184'.
start-of-selection.
clear t_edidc. refresh t_edidc.
SELECT * FROM EDIDC into table t_edidc
 WHERE DOCNUM in S_docnum
 and mestyp in S_mestyp
 and idoctp in S_idoctp
 and credat in S_credat
 and rcvpor in S_rcvpor
 and rcvprt in S_rcvprt
 and rcvprn in S_rcvprn
 and sndpor in S_sndpor
 and sndprt in S_sndprt
 and sndprn in S_sndprn
 and status in S_status.
loop at t_edidc.
 move t_edidc-docnum to v_docnum.
 move-corresponding T_EDIDC to WA_EDIDC.
 V_STA-docnum = v_docnum.
 V_STA-status = '51'.
 V_STA-repid = sy-repid.
 V_STA-tabnam = 'EDI_DS'.
 V_STA-mandt = sy-mandt.
 V_STA-stamqu = 'SAP'.
 V_STA-stamid = 'B1'.
 V_STA-stamno = '999'.
 V_STA-stapa1 = 'Changes made to idoc ...'.
t_edi_ds40-stapa2 = t_new_kunnr.
 V_STA-logdat = sy-datum.
 V_STA-logtim = sy-uzeit.
 V_STA-STACOD = V_SAPCODE.
 PERFORM OPEN_FOR_PROCESS.
 PERFORM SET_IDOC_STATUS USING V_DOCNUM V_STA.
 PERFORM CLOSE_IDOC_FOR_PROCESS.
 PERFORM OPEN_IDOC_FOR_CHANGE.
 PERFORM PROCESS_IDOC_STRUCTURE.
 PERFORM CHANGE_IDOC.
 PERFORM CLOSE_IDOC_FOR_CHANGE.
 refresh v_status.
 V_STATUS-docnum = V_DOCNUM.
 V_STATUS-status = V_EDIT_STATUS.
 V_STATUS-STACOD = V_SAPCODE.
 clear EDIDS.
 select single * from EDIDS where docnum = v_docnum.
 if sy-subrc = 0.
 MOVE EDIDS-STACOD to V_STATUS-STACOD.
 endif .
 APPEND V_STATUS.
 PERFORM CHANGE_IDOC_STATUS tables V_STATUS USING V_DOCNUM.
endloop.
*& Form OPEN_IDOC_FOR_CHANGE
 text
--> p1 text
<-- p2 text
FORM OPEN_IDOC_FOR_CHANGE.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
 EXPORTING
 DOCUMENT_NUMBER = V_DOCNUM
ALREADY_OPEN = 'N'
IMPORTING
 IDOC_CONTROL = WA_EDIDC
 TABLES
 IDOC_DATA = DEDIDD
EXCEPTIONS
 DOCUMENT_FOREIGN_LOCK = 1
 DOCUMENT_NOT_EXIST = 2
 DOCUMENT_NOT_OPEN = 3
 STATUS_IS_UNABLE_FOR_CHANGING = 4
 OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " OPEN_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC
 text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC.
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
 TABLES
 IDOC_CHANGED_DATA_RANGE = DEDIDD
 EXCEPTIONS
 IDOC_NOT_OPEN = 1
 DATA_RECORD_NOT_EXIST = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CHANGE_IDOC
*& Form CLOSE_IDOC_FOR_CHANGE
 text
--> p1 text
<-- p2 text
FORM CLOSE_IDOC_FOR_CHANGE.
CLEAR t_EDI_DS40.
t_edi_ds40-docnum = v_docnum.
t_edi_ds40-status = '69'.
t_edi_ds40-repid = sy-repid.
t_edi_ds40-tabnam = 'EDI_DS'.
t_edi_ds40-mandt = sy-mandt.
t_edi_ds40-stamqu = 'SAP'.
t_edi_ds40-stamid = 'B1'.
t_edi_ds40-stamno = '999'.
t_edi_ds40-stapa1 = 'Changes made to idoc ...'.
t_edi_ds40-stapa2 = t_new_kunnr.
t_edi_ds40-logdat = sy-datum.
t_edi_ds40-logtim = sy-uzeit.
APPEND t_edi_ds40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
 EXPORTING
 DOCUMENT_NUMBER = V_DOCNUM
 DO_COMMIT = 'X'
 DO_UPDATE = 'X'
 WRITE_ALL_STATUS = 'X'
 TABLES
 STATUS_RECORDS = t_EDI_DS40
 EXCEPTIONS
 IDOC_NOT_OPEN = 1
 DB_ERROR = 2
 OTHERS = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CLOSE_IDOC_FOR_CHANGE
*& Form CHANGE_IDOC_STATUS
 text
--> p1 text
<-- p2 text
FORM CHANGE_IDOC_STATUS tables P_IDOC_STATUS structure V_IDOC_STATUS
USING P_DOCNUM.
CALL FUNCTION 'IDOC_STATUS_WRITE_TO_DATABASE'
EXPORTING
IDOC_NUMBER = p_docnum
 IDOC_OPENED_FLAG = ' '
 NO_DEQUEUE_FLAG = 'X'
 IMPORTING
 IDOC_CONTROL =
TABLES
IDOC_STATUS = P_IDOC_STATUS
 EXCEPTIONS
 IDOC_FOREIGN_LOCK = 1
 IDOC_NOT_FOUND = 2
 IDOC_STATUS_RECORDS_EMPTY = 3
 IDOC_STATUS_INVALID = 4
 DB_ERROR = 5
 OTHERS = 6
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
else.
 commit work.
ENDIF.
ENDFORM. " CHANGE_IDOC_STATUS
*& Form OPEN_FOR_PROCESS
 text
--> p1 text
<-- p2 text
FORM OPEN_FOR_PROCESS.
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_PROCESS'
 EXPORTING
DB_READ_OPTION = DB_READ
 DOCUMENT_NUMBER = V_DOCNUM
ENQUEUE_OPTION = SYNCHRONOUS
IMPORTING
 IDOC_CONTROL = WA_EDIDC
EXCEPTIONS
DOCUMENT_FOREIGN_LOCK = 1
DOCUMENT_NOT_EXIST = 2
DOCUMENT_NUMBER_INVALID = 3
DOCUMENT_IS_ALREADY_OPEN = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " OPEN_FOR_PROCESS
*& Form SET_IDOC_STATUS
 text
--> p1 text
<-- p2 text
FORM SET_IDOC_STATUS USING P_DOCNUM P_STA.
CALL FUNCTION 'EDI_DOCUMENT_STATUS_SET'
 EXPORTING
 DOCUMENT_NUMBER = P_DOCNUM
 IDOC_STATUS = P_STA
IMPORTING
 IDOC_CONTROL = WA_EDIDC
EXCEPTIONS
DOCUMENT_NUMBER_INVALID = 1
OTHER_FIELDS_INVALID = 2
STATUS_INVALID = 3
OTHERS = 4
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " SET_IDOC_STATUS
*& Form CLOSE_IDOC_FOR_PROCESS
 text
--> p1 text
<-- p2 text
FORM CLOSE_IDOC_FOR_PROCESS.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_PROCESS'
 EXPORTING
 DOCUMENT_NUMBER = V_DOCNUM
BACKGROUND = NO_BACKGROUND
NO_DEQUEUE = ' '
IMPORTING
 IDOC_CONTROL = WA_EDIDC
EXCEPTIONS
DOCUMENT_NOT_OPEN = 1
FAILURE_IN_DB_WRITE = 2
PARAMETER_ERROR = 3
STATUS_SET_MISSING = 4
OTHERS = 5
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " CLOSE_IDOC_FOR_PROCESS

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

Inbound idoc error in 51 Status of at least one serial number of item

Dear Experts,
There is one inbound IDOC which is in error with status 51 showing error Status of at least one serial number of item is not allowed.
Can you please advice why this error is coming.
Thanks & Regards,
Nikhil Kanegaonkar.

An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
Edited by: Krupaji on May 6, 2011 2:38 PM

EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR

Hi,
We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification. When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Status, 51 - No GR documents found.
Is there any way we can process this as a Parked Invoice or for Verification in the background (MIRA)? because the current situation is a problem, as 95% of our Inbound Invoices will be received electronically before the Goods are Received.
The actual Vendor's delivery note is stored in the segment E1EDP02 (Qualifier 016), field BELNR.
Currently the IDOC as to sit in error until the Vendor's Delivery Note is Goods Receipted which can be several days later - SAP OSS Note 393883 fro 2001 suggests doing this, but surely this is a common situation. The IDOC sitting in error in WE02 in the list of IDOCs is difficult to isolate from true errors.
If this is was mnaul Invoice it could be processed through MIRA for background Invoice Verification later with program RMBABG00.
We havd SAP version ECC 6.0
I have spotted OSS Note 501524 which implies that is possible automatically Park Incoming EDI IDOC Invoices, has anyone tried this? and what would be the transaction/program that could be used to post several at once when the GR has been processed (similar to RMBABG00)

Hi ,
You can use the program RBDMANI2 which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
We had the same scenario and we have scheduled this program as a daily job at night .
Regards,
Hari.

Inbound IDOC & Comminication in Nomination

We have a scenario on the Mining industry where we created nomination (T Cd : O4NSN ) for transport of coal by railways . The outbound communication IDOC was successfully sent to a Transport Agency and is reflected in the u201C Communication Tabu201D of the Nomination.
I am getting following issues :
1. Subsequently , the Transporter/railways has send a back a communication via incoming Idoc which fails with following Eror Message : EDI: Partner profile not available
We have tried to create the partner function for processing of Inbound Idoc with following data .
Message type     : OIJ_NOM_COMM
Basic Type     : OIJ_NOM_DETAIL01
Partner Type     : KU
Can you please inform me the approriate Process Code for the inbound IDOC ?
2. Also I have noticed that that During Outbound Communication to the transporter the u201CActionu201D (Communication Tab of Nomination) field idicates as u201C Current Itemu201D. But my understanding is that it should show status : u201C New entry sentu201D .
Can you please guide on how I can define the partner function and resolve these issues .

An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
Edited by: Krupaji on May 6, 2011 2:38 PM

Inbound IDOC error while processing Invoice

Hi All,
I received the following error while processing an Invoice on an inbound IDOC:
Field BSEG-MEINS - does not exist in the screen SAPMF05A 0300
Message no. 00349
Diagnosis
The specified field does not exist on the screen
Procedure
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

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

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

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,

Inbound Idoc[INVOIC[ - Error

Similar Messages

Maybe you are looking for