SAP Knowledge Base Article - Preview

2638913 - Transaction SE16N populates 'Maximum No. of hits' field randomly

Symptom

In transaction SE16N, you enter a table in the table field and you change the 'Maximum no. of hits' field to blank.  You select the 'Number of Entries' button and the 'Maximum no. of hits' field is populated with a random number.


Read more...

Environment

  • Controlling (CO)
  • SAP R/3
  • SAP R/3 Enterprise 4.7
  • 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 Finance
  • SAP S/4HANA
  • SAP S/4HANA Cloud
  • SAP Fiori for SAP S/4HANA Finance
  • SAP Fiori

Product

SAP ERP Central Component all versions ; SAP ERP all versions ; SAP Fiori all versions ; SAP Fiori for SAP S/4HANA Finance all versions ; SAP NetWeaver 7.4 ; SAP R/3 Enterprise all versions ; SAP R/3 all versions ; SAP S/4HANA Cloud all versions ; SAP S/4HANA Finance 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

SE16N, SE16H, Maximum no. of hits, Number of Entries, Blank, random number, maximum number of entries error, Maximum no. of entries error. , KBA , CO-OM , Overhead Cost Controlling , How To

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.