SRM system performance issue.

[former_member560682]

Hello,

We are using SRM 5.0 with extended classic scenario.

Our system performance is getting worst and worst. The system is very slow.

What are the points i can check as a SRM consultant to resolve this issue?

Thanks,

Khushbu

[Former Member]

6. Workflow Archiving

The performance of the business workflow can be optimized by archiving outdated work items.

CANCELLED or in status COMPLETED entries are good candidates for archiving.

Recommendation: The lower the number of entries in the workflow runtime tables the better the

performance of the workflow engine. Work items are archived together with the SRM documents. This

allows online retrieval of the archived documents inclusive workflow via the normal web front end by the

use of ArchiveLink. For details please refer to http://help.sap.com

823893 SRM archiving: Archiving workflow items

573656 Collective note relating to Archiving in workflow

1098805 Troubleshooting Tips & Tricks for workflow issues

7. Hanging Workflow tRFCs

Some work items are not processed as errors occurred during tRFC processing. The monitor for transactional

RFCs (SWU2) shows errors for the destination 'WORKFLOW_LOCAL_<client>'.

Recommendation: Solve the problems, eliminate the hanging tRFCs and monitor transaction SM58 at

least once a day.

Solve the problems, eliminate the hanging tRFCs, and monitor transaction SWU2 at

least once a day.

Reprocessing of failed tRFC Calls

report RSARFCEX for automated reprocessing of tRFC is to be run on an hourly basis, but this also

depends on customer requirements.

Failed tRFC calls can also be executed immediately using an automatic communication error retry mechanism

that can be activated in transaction SM59 (and is normally activated by default). This setting may, however, cause

performance problems. We recommend, therefore, that you run report RSARFCEX.

Recommendation: Run report RSARFCEX on an hourly basis to collect failed tRFC calls for bulk

processing. For more information, refer to SAP Note 63483

8. Long Runtime of Report BBP_GET_STATUS_2

Recommendation: to improve the performance of the report BBP_GET_STATUS_2, review and

implement the SAP Notes listed below.

Different variants for the BBP_GET_STATUS_2 report can be used to keep the load from this report low.

For example, you can define the following

variants.

Nightly during the week: all shopping carts are checked.

Daily during the week: shopping carts from the last 30 days are checked. Hourly: shopping carts from the

current day are checked.

1145063 BBP_GET_STATUS_2: High runtime, improvement

proposals

521857 Selection parameters for BBP_GET_STATUS/BBP_GET_STATUS_2

regards,

MRao

[Former Member]

Hi,

Go through the below points.

1. Reorganization Job for Middleware Tables

Report SMO6_REORG for reorganization of the trace tables is not scheduled as a job or stops with an error.

Recommendation: Schedule the job to run on a daily basis.

Note: Please see SAP Note 206439 for details.

If errors occur, check SAP Note 214474.

2. Size of Organizational Structure

The key indicators shown in the table below describe the overall dimension of your Organizational Model. If those

key indicators exceed values, proven by SAPs experience, they might have a negative impact on the response

time of several SRM Core Business Processes, due to attributes inheritance. In addition the maintenance

transactions itself for the organizational model can show poor performance.

Recommendation: Try to avoid exceeding our recommended values when defining the organizational

model.

Key Indicator Recommended Value

Number of Organizational Nodes <= 100000

Number of Organizational Units <= 2000

Width of Organizational Model <= 500

Depth of Organizational Model <= 15

3. Configuration of Business Partner Integration

*Recommendation: To ensure that only business partners with address data are generated the

HRALX/OADRE switch must be set to X in the SRM customizing. In case that organizational units (in

transactions PPOM*) do not always have an address, a separate business partner for storing an address

template should be created. The number of this business partner, which is used as a container, is stored in

the HRALX/OADBP switch in the SRM customizing.*

Implementation: Execute the following IMG activity: 'SAP Supplier Relationship Management' -> 'SRM

Server' -> 'Cross-Application Basic Settings' -> 'Organizational Management' -> 'Integration Business

Partner-Organizational Management' -> 'Set Up Integration with Organizational Management'. As an

alternative the switches HRALX/O

4. Job HRALXSYNC

This report generates and updates business partners 'Organizational Units' and 'Employees' on the basis of the

time-dependent HR and PD Org Master Data (Organizational Units and Central Persons). It enables you to run a

consistency check for correct synchronization. If not all data exists for the business partner, you can synchronize

data. When synchronization is run for organizational units, the basic data (name, description) and the address

data is included; when synchronization is run for central persons, bank information is included in addition to the

basic data (first name, last name) and address data (home address, workplace communication details).

Recommendation: Schedule report HRALXSYNC on a daily

5. Usage of Attribute Requester

You can optimize the shopping cart transaction by reviewing the assignment of the 'Requester' attribute.

For example for some of the users this attribute could have been set to an organizational unit that contains more than 30 positions. As a result, a large amount of HR data (HRP1001 table) needs to be read, which slows down performance.

Recommendation: We recommend that you check whether it is essential to the business process that the

attribute requester is assigned. If it is essential, ensure that the number of persons for which the requester

can request is relatively low. Check whether the REQUESTER attribute can be assigned to a lower (more

specific) organizational unit.

If it is essential for a purchaser to be able to shop for many people, you can implement the BAdI

BBP_F4_READ_ON_ENTRY~GET_BOBUSER, which allows the SRM standard selection of the attended

employees in the 'Shop on Behalf' transaction to be bypassed. In this implementation, you can select users

directly, without using the organizational model. Please see also SAP Note 1095895.

If you implement the BAdI, note the following:

- If any of the tables is filled after the BAdI has been called, this module will not re-read but will preserve

the customers selection

- Note that the customer's data will not be validated

- If customers fill the favorite list, they will have to update the internal memory in the

BBP_UPD_BOBUSERS_FAV module and write the favorites back to the database in the

BBP_SET_BOBUSERS_FAV modules themselves.

- The GT_BOBUSER_FAV_ORG table can be used to store the initial list of favorites, while the

GT_BOBUSER_FAV_ACT table can be used to store current ones.