Sneha Nagaraj

Symptom Partner role VE (sales personnel) cannot be used for pricing or condition determination, although field VRTNR is contained in structure KOMK. Cause and prerequisites Structure KOMG is supposed to contain the total of fields from KOMK and KOMP. However, field VRTNR is not in KOMG. Table T681F (selection fields for defining a condition table) can only contain fields that are also contained in KOMG. Solution Add a new field to KOMKAZ and use user exit MV45AFZZ to fill it. A precise description of the procedure is listed in the Implementation Guide Sales: "Modification guidelines". Key word: Pricing

Symptom Although the maintenance order should have costs, the following message occurs: S866(CO) Error in the call Costs display. Cause and prerequisites Report group 7K0O does not exist or report group 7K0O has not been generated or the user has no authorization for the display. Solution Generate the report group via Customizing Controlling --> Product cost accounting --> Reporting --> Make-to-stock --> Generate reports --> Import reports The report has the name 7K0O. Key word: S866(CO)

Symptom The customer wants to shrink tablespace PSAPROLL, as it was defined too large. Cause and prerequisites Tablespace PSAPROLL defined too large. Solution Important: - This note applies only to ORACLE7 and Oracle8!!! - The storage parameter OPTIMAL is NOT exported. You have to activate it manually afterwards sqldba lmode=y connect internal alter rollback segment storage (optimal xxM); 1. Determine the datafiles that belong to tablespace PSAPROLL sqlplus sapr3/sap SQL> select file_name from dba_data_files where tablespace_name = 'PSAPROLL'; 2. Structure export of the complete database (no table contents!!) using ORACLE tool exp: exp system/manager The user is then prompted, and can use the default settings for all questions except for the following three: (1)E(ntire database), (2)U(sers), or (3)T(ables): (2)U > 1 Export table data (yes/no): yes > no Compress extents (yes/...

Symptom The runtime error CALL_FUNCTION_NOT_FOUND occurs with copayment/down payment. Cause and prerequisites From IS-H, copayments and down payments are processed using the SmartCall method, in other words processing is event-controlled via communication tables. If a configuration is not found for an event (for example post copayment), the transaction or the report outputs a corresponding error message. If however the function module entered in the configuration table does not exist in the system (for example, incorrect syntax), a runtime error occurs since the transaction only checks whether a configuration in fact exists, and not whether its contents are correct. Solution There is probably an incorrect table entry in table TN02K: the name of the function module is written incorrectly. Analyze dump; which function module should be called. Check and execute the function configuration (RNKONFIG), and check whether the function modules exist. If need be, you can us...

Symptom The bank sends an incorrect business transaction code. This code does not exist in the system. It is not possible to process the corresonding line in the electronic bank statement. Cause and prerequisites Bank error Solution Either a) or b) a) Temporarily define the incorrect business transaction code in the system, process the statement, then delete the transaction code afterwards. b) Change the business transaction code in the database: 1.) Transaction : SE16 Table : FEBKO Application : 0001 Sender bank : 'Bank code' (15-digit) 'Account number' Statemnt ID : 'Year'(4-digit) 'Statement number'(5-digit) ShortKey : select "Output" --> Note the displayed ShortKey! 2.) Transaction : SE16 Table : FEBEP ShortKey : noted value BusTransCode : select "Output" --> Note the incorrect BusTr...

Symptom Either an incorrect inspection instruction or sample drawing instruc- tion is printed, or none at all. Errors in the print control settings in the Customizing application cannot be ruled out. If no inspection instruction or sample drawing instruction is printed, two different situations can exist: a) In the inspection lot transactions, no sample drawing instruction or inspection instruction can be printed after the sample has been calculated. b) In the inspection lot transactions, the documents can be printed, but not immediately from the stock postings. Error messages: QA162, CO412 (among others) Transaction codes: QA01, QA02, QA03, MB01 (among others) Cause and prerequisites There can be several reasons for this situation: 1. The print form does not exist, the print form does not exist in the required language nor does it exist in the client concerned, or the print form is not activated (system installation). 2. The table settings are incorrect (Customizing...

Symptom Payroll program RPCALCD0 terminates with the message: Function RAB Operation 00 Cause and prerequisites The time intervals of an absence (infotype 2001) and an inactive work contract (measure: notice of termination of work contract) overlap. Solution To implement the measure "notice of termination of work contract", you must first temporally delimit the absence. Key word: Function RAB

Symptom You want to print out more fields than those specified in the standard form, F_M40S_CHEQUE, on the check deposit list (for example, FEBSCK-KUNNR = Customer number, ...). Cause and prerequisites Outputting other fields on the check deposit form is not supported. Output is not possible for most fields because the relationship between form and check is not 1:1, but instead N:1. For example, one check could be used to pay the invoices of several customers. In addition to the fields available in the standard form, the fields in table FEBEP can be output for each check. However, only a few of the fields in FEBEP are filled. Solution If organizational measures can guarantee a 1:1 relationship, you can enter the required field in the "Issuer" field manually and print it on the form. Of course, you can do this only if you are not using the "Issuer" field. Additional key words SAPMF40S, FF68

Symptom If 'Reverse w. reference -> To BOM' for a goods issue is processed on the item entry screen, all data is deleted during GI for the cost center, for example 'G/L account' and 'Cost center', and so on. Cause and prerequisites It must be deleted since it is not sure for the new items whether all are allocated to the same cost center or G/L account. Solution Proceed as described in the manual: Process 'Reverse w. reference -> To BOM' on the first screen. Key word: MB1A

Symptom Program : SAPMK21A 1. Your own display variants entered in the Customizing are not displayed in the selection list. 2. Message KB497 Maintain table T180Z is generated Affected transactions: KSB1, KOB1, KSB2, KSB5, KOB2, CJ74, CJ76, KOB3 Cause and prerequisites a) Up to and including 2.1D, table T180Z was not always correctly updated. b) Entries may be lost through transports. Solution Please check table T180Z for all display varients, and maintain manually if required: For the cost centers/order reports/project reports, you start with Program SAPMK21A: Pgnam GTV Agr Var Zugr Ag Ma Li St SAPMK21A ... . ... A . . . . SAPMK21A ... . ... . . . . Please check whether 'A' stands in the column Zugr. If it is missing, please add it. Open item reports have to be started with program SAPMK21O. For variances on orders, use program SAPMK21V. Key word: KSB1/KOB1/CJ74

Symptom The function module G_GLDB_POSTING cancels the process with the error message GI207 'Error when writing line item index for ' or the error message GI201 'An error occurred when writing the record for table Cause and prerequisites This error message usually occurs if the customer has not reset test data before the production startup. Then, there still is data in the user-specific tables (for example GLS1, GLIDXB). If the document number ranges are reset afterwards in the sending applications, documents with numbers which have already been stored in the GLX tables are now posted directly in GLX. A 'duplicate record' occurs. Solution Often the customer has unintentionally activated the GLX. Using the diagnostic tool (TA GCD1), they should check which ledgers are posted directly under a certain transaction. If direct posting of these ledgers is not required, the GLX can either be switched off completely as a component (TO GCVO, however, caution is advisable ...

Symptom Program : SAPMA02S Error ID: aa034 Creating a sub-number leads to update termination AA034 when the system tries to update Table ANLZ. Cause and prerequisites The customer has migrated from R2 to R3; date specifications in fields ANLZ-BDATU and ANLZ-ADATU are incorrect. for example: Incorrect data rec.: BDATU ADATU 00000000 19000101 99991231 19000001 Solution 1. Correct and repeat the conversion. or 2.a. ADATU 19000001 must be changed to 19000101. b. The record with BDATU '00000000' must be deleted. See coding for utility report. Additional key words AS11 AS94 AS02 AS92 Time-dependent data

Symptom Authorization concept in FI is not complete. For example, an accounts receivable with the profile F_DEBITOREN is to be created in balance status (RFBILA00) Cause and prerequisites The reports are mostly delivered without authorization group. Solution The development request exists. Temporary workaround: 1. Define authorization group for the reports to be protected. (via SE38; change attributes for the program concerned) 2. Define authorizations for authorization object S_PROGRAM and by doing so, access the authorization group defined in 1. S_PROGRAM has 2 fields, in the field "user input", the following values are relevant for users (not programmers). - SUBMIT to carry out program online - VARIANT to maintain a variant for the program - BTCHSUBMIT to carry out program in the background. 3. Include authorization in employee profiles. Caution: before a final solution is provided by SAP, this involves a modification. This is because the authoriz...

Symptom Balance confirmation SAPF130K; SAPF130D; the results do not correspond with the balance display (FK10; FD10). Cause and prerequisites An interval is entered in the selection option (Special G/L indicator), in which " " is not contained. In these reports, standard transactions are interpreted as (SHB = " "). This constellation results in the standard transactions not being selected as well. Unfortunately, this correlation is not explained in online documentation. Solution If only standard transactions are required, all transactions with special G/L indicators not equal to " " must be excluded in the selection option for special G/L transactions. Otherwise, determine the intervals so that " " is contained. Key word: Correspondence

Symptom The values for the load of the nametab table descriptor buffer are over 100%. Individually, these are the statistical values for the buffer size used and the directory size used. The detail display in ST02 displays incorrect values: The buffer size "Used" is larger than "Available". The "Free" value becomes negative. Cause and prerequisites Error in the nametab interface in providing the statistics counter with data. Solution Repaired in Release 2.1J, 2.2D, 3.0A and later Keyword: ST02 CCMS Nametab TTAB

Symptom There is an active physical inventory for a material or a batch in several stock types but the posting block is only set for a part of the stock types. If you now count a stock type without posting block, the posting blocks are nevertheless reset for all stock types during this count although the physical inventory document for the stock types with posting block is not yet counted. Cause and prerequisites The posting block applies on storage location/batch level and thus to all stock types of a material or a batch. Solution Solving this problem would result in a significant deterioration of performance. Since this case has never occurred before so far and because the probability that it occurs is very small, no solution is implemented until further notice. Key word: Phys. inventory

Symptom ORA-1452 cannot CREATE UNIQUE INDEX; duplicate keys found when you import a dataset that was exported from a source system into a target system. Reason and Prerequisites A table in the source system contains duplicate keys, although a UNIQUE index existed there. This may result from rollback problems with ORACLE 7.0.13 in connection with cluster tables containing long raw fields. Solution Determine the keys: DESCRIBE sapr3. ; ???Fields with entry NOT NULL Determine the duplicate records (summary diplay of the records with multiple key values): select alldata.rowid, alldata.* from alldata, (SELECT , ..., FROM GROUP BY , ..., HAVING COUNT(*) > 1) keydata where alldata. =keydata. and ... and alldata. =keydata. ; For example: Table with duplicate keys is sapr3.dk with 2 key columns c1 and c2 select alldata.rowid, alldata.* from SAPR3.dk alldata, (SELECT c1,...

Symptom When Multiple Selection is chosen, only 6 lines appear for creating a purchase order. Cause and prerequisites No error! Only 6 lines are provided in the pop up. Solution Any number of additional purchase orders can also be referred to in an invoice, for example, in the Document Overview screen by selecting the function Edit --> New item --> Purchase order or Edit --> New item --> Goods receipt. This function must be performed for every additional purchase order. Starting with release 3.0, the fast entry of any desired number of purchase orders/goods receipt/delivery note numbers is possible within 'logistics-invoice check'. . For release 3.0, in the conventional MM invoice check there are no changes on the other hand, with respect to multiple selection of orders. Additional key words MRHR Key word: MR01