Problems after system copy

[Former Member]

Hi,

We areon SRM 3.0, EBP 4.0 SP11.

We created a system copy few days back and also completed the post copy steps.

We used the SAP guide- <b>"Setup, Transport and copy of EBP systems"</b> to do it.

While testing the copied system all the shopping related transactions are working fine...but the carry out sourcing transaction is throwing a timeout dump.

We are able to observe that there is a SAP connection to the system

0 DIA 4293 running Yes 414 SAPLBBP_PD 600 TESTUSER Sequential read BBP_PDVIEW_ORG

after 300 seconds the connection times out.

This happens in GUI as well as thro Web.

Have I missed out any specific post system copy steps related purchase orgs/purchase groups.

As far as I can see, I have completed all the post steps as per the guide.

Can anyone throw some light on this?

Thanks,

Srivatsan

[Former Member · Accepted solution]

Hi

Please refer to the following OSS notes.

<b>

Note 534327 - Performance problems in BBP_PROCDOC_GETLIST

Note 675923 Minor performance increase for search modules

Note 634621 GTOP21 -- Search for Bid Invitations & Bids

Note 634623 GTOP21 -- Search for Bid Invitations & Bids

Note 568781 Performance improvement of search modules (GetList)

Note 537083 BBP_BW_SC_SELECT_1: Performance improvement

Note 996676 Performance improvement in search for bid invitations

Note 926434 Purchasing group displayed incorrectly in internal list

Note 868382 SRM Sourcing Cockpit

Note 721358 Perfomance improvements for list displays

Note 773645 SRM contrct and global outlne agreemnt: Perfrmnce for search

Note 815870 - Timeouts in SRM

Note 787417 - SRM and internal ITS: Session cookie is retained

Note 979371 - Sourcing: Reading the hierarchy data takes a long time

Note 978959 - Sourcing: New transaction immediately calls the search

Note 979476 - Calling transaction BBPSOCO01 takes a very long time

Note 675923 Minor performance increase for search modules</b>

Hope this will help.

Please reward suitable points, incase it suits your requirements.

Incase it does not help, please raise an OSS message with SAP.

Regards

- Atul

[Former Member]

Hi,

This issue is resolved.

There was an adjustment which needed to be done at DB level by basis and this solved the issue.

I am still not sure what was exactly done...probably some DB tuning.

Thanks for all your help!

Srivatsan

[Former Member]

Hi Srivatsan,

Try to call this transaction in SAP GUI this is a usual bug in srm.

with regards,

mahesh

[Former Member]

Hi,

In PPOMA_BBP all companies and also purchase orgs/groups have maintained SYS attrubute which corresponds to logical system name. Look up for this attrubutes and check if they hanged after system copy.

Regards,

Marcin Gajewski

[Former Member]

Hi,

See if the foll notes help:

979476

979371

978959

BR,

Disha.

Pls reward points for useful answers.