Skip to Content

The following jobs need to be scheduled to ensure smooth operation of your SAP CRM server.

Job: GN_GENERATE_CHECK

The report updates generation status information. If this report is not scheduled to run daily, the general status information displayed in the CRM middleware monitoring cockpit (transaction SMWP) is not up to date.

SAP Best Practice:Schedule the GN_GENERATE_CHECK report with period “daily”

How you do it ?

Call transaction SMWP. Select “Background Jobs”. Use the secondary mouse button to click “Check Generation Status of Objects” and select “Show Suggested Action”. Choose “Action”.

Tip: Make sure that you run this job before job GN_WORKLIST_GENERATE because job GN_GENERATE_CHECK creates the worklist with objects and the objects created in worklist are generated by job GN_WORKLIST_GENERATE.

Job: GN_WORKLIST_GENERATE

This report generates the objects in the worklist created before by GN_GENERATE_CHECK report. When new or changed BDOCs are imported to the system, function modules must be generated. After import, the module inserts the objects to be generated into a worklist. The report takes the objects from this list and generates the function modules for them.

SAP Best Practice:Schedule the GN_WORKLIST_GENERATE report with period “daily”

How you do it ?

Call transaction SMWP and select ‘Background Jobs’. Right-click “Periodical Background Generation” and select “Show suggested action”.

Tip:Please make sure that there is a reasonable time frame availble between the GN_GENERATE_CHECK and GN_WORKLIST_GENERATE program runs.

Job SMO6_REORG2

SMO6_REORG2 is responsible for reorganizing tables that hold statistical data in CRM Middleware.

Related tables: SMW0REL, SRRELROLES, SMW3_BDOC,  SMW3_BDOC1,SMW3_BDOC2,SMW3_BDOC4, SMW3_BDOC5,

Please note the job SM06_REORG2 only deletes fully processed BDOC´s. Not “Intermediate” or “error” ones. BDocs in the error state are stored in the

system for the correction of the problem. After the relevant BDoc-Mesage are set to “green” status the job / report reorg. the relevant tables.

Object links between mBdoc messages and mBdoc/sBdoc messages are held for 21 days in the standard job variant. If a business process is completed successfully, object link entries are no longer required. In our experience, a value of seven days is usually sufficient. If this is the case, set “Reorganize for object links (BDocs) days to hold” to seven days in your variant.

SAP Best Practice:Schedule SMO6_REORG2 to run in every production client on a daily basis.

Known issue & Fix

SAP Note 1789869 – SMO6_REORG2 terminates with SAPSQL_INVALID_TABLENAME short dump

SMO6_REORG report is taking time due to huge number of records.

Entries in table SMW0REL are high and the number of entries in table SRRELROLES of object type MIDMESSAGE is very high.

SAP Note 503002 – Performance problems during BDoc processing

SAP Note 493156 – Performance of BDoc message related object links

SAP Note 206439 – Reorganization of tables in CRM Middleware

Make sure you have created secondary indexes on table SRRELROLES and also for IDOCREL or SMW0REL as per SAP Note 707820 – Performance: Object links and RSRLDREL

Generally, you should schedule the report RSRLDREL periodically to prevent the link tables from filling up. Otherwise, the runtimes of all the programs that access links will increase.

JOB: HRBCI_ATTRIBUTES_BUFFER_UPDATE

This report buffers the organization management structures in the INDX cluster table, which can cause significant performance improvements in nearly all CRM scenarios.

If the job is not executed, significant time is spent searching the attributes of organizational management or determining a responsible organizational unit, which has a direct influence on all business transactions in the CRM system.

The buffering indicator must be configured in the OOATTRCUST transaction for the scenario you use in CRM.

SAP Best Practice:Execute the HRBCI_ATTRIBUTES_BUFFER_UPDATE report after midnight on a daily basis with variant SAP&CRM.

Known issue & Fix

If the HRBCI_ATTRIBUTES_BUFFER_UPDATE report is scheduled regularly and runs successfully, there is no need to update daily changes online. To avoid the exclusive lock on the organizational buffer and performance degradation of your system, deactivate the BAdI HRBAS00INFTY implementation CRM_ORGMAN_ATTR_BUFF, which is active by default.


926540 – Missing Organizational units

896128 – HRBCI_ATTRIBUTES_BUFFER_UPDATE: selection screen not correct

934441 – Missing service in the SMOMITAREA table

HRBCI_ATTRIBUTES_BUFFER_UPDATE cancel due to memory errors TSV_TNEW_PAGE_ALLOC_FAILED or TSV_TNEW_BLOCKS_NO_ROLL_MEMORYJob cancle.jpg

Error details

Memory error.jpg

Implement SAP Note 1812579 – Performance issues with report HRBCI_ATTRIBUTES_BUFFER_UPDATE

Make sure that the distribution to mobile client is ‘OFF’ as you do not use mobile, when running the report

Make sure that your system does not have unrelated objects. For example if you have created several positions without assigning to any org unit, which does not make any business sense. As these objects are not useful in the business transactions it is required to delete by using the report RHRHDL00 which in turn improves the performance


Job HRBCI_ATTRIBUTES_BUFFER_UPDATE takes long time or cancelling due to program error

Make sure that you have implemented SAP Note 2006166 – CRM ORG:Performance improvement in the hrbci_attributes_buffer_update report



JOB: BSP_CLEAN_UP_SERVER_COOKIES

This background job deletes expired server-side cookies from database table SSCOOKIE. If this job does not run, the table SSCOOKIE grows significantly and may lead to performance when it is accessed. The job deletes COOKIES older than the current date. All cookies can be displayed with the job called BSP_SHOW_SERVER_COOKIES


SAP Best Practice: Schedule job BSP_CLEAN_UP_SERVER_COOKIES to run on a regular basis, ideally daily during a non-operational time frame (for details, see SAP Note 1080518).

This job deletes expired cookies in the SSCOOKIE table that are older than the current date.

Rebuild the indexes of the SSCOOKIE table periodically.

JOB:SMWP_BATCH

This background job refreshes flow definition information for the middleware generation.

If this report is not scheduled periodically, information displayed in the CRM Middleware Monitoring Cockpit (transaction SMWP) is not up to date.

How you do it ?

Call transaction SMWP. Select “Background Jobs”. Right-click “Collector for Monitoring Cockpit” and select “Show suggested action”. Choose “Action”.


SAP Best Practice:Schedule the “Collector for Monitoring Cockpit” job on daily basis.

To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

Leave a Reply