2417692 - BAPI_ENTRYSHEET_CREATE and BAPI_INCOMINGINVOICE_CREATE called in a custom code sequence | SAP Knowledge Base Article

SAP Knowledge Base Article - Preview

2417692 - BAPI_ENTRYSHEET_CREATE and BAPI_INCOMINGINVOICE_CREATE called in a custom code sequence

Symptom

When calling BAPI_ENTRYSHEET_CREATE and BAPI_INCOMINGINVOICE_CREATE in sequence in 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.


Read more...

Environment

  • Materials Management (MM)
  • SAP R/3
  • SAP R/3 Enterprise 4.7
  • SAP ERP Core Component
  • SAP ERP
  • SAP enhancement package for SAP ERP
  • SAP enhancement package for SAP ERP, version for SAP HANA

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP R/3 Enterprise all versions ; SAP R/3 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 , 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 ONE Support launchpad (Login required).

Search for additional results

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