No subsequent document found in Accounting Message no. RW011 - S4HANA CLOUD PUBLIC EDITION

[NL_VBMS58]

Dear experts,

in the starter system, i'm having the following message:

We have created a po with cost center(account assignment K) and into the Delivery tab the 'GR Non Valuated' is not ticked.Then we have also created the good receipt and the invoice but the co document is not appearing, can you help me to understand a solution?

Consider that we are in S4HANA Cloud public edition, because I've read some threads regarding this error but seems that they are referring to S4Hana or ERP (there are some OSS notes), and I assume that are not for S4HANA CLOUD public edition.

Thanks in advance for your help.

Regards,

Nicla

[JulianoRomanato]

Hello niclalavarra.

How are you? I have excluded the Tag "SAP S/4HANA Cloud" and included the Tag "SAP S/4HANA Cloud for Finance" for this question, as Accounting is an Process of Finance Line of Business.

Regards.

Juliano Romanato.

[MartyMcCormick · Accepted solution]

Hi Nicoletta

I think you are going to need to open an incident with SAP to reset the posted invoices to held status, delete all erroneous follow on table entries and then post the invoice again so that the follow on documents will correctly be created.

I would use component MM-FIO-IV.

Thanks,
Marty

[Eric_Yu1 · Accepted solution]

We helped you to accept the answer, since there were no updates after 7 days.

You can unaccept it anytime if you have further questions.

[NL_VBMS58]

Hello Neeraj Jain,

thanks for your suggestion, but I can't apply the resolution described on oss note 2009994 on S4HANA Cloud public edition:

Resolution

1. Execute transaction SE16
2. Enter table RBKP
3. Enter document number and Fiscal Year.
4. Check the value of logical system, field LOGSYS.
5. Execute transaction SE16
6. Enter table T000 and check the logical system maintained for the client.

If there is a change in the logical system please check SAP Note 28958. For documents that were posted before this change it is no longer possible to navigate to the original document or to the accounting documents, this is due to the fact that all document headers have the original logical system that is current at the time of posting. The logical systems (field AWSYS/LOGSYS) in the document headers of all applications involved have to be converted. In addition to this, the document header of the financial accounting document (table BKPF) and all AC applications (such as cost accounting, classic Profit Center Accounting, profitability analysis, Special Purpose Ledgers, Funds Management, etc.) are affected.

If the new General Ledger Accounting is used (Release 5.00 and higher) the logical system is updated in the totals table, this means that relevant adjustments must be made here. A standard solution is not available as an advanced analysis of the affected system has to be made in each individual case and a tailored solution has to be provided.

In the case when the IR document is held (not parked) then there is no entry in PO history and there are no follow-up documents created.

If there aren't any FI documents for a logistic document, then the report ZREPMIR7 (from SAP Note 382797) determines the incorrect documents

1. Running the report with field P_UPDATE as 'blank' only shows a list and no updates are performed. The documents without FI document have an 'X' in the column 'No FI'. This can be used in a test run to find the MM documents that have no follow-on documents.
2. Running the report with field P_UPDATE as 'X' changes the posted MM document to a held document and the entry in the PO history is deleted. The MM document now has the status 'Held' and can be displayed or deleted in MIR4.

There is any other suggestion? Or I'm wrong?

Regards,

Nicla

[Neeraj_Jain1]

Hello nicla,

Please refer below SAP Note. Hope it's clarifies your query.

https://userapps.support.sap.com/sap/support/knowledge/en/2009994

2009994 - RW011 No subsequent document found in accounting

Confirm if it's works for you.

Regards,

Neeraj Jain

[Mers]

Hello, i am getting the same messsage in public cloud. How did you solve the issue?