1.10.11

SAP Note 28226 - Error message KN043 during report call

Symptom:

When calling a report from the settlement transactions, from the variance calculation or WIP calculation, you get error message KN043 'Report & does not exist'.
The error can also occur in the archive evaluation of internal orders.
The missing report could be: 6000, 7KO1, 7KO2, 7KO5, 7K0C.
Transactions: CO88, KKS1, CJ88, KOR3.
Programs: SAPLKO74, SAPLKKB2, RKAARCS2.

Other terms ----- SUPPORTGUIDE 20010214111707 -----


REPORTWRITER,
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS

Reason and Prerequisites

A report which should be called as described above must fulfill three requirements:

    1. it must exist in the current client
    2. it must be up-to-date
    3. it must be in the report list of the respective application
Solution
The three conditions above ensure:
the import or generation of the report using the Report Writer
or the entry of the Customizing transactions of the respective application or the report in the report list of the respective application.
The latter can be achieved either with a complete Client Copy of table TKKB1 or using the following transactions:

Report transaction for maintaining the report list ------ -------------------------------------------
6000 OKR1
7K0C OKR1
7KO1 OKR2
7KO2 OKR2
7KO5 OKR2
7OV0 OKR1
7OV1 OKR1

SAP Note 28224 - "Incorrect" extended help for SAPF130D/SAPF130K

Symptom:

If you call "Extended help" (Help -> Extended help) for report SAPF130D or SAPF130K and then branch to the Customizing transaction "Forms for Correspondence" (transaction OB96) using "Proceed",

the following information is given in Release 2.1*: "Reference cannot be cancelled"

or

the incorrect Customizing transaction OB33 'Change View "Credit Management Field Group Fields": Overview' is called in Releases 2.2*, 3.00 and 3.0A.

Additional key words

SAPF130D, SAPF130K, F.17, F.18, balance confirmation

Cause and prerequisites

The transaction (OB33 instead of OB96) was defined incorrectly.

Solution
The error is corrected in Release 3.0B.

Correct the transaction call in the help function

Transaction: SE38
Program: SAPF130D or SAPF130K
Object components: Documentation -> Change

(documentation for finding the place where changes must be made)
Edit -> Find term: OB33
<(> INCLUDE FUNKTION_AUSFÜHREN <)>
<(> IF &DEVICE& = 'SCREEN' <)>
<(> Proceed. <)> <--- change
<(> ENDIF <)>

SAP Note 28221 - ABAP/4 runtime error RAISE_EXCEPTION in SAPLKALP

Symptom:

When you post interest payments to a project, a termination occurs through ABAP/4 runtime error RAISE_EXCEPTION 'ERROR_IN_COEP' in function module K_COEP_COMPLETE, program SAPLKALP

Cause and prerequisites

Business transaction 'KZRI' for posting directly from FI into CO.

Solution
Program error SAPLKALP, corrected in Release 3.0B. You can make the following advance correction:

Additional key words

Update termination

SAP Note 28219 - MMIM: Enter with reference to BOM/batch '*'

Symptom:

During a goods movement (for example, GR other), the function "Enter with reference to BOM" works incorrectly if an item exists already in the document and if the batch of this item was selected with the batch function '*'. The error: If this entered item has line item number 1, the components exploded to the bill of material (reservation) are incorrectly displayed with line item numbers 3,4... (instead of the correct: 2,3...) on the selection screen. All other actions lead to error message "Please check table FUSS: Entry & does not exist".

Cause and prerequisites

Program error.

Solution
Please change Include MM07MFL0.

SAP Note 28217 - Missing short texts in the Business Navigator

Symptom:

In the Business Navigator, transactions SB01, SB02, all short texts except for the texts of the application fields are missing. The message "Not labeled" is displayed instead.

Cause and prerequisites

The data, along with many other R/3 tables, was deleted by mistake during a clean-up action shortly before the tables were delivered. The short texts are missing in all 3.0A systems.

Solution
Data file on sapserv3/4/5:
Find the data file for transport SAPK30ATN2, and a Read Me file
explaining how to import the data file, on these servers in directory
/dist/permanent/Note.0029447.
This transport contains all the missing data, not just those for
the Business Navigator.

Additional key words

3.0A data loss

SAP Note 28216 - WBS has no scheduled dates after scheduling

Symptom:

If all activities assigned to a WBS element are scheduled and if the WBS element is scheduled, the scheduled dates of the WBS element are deleted.

Cause and prerequisites
Solution
Program correction

Additional key words

WBS scheduling

SAP Note 28215 - MR01: State central bank indic. in the Netherlands

Symptom:

UKSymptom In the Netherlands, the state central bank indicator must also be maintainable for domestic invoices in foreign currency (usually this

Cause and prerequisites

UKCause and preconditions

Solution
UKSolution

Additional key words

UKAdditional key words

SAP Note 28212 - Cross company gives error message KI203

Symptom:

Create a sales order. For example, sales organization 9000. Enter plant 0001, for example, on the item screen. Jump into the account assignment screen for the item. Enter the profit center. The above error message occurs. This crosses companies, that is, sales organization 9000 belongs to company code 1000 and controlling area 1000, and plant 0001 belongs to company code 0001 and controlling area 0001 This means that the check is incorrectly performed with the controlling area of the sales document header.

Cause and prerequisites
Solution
You can make the following advance correction as of 2.2B:

SAP Note 28211 - Changing control keys in activity with pur. order

Symptom:

Various subsequent errors may occur, if you change the control key of an externally processed activity or element in the network for which a purchase order already exists so that the activity/element loses its as external processing character.

Cause and prerequisites
Solution
You must not permit a change of the external processing character in existing purchase orders.

SAP Note 28207 - MR01 - Purchasing statistics: No freight update

Symptom:

Symptom

When freight charges were posted for a vendor, the info structures S011 and S012 were not updated because in this case the transfer structures to LIS were not filled properly.
In particular, header conditions were also passed on.

Cause and prerequisites
Solution
See below.

SAP Note 28204 - MF50: Specifying a default capacity category

Symptom:

It was not possible to specify a default capacity category in a planning table containing capacity data.

Cause and prerequisites

This was not programmed

Solution
The capacity category relevant to scheduling is used as a default.

29.9.11

SAP Note 28199 - Texts of text object 'BELEG' are not posted

Symptom:

Texts of text object 'BELEG' are not posted.

Cause and prerequisites

Program error.

Solution
Insert the lines indicated with "<-- new in program FV45TF0T.

SAP Summary Symptom The release status display may be incorrect under certain circumstances. Customizing OMGQ - Release strategy - Select a release s

Symptom:

Documentation created in the customer system is incomplete in 3.0FCS or 3.0A after upgrading the R/3 System.

Cause and prerequisites

The report RSGESCAD is incorrect. (affects 3.0FCS and 3.0A)
After the actual upgrade, the report imports customer documentation that was rolled out before the upgrade with the report RSPUSCAD into the new system.

Solution
Correction to the program code of RSGESCAD and execution in the background.
This can be carried out subsequently.

Additional key words

Upgrade Maintenance level Installation

SAP Note 28193 - Incorrect rel. statuses (OMGQ) in rel. procedure

Symptom:

Summary

Symptom

The release status display may be incorrect under certain circumstances.
Customizing OMGQ - Release strategy - Select a release strategy - Release statuses
Example:
Group Strategy 01 S1 ...
01 S2 ...
91 M1 ...
91 M2 ...
If you select strategy M2 during the access followed by strategy S1, the release statuses of strategy M2 were displayed for strategy S1. If the selection was made in reverse order, the release statuses were displayed correctly.

Cause and prerequisites

The access to the internal table to which the release statuses of each selection are written was incorrect because the table was not sorted in ascending order.

Solution

Sort after APPEND in internal table XT16FK.

Header Data



Release Status:Released for Customer
Released on:19.01.1997 23:00:00
Master Language:German
Priority:Correction with medium priority
Category:Program error
Primary Component:MM-PUR-REQ Purchase Requisitions
Secondary Components:MM-PUR Purchasing

Affected Releases

Software
Component
Release
From
Release
To
Release
And
subsequent
SAP_APPL
30
300
30A

SAP Note 28192 - KP97: No update of activity records

Symptom:

When you copy activity types, no data is updated although no error messages are written to the log. However, the object number tables (ONR00, ONRKL) were updated so that an update termination may occur during another copy procedure (with INSERT ONR00 or INSERT ONRKL).

Cause and prerequisites

The data in the target version is to be copied for more than one cost center. You copy a cost center on which more than one activity type is planned.

Solution
1. The error does not occur if you always only specify one cost center as the target.
2. Program correction in 3.0B. You can make the following advance correction.

SAP Note 28190 - 'Phone number' field is not cleared in RFQ

Symptom:

When you save the request for quotation for the first vendor, the 'Phone number' field is not cleared.

Cause and prerequisites

Program error

Solution
The error was corrected with correction number P22K010123 2.2G and correction number P30K022154 in 3.0B. You can make the following advance correction: In program SAPMM06E, Include MM06EF0O, FORM routine OKCODE_BUCH:

Additional key words

ME41

SAP Note 28189 - Certificate: Incorrect tolerances in batch specif.

Symptom:

Incorrect supply source of sample data (tolerances) on the certificate, if the batch was first searched for in the sales order or delivery note via the selection criteria of the batch determination and if the batch was then determined without classification selection.
Data from the batch determination is printed. In this case, however, data from the material classification is expected.

Cause and prerequisites

Program error

Solution
Program correction in function module QC01_BATCH_OBJECT_NUMBER.

Additional key words

Tolerances, selection criteria, data origin 02, general characteristic, batch specification, quality certificate

SAP Note 28187 - HR-DPF: Pfändung und Weihnachtsgeld

Symptom:

Die Freibeträge bei der Pfändung vom Weihnachtsgeld werden in der Abrechnung falsch ermittelt oder überhaupt nicht.

Weitere Begriffe

RPCALCD0

Ursache und Voraussetzungen
    1. Die Lohnart des Weihnachtsgelds ist in der Tabelle T512W in den Verarbeitungsklassen 72, 73 und 74 nicht richtig geschlüsselt.
    2. Die Lohnart /147 für den Vergleich mit dem Arbeitseinkommen ist falsch oder überhaupt nicht vorhanden.
    3. Es werden zwei oder mehr Benutzerlohnarten für das Weihnachtsgeld verwendet.
Lösung
zu 1: Die Lohnart des Weihnachtsgelds muß in Verarbeitungsklasse 72 mit 2, in 73 mit 3 und in 74 auch mit 3 geschlüsselt sein.
zu 2: Das Arbeitseinkommen wird in der Lohnart /147 gesammelt. Alle Lohnarten, die für den Vergleich des Weihnachtsgelds mit dem Arbeitseinkommen verwendet werden, müssen in der Kumulationsleiste in der Spalte 47 geschlüsselt sein. In der Spalte 47 darf die Lohnart des Weihnachtsgelds nicht geschlüsselt sein.
zu 3: Da das Weihnachtsgeld mit einem festen Betrag verglichen werden muß, muß das Weihnachtsgeld in einer Lohnart stehen. Wenn Sie mehrere Lohnarten für das Weihnachtsgeld haben, müssen Sie diese erst in einer speziellen Summenlohnart zusammenfassen. Die Pfändbarkeit schlüsseln Sie in der Summenlohnart, bei den Einzellohnarten darf in den Verarbeitungsklassen 72, 73 und 74 nichts eingegeben werden.

SAP Note 28186 - What does the profile SAP_NEW do?

Symptom:

SAP updates the profile SAP_NEW with every functional upgrade. The profile can be assigned to the users in the upgrade postprocessing phase, but the meaning of the profile is not particularly clear to all administrators.

Cause and prerequisites

The meaning of this profile is not self-explanatory.

Solution
Motivation for delivery profile SAP_NEW
---------------------------------------

There are some functionalities that are not protected by an authorization check, although they are worth protecting. SAP is slowly working on closing these "gaps", that is, further authorization checks are being installed. The authorization profile SAP_NEW contains authorizations for all check objects that were implemented in previously existing functions. To ensure upward compatibility for every upgrade, the delivery profile SAP_NEW was implemented. All users should have the profile SAP_NEW in their master record. This ensures that a user may execute the same functions after the upgrade as he could before it.

Administrator's task after the upgrade
--------------------------------------

Directly after the upgrade, the user administrator should go through the profile SAP_NEW and leave only the subprofiles in this composite profile, which were generated for releases greater than the source release. The individual profiles SAP_NEW_ should be retained in order to later be able to verify which autorization was introduced in which release.

Caution
-------

The profile SAP_NEW does not contain the authorizations for functions that are new in that upgrade.

Especially the subprofile SAP_NEW_30E should never be assigned to the users in higher releases because it contains a start authorization for all transactions.

As of Release 4.6 SAP_NEW is not so important any longer if the profile generator is used and the SU25 is used for upgrade postprocessing of the user roles.

SAP Note 28185 - Process order: Dispatching planned orders

Symptom:

You cannot dispatch a planned order with master recipe.
Message number CY350: Order : No start date given.

Cause and prerequisites
Solution
Program correction

SAP Note 28179 - Requirements date not set for material component

Symptom:

The requirements date for a material component is initial.

Cause and prerequisites

The requirement quantity of the material component is 0.
Components for parts to be discontinued/successor components can have a quantity of 0.

Solution
Program correction

SAP Note 28177 - Rep.points for run sched.header:Missing rout.data

Symptom:

Data from the routing is missing when you create a run schedule header with reporting points.

Cause and prerequisites

Not all data is entered directly in the routing, but copied from the work center.

Solution
Correction P30K018767

SAP Note 28175 - Questions regarding the authorization concept

Symptom:

Questions which occur regarding the authorization concept:
1) How do you delete the user SAP*?
2) How do you transport profiles and authorizations?
3) Authorization check when starting transactions (table TSTCA)
4) Which authorization objects are checked?
or, How can the administrator find out which authorization objects
are checked with which values for a particular function that is to be checked?
5) A short introduction to the topic authorization check?
6) What naming convention is used for authorizations?
7) What can a user do if he is not authorized for a function?
8) What does the standard SAP profile SAP_NEW do?
9) Why are blocked users unblocked by an incorrect logon at midmight?
10) How can a customer let his/her own coding run after user logon?

Cause and prerequisites

Information request which is not or only partially covered by the System administration manual.

Solution
1) See note 4326 (Currently, only released internally in SAP. Contact your SAP Basis Consultant if you need this Note.)
2) See note 11013
3) See note 15253
4) See note 18529
5) See note 20534
6) See note 20643
7) See note 23342
8) See note 28186
9) See note 32068
10) See note 37724

SAP Note 28171 - No reaction when double-clicking on WBS elements

Symptom:

There is no reaction if you double-click on the WBS elements on the project planning board.
You can possibly also not perform other functions with WBS elements.

Cause and prerequisites

The problem described above occurs if you call logs from the project planning board.

Solution
see below

Additional key words

CJ27, CJ2B

SAP Note 28169 - F4: Standard search in the matchcode is not set

Symptom:

After pressing the button/icon "New search" in the restriction popup of the matchcode search, a new search method is chosen. However, this is not used as the standard search method when the matchcode help (matchcode ID) is next started.

Cause and prerequisites

A search method (ID) is only used as the standard when first starting the matchcode help, if it is set as the standard using the function "Define standard".
Note: if the module HELP_VALUES_GET_WITH_MACO is used in a user-defined F4 matchcode search, the note is valid up to Release 3.0F.

Solution

If you want to set a new search method as the standard, you must perform the function "Define standard". The respective button/icon appears on the right, next to the button/icon "New search".
Further actions:

Also check whether there are any inconsistent entries in table MCDEFID using Transaction SE16 or SE17 for displaying tables. Such entries have the value SPACE in the MCID field or they have values which do not exist anymore.

Where necessary, delete these entries with the procedure described below.
To avoid further inconsistencies, change line 85 in the Include LSHL2U10 - function module MATCHCODE_ID_SELECT - as shown below.

Additional key words

F4, matchcode, standard search method, choice of matchcode ID

SAP Note 28168 - F4: Matchcode does not find any entry possibilities

Symptom:

For Matchcode F4 Help, neither the popup for selection of the search method (matchcode ID) nor the restriction popup or data are displayed if the F4 Help is not called via the abbreviated dialing. However, the popups and the data do appear if you search via abbreviated dialing (=.).

Cause and prerequisites

A matchcode ID was previously defined with the standard ID, for which no data exists.

Solution
Run the search once using abbreviated dialing =. where this dialing should be saved as the standard ID

Additional key words

Matchcode, F4 Help, default matchcode ID


SAP Note 28165 - RGCAUS00: Cons entries in the Company Report

Symptom:

No consolidation entries are displayed when you start a standard report which is limited to a single company.

Cause and prerequisites

The standard logic is designed to not show any consolidation entries on company reports since this has no meaning from the point of view of the individual company. This is due to the fact that these entries usually always affect two or more companies. Hence, only in group reports do the entries provide meaningful values.

Solution
If you want to deviate from this logic, you must modify the report program RGCAUS00.


The modification has been changed in passing in the edited version of this Note, dated Apr. 8, 1998, so that the consolidation entries are displayed only if the evaluation for values in the group currency has been started. The previous version of the modification led to mixing of the various currencies in the case of evaluations using local currency amounts because only group currency amounts are available for consolidation entries.
Source code blocks "LOOP AT GESVBUND" and "LOOP AT GESPOS" are also to be adapted to the current form of this note.

Additional key words

OC53

SAP Note 28161 - Abnormal terminat. when saving on planning board

Symptom:

If you choose "Save" on the planning board, an abnormal termination occurs with error message CALL_FUNCTION_PARM_MISSING when you call function module MD_POST_PLANNED_ORDERS; parameter CUOBX is not defined.

Cause and prerequisites
Solution
Interface correction of function module MD_POST_PLANNED_ORDERS.

SAP Note 28159 - Change in storage loc. for WM-relevant comp.

Symptom:

If the storage location for a component in the production order was changed from a non-WM-relevant (WMS) storage location to a WM-relevant storage location this did not give rise to a new transfer requirement in WM.

Cause and prerequisites
Solution
Corrected in the ABAP Include LCOBCFC1.

SAP Note 28156 - Error in scheduling collective order

Symptom:

If components of a collective order which give rise to the order are configured (characteristics valuation), the order is not scheduled correctly.

Cause and prerequisites

Program error

Solution
P30K020590

Additional key words

Scheduling, collective order, multi-level order

SAP Note 28154 - Duplicate record when creating multi-level PO

Symptom:

Duplicate Records on RESB file when creating a collective order

Cause and prerequisites

Program error

Solution
Correction P30K020589 or make changes to Include LCOSDFB1 as follows

Additional key words

RESB, collective order, termination, DUPLICATE RECORD

SAP Note 28149 - FD11: Bill of exchange payment requests displayed

Symptom:

During account analysis (FD11), the bill of exchange payment requests are displayed on screen 160.
Since the receivables are displayed as well, you get the wrong impression of a higher receivable balance.

Cause and prerequisites

This case was not considered.

Solution

Corrected in 3.0B.

Additional key words

SAPMF42B, T074U, balance display

SAP Note 28148 - Table category processing during language import

Symptom:

Different handling of the individual table categories during the language import

Cause and prerequisites

Different processing with the import of the language-dependent tables into the available clients, dependent on the table type.

Solution

When importing the language-dependent tables, these tables must be differentiated depending on the delivery class of the tables, into which clients they may be imported.
The delivery class of a table is determined in the dictionary (Transaction SE11).Also see the existing F4 help for the delivery class.
Importing Customizing tables in Clients < > 000 is problematic because customer entries must not be overwritten.

As of Release 3.0, language-specific tables are imported as follows:


A. Import of client-specific tables

    1. general check:
    The respective client is protected against cascading
    if field CCNOCASCAD = 'X' in table T000), then no import.
    2. Check against the table category:
    Class S Insert/Update into all clients except 1.
    Class E Insert/Update into all clients except 1.
    Class W Insert/Update only into client 000
    Class C Insert/Update only into client 000
    Class G Insert/Update into client 000
    Insert for all clients < > 000, except for 1.
    Class L No Insert/Update
    Class A Insert/Update only into client 000

B. Import of client-independent tables

    1. Check against the table category:
    Class S Insert/Update
    Class E Insert/Update
    Class W Insert/Update
    Class C Insert with full language import
    No Insert/Update with delta language import
    Class G Insert
    Class L No Insert/Update
    Class A No Insert/Update
As of Release 4.6C language-specific tables are imported as follows:
As of Release 4.6C, the language transport was changed on the tp/R3trans transport tools. The table types have the importance as described in Note 2857.

SAP Note 28147 - Dunning form for real estate

Symptom:

The dunning form for financial assets management is not used or the fields specific to real estate are not printed.

Cause and prerequisites

In the dunning program, the dunning form is only used for financial assets management if:

    1. financial assets management is active (global parameter for company code),
    2. an entry is available in the grouping key (key for dunning grouping) in the customer master record (correspondence); (field MHNK-CPDKY is filled with the specifications from the grouping key.) This grouping must consist of fields - Contract number VERTN Länge 13
    - Contract type VERTT Länge 1(in this sequence!) (Customizing financial accounting).
    3. As of Release F3.03, the forms in Customizing must no longer be maintained in the "Financial Assets Management forms" column but in the left "Dunning forms" (standard) column. The sample forms (for example, F150_DUNN_01_VVI) can still be used, which, for example, print the contract number. The seperation of the dunning forms (documents from standard and documents from real estate management) is done via the dunning areas. If you enter a dunning area in the rental agreement (payment data screen), this is transferred to the documents. Via the dunning area, a suited dunning procedure/form can then be accessed. Even here, however, the fields specific to real estate are only used if grouping is set as described above.
Solution
Maintain the grouping key and enter it in the customer master record.

Additional key words

Dunning form, contract number, financial assets management, real estate

SAP Note 28145 - Using technical inspection report RKACSHOW

Symptom:

After apparently incorrect data was displayed in a report, you can inspect the data on the level of the physical tables (or views on this). As a result, you can make a decision on whether the error is to be searched for in the report definition or in the incorrect data. This way, the cause of the error can be significantly narrowed down, for example for a message to SAP, and its processing significantly speeded up.

Cause and prerequisites
Solution

Report RKACSHOW allows a data analysis of the tables relevant to CO reporting. The data for this can be selected in many ways.

Key:
* only from Release 3.0
() only up to Release 2.2


Selection screen:
---------------------------------------------------------------------
| Object number [1] |
| |
| Controlling area [2] |
| Cost center [3] |
| Activity type [4] |
| |
| Order / Network [5] |
| Activity [6] |
| |
| Project [7] |
| WBS element [8] |
| |
|*Sales order [9] |
|*Sales order item [10] |
| |
| Restrictions |
| Ledger [11] |
| Value type [12] |
| Version [13] |
| Fiscal year [14] |
| Cost element [15] |
---------------------------------------------------------------------
A group of specifications must always be made on the selection screen. The groups are also separated optically in the selection screen:
- [1] The object number contains all of the necessary specifications for the report
Report
- [2] - [4] create reports using a cost center / activity type
Example: we are intersted in cost center 2000 in
controlling area 0001. This cost center carries primary
costs so that the activity type remains empty.
- [5] - [6] create reports using an order and a business transaction
- [7] - [8] create reports using a project
- [9] - [10] create reports using a sales order


To restrict the data selected for the specified cost element itemization even further, the fields [11] - [15] are available. There is not a required entry here, unlike [1] - [10].
Example: You only want to see data from cost element 400000 and enter cost element 400000 for [15].

  • ad [1] The object number consists of the object type (positions 1-2), and further specifications that are necessary for the unique identification of the cost object. The object number of a cost center (object type KS) contains the controlling area (positions 3-6) and the cost center name (from position 7) for the further functional specification.
    Example:
    Enter object number KS00010000002000.
    • KS The cost object is a cost center
      The object types are defined in the domain J_OBART
    • 0001 controlling area
    • 0000002000 cost center
  • ad [4] activity type
    Apart from individual values, there are also the following possible entries here:
    : Only activity-independent values are selected
    * : All activity types are selected (as of Release 3.0)
  • ad [9] only as of Release 3.0
  • ad [10] only as of Release 3.0


The following selection screen appears after executing the report:

Selection screen
In the indented entries, line items are displayed and the totals records in the others. From the totals record display, you can branch back into the line item display. Choose the data list relevant for your case by double-clicking:

COKA cost element: Control data cost element
COKP cost element: Primary planned control data
COSPA cost element: Cost totals - ext.postings - all periods
COSPD cost element: Total ext.costs - settled from this
* COVP cost element: Line item period-related and doc.header
* COVJA cost element: line items by year + doc.header all periods
* COOI open items management: Line items
* V_COFP line items (cash flow) and document header
* COEPD cost element: Line item settlement nonvaluated w.status
* COEPBR cost element: Line item settlement valuated
COKS cost element: Secondary planned control data
COSSA cost element: Cost totals - int.postings - all periods
COSSD cost element: Total int.costs - settled from this
COVP cost element: Line item period-related and doc.header
COVJA cost element: line items by year + doc. header all periods
( COOI ) open items management: Line item
COKR cost element: Control data statistical values
COSRA cost element: Totals stat.key figures - all periods
COVPR cost element: OI stat. key figs - period-related + doc.header
COVJRA cost element: OI stat.key figures by year - all periods
COKL cost element: Control data activity type
COSLA cost element: Totals activity types - all periods
COVPL cost element: Line item act.types for each-rel.+doc.header
COVJLA cost element: EP OI act.types by year+ + CoCde - all periods
COSTA cost element: Totals activity prices - all periods
COVPT cost element: Line item act.prices for each-rel.+doc.header
COVJTA cost element: OI act.prices by year u. +doc.header - all periods
COSBA cost element: Totals variances/calculations of imputed costs - all periods
COSBD cost element: Totals for variances/imputed costs - settled from this
COVPB cost element: Line items for variances/imputed costs and document header
*COANZ index 'Objects for which down payment requests were made
*FMSU FI-FM totals records
* V_COFP line items (cash flow) and document header
*RPSCO project information database: Costs, revenues, finances


Importance of some tables:
COSPA = CO table Totals records Primary costs
All periods = CO-external postings (for example from FI)
COSSA = CO table Totals records Secondary costs
All periods = CO-internal postings (for example,
from internal activity allocation, distributions and so on)
COVP = CO tables View (line items COEP and
line item document headers COBK) Period-related
COSRA = CO table Totals records of the statistical
key figures from All periods
COSLA = CO table Totals records Activity types
All periods


Example:
Display after double-click on COSPA:
---------------------------------------------------------------------
| Objekt.............. KST 0001 2000 General Cost Center |
| File COSPA |
| ----------------------------------------------------------------- |
| LEDNR OBJNR GJAHR WRTTP VERSN KSTAR |
| ----------------------------------------------------------------- |
| 00 KS00010000002000 1995 04 000 0000400000 |
| ----------------------------------------------------------------- |
| HRKFT VRGNG VBUND PARGB BEKNZ TWAER |
| ----------------------------------------------------------------- |
| COIN H DEM |
| COIN S DEM |
| COIN 999999 S DEM |
---------------------------------------------------------------------
you can now choose a data record by double-clicking and display all the fields of the data record:
---------------------------------------------------------------------
| Objekt.............. KST 0001 2000 General Cost Center |
| Field contents COSPA |
| ----------------------------------------------------------------- |
| Field name Field contents |
| ----------------------------------------------------------------- |
| LEDNR 00 |
| OBJNR KS00010000002000 |
| GJAHR 1995 |
| WRTTP 04 |
| VERSN 000 |
| KSTAR 0000400000 |
| HRKFT |
| VRGNG COIN |
| VBUND |
| PARGB |
| BEKNZ H |
| TWAER DEM |
| MEINH kg |
| WTG001 2,001,150.00- DEM . . . WTG016 0.00 DEM |
| WOG001 2,150.00- DEM . . . WOG016 0.00- DEM |
| WKG001 0.00 DEM . . . WKG016 0.00 DEM |
| WKF001 0.00 DEM . . . WKF016 0.00 DEM |
| PAG001 0.00 DEM . . . PAG016 0.00 DEM |
| MEG001 0.000 . . . MEG016 0.000 |
| MEF001 0.000 . . . MEF016 0.000 |
| MUV001 X . . . MUV016 X. |
---------------------------------------------------------------------
The importance of the individual fields can be found in the ABAP/4 dictionary (transaction SE11).
Example:

    1. Field WRTTP
  • Importance of the field WRTTP ?
    Procedure: SE11, table COSPA, ->
    ==> Result: WRTTP = value type
  • Possible values of the field WRTTP ?
    Procedure: SE11, table COSPA, -> Fields -> Double-click on WRTTP -> Data element -> Domain -> Fixed values
    ==> Result:
    01 Plan
    04 Actual
    05 Target
    10 Statistical plan
    11 Statistical actual
    ...und others.
    2. Field VRGNG
  • Importance of the field VRGNG ?
    Procedure: SE11, table COSPA, -> Fields
    ==> Result: VRGNG = CO activity
  • Possible values for VRGNG ?
    Procedure: SE11, table COSPA, -> Fields -> Double-click on VRGNG -> Data element.
    ==> Result: Value table T022 or TJ01

    Further procedure:
    SE16, table T022 ==> display possible values
    SE16, table T022T (T for texts) ==> Display possible values and
    their meaning.
    3. Meaning of some fields:
    WKGxxx = Value in Controlling area currency Total
    MEGxxx = Quantity Total
    xxx = Periods in the period block (PERBL).
    For periods <= 16: PERBL = 16


Application:
Execute a cost center cost element report in controlling area 1. Incorrect values are displayed for a cost center 2000 for cost element 400000. You now want to check whether this is due to incorrectly posted data in the database Call transaction SE38 and execute report RKACSHOW. Enter KS00010000002000 as a cost object number or 1 for controlling area and 2000 for the cost center. Since it is primary costs for cost element 400000, do not enter an activity type. Execute the report. In the selection screen that now follows, choose COSPA. In the display of the totals records, you can now choose a data record and display the values of the individual fields (double-click or 'Details') or change to the line item display ('Line item'). From there, you can also display the documents for the line items, subdivided into document headers and line items.

Explanation of some of the fields of RPSCO
Table RPSCO is the basis of all drilldown reports in the
Project System. This is also called the project information database.

Field Explanation
-----------------------------------------------------------------------
OBJNR Internal object consisting of
an object type and number

LEDNR Values in a ledger are updated in
one currency.
Example:
Controlling area currency USD in ledger number 0001
Object currency DEM in ledger number 0002
Posting of 300 USD in period 8.
Exchange rate DEM/USD: 1,5

LEDNR TWAER WLP008 WTP008
0001 USD of 300 300
0002 USD 450 300

WRTTP Value type (plan = 01, actual = 04) see fixed values of the domain)

TRGKZ Object indicator
The object indicator is used for classification of the
costs objects.

ACPOS Value category
The value category consists of a group or
a range of cost elements and/or commitment items.

VORGA business transaction (see Transaction BS33)

VERSN Plan version (0=original plan)

ABKAT Category variance/calculation of imputed costs
(for example 01 = price variance, 04 = quantity variance)

BELTP Debit category
0
1 Costs and credit payments
2 Revenues and debit payments
3 Balance sheet item

Additional key words

Reporting, example error messages:
GR392 Row & in key figure block & does not contain any data
GR438 No appropriate selection entries exist
GR463 No values were found in the selected interval
GR551 No data exists for your selection
GR601 & & does not contain any data pages
GR605 List is empty (function cannot be executed)
incorrect data, no data, Report Writer, incorrect numbers, instructions, information ----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_AMOUNT, SGRW_RC_STRUCTURE, SGRW_DATA
SGRW_OM

SAP Note 28142 - Scheduling type '3' deletes dispatched dates

Symptom:

Repetitive manufacturing: If you dispatch an operation, the date that was specified for dispatching is overwritten by midpoint scheduling.

Cause and prerequisites
Solution
Program correction

SAP Note 28141 - NAST: Messages not found after changes

Symptom:

A message is found in an application transaction (MESSAGING).
The conditions are then changed and the message is no longer found!
If the condition is now reset, the message is however no longer created. Determination analysis also displays that the message was found.

Cause and prerequisites

Deletion flag is not reset!

Solution
Use corrections P30K022253 and P30K074343.

Additional key words

NAST, MESSAGING

SAP Note 28140 - Termination in collective order, table STACK

Symptom:

If you repeatedly branch from the collective order overview to the component list or activity list, the termination message 'Internal table STACK is not filled' is displayed.

Cause and prerequisites

Incorrect entries in table T185

Solution
Maintain table T185 (SM31):
Provide all entries of the category
Program: 'SAPLCOKO', function code 'NBAU', enter a value '1' for ST.
This initiates the setup of a stack that can then be reduced correctly when you change the screen.

Additional key words

V0050, collective order, STACK

SAP Note 28139 - Derivation table ignores offset and length

Symptom:

In CO-PA Customizing, you entered an offset and a field length for a characteristic on the detail screen for the derivation table (transaction KE4K). (That is, only part of the table field entered under "master data field" is supposed to be transferred to the relevant characteristic for derivation.)
In characteristic derivation using the derivation table in CO-PA, the system ignores the offset and length. It always assumes an offset of 0 and the length of the source field.

Cause and prerequisites

Error in Program LKEAAU01. Offset and length are taken from Table NAMETAB without adapting them to the entry in Table TKEAN.

Solution
Corrected in Release 3.0B. In earlier releases, change Program LKEAAU01 (Form RESET_PLAN_DEPENDANT_ENVIRON) as follows (changes are marked with <-- ):

Additional key words

Derivation, CO-PA characteristic derivation, KE4K, V_TKEAN, TKEAN

SAP Note 28136 - Fin.sched.: Insert operation with mult.reservat.

Symptom:

Planning board: Insert operation contains errors

Cause and prerequisites
Solution
See note 28338

Additional key words

Finite scheduling

SAP Note 28134 - MR01: Incorr. withholding tax base for credit memo

Symptom:

In table T059Q, the 'Net base for contributions' indicator is selected for the withholding tax base calculation. When you post a credit memo, the withholding tax base was calculated incorrectly (if it was not entered).
The tax amount was added to the gross amount instead of being subtracted. Another consequence was a negative withholding tax exempt amount.
Sympton during the document display:
A: The field value is too great. A display is impossible.
Message number 00020

Cause and prerequisites

Program error

Solution
Program correction

SAP Note 28133 - Fin.sched.: TIMEOUT during Insert operation

Symptom:

Planning board: The insertion of an operation into an available commitment situation causes an infinite loop in the program.

Cause and prerequisites

The indicator 'Insert operation' is active in the planning strategy.

Solution
Source code corrections

Additional key words

Finite scheduling

SAP Note 28129 - Errors with entry tool in standard network

Symptom:

If you select the "Entry tool" indicator in the standard network profile, the entry tool is still not activated.

Cause and prerequisites

The incorrect program is entered in table TCA62 for task list application 'N'. The table entries are incorrect.
The original idea was that the entry tool can be defined by the user. This, however, was rejected because there are not too many screens that must be gone through.

Solution
Change tables TCA60 and TCA62 and adapt the table entries.
For Release 2.2, you first have to set the indicator 'Table maintenance permitted via SM31' for table TCA62 in the ABAP/4 Dictionary.
- Create screens for the tables via transaction SE51.
- Then change the entries for task list application 'N'.
- The program name SAPMCPDO is incorrect. Change it to: SAPLCPDO.
Make the corresponding entries for the entry tool or input facilities in the standard network profile.

For Release 3.0, you have to change tables TCA60 and TCA62 in the ABAP/4 Dictionary.
-> Table maintenance permitted
- Create the corresponding screens for the tables.

Include the following entries in TCA60 for application 'N':
Application Sequence key Object
N FCHECK F
N OC0001
N OC0002
N OC0003
N OC0004

delete all other entries for 'N'.

Include the following entries in TCA62 for application N:

Application Sequence key Verif.no. Program Screen group Panel
N FCHECK 1 SAPLCFDF RD 0100
N FCHECK 2 SAPLCFDF RD 0120
N OC0001 1 SAPLCPDO V2 0020
N OC0001 2 SAPLCPDO V2 0021
N OC0002 1 SAPLCPDO V2 0020
N OC0002 2 SAPLCPDO V2 0021
N OC0002 3 SAPLCPDO V2 0023
N OC0003 1 SAPLCPDO V2 0023
N OC0004 1 SAPLCPDO V2 0022

delete all other entries for 'N'.

Additional key words

Standard network, project, activity

SAP Note 28126 - Including reference routing into production order

Symptom:

Symptom

When you include the reference routing into a production order, you can use any standard task list without the selection criteria for an order, which are checked during the order creation, being taken into account.

Cause and prerequisites
Solution
Change the source code in Include LCOSDU16:

SAP Note 28124 - SAPFV56S, DBIF_RSQL_INVALID_CURSOR, run-time error

Symptom:

SAPFV56S, DBIF_RSQL_INVALID_CURSOR, run-time error
Termination while running transcation VT01, VT02 or VT03
when a route is entered in header general data.

Cause and prerequisites

In the FORM ROUTE_ABSCHNITTE_GENERIEREN there are two nested SELECT/ENDSELECT statements with an ORDER BY PRIMARY KEY in the first one.

Solution
Modification of Coding

Additional key words

FORM ROUTE_ABSCHNITTE_GENERIEREN

SAPM Note 28117 - Incorrect depreciation for multiple-shift factors

Symptom:

During the depreciation calculation, incorrect depreciation amounts are calculated when you are using multiple-shift factors. Furthermore, the expired useful life can be calculated incorrectly during the fiscal year change.

Cause and prerequisites

Program error.

Solution
Corrected in 2.2H and 3.0B
Advance correction in LAFARF00 and LAFARU04 (syntax check only in SAPLAFAR).

Additional key words

Depreciation, multiple shift

SAP Note 28115 - Transact. OVF1: Division descript. read incorrectly

Symptom:

The division description is not displayed in transaction OVF1.

Cause and prerequisites

Incomplete program

Solution
Please insert the lines indicated with "<-- new.

SAP Note 28114 - Entry SAPLCOVG,ARBD,FU,*,0004,* missing in T185

Symptom:

If in the network you call the work detail screen on the external element overview, a message is displayed that entry SAPLCOVG,ARBD,FU,*,0004,* is missing in table T185.

Cause and prerequisites
Solution
Add the entry in table T185.
Please call the table maintenance transaction of table T185 with SM31.
Position the cursor on SAPLCOVG,PE,ARBD.
Overwrite PE with FU and press ENTER.
Please specify a correction number and save your changes.

SAP Note 28110 - "Display object" in the component overview

Symptom:

The "Display object" function is activated in the general component overview, the component overview for the operation and the missing parts overview. This is an error.

Cause and prerequisites

Program error

Solution
In the statuses "AAKOMP", "AAKOMPVG", "AAVERF", "HVKOMP", "HVKOMPVG", "HVVERF", "VVKOMP", "VVKOMPVG" and "VVVERF" of function group "COCU", you must deactivate the "Display object (OBJA)" function in the "Environment" menu. Then regenerate the statuses.

SAP Note 28104 - Calling ME39 from transaction MD04

Symptom:

Symptom

MD04:
Within the current stock/requirements list, you could not use the function 'Display element'. A termination occurred because some table entries were missing in Customizing for the transaction ME39.

Solution
see below

Additional key words

ME027 06007
DELIVERY SCHEDULE ME33

SAP Note 28093 - Error in RMMRP000 - incorrect plant ...

Symptom:

Report RMMRP000 for batch or background planning on plant level (corresponds to MD01 online) ignores the parameters entered.

Cause and prerequisites

Release 3.0 up to and including 3.0A.
As of 3.0B and until Release 2.2, the error described here does not occur.

Solution
The order of two form routine calls in report RMMRP000 is to be reversed:

Additional key words

Materials planning; MRP

SAP Note 28092 - Asset retirement: Subseqnt sales revenues or costs

Symptom:

No financial accounting document is created for subsequent sales revenues and costs.

Solution
The transaction entered via the Asset Accounting merely allows you to display a complete display in the retirement list. The corresponding accounting document must also be entered via financial accounting.

SAP Note 28091 - CO888 Internal error when creating ITAB

Symptom:

During the second takeover of a task list into the order (if the operations of the task list taken over before were not deleted), the system terminates with error message CO888: 'Internal error when creating ITAB'.

Cause and prerequisites

Program error

Solution
Error recovery

Additional key words

IW31, IW32, RIPLKO10

SAP Note 28089 - HP 48AL Autoloader supported as of 3.0E/2.2I

Symptom:

BRBACKUP cannot change the tape in HP Autoloader 48AL. The command "mt -t offline" does not change the tape. The tape remains in a so-called "semiloaded" status.

Cause and prerequisites

This device type has two driver address types:
Data driver address - that is called with cpio/dd and control driver address - that is called with the "mtx" command. Using the "mtx" command you can import/export a certain tape and call up the status,
among other things.
With HP-UX 10.xx, the "mtx" command is available on all HP platforms, but must first be installed in addition to the special driver software. If you have further questions, please contact the HP Competence Center.

Solution
Store the following two shell scripts in the directory /usr/sap//SYS/exe/run:
mtxrew.sh:
---------
CURR_SLOT=`mtx -d $1 -s | grep Drive | awk ' { print $3 }'`
mtx -d $1 -u $CURR_SLOT -l $CURR_SLOT

mtxoff.sh:
---------
CURR_SLOT=`mtx -d $1 -s | grep Drive | awk ' { print $3 }'`
NEXT_SLOT=`mtx -d $1 -s | grep Drive | awk ' { print $3+1 }'`
mtx -d $1 -u $CURR_SLOT -l $NEXT_SLOT

Adjust the init.sap profile as follows: rewind = "mtxrew.sh $"
rewind_offline = "mtxoff.sh $"
tape_address =
tape_address_rew =

Parameter tape_pos_cmd remains unchanged in this case: tape_pos_cmd = "mt -t $ fsf $"
This solution is supported as of BRBACKUP version 3.0E/2.2I.

Caution:
Make sure that one more tape than necessary for the backup is placed in the autoloader to prevent the failure of the last mtxoff.sh call. You can use a scratch tape that you load at the end, but do not use.

The HP autoloader can also be called via BACKINT/OmniBack. Please contact HP for more information.

SAP Note 28088 - Ab.term. after cancel. during date spec.int.proc.

Symptom:

If you secify the value 4 (user decision between earliest and latest start) in the strategy profile for "Internal processing dispatching", a dialog box is brought up when dispatching an internal processing operation, in which the user can decide between dispatch on the earliest or on the latest date. If the user selects "Cancel" in this dialog box, the program terminates abnormally.

Cause and prerequisites
Solution
This solution involves implementing the following program changes.

SAP Note 28086 - Duplicate key when saving the WF definition

Symptom:

When saving the workflow definition, a crash occurs for 'Duplicate key'.

Cause and prerequisites

The problem occurs if blocks were manipulated in workflow with 'Cut' and 'Move', and if the workflow is defined in different languages.

Solution
see source code corrections

SAP Note 28081 - Missing PO statistics for third-party PReqs.

Symptom:

A purchase requisition with item category 'S' which is assigned to a sales order is converted into a purchase order. A change is made here (for example, the delivery date is changed. After the purchase order has been saved, the data of purchase order statistics (quantity ordered, purchase order number, purchase order date) is missing in the purchase requisition.

Cause and prerequisites

Program error. The purchase order statistics are updated correctly in the function module ME_UPDATE_REQUISITION_PO. However, the function module SD_PURCHASE_CHANGE_ORDER (which updates the changes in the order and also the purchase requisitions) is called up after this. The purchase order statistics are overwritten again here.

Solution
Corrected in 2.2G or 3.0B. You can make the following advance correction by moving the startup of function module ME_UPDATE_REQUISITION_PO behind that of function module SD_PURCHASE_CHANGE_ORDER (see below).

Additional key words

ME21 ME22 ME52 ME53 ME57 ME58

SAP Note 28080 - Incorrect business area or missing profit center

Symptom:

1) The business area in the billing document is not plant-specific
(T134G)
2) The profit center in the billing document is missing

Cause and prerequisites

Program errors, caused by a correction in 2.2F from note 22771

Solution
Corrected in 2.2G/3.0B

Additional key words

VF01 VF04 VBRP-GSBER VBRP-PRCTR

SAP Note 28077 - Update term. in certificate profile, swapped txts

Symptom:

Characteristic short text are not taken over from the certificate profile or the sequence of the characteristic texts is swapped or update termination SAPSQL_ARRAY_INSERT_DUPREC occurs in QC05_QCVMT_INSERT, if the certificate profile contains characteristics with texts (inconsistency of tables QCVM and QCVMT).

Cause and prerequisites

The update termination can occur under the following conditions:

    1. A characteristic has an additional text which was maintained with the function "More texts".
    2. You delete the characteristic.
    3. You then create another characteristic and provide it as well with an additional text.
    4. After you have posted the reference, the text is no longer found when you access the certificate profile again.
    5. If you delete the characteristic again, create a new one again and provide it with an additional text, a update termination occurs when you post.

The texts can be swapped under the following conditions:

    1. You create or change a certificate profile: You enter a new characteristic and provide it with an additional text.
    2. You enter another characteristic with a smaller sort number and also enter an additional text for it.
    3. After you have savedthe the texts of the two new characteristics are swapped in the display transaction or change transaction.
Solution
    1. Change program SAPMQCPA, Includes MQCPAF01 and MQCPAF02: see below
    2. You can detect and correct inconsistencies between the files QCVM and QCVMT with a report that is given below as example program.
    3. Incorrect allocations (characteristic texts are swapped) can only be detected with expert knowledge. You then have to correct the allocations manually with the transaction for changing a certificate profile. A report which lists all characteristics with characteristic texts from certificate profiles is of help here. This report is also given below as example program.
Additional key words

Transactions QC01, QC02, QC03
Alternative texts disappeared
Alternative texts were swapped
Short text
Text
SAPLQC05
LQC05U06

SAP Note 28074 - Dump when creating coll.order with discont.parts

Symptom:

Symptom

When creating a production order for a collective order with discontinued parts, the program terminates with a dump after the order quantity and dates have been specified: BCD_FIELD_OVERFLOW

Cause and prerequisites

Program error

Solution
P30K017073

SAP Note 28073 - Finite scheduling: Avail. capa. change not copied

Symptom:

Planning board: If you interactively change a capacity, it is not copied internally if you did not dispatch or deallocate orders/operations for this capacity since starting the planning board.

Cause and prerequisites
Solution
Source code corrections

Additional key words

Finite scheduling

SAP Note 28072 - Environmt -> Excep.mess. during req.for quot./quot.

Symptom:

If you choose the menu option Environment -> Exception messages for the request for quotation or quotation, error message 06 006 is displayed:
'This function is not defined'.

Cause and prerequisites

Missing entries in tables T168F and T168.

Solution
Add the following entries to tables T168F and T168:

Table T168F:
Tran FCod ------Masking------------ Processing routine
TrCat AcCat ScrGr Cl1 Cn2
A MESS X X X OKCODE_MESS
AG MESS X X X OKCODE_MESS

Table T168:
Tran FCod TCat AcC SG 1 2 Scrn AcC FCod Calli. Window
A MESS * * * 321
A MESS * * * 1 320
AG MESS * * * 321
AG MESS * * * 1 320

Additional key words

ME41, ME42, ME43, ME47, ME48, ME49

SAP Note 28071 - Default trans. types when settling invent. measures

Symptom:

When you settle capital investment measures (transaction KO88 / CJ88), error AA816 or AA820 occurs.

Cause and prerequisites

The default transaction types for the settlement of capital investment measures are not set at all or only incorrectly.

Solution
Please set the following default transaction types in Asset Accounting Customizing.
Transaction description Transaction type
Delimit. inv. measure -> AuC 114
Old asst data set.of inv.meas. 338

SAP Note 28068 - Simultaneous posting from SD to CO-PA and CO-CCA

Symptom:

Up to and including Release 2.2, invoices from SD could be posted simultaneously to CO-PA and also cost element by cost element to CO-CCA or CO-OPA. Either the automatic account assignment (transaction OKB9) or the default assignment in the cost element master record is used for posting to the CO-CCA and/or CO-OPA applications.
In Release 3.0, posting by cost elements to cost centers or to orders only functions when CO-PA is not active. If CO-PA is active, normally only the profitability segment will be posted to, even though a flexible assignment, cost center + profitability segment, is in principle possible.

Cause and prerequisites
Solution
The functionality possible up to Release 2.2 can be accessed as of Release 3.0 using a standard substitution. This substitution is delivered by SAP and the customer only needs to activate it.
If you have not used a substitution before, proceed as follows: Transaction OKC9, Function "New entries". Enter your controlling areas. In the column "Callup point", enter "0001" each time; in the column "Substitution" enter "0_SCO10" each time (please take note of the '0' and 'O'), and in the column "Activation level" enter a "1" each time. After you save this, you have restored the 2.1/2.2 functionality.
If you presently use substitutions, you will recognize this in transaction OKC9 because at least some of your controlling areas are already assigned to substitutions with other names and an activation level "1" or "2". You must change the already existing substitutions for these controlling areas. To do so use the menu options, Environment -> Substitution. Enter the name of your substitution. On the next screen select step 001 and push the function button "Insert entry". On the next screen select "Only exit" and hit 'Enter'. Leave the block 'Prerequisite' empty for the substitution step to be changed and enter the value "SCO10" in the field "Substitution exit" in the "Substitutions (if prerequisite is met)" block. Finally, push F3 until you are prompted to save and then save the change.
Important: In Release 2.2, it was also possible to post on a real order
in addition to posting into CO-PA via the automatic account assignment
determination. This is not possible as of 3.0, under any circumstances,
because the data cannot be properly updated on two account assignment
objects. For this reason, you need to enter a statistical order or a
cost center during the automatic account assignment determination.
The cost center is then statistically posted as of 3.0 according to the
account assignment method (see also Note 41103).

Additional key words

Transaction VF02, VF04

28.9.11

SAP Note 28066 - ME90, MB90: No F4 help for message type

Symptom:

On the selection screens of transactions ME90 (Print/Transmit Messages: Purchasing Documents) and MB90 (Inventory Management Message Processing), there is no "possible entries" pushbutton (F4) on the field 'Message type'.

Cause and prerequisites

Parameter P_KSCHL refers to the field NAST-KSCHL, for which the foreign is not maintained. If you maintain the foreign key, however, all messagetypes for all applications are displayed. This is of limited use to the user.
A sensible F4 help for the field "message type" (and, incidentally, alsofor the field "message application") is not available until Release 3.0B. It uses the new ABAP language element
AT SELECTION-SCREEN ON VALUE-REQUEST (new as of 3.0). This F4 help cannot therefore be installed in existing 2.2 releases.

Solution
The only solution for 2.2 is to maintain the foreign key for the database field NAST-KSCHL. The checking table has already been entered in the Data Dictionary; the foreign key need only be saved.

Additional key words

P_KSCHL, NAST-KSCHL

SAP Note 28064 - SAProuter during update/upgrade

Symptom:

During update/upgrade, the new SAProuter cannot be written into the executables directory. For example, the error message
cp: cannot create saprouter: Text file busy

Cause and prerequisites

The SAProuter runs and the operating system requires disk space for paging.

Solution
either:
- Shut down the SAProuter before the PUT and restart it afterwards
or:
- Rename the current SAProuter (mv saprouter saprouter.busy)
- Carry out the update
- Delete saprouter.busy after the next time you restart SAProuter

SAP Note 28062 - Sched. rough-cut plan. profile using fact. cal.

Symptom:

The factory calendar is not taken into account when scheduling the rough-cut planning profiles.

Solution
Program correction

SAP Note 28061 - Duplicates in the profile

Symptom:

Profile entries do not seem correct.
The effect of profile entries depends on changes elsewhere in the profile.
Error message in the stderr file:
sapparam: Duplicate Profile Parameter "...

Cause and prerequisites
Technical context

In the C kernel, the module 'sapparam.c' is responsible for processing the profiles. It contains default values for most profile parameters.
If a profile value definition occurs repeatedly, the following rules are valid:
Parameters which are not prepared in the C kernel (sapparam.c) must also not occur in DEFAULT.PFL.
All parameters may occur in the instance profile, regardless of whether they are in the kernel or the DEFAULT.PFL or not.
If parameters occur in DEFAULT.PFL twice:
There is no message.
Only the last value is taken.

If parameters occur in the instance profile twice, the effect depends on the release:

Up to and including 2.2 :

There is an error message after 'stderr' (file in the work directory.)
When displaying tables, the parameter appears repeatedly.
There is no definite rule for which value is taken.

As of Release 3.0:

There is no error message.
The last value is taken.
Error search:

    1.
    Read the stderr files in the SAP work directory.
    2.
    On operating system level:
    sapparar pf= or
    sapparar pf= all or
    sappfpar pf=< profile_file> or
    sappfpar pf= -check
    3.

In R/3:
Report RSPFPAR or
Report RSPARAM

Solution
Repair profile and then restart R/3.

Additional key words

sapparam.c, Profile, SAPPARAM, RSPFPAR, RSPARAM, SAPPARAR, SAPPFPAR

SAP Note 28058 - Stock overview: comma instead of period

Symptom:

In the stock overview, stocks are displayed in the format ____.___.___,___ although you have specified in the user settings that the decimal places are to be separated by a period.

Cause and prerequisites

Program error

Solution
Problem corrected in Release 3.0B.

Additional key words

Report: RMMMBEST; transaction: MMBE

SAP Note 28056 - Table maintenance: No entry for charact. w/o values

Symptom:

If no values are defined for a characteristic and if no other values are explicitly allowed, you cannot make any entries in table maintenance CU60.

Cause and prerequisites
Solution
Corrected in LCUD2F04.

Additional key words

CU60, SAPLCUD2

SAP Note 28053 - NAST: no F4 Help for output types

Symptom:

Message Control: On the screen for displaying messages (program SAPDV70A, screen 100), no possible entries are displayed for the output types.

Cause and prerequisites

The output determination procedure is not filled. The function module for the possible entries pushbutton cannot locate output types for an empty output determination procedure.

Solution
For an empty output determination procedure, the function module must be called differently. In this case, all output types are displayed for the current application

SAP Note 28050 - VL71 print view CONTROL_FORM is invalid

Symptom:

When you perform the "View" function from transaction VL71 (menu path: Certificate creation, Certificate dispatch) abnormal termination message TD443 "CONTROL_FORM is invalid since START_FORM is missing" is issued when processing quality certificates

Cause and prerequisites

Incorrect query logic in processing program RQCAAP00.
The print view function was only supported from transactions for certificate profiles.

Solution
Change in report RQCAAP00 or similar change in your own program, if you have not used the standard program.

Additional key words

SD70AV2A
Output type LQCA LQCB
Certificates, certificate profile
Certificate view

SAP Note 28047 - User exit activation during doc. number conversion

Symptom:

The conversion user exit in DMS is only activated by screen 0101.

Cause and prerequisites
Solution
Correction P22K010028 in 2.2G.
Please also see note 28043 for bills of material.

SAP Note 28044 - PM order: flow control: SAPLCOIH, IMKL, ...

Symptom:

IW31 IW32 IW38 Flow control SAPLCOIH IMKL

Cause and prerequisites

Transport error

Solution
Check the appropriate entries in tables T185F and T185.

SAP Note 28042 - Drill-down rep.: Numbering for >99 columns in report

Symptom:

Module - R/3 Business Planning and Control
Transaction: Change Drill-Down Report
The following problem occurs in reports with more than 99 lines when you use the function 'Sort lines':
1. Page 0 of 0 - no page number
2. The next line after line 99 is displayed without numbering and is then continued again from the beginning with 1, 2 .... When scrolling, the following message is output 'Please enter a valid value'.
The problem also occurs when you use the functions 'Sort characteristics', 'Sort key figures', and 'Sort columns' within drill-down reporting.

Cause and prerequisites

ad 1. Program error in 2.2.
ad 2. Dialog box is designed for a maximum of 90 entries.

Solution
ad 1. (The problem only occurs in 2.2)
Choose the fullscreen editor for program SAPLKEBR and screen 1000 in transaction SE51, position the cursor on the line "Page __ of __" and choose 'Edit -> Edit lines -> Delete line' to delete the line.
Then make the source code changes described below to reduce the size of the screen.
ad 2. (Releases 2.2 and 3.0)
First change the domain from NUMC2 to NUMC3 for data element RKE_RFLG with transaction SE11. You can then change the length of the heading to three. Activate the data element.
Then choose the fullscreen editor for program SAPLKEBR and screen 1000 in transaction SE51.
Release 2.2:
The field for entering the numbers must be moved 1 byte to the left and extended from two to three characters.
Branch to the change mode, mark field RKB1B-NUMMER01, move the field one byte to the left and then extend the field by adding an underline "_". Generate the screen. adding an underscore "_".
Release 3.0
The field can be extended with the "Field Attribute" button: Change
Vis. lenth to 3.
Then correct the following error message in both releases:
Transaction SE91, Change message class KH.
Message 045:
Sort number & is not allowed (only numbers: 1 to 990)
Message 348:
Enter a number between 1 and 990.

Additional key words

Transaction KCR0, KE30, KCR1, KE31, KCR2, KE32

SAP Note 28040 - Error when posting 'Back to vendor'

Symptom:

Error message E201 (QV) in transactions QA11, QA12, QA14.
Internal error! Table TQ07M is not maintained for field VMENGE07!

Cause and prerequisites

Missing entry in table TQ07M

Solution
Call table TQ07M with transaction SM30.
Please enter field name VMENGE07 (function 'New entries'). Enter movement type 122 in columns 'Q stock' and 'AvailStock'. The origin column (LO) remains initial

Additional key words

Usage decision, inventory postings

SAP Note 28037 - CK11, RAISE_EXCEPTION DIVISION_BY_ZERO

Symptom:

Program terminates with RAISE_EXCEPTION DIVISION_BY_ZERO in the program LCK10FOR or in the program LCK40U03. This affects the costing of a material, that is maintained in a BOM item in an alternative unit of measure. This alternative unit of measure is much larger than the base unit of measure. Example: The base unit of measure is piece (pc), the alternative unit of measure box (bx) and the conversion 1bx = 20000pc, as defined in the material master.

Cause and prerequisites

Program error, corrected in 3.0B or 2.2G. An advance correction is possible.

Solution
Note 22521 must be installed for releases prior to 2.2F. After this, please install the following correction. As of Release 2.2F or 3.0A, only the correction is necessary. As there are small differences in the program code for 2.2 and 3.0, there are two blocks of code below, one for each release. Please note the marked code. Please deactivate the lines marked with <<<<<<<<<

SAP Note 28035 - No costing with optional external processing

Symptom:

If internal activities are to be confirmed for an order (PP/MM/PS) and the control key in the operation is set to "External processing possible" (external processing in control key = X), no actual posting occurs and message CK060 ("No valuation for the costing object") is issued.
No costs are determined in the standard cost estimate for the order.

Cause and prerequisites

Program error. Corrected in 3.0B, 2.2G and 2.1M. Preliminary correction is possible.

Solution
Repair in the function module CK_F_AFRU_AMOUNT_CALC. Deactivate the lines marked with <<Additional key words

Costs, planned costs, actual costs IW41 IW32 IW31 IW33 IW34 CO01 CO02 CO03 CO11 CN21 CN22 CN23 CN25


SAP Note 28034 - ME21: Loop during 'Cancel' on accnt assignmt scrn

Symptom:

    1. Create purchase order with reference to the purchase requisition. If the account assignment data in the purchase requisition is incomplete, the program stays on the account assignment popup.
    If you choose 'Cancel' there, the program loops and a termination occurs after some time.
    2. Create, change or display an order assigned to an account with confirmation control. If you choose the list function for confirmations from the overview screen, you can not return from there with F3.
Cause and prerequisites

Error

Solution
1) Corrected in Release 3.0B.
2) Corrected in Release 3.0D.

SAP Note 28027 - ME41: Material description in incorrect language

Symptom:

When you create a request for quotation, the material description is not issued in the language of the vendor.
The request for quotation is created, for example, with language indicator 'D' (German) (EKKO-SPRAS). The material description is then also issued in language 'D' (German). If you then, for example, enter a vendor in language 'E' (English), the request for quotation is still printed with a material description in German. The material description is also displayed in German, even if you log on in another language.

Other terms

ME41, ME42, ME43

Reason and Prerequisites

You cannot change the language after you have entered items of a request for quotation. As soon as a material description was issued in one language, you can no longer change the language. The language of the document and not the language of the vendor is the decisive language when printing the form. In purchase orders, the language of the vendor is proposed as document language; in requests for quotation, however, this is not possible.

Solution
Recommendation:
For English vendors log on to the system again with document language E (English). You can use a request for quotation that has already been entered in German as a reference; the short texts are then displayed in English.
Procedure:
Transaction ME41; Change language (EKKO-SPRAS); Button 'Item overview'; RFQ -> Create w. reference -> To ref. document (as of Release 4.0: RFQ -> Copy); enter the previous request for quotation and copy the items.

SAP Note 28025 - Shared pool 10: (default size assumed)

Symptom:

Error messages are displayed in the trace file, for example, dev_disp:
*** ERROR => Profile configuration error detected [shmux.c 1962]
*** ERROR => Shared Pool 10: ipc/shm_psize_10 = 2000000 (too small)
*** ERROR => Shared Pool 10: (smaller than default 12000000) [shmux.c
*** ERROR => Shared Pool 10: (default size assumed 12000000) [shmux.c

Other terms

sappfpar, shared memory pool

Reason and Prerequisites

A profile parameter (ipc/shm_psize_10 or ipc/shm_psize_40) for setting the size of a shared memory pool has a value that is lower than the default value. The system uses the default value instead of the specified value.
The system can run without restrictions. No follow-on error are expected.

Solution

The value of the profile parameter (ipc/shm_psize_10 or ipc/shm_psize_40) should not be set lower than the default value and the default disposition should be used for the pools.
If the system creates a pool that is much larger then required, this results in the loss of swapspace only, not main memory. We recommend that you reserve at least 2 MB in the pool.
Deviate from the default disposition of the shared memories only when absolutely necessary. Adhere to the suggested default disposition from the
profile check program sappfpar.
Call: sappfpar check pf=
In some installations, it has been observed that many R/3 shared memories are taken from pools to avoid the dependency of the pool sizes on the size of the contained R/3 shared memories, for example, using parameters such as:
ipc/shm_psize_ = 0.
We strongly advise against this. Reasons:

    1. When the R/3 is stopped, certain shared memories are not cleaned up if they are outside of the pool. Problems then occur the next time the R/3 is started. Shared memories with numbers {12, 13, 15, 16, 46, 49} must always be in the pool.
2. Performance problems occur on some hardware platforms (particularly HP) because the higher number of shared memories increases the possibility of protection faults occurring during access. (The HP-MMU contains only a limited number (for example, 6) of protection cache registers for shared memories. These may be set during access using a protection fault and may increase the access time by a factor of 10 ... 40.)

SAP Note 28022 - Customer system: Where-used list of SAP objects

Symptom:

    1. The where-used list for SAP objects is incomplete in the customer system.
    2. The supporting program list for an SAP include is incomplete.
Other terms

() EUNOTE, EUWORKBENCH, ES244

Reason and Prerequisites

In a customer system, you cannot be sure that the where-used list for SAP objects is complete. The where-used list is normally only set up for customer-specific objects and is updated incrementally (see Note 18023).

Solution
If required, the necessary index can also be created for the where-used list of SAP objects. To do this, you must start the report SAPRSEUB (in the background). Note that when you execute the report, you must have generated all programs. If necessary, start a mass generation in advance using transaction SGEN.
Also make sure that the job EU_INIT does not run in parallel.

Due to the size of the index, we recommend that you set up the index in development systems only.
In releases up to and including 46D, the report runs for about 6 to 7 hours. The additional memory required is approximately 100 MB.
A more detailed index is set up as of Basis Release 610; this makes it possible to find a global use of types in programs. This also includes uses of table fields and data elements. The additional memory required for this is 1 GB. The report has a very long runtime and can run up to 100 hours (5 days).

In general, the following applies: A new upgrade does not automatically update the index for the where-used list. You may have to start the report SAPRSEUB again.

SAP Note 28019 - PPPR: List control depends on the order type

Symptom:

In Customizing for printing shop floor papers (Transaction OPK8), entries for certain order types are ignored. The masked entry (XXXX), for example, is used instead during the print control.

Cause and prerequisites

Prior to each access to one of the print control tables, the current order type is converted into a reference order type via table T496B (document types) with which the access is then made.

Solution
If you create a new order type (for example, TEST) with special print control, you have to define this order type as reference order type in Transaction OPK8 under object component 'Document types'. For example with the new entry

TEST TEST

Otherwise, the masked standard entry

XXXX PP01

is used, in general. The accesses are then made with order type PP01.

Additional key words

T496T, T496F, T496R, order category, error SV033

SAP Note 28016 - ME21 ME25 Account assignment fields without user-input requi

Symptom:

On the multiple account assignment screen in the PO and requisition, no user input was required in fields such as G/L account, goods recipient, and unloading point, even if these fields had been declared as mandatory-entry fields in the field selection.

Cause and prerequisites
Solution
See below.

Additional key words

Multiple account assignment FMMEXE01.

SAP Note 28013 - Investment measures with collective AuC

Symptom:

You do not want to create a separate AuC for every measure during periodic settlement of investment measures (order / project with investment profile) but only one asset or a few collective assets under construction.
However, the system creates a separate asset under construction for every internal order / every WBS element.

Cause and prerequisites

You are familiar with the collective AuC.
The 1:1 allocation is necessary for the following functions:

  • Finding the values for final billing settled by period.
  • Special valuation of the asset under construction for selected measures (for example special depreciation, investment support).
Solution
With the specification of the asset class for the AuC in the investment, the AuCs are created automatically without any extra effort by the user and therefore the settlement rule for the periodic settlement to the AUC is determined as well.
The additional memory requirement for the AuC as compared to the order / WBS element should be very small.
The number of line items is not increased by this measure.
This has rather a positive impact on the performance, because for a collective AuC the line items from the periodic settlements would have to be searched for via an additional index or the like for an individual investment measure.

SAP Note 28012 - Condition determination: incorrect reading

Symptom:

When determining conditions (pricing, material determination and so on), the program finds the incorrect condition record.
In some circumstances, the condition determination can read until the memory is full or a TIME_OUT is triggered.

Cause and prerequisites

The fields for access are missing in Customizing.
The program does not recognize the incomplete Customizing and incorrectly reads a condition table.

Solution
Maintain the missing access fields and make the following program change.

Additional key words

Conditions
Program SAPLV61Z
Transactions: VA01.

SAP Note 28011 - Availability check in assembly order

Symptom:

In strategy group 81 assembly order repetitive manufacturing a planned order is created every time you create a slaes order, regardless of existing warehouse stock. As a result, there is no automatic reduction of possibly existing warehouse stocks.

Cause and prerequisites

The service spectrum together with the item category group is not realized in SD.

Solution
None. Not realized in Release 3.0.

Additional key words

VA01

SAP Note 28009 - FB10: Incorrect line item is displayed

Symptom:

Transaction FB10 (invoice/credit memo fast entry). When you display an item on the overview screen, the incorrect line item is displayed at first. If you display it again, the correct line is displayed.

Cause and prerequisites

Program error

Solution
Corrected in Release 3.0B

Advance correction:
Transaction SE38.
Change program MF05AFF0 (FORM FCODE_BEARBEITUNG).
Search for the following statement in the source code and insert the lines marked with <--- INSERT:
*------- Beleguebersicht anzeigen --------------------------------------
when 'AB'.
rw_code = 'AB'.
get cursor field crs-field line crs-line.

if sy-dyngr ne 'U'. <--- INSERT
req-buzei = 0. <--- INSERT
endif. <--- INSERT

SAP Note 28008 - SAPLCXTK PARAMETERS_NOT_VALID: Dispatching element

Symptom:

Raise exception "PARAMETERS_NOT_VALID" is triggered, if you dispatch an element on the planning board at the earliest possible date.
The termination occurred in ABAP/4 program in "CX_OPR_SCHEDULE". The main program is "SAPLCJTR".

Cause and prerequisites
Solution
Program correction

SAP Note 28007 - FI-SL: Defining unique index on object tables

Symptom:

Important:
This note is only relevant for customers who defined FI-SL tables containing objects in Release 2.1 and are working productively with these tables in this or a later release.

For reasons of data consistency, a unique index should be defined using the object number of the respective FI-SL table.
This technically ensures that no double object numbers are written to the FI-SL object table.

Cause and prerequisites

If no unique index is defined for the object table, it can happen under certain special circumstances that double object numbers are written to the object table, namely when the current number level of the number range object GL_OBJECT is reset by mistake (manually or by a transport).
As a result, the line item record and the respective summary record also would be updated differently. Line item record and summary record would no longer "match", which would lead to data inconsistency.

Solution
1) Using transaction SE11, create a unique index for the FI-SL object table in question, which contains the fields
MANDT
OBJNR.

Do not forget to activate the UNIQUE index indicator.
Then please activate this index in the ABAP/4 Dictionary.
2) Create the index in question in the database using transaction SE14.

If activating the index terminates with the message that the index cannot be defined as UNIQUE, this is an indication that double object numbers have already been assigned. In this case, please contact the SAP Hotline.

SAP Note 28005 - SAPLCOVF, scrn 206, queue times not ready for input

Symptom:

The queue times AFVGD-ZWNOR and AFVGD_ZWMIN in the operation detail screen of the interoperation times are not ready for input.

Cause and prerequisites

Program error

Solution

Set field attribute "Input field" with the Screen Painter for the following fields:

  • AFVGD-ZWNOR
  • AFVGD-ZEIWN
  • AFVGD-ZWMIN
  • AFVGD-ZEIWM

SAP Note 28004 - Replacing the work center in inspection plans

Symptom:

When you branch to the inspection plan, the program stops on the initial screen.

Cause and prerequisites

Change program SAPMC27V

Solution
P30K020970

Additional key words

Branching to inspection plans mass replacement work_center

SAP Note 28003 - OnArchive: Level 0 Archive - Aborted by client

Symptom:

OnArchive, level 0 archive terminates with the message:
Aborted by client

Cause and prerequisites

A local tape device is defined as a 'remote device'. That is, the device was entered with the prefix of a host name (for example, :/dev/rmt/0m).

Check the parameters:

  • DEVICE TAPE/DEVICE TAPES in the config.arc file or
  • TAPEDEV/LTAPEDEV in your onconfig file.


Treat a tape device that is entered this way as a remote tape device, and open a remote shell to process the archive/restore processes.

If the remote shell encounters a timeout, the above-mentioned error can occur.

Solution
If you are not using remote backup, do not define local tape units with a preceding host name.

Additional key words

Onarchive, Aborted by client, remote device

SAP Note 28002 - System messages of more than 3 lines

Symptom:

Transaction SM02: System messages are limited to a length of 3 lines with a maximum of 60 characters (Release 2.2: 1 Line ). Can you send longer messages?

Cause and prerequisites

Not contained in the Standard System.

Solution
System messages are only designed for very short messages which all users should read. The length was therefore limited:
For SAPoffice users, the following option exists: the detailed information is stored in a folder to which every user has access. Simply refer to this in the system message.