SAP R/3 форум ABAP консультантов
Russian ABAP Developer's Club

Home - FAQ - Search - Memberlist - Usergroups - Profile - Log in to check your private messages - Register - Log in - English
Blogs - Weblogs News

Performance: Customer developments in SD (Note 185530)



 
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> Performance tuning | Производительность
View previous topic :: View next topic  
Author Message
admin
Администратор
Администратор



Joined: 01 Sep 2007
Posts: 1636

PostPosted: Mon Sep 10, 2007 12:37 pm    Post subject: Performance: Customer developments in SD (Note 185530) Reply with quote

Symptom
Customer-specific programs and program enhancements ("User Exits") have a bad performance. The bad performance is noticed during accesses to the following SAP SD tables: VBAK, VBAP, VMVA, LIKP, LIPS, VBRK, VBRP, VBFA


Cause and prerequisites
The R/3 System contains no secondary indexes to the most important SD transaction data tables in the delivery. Instead, the R/3 System has proprietary index tables (sales document indexes, for example the tables VAKPA and VAPMA, matchcode tables for example M_VMVAB, M_VMVAC or matchcode views for example M_VMVAA, M_VMVAE), which allow an efficient access.
In order to use these efficiently a certain basic knowledge of the SAP data model is required. For this this note lists the most important errors which are made and it offers alternatives.

However note the following WARNINGS:

Before you use the listed alternatives productively, you must check your program closely for functional accuracy.
The sales document indexes must be maintained correctly in your system. This is usually automatically the case, however, there can be inconsistencies. Carefully read and follow Notes 128947 and 178328.

Consider the following NOTES:
In the following examples, there are often accesses to several tables, for example:
SELECT FROM vakpa WHERE kunde = ... SELECT FROM vbak WHERE vbeln = vakpa-vbeln.
It can increase the performance, to define a selection view on the corresponding tables (here: VAKPA and VBAK) in order to combine the accesses to the two tables in one access.


Solution

1. Accesses to sales orders (tables VBAK, VBAP)
a) Search orders for customer number (field VBAK-KUNNR):
Incorrect: SELECT FROM vbak WHERE kunnr = ...
Correct: SELECT FROM vakpa WHERE kunde = ...
SELECT FROM vbak WHERE vbeln = vakpa-vbeln.

b) Search order items for material number (field VBAP-MATNR):
Incorrect: SELECT FROM vbap WHERE matnr = ...
Correct: SELECT FROM vapma WHERE matnr = ... SELECT FROM vbap WHERE vbeln = vapma-vbeln
AND posnr = vapma-posnr

c) Other search helps for sales orders offer the matchcode tables and views M_VMVAx, x. = A, B, C, ... M; for example search for purchase order number of the customer, description and so on

2. Accesses to deliveries (tables LIKP, LIPS)
a) Search for deliveries with customer number (field LIKP-KUNNR):
Incorrect: SELECT FROM likp WHERE kunnr = ...
Correct: SELECT FROM vlkpa WHERE kunde = ... SELECT FROM likp WHERE vbeln = vlkpa-vbeln.

b) Search for delivery items with material number (field LIKP-MATNR):
Incorrect: SELECT FROM lips WHERE matnr = ...
Correct: SELECT FROM vlpma WHERE matnr = ... SELECT FROM lips WHERE vbeln = vlpma-vbeln
AND posnr = vlpma-posnr

c) Search for deliveries with sales order number (preceding document, field LIPS-VGBEL):
Incorrect: SELECT FROM lips WHERE vgbel = ...
Correct: SELECT FROM vbfa WHERE VBELV = ... and VBTYP_N = 'J' SELECT FROM lips WHERE vbeln = vbfa-vbeln
AND posnr = vbfa-posnn

d) Other search helps for deliveries offer matchcode tables and views M_VMVLx, x. = A, B, C, ... M; for example search for goods issue date, picking date, transportation planning date and so on.

3. Accesses to invoices (tables VBRK, VBRP)
a) Search for invoices with customer number ("payer") (field VBRK-KUNRG):
Incorrect: SELECT FROM vbrk WHERE kunrg = ...
Correct: SELECT FROM vrkpa WHERE kunde = ... SELECT FROM vbrk WHERE vbeln = vrkpa-vbeln

b) Search for invoice items with material number (field VBRP-MATNR):
Incorrect: SELECT FROM vbrp WHERE matnr = ...
Correct: SELECT FROM vrpma WHERE matnr = ... SELECT FROM vbrp WHERE vbeln = vrpma-vbeln
AND posnr = vrpma-posnr

c) Search for invoices with delivery number (preceding document, field VBRP-VGBEL):
Incorrect: SELECT FROM vbrp WHERE vgbel = ...
Correct: SELECT FROM vbfa WHERE vbtyp_n = 'M'
AND vbelv = ... SELECT FROM vbrp WHERE vbeln = vbfa-vbeln
AND posnr = vbfa-posnn

d) Search for invoices with order number (preceding document, field VBRP-AUBEL):
Incorrect: SELECT FROM vbrp WHERE aubel = ...
Correct: SELECT FROM vbfa WHERE vbtyp_n = 'M' AND vbelv = ...
SELECT FROM vbrp WHERE vbeln = vbfa-vbeln
AND posnr = vbfa-posnn

4. Other accesses in SD:
a) Document flow:
Incorrect: SELECT vbelv FROM vbfa WHERE vbeln ...
In table VBFA only the preceeding document is used to search for the subsequent document (for example, delivery for order). Searching the other way makes no sense with this table since the preceding documents (for example, order for delivery) are stored directly in the document tables. Thus reading in table VBFA is a one-way street.
Correct: SELECT vgbel FROM lips WHERE vbeln = ...; or SELECT vgbel FROM vbrp WHERE vbeln = ...; or
SELECT aubel FROM vbrp WHERE vbeln = ...

b) Search for shipping unit item with delivery
Incorrect: SELECT FROM vepo WHERE vbtyp = 'J' AND vbeln = i_lips-vbeln
Correct: SELECT FROM vbfa WHERE vbtyp_n = 'X' AND vbelv = i_lips-vbeln
SELECT FROM vepo WHERE venum = vbfa-vbeln.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> Performance tuning | Производительность All times are GMT + 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG.
Every effort is made to ensure content integrity. Use information on this site at your own risk.