SAP Note 26341 - Transfer of lot size ind. costs from MRP profile

Symptom:

You create an MRP profile, selecting the field "Lot size independent costs". You then create the MRP view on a material, entering the MRP profile as a reference. If, in the company code for the plant, a currency applies that does not have two decimal places, the lot size independent costs are not transferred correctly. (If, for example, the currency is the Italian lira, the value 1.00 is changed to 100.)

Cause and prerequisites

The currency field of the company code is assigned to the field "Lot size independent costs". However, this assignment does not make sense here since the MRP profile applies to all clients.

Solution
Problem corrected in Release 3.0B.

Additional key words

Transactions: MMD1, MMD2; program: SAPMM03D; field: MDIP-LOSFX

SAP Note 26339 - Weight condition for alt. weight unit

Symptom:

In the material master, alternative units of measure are defined with an alternative weight unit or volume unit.
If the unit of measure is changed to the entry quantity in order processing, the value of the weight conditions or volume conditions is incorrect.

Cause and prerequisites

The conversion factors were not redetermined

Solution
Corrected in 2.2G/3.0B

Additional key words

VA01 VA02 Pricing condition base value

SAP Note 26347 - IBIP:Message batch input RIWO00-SELEC(02) not ...

Symptom:

RIWO00-SELEC(02) on SCREEN SAPMIWO0 ( 3400 / 4000 / 3000 / 1000 )
not available.
FM: S 00349 S00349 field RIWO00-SELE screen SAPMIWO0 nnnn

Cause and prerequisites

1. The window size you are working with is smaller than the standard size of 25 lines.

2. Variable step loops larger than 25 lines not capable of batch input.
Compression within border has too much space.
Refers to Release 3.0A-3.0C

Solution
1. Enlarge your window by at least 25 lines. If this is not possible,
use the second solution.

2. Another method is to change the loop from variable to fixed. This
ensures that two loop lines are always available for batch input.
For this, start Transaction SE52 for program SAPMIWO0 and the
corresponding screen. Confirm function key 'LOOP' and afterwards
'Fixed Loop'. After this, save and generate the screen.

3.) Special procedure for 3.0A-3.0C, if the batch input for a window
with 25 lines does not work.

SAPMIWO0 3400 / 4000 must be zoomed out.

Transaction: SE51
Program: SAPMIWO0
Screen: 3400/4000/3000
You must gain an additional 2 lines. You can check this by the number of lines occupied in the screen attributes.

Delete the outer border. You can also delete blank lines. The step loop must not be within a border.

*--------------------------------------------------------------------*
The result should resemble the diagram below.
Go to the screen attributes. Check the number of lines occupied.

Lines/columns occupied 24 83 <------ Important
maintenance 26 83

EXAMPLE: Screen 3400 of SAPMIWo0

Additional key words

IBIP, batch input, IQS1, IQS2, S00349, SAPMIWO0, IW15, QM04

SAP Note 26329 - oncatlgr: "The catalogers' named pipe is missing."

Symptom:

When carrying out database archives via CCMS (transaction DB13), the archive terminates and the following error message appears in the file '~adm/archive.log':
21:30:47 The catalogers' named pipe is missing.
21:30:51 Attempt to start cataloger failed.
In most cases, there are several oncatlgr's in the process list after such a termination.

Cause and prerequisites

The program 'infarcexe' (which is started by the R/3 System) tests first whether an oncatlgr process is already running in the system and whether the named pipe of this process ('/tmp/IX_ARC_CAT_V6.') exists.
If the named pipe is missing, then the above error message is written to the log file and a new oncatlgr is started.

There are two reasons why this named pipe can be missing:

a) If the system runs using database version 7.x (for example, under OSF/1 on a DEC alpha), this error message appears continually since the name of the pipe has changed to '/tmp/IX_ARC_CAT_V7.' in this case.

b) The named pipe in the '/tmp' directory was deleted manually.

Solution

This problem has been corrected starting with SAP release 2.2G and 3.0C.

Until then:

• Under the user informix, stop all oncatlgr processes using "stop_onctlgr".

• If the system runs using database version 7.x, use the following workaround until a new infarcexe is released:
  su - informix
  cd /tmp;
  ln -s IX_ARC_CAT_V7. IX_ARC_CAT_V6.
  

• Use Note 24253 to help get rid of any inconsistencies that may arise.

Additional key words

ccms, db13, onarchive, oncatlgr, archive, named pipe, infarcexe

SAP Note 26327 - RFFOD__L: Field T23 filled incorrectly in lang. E

Symptom:

If the German foreign payments program for DME is started and the system language of the user is English, the contents of the T23 field are cut off so that information on the payment document is missing.

Cause and prerequisites

The translation of the respective text is incorrect.

Solution
You can correct the translation using transaction SE63:
Translation->Short texts->Program->Numbered texts
Program RFFOD__L
From language D
To language E
Proofread and translate

706 Beleg &ZBUKR &GJAHR &VBLNR
Document &ZBUKR& &GJAHR& &VBLNR& <<< INCORRECT
Doc. &ZBUKR &GJAHR &VBLNR <<< CORRECT

Additional key words

RFFOD__L, printing forms, DME

SAP Note 26325 - 3.0: Manual avail.check during assembly

Symptom:

If a manual availability check is started for an order item with an assembly order (production order or network), then errors occur in the screen sequence control or the transaction is exited after the check.

Cause and prerequisites
Solution
Extensive correction in 3.0B

SAP Note 26323 - Network: Partially confirmed activities

Symptom:

Duration of partially confirmed activities that is used for scheduling is calculated incorrectly.

Cause and prerequisites

Program error

Solution
Program correction
If necessary, only implement the changes in LCXTMF13 from note 22917.

Additional key words

Scheduling network reduction

SAP Note 26321 - Process order cannot be technically finished

Symptom:

Control recipe(s) were created for a process order, and all of these control recipes were terminated or exited using PI_CRST process messages (Status 00004 or 00005).
In the process order, the status SRen (control recipe exited) is set correctly in the header.
However, the status SREZ is not deleted.
Therefore, the function "finish technically" cannot be performed.

s Cause and prerequisites

The problem has been solved in 3.0b.

Solution

Call transaction bs32. Double-click on business transaction "CRFI" (exit control recipe). Activate "Delete" on the following screen under status I0241 (SREZ).
You will need authorization S_TABU_DISS to carry out bs32.

Additional key words

Finish technically, control recipe statu

SAP Note 26320 - Value display: parameter AFB gets lost

Symptom:

The SAP parameter 'AFB' (depreciation area) exists for value display in Asset Accounting. This parameter is provided for this transaction only.
However, the default setting in the user master record goes missing when the value display is called up.

Cause and prerequisites

Up to now, this was provided for internal use only

Solution
Advance correction in the modules MA03WTOP and MA03WO01. The syntax can only be checked in the main program, SAPMA03W.

Additional key words

SAPMA03W AW01

SAP Note 26319 - ERS procedure: Separate document type for ERS doc.

Symptom:

ERS procedure: The document type cannot be set separately for documents that are created by ERS without enhancement (user exit).

Cause and prerequisites

This was not programmed.

Solution

Read Customizing table 'Transaction-dependent Defaults: Invoice Verification' (T169F) with transaction 'MRRS'.
Priority during the document type determination:

1. Return of document header data from the customer enhancement

2. Entry for transaction 'MRRS' in table T169F

3. Entry for transaction 'MR01' in table T169F.

Corrected in Release 3.0B. Advance correction:

Additional key words

RMMR01RS, MRRS, ERS

SAP Note 26317 - Set up for LOGON group for autom. load balancing

Symptom:

It is unclear how the LOGON groups should be set up for automatic load balancing.

Other terms

CCMS
Transaction SMLG
Group logon
Group logon procedure
SAPLOGON
SAPGUI

Reason and Prerequisites

Group distribution can be configured in a variety of ways.

Solution
Introduction

LOGON groups are used to automatically distribute user logons to individual instances or to groups of SAP instances (Applications Server).
The idea behind this is that a user does not log on to a special instance but rather logs on to a so-called LOGON group, and is then logged on to the relevant instance with the lowest load (that is, the best average response time. The advantages of using this procedure are twofold:

1. Users are no longer tied down to individual instances that might possibly become overloaded.

2. Since users now log on to logical LOGON groups and not to physical instances, instances can be exchanged or created within a group without the SAPGuis having to be reconfigured.

LOGON group maintenance

LOGON group maintenance and configuration can be carried out using Transaction SMLG (Tools -> Administration -> Computing center -> Management system -> Configuration -> LOGON Groups).

a) A common group is used for all instances. If only a small number of instances exist, this configuration is the best solution as regards optimal load balancing and redundancy. Only if a larger number of instances exist does it make sense to distribute users for each specific application to two or more instances. Example of a system with only a few instances:
Instance Group Max. no. users Max. average resp. time
app1_C11_00 Public
app2_C11_00 Public
app3_C11_00 Public

Example of a system with a large number of instances:
Instance Group Max. no. users. Max. average resp. time
app1_C11_00 FI-Users
app2_C11_00 FI-Users
app3_C11_00 SD-Users
app4_C11_00 CO-Users
app5_C11_00 CO-Users
app6_C11_00 SD-Users

b) One or more LOGON groups are set up for several instances. Several groups can be allocated to the same instances.
In this case, the users of a LOGON group are distributed in such a way that the load on each of the relevant instances is as little as possible. If only a limited of users are to be allowed access to instances, or if a predefined average response time may not be exceeded, then maximum values can be entered for the number of users or for the average response time. The optional definition of these values guarantees as much as possible that users are only logged on to the instance if the limiting values are not exceeded. However, the definition of limiting values does not prevent users from logging on to the instance directly. It is also possible to log on to an instance with exceeded threshold values if all of the instances available for the LOGON group in question were also defined with limiting values and these were subjected to a relatively greater load. Example:
Instance Group Max. no. users Max. av. resp. time
app1_C11_00 FI Users 20 1500
app1_C11_00 SD Users 20 1500
app1_C11_00 Adminstration 20 1500
app2_C11_00 FI Users
app2_C11_00 CO Users
app3_C11_00 SD Users

Note: The definition of limiting values is optional and is not normally visible. You can make this visible by choosing Properties -> Display Variants -> Change in the menu list. Double-click the logon group and a dialog box opens that allows you to adjust the limiting value.
Limiting values must always be kept uniform for each instance (this is regulated automatically by the maintenance Transaction SMLG), since the average response time or the number of users can only be calculated globally for each instance and not for user of a specific group. In other words, the limiting values apply to one instance, regardless of group, but at the same time, can be set up differently for the same group for another instance.
However, in most cases, it is unnecessary to specify limiting values since the sole aim is to achieve an even distribution of users with regard to system load.

c) Groups are set up for only one instance, but several groups can be allocated to an instance. The distribution of user logons resulting from this configuration is not dependent on the system load. That is why it does not make sense to define limiting values for user number or average response time either. The disadvantage of this is that if an instance is not available an alternative instance is not automatically provided. The group definition must then be changed so that the logons of the group affected are redirected to other instances.
Example:
Instance Group Max. no. users Max. av. resp. time
app1_C11_00 FI Users
app2_C11_00 CO Users
app3_C11_00 Administration

Technical information
The utilization information is determined for every instance by a report which is executed automatically every 5 minutes. This report stores information in a special storage area in the message server from which the SAPGuis can then request the best instances of a group at that particular point in time. To avoid situations where a large number of users want to log on within this 5-minute period (this would lead to a large load being placed on the best instances of a group at that particular point in time), the utilization information for each instance is updated after every fifth logon.

SAP Note 26316 - Incentive wages: Error in the gross wage form

Symptom:

1) When you try printing a gross wage form (for example, DL08 or DL09) using RPCEDT*0, a form will not be printed if data for the employee does not exist on cluster L1. 2)When you print out a gross wage form by means ofRPCEDT*0, blocked time tickets are also printed.

Cause and prerequisites
Solution
Programming error

Additional key words

RPCEDTD0

SAP Note 26315 - ME12 ME13 ME21 Wrong purchase order in info record

Symptom:

1. During the creation of a purchase order, the system suggests an incorrect price.

2. In the info record, a purchase order that belongs to a different material or a different vendor is shown as the last purchase order.

Cause and prerequisites

Unknown. Possibly an undetected problem from the past.

Solution
The incorrect relationships can be cancelled with the following report. Please execute the report repeatedly at intervals in the case of long runtimes. Parameter P_UPDATE determines whether the changes are to be made in the database.


report tkmist89.

tables: ekpo, eina, ekko, lfa1, eine.
select-options: p_infnr for eine-infnr.
parameters: p_update.

select * from eine where ebeln ne space
and infnr in p_infnr.
select single * from ekpo where ebeln eq eine-ebeln
and ebelp eq eine-ebelp.
check sy-subrc eq 0.
select single * from ekko where ebeln eq ekpo-ebeln.
check sy-subrc eq 0.
select single * from eina where infnr eq eine-infnr.
check sy-subrc eq 0.
if ekko-lifnr ne eina-lifnr.
write: / 'Best. anderer Lieferant', ekko-lifnr, eina-lifnr,
eina-infnr, ekko-ebeln, ekpo-ebelp.
endif.
if ekpo-matnr ne eina-matnr.
write: / 'Best. anderes Material ', ekpo-matnr, eina-matnr,
eina-infnr, ekko-ebeln, ekpo-ebelp.
endif.
if p_update ne space.
if ekpo-matnr ne eina-matnr or
ekko-lifnr ne eina-lifnr.
* Verbindung aufheben, da nicht richtig
update eine
set
ebeln = space
ebelp = space
datlb = 0
where
infnr = eine-infnr
and ekorg = eine-ekorg
and esokz = eine-esokz
and werks = eine-werks.
endif.
endif.
endselect.

Additional key words

Info record.

SAP Note 26313 - No reporting tree for current application (PS)

Symptom:

The message "No reporting trees were created for the current application" (message KN124) appears when report selection is accessed in the Project System (transaction CJR1).

Cause and prerequisites

Transport error.

Solution
Please register reporting tree PS01 for the application PS: R/3 Customizing Implementation Guide -> Project System -> Information system -> General functions -> Create/Change report selection (transaction OPIR)
Enter report tree PS01 (can be selected via 'Possible entries') and save your entry.
The tree PS01 is now registered as the standard tree for the PS application.

SAP Note 26312 - SAPDBA: data file "" could not be created.

Symptom:

The following problem occurs during the restore/recovery with SAPDBA:
After the successful restore of all data files of the database, SAPDBA possibly tries to create further data files with "ALTER DATABASE CREATE DATAFILE ..." and reports:
SAPDBA: The specified datafile does not exist
or the size is not specified.
SAPDBA: The restore of datafiles failed, the database was changed.
SAPDBA: data file "" could not be created.

Cause and prerequisites

SAPDBA selects the files belonging to the database from v$datafile.
As a result, SAPDBA reads an empty file name in a double line due to the ORACLE bug described in note 21762 and tries to generate the file "" instead of ignoring it.

Solution
The ORACLE bug should be corrected as of Version ORACLE 7.3.
SAPDBA will ignore empty file names as of 3.0B or 2.2G (2.1M).

If the error occurs, as described, after the restore, you cannot continue with sapdba. Check the log to determine that no other errors occurred during the restore. This is most likely.
Then you have to recover manually:
sqldba lmode=y
SQLDBA > connect internal
SQLDBA > recover database [until ...]; (see notes 4161, 4164)
SSQLDBA > alter database open [resetlogs];
SQLDBA > exit


To avoid the same error during the next restore/recovery, it would be possible to delete the unnecessary entry from the control file. However, this can only be done by recreating the control file:

complete OFFLINE backup of the database! sqldba lmode=y
SQLDBA > connect internal
SQLDBA > alter database backup controlfile to trace;
You can now edit the file $ORACLE_HOME/saptrace/usertrace/ora_.trc (delete the comments) and use it to recreate the control file: SQLDBA > !cd saptrace/usertrace
SQLDBA > ora_.trc
SQLDBA > exit

SAP Note 26311 - Scheduling agreement and bill of material - quantit

Symptom:

Symptom

VA32
SAPMV45A
Sub-items in a sales document, which contribute to the availability check / transfer of requirements. The main item does not contribute to these. If the quantity is then set at zero in the main item, then the corresponding schedule line in the sub-item is deleted. If the quantity is entered again in the main item, no schedule line is created in the sub-item.

Cause and prerequisites

The system cannot tell, whether the schedule line in the main item was deleted seperately or due to a change in the main item.

Solution
The following correction prevents the schedule line quantities being changed to zero in the main item. The corresponding schedule lines must then be deleted instead.

Additional key words

Bill of material

SAP Note 26310 - Releasing invoices: Details in totals display

Symptom:

If the user selects totals mode in the list of blocked invoices and double-clicks a line, the system branches:

• to a list of items per invoice document when Totals Invoice is
  selected

• to a list of invoice items for a vendor when Totals Vendor is selected

The system does not, however, calculate the line in which the cursor is positioned accurately and shows detailed information on another line.

Cause and prerequisites

Program error

Solution
Corrected in release 3.0B

Additional key words

MR02

SAP Note 26309 - RGCEDR20: Identical file names

Symptom:

The PC download of financial reporting data from R/3 Financial Accounting for the R/2 consolidation by means of program RGCEDR20 creates identical file names ("POS_0000"). Each file contains data of a company. As a result, data was only downloaded for one company.

Cause and prerequisites

Integral values were used as company ID. Six characters are available which were not completely used.
Example: Company '1' is stored internally as '000001'.
Company '99' is stored internally as '000099'.

The file name is made up of the fixed text fragment "POS_" and the first four figures of the company ID. As a consequence in this above example, file name
"POS_0000" is used for every company.

Solution
Not the first four figures of the company ID are to be used but the last four.

SAP Note 26306 - Syntax error SAPLSUM5 RV_DELIVERY_ADD

Symptom:

When creating an order (VA01) or a delivery (VL01), the system issues
error message SY047: 'Syntax error in program SAPLSUMn.

Cause and prerequisites

Example: Matchcode MBAN
The error occurs in function module MC_UPDATE_MBAN, which is generated by report SAPMACOP. This function module has a syntax error, which causes an ENDFORM statement to be inserted in the wrong place.

Note: This error also occurs with other matchcodes! A syntax check
in the main program, e.g. SAPLSUM5 (using SE38) determines
the incorrect line number in the program. It is then possible
to determine the matchcode affected.

Solution
Move the ENDFORM statement to the correct position and regenerate
the program.

Additional key words

SAPLSUM5 SAPLSUM7 SY047 LV05IU01 LV05IU07 RV_SALES_DOCUMENT_ADD
RV_DELIVERY_ADD

SAP Note 26305 - Cancel when display. master inspect. feat./method

Symptom:

You are in transaction QS24 (display master inspection characteristic version) or QS25 (delete master inspection characteristic version) on the 'Master data' screen. If you choose function F12 (cancellation) here, a pop-up window appears asking you whether you want to exit the screen without saving.
The same occurs with transaction QS34 (display inspection method version) or QS35 (delete inspection method version).

Cause and prerequisites

Program error

Solution
Program changes

SAP Note 26304 - MB90: No collective slip after upgrade from 2.2C

Symptom:

After the release upgrade from 2.2C to a later release, it is no longer possible to edit the collective slips created in 2.2C with MB90 (Material document -> Edit output).

Cause and prerequisites

Up to and including Release 2.2C, the collective slips were created with line item number 0000.
As of Release 2.2D, they are created with line item number 0001. For this reason, the "Collective slips" indicator is no longer necessary. It was made suppressed on the initial screen of transaction MB90.

Solution
Display the "Collective slips" indicator again on the initial screen of MB90 to edit the "old" collective slips. To do this, see correction in program RM07MNDR.
If you have edited all collective slips with line item 0000, you can suppress the indicator again, since all new collective slips are listed together with the individual slips.

Additional key words

Output determination, WE03, WA03, goods receipt/issue slip

SAP Note 26302 - Product costing termination with CO 901

Symptom:

Product costing of a dependency terminates with message CO 901.

This applies to the following releases: Release 3.00 (FCS), 3.0A.

Cause and prerequisites

Missing refresh of local structure.

Solution
Insert one line into the source code of program (INCLUDE)
- LCOSDF40.

Additional key words

CK11, process order, material quantity calculation

SAP Note 26301 - General info. on depreciation method conversion

Symptom:

It is not clear when a conversion of the depreciation method is carried out.

Solution

Generally, it only decided with the annual balance carried forward whether the valuation is carried out according to the original method (calculation key) or according to the conversion method (conversion key in the calculation key).
Exceptions are:

• Conversion method '1 = conversion if the depreciation of the conversion key is greater than the one of the calculation key' .

Here the system also checks for the original acquisition, in addition to the annual balance carried forward, whether to switch to the conversion method.

• Conversion method '5 = Conversion upon end of planned life'

If the end of planned life is not a fiscal year-end, the decision as to which method applies is made individually for each transaction ( annual balance carried forward or transaction ) by means of the asset value date. The calculation for one transaction, however, is not carried out according to two methods ( period preceding the end of planned life and period following the end of planned life ). For the decision as to which method applies, it is only relevant whether the asset value date of the transaction precedes or follows the planned life. This means that a conversion following the end of the planned life for an annual balance carried forward is only carried out upon completion of the fiscal year, which is at the end of the useful life. For a transaction, it is decided individually whether its asset value date precedes or follows the end of the useful life.

Note
The conversion to another percentage rate or base value in the levels of a calculation key is not to be seen as a conversion method in this context. This conversion to another level is carried out period-specifically for each transaction.

Example of conversion following the end of planned life

• Depreciation start date: 07/01/1995

• Useful life: 5 Years

• End of useful life: 06/30/2000

• Acquisition and production costs: 100

• Depreciation method: linear, percentage rate according to useful life, base value 100% of the acquisition and production costs

• Conversion after the end of useful life: linear, percentage rate according to useful life, base value 50% of the acquisition and production costs

The result is the following depreciation development

• 1995: 10 (100/60*6)

• 1996: 20 (100/60*12)

• 1997: 20 (100/60*12)

• 1998: 20 (100/60*12)

• 1999: 20 (100/60*12)

• 2000: 18 (100/66*12) or alternatively 2000: 10 (100/60*6)

• 2001: 10 (50 /60*12)

Thus, a conversion is not carried out in the year 2000, however, the useful life is internally increased by the 6 months and the calculation is continued with the old method since it was determined, that the depreciation is to be carried out also after the end of the useful life and also 'below zero'. If you want the alternative display, you must change the calculation key so that a calculation is only carried out up to the end of the useful life and not 'below zero'.
A transaction with asset value date up to 06/30/2000 is calculated with theold method; a transaction with asset value date as of 07/01/2000 is calculated with the conversion method.

Additional key words

Conversion, T090-UMAFSL, T090-UMRPRZ, T090-UMSTM

SAP Note 26299 - SAPLCRK1: COMPUTE_INT_PLUS_OVERFLOW

Symptom:

Abnormal termination with error COMPUTE_INT_PLUS_OVERFLOW.

Cause and prerequisites

Scheduling via operating time. The end during the permanent calculation between two dates is exactly on the shift finish. The shift was copied from the standard available capacity. No scheduling was made to the breaks.

Solution
Source code corrections

SAP Note 26294 - SD-30*: SAPMV13A - ASSIGN_OFFSET_NOTINFIELD

Symptom:

Symptom

When you call program SAPMV13A using transaction VK13, a runtime error occurs: "ASSIGN_OFFSET_NOTINFIELD".

Cause and prerequisites

Program error

Solution
Repair the coding as follows:

SAP Note 26291 - RAINZU01 includes unplanned depreciation

Symptom:

During the determination of investment support, the program also includes unplanned depreciation on current acquisitions into the calculation.
This is also true for manual amortization.

Cause and prerequisites

Program error.

Solution
Advance correction in module RAINZUSR, syntax check only in main program RAINZU01

SAP Note 26284 - Branch into text screen, date = system date

Symptom:

Create sales activity / MAILING, enter a date different from the current date. When you branch into the text screen, the date is equal to the current date.

Cause and prerequisites

Program error.

Solution
Corrected in 2.2G, 3.0B.

SAP Note 26277 - Change risk class: Sales order -> delivery

Symptom:

When a delivery from an order is entered, the risk class of the credit account should not be taken from the order but should be recalculated from the credit account.

Cause and prerequisites

In the data transfer routines order to delivery, the risk class is taken from the order.

Solution
Transaction VOFM, data transfer for delivery: You must set up a new data transfer routine which copies the risk category from the master data of the credit management account (Table KNKK) into the delivery header (for the access to the master data of the credit management account use the fields CVBAK-KNKLI and CVBAK-KKBER).
Afterwards, store this routine in copying control for sales document to delivery note at the header level (Transaction VTLA).

Additional key words

VL01, credit limit

SAP Note 26271 - Invoice reference for alternative payee

Symptom:

If an item is entered with invoice reference and the invoice contains one-time data (one-time account or alternative payee in the document), the terms of payment are actually copied from the invoice, but not the one-time data.
In Release 2.2, the system also fails to copy the payment method supplement (BSEG-UZAWE) from the invoice.

Cause and prerequisites

Transfer of the one-time data was not programmed.

Solution
Corrected in 2.2G and 3.0B

Additional key words

OTA payment method supplement

SAP Note 26270 - Cancel function when displaying material specific.

Symptom:

You are in transaction QS62 (Display Material Specification) on the screen 'Feature Allocations'. If you choose F12 (Cancel) on this screen, error message V0105 is displayed: 'Flow control: All windows are closed'

Cause and prerequisites

Program error

Solution
Program change

SAP Note 26269 - F-19 credit amounts displayed without +/- signs

Symptom:

The credit amounts are displayed without a minus sign in the overview display when cancelling statistical postings.

Cause and prerequisites

Program error

Solution
Corrected in Release 3.0B

Additional key words

Cancelling statistical posting / F-19 / FB22

SAP Note 26265 - Foreign currency posting: Error message GI812

Symptom:

Transaction FBB1, FB01, MR01
Error message GI812

The problem particularly occurs with foreign currency valuations.

Cause and prerequisites

Program error

Solution
Correction of the following program code:

SAP Note 26263 - Hierarchy graphic: Missing network number in key

Symptom:

The network number for the activities is missing in the key in the hierarchy graphic of time scheduling.

Cause and prerequisites

Program error

Solution
Change the source code.

Additional key words

Hierarchy, graphic

SAP Note 26262 - Termination when copying with reference in VA01

Symptom:

Key word: copy
The screen for specifying a reference document is skipped over, even though 'Reference is mandatory' was set for the sales and distribution document in Customizing. This problem occurs if you specify a reference document, branch to the item selection screen and press "Cancel" there. In this case, you go to the request screen.
If you now press ENTER, the dialog box is skipped.
Afterward, when an order is manually created, fields from a document created earlier may be copied to the order.

Cause and prerequisites
Solution
As of 2.2C, you can carry out the following repair:

Additional key words

tvak-bezpb Reference

SAP Note 26256 - Deleting Production Orders, Error with CUA-Status

Symptom:

Whe changing a order with deletion flag and answering 'No' on the
following popup an error occurs: missing CUA-Status

Cause and prerequisites

program error

Solution
program correction in lcokofo1 as given in P22K009254

Additional key words

Deletion flag

SAP Note 26251 - OKKP: Version 000 created with exch. rate type 'P'

Symptom:

Version '000' is always created with exchange rate type 'P' when creating a controlling area with transaction OKKP.

Cause and prerequisites

Cause: Program error (corrected in 3.0B)
Preconditions: The exchange rate types 'B', 'G' and 'M' delivered with the standard system (table TCURV) are used.

Solution
Please correct the indicated lines in program SAPMKC00.

Additional key words

OKKP, exchange rate type, TCURV

SAP Note 26248 - Posting parked documents and canceling not possible

Symptom:

When canceling an invoice, message 00347 'Field && is not an input field" sometimes appears. Sometimes no message appears at all. But in both cases the document is not canceled.
When parking an invoice, message M8 252 "Parked document & cannot be
posted (see Extras -> Messages)". When you choose Extras -> Messages,
no messages are displayed.
The parked document is not posted.
The invoice refers to a purchase order with account assignment or contains direct postings to G/L accounts. The relevant G/L account has the tax category , and not '- ', '* ' or similar.

Cause and prerequisites

Program error

Solution
Corrected in release 2.2I and 3.0B. Prior correction as follows.

Additional key words

MR08

SAP Note 26247 - Error in line item sorting

Symptom:

Item sorting for vendors does not work.

Cause and prerequisites

Program error

Solution
Corrected in the standard system as of Release 3.0B

Additional key words

RFKORD10, RFKORD11

SAP Note 26243 - Conditions missing in the sales document

Symptom:

Sales documents exist, for which the conditions are missing in the pricing screen, although the net values are correct at header and item level.

Cause and prerequisites

The cause is not known

Solution
The following correction causes the system to terminate and issue a message when you save a document of this kind. This makes it possible to discover which particular situation led to the error. When a user comes across the message, all problems and messages that occurred in the document up to that point are taken into account.

Additional key words

Pricing

SAP Note 26242 - PPT024F: XPRA Planner group/production scheduler

Symptom:

Customizing tables Planner group (routing) and production schedulers were one table in 2.2. In 3.0, they are split up in two tables. During the upgrade to 3.0, only the planner group was filled although report PPT024F ran.

Cause and prerequisites
Solution
Correct report PPT024F and then start it.

SAP Note 26253 - Network number cut off in printout

Symptom:

The network number in the frame description is cut off in the network printout.

Cause and prerequisites

The field length is not long enough.

Solution
Transaction 'CNG8', FORM 'PSNC01', field 'a':
Change the 'Min.fld width' to '8000'.

Additional key words

Print, PostScript

SAP Note 26235 - Missing CUA-Status when display order deletion flag

Symptom:

Msiing CUA-Status when displaying deleted order.

Cause and prerequisites

programm error

Solution
correction in include lcokofo1 as given in correction P22K009254

Additional key words

CUA-status, production order

SAP Note 26233 - Printout of calculation of interest on arrears

Symptom:

Error when printing out forms (incorrect layout, ...) for the calculation of interest on arrears.

Cause and prerequisites

You want to print out the list displayed on the screen. This list, however, is formatted for the screen.

Solution
Set the parameter 'Print form on printer' in the report. Then the form is formatted for printing.

SAP Note 26231 - Discounts on characteristic level (VA00, VA01)

Symptom:

In object dependencies, a price and a discount are set up as actions on characteristic level. The price was given condition type VA00. The discount was given condition type VA01. When a sales order is created and this characteristic is chosen, the price VA00 and discount VA01 are taken.

However, discount VA01 affects not just the VA00 condition for the same characteristic, but also the entire price which was accumulated up to the corresponding level of the pricing procedure.

Cause and prerequisites

..

Solution
In Release 2.2:
---------------
Define different condition types for each characteristic and add further levels to the pricing procedure.
Example: 50 VA00 ( Variant condition for characteristic A )
51 VA01 (Discount for characteristic A, i.e. ref.step 50)
60 VB00 (Variant condition for characteristic B)
61 VB01 (Discount for characteristic B, i.e. ref.step 60)

As of Release 3.0:
------------------
Explode BOM for the configurable material in the sales order. If a component results for every characteristic/characteristic value, and this component is an independent item in the sales order, then material price PR00 can also be used for the component instead of pricing it via VA00. A 'normal' material discount (instead of discount VA01) can then also be used for this item.

Additional key words

KMAT, configuration, variant pricing, pricing

SAP Note 26228 - Display material debiting

Symptom:

If you post a material debiting for a material with moving average price and zero stock or for a material with standard price, no inventory posting is made. As a result, no material document is created. You can only display the accounting document from Financial Accounting.
If you tried to display the document from Materials Management, you received an incorrect error message.

Cause and prerequisites

Program error.

Solution
Corrected in 3.0B
You now get a special message.

Additional key words

MR03

SAP Note 26227 - Intercompany billing in logical database VFV

Symptom:

In the logical database VFV, intercompany billing is not selected.

Cause and prerequisites

Document categories 5 and 6 are not taken into account.

Solution
1. see repair
2. Maintain selection texts of program SAPDBVFV

VBTYP_5 Intercompany billing
VBTYP_6 Intercompany billing (credit memo)

Additional key words

IV, IG, billing document

SAP Note 26226 - Copy model plan: GL209 during job generation

Symptom:

If the function 'Copy model plan' is scheduled in the background, error message GL209 'System error when generating job' is displayed.

Cause and prerequisites

Program error

Solution
Please make the following correction in FORM routine APPEND_SELFIELDS (approx. line 4860) in program MGPLCF10:

Additional key words

GP52, GP62, copy model plan

SAP Note 26223 - Global replacement of master inspection charact.

Symptom:

If you globally replace a master inspection characteristic in task lists, you receive the following message in the replacement log: PLMKB-SPCKRIT allows no entry.
This message can be displayed if you start the global replacement with transaction QS27 or from the master inspection characteristic maintenance when saving.

Cause and prerequisites

The error occurs if the new master inspection characteristic is not an SPC characteristic.
Program error

Solution
Program correction

Additional key words

SPC characteristic

SAP Note 26222 - RFWERE00 - Posting foreign currency is not possible

Symptom:

RFWERE00 posts with correct allocation number (purchase order number and item) at the key date. The clearing is to be with FB05 at the reversal date. The session cannot be processed because an incorrect document is selected.

Cause and prerequisites

Program error. This error only occurs if the "Posting in foreign currency" parameter is selected.

Solution
Start RFWERE00 without "Posting in foreign currency" or make the following correction.
Read the program documentation again: You generally do not require the "Posting in foreign currency" transaction.

SAP Note 26221 - Move time when dispatching on planning table

Symptom:

The move time for a preceding operation or successor operation is not considered when dispatching an operation on the planning table.

Cause and prerequisites
Solution
Source code corrections

SAP Note 26220 - Long run-times for delivery and sales doc with ref.

Symptom:

When deliveries are processed in connection with batch split, very long run-times may occur in the update in exceptional cases. The program reaches an endless loop.
The error can also occur when preparing a delivery for an order that has preceding documents; batches are not necessary for this.

In addition, this problem can occur if the preceding document cannot be found at all or not with the proper document type when recording a document flow (not only for VL01 and not only in shipping).

This problem may also occur when creating a sales document that refers to another document.

Cause and prerequisites

Program error

Solution
Make the following correction in program LV45VFDB:

Additional key words

VL02, batch, batch split, VBFA, SAPLV45V, LOOP, VL01, VF04, VF01, lv45vffa

SAP Note 26219 - ME61 Missing Customizing link in ML061

Symptom:

If you choose 'Proceed' if error message ML061 is displayed, nothing happens in the 2.2 system and a termination occurs in the 3.0 system.

Cause and prerequisites

Incorrect transaction link

Solution
Replace transaction code OLME by OMGL in the long text of error message 061 in message class ML.

Additional key words

ME61, 061(ML), CALL_TRANSACTION_IS_MENU

SAP Note 26216 - Completion Confirmation message RU415

Symptom:

If you try to create a completion confirmation the message RU 415 appears: Number range for object PD_SEQ_NR does not exist.

Cause and prerequisites

The object PD_SEQ_NR does exist but no number range is defined.

Solution
Create number range like described:

The only thing you have to do is to create an internal number range for object PD_SEQ_NR. How you maintain it:
Choose:
Tools --> CASE --> Development --> Other tools --> Number ranges
Enter Object PD_SEQ_NR and press push button 'Number ranges'.
Press push button 'Change intervals'. Then create a number range '01' from number 000000000001 to number 999999999999. The number range is internal, so don't set 'Ext' to 'X'.

Additional key words

CO1, CN25, IW41

SAP Note 26213 - Credit limit: released orders are checked

Symptom:

If sales orders which were released from a credit point of view are changed, a further credit check is carried out even though the change does not affect the credit value in the slightest.

Cause and prerequisites

Program error: always, if the sales order was created with reference to a customer quotation.

Solution
Corrected in 3.0B using P30K012985 and in 2.2G using P22K008675.
\
Additional key words

VA02, VKM1

SAP Note 26212 - SD-30* : OVV9 - Incorrect view maintenance

Symptom:

In transaction OVV9, which is used to assign sales areas to a plant, not all plants are displayed with the assigned sales areas. In addition, the scroll keys are not active so that no new plant-sales area assignments can be made.

Cause and prerequisites

Generation error

Solution
Transaction OVV9 cannot be used due to a generation error. Use transaction SM31 (table: T001W) to maintain the data.

SAP Note 26209 - Errors 06 150 in product costing

Symptom:

If product costing (CK11) was carried out, the error message 06 150 'Please enter a valid release date', if a non-stock component existed in the bill of material.

Cause and prerequisites

Non-stock component in the bill of material

Solution
Corrected in the ABAP include LCOBCU04.

SAP Note 26208 - Incorrect stat.values for foreign currency docs.

Symptom:

1) The statistics values of billing are updated incorrectly for foreign currency billings.
2) The exchange rate transferred to FI is incorrect

Cause and prerequisites

1) The company code in the billing document is determined from the sales organization in the standard system. If a different company code is now set via the data transport into the billing document ( VOFM ) and the two company codes have different local currencies, then this error occurs.
2) As of 2.2F (note 22771), the company code for the intercompany billing document is no longer determined from the sales organization but from the plant for intercompany billing. If both of these company codes have different local currencies, then this error occurs.

Solution
Corrected in 3.0A

Additional key words

Local currency VF01 VF04

SAP Note 26202 - Matchcode objects in the LIS

Symptom:

************* Modification information ********************

The following is not a program error. In the case of a characteristic of an info structure with a specific data element XXXXX you want to use a matchcode object YYYY that differs from the automatically generated object for standard analysis, planning screens or in condition maintenance.

Solution

1. If you only want to adopt the matcode objects to standard analyses, use modifications *1A* or *1B*.

You have to distinguish betweeen ordinary characteristics and "key figures similar to characteristics". In the case of ordinary characteristics use modification *1A*. If you want to adopt a key figure similar to a characteristic use modification *1B*.

2. If you also want to adopt planning screens and condition maintenance, use modification *2* as well.

Additional key words

Information Structure, Matchcode

SAP Note 26198 - Error message GB081 when access validation

Symptom:

When making postings in external accounting (FI, MM, SD ...), the error message GB081 is output.

Cause and prerequisites

A validation was defined in CO, but no substitution.

Solution
Implement the following correction.

SAP Note 26192 - Tableview control: Doubling fields

Symptom:

Error: If a table control is created with the Screen Painter and filled with fields, the entries for the participating fields in the field list are doubled during every generating step.
Message: Area exists several times

Cause and prerequisites

Error in the Screen Painter, only in FCS systems

Solution
Corrected in 3.0A. The table control is released officially in Release 3.0B. In the FCS System you should not use the TC.

SAP Note 26190 - Addresses: Create control file for WORD

Symptom:

An address list is created in R/3. This should be used as a control file for WORD ... and should therefore be loaded on a PC.

Cause and prerequisites
Solution
Solved by using a separate message and a separate form.

What is to be done ?
1. Separate SAPScript form
The form contains all the variables that are to be output in the
WORD control file.
2. Create a separate message
... via Customizing. Allocate the new form to this message.
3. Execute the new message
... in the same way as the standard message MAAK.
4. Download
You can now load the spool file created in 3. as follows onto a
PC:
a) Display the spool request
b) Menu SYSTEM --> LIST --> DOWNLOAD

SAP Note 26189 - Creating total for each main asset number

Symptom:

Customer wants to use summarization to main numbers in reporting but the main number is a non-capitalized fixed asset and is therefore rejected in some reports (RAGITT01 RABEST01, and so on ) for these variants.
A deactivated fixed asset acts in the same way as a non-capitalized asset.
Report RAVERS01 does not support function 'Totals per main no.'.

Cause and prerequisites

Since the main number is not capitalized, it is not listed.Since the main asset master record is used as 'basis' for the summarization to main numbers, the subnumbers are also not listed.

Solution

1. From the viewpoint of SAP, there is no simple solution.The error is corrected with the conversion to a new reporting method. This occurs with Release 4.6 with the ALV reports, it cannot be implemented in advance.

2. A good workaround is a separate sort version, where the lowest sort level is the asset number (field name 'ANLN1') and the report is called with the function 'Create group totals only'.

Additional key words

SAPDBADA, RABEST01, RAGITT01, DEAKT, XUNTNR

SAP Note 26187 - 3.0E: Changing the configuration of material variants

Symptom:

1.

The configuration cannot be changed for a material variant item whose requirements type allows configuration, for example ELVV, derived from planning group 0065 or requirements class 061. The system issues error message V1360 'Configuration not possible' or the 'Configuration' function key does not work.

2.

The system issues error message V1360 'Configuration not possible --> reason 7' for a material variant item whose requirements type requires configuration (in the requirements class, the field CONFIGURATION is set to '+').

3.

The system issues error message V1360 'Configuration not possible --> Reason 1' for a material variant item whose requirements class requires configuration (in the requirements class, the field CONFIGURATION is set to '+').

Cause and prerequisites
Solution

1.

The CONFIGURATION field in the requirements class (table T459K) should be set to '*' or '+'.

2.

Corrected in 3.0E

3.

Corrected in 3.0E

Additional key words

Material variant, kept in stock, VA01, VA02, KMAT, configurate, V1360

SAP Note 26185 - PPPR: Sorting components in withdrawal papers

Symptom:

The output sequence of the withdrawal slips or component sorting in the material provision list does not meet the company-internal requirements.

Cause and prerequisites
Solution
The sort sequence can easily be adapted: Copy the layout set and the respective report to make the changes in your own customer-specific copies. Since the standard reports and layout sets change sometimes, it is not always guaranteed that you can print your changed layout set with the standard report after the next upgrade.

Additional key words

PPPRMBRL / PPPR_PICK-LIST, PPPRWARS / PPPR_GOOD-ISS-SL

SAP Note 26182 - PPPR: Assigning print reports and layout sets

Symptom:

The printing of shop floor papers is terminated.

Cause and prerequisites

• Incorrect assignment of layout sets and print reports. The correct assignment is described below according to release.

• Another reason may be an outdated layout set translation. In this case, you should be able to print with logon language German. There generally is a special solution note here.

• When you print your own client-specific layout sets using a standard report, the error may occur after an update because the standard report and standard layout set were changed. In this case, you would have to copy the print report in addition to the customer layout set into the customer name range in order to make the modification independent of the changes in the standard system.

Solution
The following layout sets and print reports are currently delivered:
List Report Layout set
Object list PPPROBJU PPPR_OBJECT-LIST
Operation control ticket PPPRSTEU PPPR_JOB-CTRTICK
Job ticket PPPRLAUF PPPR_JOB-TICKET
Acquisition list PPPRZUGL PPPR_ZUGL-LIST (as of 3.0)
Time ticket PPPRLOHN PPPR_TIME-TICKET
Completion confirmation slip PPPRRUEC PPPR_CONF-TICKET
Pick list PPPRMBRL PPPR_PICK-LIST
Withdrawal slip PPPRWARS PPPR_GOOD-ISS-SL
PRT overview PPPRFHML PPPR_PRT-LIST
Split ticket PPPRSPLT PPPR_SPLIT_TICK (as of 3.0)
In 3.0, another layout set record will be delivered that can be printed with the same reports:
List Report Layout set
Object list PPPROBJU PSFC_OBJECT-LIST
Operation control ticket PPPRSTEU PSFC_JOB-CTRTICK
Job ticket PPPRLAUF PSFC_JOB-TICKET
Acquisition list PPPRZUGL PSFC_ZUGL-LIST
Time ticket PPPRLOHN PSFC_TIME-TICKET
Completion confirmation slip PPPRRUEC PSFC_CONF-TICKET
Pick list PPPRMBRL PSFC_PICK-LIST
Withdrawal slip PPPRWARS PSFC_GOOD-ISS-SL
PRT overview PPPRFHML PSFC_PRT-LIST
Split ticket PPPRSPLT PSFC_SPLIT_TICK
The forms in production order printing no longer need to be copied into the individual clients starting with releases 2.1M, 2.2G, and 3.00. It is recommended, in case the forms are not designed depending on the client, to delete the copies of the production order formulas so that only the versions in client 000 are still used.

Additional key words

Error TD427