Skip to main content

SAP Technical Settings

SAP Technical Settings
Once this has been saved, the next step is to move on to maintaining the technical settings of the Table. Before creating the final Database table, SAP will need some more information about the table being created.
Select 'Technical settings' via the toolbar above the table, through the 'Go to' menu, or with the shortcut CTRL+SHIFT+F9.
Here, it is important to tell the system what Data class is to be used, so select the drop down button. There are five different options, with accompanying descriptions. For this table, select the first, labelled 'APPL0', and double-click it:




For the 'Size category' field, again click the drop-down button. Here, you have to make an estimate as to the amount of data records which will be held within the table so that the system has some idea of how to create the tables in the underlying database. In this instance, it will be a relatively small amount of information, so select the first size category, labelled 0:


Below this are the Buffering options. Here, 'Buffering not allowed' should be selected:


This prevents the table contents from being loaded into memory for reading, stopping the table from being read in advance of the selection of the records in the program. You may, correctly, point out that it may be advantageous to hold the table in the memory for speed efficiency, but in this example, this is not necessary. If speed was an issue in a development, buffering would then be switched on, ensuring the data is read into memory. In the case of large tables which are accessed regularly but updated infrequently, this is the option to choose.

Nothing else on the 'Maintain Technical Settings' screen needs to be filled at this point, so click Save and then go back to the table itself. If all of this is successful, then the table should now be in a position to be activated and the entry of records can begin. Click the Activate icon to activate the table and check the status bar, which should again read 'Object Activated'.


Comments

Popular posts from this blog

DBIF_RSQL_SQL_ERROR dump, ORA-14400 error FAQ

Symptom DBIF_RSQL_SQL_ERROR short dump in ST22 (exception CX_SY_OPEN_SQL_DB, form routine INSERT_ODS) "ORA-14400: inserted partition key does not map to any partition" The dump & error can occur when writing/inserting to PSA or F-fact tables or when DSO objects are activated. PSA loads fail. Unable to activate DSO requests. DSO activation fails. Activation job BI_ODS..... dumps Environment SAP NetWeaver 7.0 SAP enhancement package 1 for SAP NetWeaver 7.0 SAP enhancement package 2 for SAP NetWeaver 7.0 SAP NetWeaver 7.3 SAP enhancement package 1 for SAP NetWeaver 7.3 SAP NetWeaver 7.4 SAP Business Information Warehouse (SAP_BW) Reproducing the Issue Dump occuring during DSO activation: Run tcode RSA1  Find the problematic DSO & click manage Enter the activation log to view the returned error msg which will enable you to jump to tcode ST22 & view the related DBIF_RSQL_SQL_ERROR dump. Dump...

SAP Data Domains

SAP Data Domains Double-click the entry ('ZEENUM') in the Domain area, and agree to save the changes made. Now, the 'Create Object Directory Entry' window will re-appear and again it is important to save this development to the '$TMP' development class, via the 'save' or 'local object' button visible in this window. After doing this, a window will appear stating that the new Domain 'ZEENUM' does not exist. Choose 'Yes' to create the Domain, and in the window which appears, type into the 'Short text' box a description of the Domain. In this example, 'Employee Domain': The 'Definition' tab, which, as shown above, opens automatically. The first available field here is 'Data type', click inside the box and select the drop-down menu, and a number of generic data types already existing within the ABAP dictionary will appear. The 'NUMC' type is the one to be used here for the Emplo...