SAP Knowledge Base Article - Preview

3333701 - User exit not called even if you placed custom code into it via SE37

Symptom

You have a certain user exit into which you coded custom ABAP code to influence a certain SAP business document processing logic.
Eventhough you have the code in the exit and the exit seems to be activated at SE37 tcode, the calling of the custom code not happens, the custom code not runs when it should.

For example user exit EXIT_SAPLMEREQ_010 and EXIT_SAPLMEREQ_008 are not called in ME51N even if it's active.


Read more...

Environment

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

Product

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

user exit, EXIT_SAPLMEREQ_010, EXIT_SAPLMEREQ_008, CMOD, NE51N, not called, active , KBA , MM-PUR-GF-CE , Customer Enhancements , MM-PUR-REQ , Purchase Requisitions , MM-PUR-OA-CON , Contract , MM-PUR-PO , Purchase Orders , MM-PUR-OA-SCH , Scheduling Agreement , 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.