SRM and CCM config

[Former Member]

HI,

We are able to upload products in procurement catalog and we have published it also.

But if we go to SRM , --- shop, we are getting the following error:

"Your session has timed out - call up SAP Catalog Search Engine again in SRM "

What could be reason? any suggestions.

We are missing some config setting, we couldnot trace out exactly.

We are using SRM 4.0 component version and CCM 2.0

Best Reg.,

Sridhar

Message was edited by:

P.T. Sridharbabu

[Former Member · Accepted solution]

Hi

Seems to be some SAP OSS note is missing. Try the following ->

<b>970710 Long runtime in TREX based searches using search items

996885 Cross Catalog Search - Timeout while accessing MDM Catalog

993828 TREX : timeout for search requests

969080 Long runtime in TREX based searches

442963 Search terminates with timeout in case of too many rules

814399 List price in product catalog (performance/all releases)

Note 1011683 - What is the session timeout for buyers and suppliers?</b>

Hope this will help.

Regards

- Atul

[Former Member · Accepted solution]

Hi Atul,

Thanks for the reply, I expected your reply like this with OSS notes either from you or Mahesh madasu.

Thanks a lot I will check and will let you know the result.

Best reg.,

Sridhar.

[Former Member · Accepted solution]

Hi,

I couldnot find much useful with these notes though 996885 is not of our patchlevel.

Any other suggestions pl.

Reg.,

Sridhar.

[Former Member · Accepted solution]

Hi

Please check your timed out parameters are set to respective values from RZ10. 

icm/conn_timeout 10000 

rdisp/max_wprun_time 1200 

icm/keep_alive_timeout 10800 

rdisp/j2ee_timeout 1000 

Increase the value em/global_area_mb if more users are connected from Web FrontEnd when compared to R/3 Backend login.

<u>Few SAP OSS notes -></u>

<b>Note 815870 - Timeouts in SRM

Note 742048 - Integrated ITS, memory requirement in application server</b>

<u>Also refer to these links -></u>

<b>/thread/328921 [original link is broken]

Do let me know.

Regards

- Atul

[jason_boggans]

Hi Sridhar,

If the SE version is active then the only other possibility is an incorrectly configured call structure.

Please verify that the URL is correct, i.e. it should read ~

http://[webserver:port]/sap/bc/bsp/ccm/srm_cse/main.do

Client = Client the CCM resides in

Catalog ID = The ID of the catalog in the CCM, not the description you have decided to give it here in SRM but the value in the table /ccm/d_ctlg_req

Language = Self explanatory

Locale = Langauge locale to access the catalog, e.g. EN-US

User/pass = Optional, not required if using SSO and the SSO user has the /CCM/CATALOG_SEARCH role

Hope this helps.

Jason

[Former Member]

Hi,

We have all the attributes maintained as mentioned above but while creating the procurement catalog we have added a space to that of the "define webservices'

The problem is solved now.

Thanks a lot for all your suggestions,

Best regards,

Sridhar.

[Former Member]

Hi Sridhar,

We are facing the same time out error as you mentioned. Can you let me know how you resloved this error.

Thanks

Anthony

[Former Member]

Hi Anthony,

We have added an empty space before our catalog name like XXX in the SRM server --> Master data --> define external web services

and we have typed(entered) the name directly in the PPOMA_BBP attribute CAT.

So I suggest you to check the name of the Webservice ID created and the value of the CAT attribute in the org structure and always try to select from F4 and dont type your catalog name in the org structure. Both should be identical.

Best Reg.,

Sridhar.

[Former Member]

Hi Sridhar,

We are using the Punch out scenario from ECC 6.0 work order. So we are accessing CCM from the work order in ECC once we do that we get the error

"Your session has timed out - call up SAP Catalog Search Engine again in SRM".

I did try what you said but we get the same error.

Do let me know if your thought.

Thanks

Anthony

[Former Member]

Hi Sirdha,

I have been facing such issues several times. Everytime it was connected to

the Internet Browser Settings.

All BSP driven pages (CCM, ROS and EVAL) need to be entered as alllowed

pages in Internet Browser via Extras - Internet Options - Security - Trusted Sites.

Make sure, the site is removed from untrusted sites.

This is depending on the policies of the related companies.

In order to controll access to the BSP applications, be aware of the "red eye"

show in Internet Explorer at the right hand corner on the button of the Internet

Browser Page. The corresponding report gives an indication, which sites are

blocked by company policy. By entery them in the allowed sites, the access

works.

Thanks,

Claudia

[jason_boggans]

Dear Sridhar

The issue is most likely related to the SE version of the CCM catalog, i.e. it is likely there is none.

In order for the catalog to be accessible from the SRM Server the catalog must be published, please verify in table /ccm/d_ctlg_req for the relevent catalog id if there is an <b>active</b> SE version of the catalog available.

Regards,

jason

[Former Member]

Hi,

With the above the process I found two entries in the table for my catalog out of which one is active and the other version is not.

SE Catalog object for search engine (active)

AI Catalog object for Authoring (not active)

I hope as per your reply SE should be active and it is.

Best Reg.,

Sridhar.

[Former Member]

Hi Sridhar,

This problem comes often in accessing CCM after newly publishing of catalogs.

Try this process.Call your published procurement catalog directly using your CSE URL that you will find it in Transaction SE80

Choose BSP Application and enter /ccm/srm_cse for Object Name

Expand Pages with flowlogic there you will find temp_entry.htm click on the top then a separate window opens on the ABAP Workbench go to the Properties window there you will find the URL to call the CSE.

Try to call this in the Internet Explorer ( if you can able to access your catalog which you have published then your problem is solved).

Then call your catalog again from EBP.

with regards,

mahesh