cancel
Showing results for 
Search instead for 
Did you mean: 

Error on Parked Logical Invoices

0 Kudos

Hello everyone,

I have a problem with posting logical invoices in a new fiscal year.

Parked logical invoices are getting a hard error when users attempt to process the invoice in the new fiscal year.

Do you have any idea how to make it work?

The last year period is closed, but we still have some parked logical invoices.

I would appreciate any help and advice on this issue.

Thank you very much.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182098
Active Contributor
0 Kudos

Hi,

If I understand correctly, you have parked some logistics invoices in the last year. Now you are trying to post them, but the last fiscal year has been closed. Hence, it cannot be posted in the current fiscal year. The system throwing error. If this is the case, need to change the posting date in the parked invoices and post them in the current year.

If you are still getting error, please let me know the error message number.

Regards,

Ravi

0 Kudos

Thank you very much for fast reply and you understood me correctly. Sorry, not a logical invoices , logistical.

Here is what we did:

1. Document 5105654090 was parked in FY 2008 using transaction MIR7.

2. I pulled up the document using transaction MIR7.

3. I changed the posting date from prior year to the current year.

4. I simulated the posting and received no error messages.

7. I attempted to save the parked document and still received the error

"Message not found in main memory"

Thank you.

former_member182098
Active Contributor
0 Kudos

Hi,

If it is giving some error, please double click on the error showing below.

Then another session gets opened and it will give you a message number.

If you have given current date and trying to post, but still the system is giving error means, the error may not be relating to posting date. It could be something else.

The message number would give a clue to find the solution.

Regards,

Ravi

0 Kudos

Thank you. I'll try.

former_member182098
Active Contributor
0 Kudos

Hello,

Please make sure you have changed the posting date, but not document date. Because document date will not have any relevance for posting the document.

Kindly update me with the error message.

Regards,

Ravi

0 Kudos

Thank you very much for help. I will update you with my progress.

Rimma.

0 Kudos

Hello Ravi,

I've got more details on this issue and it is seems like our have specific process how they handle those parked logistics invoices.

1. The last day of the fiscal year, they closed all existing POs, even parked invoice for theses POs already exist.

2. Rollover those POs to the next fiscal year, using T-code FMJ2 and assign the same PO number.

3. Manually delete parked invoices in the last day of fiscal year.

They think that it is much cleaner do not have any parked logistics POs when new fiscal year starts.

I think they were not able to post it because of POs rollover; it was new POs even with the same PO numbers.

The problem what I am looking to resolve right now:

It can be a situation that AP users will forget to delete parked logistics invoice in the last day of the fiscal year. The system does not allow deleting or canceling them when year starts.

Do you have any idea is it possible to delete old parked logistics invoices in a new fiscal year?

What can be done to accomplish that?

I appreciate your help vey much. I am very new to SAP, so forgive me if some wording or explanation is not that clear,

Sincerely, Rimma.

former_member182098
Active Contributor
0 Kudos

Hi,

I have searched for few SAP notes:

Note 788231 - Deletion of parked documents with archived purchase orders

Note 366965 - MIR4: Changing posting date of parked documents

Note 598018 - MIR4: New document number: Information is lost

Note 801832 - MIR7:Incorrect W/tax info in park doc on fiscal year change.

However, please let me know if still these notes does not solve your issue. I would like to know the exact error message, which helps me check for further solutions available.

Regards,

Ravi