General note for help with performance problems during allocation
The note is arranged as follows:
A) Cross-application notes
B) CO specific notes
C) FI-SL specific notes (also for Profit Center EC-PCA)
Transactions: KSV5, KSVB, KSU5, KSUB, KSW5, GA15, GA35, GA2B, GA4B,
3KE5, 4KE5
A) Cross-application notes
1. "Smaller" cycles are better for performance:
If a cycle has many segments (more than approx. 50), this cycle is processed with low performance. Analyze your cycles with a view to reducing a large cycle into several smaller cycles.
2. "Individual start" before "collective start" for many cycles:
Check whether the individual start of several cycles gives better performance than the collective start of several cycles. Under certain circumstances, a collective start provides poorer performance than an individual start of individual cycles.
3. Assessment instead of distribution:
If distribution can be replaced by assessment from a business-related view, this can lead to a considerable increase in performance due to the smaller amount of data to be processed.
4. Inactive iterative indicator not adopted during background processing (up to Release 2.2F).
Non-iterative cycles can be processed faster as iterative cycles. SAP recommends dividing a large cycle into smaller ones so that the necessary segments for constructing the iterative relationships form a seperate cycle and that all non-iterative segments form a cycle.
As in point 1 above, it makes sense especially for system performance to divide these non-iterative cycles into further, smaller cycles.
Up to and including Release 2.2F, the inactive iterative indicator is not adopted properly during background processing. Therefore, please install Note 15031 in your SAP System.
5. Performance problems with the master data validation: Note 72359 for Releases 3.0C-3.0F and 3.1G. Note 319913 for Releases 3.00-4.6C.
6. Selection of the sender/recipient values in segment definition:
If you use several individual values or sets for the selection of sender/recipient values in segment definition, please note that the number of individual values or of the sheets in these sets influences the runtime of the master data check in a linear way. The effect of a large number of individual values or sheets in a set may be a long processing time when creating the sender/recipient relationships. For this reason, you should keep the number of individual values as low as possible, and prefer intervals - if possible. Checking an interval has a much higher performance than checking the individual values in total.
B) CO specific notes
1. Expedited importing of transaction figures from COSP and COSS:
Up to and including Release 2.1H and 2.2B, you can expedite the importation of COSP and COSS transaction figures by installing note 14043.
If you have a release level BEFORE 2.1G, you can drastically improve the importation of transaction figures by creating a further database index for the tables COSP and COSS. As of Release 2.1G, the following changes are contained in the standard version.
To create this new index, follow the steps below. Note: You will require a great deal of knowledge concerning databases.
a. Creating an index for tables COSP and COSS
First create the following new index for tables COSP and COSS using transaction SE11:
OBJNR, MANDT, LEDNR, VERSN, WRTTP, GJAHR, VRGNG
Using the menu UTILITIES->DATABASE UTILITY or transaction SE14, then create the new index in the database.
b. Program modification
To use the new index you must make the following program modification.
************************
* Module FKARME01
* FORM K_COSPA_READ_MULTI
****************************
FORM K_COSPA_READ_MULTI
*---------------------------------------------------------------------
TABLES ICOSEL STRUCTURE COSEL
USING VALUE(VON_PERIODE)
VALUE(BIS_PERIODE)
VALUE(RNAME)
VALUE(PNAME).
*--------------------------------------------------------------------
:
:
*.........Summensätze.lesen,.geordnet.nach.PRIMARY.KEY.
CLEAR COSPA .
* SELECT * FROM COSP WHERE <---CHANGE
SELECT * FROM COSP CLIENT SPECIFIED WHERE <---INSERT
LEDNR IN TAB_LEDNR AND
OBJNR IN TAB_OBJNR AND
GJAHR IN TAB_GJAHR AND
WRTTP IN TAB_WRTTP AND
VERSN IN TAB_VERSN AND
KSTAR IN TAB_KSTAR AND
HRKFT IN TAB_HRKFT AND
VRGNG IN TAB_VRGNG AND
VBUND IN TAB_VBUND AND
PARGB IN TAB_PARGB AND
BEKNZ IN TAB_BEKNZ AND
TWAER IN TAB_TWAER AND
* PERBL BETWEEN VON_PERBL AND BIS_PERBL <----CHANGE
PERBL BETWEEN VON_PERBL AND BIS_PERBL AND <----INSERT
MANDT >= SY-MANDT AND <----INSERT
( MANDT = SY-MANDT OR MANDT < SY-MANDT ) <----INSERT
ORDER BY PRIMARY KEY. *.........falls.ein.neuer.Schlüssel.gefunden.wurde:.....
IF COSPA-LEDNR <> COSP-LEDNR
:
:
**********************************************
* Module FKARME02
**********************************************
FORM K_COSSA_READ_MULTI
*-----------------------------------
TABLES ICOSEL STRUCTURE COSEL
USING VALUE(VON_PERIODE)
VALUE(BIS_PERIODE)
VALUE(RNAME)
VALUE(PNAME).
*-----------------------------------
:
:
*.........Summensätze.lesen,.geordnet.nach.PRIMARY.KEY.
CLEAR COSSA .
* SELECT * FROM COSS WHERE <----CHANGE
SELECT * FROM COSS CLIENT SPECIFIED WHERE <----INSERT
LEDNR IN TAB_LEDNR AND
OBJNR IN TAB_OBJNR AND
GJAHR IN TAB_GJAHR AND
WRTTP IN TAB_WRTTP AND
VERSN IN TAB_VERSN AND
KSTAR IN TAB_KSTAR AND
HRKFT IN TAB_HRKFT AND
VRGNG IN TAB_VRGNG AND
PAROB IN TAB_PAROB AND
USPOB IN TAB_USPOB AND
BEKNZ IN TAB_BEKNZ AND
TWAER IN TAB_TWAER AND
* PERBL BETWEEN VON_PERBL AND BIS_PERBL <----CHANGE
PERBL BETWEEN VON_PERBL AND BIS_PERBL AND <----INSERT
MANDT >= SY-MANDT AND <----INSERT
( MANDT = SY-MANDT OR MANDT < SY-MANDT ) <----INSERT
ORDER BY PRIMARY KEY.
*.........falls.ein.neuer.Schlüssel.gefunden.wurde:..
IF COSSA-LEDNR <> COSS-LEDNR
:
:
2. Performance problems during importing, when, as a precondition, the reference bases "Variable portions/costs" or "Consumption quantity" are used by the cost element.
Please install note 20793 in your SAP System.
3. Unnecessary data bank access sorting, up to and including Release 2.2F.
Please install note 26950 in your SAP System.
C) FI-SL (EC-PCA) specific notes
1. Definition of secondary indexes in transparant FI-SL totals tables
Please read Note 31374
2. Update of sender recipient relationship during the allocation
Please double check whether you really want to update the sender recipient relationship. This might be the case e.g. if you want later to carry out an elimination of internal business volume.
If this is not the case, you can suppress this update using transaction GCA8, which results in a the records to be updated being considerably reduced.
Please note that you cannot deactivate the sender/recipient relationship in accumulated cycles. (The flag in Transaction GCA8 is not considered.)
Reason and Prerequisites
Information note.
No comments:
Post a Comment