Regarding size category

i have created a custom table with size category as 0 to....
as it aceepts only 19000 records.when i need to add 25000 record will it accept.if not,what error will be passed.

hi
size cataogiry just allocate space in database to store that table data; if the table records exceed than size catagory limits then those rows are stored in data base but not in sequence because of that performance has slite effect but u need not to consider about that. till the size cataogiry range the records will entered line by line in data base , so when retriving data simple to retrive.
with regds:
rajesh.k

Similar Messages

Data dictionary size category

Hello Experts!
What is the case if the expected number of data records in sap database table are very much more than the records expected for the size category 4? Will it leads to dump?
Regards
Sanguine
Moderator message: FAQ, please search for previous discussions and read F1 help.
Edited by: Thomas Zloch on Mar 8, 2012

Hi
No..it wil not leads to dump..size cat is for initial buffer alloaction.
Regards,
Raghu.l

Error in Size category in COPA

Dear experts,
When i creating Operating concern.System is showing error message'" maintain size category of CE1s001 in SE13 tcode.
Not able to understand the logic.Why it is required?
If i will maintain.Will not hurt the process.Becoz i will create operating concern later based on client requirements.
Right now i m adding Batch field in operating concern S001 in gloden client so that i can do some testing.
regards
RR

HI,
for CE1S001 the size category is empty in SE13, thus you cannot use this sample operating concern if you don't maintain a size category.
F1 help: Size category
     The size category determines the probable space requirement for a table
     in the database.
     You can select the categories 0 to 4 for your table. Each category is
     assigned a specific fixed storage area value in the database. When you
     create a table, initial space is saved for it in the database. If more
     space is required later as a result of data that has been entered, the
     storage space is increased in accordance with the category selected.
     Press F4 on the field Size category to see the number of data records
     that can be maintained for the individual categories of your table
     without complications ensuing. These complications could be for example
     a reorganization becoming necessary because the maximum space to be
     reserved for the table was exceeded due to the maintained size category.
BR Christian

Size Category of a standard table - - Urgent

Guys,
Suppose the data in the table exceeds the size category of the table defined, will there be any problem??
Is there any possibility of changing the size category of the standard table??
Regards
Jiku

Hi,
Internal tables
Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and
formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects. A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.
Internal Tables as Dynamic Data Objects
Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2
gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.
Regards,
Bhaskar

Transporting Table Size Category

We are increasing the size category on a table in our database (Oracle). I made the change in development and was prompted for a transport, which was saved, released and migrated to QAS. However, in checking the tables techical settings in QAS it appears that the size category did not change.
I verified that the transport went in cleanly, even tried re-transporting, and making sure the object was generated. Nothing I do seems to be bringing the change over. Is anyone aware of any tricks in transporting technical settings on a table, or size categories in particular?

Hi Bret,
If this is the case in QAS, then I doubt whether the technical setting changes have been properly added in the transport request. Please cross check the objects and stuffs added to that paricular TP request ini SE01 and confirm back that all the technical setting changes have been added the TP request.
I doubt it is not added to the TP request.
regards,
Vinodh.

LIKP Techinical Settings Size Category

Hello colleagues, I'm opening this thread on behalf of a friend.
In DEV System, the table LIKP contains 7.2 million records and size category in Technical Settings is '2' (Data records expected: 2,500 to
10,000 ). Is it advisable to increase the size category to 6. Does this improve the database performance? If Yes, then can we increase the size category? can this be applied to other SAP standard Tables whose size category is not matching with the record count?
Thanks in advance!
Best regards,
Daniel.

This is what the f1 documentation on size category says
Each category is assigned a specific fixed storage area value in the database. When you create a table, initial space is saved for it in the database. If more space is required later as a result of data that has been entered, the storage space is increased in accordance with the category selected.
So defining the size category is for storage . .Hope this gives the answer for your question.

Table Size Category

We have a table (FMIFIIT) which has 15,000,000 records. This table is sized at level 4, which is 40,000 to 160,000 expected records. Obviously, performance is very slow on this table. Will increasing this size category speed up performance? If so, are other steps involved? If not, what other options other than indexes can we take. We are running ECC 6.0 and Oracle 10g
Thanks,
Blake

Hi,
Changing the table category now will not improve performance.
It is just a hint for the DB tools to size the tablespace next extent at installation.
Check to see if the indexes need to be reconstructed and check to see if the table needs to be reorganized.
And check if you need to add one index.
Regards,
Olivier

Size category

Hi Experts
While creating table in SE11, we mention size category,
If the records exceeds the limit what we mentioned in the table,
then how it will store data.
for example, if exceeds 12000 records, cant we store data in the table.
pls advice me.
regards
rajaram

Hi,
The size category describes the expected storage requirements for the table on the database.
An initial extent is reserved when a table is created on the database. the size of the initial extent is identical for all size categories. If the table needs more space for data at a later time, extents are added. These additional extents have a fixed size that is determined by the size category specified in dictionary.
Regards
Abhijeet

Why SXMSPMAST and SXMSPMAST2 have diferent size category

In PI 7.0 size category of tables SXMSPMAST and SXMSPMAST2 was 4 (200.000). After installing SP 18 I found that category increase till 6(830.000). But it increase only for SXMSPMAST2.
Why they have diferent size category?

You can use TA: SE11 => "Database table: SXMSPMAST" => "Technical settings" => change size category to "6". Then activate your changes!
A transport will be generated for this change which has to go from DEV => QA => Prod system!
Regards,
Kai

Increase the range in size category

Hi All,
I want to increase the no.of record in Size Category...
as it shows....at size category 8 we can add upto max. 48,000,000 record...
but we have 62,000,000 records ...
so wt wt to do..plz suggest...
can we increase the range of records in size category...or can we add another size category as 9 ...for bigger range,.
Plz suggest.
Thnx Rohit

Hi,
For size category, if you define as 8, this means in the initialization, the system will distribute 48,000,000 space for it, when it is consumed off, then another 48,000,000 space will be created.
So I think you don't need to worry about this.
Please try.
Regards,
Chris Gu

Size category in technical settings while creating database table

Hi all,
I am creating custom table in ABAP dictionary, while allocating size category in technical settings F4 help values are not coming.i am entering 0,but number of records expected range is not coming.i searched across SDN but couldn't find anything related to it.
Thanks in advance.
Sheela Patil
Edited by: Sheela Patil on Oct 4, 2011 7:21 PM

Hi
Check it properly it will dispaly the size ranges on clicking F4 button.
In this format it will display on clicking F4 button on size category field.
SzCat Number of data records of table expected
0                0 to         4,800
1            4,800 to        19,000
2           19,000 to        76,000
3           76,000 to       300,000
4          300,000 to     1,200,000
5        1,200,000 to     2,400,000
6        2,400,000 to     4,900,000
7        4,900,000 to     9,800,000
8        9,800,000 to    19,000,000
I hope it is solved for you.

Changing Size Category of CIF_IMOD table

Hi,
There was a performance issue in CO11 transaction, then we found out that , select query fetching data from the table CIF_IMOD iis expensive. So we created a secondary index for this table(N0n-Unique index-->No database index). The performance issue was resolved for few days. Again we are facing the same issue and now we are trying to change the size category fo the table CIF_IMOD. Currently its size category is 1 (holds 75 to 340 records) . but it contains more records.
Please advice me will it improve the performance after changing the size category and what will be its impact on the system.
If someone had faced the same issue please share your experience,
Thanks
-Always Learner

Hi,
Size category will not improve the performance data reading from table, It used only how motch tablespace allow when extend the table size.
You should check for which index is corrently and it is right index or not.
Check for last Index Statistics update date, if it is not updated recently, Tell basis person to update index statics.
Rgds
Ravi Lanjewar
Edited by: Ravishankar Lanjewar on Jun 23, 2010 1:48 PM

Changing of data class and size category for keyfigures .

Hi,
I am not able to change the data class and size category for keyfigures .
can you please let me know how to enable the changing of data class and size category for keyfigure under Maintain DB storage parameters.

Ok then it sounds like your primary key of 8 fields and secondary index of 3 non-unique fields appear somewhat similar to the database and it wrongly uses the secondary index. Perhaps you can try to declare the table as a SORTED table with index fields as key. I doubt this will do any good, but you can try.
You can try to deactivate the sec. index if it is not being used.
Or by far the best but also debatable, try to pass hints to the SQL parser by %_hints statement. Please refer to SAP note 129385 for details on hints in general and note 772497 for various hints statements for ORACLE DB. This will surely make the DB interface use the primary index and the update would be faster. But with 1 million records, hopefully you are not looking at response time in micro seconds, are you?
rgds,
Prabhu

Size category while creating a ztable

Hi,
I had created a ZTABLE with Size category(Technical Settings) as 1 which has a capacity of 1,400 to ,5700.
Just in case at a later date if the no.fo records gets increased will the system take care of the size category by itself
or it has to be changed again.
Thanks,
K.Kiran

if you know that this may be increased, better define it as a greater value range.
but any ways.
The size category determines the probable space requirement for a table in the database.
You can select the categories 0 to 4 for your table. Each category is assigned a specific fixed storage area value in the database.
When you create a table, initial space is saved for it in the database. If more space is required later as a result of data that has been
entered, the storage space is increased in accordance with the category selected.

Regarding receiver category in sales order.

hi Gurus,
I am facing a problem in making Sales Order, the problem is as follows: -
I have enter the all input to make SO, like sold-to-party, division, qty, etc.
But, by cliking enter i got a massage " receiver category is not allowed by SD1 settlement profile"
I check the parameter of receiver category as well as settlement profile, but i can't understand it.
please any one tell me to how to solve this problem?
Thanks in advance,
Regards,
Shripad

Hi
It is some thing to do with settlement profile for the sales order.
you better coordinate with your CO collegue for solvin this.
Regards
YMREDDy

Regarding size category

Similar Messages

Maybe you are looking for