CCM 2.0 Publish and table /CCM/D_VIEW_OB_R

[Former Member]

Hi

CCM 2.0 questions

1) Are there any more support packs after SP15 for CCM 2.0. I can't see anything on OSS.

2) Catalogue publish - We are finding that table /CCM/D_VIEW_OB_R is increasing by a large amount when we run a full publish, even though no new items have been added. Can anyone explain why / how this table is used via publish.

I am aware that first all items are marked as deleted and then the catalogue is re-built in effect, but why would there be such a large increase in entries, when we have for example not added any new items and only changed the price on 200 ?

Catalogue items example 100K. Change the price on 200 then run a full publish. Takes hours. Cancel publish, run unlock, then re-org tables. Publish then takes expected time and is ok ?

Thanks in advance

[Former Member]

Thanks for the fast response.

[Former Member]

Hi Jason

Many thanks for the reply. I cannot open the text file. Could you please email me. i've sent you an email

Kay

[jason_boggans]

Hi Kay,

As CCM is no longer being developed, there are no immediate plans to introduce any further support packages for it. (This relates to the 640 version, for 700 version, there is no official change to the SP stack release, we just do not have any corrections to add to a new SP.)

The table /CCM/D_VIEW_OB_R is designed to retain the object relations of the item view contexts in CCM, when publishing takes place, this table registers and identifies the requirement for adding/changing/deleting etc content from specific views, sometimes this becomes inconsistent, if for some reason the publication fails, the view relations table may also be stuck in an inbetween status where it's process has not completed, generally, after the next successful publishing of the catalog these errors correct themselves. However, in the case of content deletion sometimes this is not possible, for this we have a Z Report which I will attach here for your convenience.

Please adjust the report to suit your system with reference to the catalog ID and version.

lv_ctlg = '4000_PROC'.

lv_version = '2'.

Regards,

Jason