3748927 - [R] Runtime error 'CONVT_NO_NUMBER' during processing in finance posting and cash application apps - SAP S/4HANA Public Cloud Edition

Below runtime error is received when posting in various G/L and cash applications:

'CONVT_NO_NUMBER'. The OData request processing has been abnormally terminated. Analyze the runtime error using Feed Reader in ABAP development tools for Eclipse or using transaction /IWFND/ERROR_LOG or /IWBEP/ERROR_LOG or ST22. Create a support ticket on the application component of the OData service for errors in services delivered by SAP. 

SAP S/4HANA Cloud Public Edition

Apps concerned:

Reprocess Bank Statement

Post Incoming Payments

Post Outgoing Payments

Post General Journal Entries

Clear Outgoing Payments 

Clear G/L Accounts - Manual Clearing

This is a known regression issue which was due to a technical error at code level in the hotfix collection associated with internal conversion between different data types. It was not detected early enough neither by our internal tests nor by the code review performed. SAP intends to enhance our internal test infrastructure and integration tests to prevent occurring that is future.

SAP has created an Emergency Patch which is applied to all systems concerned one-by-one. In case you encounter the error please raise a ticket on the component where the App you receive the error for belongs to.

CONVT_NO_NUMBER, odata, runtime error, ST22, /IWFND/ERROR_LOG, /IWBEP/ERROR_LOG, supplier subledger, customer subledger, on account posting, post to GL, reprocess bank statement, post incoming payments, post outgoing payments, Post General Journal Entries, cash application, abap dump, odata service, finance posting, public cloud , KBA , FI-FIO-GL-TRA-2CL , Transaction Apps (Public Cloud) , Problem