I don’t believe so. I do use those fields on some items but I update them through a csv file import. If I use the strikethrough pricing treatment option then typically MAP will have a lower price than MSRP but I believe the errors are occurring on items where the pricing treatment/MAP exposure are set to “None” and MSRP/MAP are equal.
Next time I see it happen I’ll make a note to check.
I see the same error in the eBay csv file upload I do to update inventory but those fields aren’t in that file.