Ansicht
Dokumentation

/SAPCND/CHANGE_BUFFER_SETTING - Change buffer setting of condition tables access view

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Purpose

The Function of this report is to change the buffer settings of the generated access view for the Condition Table.

Reason

Generated Acces Views of Condition tables are alway's Fully buffered in order to improve the perfomance during data retrieval and to reduce the Database access for each record.

This setting can lead to performance issue in scenario's where the Condition Table holds huge amount of condition records. As per the note no. 1011158 Section 1, such tables should not be buffered

Prior Check

Before going for the execution of this report consider below points if can be applied to reduce the size of condition table.

1: Check if there are un-necessary Condition records are exist in table which are no more used in any transaction and just holding the space in table. Try to archive and delete such records which are no more usable via transaction SARA for Archiving object CND_RECORD. Once done check if it improves the performance or not.

2: If still the performance does not improved after applying point 1 check if Condition Table holding records with Release Status as 'x'. Try to archive such records as well if not needed. You can make use of below two reports to archive and delete the records.

1: /SAPCND/CND_RECORD_WRITE to archive the conditon records (select 'Archvive Deleted Records only').

2: /SAPCND/CND_RECORD_DELETE to delete the archived records.

Execution of Report

If none of the above approach works in order to improve performance then execute this report.

This report will only regenerate the Accessview of the given table and change the buffer setting as the input given by the user. It will not regenerate any other objects of the Condition table.

This report provide option for both Buffering and Unbuffering for a Accessview, just in case if in future user wants to Buffer the table again.

Note:- You can't provide multiple Input in the input fields, it has been restricted intentionally so that at a time user can enter only one table. This restriction is there so that user can't enter any other table belongs to the same Application and Usage by accidently, which may lead to changing of technical setting of unwanted table access view.

BAL_S_LOG - Application Log: Log header data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2481 Date: 20240427 Time: 061617     sap01-206 ( 52 ms )