Solved

Posting Proposal Lines Missing After Posting

  • 2 June 2021
  • 5 replies
  • 274 views

Userlevel 6
Badge +10

Hi All,

Do you know any scenario that below could happen.

The Posting Proposal Lines (except for Manual lines) gets deleted from after posting invoice.

Posting Proposal Lines

 

But it appears correctly in invoice postings

Manual Supplier Invoice Postings

 

Thanks

icon

Best answer by Thanushi Jayaweera 9 June 2021, 20:55

View original

This topic has been closed for comments

5 replies

Userlevel 7
Badge +10

Hi @GayanD ,

Does this happen for all  manual supplier invoices and for all users?

Best Regards,

Sachin

Userlevel 6
Badge +10

Hi Sachin,

No only for several invoices with different users.

Userlevel 6
Badge +10

Hi,

I see another invoice which has posting like below.

As I understand the posting lines with 0 amount in invoice currency are not shown in Posting Proposal lines.

 

Posting {roposal

 

Is it the normal behavior?

Thanks

Userlevel 7
Badge +10

Hi @GayanD ,

I was able to observe a similar scenario in core environment as well. The M18 line which was created automatically for the clearance of currency difference is not appearing in posting Proposal.

Invoice

posting Proposal

 

However, in addition to currency difference postings, if other posting lines are also missing, better to raise a support ticket with a specific test plan to replicate a similar invoice. Then we can further investigate and confirm whether this is a bug or not.

 

Best Regards,

Sachin

Userlevel 7
Badge +15

Hi @GayanD ,

I noticed a similar issue reported to RnD via Solution - 279336.

Could you kindly check the below;

1) The purchase order connected to the invoice is in foreign currency and the currency rate in purchase order and in supplier invoice are different?
2) The purchase unit of measure is different than the inventory unit of measure (in the Supplier for Purchase Part window)

If both the above points are true then it seems to be the reason why M18 and M20 postings have been automatically created.

Perhaps bug fix - 152477 will help you resolve it.

Best Regards,
Thanushi