CDPOS

[Former Member]

Hi,

I just want to know the number of entries in cdpos.

But clicking on Number of entries in se16n is taking a lot of time and not giving any result.

Can any body tell the reason?

Thanks

[Former Member]

This table stores all the changes done on the dataelemnts which have change document check box checked. so it holds huge number of entries. hence do not attemp select on this table.

the header table is CDHDR

[Former Member]

I was using select on cdpos,

what can be the other option to enhance the performance?

[Former Member]

Hi Mahendra,

First check CDHDR and then query CDPOS to enhance the performance.

Regards,

Atish

[Former Member]

Hi,

There could more no.of records for that it is taking toomuch time.

What u can do u work on selection criteria.

enter values in selection-screen then choose no.of entries.

Assign points if useful.

[Former Member]

Goto SE11

write CDPOS in database tables

display

Ctrlshiff10 (contaents)

Width of Output List 250 make it blank

Maximum No. of Hits 200 make it blank

Width of Output List

Maximum No. of Hits

press push button NUMBER OF ENTRIES

you will get how many entries are there in table

Rewards if useful...............

Minal

[Former Member]

Hi,

CDPOS is a line item table and contain the old & new Values of all the changes done in SAP.

CDHDR is the header table which contains Object Class, Object Id and change No based on date & time stamp.

Corrsponding to a single change no in CDHDR there can be a multiple items in CDPOS.

If you want to search for number of entries in CDPOS you need to specify some filter criteria otherwise there might be system time-out as well.

It is always advisable to first go to CDHDR and get the required change numbers and based on it, expolre CDPOS.

[Former Member]

Hi

CDPOS - Stores the item change data.

CDHDR and CDPOS are indeed the only logs where any and all changes are recorded on a stand-alone R/3 system. But, if you have a BW system set up, then certain patches must be applied to R/3, the main reason being to set up special structures to record any deltas (changes to transactions).

This is done in Logistics, for example, by adding new sets of three Infostructures to each transaction type. Say for Sales, up to now we've had S001 ( I think) as the Infostructure for Sales (VA01) transactions. Now with the new BW patches, we will have S260, and S260BIW1, and S260BIW2. This set-up allows BW to trigger data extractions from R/3 into BW without burdening on-going R/3 transaction activity: it works like this: initial sales data would be recorded in S260; and then R/3 checks in a certain table to determine where to place any changes to this original sales data; it will go to table TMCBIW to determine which of the two tables is active ( S260BIW1 or S260BIW2), and then proceeds to record the changes therein. Now when BW wants to trigger an extraction, it also goes to the TMCBIW table and swithches the active table off, and the idle one on: now R/3 continues recording its changes, but now they are recorded in the newly activated table, meanwhile BW can now draw out all the change data recorded in the active table, now deactivated.

Read about it in 'Business Information Warehouse for SAP' by Hashmi.

there may be lot of entries in that thats why it is taking time to show all the values

when you click on number of entries button then it is trying to collect all the data at that time it is taking so much time

other wise you can execute some number of entries like 500 and click on execute

<b>Reward if usefull</b>