Symptom
You use SAP HANA as a database for Contract Accounts Receivable and
Payable Vertragskontokorrent (FI-CA). This may have a negative effect on
the performance of some processes. In particular, this may be the case
for customer-specific developments or enhancements (for example, if you
have customer-specific definitions of FI-CA events).
Other Terms
FP-PERF, HANA, SAP HANA
Reason and Prerequisites
You use SAP HANA as a database.
Solution
Performance optimizations for FI-CA on SAP HANA
As of SAP Enhancement Package 7 for SAP ERP 6.0, SP 02 and SP 03, you can improve the performance of a large number of Contract Accounts Receivable and Payable processes. To do so, in Customizing, you must activate optimizations for the database accesses for column-oriented main memory databases such as SAP HANA:
In the IMG for Contract Accounts Receivable and Payable, under "Technical Settings -> Activate Optimizations for Database AccessOptimierungen für Datenbankzugriffe aktivieren", you can activate individual optimization IDs. The following optimizations are available:
For more information, see the following release notes:
Optimizationof customer-specific definitions of FI-CA events
SP 03 provides the new FI-CA event 1820 for customer-specific developments for FI-CA events in mass activities:
Event 1820 executes preparatory selections prior to the processing of each interval in the mass activity framework. By default, no processing is provided at this point. However, you can define an installation-specific module here.
Example:
In the interval module of a mass activity, there are selections on customer objects. The mass activity is a SAP standard implementation for the interval module. For an optimization of the data selection, in event 1820, fill the buffer for the selection that is performed subsequently in the interval module.
Typically, the parallel processing object (I_BASICS-RUNKEY-OBJECT) is determined for this. A suitable mass read module can be called for this object for the current interval limits (I_LOW, I_HIGH) that writes the read data in a buffer. The single accesses that subsequently occur in the interval module can then read from this buffer.
Additional optimizations of customer-specific developments
For general performance recommendations for customers, go to: http://service.sap.com/performance
On the left side, navigate to "Performance -> Resources -> Best Practices for ABAP Performance". This displays a list of documents, in particular "Performance Do’s and Don’ts ABAP". While this document does not contain any SAP HANA-specific recommendations, it does contain recommendations that are still valid for SAP HANA.
Currently, there is an exception for SAP HANA: We recommend that you do not use Joins in combination with SAP HANA because this may have a negative on performance.
As of SAP Enhancement Package 7 for SAP ERP 6.0, SP 02 and SP 03, you can improve the performance of a large number of Contract Accounts Receivable and Payable processes. To do so, in Customizing, you must activate optimizations for the database accesses for column-oriented main memory databases such as SAP HANA:
In the IMG for Contract Accounts Receivable and Payable, under "Technical Settings -> Activate Optimizations for Database AccessOptimierungen für Datenbankzugriffe aktivieren", you can activate individual optimization IDs. The following optimizations are available:
Process | Transaction code | Optimization ID |
Payment lot | FP05 | 0001, 0002 |
Cash Journal Evaluation | FPCJR | 0004 |
Payment run | FPY1 | 0010, 0011, 0012, 0020, V010 |
Automatic Clearing | FPMA | 0020 |
Dunning proposal run | FPVA | 0020, 0030, 0031, 0032 , 0033 |
Dunning activity run | FPVB | 0035, 0036 |
Correspondence Printing | FPCOPARA | 0040, 0041, 0042, 0043 |
Open item list | FPO1/FPO4 | 0050 |
All item-relevant posting processes (for example, FPY1, VYSPA) | 0060 | |
CO-PA transfer | FPG3M | 0070 |
G/L document check | FPG2 | 0071 |
Check totals records | FPT1 | 0072 |
Check CO-PA document | FPG7, FPG7M | 0073 |
Release to collection agency | FP03M | 0079, 0082 |
Submit to Collection Agency | FP03DM | 0083 |
Information to collection agency | FPCI | 0084 |
Mass write off | FP04M | 0080, 0081 |
Interest Run | FPINT1 | 0085, 0086 |
Revenue distribution | FP60M | 0087, 0088 |
Post revenue distribution | FP60PM | 0089, 0090 |
Requests | FKKORD1/2/3 | 0095 |
Credit clarification | FPCRPO_DET | 0100 |
Invoicing | FKKINV_MA | 0550, 0580 |
PS-CD transfer of billing document | P001 | |
Account Balance | FPL9 | R001, T001 |
Create IS-U bill | EA26 | R480 |
Insurance invoices | VYCOV004 | V015 |
Debit position | VYSPA | V020 |
Payment plan transfer | Function module ISCD_SCPOS_MAINTAIN | V030 |
FS-CD dunning proposal | VPVA | 0020, 0030, 0031, 0032 , 0033, V040, V041 |
FS-CD dunning activities | VPVB | 0035, 0036, V045 |
Broker report | IBR50 | V055 |
- FICA_607_2_PERFOPT (for SP 02)
- FICA_607_3_PERFOPT (for SP 03)
Optimizationof customer-specific definitions of FI-CA events
SP 03 provides the new FI-CA event 1820 for customer-specific developments for FI-CA events in mass activities:
Event 1820 executes preparatory selections prior to the processing of each interval in the mass activity framework. By default, no processing is provided at this point. However, you can define an installation-specific module here.
Example:
In the interval module of a mass activity, there are selections on customer objects. The mass activity is a SAP standard implementation for the interval module. For an optimization of the data selection, in event 1820, fill the buffer for the selection that is performed subsequently in the interval module.
Typically, the parallel processing object (I_BASICS-RUNKEY-OBJECT) is determined for this. A suitable mass read module can be called for this object for the current interval limits (I_LOW, I_HIGH) that writes the read data in a buffer. The single accesses that subsequently occur in the interval module can then read from this buffer.
Additional optimizations of customer-specific developments
For general performance recommendations for customers, go to: http://service.sap.com/performance
On the left side, navigate to "Performance -> Resources -> Best Practices for ABAP Performance". This displays a list of documents, in particular "Performance Do’s and Don’ts ABAP". While this document does not contain any SAP HANA-specific recommendations, it does contain recommendations that are still valid for SAP HANA.
Currently, there is an exception for SAP HANA: We recommend that you do not use Joins in combination with SAP HANA because this may have a negative on performance.
Header Data
Released On | 07.12.2015 08:08:28 | |||||||
Release Status | Released for Customer | |||||||
Component | XX-PROJ-FI-CA Contract Accounting | |||||||
Other Components |
| |||||||
Priority | Correction with medium priority | |||||||
Category | Consulting |
No comments:
Post a Comment