Debugging tips and tricks for analysing error messages in the SD-FI interface

To investigate the root cause of error messages in the process of releaseing an invoice to accounting the following blog entries could be useful for FI experts as well:

Error message F5 704 “Inconsistent amounts”

http://scn.sap.com/community/erp/sd/billing/blog/2013/09/02/debugging-tips-how-to-analyze-error-message-f5-704

Error message F5A 190 “Enter a business place under “Basic data”

http://scn.sap.com/community/erp/sd/billing/blog/2013/09/03/debugging-tips-error-message-f5a-190-enter-a-business-place-under-basic-data

Error message FF793 “SYST: Tax jurisdiction code at lowest level not transferred”

http://scn.sap.com/community/erp/sd/billing/blog/2013/09/03/debugging-tips-error-message-ff793–syst-tax-jurisdiction-code-at-lowest-level-not-transferred

Error message F5 351 “Account & & is blocked for posting”

http://scn.sap.com/community/erp/sd/billing/blog/2013/11/21/error-f5-351–why-do-you-need-the-sold-to-party-when-releasing-an-invoice-to-accounting

Error message KM 133 “Currency/valuation type does not exist”

Dangerous Modifications – How to avoid error message KM133?