SAP Knowledge Base Article - Preview

3776354 - ABAP Dump in MIRO when posting Subsequent Debit with non-numeric NF document type

Symptom

An ABAP runtime error (dump) CONVT_NO_NUMBER occurs in transaction MIRO when posting a vendor invoice using the Subsequent Debit transaction type.

The dump occurs with the following details:

Runtime Error: CONVT_NO_NUMBER
ABAP Program: SAPLJ1BI
Application Component: FI-LOC-LO-BR
Function Module: J_1B_NF_IV_REFERENCE_NEW

The issue is triggered when the Nota Fiscal Category used is configured with a non-numeric value (e.g., "D") in the Document Type field (DOCTYP) of the Nota Fiscal customizing (J_1BAA table).


Read more...

Environment

  • SAP S/4HANA
  • SAP ERP
  • Materials Management (MM)
  • Localization Brazil

Product

SAP ERP all versions ; SAP S/4HANA all versions

Keywords

miro, subsequent debit, nota fiscal, brazil localization, convt_no_number, abap dump, j_1b_nf_iv_reference_new, doctyp, non-numeric, debit note, nf category, saplj1bi, function module dump, vendor invoice , KBA , FI-LOC-MM-BR , Brazil , XX-CSC-BR-MM , Use FI-LOC-MM-BR , Known Error

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.