SAP OSS Notes: 6/5/11

11.6.11

SAP Note 26000 - PPPI Master recipe for data transfer

Symptom:

Create master recipe by copying

Solution
Function: Create by copying

SAP Note 25998 - RFUVDE00 - Vorauszahlung wird nicht berücksichtigt

Symptom:

Der im Customizing hinterlegte Steuervorauszahlungbetrag wird vom Druckprogramm des deutschen Umsatzsteuerformulars nicht berücksichtigt, wenn nach Umsatzsteuerkreisen abgegrenzt wird.

Weitere Begriffe

RFUMSV00, RFUVDE00, F_RFUVD____01, T007J

Ursache und Voraussetzungen

Programmfehler.

Lösung
Fehler ist zu Release 3.0B behoben. In den Releases 3.0 FCS und 3.0A ist die folgende Korrektur einzupflegen:

SAP Note 25992 - Various errors in network graphic (Gantt chart)

Symptom:

Restrictions for an activity are not set correctly.

Cause and prerequisites

Fields are incorrectly filled.

Solution
Program correction

SAP Note 25991 - Platforms for the R/3 Analyzer/ARIS Tool Set

Symptom:

Platforms for the R/3 Analyzer are not known

Cause and prerequisites
Solution
The R/3 Analyzer Release 3.0 and the ARIS Tool Set Version 3.0 can be operated as a standalone version or as a multi-user version. The multi-user version requires the acquisition of one or more ARIS server licenses from IDS Prof. Scheer GmbH in Saarbruecken. The R/3 Analyzer Release 3.0 and the ARIS Tool Set Version 3.0 can be operated on the following operating systems and network platforms:
Operating system:
- Windows 3.1 or above
- Windows for Workgroups 3.11
- Windows NT (16 bit emulation)
- WIN-OS/2 emulation, IBM OS/2 Warp (release 1st quarter 1996)
Network: Client Server Protocol Server version
Windows 3.1, WfW 3.11 Novell 3.11/3.12 SPX/IPX-VLM from 3.0
and Windows NT Novell 4.1 SPX/IPX-VLM from 3.0b
Windows NT Named Pipes, from 3.0b
LAN Manager
Windows 3.1, WfW 3.11 Windows NT TCP/IP 3.0b Beta
IBM OS/2 Warp Named Pipes, Test Version
SPX/IPX-VLM, "
TCP/IP
Windows NT Windows NT TCP/IP "
IBM OS/2 Warp SPX/IPX-VLM "
WIN-OS/2 Em. and IBM OS/2 Warp Named Pipes, "
IBM OS/2 Warp SPX/IPX-VLM,
TCP/IP

Further information can be obtained from IDS Prof. Scheer GmbH in Saarbruecken (hotline: 0681/9921-777).

SAP Note 25989 - Pensions and Court Orders being cleared in period 1

Symptom:

GB pensions and court order cumulatives being cleared at start of year.

Cause and prerequisites

Function IMPRT with a parameter of L.

Solution
Change as detailled below.

SAP Note 25985 - Entering enhancements in customer name range Z*

Symptom:

It is not possible to enter enhancements in customer name range Z*/Y* (Transaction SMOD). Also in the customer system the message "The names Z* and Y* are reserved. Please choose another name" is displayed.

Cause and prerequisites

Enhancements can only be created by SAP in the SAP namespace.
The enhancement concept is based on a two-level model SAP / customer.Partners, industries or other intermediate vendors are not taken into account.The present concept cannot be easily enhanced since the overall implementation is focused on the two-level model.
As of Release 4.6 a new enhancement technology is available (Business Add in) which can be used by all software producers involved (SAP, partners, customers). The technology supports the namespaces continuously and is to replace the other enhancement technologies in the long term.

Additional key words

SMOD, CMOD, enhancement concept

SAP Note 25983 - Monitor for list of tasks terminates

Symptom:

If you call the monitor function in the list of tasks (report RQMELL20) for quality notifications with more than 100 tasks, the following termination occurs:
CONVT_NO_NUMBER
"*0" cannot be interpreted as number

Cause and prerequisites

Variable h_row only consists of two digits which leads to an overflow.

Solution
Only the first 100 tasks are displayed on the monitor.
Please make the following corrections to the specified report.

Additional key words

RQMELL20, RIQMEL30, list of tasks, QM12, QM13, IW66, IW67

SAP Note 25978 - Drill-down: Cond., sorting for +/- sign reversal

Symptom:

If a condition is set for a value column or sorted by it and +/- sign reversal is active for this column, then the result is not what the user expects.

Cause and prerequisites

+/- sign reversal is not taken into account in the sort and the condition.

Solution
Correction P21K005813 in 2.1 or P21K008995

Additional key words

COBPC3, sort columns, +/- sign reversal, set condition

SAP Note 25977 - Incorrect text output if the routing is missing

Symptom:

Incorrect text output if the routing is missing.

Cause and prerequisites
Solution
a) Change text element, b) Change program code in SAPLCPDI

Additional key words

text_problems further

SAP Note 25976 - Syntax error in program RKABCCD0

Symptom:

A syntax error occurs in program RKABCCD0 when transferring statistical key figures from LIS.

Cause and prerequisites

Due to a transport error, the generated program RKABCCD0 contains a syntax error.

Solution
Start report RKABCCD6 to regenerate the program in question.

Additional key words

statistical key figures, LIS, ABC, transfer

SAP Note 25975 - Operation ADDZLM*E: wage type not copied

Symptom:

In time accounting, operation ADDZLM*E does not function correctly if the cycle is started by function POVT.
An entry is stored in table ZL, but the wage type is not transferred.

Cause and prerequisites

For function POVT, nothing was entered for the field string ZH.
However, for operation ADDZL, this is used as the value passed for the
wage type.

Solution
For function POVT, make entries for field string ZH also.
To do this, change routine FUPOVT in RPTMAS03 as described below, and
then check that program SAPFP51T contains no errors.

Additional key words

Overtime wage types, RPTIME00

SAP Note 25969 - Additional Info: Upgrading to 3.0A INFORMIX

Symptom:

Errors in the guidelines or problems during the upgrade which only occurred after creating the guidelines.

Additional key words
Cause and prerequisites

Solution
*******************************************************************
This note only contains INFORMIX-specific problems!!!
*******************************************************************

The topics are Date of last change
============== ===================
0/ Space requirements in Dbspaces
I/ Actions before Upgrading to 3.0A
II/ Errors in the Guidelines
III/ Problems in the Upgrade Phases
IV/ Problems after Upgrading to 3.0A

**********************************************************************
0/ Space requirements in Dbspaces
**********************************************************************

The table below gives the space requirements for individual dbspaces:

Space Required (KB)
(according to starting release)
Dbspace 2.2D/E/F 3.0FCS
====================================================
rootdbs 33 11
psappool 243 77
psapbtab 110 66
psapprot 6 6
psapstab 275 220
psapddic - 28
psapes30a 2500 2500 -> new Dbspace
psapel30a 390 390 -> new Dbspace
In order to create the new dbspaces (psapes30a and psapel30a), you need
either ON monitor (more information about this can be found in the
INFORMIX manual "INFORMIX-OnLine Dynamic Server, Administrator's Guide")
or use the onspaces command:
"onspaces -c -d -p -o -s "

**********************************************************************
I/ Actions before Upgrading to 3.0A
**********************************************************************

When executing the script ALTERSYS.SH (see upgrade guidelines), the SAP system must be shut down.

----------------------------------------------------------------------

To prepare a 3.0A upgrade, there is a report (RSATAF03) which, determines the additional time and space required, depending on the application data volume.
This is especially important for systems into which large datasets have already been copied.

The report is stored on the CD 'SAP Kernel' in the subdirectory DBTOOLS and can be imported as follows:

- Mount the CD 'SAP Kernel'
- Import the report with R3trans:
"R3trans -i //DBTOOLS/RSATAF03"

The report RSATAF03 can be executed with transaction SE38. So that the report can deliver useful results, you must perform an 'update statistics medium' before executing the report.

See also note 27943.

**********************************************************************
II/ Errors in the Guidelines
**********************************************************************

**********************************************************************
III/ Problems in the Upgrade Phases
**********************************************************************

In the phase MAIN30A, errors with the following error message in log MAIN30.ELG can arise:

SQL error "-750" during "" access: "INF750 Invalid
distribution format found for "

In this message,

stands for a table and for a field of
this table.
In this case, carry out the following SQL statement as user 'informix' for each table/field given:

"update statistics low for

() drop distributions;'

Replace

or with the given table or field name.

Then you can continue the upgrade with 'repeat'.

**********************************************************************
IV/ Problems after Upgrading to 3.0
**********************************************************************

Creation of database-specific objects

o Shell script D010LINF.SH

With the shell script D010LINF.SH, additional informix-specific
indexes/constraints for the table D010LINF are created. The script
is in the directory DBTOOLS on the 3.0A Kernel CD. It is also to
be found on sapservX in directory
/general/3rdparty/informix/upgrade as D010LINF.SH.34045.

Start the script as follows:
"su - informix"
"/DBTOOLS/D010LINF.SH

WARNING: If the SAP system is running when the script is started,
ISAM error -106 can occur: "non-exclusive access."
In this case, you must bring down the SAP system
("stopsap r3") and re-run the script.

o Report SINDXINF

After the upgrade, execute the program SINDXINF.
The report creates database-specific objects (e.g. indexes).

You must make sure you have imported the latest version of the report
into your system. You will find the R3trans file on the 3.0A Kernel
CD in directory DBTOOLS. It is also to be found on sapservX in
directory /general/3rdparty/informix/ddic as 'SINDXINF.29751'.

Import the report as follows:
"su - adm"
"R3trans -i /DBTOOLS/SINDXINF"

Now you should generate and start the report SINDXINF with the
transaction SE38 (NOT as user DDIC!)

========================================================================

Access rights for SAPDBA
========================
If you wish to use SAPDBA, you will need to change the access rights
for the program /usr/sap//SYS/exe/run/sapdba as follows:
o "su root"
o "cd /usr/sap//SYS/exe/run"
o "chown informix sapdba"
o "chgrp informix sapdba"
o "chmod 6755 sapdba"

SAP Note 25967 - Fields "From" and "To" missing for time

Symptom:

Time or hours cannot be entered for the confirmation.
Fields "From" and "To" are missing in confirmations for the time.

Cause and prerequisites

The time unit in the operation is longer than a day
If a time unit which is longer than one day is used in the operation, it does not make sense to enter a time in the order completion confirmation or operation confirmation.
The time fields are suppressed for this reason.

Solution
None, it was intended to do this.

Additional key words

Times have been suppressed

SAP Note 25963 - Customer field selection in task list header

Symptom:

The QM data in the task list header cannot be influenced by the customer field selection.

Cause and prerequisites

The function module call for the customer field selection was missing.

Solution
Please correct function module CP_MF_QDATEN as described below.

Additional key words

Dynamic modification rule, dynamic modification level, inspection point, external numbering, QP02, CA02, QP01, CA01

SAP Note 25959 - Abend when scrolling in consumption/forecast values

Symptom:

When maintaining a material master record, you maintain consumption values or forecast values. The program thereupon terminates with message 61 119, "Please maintain periods in table T009B".

Cause and prerequisites

The consumption values or forecast values are maintained with reference to a year-dependent fiscal year variant. Here, you have scrolled to a page on which not all periods can be determined since the relevant fiscal years have not been maintained in Customizing.

Solution
Problem corrected in 2.2G and 3.0B. As a temporary workaround, you can resolve the problem either by creating additional fiscal year variants in Customizing or by integrating the coding below which prevents the termination message.

Additional key words

Transactions: MM01, MM02; program: SAPMM03M; screens: 254, 255

SAP Note 25952 - Persons from the ranking list are not copied

Symptom:

When you plan individual capacities and persons within capacity leveling, you can choose the 'Ranking list' function in the dialog box of the split definition. You can select persons from the ranking list and copy them into the splits. However, this is only possible if splits were selected in the dialog box of the split definition. If you did not do this, nothing is going to happen when you exit the ranking list with "Copy".

Cause and prerequisites

Basically, the behavior is correct. However, there is no message that you first have to select splits.

Solution
A warning message should be output, if persons to be copied were selected in the ranking list and no splits were selected in the dialog box of the split definition.

SAP Note 25951 - Account assignment model: Known errors 3.0A

Symptom:

In Release 3.0A, the account assignment model method contains small errors which interfere with processing (but do not endanger data). The following symptoms are known:

1. When selecting an account assignment model when you enter a document, message FX260 appears although the entry screen has not been changed and the account assignment model can be maintained as normal. It reports that the field CCode is missing.

2. If you Cancel in the entry screen selection, the maintenance transaction FKMT also cancels (with error FX201) although the standard screens exist.

3. If the maintenance transaction FKMT is used by one user in two sessions on different account assignment models, then when you move from the line screen to the header screen, the data of the account assignment model edited in the other session can appear. When branching to the line screen, the entry screen of the other account assignment model can suddenly appear. Cause and prerequisites

Small program error

Solution
The above error is corrected in 3.0B by P30K012899.
The field Company code must be included in the reported entry screen for symptom 1.

Additional key words

SAPLFKMT, FX201, FX260

SAP Note 25949 - Error in dunning run when clearing cust./vendor

Symptom:

Key words: Clearing, dunning run, SAPF150S.
1. With a common dunning notice of a customer who is also the vendor,
vendor items, that were not due, were also cleared.
2. The dunning run was cancelled with the error FM003 'Dunning
selection cancelled: Error in internal table XKNB5'. This error
occurs under the following preconditions:
- dunning notice for each dunning area
- customer and vendor are cleared
- customer and vendor are dunned in different dunning areas.

Cause and prerequisites

Program error.

Solution
Corrected in Release 3.0B.
As advance correction, make the changes marked in the include F150SFV0:

SAP Note 25946 - SAPDBPSJ: F4 help for project version

Symptom:

The F4 help for the project version in the PS Info system (for example transaction CN40) and when using the logical database PSJ only displays the version key, the name and the version group. You can only choose one value. This complicates matters if for instance you want to make a selection based on version groups.

Cause and prerequisites
Solution
Function module
'HELP_VALUES_GET_AND_RETURN_TAB' is used for the F4 help.

SAP Note 25942 - BTCI for orders with classification

Symptom:

If background input sessions which create or change orders to be classified are processed, these sessions cannot be executed. In the case of batch input, a different screen appears in classification during characteristic value assignment than in the online case.

Cause and prerequisites

Classification has a special batch input processing. Screen SAPLCTMS-0109 is used here.

Solution
After the function code for classification was entered by master data maintenance, screen SAPLCTMS-0109 must be used for valuating the user-defined characteristics.

Those user-defined characteristics which should be valuated, must be listed here with the name of the characteristic (RCTMS-MNAME) and the characteristic value (RCTMS-MWERT).

Example of the batch input table (structure: BDCDATA)
only classification part

PROGRAM |DYNPRO|DYNBEGIN|FNAM |FVAL
--------|------|--------|-----------------------------------|----------
* Sprung in die Klassifizierung (am Beipspiel eines CO-Innenauftrags)
SAPMKAUF|0140 |X |BDC_OKCODE |/18

* Bewertung der freien Merkmale im Dynpro SAPLCTMS-0109
SAPLCTMS|0109 |X |RCTMS-MNAME(1) |MERKMAL1
SAPLCTMS|0109 | |RCTMS-MWERT(1) |WERT1
SAPLCTMS|0109 | |RCTMS-MNAME(2) |MERKMAL2
SAPLCTMS|0109 | |RCTMS-MWERT(2) |WERT2
SAPLCTMS|0109 | |RCTMS-MNAME(3) |MERKMAL3
SAPLCTMS|0109 | |RCTMS-MWERT(3) |WERT3

* Rückkehr zur Stammdatenpflege
SAPLCTMS|0109 | |BDC_OKCODE |/03

SAP Note 25941 - SAP System does not find host name of

Symptom:

Output requests receive the status "Error." The error message in the syslog is "FA6: Attempted to connect to the host ... Failed, as the gethostbyname(3) for this host was not recognized", such as:
"Name of destination host unknown".

Other terms

NILIB, gethostbyname, SAPLPD, telnet, ping, hosts, print, SAPSprint

Reason and Prerequisites

The C-library functions gethostbyname or NiHostToAdr called by R/3 fail.
Unfortunately, the same error message is returned in both cases.

Solution

Carry out the following tests:

1. Are there incorrect entries for this host in the THOST ?

work (under user adm)?

515/tcp work (user adm)?

If a connection is set up after transmission of this command, you can use 4 x 1 to test whether you can reach SAPLPD. This should then return its version number and close the connection.

adm has no read rights to the entries.

5. Does an nslookup with the host name function?

If this program fails, you have to contact your network administrator.

adm and run the command "niping -t -H ". If the function NiHostToAdr returns a value <> 0, try if an NI reset in the definition of the output device using transaction SPAD solves the problem.

7. Use more SUBDOMAINS ? -- for example, the editing computer is named host1.xx.yy.zz; the router on which SAPLPD is running is called host2.uu.vv.ww. Call Transaction SM55 and enter the following alias:

host2 host2.uu.vv.ww

The host computer will still be named host2 in transaction SPAD. This can solve the probelm, but if it does not, you need to examine the configuation of your domain name server.

Have you made changes to the host files or were PC addresses allocated dynamically? If so, reboot the application server running the spool work process in question.

SAP Note 25938 - Error during primary costs transfer for delta vers.

Symptom:

In reports for cost centers in a delta version, activity-independent primary costs are incorrectly displayed or not at all.

Cause and prerequisites

When you define a delta version, different business transactions must be assigned to it. If you determine in this case that the primary costs should remain in the reference version, however, the activity allocation is to be carried out in the delta version, then the described error can occur.

Solution
see the following correction:

Additional key words

Delta version, CO-ABC, ABC, activity-based costing, reports.

SAP Note 25931 - Session terminates in availability check screen

Symptom:

Session terminates when branching to the availability check screen
Program: SAPLV03V, screen number: 0500.

Cause and prerequisites
Solution
Call up the Screen Painter (Transaction SE51) and enter 'SAPLV03V' in program and in '0500' in screen number.
Click on 'screen attributes' and go to 'Change'.

Click on 'Deactivate runtime compression' and regenerate the screen.

Additional key words

VA01

SAP Note 25928 - 3.0A: Termination in SAPLV07A, SD_ORDER_SUBSEQUENT_ALLOWED

Symptom:

Termination when creating an order item with integrated assembly order.
--> Program SAPLV07A, error with external perform <--

Cause and prerequisites
Solution
Correction for 3.0B

Additional key words

VA01, Assembly, Assembly order, Assembly processing, Strategy group
KMFA KMSE

SAP Note 25920 - MD82: Cust.ind.reqs change - missing entry T185

Symptom:

MD81 / MD82 : Create/change customer independent requirements
The following message appears in the scheduling screen when scrolling:
E: Flow control: Entry SAPMV45A,P-,P0,PEIB,*,* is missing in T185.

Cause and prerequisites
Solution
Complete the entries in table T185 with transaction sm31.

Call transaction sm31 and maintain table T185.
Create the 4 records necessary for scrolling by positioning the cursor on the following similar records and replacing the field Panel 'PEIN' by 'PEIB' in each case.
Area FCode Grp. Panel Grp. ItGr
SAPMV45a P- P0 PEIN * *
SAPMV45a P+ P0 PEIN * *
SAPMV45a P-- P0 PEIN * *
SAPMV45a P++ P0 PEIN * *
Saving is carried out automatically when you press ENTER.
The following entries must then exist:
Area FCode Grp. Panel Grp. ItGr
SAPMV45a P- P0 PEIB * *
SAPMV45a P+ P0 PEIB * *
SAPMV45a P-- P0 PEIB * *
SAPMV45a P++ P0 PEIB * *

SAP Note 25917 - Changes to /etc/hosts are not accepted.

Symptom:

Changes to the operating system tables hosts or services are only effective after restarting R/3.

Cause and prerequisites

For performance reasons, the SAP network interface (NI) buffers the host and service names. The system only calls the host and service names once to translate host names to IP addresses or service names to port numbers (and vice versa).
The NI level does have calls to flush these buffers, but this function is not yet used in all R/3 components.

Solution

prior to R/3 Release 3.1G:
The corresponding application server must be restarted.
To avoid such situations you should make sure when adding new hosts that you do not access the new name before it is known by the operating system.

as of R/3 Release 3.1G:
As of R/3 Release 3. 1G you have the option of resetting these buffers when the system is in operation. Use Transaction SM51: "Goto ==> Host name buffer ==> Reset".

Additional key words

host name, service name, hosts table, services table, buffer

SAP Note 25916 - MR01: Termination of the function "New item"

Symptom:

If you choose the function "New item -> G/L account" (or another function contained in the menu "New item") directly on the initial screen, then you access a window for entering the G/L account (or the material and so on). Up to now, if you pressed "Cancel" here, you returned to the vendor screen and the originally entered data was lost.

Cause and prerequisites
Solution
Corrected in Release 3.0B.
The system now branches into the document overview into which the vendor item is copied. (This corresponds to the procedure if you choose "Cancel" on the G/L account screen (or material individual screen and so on).

SAP Note 25915 - QM inspection data in material master are not saved

Symptom:

A new inspection type for which no default values are stored in Customizing is created in the QM inspection data (Quality management --> Inspection process --> Insp. lot processing --> Inspection lot --> Create --> Define default values for inspection type).
This new inspection type is not saved when you save.

Cause and prerequisites

Program error

Solution
Maintain default values for the inspection type in Customizing. You can call the Customizing table in question via :
Quality management --> Inspection process --> Insp. lot processing --> Inspection lot --> Create --> Define default values for inspection type
OR
Make the change described below in the program code.

Additional key words

MM01, MM02

SAP Note 25914 - MMIM: GI posting w.enhanced sel.: Selection plant

Symptom:

Goods issue posting for the order with enhanced selection: if a plant is not entered, all components of the order should be proposed for posting. In the current status, only the components that correspond to the plant of the first component are displayed.

Cause and prerequisites

Program error.

Solution
Please make the following program change in Include MM07MFR0.

SAP Note 25913 - Icons are not displayed. Instead,@ 01\Q appears

Symptom:

Icons appear on the screen as an @ sign....
From time to time the session disappears with signal 11 (SYSTEM_CORE_DUMPED)

Cause and prerequisites

Please check whether the screen is translated. Transaction SE63, Translation -> Short texts -> Screen Painter. Double-click on the lower icon in each case. Fill the popup correspondingly. A foreign-language text must exist for every German text.
The translation is indispensable if the profile parameter zcsa/system_language is set <> D. The Dynpro load is then set up in the corresponding language. If a standard quickinfo is copied from the ICONT, although a Quickinfo text is available in German and this Standard quickinfo is longer than the German Quickinfo text, the icon is often destroyed, as the latter part of the icon infomation is truncated. The result of this is that the frontend outputs a text string rather than an icon. This consists of the following: "@12\Q__Quickinfo__@__Text for the icon on the screen__"

Solution

1. Translate and generate the screen with SE51.

2. If point 1 fails: SE51, Fullscreen, attribute for 1st field (position cursor on the corresponding icon), Delete Quickinfo. Save the screen with the repair correction, retranslate and then generate the screen with SE51.

Additional key words

Icons, @, Quickinfo, icon text
SAPFH5AH Screen 4000
SAPLSHLC Screen 0100

SAP Note 25907 - IP05, IP06 Maint.item with inc. maintenance plan

Symptom:

When displaying or changing a maintenance item with an existing allocation to a maintenance plan, the incorrect maintenance plan may be displayed. In individual cases, the following message can also occur: IP320 Maintenance plan & does not exist, although the maintenance plan does exist.

Cause and prerequisites

Read the allocated maintenance plan with the incorrect structure.

Solution
Please carry out correction P30K013146 in program SAPMIPM0.
This affects the FORM routine MPOS_LESEN_F20 in Include MIPM0F20 as well as the FORM routine TABLE_INIT_O00 in Include MIPM0O00.

SAP Note 25903 - Project acc. assign. without make-to-order stock

Symptom:

You assign an order item to an account in a project. No make-to-order stock should exist for this item. The following problems occur:
1. During goods issue, the system requires a storage location even for non-stock materials. Message M7018.
2. If you set the field 'Individual requirements' in the material master to '2', Message V1251 'This material cannot have requirements type ...' is issued when you create an order.
3. The availability check is always carried out on the make-to-order stock level.
4. During goods issue for the delivery note the system issues the
error message E139 'Project xxx already exists in the sales order'.

Cause and prerequisites
Solution
1 and 2: The problem is the special stock indicator. In the 'Procurement' overview screen, you can see the requirements type used for the item. The requirements type is assigned in SD Customizing to a requirements class. Account assignment 'D' is in the requirements class and contains the special stock indicator 'E'. If you define in Customizing for Purchasing a new account assignment category parallel to 'D' but with the special stock indicator ' ' instead of 'E', and if you assign it to the requirements class being used, the error message will no longer be issued.

3: See Note 24753.
4: See the changed coding and table entries below

Additional key words

Make to order production, KP, KPX, PSP element, account assignment, goods issue

SAP Note 25900 - Order unit is not taken over from info record

Symptom:

When you enter an info record, the order unit is not taken over from the info record.

Cause and prerequisites

The unit is not taken over.

Solution
Take over the unit from the info record.

Additional key words

External processing; standard network;

SAP Note 25899 - Transport asset classes/transaction type groups

Symptom:

If you copied asset classes with the SAP transport connection to another client, the allowed transaction type groups were not transported. (for example, transaction type group for down payments)

Cause and prerequisites

technical restrictions

Solution
The transaction type groups of the asset class are stored in dependency of chart of depreciation and are therefore not transported with the asset classes but with the chart of depreciation. If possible, the chart of depreciation can be transported again or transport asset classes and chart of depreciation simultaneously.
Another possibility is a separate subsequent transport of the transaction type group by directly entering it into the correction: To do this, you must make an entry using SE01 (as of Rel. 3.0 SE09) in the editor of the correction:

PgmID Obj Object name Function
R3TR TABU TABWI K

You can specify the key of table TABWI more precisely by doubleclicking on the line, where (as in the example) client and chart of depreciation must be specified and the transaction type group must be specified generically with '*'.

Example of key specification of table TABWI:
Field description Type Pos. Value
Client C 1 003
Chart of depreciation C 2 1DE
Transaction type group C 3 *
Asset class C 4

Additional key words

TABWI

SAP Note 25898 - Upper/lower limit for double-line entry

Symptom:

Order entry with the double-line entry screen:
A condition record or a condition type is created with upper limit / lower limit.
If, when creating, the condition type, for example, PR00 is now entered with an invalid amount, then a check is not made against the maximum values.
The check is then carried out during a subsequent change.

Cause and prerequisites

Program error

Solution
Corrected in 2.2G/3.0B

Additional key words

VA01 VA02

SAP Note 25897 - Report Writer: Archiving does not work

Symptom:

Archiving a Report Writer report does not work. If you choose in the transaction GR55 "Execute report group" Select -> Execute and print and on the dialog box "Print list printout", '2' (archive only) or '3' (print and archive) as an archiving mode), a termination is carried out with the error message PT019.

Cause and prerequisites

Program error

Solution
Please make the following corrections. The lines to be inserted are marked with '"<- insert' at the end of the line.
Please also consider note 15547.

Additional key words

Report Writer, archiving

SAP Note 25896 - Old assets data takeover of revaluations for AuC

Symptom:

The customer also has to transfer past revaluations to assets under construction that are managed by line items in old assets data takeover. This is especially necessary in countries with high inflation such as Argentina.
How can the revaluation be transferred into the system?

Cause and prerequisites

Export regulations

Solution

A transfer of the past values is generally carried out for AuC as transactions in line item management. The cumulative values are blocked for entry during old assets data takeover.

The transaction types 900 for APC and 910 for down payments are provided as standard movement types of the old assets data takeover. For these transaction types, the field Revaluation can be maintained by branching to the proportionate values.
(Menu path: Transfer value -> Transaction -> Proportionate values ).

For APC, the value 0 can also be specified and therefore only one transaction can be used for revaluation.

If you want to use a separate transaction type, you can copy transaction type 900.
(see Customizing -> Transactions -> Transaction types)

Additional key words

Old assets data takeover transactions AS91 AS92 RAALTD01

SAP Note 25887 - STORAGE Parameter for ORACLE parallel server

Symptom:

Performance problems of an ORACLE parallel server due database to excessive pinging.

Cause and prerequisites

Solution
A change of the FREELISTS and FREELIST GROUPS parameters is only possible with a reorganization of the table or index. They can no longer be changed later by an ALTER command.
The optimal value for FREELIST GROUPS is the number of database instances. If you plan to increase the number of instances in the future, you should use the higher value from the beginning. The number of FREELISTS should be as large as the maximum number of update processes that are connected to a database instance.
PCTUSED and PCTFREE should only be changed with good cause and only for small tables. To ensure that only one record is stored per data block, you should set PCTUSED to 1 and PCTFREE to 99. We recommend here that you reorganize the table so that the STORAGE parameters also take effect for the existing records. To achieve a satisfactory performance during number assignment (Customizing setting "Buffering in local file"), the described change must be made for table NRIV_LOKAL.

List of tables for which increased FREELIST GROUPS and FREELISTS parameters are recommended:

AABLG AEOI AFFL AFKO
AFPO AFRU AFVC AFVU
AFVV ANLB ANLC AUAK
AUFK BKPF BPIG BSAD
BSAS BSID BSIK BSIM
BSIS CDCLS CMFK COBK
COBRA COBRB COEP COEPL
COKA COSL COSP COSPD
COSS DBSNP DBTABPRT EBAN
EIPA EKBE EKET EKKO
EKPO INDX JEST JSTO
KBKO KNVD KOCLU LIKP
LIPS LQUA LTAK LTAP
LTBK LTBP MDKP MKPF
MONI MSEG MSTA M_AANL
M_MBRK M_MEKK M_ORDE M_PREM
M_PRPM M_REVN M_VMSK M_VMVA
M_VMVL NAST ONR00 ONROK
ONROR ONROS ONROV PCL1
PCL2 PROW REGUC REGUH
REGUV RESB RFBLG RKPF
S031 S033 S502 S507
S508 SNAP SOC3 SOFM
SOOD STXH STXL TBTCO
TBTCS TSP01 TSP02 TST01
TST03 VAKPA VAPMA VARI
VBAK VBAP VBBE VBEP
VBFCL VBKD VBPA VBRK
VBRP VBUK VBUP VEPVG
VKDFS VLKPA VLPMA VRKPA

Additional key words

Parallel server, OPS, PSO, FREELISTS, FREELIST GROUPS, PCTUSED, PCTFREE, pinging

VRPMA