Skip to Content
avatar image
Former Member

Basics settings for CCM

Hi friends

We have CCM system as add-on in SRM (version 2.0_700).

Could you tell me, that necessary basics settings should I do for CCM in this case?

Everywhere I can see only settings for SRM and CCM on separate client with IX.

Thanks

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Oct 21, 2008 at 10:14 AM

    Hi Marina,

    Basic settings required for all in one deployment of SAP CCM will include configuration of the customizing settings available under cross application components in SPRO.

    These include definition of the TREX engine which will be used in indexing and optimizing, definition of additional catlaog specific parameters like renaming the master catalog (ONLY do this if in initial startup, if the CCM system is already installed and catalogs exist, do not perform this change!!), definition of parallel processes to be used in mapping and/or publication (search notes for parallel publishing under component AP-CAT*), access to CCM specific Badi's, definition of XI transformation system for contract or product master data transfer (additional customizing of the SAP XI is needed to achieve the communication and data transfer, see the SAP CCM cookbook for more information), definition of catalog approval status where an incorrect status has been chosen at catalog creation for a procurement catalog (i.e. you can change from approved to to be approved and vice versa), definition of catalog upload settings, i.e. max package size etc., access to PFCG for assignment of views creaetd in SAP CCM to roles for catalog restriction.

    The 'advantage' of using SAP CCM as an integrated component in SAP SRM is that if you are not planning on using the contract or product master exchanges, and using CSV 2.0 flels for catalog schema/content upload, then no configuration of XI is necessary as it is not required in this case.

    Regards,

    Jason

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Ramakrishna.

      Yes, TREX is a mandatory requirement for CCM 2.0, it is used for indexing and optimizing the published metadata, without it, there cannot be any publication and as such no SE (Search Engine) version of the catalog.

      Configuration of the TREX is quite straightforward, i.e. you just need to install the TREX on the server you wish it to be, then in CCM Customizing, set the customizing for TREX engine to be used in publication ... if this TREX RFC destination is directed to a client other than the client CCM is installed in, this is regarded to be a 'Distributed' publication rather than local. So the indexed data is available in the TREX client, not in the CCM client, see SAP Help for more details on this if required.

      Regards,

      Jason