SAP Knowledge Base Article - Preview

2299244 - BAPIs called in a custom code LOOP

Symptom

With the usage of a BAPI in a LOOP inside a custom code, it is observed that internal BAPI tables are not cleared after the first call. This may lead to DUMP or a "User-lock" error.


Read more...

Environment

  • Materials Management (MM)
  • SAP ERP Central Component
  • SAP ERP
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA
  • SAP S/4HANA

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP S/4HANA all versions ; SAP enhancement package for SAP ERP all versions ; SAP enhancement package for SAP ERP, version for SAP HANA all versions

Keywords

BAPI, BAPIs, BAPI_INCOMINGINVOICE_CREATE, BAPI_INCOMINGINVOICE_PARK, BAPI_INCOMINGINVOICE_SAVE, customer, Z, Y, invoice, invoices, receipt, fatura, faturas, COMMIT WORK, BUFFER_REFRESH_ALL, MM-IV, MM-IV-LIV-BAPI, TIME_OUT , KBA , MM-IV-LIV-BAPI , BAPI , Problem

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.