《SAP推薦樣例》word版.doc

Performance :MMPPSDPerformance: Customer developments in MM/WM SAP Note Number SymptomCustomer-specific programs and program enhancements (user exits) have a poor performance.The poor performance was observed when the following SAP MM/WM tables were accessed: MSEG, LTAP, EBAN, RSEG.Additional key wordsCause and preconditionsHowever, note the following warnings: Before you productively use the alternatives proposed here, you must carefully check your program with respect to functional correctness.Pay attention to the following note:In the following examples you can often find accesses to several tablesExample: SELECT * FROM LEIN WHERE = . SELECT * FROM LTAP WHERE LGNUM = LEIN-LGNUM and TANUM = LEIN-BTANR.It might be more favorable, with regard to the performance, to define a selection view on the corresponding tables (here: LEIN and LTAP ) in order to combine accesses to these two tables in one access. Solution1. Accesses to transport requestsa) via the storage unit numberIncorrect: SELECT FROM LTAP WHERE VLENR = .oderSELECT FROM LTAP WHERE NLENR = .Correct:SELECT FROM LEIN WHERE LENUM = .SELECT FROM LTAP WHERE LGNUM = LEIN-LGNUM andAND TANUM = LEIN-BTANRAND TAPOS = LEIN-BTAPS.b) via the SD delivery noteIncorrect: SELECT FROM LTAP WHERE NLPLA = LIPS-VBELN AND POSNR = LIPS-POSNR.Correct:SELECT FROM VBFA WHERE VBELV = LIPS-VBELNAND POSNV = LIPS- POSNRAND VBTYP_N = Q.SELECT FROM LTAP WHERE LGNUM = LIPS-LGNUMAND TANUM = VBFA-VBELNAND TAPOS = VBFA-POSNN.Remark:This access mode only exists if the transport orders were created on account of deliveries in Sales and Distribution. In this case the respective transport orders can be determined via the document flow table VBFA.The field LTAP-NLPLA is filled with the delivery note number via the dynamic storage bin assignment. This automatic assignment can be deactivated in WM Customizing (see movement types in WMS). This side effect must be considered when field NLPLA is used for data selection.2. Access to material documentsa) via the purchase order numberIncorrect: SELECT FROM MSEG WHERE EBELN = . and EBELP = .Correct:SELECT FROM EKBE WHERE EBELN = .AND EBELP = . AND VGABE IN (1,6,7,8,9).SELECT FROM MSEG WHERE MBLNR = EKBE-BELNRAND MJAHR = EKBE-GJAHRAND ZEILE = EKBE-BUZEI.Remark:The fiscal year must be specified so that the system has effective access possibilities via the primary index.If the fiscal year is missing, the database can no longer effectively use the item number for the search (this is a problem, especially for material documents with many items).If the operation type VGABE is specified, the values can be additionally restricted to the corresponding goods movements that are relevant.b) via the transport order numberIncorrect: SELECT FROM MSEG WHERE TANUM = .Correct:SELECT FROM LTAP WHERE TANUM = .SELECT FROM MSEG WHERE MBELN = LTAP-WENUMAND MJAHR = AND ZEILE = LTAP-WEPOS.c) via transfer requirementIncorrect: SELECT MSEG WHERE TBNUM = .Correct:SELECT LTBK WHERE TBNUM = .SELECT MSEG WHERE MBLNR = LTBK-MBLNR AND MJAHR = LTBK-MJAHR.Remark:All items of the material document are returned. It is possible to have a restriction to one individual item of the material document by specifying the material number.d) Via the vendor numberIncorrect: SELECT FROM MSEG WHERE LIFNR = .Correct:SELECT EKKO WHERE LIFNR = .SELECT EKBE WHERE EBELN = EKKO-EBELNAND VGABE = 1.SELECT MSEG WHERE MBLNR = EKBE-BELNR AND MJAHR = EKBE-GJAHRAND ZEILE = EKBE-BUZEI.Remark:Accesses to EKKO and EKBE return several datasets under certain circumstances. This must be taken into account in the program logic.With the operation type VGABE = 1, only goods movements for purchase orders are selected.As an alternative you can use matchcode object M_MEKKL in place of table EKKO (for example SELECT FROM M_EKKL WHERE LIFNR = .).Access can be improved by specifying additional restrictions.The fields purchasing organization EKORG, purchasing group EKGRP, document date BEDAT, purchasing document category BSTYP, order type BSART can make the access more selective.3. Accesses to purchase requisitionsa) via the reservation numberIncorrect: SELECT FROM EBAN WHERE EBELN = . AND EBELP = .Correct: SELECT FROM EKET WHERE EBELN = . EBELP = . SELET FROM EBAN WHERE BANFN = EKET-BANFN AND BANFPO = EKET-BANFPO.4. Access to incoming invoicesa) via the purchase order numberIncorrect: SELECT FROM RSEG WHERE EBELN = . and EBELP = .Correct: SELECT FROM EKBE WHERE EBELN = . AND EBELP = . AND VGABE IN (2,3,P). SELECT FROM RSEG WHERE BELNR = EKBE-BELNR AND GJAHR = EKBE-GJAHR AND BUZEI = EKBE-BUZEI.Remark:By specifying transaction type VGABE, the values are restricted to the relevant goods movements. With GJAHR and BUZEI, the primary index is completely utilized by RSEG.Source code correctionsPerformance: Customer developments in SD 表單的頂端SAP Note Number SymptomCustomer-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, VBFAAdditional key words Cause and prerequisitesThe 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.Solution1. 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.a) 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-vbelnAND posnr = vapma-posnr a) 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 on1. 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. a) 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-vbelnAND posnr = vlpma-posnr a) 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 = JSELECT FROM lips WHERE vbeln = vbfa-vbelnAND posnr = vbfa-posnn a) 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. 1. 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 a) 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-vbelnAND posnr = vrpma-posnr a) 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-vbelnAND posnr = vbfa-posnn a) Search for invoices with order number (preceding document, field VBRP-AUBEL):Incorrect: SELECT FROM vbrp WHERE aubel = . Correct: SELECT FROM vbfa WHERE vbtyp_n = MAND vbelv = .SELECT FROM vbrp WHERE vbeln = vbfa-vbelnAND posnr = vbfa-posnn 1. 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 = .; orSELECT vgbel FROM vbrp WHERE vbeln = .; orSELECT aubel FROM vbrp WHERE vbeln = . a) Search for shipping unit item with deliveryIncorrect: SELECT FROM vepo WHERE vbtyp = JAND vbeln = i_lips-vbeln Correct: SELECT FROM vbfa WHERE vbtyp_n = XAND vbelv = i_lips-vbelnSELECT FROM vepo WHERE venum = vbfa-vbeln Performance: Customer developments in PP and PM SAP Note Number SymptomCustomer programs and program enhancements (user exits) have a bad performance. The bad performance can be seen when accessing the following SAP logistic tables:AFRU, AFKO, AUFK, CAUFV, RESBAdditional key wordsCause and prerequisitesThe R/3 System does not contain secondary indexes to the most important PP / PM flow tables.To access them effectively you need a basic knowledge of the SAP data model. This notes contains information on the most important errors and provides alternatives.However, note the following WARNINGS:- Before you use the suggested alternatives check your program for functional correctness.Pay attention to the following NOTES:In the following examples, you often find accesses to severale.g.:SELECT aufnr FROM resb WHERE rsnum = SELECT . FROM afko WHERE aufnr = To increase the performance you should define a selection view on the corresponding tables (here: resb and afko) to combine the accesses to both table into one.Solution1. Access to order confirmation (table AFRU)a) Search for confirmation of orders (field AFRU-AUFNR):Incorrect:SELECT FROM afru WHERE aufnr = .Correct:SELECT aufpl FROM afko WHERE aufnr = SELECT rueck FROM afvc WHERE aufpl = SELECT . FROM afru WHERE rueck = Caution:From table AFVC, you receive one value per operat