How to clear status "Error in process"?

[Former Member]

Hi All,

I need help to clear the status of my invoice in SRM. The invoice status is "error in process". We checked in backend and reprocessed the IDOC through WE19 instead of BD87 and the invoices are posted now in backend. But the status of the invoices still shows "error in process" in SRM. I do understand that we should not use WE19 and should have processed it through BD87.

I checked in SRM and the enteries exists in BBP_DOCUMENT_TAB table for these invoices, just tried to run CLEAN_REQREQ_UP and BBP_GET_STATUS_2 but no help.

Please help

Thanks, Sachin

[Former Member]

Hi Sachin

i learnt that you were corrected a record via WE19 post via FM. You followed correct .

As standard says that some thing inconsistancy between SRM and ECC thats why it is not clearing the records in DOC tab table.

Are you very sure invoices are posted successfully when you reprocess the data.

Is that happen in production ? or test.

Hope you might run the both jpbs for this one sc manually.

If the invoices are not posted via IDOC, You can do in the backend itself .but you are stating that it was posted successfully.

What was the error message in BD87 with 51 ERORR message?

in your sc may not updated with invoice info right?so far

Thanks

Muthu

[Former Member]

Hi Muthu,

Yes invoice is posted in backend. I think reprocessing IDOC through WE19 is not the right way and thus we have this issue. BD87 is the right way to reprocess the IDOC since WE19 create new IDOC and thus table BBP_DOC_TAB is not get cleared up.

In BD87, the error was temporary (another user processing the PO). I would like to know in such case how will you delete entry from BBP_DOC_TAB table?

Thanks, Sachin

[Former Member]

Hi Sachin

WE19 , We could edit the bad record and reprocess it . in bd87 just post the same data right.

in BBP_document_tab. manually it is not advisable to delete the data.

how many entries you have in BBP_DOCUEMent_tab.

but take sap help and remove.

i also need to do some house keeping in this table. i will update you..

if everything fine . leave it. there is some inconsiatance thats why this table has an enrty and seek a help from sap to delete .

did you do confirmation ?

if you could recreate the problem . you can do in development boxes.

ps:- run clean_reqreq_up for only this backend docuemnt. will see..and run bbp_get_status_2 job.

are you finding difficulty? hope you made payment to vendor too.SAP Note 535765 - Too many entries in BBP_DOCUMENT_TAB

request sap, they may give some zreport to clear this table.

Dont take asty decision. understand clena req job. what it does and analyse te whole record. no worries. u have posted invoice at leg of procuremnent process. it has an entry because of u r idoc failure. why the idoc failed with 51. i wanted to know analyse. then u will understand the fact. we can not blame the system. clean req is a life line of srm system.

update the docuemnt entry in this page. each record has meaning.you will get answer from every one.

thanks

Muth

[Former Member]

please read all below

An IDoc BBPIV is sent if an invoice is released in the BBP system.In the invoice the statuses I1022 "Release granted" and I1017 "In transfer" are set.In addition, for the background job (see below) an entry is written to table BBP_DOCUMENT_TAB.

Unless I1017 is not set again to inactive, all previous operations are not allowed (in particular all changes to the invoice), that is, they are stopped by the program. The sending of the IDOC is checked by the background job CLEAN_REQREQ_UP. The report reads the BBP_DOCUMENT_TAB and makes a RFC (remote function call) per META_GOODSMVT_UPDATECHECK to check the posting of inbound IDocs.If the IDoc is posted successfully (status 53), the BBP invoice receives status I1018 "Transferred to backend".In addition, the entry is deleted in BBP_DOCUMENT_TAB.

If the IDoc is posted incorrectly (status 51, no follow-on document), the status of the invoice is set to I1019 "Transfer failed".The entry in BBP_DOCUMENT_TAB remains as is, that is, the status of the IDOCs in the backend system is still checked by the background job.The sending of the IDOC is checked by the background job CLEAN_REQREQ_UP.If the IDoc has not (yet) arrived in the backend system, the entry also remains as is.

Status I1018 allows to reverse the invoice in the future. In case of status I1019, a deletion is (again) possible.

-

---

-

---

The following must be considered when processing an incorrect IDoc in the backend system:

a) Further process the same IDoc (BD87), instead of copying and correct the IDoc with Transaction WE19 since in the latter case, the background job cannot find the (copied) IDoc and the invoice posted from that. In this case the BBP invoice would remain endlessly in status "incorrect", the entry in BBP_DOCUMENT_TAB would never be deleted and the background job would always make the RFC at every run.In addition the BBP invoice would never receive the status "paid" (see below).

b) If the IDoc cannot be corrected or the error in the backend system cannot be solved, the IDoc remains in status "incorrect".In this case the BBP invoice should be deleted and the entry in BBP_DOCUMENT_TAB should be deleted manually or with a self-written report.

Additional information: As of EBP Release 4.0 or after the implementation of Note 601470 or the import of the relevant Support Package, the entry in BBP_DOCUMENT_TAB is deleted by the program (during the deletion of the invoice). Then the manual deletion is no longer required.

-

---

The following section does not correspondingly apply to the confirmation, but only applies to the invoice.

Status I1020 "paid" is set in the invoice by using the second background job BBP_IV_UPDATE_PAYMENT_STATUS to check the payment status of the follow-on invoice in the FI backend system for all invoices from the selection area.This only occurs for BBP invoices with status I1018 "Transfer to backend". To read the FI documents, META_FI_DOCUMENT_READ_40B is used.

[Former Member]

Hi Sachin

Do you see invoice posted in SRM via SC status or monitor sc status.

may not be

since

Report CLEAN_REQREQ_UP reads table BBP_DOCUMENT_TAB and checks if the relevant follow-on document has been created for an SRM document.

If the follow-on document exists, the object relationships for the SRM document are updated, the status is set, and the relevant entry is deleted from table BBP_DOCUMENT_TAB.

If the follow-on document does not exist, the entry remains in table BBP_DOCUMENT_TAB, where it can be checked again the next time the report is run.

send me your bbp_pd for this sc and invoice in .txt file.

muthu