SAP Knowledge Base Article - Preview

2417692 - BAPIs called in SEQUENCE or LOOP in custom code - SAP ERP & SAP S/4HANA

Symptom

With the usage of a BAPIs in sequence or in a loop inside a custom code, it is observed that internal BAPI tables and variables are not cleared after the first BAPI is called. Depending how the BAPI tables and variables are filled, 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/4 HANA

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_ENTRYSHEET_CREATE, 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, DUMP, runtime, run time, CALL FUNCTION 'MS_RESET_STORAGE_LIMITS', MS_RESET_STORAGE_LIMITS, TIME_OUT, Dump, SE37 , KBA , MM-IV-LIV-BAPI , BAPI , MM-SRV-BPI , BAPIs , 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.