Posts

SAP Note 11526 - Sales personnel in pricing.

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

SAP Note 11518 - Maintenance order: S866(CO) Error in the call costs.

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)

SAP Note 11515 - Shrinking/deleting rollback tablespaces.

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/...

SAP Note 11508 - IS-H:Runtime error CALL_FUNCTION_NOT_FOUND.

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...

SAP Note 11507 - Fields returned wrong in elec. bank statement.

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...

SAP Note 11489 - What to do when there are print problems in QM.

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...

SAP Note 11488 - RPCALCD0 terminates at function RAB.

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