SAP OSS Notes: 8/21/11

25.8.11

SAP Note 26972 - INST: 3.0/3.1 R/3 Inst. - ORACLE Parallel Server

Symptom:

+---------------------------------------------------------------------+
I R/3 Installation on UNIX - ORACLE Parallel Server I
I I
+---------------------------------------------------------------------+

Related Notes:
3.0D 3.0E 3.0F 3.1G Title
----------------------------------------------------------------------
31451 44795 47946 50183 R/3 Installation on UNIX
31445 44804 47942 50184 R/3 Installation on UNIX - ORACLE Database
31450 44796 47954 50189 R/3 Installation on UNIX - OS Dependencies
31449 44797 51690 50192 R/3 Advanced Installation/ Homog. System Copy

Cause and prerequisites

Problems discovered after publication of the Installation Guide.

Solution

The note is maintained in English only. No German version exists.

DO NOT CHANGE OR ADD INFORMATION TO THIS NOTE !

If you want to contribute something, please send a mail to to any of:
Winfried Nesselhauf winfried.nesselhauf@sap-ag.de
Robert Voelkel robert.voelkel@sap-ag.de

table of contents (sorted by date)
===================================

date section description
-----------------------------------------------------------------------
04/JUL/1997 1 3.1G: Oracle 7.3.2.3: DB startup fails
13/DEC/1996 1 3.0E: SICK error at 1st SAPGUI connect after startup
13/DEC/1996 1 3.0D: Oracle patches required
12/DEC/1996 1 Adapt SAPFS.TPL after creating raw link script
04/NOV/1996 1 3.0E: Executables of sapdba, etc. must be extracted
04/SEP/1996 1 3.0D: File OPSFILENAME is not on CD
04/SEP/1996 2 3.0D: New name for the file DEFAULT.CONF

Sections of this note are:
1 General Notes
2 RS 6000 SP Specific Notes
3 RM1000 Specific Notes

1. General Notes

----------------------< d019628 04/SEP/1996 >------------------------
ONLY 3.0D:
File OPSFILENAME is not on CD:
In the guide the file OPSFILENAME is mentioned. This file does not exist on the CD. Please substitute OPSFILENAME with OPSFILE during reading the Guide. This file you will find on the CD.

----------------------< d020783 04/NOV/1996 >--------------------
ONLY 3.0E:
Executables of new administrations tools must be extracted:
On page 4-2 (Installing the OPS Administration Extensions), a note mentions a number of files to be copied.
These files are compressed in the file
/sapmnt//exe/INSTALL/SAPDBA.CAR
You have to extract SAPDBA.CAR before you can copy the executables to /sapmnt//exe:
Extracting: cd /sapmnt//exe/INSTALL
/sapmnt//exe/CAR -xvf SAPDBA.CAR

----------------------< d020783 12/DEC/1996 >------------------------
3.0D and 3.0E
Adapt SAPFS.TPL after creating raw link script
After having created the raw link script with R3INST (see section "Preparing the DBB Installation" in Chapter "Common OPS Installa- tion" of the OPS Installation Guide), adapt the file SAPFS.TPL as follows:
1. Exit R3INST
2. Edit the file SAPFS.TPL: Replace the line
OPSFILE = /OPSFILE
with
OPSFILENAME = /OPSFILE
Without this change in SAPFS.TPL, no freelists or freelist groups are created for the tables listed in the file /OPSFILE.

----------------------< d020783 13/DEC/1996 >------------------------
ONLY 3.0D:
Oracle patches required
Installation of Oracle 7.3.2.1 (the Oracle version on the 3.0D OPS Installation CD) requires the following Oracle patches:
bug383534, bug389223, bug393692,
bug375721, bug387086, bug390288, bug401115,
bug382196, bug389032, bug391720, bug419181.
The patches can be downloaded from sapservX:
Directory: /home/ftp/general/3rdparty/oracle/SP2/7321
File: PATCH_7321_SP2.tar.Z

----------------------< d020783 13/DEC/1996 >------------------------
ONLY 3.0E:
SICK error at 1st SAPGUI connect after startup
After startup of an application server, the first SAPGUI trying to connect to this server receives the error message "Inconsistency with database: call transaction SICK".
The user cannot log on. Subsequent attempts to connect are successful.
Cause:
R/3 System suggests that release 3.0E would not be supported with Oracle release 7.3.2.1.0 However, R/3 on Oracle Parallel Server is supported with this database release.
Solution:
The error can be ignored.
The error message is not displayed if you add the following line to the profile DEFAULT.PFL: abap/ignore_icc =2
However, other error messages are also not displayed then. Error messages are still written to the SysLog.

----------------------< d022237 04/JUL/1997 >------------------------
Only 3.1G:
After installing Oracle 7.3.2.3, the startup of the database instance
fails with the following error message:

SVRMGR> startup parallel
LCC-00161: ORACLE error (possible syntax error) parameter [NULL]
ORA-04017: Message 4017 not found; product=RDBMS; facility=ORA

The solution: include the following entry in the ocommon.ora file:
max_dump_file_size=200000

RS 6000 SP Specific Notes
----------------------< d019628 04/SEP/1996 >------------------------
ONLY 3.0D:
New name for the file DEFAULT.CONF
The Filename of the template file for configuring the distributed lockmanager is not DEFAULT.CONF. The rigth name is DEFAULT.CON.

Additional key words

OPS

SAP Note 26971 - Termination during char. value assignment

Symptom:

Symptom

ABAP/4 runtime error STACK_PARM_NO_ROLL_MEMORY in program SAPLQEST in subroutine MOMENTS_CORR_2_PASS or MOMENTS_CORR_2_PASS_CLASS.
The error can only occur for characteristics with measured values and single value management or class management if a mean value is calculated close to 0. This can occur especially, but not only, when you are assigning or completing a calculated characteristic.

Cause and prerequisites

Program error for setting a termination condition

Solution
Correction of function modules QEST_MOMENTS_CORR_2_PASS_CLASS and QEST_MOMENTS_CORR_2_PASS_VALUE. You should make the same correction in both function modules.

Additional key words

Results recording QE01 QE11 QE14 arithmetic recursion endless loop

SAP Note 26967 - MR44 Error M8252 -> M8107 Not posted & no messages

Symptom:

When trying to post a preliminary posted invoice, message M8252 - 'Parked document & cannot be posted (see Details -> Messages)' appears. However when the user attempts to use DETAILS > MESSAGES, the error message M8107 - 'No messages exist' appears.

Cause and prerequisites

MR44 posts the preliminary posted invoice using batch input in background ('CALL TRANSACTION'). If the batch input fails, message M8252 is returned, rather than the actual message from the batch input run. Usually such messages may be displayed via DETAILS > MESSAGES, but in some cases the relevant message has not been included in the XMESG table by function MR_CREATE_INVOICE.

Solution
Firstly, you need to identify the real error which is preventing the posting. To do this without changing the programs, set a breakpoint in LMRBIU01 before executing the statement CALL TRANSACTION 'MR01' ...
Set the value of MODUS to 'A' (foreground) or 'E' (errors only), then press pushbutton 'CONTINUE'. This will allow the user to see the BDC session being posted, and therefore see the actual error which causes the problem.

WARNING: It is ESSENTIAL!!! that users are warned NOT to change
anything in the BDC session - this procedure must be used as a diagnostic tool ONLY.

To leave the transaction without posting anything, enter '/N' in the OK code field. Do NOT use the functions 'Back', 'Exit', 'Cancel'.

Once the cause of the error is determined, the relevant error message number/text must be reported back to the developers so that MR_CREATE_INVOICE can be modified to prevent the error situation.

Additional key words

MR44 SAPMM08R MR_CREATE_INVOICE SAPLMRBI

SAP Note 26966 - Background jobs do not start when transporting

Symptom:

Transports which were started with the transport control program tp do not exit. In the tp log file SLOG, the following messages are periodically written:
Background job not running properly. Function: ... Jobcount: ... Status: S
Please check the system. Use Transactions SM21, SM37, SM50.

Other terms

RDDIMPDP, RDDMASGL, RDDDIS0L, RDDGEN0L, RDDDIC0L, RDDDIC1L, RDDDIC3L, RDDVERSE, RDDVERSL, RDDEXECL
TR496

Reason and Prerequisites

When executing transports, programs are started within the SAP System. These programs are scheduled as background jobs.

Background jobs are started as separate processes (type BTC in Transaction SM50). If all such background job process slots are occupied no new background jobs can be started. These jobs stay locked until there are process slots free.

Sporadically it may also happen that the scheduled batch jobs hang in status "ready" or "scheduled" despite of there being free BTC processes. So far we have no plausible explanation to that phenomenon.

Solution

The solution to this depends on whether the background processes are just temporarily over-used, or whether a long-term bottleneck exists.
If the capacity overload is only caused by one or two very lengthy background jobs that are not regularly scheduled, a little patience is the best remedy. After these jobs terminate, the transport programs will also exit correctly.
The number of background processes or application servers which are used to process background jobs should be increased if the capacity overload for background processing is long-term. Details for this can be found in the "BC System Administration" manual, in chapter 4 (Configure Background Processing).
The Transactions SM50 (process overview of an application server), SM51 (overview of the application servers) and SM37 (overview of background jobs) can be used for analysis. Details for this can also be found in the "BC System Administration" manual in chapter 4.

If the batch jobs do not start despite of free BTC processes, you can work around the problem by scheduling those "hanging" jobs again using Transaction SM37 (Job -> Repeat scheduling -> Immediate). It is important that you repeat the job scheduling as user DDIC (the user under which the original job had been scheduled).
According to our experience, the batch system will work without problems afterwards.

SAP Note 26965 - Charts of accounts: DBIF_NTAB_TABLE_NOT_FOUND

Symptom:

When copying or deleting charts of accounts, the system writes a dump with DBIF_NTAB_TABLE_NOT_FOUND, C501 was not found.

Table C501 is only an example. Any table between C501 and C999 can be missing.

Cause and prerequisites

Inconsistency between Customizing and DDIC.

Solution
Caution: it is assumed that the condition table is not required.

You can delete the condition table with Transaction VK04.
Enter 'C', 'V', and the number of the condition table (for example, '501'). Use the 'Delete' function to delete the condition table.

Important: in Releases before 3.0F, the 'Delete' function can be found directly on the first screen. From Release 3.0F, this function can be found on the second screen.

Additional key words

Account determination, ORFB, OBY7, OBY8, OBY9, T681

SAP Note 26962 - Payment prog. + lost cash disc. for net posting

Symptom:

If the payment program pays a net-posted invoice so late that no cash discount can be deducted anymore, the transfer posting from the cash discount clearing account to the account for lost cash discounts is not made in the payment document.

Cause and prerequisites

Program error in version 3.0A

Solution
Corrected in 3.0B

Additional key words

SKV

The customer can import the planned values, either from tables, which are read using ABAP/4, or via a dialog box programmed by the user. In Customizing, the 'Profit basis' field must have the characteristic 'X' so that the planned values are determined this way.

As of Release 3.0B, the customer can change the planned values imported by the system. Here, the system imports the planned values according to the setting in the valuation method and branches to the customer enhancement prior to the results analysis accounting of each period. In Customizing, the 'Valuation basis' field must have an entry from value range '0-9' to make this possible.

As of Release 4.5, you can assign the actual values read by the system to other line IDs. You may not change the actual values in total. To allow this, field 'Valuation basis' in the Customizing should contain an entry from value range '0-9'-

To use customer enhancement 2, you have to execute several actions:

Include the customer enhancement using Transaction CMOD.

Create a project; this is not a project from SAP Project Management System.

Assign the SAP enhancement KKAG0001 to the project.

Choose the component EXIT_SAPLKKAG_002 from this enhancement; this is a function module.

The function module contains the include module ZXKAGU02. Branch to this include and maintain your program code there.

When your module is complete, activate the project.

Branch to the Customizing of Results Analysis and choose the maintenance of the valuation methods and branch to the detail screen.

If you want to import the planned values yourself, enter an 'X' in the 'Profit basis' field.

If you only want to change the data imported by the system, then enter a number from value range '0-9' in the 'Valuation basis' field. You can use the numbers to control the program flow in the function module. (This has been available as of Release 3.0B)

Interface of the function module EXIT_SAPLKKAG_002:

Import parameters
ABGRENZUNGS_SCHLUESSEL Results analysis key
ABGRENZUNGS_VERSION Results analysis version
BEWERTUNGSBASIS Valuation basis
BEARBEITUNGS_WAEHRUNG Currency of results analysis accounting
COEP_KOKRS Controlling area
COEP_BUKRS Company code
AUFK_AUFNR Order number
PRPS_PSPNR Internal project line item number
PRPS_POSID Work breakdown structure element
VBUK_VBELN Sales and distribution document number
VBUP_POSNR Line item no. of the SD document
OBJEKTNUMMER Cost element itemization number
BEARBEITUNGS_PERIODE Period of processing
BEGINN_OFFENE_PERIODE First open period

CHANGING parameters
POSITIONS_NETTOERLOES Plan.revenue of line item no. of SD document
STRUKTURPLAN_ERLOES Work breakdown structure revenue
STRUKTURPLAN_KOSTEN Work breakdown structure costs
BASIS_PLANMENGE Plan.quantity of line item no. of SD doc.
BASIS_PLANMENGE_EINHEIT Header unit

Table parameters for data import and export
EXPORT_BASIS Table w. (actual and) plan.values for valuation
EXPORT_ISTTAUSCH Table for changing the actual data assignment

Exceptions
FEHLER_MIT_NACHRICHT Error with message from this module
FEHLER_OHNE_NACHRICHT Error without message from this module

The meaning of the import parameters is self-explanatory to a large extent. The 'Valuation basis' field contains the contents of the 'Valuation basis' field of the valuation method detail screen. The program flow in the function module can be controlled this way.
If you change the valuation basis (you are using valuation basis 0-9), BEARBEITUNGS_PERIODE contains the period for which the results analysis is just being carried out. Please take into account that the customer enhancement is first called for the closing period (i.e. for the period before the first open period to accrue). Thus, if you carry out the results analysis for exactly one period, the customer enhancement is called twice. If you are not interested in the data of the closing period, do not change the valuation basis until the condition "BEARBEITUNGS_PERIODE >= BEGINN_OFFENE_PERIODE" is met.
If you change the planned data (you use profit basis X), the customer enhancement is called once befor the periods are processed. Parameters BEARBEITUNGS_PERIODE and BEGINN_OFFENE_PERIODE are not filled.

The planned values not depending on cost elements are processed using the change parameters. The change parameters are declared as export parameters in Release 2.2.

The table 'EXPORT_BASIS' imports the actual and planned values imported by the results analysis program. The planned values are changed in the customer enhancement in table 'EXPORT_BASIS' or set up again, and then exported back to the results analysis program. Actual data changes in table 'EXPORT_BASIS' are ignored.

Error-related exceptions for extraordinary returns from the function module can be programmed with the statements

MESSAGE E300 WITH <... 2> <... 3> <... 4> RAISING FEHLER_MIT_NACHRICHT

RAISING FEHLER_OHNE_NACHRICHT

The table 'EXPORT_BASIS' has an underlying structure. In the definitions of the specified domains, a list with fixed values, the meaning of which is also explained there, is predefined in each case. The ZLNID field is an exception; its allowed values are defined in the 'Update' table in Customizing.

The table 'EXPORT_BASIS' has the structure 'XKABASIS'. Only the first field is a key field.

Field Domain Meaning
ZLNID ZEILEN_ID Line ID
BEWKZ ABGR_BEWKZ Valuation indicator
KATEG KATEGORIE Category
ISTKUMKG Accumulated actual value, total
ISTKUMKF Accumulated actual value, fixed portion
ISTJHRKG *** currently not used ***
ISTJHRKF *** currently not used ***
ISTPERKG Actual period value, entire
ISTPERKF Actual period value, fixed portion
PLANBEWKG Overall planned value, total
PLANBEWKF Overall planned value, fixed portion
ISTMNGKUM *** currently not used ***
ISTMNGPER *** currently not used ***
PLANMNG *** currently not used ***

If you use the setting 'Profit basis = X', the value fields for planned and actual values are empty when the data is transferred to the function module. You can then enter the planned values after the data transfer.

If you use the setting 'Valuation basis = 0,1,2, ...,9', the value fields for the planned and actual values are provided with values when the data is transferred to the function module, and you can change the planned values once the data has been transferred.

Additional key words

The description 'Work in process calculation' is also used instead of the description 'Results analysis'.

Keyword: EXIT_SAPLKKAG_002, KKAG0001, ZXKAGU02

SAP Note 26955 - Resource-related billing doc. (VA90) 'Date_invalid'

Symptom:

1. Resource-related billing document ( VA90 ) causes a dump, 'Date_invalid'.
2. Creating credit memo requests and debit memo requests from Contacts produces error message V1185.
3. The same message can appear during first data transfer with program rvinvb00.

Cause and prerequisites

This happens if the following applies:
- a resource-related billing document exists for a plant maintenance order
- the plant maintenance order is not allocated to a sales order
- a calendar for billing schedule is allocated to the customer in the master record

Solution
The following preliminary correction is possible.

SAP Note 26954 - Calculation of AWE after the PIW is created - SSP

Symptom:

The user inputs the details of a SSP1L form on an employee starting with the company. The AWE field is left blank and the absence processing routine should calculate and fill this based on the first linking absence in this employment.

Cause and prerequisites

SSP1L form input to the PIW infotype P0085 without AWE value

Solution
Code must perform the routine to find the correct Average weekly earnings.

SAP Note 26953 - SAPDBA: User/password problems

Symptom:

The user can no longer log on to the database with SAPDBA using the password that he choses.
In particular, entry by changing online/batch (password in protected file) no longer works, that is, the call: sapdba -check -u system < does not work!

Cause and prerequisites

The length of the string in the UNIX function getpass is limited on some BS and is unfortunately always read from the keyboard rather than STDIN!
The length restriction is determined in the MACRO: PASS_MAX, in the file /usr/include/limits.h!

Solution
There is an additional option with 3.0B or 2.2G -l (for long user_name), which makes the old transparent entry via STDIN and with long names possible again!
Here are the different procedures for using the password:
Examples
1.) BATCH:
'sapdba -check -l system < ', where contains the password of the SYSTEM user.
2.) ONLINE:
'sapdba -l system < '
3.) ONLINE:
'sapdba -l system', where SAPDBA processes the password in the foreground.
4.) ONLINE:
'sapdba -u system', where SAPDBA processed the password in the background.
5.) ONLINE or BATCH also permit the use of
OPS$ mechanisms:
'sapdba -u /', where the OPS$ must be in possession of the DBA roll.

SAP Note 26952 - IBIP: EQUZ-MAPAR does not exist on SAPMIEQ0 102

Symptom:

Producer subnumber was sent to wrong screen

Cause and prerequisites

Program Error / as of 2.2 the fields have been moved

Solution
Correction P30K016728 Transaction: Se38
Report: libipfeq

Additional key words

s00349 Field 2 does not exist in screen &3 &4

SAP Note 26949 - CJ02,WBS fore.dates->V0102 entry miss.table T185V

Symptom:

Access the initial screen of WBS element maintenance by means of CJ01, CJ02, CJ03. From there, call up the date view. If you then press F3 or Cancel, the following error message is issued:
Flow control: Entry SAPLCJTR, EX, 0101 is missing from table T185V

Cause and prerequisites

Missing entries in table T185V

Solution
See below

SAP Note 26948 - VA01 Material text disappears

Symptom:

1. If you enter a valid material number when entering a sales document
(ENTER)
2. then overtype it by mistake with a non-existing material number
(ENTER)
3. and then enter the material number as in 1.

the material description in the item disappears.

In the creation of the delivery, the requirements of the order are then incorrectly reduced.

Cause and prerequisites
Solution
The following repair can be carried out as of 2.2C:

Additional key words

Article short text vbap-arktx vbap-sumbd

SAP Note 26947 - Foreign trade : Negative statement - consulting

Symptom:

For what purpose is the negative statement used on the foreign trade screen - material master

Cause and prerequisites
Solution
The field negative statement is used within export control according to the AWV (German export administration act in Germany).
If a number exists here and the date is valid, then this material number is considered as "not requiring a license" during the export control check.

SAP Note 26946 - Time scheduling

Symptom:

In time scheduling, the duration which results from the difference between the finish date and start date in the 'Copy top-down' function, is always incorrectly specified as 9999.9

Cause and prerequisites

Incorrect source code in LCJTRFO1

Solution
see below

Additional key words

Copy_top-down, project planning board, planning according to structure

SAP Note 26945 - Cash discount for subsequent delivery costs

Symptom:

If you subsequently enter unplanned delivery costs (that is, the item value without additional costs is zero at first), no cash discount was deducted from these additional costs during net posting (that is, it was posted as with a gross amount document type).
The following messages also appea:
EM8999 (no text) in release 2.2 and
EM8199 "Cash discount clearing account for tax code could not be
determined" in release 3.0.

Cause and prerequisites
Solution
Program correction

Additional key words

MR01 MRHR MRHG, delivery costs net

SAP Note 26943 - Function 'Change inspect. point'(QA22) incorrect

Symptom:

If you use inspection points without partial lots (TQSS1-PPKZTLZU) for in-production inspection and inspection points have already been entered for the production lot, error message QT303 is issued when you run transaction QA22.
´No inspection points are available for the partial lot 0000´.

Cause and prerequisites

Cause: Program error
Preconditions: In-production inspection with inspection points without partial lots.

Solution
As of Release 3.0B, in-production inspection lots with inspection points without partial lots can also be processed using QA22.
For Release 3.0A, the inspection points can be changed using transactions QE11 or QE12 (enter or change results for the inspection point).
To do this, within the transaction, choose Goto --> Data for inspection point.

SAP Note 26940 - Settlement rule JHR is copied with KO01

Symptom:

A capital investment measure which was created by copying is not settled to 'their' fixed asset but to those the reference order (that is, the capital investment measure used as reference).

Cause and prerequisites

Program error
If an order is specified as reference when creating a capital investment measure, the generated annual rule JHR of the reference is copied into the new order.

Solution
Please install the repair below in the program code.

Additional key words

KO01, posting rule, activation, settlement

SAP Note 26939 - Documentation wrong on how to get to Data Browser

Symptom:

Documentation wrong on how to get to Data Browser
Discovered by: Jim Murray (901)320-4249
The Instructions on how to reach Data Browser are wrong. It says from ABAP/4 Workbench the path is Test then Data Browser or Tools then Data Browser.

Cause and prerequisites
Solution
Docu: Text has been corrected.

SAP Note 26937 - Order list creates order group without '0H'

Symptom:

Transaction: KOL1
Program: RKOALI01
Description: With the help of the order list, order groups can be
created. However, these order groups cannot be changed
or displayed by means of the maintenance transaction
for order groups.

Cause and prerequisites

The order groups which are created in the order list do not start with '0H'. However, this is a requirement for the maintenance transaction for order groups.

Solution

Please make the following program code changes.
In addition, the input length of the 'Order group' field should be limited to 10 characters in the screen RKOALI01 0099. To do this, access the fullscreen editor in the transaction SE51 for the above screen and remove the last two positions of the input template for the 'Order group' field. Then please generate the screen.

Additional key words

KOH2, KOH3

SAP Note 26934 - Drill-down rep.: incorr.calc.comps. f. 1Dim w. ID

Symptom:

If rows, which are used in calculation lines (formulas), are hidden for a 1-dimensional form (row/column structure) with key figures, these dependent components might be calculated incorrectly.

Cause and prerequisites

This is caused by a program error.

Solution
Implement the following correction and then generate the affected reports again with the monitor KEMO or KCW0 (see also Note 84023 with
regard to re-generating).

Additional key words

Drill-down reporting, hide lines, RKEDU1ON, KE30, incorrect totals

SAP Note 26930 - PS txt and relationship changeable desp. netw.stat.

Symptom:

Relationships and PS text allocations can be maintained in the network although this is not permitted by the network statuses, 'Blocked', 'Completed technically' and 'Deletion indicator'.

Cause and prerequisites

Program error

Solution
Program correction

Additional key words

Status management

SAP Note 26928 - Incompleteness incorrectly reduced for texts

Symptom:

If you maintain texts via the incompletion log, then the status is not also correctly changed.

Cause and prerequisites

Program error

Solution
Please include the line indicated by "<- new in program MV45AF0F

SAP Note 26926 - ME25 Copy PReq then source determination

Symptom:

Transaction ME25 (create purchase order vendor unknown): If you copy a PReq as a reference, transfer the item(s) using transfer + detail and allocate a source of supply on the detail screen, the source of supply fields remain empty (contract number, info record number, etc.), except for the name of the vendor.

Cause and prerequisites

Program error

Solution
Corrected in Release 3.0B. You can implement a preliminary correction by inserting the lines indicated below in the specified program:

SAP Note 26924 - Activ. price calc.: Termin. with incorr. fld format

Symptom:

The activity price calculation terminates with the program error: Field of category P has incorrect BCD format. The field in question is BASF.

Cause and prerequisites

Program error
Preconditions: The activity price calculation is started for an interval which does not begin with the first period. In the version, it is determined that an activity price is to be calculated for the period. For individual cost center/activity types, however, it is determined in the planning that an average activity price is to be determined.

Solution
Perform the activity price calculation for an interval which contains the first period or make the following correction.

Additional key words

Transaction: KSPI, KSII

SAP Note 26923 - SAPLCXTP: COMPUTE_INT_TIMES_OVERFLOW

Symptom:

Abnormal termination with dump

Cause and prerequisites

The date entered for the conversion Date -> Internal second display exceeded the defined values.

Solution
Source code corrections

SAP Note 26913 - Error in SOP product groups graphic overview

Symptom:

Transaction MC92: Logistics -> Production -> SOP -> Product groups -> Graphics -> Overview.
The following error messages are displayed when the graphic is set up:
"Illegal node-id in line table"
"Third fieldvalue (node-id) in NVAL-table is unknown"

Cause and prerequisites

Error in the source code.

Solution
Correction P30K016081

SAP Note 26910 - Unit of measure can be changed in production order

Symptom:

The unit of measure for the material to be produced could not be maintained in the production order. If a production unit was maintained in the material master, it was copied during order creation; otherwise, the base unit of measure was copied. The unit of measure can now be changed in the production order until the order is released. This requires that the unit of measure can be converted into the base unit of measure.

Cause and prerequisites
Solution
Correction. The correction cannot be performed in advance.

SAP Note 26909 - SE16 - Security

Symptom:

Symptom:

When you call the insurance list RAVERS01 for future years, the insurable value of the past fiscal year or the value zero is displayed.
When you use the function 'Fiscal year change of insurable value' when you display/change an asset with transactions AS02 /AS03, message AA288 is issued:
Last fiscal year & for insurance fiscal year change reached

Cause and prerequisites

Forecast on insurable value of future years is not possible.

Solution
See long text of error message AA288;
For current market value insurance, you can carry out a simulation of the corresponding depreciation area with the asset value display AW01 or with asset lists or depreciation lists.
For value as new insurance, the system does not support any simulations of future vlaues.

Additional key words

AR10

SAP Note 26891 - Depreciation not reduced in shortened fiscal year

Symptom:

1. In the shortened fiscal year, a complete annual depreciation is calculated (and consequently also posted in the last period) even though the depreciation should be reduced proportionally.

Cause and prerequisites

In Customizing for the asset company codes, you have to determine for each area and depreciation type whether or not the depreciation should be reduced in a shortened fiscal year.
If you do not make an entry, the depreciation is not reduced!
Furthermore, you can determine for individual depreciation calculation keys that the depreciation for this key should not be reduced contrary to the general specification in the company code and depreciation area.

Solution
Maintain the specifications correspondingly in Customizing.
You can access the general specifications for each posting area and depreciation area using Transaction OAB1 and choosing "Company code > Shortened fisc. year" from the menu.
You can maintain the depreciation calculation keys using Transaction OA23.
For further details on how to process a shortened fiscal year, refer to the chapter "Fiscal Years and Periods" in the System Administration Guide.

As of Release 4.6, use Transaction AFAMA for the maintenance of the calculation keys.

Additional key words

AW01, RABUCH00, T093Y, T090-XRAFA

SAP Note 26886 - Credit limit: Date of next credit check, horizon

Symptom:

The date of the next credit check was not reset if schedule lines with a material availability date far in the future were in the credit horizon.

Cause and prerequisites

Program error

Solution
Corrected in 2.2G with P22K009558 and in 3.0B with P30K016202.

Additional key words

VA01, VA02, VKM4, VKM1, RVKRED01.

SAP Note 26882 - Billing plan: termination

Symptom:

The program terminates in an order with a billing plan with several
items.

Cause and prerequisites

Program error

Solution
Change Program LV60AF0F:

SAP Note 26881 - Credit limit: Report for sales doc. in horizon

Symptom:

A report which rechecks sales documents from the credit point of view in the background is missing if schedule lines which have a subsequent material availability date reach the credit horizon.

Additional key words

Credit limit, credit management

Solution
Corrected in 2.2G with P22K009555 and in 3.0B with P30K016202.
The program code in note 26886 is a requirement.

SAP Note 26880 - SAPcomm: No link to the SAP System

Symptom:

The component "SAP" of the communications server SAPcomm cannot make the link to the SAP System. Error entries in the log file (lyymmdd.sap) of the "SAP" component: E1521 Back from CMINIT: RC=20
E1506 CPI-C function CMINIT returns 20 = CM_PRODUCT_SPECIFIC_ERROR
E1508 > Additonal SAP CPI-C error information: .....RC=472....
E1707 Cannot open destination

Cause and prerequisites

The component "SAP" of the SAPcomm communications server searches for the entry, in the sideinfo file, DEST=. is taken from the SAPcomm configuration or from the "environment" (see SAPcomm manual or also Note 14930). However, this entry does not exist in the sideinfo file.

Solution
Add the entry DEST= to your sideinfo file. Alternatively, if a suitable entry already exists under another name, change the SYSTEM parameter in the SAPomm configuration file. Documentation on SAPcomm: "SAP Communications Server." Manual: Documentation for maintenance of the sideinfo files: "SAP Communication: Configuration."

SAP Note 26879 - Credit limit: Report for check in the background

Symptom:

A report which checks blocked sales and delivery documents from a credit point of view in the background is missing. This report should be started after the posting of incoming payments.

Additional key words

Credit limit, credit management

Solution
Corrected in 2.2G with P22K009558 and in 3.0B with P30K016202.

SAP Note 26875 - Data transfer deliveries: Reserve fields

SAP Note 26863 - Subcontract order with components in alternative QU

Symptom:

The goods receipt for a subcontract order which contains a component (material to be provided) in alternative unit of measure is rejected with message M7022:
EK quantity withdrawn exceeded by xxx.

Cause and prerequisites

The component quantity booked out in the purchase order history during the goods receipt was posted in the base unit of measure instead of in the alternative unit of measure. As a result, the system checks the quantity to be cancelled in order unit (for example, 1000 G) against the quantity booked out during the goods receipt in base unit of measure (for example, 1 KG). Since 1000 is greater than 1, the system rejects the cancellation.

Solution
Please use transaction MB01 (Goods Receipt for Purchase Order) with movement type 102 if you want to cancel already entered goods receipts.
You can cancel goods receipts entered after you have made the corrections described below with transaction MBST (Cancel Material Document).

Additional key words

MBST, subcontracting order item, cancellation, material document

SAP Note 26860 - Termination in VL70 for shipping conditions

Symptom:

Within transaction VL70, output of picking, an abnormal termination or a runtime error occurs in the respective report SD70AV4A when entering the shipping condition.

Cause and prerequisites

Program error: The parameter for the shipping condition is converted in the incorrect are table (range table).

Solution
Change the source code of program SD70AV4A with transaction SE38 (ABAP editor). Search for the FORM routine PARAMETER_CONVERT and at the beginning of the FORM routine (only in the first block) insert the correct area table RG_VSBED instead of the incorrect area table RG_VSTEL.
The error is corrected in Release 3.0B.

Additional key words

Output control, Selection conditions.

SAP Note 26858 - CO01 / CO02 : Loop during phantom assembly change

Symptom:

A loop can occur when you are changing a phantom assembly in the production order.

Cause and prerequisites

Program error

Solution
Correction in function module CO_IT_DUM_ASS_UPD

SAP Note 26857 - 'Period. transfer posting plan' not allowed

Symptom:

Error message: BS006 'Period. transfer posting plan' is not allowed
Transaction: KSWB
Description: With the periodic transfer posting, the above error message appears if orders or projects are involved.

Cause and prerequisites

Missing entries in system control tables

Solution
Run the following report in your system:

REPORT ZBSVRKPB .

TABLES: TJ01,
TJ05,
TJ07,
TJ31,
TKAVG.

UPDATE TJ01 SET VRGSV = 'X'
WHERE VRGNG = 'RKPB'.

SELECT * FROM TJ05 WHERE VRGNG = 'RKPV'.
TJ05-VRGNG = 'RKPB'.
INSERT TJ05.
ENDSELECT.

SELECT * FROM TJ07 WHERE VRGNG = 'RKPV'.
TJ07-VRGNG = 'RKPB'.
INSERT TJ07.
ENDSELECT.

SELECT * FROM TJ31 CLIENT SPECIFIED
WHERE VRGNG = 'RKPV'.
TJ31-VRGNG = 'RKPB'.
INSERT TJ31 CLIENT SPECIFIED.
ENDSELECT.

SELECT * FROM TKAVG CLIENT SPECIFIED
WHERE ACTIVITY = 'RKPV'.
TKAVG-ACTIVITY = 'RKPB'.
INSERT TKAVG CLIENT SPECIFIED.
ENDSELECT.

SAP Note 26854 - Early Warning system LIS: Change assignments

Symptom:

Transaction MCY5 (group exception: Change assignments). If the change simply consists of the deletion of an assignment, it is not recognized internally as a change and is not taken into account, for example, when saving.

Cause and prerequisites

Program code error

Solution
Repair

SAP Note 26853 - Customer hierarchy: Graphics profile missing

Symptom:

When calling up the graphic display from customer hierarchy maintenance, you get message CG014 'Graphics profile VDH Kundenhier_2, 2 is not available'.

Cause and prerequisites

Transport error

Solution
The missing graphics profile can be maintained as follows:
Transaction CNG4 -> New entries:

Profile group : VDH
Profile name : KUNDENHIER_2
Profile index : 2 Customer hierarchy

Object profiles :
Node profile : PG_KNOTEN__1
Link profile : PG_KANTEN__1
Frame profile :
Options profile : PG_OPTIONEN

Other (available or newly defined) simple profiles can also be used. In this way, the graphic display can be laid out individually.

Additional key words

Hierarchy graphic

SAP Note 26852 - Information on cross-company code transactions

Symptom:

In the case of cross-company code postings, the tax codes are always checked against the "initiating" company code and are posted there also. The initiating company code is always the company code of the first line item. It is displayed for control purposes following the tax codes for the items of the other company codes.

Cause and prerequisites

As of Release 2.2, the restriction no longer exists that the involved company codes must set up a taxable entity for cross-company code transactions (that is, the advance return for tax on sales/purchases was carried out through one company code for all other company codes). Therefore the taxes are now only posted to the initiating company code; consequently, the other company codes are not debited by tax.
Thus, the tax information for the entire transaction is stored only in the initiating company code and also only occurs in the advance return for tax on sales/purchases of this company code.

Also compare Release Note FI_22A_STEUERN for reference.

Solution

If you want to pass on the tax debit to other company codes, this must be done manually by document breakdown; generally the involved organizations must be invoiced for such transactions - at least as a matter of form - for legal reasons.

If you make the clearing entries manually, the transaction is to be split into two documents manually, and these documents are also to be entered separately.

1. Receivable in CCode 0001 from CCode 0002 with output tax

and

2. Payable in CCode 0002 to CCode 0001 with input tax

SAP Note 26850 - Run-time error in program "RFKORD10".

Symptom:

the "STAGE" field of program "RFKORD10".

Cause and prerequisites
Solution
Program change

Additional key words

RFKORD10, RFKORD11

SAP Note 26849 - Extensions to the SAP Reference IMG

Symptom:

Summary

Symptom

Customer-specific extensions should be included in the Reference IMG (Implementation Guide). These are displayed in the SAP Reference IMG, but are not copied into the Enterprise IMG.
After an upgrade the customer-specific extensions are not displayed anymore in the reference IMG.
After an upgrade the assignment of the customer specific activities for the application components are missing.

Cause and prerequisites

To transfer to the Enterprise IMG, the extensions must exist in a particular document class (SIMG) and must have the correct attributes. Generation of the Enterprise IMG is carried out via selection of application areas. Therefore, the documents created must at least be allocated to the application areas during attribute assignment. A complete attribute assignment is recommended to achieve problem-free operation within the projects.
After an unpgrade the customer-specific IMG extensions are not automatically transferred. This should provide an opportunity to check the new SAP structure first.
The assignment of the activity for the application components is stored in table TFM18. In Releases prior to and including 3.1G the table is exchanged. As a result the assignment of customer-specific activities for the components is lost.

Solution

Please check:

Is the extension a document of the class SIMG? Only these are taken into account when generating the Enterprise IMG or the Project IMG.

Are the attributes maintained for the extensions? The allocation to the application area must be maintained. The attributes "High priority function" and "Processing priority" should also be maintained as well as any possible country dependencies. Attribute maintenance can be reached via the menu Goto->Attributes for the document in the structure display / maintenance.

Are Customizing objects assigned to this activity? You can display the assigned Customizing objects in the maintenance screen for attributes. If there is no object assigned to an activity, you can maintain the assignment in Transaction SOBJ. Choose the desired object (for example, a view) and go to sub-object. The transaction to be called and the IMG activity will there be entered.

Save the assignments of the customer-specific activities for the application components as follows:

Create a transport request with the entry:

R3TR TABU TFM18
In the list of key fields enter the following:
DOKCLASS = "SIMG" DOKNAME = "Y*"
DOKCLASS = "SIMG" DOKNAME = "Z*"
Thus the transport request will contain all allocations for activities
in the customer name range.

Export this transport request prior to the upgrade and import it again after the upgrade.

To copy the extensions after the upgrade you have to process the changed SAP structures in the maintenace transaction again. After you choose Change, you are asked whether you want to copy the extensions that have already been maintained. Confirm this question and save the structure afterwards. Make sure that the structure has the status final version, otherwise it cannot be transported.
You should execute extensions as follows: Create the customer-specific structure in the IMG functionality first. This is included in the SAP reference IMG afterwards. To do this change the structure "SIMG_ALL" in language "D" with Transaction SO70. To include a structure "ZCUSTOMER" in structure SIMG_ALL enter there as document class "BIBL" and as document name "ZCUSTOMER". Afterwards you have to translate structure SIMG_ALL with Transaction SE63 so that the extension text can be displayed in this structure in other languages than German. For the translation the structure should be in the status "Active".

Header Data


Release Status:	Released for Customer
Released on:	06.04.1998 22:00:00
Master Language:	German
Priority:	Recommendations/additional info
Category:	Consulting
Primary Component:	BC-CUS Customizing

Affected Releases

Software Component	Release	From Release	To Release
SAP_APPL	30	300	31I
SAP_APPL	40	40A	40B
SAP_APPL	45	45A	45B

Additional key words
Customizing

SAP Note 26846 - Paymnt on acct for asset with nonval. GR -> 2x APC

Symptom:

If a down payment and a valuated goods receipt are posted for a purchase order with account-assignment category 'Fixed asset', the down payment cannot (automatically) be cleared so that the APC of the fixed asset (or the AuC) are duplicated.

Cause and prerequisites

This is a basic accounting problem:
According to the opinion of the majority of the auditors, the goods receipt of a fixed asset should already be displayed in the fixed assets, that is, it should be assigned to a fixed asset.
However, a down payment can be cleared only if an invoice exists.

Solution
For assets under construction (down payments may generally only be posted to AuC), it is usually unimportant for tangible assets whether the received goods are displayed as "actual" APC of the fixed asset or as down payment because most of the depreciations and investment support measures allowed for assets under construction are already allowed for down payments.
We therefore recommend to post the goods receipt for purchase orders with down payments always nonvaluated. This can be set in Purchasing Customizing.

SAP Note 26840 - No skip for dynamic modification by inspection lot

Symptom:

Symptom

For dynamic modification by inspection lot, the sample calculation for all characteristics is always carried out with the beginning inspection stage. A change of sample size in accordance with the planned inspection severities and a skip is therefore not possible.

Cause and prerequisites

Program error

Solution
Program correction in function module QDSE_DYNAMIC_SAMPLING

Additional key words

Inspection processing Dynamic modification Inspection stage Inspection severity Sampling scheme Skip Skip lot Skip-to-stock

SAP Note 26839 - VA01, VA02: Credit check and incompleteness

Symptom:

Important: This note is obsolete !!!
The problem is solved with Note 395602 !!!

During order processing, documents are authorized from a credit point of view although the static or dynamic credit limit check exceeds the credit limit. The error occurs frequently if the dialog box for the imcompletion check is displayed after saving.
The procedure is as follows:

After you saved, the system issues the message "Credit limit exceeded"

and then the dialog box for the incompletion check is displayed.

The user completes the document and saves it again.

The document is then no longer blocked but approved. If the dialog box for the incompletion check is not displayed, the document is blocked.

Cause and prerequisites

This happens if the confirmed quantity is canceled with the subsequent function "Requirements availability" in case of a credit block (Transaction OVB8).
In general, the system carries out the credit check on the basis of the confirmed or approved quantity of schedule lines.

Solution
As a solution, we recommend that you start an availability check in the above case before saving again. The documents which are mistakenly approved do not represent any risk as the confirmed quantity in the schedule lines is zero.
If it is not possible or if you do not want to initiate the availability check, you should NOT cancel the reserved quantity with the subsequent function "Requirements availability" in case of a credit block (Transaction OVB8).

Additional key words

VA01, VA02

SAP Note 26837 - MaxDB: Data corruption, error -9026/-9028

Symptom:

Database error message -9026 BAD DATA PAGE
If the database determines such an error, the affected table can only be processed in reading status from that moment on. The following describes how write accesses with the error message BAD FILE (-9028) are confirmed.

In the SAP system, the error is logged as error -602 (for example, in the syslog or in a short dump).
The exact error message is logged in file knldiag in the database working directory.

Example (Version 7.4 or below):
...
11.11-17:25:53 19669 -512 page 0000270F08000001...0079005500290001
11.11-17:25:53 19669 -9026 BAD DATA PAGE 1355
11.11-17:25:53 19669 -9026 on DEVNO 1 DEV_OFFSET 1755
11.11-17:25:53 19669 -9026 /u4/filedevs/N61Adat1
11.11-17:25:55 19669 -512 page 0000270F08000001...0079005500290001
11.11-17:25:55 19669 -9026 BAD DATA PAGE 1355
11.11-17:25:55 19669 -9026 on DEVNO 1 DEV_OFFSET 1755
11.11-17:25:55 19669 -9026 /u4/filedevs/N61Adat1
11.11-17:25:57 19669 -512 page 0000270F08000001...0079005500290001
11.11-17:25:57 19669 -9026 BAD DATA PAGE 1355
11.11-17:25:57 19669 -9026 on DEVNO 1 DEV_OFFSET 1755
11.11-17:25:57 19669 -9026 /u4/filedevs/N61Adat1
11.11-17:25:57 19669 -11066 vfopen 'd1355.bad'
11.11-17:25:57 19669 -514 BAD FILE: 1359 (ROOT)
...

Other examples for error messages in file knldiag from Version 7.4:

1. Incorrect check sum:

ERR 4 Data Checksum mismatch; calculated: 38068804 found: 380688
ERR 13 IOMan Bad page on Data volume 1 blockno 262

The working directory contains file Data-1-262.bad.

2. Incorrect WriteCount:

ERR 5 Data Write count mismatch; header: 1, trailer: 51143
ERR 13 IOMan Bad page on Data volume 1 blockno 228

The working directory contains file Data-1-228.bad.

3. Incorrect page type:

ERR 6 Data Bad data page type 1
ERR 13 IOMan Bad page on Data volume 1 blockno 262

The working directory contains file Data-1-262.bad.

4. Header/trailer mismatch:

ERR 4 Kernel Header/Trailer mismatch
ERR 5 Kernel Header : ID: 0 Type: 1 Type2: 2 CheckType: 5 Mode: 0.
ERR 6 Kernel Trailer: ID: 0 Type: 1 Type2: 2 CheckType: 5 Mode: 0.
ERR 13 IOMan Bad page on Data volume 1 blockno 1

The working directory contains file Data-1-1.bad.

5. Incorrect page number:

ERR 18 IOMan Wrong page 14888 on Data volume 1 blockno 262
ERR 18 Data Bad data page 14888 of filetype 13 identified by root 14888
ERR 53021 B*TREE BAD FILE: 14888 (ROOT)

The working directory contains file Data14888.bad.

Other terms

BAD FILE, block corruption, -9028, -602, -9018

Reason and Prerequisites

Error message '-9026 BAD DATA PAGE ...' occurs when the page delivered from the operating system does not correspond to the required database page during an I/O request. This can be determined using several tests. For example, the page number is checked and a header trailer check is carried out.

The cause for such errors is found in the areas disk periphery, disk controller, RAID controller, RAID software, disk caches and so on.
This is why the affected HW components and their 'accessories' must be thoroughly tested and defect parts be replaced after the error occurs.

Solution
The database provides some information for the error analysis in knldiag or knldiag.err.

The database page should only be read with the logical number 1355 in this example. The space required on the disk is determined from the control structures: Device (volume) 1 Offset 1755. The reading procedure delivers a block, whose first and final 8 bytes are also logged. In the example, the page read has in the first 4 Bytes the value x'270F' = 9999, this does not, therefore, match the required 1355.

Since the peripheries are often driven with RAID (1 or 5), there is the possibility that the RAID is implemented in such a way that the corrections are not executed synchronously, but only once the read request takes place. For this reason, the read request is repeated twice in intervals of 2 seconds after the error occurs, and is only noted as an error after the occurrence.
An additional file is created in the working directory (*.bad) which contains the complete 8K block as it was delivered by the operating system. This image can be displayed using the MaxDB diagnostics tool x_diagnose.

The root of the affected table or the B* tree of the affected table is issued as further important information. This number (1359 in this example) enables you to determine the name of the affected table using the Database Manager (CLI) tool:

dbmcli -d -u , -uSQL , sql_execute select * from roots where root =

For example:
dbmcli -d N61 -u control,control -uSQL sapr3,sap sql_execute select * from roots where root = 1359

This statement delivers the name and the entry, whether it is a index, a primary table or a table for LONG buffers with short LONG column.

If the table name is known, execute the following SQL statement in the Database Manager (CLI):

dbmcli -d -u , -uSQL , sql_execute check table

This statement checks the tree consistency of the operative data of this table, and even resets the file status to ok, if required, if the table was subject to an asynchronous RAID correction (pseudo corruption), but the B* structures should now be faultless again.

In general, the complete operative dataset should be checked using a verify (check data).
You can use the 'Check -> Database' menu option in the Database Manager (GUI) tool.

If the check data or check table continues to return errors, a recovery of the data is required.

Since a data backup does not run correctly if a BAD DATA PAGE is contained in the contents to be backed-up, you can always access the most recent successfully saved complete backup; you must then still import incremental backups or log backups which correspond to the backup scheme, or simply restart if the log information in the log volume (Logdevspace) has not been overwritten yet.

If the defect objects are indexes exclusively, they can be deleted and recreated using the SAP System Data Dictionary. Following the index reconstruction, a verify in database status COLD (ADMIN) is required. This only works using the Database Manager (GUI and CLI) tool; the xpu cannot be used in COLD (ADMIN) status.
Due to the defect pages, the B* tree of an index may not have been deleted completely. During the deletion process, an error is not reported, but it is impossible to create a backup in this state. The verify in cold status (check data with update) deletes all remaining pages of the deleted B* tree.

If there is no backup for a recovery, your consistency check and backup concept is insufficient.
You cannot correct the corrupt data. Development Support can carry out an analysis as part of the SAP remote consultation (subject to charges, Note 423778) and can try to save the data that is readable. However, SAP cannot provide a guarantee for success.

During remote consulting, individual tables may be restored from other tables. Application Support will decide this.

The following is a list of tables that can probably be restored by application support:
BSAD, BSAK, BSAS, BSID, BSIK, BSIM, BSIS, BSIW, BSIX

Tables that can be created as empty tables and are automatically filled when the system is stopped (even if only one of the tables is affected, all of the tables for the relevant row must nevertheless be emptied for consistency reasons):
D010L, D010Q, D010Y, D010LINF
D020L, D020LINF, D021L, D021LINF
D346T, D342L
DDFTX
D344L
REPOLOAD
DYNPTXTLD, DYNPLOAD
DDLOG

SAP Note 26836 - Adoption of fields in contract release order, item category

Symptom:

If you create a release order with material number for a contract item with item category M (material unknown), various fields are always drawn from the contract and not from the material master or info record. The specific fields involved are the following:

MAHN1, MAHN2, MAHN3 (reminder levels)
KZABS (acknowledgment requirement)
BSTAE (confirmation control key)
MWSKZ (tax code)
WEBRE (GR-based invoice verification)
UNTTO (underdelivery tolerance)
UEBTO (overdelivery tolerance)
UEBTK (unlimited overdelivery)
EVERS (shipping instructions)
SKTOF (indicator: "cash discount")
PLIFZ (planned delivery time)
WEBAZ (GR processing time)
EKKOL (condition group)
IDNLF (material number used by vendor)
INSMK (quality inspection indicator)

plus the additional fields in Release 3.0:

LTSNR (vendor sub-range)
MEPRF (pricing date control)
INCO1, INCO2 (Incoterms at item level)
MHDRZ (minimum remaining shelf life)
KOLIF (prior vendor)
EBONF (indicator: subject to volume rebate)
BONUS, EBON2, EBON3 (volume rebate groups)

Cause and prerequisites

Program error.

Solution
Corrected as of 3.0B. The new logic provides that the fields are only adopted from the contract if they contain entries there. Otherwise they are taken from the info record. If no info record exists, they are taken from the material master record.
You can implement the correction in advance by inserting or changing thelines indicated below in the specified program. The correction shown below relates only to releases 2.1 and 2.2!

Additional key words

ME21.

SAP Note 26835 - Line item: Double values

Symptom:

Message: Double values in the list

Cause and prerequisites

Program error.

Preconditions:
The group was displayed with 'Environment' OR
the entry window was requested with 'Process,' but the window was later
terminated with F12.
Example:
'Enviroment' --> 'Cost element group'. Then you returned back to the initial screen. After this the line items existed twice.

Solution
1. Do not use the function 'Environment --> ..' until Release 2.2G/2.1M or 3.0B.
2. In urgent cases, you can make the following advance correction.

Additional key words

Transactions: KSB1, KOB1, KSB2, KOB2, CJ74, CJ76

SAP Note 26833 - FI-SL: XPRA RGUXI301 causes error (GLU1...)

Symptom:

The XPRA RGUXI301 displays the error message: 'Foreign key with cardinality 'X' for type DYNP is not supported' (or a similar message). GLU1 cannot be activated.

Cause and prerequisites

A DDIC error during the Repository switch inserted 'X' into the cardinality.

Solution
Following correction to the coding

Additional key words

RGICGLU1, SAPLGLIN.

Symptom:

Goods receipt for the purchase order. One of the order items is deleted without goods receipts or invoice receipts being created for the item. The goods receipt is posted automatically with the outstanding quantities.

Cause and prerequisites

Missing exit.

Solution
Corrected in Release 3.0B.

SAP Note 26812 - Analysis option for batch costing run

Symptom:

When costing a costing run in the background (Transaction:CK65), it is possible for you to write the costed materials to the job log.This makes it possible for you to display the sequence of the materials costed, which can be very useful in the event of a program termination.In most cases, you can determine the material that caused the program termination in this way.
As of Release 3.1I, message CK576, which is written to the job log during parallel processing of a costing run and which is used to check the work progress, is only written if it has been activated as described below.This prevents the job log from becoming unnecessarily large.If required, you can activate the message for analysis purposes.

Other terms

Analysis tool for costing run in the background

Solution

To ensure that the costed materials are written to the job log when costing a costing run, proceed as follows (up to and including Release 4.6B):

Preparation:

a) Include a variable with the value 'X' in table TVARV using Transaction SM31: Menu: 'System -> Services -> Table maintenance', enter table 'TVARV'; choose the 'Maintain' pushbutton and enter any variable name; set the 'Type' radiobutton to Parameter and choose the 'Create' button; enter the parameter value 'X' in the dialog window; choose the 'Save' and the 'Back' pushbutton.

Create a variant for costing a costing run:

b) Main menu: Logistics -> Production -> Product costing -> Costing run -> Material -> Costing -> Proceed -> Background (Transaction: CK65) -> choose the 'Variants' pushbutton and enter any variant name; choose the 'Create' pushbutton and maintain the input fields 'Costing run' and 'Costing run date' on the next screen and go to the next screen by choosing the 'Continue' pushbutton; enter any text in the 'Description' field and select the 'Hidden' and 'Variable' checkboxes for parameter ANZMATNR; choose the 'Selection variable' pushbutton and enter the variable created under a) on the next screen; Save your entries and return to the screen 'Execute Report in Background'. There, enter SAPRCK10 in the 'Report names' field and the name of the just created variant in the 'Variant name'field.

Procedure as of Release 4.6B:
a) Call up Transaction STVARV, choose the "Display < > change" and the "Change" pushbutton; enter any variable name for parameter ANZMATNR and value X and choose 'Save'
b) CK40N costing process step, change parameters, choose the pushbutton variant attributes -> pushbutton "Display all selection criteria" -> set the selection variable indicator for ANZMATNR and choose the selection variable pushbutton -> enter the name of the created variable a) and choose 'Save'

In the job log, the following information is issued under the message number CK416 in the 'Message' column: Material number, plant and costing number (that is, the MBEW fields:MATNR, WERKS, KALN1).

To achieve as of Release 3.1I that the success message CK576 is written to the job log during parallel processing of a costing run in the background, proceed in the same way:Create a variable with any name and with parameter value 'X' in table TVARV. Assign this variable to parameter ANZBLOCK.The procedure is the same as described for parameter ANZMATNR above.

SAP Note 26806 - ME16: Document line missing in list output

Symptom:

During the list display of deletion proposals for purchasing info records (ME16), no line containing the last purchase order is outputted, although the relevant header line and navigation options (Environment -> Purchase order) exist.

Cause and prerequisites

Functionality not previously defined.

Solution
Added in 3.0B. You can make the following advance correction by inserting the line indicated below in the specified program.