CDPOS table is oversized

[Former Member]

Hi experts,

I don't know too much about table CDPOS. Could you tell me something in detail about this SAP table?

I had performance problem according to cdpos table. It has a size category 3, which means that it is planned for 50.000 records. Now it has more than 50 million records.

How can I solve the performance problem or reduce the execution time of a selection applied on this table?

[Former Member]

Hi experts,

I don't know too much about table CDPOS. Could you tell me something in detail about this SAP table?

I had performance problem according to cdpos table. It has a size category 3, which means that it is planned for 50.000 records. Now it has more than 50 million records.

How can I solve the performance problem or reduce the execution time of a selection applied on this table?

[Former Member]

hi White,

1. Include all the key fields when selecting the data from this table

2. Never write repeated selects in a single program. Fetch the entire data for all the required condition with a single select and perform your operations with the data fetched.

Regards,

Santosh

[Former Member]

Hi,

I cannot restrict the selection for all the key fields, but anyway, it contains 50 million records instead of 50 thousand. How could it be? It cause serious performance problem. Even If I only want to check the number of entries in SE11 it takes more than 30-40 minutes.

[former_member194669]

The following is the documentation when i press f1 in size catagory field

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

a®

[Former Member]

CDPOS table is the change doucment item table.

We will take an example.

Let us take an example of creating a PO .

The the change documents are activated fro a particular field say PO date, then an entry will be created in CDPOS first time when the PO is created.

The CDPOS table gets updated each time when the PO date is changed. IN other words it will have a history of all the changes that are made to a particular table-field.

Regards,

Ravi

[Former Member]

You need to look at archiving change pointers.

[vinod_vemuru2]

Hi,

CDPOS table is change documents item table.

It will store all the changes done to the transactions.

eg: If u change the delivery quantity a change document will be created with the old and new data for that field. This will be done for the fields whose data element has is applicable for change document(i.e When u open this data element u can see one check box Change document)

If it is checked then change document will be created.

eg: LIPS-LFIMG has data element LFIMG. Open this data element in SE11. U can see that Change document check box is checked.

So when ever u change this table field a change document will be created.

Coming to performance usually it is slow. We can't help it out.

Only thing we can do is archiving old data so that table contents will be less. Ask ur basis people for more info

Why thosemany entries is because when ever u change any thing in SAP a change document will be created.

eg: sales orders, deliveries etc

Master data like customer data, material data etc

Instead of selects u can try FMs

CHANGEDOCUMENT_READ_HEADERS

CHANGEDOCUMENT_READ_POSITIONS

which are slightly faster than direct select.

Hope it is clear.

Thanks,

Vinod.

Edited by: Vinod Reddy Vemuru on Jul 2, 2008 8:34 PM