SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
If data is selected on the selection screen when editing the billing due list, and then the pushbutton "Save" is pressed, the billing due list is then edited without giving you a confirmation prompt.
Cause and prerequisitesThis function was not provided by SAP up to now.
SolutionAccording to warning M8108, duplicate invoice checking is based on vendor, document date, reference document no., $ and currency.
However the system does not check across companies, even though it is
the same vendor, in both invoice verification (warning M8108) and
accounts payable (warning F5117).
Documentation is incorrect.
SolutionFB01 MRHR MR01 SAPMF05A SAPMM08R MM08RI10 DUPLICATE_INVOICE
SAPFF001 DOPPELTE_BELEGE_PRUEFEN F5117 M8108
An intercompany billing document is entered for a delivery which contains an additional item.
1) Although the billing document for this item category is created with a new pricing, price PR00 is missing.
If a new pricing is then carried out on the item condition screen, the price is found.
2) If the business area is determined with the sales organisation (rule 002, table TVTA), this additional item gets the wrong business area. The business area of this item is identical to the business area of the same item in the customer invoice.
1) The incorrect distribution channel or division is transferred to pricing when creating.
2) The access to table TVTA is done with the organisational data of the customer invoice, und not with the organisational data of the internal sales organsiation.
V1108 VF01 VF04 pricing error
LV60AF0F Item category DLN GSBER
Activities for a subnetwork in the Project Information System are displayed on the same level as the network header.
Cause and prerequisitesAlthough the 'ENTRY_LEVEL' parameter is changed in routine GET_NETZ_FOR_AFVG, it is not transferred to the calling routine because it is defined as VALUE(ENTRY_LEVEL).
Solutionlogical database PSJ
If you try using the menu option 'Alternative transaction' within RPDSYS00 to branch into a table (TABL), the program terminates with the runtime error CALL_TRANSACTION_NOT_FOUND " ".
Cause and prerequisitesThe possibility of branching into a table using transaction SM31 was removed from RPDSYS00 in Release 3.0; due to a program error, the system carries on trying to call a transaction, but the name of this transaction is blank (" ").
SolutionTax and NI calculated even when the Taxable pay and NIable pay figures are negative.
Cause and prerequisitesThe tax and NI routines should not even be called when this occurs
SolutionIf a returns item is entered in a normal sales order, for example with order type TO, in addition to the items to be delivered, then a requirement is posted by the delivery as an outward stock movement for this returns item, which, of course, is incorrect.
Cause and prerequisitesThis case was not taken into account.
SolutionREN, SHKZG, SOBKZ, returns
When maintaining material master records, you can enter a greater value in the "Reorder point" field than in the "Maximum stock level" field. However, this makes no sense since the maximum stock level of a plant may not be exceeded.
Cause and prerequisitesUntil now, no check was made whether the reorder point is at most equal to the maximum stock level.
SolutionTransactions: MM01, MM02; fields: MARC-LABST, MARC-MINBE
When attempting to create a sales deal with reference to a promotion, the following error message occurs:
ERROR VK335 - "Agreement type 0030 cannot be processed using this transaction".
program error.
sales deal, promotion
If you enter relative dates for the order start date and the order finish date in the order information system, they are not considered.
Cause and prerequisitesProgram error
SolutionCO26
When you delete a work center, message CR002 is displayed:
"Work center & in plant & is still being used".
Before the work center is deleted, a check is made whether the work center is still being used in the system. This check also takes into account whether objects (for example, operations in routing) were possibly only deleted logically (key word deletion indicator or deletion flag).
Before the work center can be deleted, these logically deleted objects first have to be deleted physically in the database by means of a reorganization of the objects in question.
The check refers to the following objects:
The usage as reference in hierarchies and the usage of the capacities defined in the work center in capacity requirements is checked as well.
If you are using a template for the material number conversion and if a material number is to be converted with a template, the following error message is displayed: (CZ141) Entry is too long.
Cause and prerequisitesThe template entered was not considered.
Additional key words
CZ141
Capacity requirements planning for process order: Dispatching an operation with phases on the planning board leads to the following message in the planning log:
'No capacity requirements record found for the operation'
The operation has more than one phase. At least one of the phases has no capacity requirements (for example, because of a corresponding control key) and at least one of the phases has capacity requirements.
SolutionDuring the acquisition to a fixed asset with depreciation start date in the following year, the depreciation is already planned and posted in the acquisition year, to round off the net book value for the year-end closing according to the number of characters specified in the depreciation area for the company code.
Since no true depreciation is calculated yet, it is only possible to round down the net book value, since a negative depreciation would result if it were rounded up. Therefore, decimal amounts over 0.50 are kept.
You can set the depreciation start date in the following year, for example, when you use a depreciation calculation key with the following period controls:
08 (= by year-end = start date in the following year) or
11 (= following month) or
12 (= subsequent quarter).
T093B-RUNDEN, T090-PERBZU, OAEC, AW01
The rule for rounding off the net book value has priority over the depreciation start date rule.
Whenever you create (QI01), maintain (QI02) or display (QI03) the Q-information record you are on the 'Inspection control' screen. If you choose function F4 on the 'Inspection type incoming inspection' field, an abnormal termination occurs: 'Missing parameter for CALL FUNCTION'
Cause and prerequisitesNo authorization check of the purchasing group
Cause and prerequisitesWhen maintaining a material master record, you enter a price unit on the Accounting screen or Costing screen.
The system thereupon calculates the value on the basis of the moving average price (field MBEW-SALKV) without taking the price unit into account.
This can result in the moving average price being calculated incorrectly in the case of goods movements for materials with standard price as the price control.
Program error
SolutionTransactions: MM01, MM02; program SAPMM03M
If documents are posted in preliminary posting, the system issues a message informing you that double-account assignments are not allowed (KI249).
Cause and prerequisitesA default account assignment (for example, a cost center) is defined for the cost element. In preliminary entry, the user cancels the default account assignment (cost center = blank) and specifies a project account assignment. During posting, the cost center is again proposed through the default account assignment and at the same time the project account assignment is transferred.
SolutionFBV0, preliminary posting, default account assignments, OKB9
Message 1: Values are displayed twice. This becomes obvious if the same document number with the same item is repeatedly displayed.
Message 2: line items are misssing
ad message 1:
ad message 2:
Cause: Note 25501 implemented in advance or program error in maintenance level 2.2F.
Preconditions
ad message 1
ad message 2:
Transactions: KSB1, KSB2, KOB1, KOB2, CJ74, CJ76 or if the line item actual was called from a summary report. (Transactions: KSBB,KOC2 ).
Further key words:
Report Writer, Performance, TIME_OUT, Conversion, Summarization
SAPFK00B, FK00BE01, SAPFK21R, FK21RE01.
Missing line items, Incomplete.
You cannot create a transfer order for the delivery (transaction LT03). The note 'No items to be picked were found' is displayed.
Cause and prerequisitesThe delivery items are not relevant to WM, that is, the WM status is not set to ACTIVE for the respective items although they are to be picked with WM means.
This problem can occur both during integrated and decentralized processing.
As long as the WM status is not set to active in the delivery item, it cannot be processed in WM. The WM status cannot be set for the following reasons:
LT03
Decentralized processing
For a transfer with transaction type 300 (transfer of asset data from previous years) from a fixed asset onto which only current acquisition from the same fiscal year has been posted, to a fixed asset for which more depreciation areas are active than on the issuing asset, error message AA698 is issued:
SYST: Abnormal termination in SAPLAFAR ( T_ANLB not equal to T_ANEP )
Program error (internal table XANEP set up incorrectly.)
SolutionABUM
The variables lists / object overviews terminate when you press the F4 possible entries pushbutton.
Cause and prerequisitesIf the field you have selected with the cursor has no DDIC reference, the help module processes a termination.
SolutionUp to and including 3.0A:
If a parameter or a select option was assigned an SPA/GPA ID by adding ... MEMORY ID abc, then this was active during background processing and for a selection screen processed in the background. As a consequence, the value from the SPA/GPA memory is taken (even for initial values transferred explicitly during the SUBMIT) without the user being able to see this. The effect is particularly unpleasant in the case of background processing: if the report was scheduled here twice within the same job (and a value not equal to the initial value was transferred the first time, but the initial value was transferred the second time), the value from the first step was taken for both the first AND the second step.
As of 3.0B:
SPA/GPA handling is deactivated on the selection screens in the case of a selection screen processed in the background and in background processing. The above problems no longer occur. However, all of the programs which transferred parameters using SPA/GPA (instead of transferring them explicitly during the SUBMIT) run into difficulties.
As of Release 4.0:
In the variant maintenance, SPA/GPA handling can be deactivated for a parameter or a select option.
From 4.0 to 4.5 (and after implementing the advance correction specified in Note 74501 also in 3.1H/I):
The following occurs:
You get a variant on the selection screen. You overwrite a field supplied with a memory ID (parameter or LOW field of a select option) with an initial value. After pressing enter, the old value from the SPA-/GPA memory is there again.
4.6A to 4.6C: You overwrite a field, which has a memory ID (parameter
field or LOW field of a selection option) by using the initial value.
After ENTER, the system displays the old value from the SPA-/GPA memory.
This makes it necessary to delete all these values twice. The problem
only occurs, if you start the program using a variant.
The cause and prerequisites are known.
SolutionABAPNOTE ABAPRESERR SELECT-OPTIONS SUBMIT
Incorrect predecessor requirement after dynamic credit limit check:
A quotation item is copied into a sales order, and then both the preceding document and the subsequent document have created MRP records. The dynamic credit limit check blocks the sales order and resets all the confirmed quantities (also the respective MRP records). Quotation requirement results in the full amount.
Predecessor requirement is not set up when deleting the subsequent item. The subsequent item was blocked in the document header for the delivery ( with relevance to MRP) or had a dynamic credit limit block.
Copying into sales (with MRP records)
SolutionCredit limit block, delivery block with relevance to MRP
Can the customer define status values for the IDoc Interface?
Other termsTable TEDS1, view V_STACUST
Transaction WE47
You want to confirm specific information about processing an IDoc to the SAP System.
SolutionThe definition of separate status values is a modification and harms the concept of the status values.Separate status values must not be created as a result.
Specific information for a status value (processing milestone reached like statuses) can be transmitted in the STACOD, STATXT, STAPA1, STAPA2, STAPA3, SATPA4 and STATYP fields.If the status record is used in Version 3 (as of Release 4.0), the STACOD field is split into the three fields (STAMQU, STAMID and STAMNO). A status value can also be sent repeatedly so that as much detailed information as desired can be transferred.
There are two possible procedures:
Define a message for all of the detailed information in the T100 table.Then in the EDI subsystem, fill the STACOD field with 'SAP
You can then access the detailed information in the IDoc display of the status records.The information is language-dependent and is displayed with a long text which supports all hypertext functions.
You can occupy the first three characters in the STACOD field with a fixed prefix. You can then transfer any EDI subsystem source codes to the five remaining characters (or STAMQU < > SAP).
You can implement your own function module which transfers the format of this source code to the IDoc display of the status records.The function module is communicated to the IDoc Interface with transaction WE43.
The American calculation key NA0 (ALTMIN Tax, wiht declining balance of 15%) was delivered with the incorrect base value 'Acquisition value' (01). Declining balance keys can only calculate correctly with the base value 'Net book value' (24).
Cause and prerequisitesIncorrect delivery
SolutionA user exit has been set up for document archiving. However, a production run and a test run cannot be distinguished between when the deletion program is started manually.
Cause and prerequisitesUp to now it was not possible to start the program manually and to supply the user exit with test run/restart flag.
Note: This problem does not persist if you start archiving in the normal way using SAPF040 or SAPF048, since here, in the test case, the deletion program is not called up and the user exit is consequently not processed. The user exit can only not distinguish between a production run and a test run in the case of a restart.
Up to and including 2.2: SAPF040, SAPF040D, EXIT_SAPFF040_001, SAPFF040
As of 3.0: SAPF048, SAPF048D, EXIT_SAPFF048_001, SAPFF048
When calling transaction KSH3 for displaying a cost center group which belongs to the standard cost center hierarchy of a controlling area, error message K0127 "Set of values of node & not explicit" appears (in a dialog box).
The cost center hierarchy contains the same cost center repeatedly in the bottom nodes. If you display these bottom nodes directly with transaction KSH3, they contain other cost centers than in the display of the whole hierarchy.
Program error.
The error only occurs together with a formal defect in the bottom nodes of the cost center hierarchy. Before Release 3.0, this defect did not cause any errors.
Three measures are necessary.
The source partner function in the partner determination procedure for the sales document header is not taken into account during the following transactions:
the copying of sales documents into sales documents
the data transfer of open orders (RVINVB00)
sales order enclosure by EDI
Released orders do not allow a PRT to be deleted. PRTs are characterized as deleted but are not deleted physically.
A field is missing in the layout set.
SolutionSplit number and work were output incorrectly on split papers
Cause and prerequisitesPM_TIME_TICKET3
Shop papers of an operation split are not printed
Cause and prerequisitesControl table was read too late
SolutionIW31 IW32 IPRT RIPRCSS1
Allocation
Cause and prerequisitesProgram error
SolutionWhen maintaining matchcodes for messages, an executable transaction is not called up. This affects 3.0 FCS - installations.
In 3.0A, you can branch into matchcode maintenance but you have to specify the object (QMEL).
The following solution enables a direct jump into matchcode maintenance for the object 'QMEL'.
Note 25320 must also be sent for the FCS system.
SolutionQMEL, Plant maintenance, PM Customizing
It you call up one of the transactions that refers to a user group or a report class (either Create, Change or Display) and then change to one of the other functions (for example Display -> Change), and from there press F3, F12 or F15, you do not return to the place from which the transaction was called up.
The error does not occur if you do not switch between the functions.
During the list entry of functional locations or reference locations (transactions IL04 or IL14), the ABAP/4 runtime error BCD_FIELD_OVERFLOW occurs in function module LOCATION_EXTRACT when filling the field STACKSTUFE from the field N-STACK.
The main program is SAPMILO1.
The active program is SAPLV00F.
The field STACKSTUFE has a smaller format than the field N-STACK.
SolutionScreen sequence control
During the data medium exchange (foreign payment transactions with Austria), field 44 in sales rate 4 is defined for the bank country of the receiver.
Instead, it is filled with the country of the payee.
Program error
Solution
How can the conversion of character and paragraph formats between SAPscript texts or between a SAPscript text and an RTF file be carried out as of Release 3.0?
SAPscript, paragraph format, character format, conversion, RTF, RTF file
Reason and PrerequisitesAdditional documentation
Format conversion
Format conversion enables you to allocate paragraph and character formats in source and target text to each other and to rename them when the formatted texts are being converted. To start processing, call up transaction SE74 (format conversion). You will find this transaction as a menu option everywhere in the word processing environment in the system.
Caution:
In Releases 2.1 and 2.2, format conversion was still controlled via tables TTDCF and TTDCW. If you have already worked with the older format conversion, you should change to the new Release 3.0 procedure. To do this, start report RSTXDUMS once and once only. This report gives all of the old conversions a new form so that they can be edited using transaction SE74 (format conversion).
Character and paragraph styles (formats) can be defined in what is known as a style sheet (*.sty). They are identified by means of a "key code" (a two-digit key), and some of them by means of predefined descriptions such as "structure 1".
In the "document template" (*.dot), "styles" can be defined for paragraph formats. The names of these styles can now (unlike in Word 5.5) be more than two characters long.
In addition to the features available in 2. 0, it is also possible to determine styles for font styles (character formats) in Word 6.0.
Paragraph and character formats are defined in styles and layout sets. To ensure that a text can be output in formatted form, you must assign it a layout set. Sometimes, the text may already have been given a style as well. In this case, the formats that exist in the style are used, otherwise the formats of the layout set are used. The format tags are two-digit keys.
When RTF files are imported, the styles of a document template must be represented as the character and paragraph formats of a SAPscript style or layout set. The maintenance of these conversions is split into paragraph formats (screen after initial screen) and character formats. Exactly one paragraph style can be linked with exactly one SAPscript paragraph tag; on the other hand, one character style can be linked with up to four SAPscript character tags.
Example: The style "Combi" might contain the character formatting for bold and italics. The SAPscript style might contain only the formats "ZB" (Bold) and "ZI" (Italics). In conversion maintenance, you should in this case define a conversion from Combi to ZB and ZI.
Please note the special RTF descriptions that correspond to the standard Word descriptions (for example, "heading 1", "annotation text" etc.) and also the RTF notation of foreign characters, such as French accents or German 'umlauts'! The following characters should never be used in the names of styles: '\', '{', '}' and ';'. In both cases, import a stylesheet first:
If you have already imported a style sheet (see point 3. c)), the styles will be listed as source formats. However, the SAPscript character or paragraph formats are always proposed as possible entries for the target format.
If a SAPscript paragraph is not assigned to a paragraph format, the SAPscript default paragraph ("* " ) is used. If a target format is not defined for a character style, this style is not processed.
If you export a SAPscript text without specifying a document template, a document template is generated from the style and layout set information. There are two possibilities when you specify a document template:
RTF descriptions of Word document templates already in R/3 are intended for the conversion of SAPscript formats into the formats of an existing document. For example, Word uses the document template abc.dot. This template should also be used for texts converted from SAPscript. To do this, you must store a Word text linked with the document template abc.dot as an RTF file, for example, as xyz.rtf. In format conversion itself, enter the name abc.dot and then carry out the action "Import" (function key). In the subsequent screen, you must enter the name of the RTF file (in our case xyz.rtf). Once the transfer has taken place, the style sheet part of the RTF file is now available for format conversions.
Situation: Text ABC was formatted up to now with STYLE1 and LAYOUTSET1. Now, it should only be assigned LAYOUTSET2.
In the format conversion of SAPscript texts, the relevant paragraph and character formats are compared against each other. In the above case, the formats in STYLE1 are compared against the formats in LAYOUT2. Just an for the import of RTF files, up to four target formats can be assigned to one character format.
This format conversion between SAPscript texts can be started in the editor under the menu option "Format -> Convert..." or via the function module "EXCHANGE_ITF".
Conversions and style sheet prototypes are stored in client 00 as SAPscript text, language D, and can be transported using the mechanisms provided for SAPscript objects. To do this, create a transport request in client 00 (either manually or by using report RSTXTRAN) and release the transport.
Caution:
Format conversions and style sheet prototypes are client-independent!
Format conversions are SAPscript texts with the text object STYLESHEET and the text ID ABB.
The text name is 34 characters long:
Character 1: Type of source format:
S for style, F for layout set or D for document template
Characters 2 to 17: Source format name (as specified in the initial screen of format conversion)
Character 18: Type of target format:
S for style, F for layout set or D for document template
Characters 19 to 34: Target format name (as specified in the initial screen of format conversion)
These texts are stored in client 00, language D.
The entry in the transport request should look as follows:
R3TR | TEXT |
Example:
You want to transport the format conversion of layout set ABC into the document template xyz.dot into another system. You create a transport request with the following entry:
R3TR | TEXT | STYLESHEET,FABC-------------Dxyz. dot,ABB,D
(the minus signs in this example stand for blanks in the text name)
Alternatively, you can also execute report RSTXTRAN, and then choose the texts that you want to transport.
Style sheet prototypes are SAPscript texts with the text object STYLESHEET and the text ID RTF. They are also stored in client 00, language D. The text name corresponds to the prototype name.
Planning log of finite scheduling: 'Date not defined in factory calendar', if units in the operation are >= day.
Cause and prerequisitesWhich conversion programs (both directions) are available for SAPscript texts? How are these conversions built into the R/3 system?
SAPscript, Conversion, Format conversion, ITF, RTF, ASCII
This note is not an error note, but merely an overview of the filters available in SAPscript and how they are built into Release 3.0 and higher.
SAPscript texts are stored in Interchange Text Format (ITF). SAPscript also provides conversion programs for the text file formats Rich Text (RTF) and ASCII.
RTF files contain the entire formatting information of a text and can be both interpreted and also generated by all the common word processing packages.
In ASCII files, the text is stored without any formatting information. The only layout element available is the line break. However, different character sets are supported.
The SAPscript editors offer the following functionality:
Transfer of texts in different formats
You can execute the following from within the SAPscript editor:
You can find this function in the editors under:
or
The result of the individual transfers is as follows:
A leader with the text header information is prefixed to the output file. A text header is also constructed from this leader should the file be imported again. Following this is the text just as it is displayed in the editor that is, with all character and paragraph marks, symbols, commands and so on.
Both ITF files with a leader (see itm 1.) and those without a leader can be imported. If a header with specifications for style and layout set exists, then the style and the layout set in the text and folder editor are given these values (this does not apply to the documentation editor!).
In this case, an RTF file is created where the character and paragraph formatting from the style or the layout set of the original text are (to a large extent) retained.
Variable symbols in the ITF text are replaced. INCLUDEs and control structures are broken up, comments ignored.
If a document template is specified, then a format conversion into this document template is started from the SAPscript format (style or layout set) relevant to the character and paragraph formatting. This format conversion is described in Note 26528.
RTF files can be imported easily into modern word processing packages; in the case of older DOS programs, you will have to carry out some preliminary work first:
For Microsoft Word (as of Version 5.0), the RTF file (plus style sheet) must, for example, be converted into a Word text file using the following command:
For MS-DOS: rtf_dos file1.rtf file2.txt file3.dfv /o/c
or - " - /o/m
For OS/2: rtf_os2 file1.rtf file2.txt file3.dfv /o/c
or - " - /o/m
(/o if file2.txt already exists, then it is overwritten without the user being asked to confirm this
/c style sheet file3.dfv is created again
/m style sheet file3.dfv already exists and might be modified)
NB: the source text must have been created with a document template and stored as an RTF file. On the R/3 side, a style or layout set should exist whose character and paragraph formats correspond to those of the document template. The keys of both should be the same. If this is not the case, or if this is not possible because the descriptions in the document reference are different, it is still possible to specify a Format conversion (see Note 26528)
If "style" or "layout set" are specified in the second dialog box, then style and/or layout are set to these values (either with or without format conversion) in the text editor and folder editor.
All the formatting in the ITF text (with the exception of line feeds and tabs) is removed. The pure ASCII text is transferred exactly as it would appear in printed form (only content of text!). The only formatting possible is provided by the parameter "Line width". Variable symbols are replaced, INCLUDEs and control structures removed.
The ITF text can be converted into any character set that is maintained in spool management (SPAD).
Any ASCII file can be uploaded into the SAPscript editor. The character set of this file (i.e. its number in spool management (SPAD)) should be specified; data is then converted into the character set of the system.
Function modules for this environment
The following function modules are documented:
The program for setting up country version RSCICO02 terminates and message TK428 'Table AUFK is not part of the customizing object COAS'.
Cause and prerequisitesThis problem only arises if the program of the country version is not started in simulation mode and if an order number is required.
Due to a tightening of the checks on transport objects, the change in table AUFK cannot be entered in the order specified via view COAS.
Document posting (in background input or manual mode) terminates abnormally and the following or similar message is output: "Tuple in MC table xyz exists for an INS operation", where table xyz represents a user-defined matchcode table. OR
This error results when reloading document data after archiving.
When a check is run on table xyz it turns out that this table contains a record which does not have a corresponding record in the BSEG.
Transaction data deletion program SAPF020 or document archiving and its deletion program SAPF040D (up to and incl. 2.2) or SAPF048D (as of 3.0) were started at an earlier point in time. Furthermore, a number of fields were added to table BSEG and matchcodes (ID 9, synchronous) were entered for these fields.
Up to and including Release 3.0a a cluster deletion was always attempted if tables BSEG, BSET, BSED and BSEC had been stored in cluster RFBLG. However, a cluster deletion skips the matchcodes and does not update them.
SAPF020 SAPF040D SAPF048D OBR1 matchcode reset program RFBLG BSEG SAPF049 FB01
In the network, problems occur when checking the admissibility of the CO activity of an activity. In this case, the system issues a message that the CO activity is not valid in the fiscal year.
Cause and prerequisitesnon-calendar fiscal year
Reservations in transaction CO06 are listed twice in the totals displays (for example, for warehouse stocks and batch stocks). Totals display is inconsistent when accessed from planned order or production order at component level. The system usually displays a multiple value in totals display. However, here, it should only display the totals at plant level including plant stock (for receipts total).
Cause and prerequisitesError in member LM61VF40, LM61VF60 - only relevant after implementation of correction number P22K010039.P22 (Online vs Batch).
SolutionBackorder processing
If lists are created in AM Reporting using a sort version which contained a balance sheet item, and if this balance sheet item could not be determined, the report outputs control levels both with balance sheet item SPACE (blank) and with balance sheet item '??????????'.
This creates unnecessary control breaks.
No balance sheet version for depreciation area maintained and Program error.
SolutionVERSN_011
If you call up an object detail list in the order information system (CO26) a second time, the status filter and user filter you set the first time round are not used.
Cause and prerequisitesProgram error
SolutionIf you post to an asset using only transaction types that do not result in automatic capitalization, then no depreciation is calculated for the asset, even after manual capitalization. In these cases, the depreciation start date is not set either.
If the depreciation start date is to be set via the master data function, especially using the 'Determine depreciation start' function, or if it is supposed to take place automatically based on the capitalization date during old data takeover, then the depreciation start date is still not set.
In particular, the start date is set to the initial date when the depreciation start date is changed in the asset master record.
The 'Capitalization' indicator is not set in the default transaction type for 'Purchase acquisition'. In the standard system this default transaction type is transaction type 100.
SolutionAS02, AS91, AS92, SAPLAFAR, SAPLALTD, SAPMA02S
Message: Fields from the initial screen are to be shown in the header of the list.
Cause and prerequisitesAt present only 3 lines are available in the standard system. Therefore, fields from the initial screen are no longer repeated. Exception: The object, such as the cost center, is displayed with its text.
Planning: In later release it should be possible to output a cover sheet on which the fields of the initial screen are repeated.
As of releases > 3.0, the line-item report is to be replaced by a flexible tool with which the customer can also lay out the list header himself.
Transactions: KSB1, KSB2, KOB1, KOB2, KOB3, CJ74, CJ76
Programs: SAPMK21A, SAPMK21O
Function: Posting outgoing payment, clearing account, and similar things
Program: SAPMF05B
Field: POSTAB-VERZG
Error: BCD_FIELD_OVERFLOW
Program error
SolutionPOSTAB
When you create a collective order, the explosion key
of the BOM item is not taken into consideration
Program error
SolutionCollective order, multi-level order
The transactions KEU1, KEU2, KEU3, KEU5 terminate with a syntax error in program RK1Uxxxx (xxxx - operating concern), include FCXALF10:
Field "WACOST" unknown...
Due to a change, the includes FCXALF10 and MKGALFAD are inconsistent.
SolutionRK1US001
If the function 'Maintenance item Additional data' is called in the display mode of a maintenance item and then 'Cancel' is used to try to leave the screen, there is an error in the screen control and the transaction is exited.
Cause and prerequisites'Cancel' is not correctly programmed for additional data of the maintenance item.
SolutionPreventive maintenance plan
Under ADABAS or MSSQL, read accesses to the tables COSP and COSS can take a long time. The performance of many CO transactions (such as allocations, overhead calculation, or settlement) and of reporting is poor.
Under certain conditions, when the above tables are accessed records are not found even though they are on the database. This of course has fatal effects in the various transactions. For example, in activity price determination the cost centers that are planned still show a value of zero.
Inappropriate database selection / ADABAS or MSSQL error
Runtime
DBTUNE, ADATUNE
Transactions: KO88, CJ88, CO88, KK88, KSPI, KSU5, KSV5, KSW5, KSUB,
KSVB, KSII, KP06
In BOM maintenance, material component allocations are not saved if the allocated item is new. In certain cases, this can occur with changed items.
Cause and prerequisitesThe problem is caused by the program.
SolutionThis is corrected in Release 2.2G, 3.0B.
First, carry out the following corrections:
Component allocation
The manual dispatching did not propose finish dates and finish times, if no period was selected.
Cause and prerequisitesThere are no proposals programmed.
SolutionCM22, CM24, CM34
Double entries are created in the missing parts mail when you are using separate planning sections (storage location, batch).
Program error
Double confirmation prompt
Cause and prerequisitesProgram error
SolutionOrder information system
Name formatting according to tables T522F or T522N is not carried out correctly in report RPLKSHA0.
Cause and prerequisitesTable T001P is not read at the time GET PERNR before the RMAC module RP-EDIT-NAME is called up.
This means that field T001P-MOLGA is undefined. Because of this, name formatting cannot be carried out according to these table entries.
Incorrect Customizing.
Cause and prerequisitesThe delivered calculation key setting is incorrect.
JL09: Flag ON for 'Calculation smaller zero' --> OFF (correct)
JL10: Flag ON for 'Calculate to the day' --> OFF (correct)
Error message E150 is displayed during the order entry because no delivery date was transferred to the purchase requisition.
For assemblies and configuration, it became also necessary that purchasing data had to be maintained for a configured component.
Program error
SolutionPurchase requisition, delivery date, configuration, KBAU
1. In the list of sales activities display variant "partner for sales
activity", the name of the customer which has the same number as a
partner appears in the name of the partner
2. In the list, not all partners of the sales activity are displayed.
Program error
SolutionVC05 name
The asset value date is the deciding date in Asset Accounting, and not the FI posting date. The asset value date determines the selection of line items in reporting, the calculation of depreciation (RABUCH00), and proportional values. The use of the asset value date can lead to problems in reconciling FI and AM if the asset value date and FI posting date are in different periods. The statement on selection during a RABUCH run is only valid if the 'Catch-up method' is activated in the depreciation posting run. With 'Smoothing', the planned depreciation is distributed to the still open posting periods for which the depreciation is planned, independent of the posting date or the reference date of the transaction.
Cause and prerequisitesMissing functionality
SolutionRABEST01, RAGITT01, depreciation posting, retirement, reconciliation
When you create or change an equipment, termination TABLE_INVALID_INDEX occurs. This occurs when you call the sales and distribution screens or the configuration.
Cause and prerequisitesProgram error
SolutionIn the document flow, the value is not displayed correctly in the detailed display of the accounting document. The value is always listed with 2 places behind the decimal point.
Cause and prerequisitesOutput is not currency-specific
SolutionIn the case of special payments where entitlement has already been calculated in full, the average capacity utilization level should not be calculated any further.
Cause and prerequisitesThis is caused by a program error.
SolutionThe operation "STAB" reads data without using the 3rd national split.
Cause and prerequisitesThis is caused by a program error.
SolutionEntitlement determination
Errors in the guide or in the upgrade procedure that did not come to light until after the guide was produced.
SolutionYou should include the check register (as a list) when scheduling a
payment program run. However, there is no way to maintain the print parametzers.
The print parameters of the user who schedules the print job will
be used.
RFCHKN00, RFCHKE00, FCHN, FCHX, Check info
When you use Transaction VKM4 to select sales documents and deliveries from the credit point of view, long waiting times can occur.
Under certain circumstances, you need to set up secondary indexes for the database tables VBAK and LIKP.
SolutionThe correction in Note 26464 or Release 2.2G or 3.0B is a requirement.
This is caused by missing secondary indices for the database tables VBAK and LIKP.The following contains examples of where the secondary indexes are necessary.
A database index is necessary for the database tables VBAK and LIKP.The fields are VBAK-CMNGV and LIKP-CMNGV. Set up this index.
A database index is necessary for the database table VBAK. The field is VBAK-CMNUP. Set up this index.
Additional key words
RVKRED02, credit limit
When creating a sales document, the update cancels in program LV45UF0V in module RV_SALES_DOCUMENT_ADD.
Error text : Error in update table VBEP. RC=4.
The function Sales document - Subsequent function - Billing document does not transfer the current sales document number to create the order-related billing document.
Cause and prerequisitesNo list is created when entering a partner number.
The partner number requires a partner function
SolutionRVDEB001 VC/1 customer information
If a warning message occurs do to quantity when changing the material of an order item, and then the quantity is changed, the item category can be determined incorrectly.
The error occurs, for example, in the following situation:
Creating an inquiry
Initial situation: The customer wants a certain material, for which the material number is not yet known. This item is entered as a text item: Item category AFTX
Final creation of a quotation which refers to the inquiry. In the quotation, a material is chosen which corresponds to the required product from the inquiry.
The item category is determined again by entering a material number. AGN is normally determined correctly.
A warning message appears after entering a material number:
W: the item category is determined again (everything is still OK)
AGN is determined correctly. ENTER: a warning message appears:
W: Please consider the delivery unit: ...
If a quantity is now changed directly, the item category AGNN is determined afterwards. This should not happen. (AGNN is not allocated to the item category group at all).
v1434
It is not possible to perform results analysis on sales order items with materials of material type KMAT.
Cause and prerequisitesIn make-to-order production, the inventory and the cost of sales are notposted through goods movements because the materials are managed in a nonvaluated sales order stock. The only way to create postings in FI is to use results analysis (see Note 26456). If the sales order item consists of a material of material type KMAT, results analysis is not possible because no cost estimate exists for this material.
SolutionTransactions KKA3, KKAK
Values of an order/project should also be posted to Financial Accounting in addition to the settlement of revenues and costs of sales to CO-PA (for example, costs of sales and work in process).
Cause and prerequisitesFor make-to-order production, no posting is created in FI for the goods issue (nonvaluated sales order stock). To nevertheless be able to implement a cost-of-sales accounting in FI, it is necessary to post the sales costs.
SolutionKO88 CJ88 VA88
With NT 3.51, Oracle and R/3 Release <=3.0B, the work processes hang if the database was shut down. The work processes are not completed even if the database is booted again.
Cause and prerequisitesIf the Oracle database is shut down in the current R/3 System, a work process receives an error return code from the database (for example ORA1089 or ORA1034) for a database request. Then, the work process is restarted or enters the reconnect status if the parameter rsdb/reco_trials is set (see Note 24806) and tries to reconnect itself to the database. If the database is shut down, the work process hangs when carrying out the Connect statement. The work process is not exited. It hangs even when the database is booted again. The problem was only observed up to now for NT 3.51 and Oracle (not for NT 3.5).
The cause for this behaviour is a bug in Oracle Pro*C 1.6.4. This problem was only solved with Oracle Pro*C 2.2. At the moment it is not quite clear for which Release SAP will introduce Pro*C 2.2. We do not use the Pro*C for the connect anymore as of and including Release 3.0C (instead we use Oracle Call Interface).
DB-Reconnect
Missing batch input data for class type.
Cause and prerequisitesClass types were not dealt with in the same way during batch input.
Solutions00344 Batch input data for screen & & does not exist
The selection condition for the output VAT indicator does not work.
Check for the select option was not programmed.
RFASLM00, RFASLD02, RFASLD11, RFASLD12
Function module 'RV_REPORT_VARIANTE_SEARCH'
(searching for a variant for a report) :
In the subroutine 'REPORT_EXISTANCY_CHECK', the program checks (via table TRDIR) whether the report (parameter) exists in the system. The check is carried out with the current client (sy-mandt) against the field TRDIR-RMAND. This field contains the client under which the program in question was created. If the function module is not called in the client in which the report was also created, the exception REPORT_NOT_FOUND is returned although the program exists in the system.
For operation in multiple clients, client 000 must be the central client. Only the reports from client 000 and the current client should be displayed.
SolutionDirect mailing campaign RVADRSEL.
Transaction OMFV, program SAPMM06C:
The following phenomenon occurs when linking the text for request for quotation/quotation, vendor and contract for the purchase order:
Header texts are maintained in several source objects. However, its copying sequence cannot be controlled. The text from the source object which is found first in table T165K is always used.
Functionality is not (yet) implemented.
The option to specify a copying sequence as for item texts (table T165P) is not (yet) available for header texts.
If serial numbers and an inspection lot were created during the goods receipt, these serial numbers were not displayed during the results recording and defects recording and can also not be displayed via the inspection lot.
Cause and prerequisitesNo object list is created for the inspection lot although the serialization transaction 'QMSL' is activated in Customizing.
SolutionOriginal value entry
During the dynamic cumulation of the available capacity in capacity evaluation/capacity leveling, the available capacities of the work centers are not cumulated correctly.
Cause and prerequisitesCM21, CM25
The report for determining and updating investment supports processes only the transactions of the current year. In spite of the desired depreciation (defined in Customizing of the investment support measure), no value for previous fiscal years are determined.
Cause and prerequisitesProgram error
SolutionIf the 'paid items' parameter is selected in the check information
display under the check register, an incorrect +/- sign will appear in thw 'Deductions' column. The net amount is then incorrectly calculated.
Program error
RFCHKN00, FCHN
Transaction MIDO, program: RM07IDOC Display inventory overview
When you use F4 on the selection field "Plants for company code", all materials are proposed for selection instead of all possible plants.
Program error in RM07IDOC.
SolutionIf you repeatedly choose "Save release" when releasing blocked invoices in a multipage list, the system sometimes does not recognize whether an invoice has already been released or not. This particularly applies if the invoice of a line has already been released on page m and you now try to release the invoice of the same line on page n. In this case, the incorrect message is displayed that the invoice has already been released.
Cause and prerequisitesProgram error
SolutionMR02
In quota maintenance, an existing period is extended.
When saving you receive the message that the quota arrangement was not changed.
Error
SolutionIf you delete a long text using the editor function, it is no longer displayed in the standard task list/order/bill of material, but it still exists in the database and can be looked up with READ_TEXT
Cause and prerequisitestext_problems long_text
Key word : Reconciliation ledger
Program : LKALDU06,LKALDU07,LKALDU08,LKALDU19,LKALDU25,RKAKALF1
Description : Abnormal termination during the production run of the following reconciliation ledger
transactions: Posting
Reconciliation posting
Reversal of reconciliation posting
Transactions: KALC , KALS , KAL1
Termination : because function module ENQUEUE_EKCOFIEE is missing
Transport error:
The termination occurs in the production run (not in the test run) of almost all reconciliation ledger transactions. The reason is that the lock objects EKCOFIEE and EKCOFIES were not transported.
Reconciliation ledger
Under certain circumstances, it is possible that negative stocks are posted in the system although this is unwanted.
An example is the withdrawal of components for a run schedule header.
Providing you do not exit the run schedule header transaction after posting the withdrawal and you are using the same components again in the next document that is posted, then the material master is not read for these components. This leads to incorrect data which is then used for the computation of quantities.
Program error.
SolutionIn function module FUNCTION MATERIAL_PRE_READ_MBEFU, you have to change both the interface and the source code.
Please insert the import parameter KZRFB in the interface.
Import parameter Refer.field Refer.type Default Optional
-----------------------------------------------------------
KZRFB MTCOM-KZRFB SPACE X
In Include MM07MFT0, you have to change FORM routine TRANSAKTION_INITIALISIEREN.
Error when displaying the material document that was posted as goods receipt for the purchase order.
When you display the material document, the special stock indicator is not displayed for both items. Thus, it looks as if the receipt was posted into the normal stock. However, the actual posting was made correctly, that is, into the respective special stock.
Error in screen SAPMM07M 0221.
Solutionbrbackup runtimes are longer after the OS upgrade from DEC UNIX 2.x to 3.2x.
Cause and prerequisitesThis is caused by a new cpio.
Solution