12.3.11

SAP Note 24553 - ME23 Item statistics changes: Missing data

Symptom:

Changing the "delivery completed" indicator or the final invoice indicator is not documented within the change statistics for the order item in question.

Cause and prerequisites

The change was not carried out directly in transaction ME22 'Change Purchase Order', but, for example, when posting the goods receipt or when entering the invoice.

Solution
None, because the functionality is not implemented.

Additional key words

ME21, ME22, ME23, EKPO-ELIKZ, EKPO-EREKZ

SAP Note 24552 - BRRESTORE/SAPDBA: not enough space in file system

Symptom:

When trying to restore a backup, BRRESTORE reports that there is not enough space in certain file systems.
BR360E/BR360W Not enough disk space in ... for restore/verification, missing ... MB.
The same can occur in SAPDBA in the functions:
"Reorganize tablespace and data files" and
"Move/rename data files of a tablespace"

Cause and prerequisites

To create a file, UNIX does not only need the exact space in the size of the file but also another relatively small amount of space for the file system administration.
This additional space cannot be determined exactly before the file is created. However, you definitely have to take it into account when you check the available space because otherwise errors can occur when storing due to a lack of space.

BRRESTORE and SAPDBA therefore assume that in addition to the total size of the files that are to be saved (fsize), a reserve space (res) needs to be available for the file system administration.

In some cases this could be a little more than the actual space required. For this reason, it is possible that in a very tightly calculated file system this space is not available, although the files were or still are included in the system before restore (during backup) or during reorganization (check of space).
Thus, BRRESTORE and SAPDBA only provide a warning if the assumed reserve space does not exist. As a general rule you should not set up your file systems too closely to the exact size of the individual data files.
If an error occurs, the Restore or reorganization is terminated.

Depending on the release, the following values are rlevant for the space check:
-------------------------------------------------------------------

new insp. method (in 3.1I as of BRRESTORE Patch 12 or SAPDBA-Patch 22,
in 4.0B as of BRRESTORE Patch 24 or SAPDBA-Patch 69,
in 4.5A as of BRRESTORE Patch 20 or SAPDBA-Patch 42,
in 4.5B as of BRRESTORE Patch 1 or SAPDBA-Patch 1
and in general as of SAPDBA/BRRESTORE 4.6A):

Freespache: free
Reserve: res = free/1024

Ideal situation: fsize <= free - res
Warning: free - res < fsize <= free
Error (Termination): free < fsize

old insp. method (til SAPDBA/BRRESTORE 4.5B except in the a.m. patches):

Freespace: free
Reserve (til 4.0A): res = fsize/1024 + 1MB
(as of 4.0B): res = fsize/1024

Ideal situation: fsize + res <= free
Warning: free < fsize + res <= free + 10MB.
Error: free + 10MB < fsize + res

Caution with Unix installations:
--------------------------------
If disks for database files are re-formatted (file systems are created again), then the space reserved for Superuser Root and the number of Inodes should be kept at a minimum. For this refer to the SAP Installation Guide:
"R3 Intallation on Unix: OS Dependencies"

Solution
Set up greater file systems.

SAP Note 24546 - Manually processing the account statement in the UK

Symptom:

As of Release 3.0, it is possible in Great Britain to store bank transactions with different execution days in a telepay file. The creation of payment advice notes using DME management, which is common in other countries, can generally not be used in Great Britain because the bank gives a confirmation for each execution day but not for the entire file.

Cause and prerequisites

The creation of payment advice notes in DME management creates a payment advice note for each data carrier. However, for different execution days this only applies to some data records.

Solution
When creating the telepay file, payments are already grouped together to one day and identified by a unique reference number. The new report RFFODTA1 creates a payment advice note for such a reference number.
Procedure:
A created TELEPAY file can contain payment orders for several execution days. For each execution day, at least one CONTRA record is created in this case which is uniquely identified by identifier "SAPBACS" + 10-character reference number.
Example: Payment to vendor Adams : DM 1000,00 12/15/199x
Payment to vendor Blithe: DM 2000,00 12/15/199x

Payment to vendor Miller: DM 1100,00 12/17/199x
Payment to vendor Norman: DM 2200,00 12/17/199x

Payment to vendor Adams : DM 1110,00 12/19/199x
Payment to vendor Miller: DM 2220,00 12/19/199x

CONTRA 12/15/199x DM 3000,00 SAPBACS0000123410
CONTRA 12/17/199x DM 3300,00 SAPBACS0000123511
CONTRA 12/19/199x DM 3330,00 SAPBACS0000123612

After the bank has made the payments for one day, the reference number in question is passed on to the client. To simplify the clearing, you can now create a payment advice note with the affected items in each case using report RFFODTA1.
Example:
Payment advice note 070000123511 is created for reference number "0000123511" which contains the two items of December 17th. When posting the outgoing payment of DM 3300.00, the affected items are selected by specifying the payment advice note number.

Additional key words

Bank reconciliation, RFFOGB_T, RFFODTA1, TELEPAY

SAP Note 24543 - AS91: Replacement value is not calculated

Symptom:

The replacement value is not calculated when transferring data.

Cause and prerequisites

The problem occurs if the switch "Calculate accumulated depreciation" is not set in T093U-XNEUAF and if the switch "Calculate replacement value" T093U-XNEUWB is set in the area which is to carry out the revaluation.

Solution
Please make the following correction.

Additional key words

AS01, AS92, AS93, old assets data takeover

SAP Note 24538 - MMIM: Search for reservation via requirements date

Symptom:

If you want to make a clearing posting with reference to a reservation and do not know the reservation, you can search for it by means of search criteria. One criterion is the 'Requirements date' field. If you enter a date here, the system searches for the reservations which correspond to this date. However, the documentation says that all reservations with a requirements date with a date less than or equal to are found.

Cause and prerequisites

Variance program logic and documentation.

Solution
If you want to achieve that the program logic corresponds to the documentation, that is, all reservations with requirements date <= entered date are to be selected, you have to change the programs. This functionality is not available in the standard system in Releases 2.1 and 2.2.
There will be an enhancement in Release 3.0A which allows you to enter a condition like '<', '<=', '=', and so on, for the selection criterion 'Requirements date'.

SAP Note 24526 - Purch. order: Currency change in header: no price conversion

Symptom:

If items have already been specified in the purchasing document, the price per purchase order price unit is not changed if the currency and/or the exchange rate is changed in the document header (this also applies to the creation of POs with reference to a requisition).
Example: Item 10 DM per 1 pc.
Currency changed from DEM to USD with exchange rate 2
Expected value in item: 5 USD per 1 pc.
Displayed value in item: 10 USD per 1 pc.

Cause and prerequisites

Design decision: Were the purchase order price to be translated, in the event that the currency were entered wrongly, precisely this system behavior would be undesired.

Solution
Initiate price conversion explicitly: Select item and then:
"Item -> Conditions -> New price determination". After entry of the value (which has been manually converted into the equivalent value in the relevant currency), the price determination process is carried out.

A further possibility is to create info records (material/ vendor) in the required currency. However, this only helps in the creation of a PO - not with regard to changes.

Additional key words

ME21 ME22 Document header, Currency translation, Order price

SAP Note 24522 - BOR object USER: Method USER.Create1 instance-dependent

Symptom:

No user can be created with the method USER.Create1 or with the function module BAPI_USER_CREATE1 via Visual Basic.
The following error message is issued:
"Persistent key for business object instance of type USER not set. Cannot invoke method CREATE1."
Other terms

SWO1

Reason and Prerequisites

In the Business Object Definition for the object 'User', the method USER.Create1 is defined as instance-dependent.

Solution
The definition of the BAPI method USER.Create1 is corrected with the respective Support Package. With this correction, the indicator 'instance-independent' is set for this method.

SAP Note 24515 - AS11: Update termination when creating a subnumber

Symptom:

When creating a subnumber, an update termination occurs with message EAA035: "ANLB not updated: & & & ...".

Cause and prerequisites

Customizing error.
The number of areas in the asset class was subsequently changed. This causes inconsistencies in the area data.

Solution
The subnumber can be created only when the subsequently inserted depreciation area is deactivated in the asset class to which the main number belongs. The newly inserted depreciation might possibly take effect for all assets or for assets from certain classes.
If the new depreciation area is to take effect for newly created assets, special classes need to be established here. Deactivate the new depreciation area in the classes that already exist.

Additional key words

AS11, SAPMA02S, master data

SAP Note 24514 - Capacity evaluation: no production order via custom

Symptom:

If you enter the customer order number as the selection criterion, then planned orders that are allocated to this customer order are displayed, but not the production orders.

Cause and prerequisites

While the customer order number is in the header in the planned order, it is in the order item in the production order. This was not processed until now.

Solution
The program needs to be corrected.

Additional key words

CM01, capacity evaluation, production order, customer order, load, CY144

SAP Note 24506 - Missing totals in flexible analyses

Symptom:

In flexible analyses, totals are not displayed. In standard analyses, values/quantities without unit are displayed although they must be available.

Cause and prerequisites

The missing totals can be traced back to missing units in the information structures. If several entries with differing units are read and displayed from the information structure, then it is not possible to display totals, because it might lead to apples and pears being added together. If no corresponding unit was updated for a value/quantity in the information structure, the system interprets the missing unit as a different unit for the display.
This means that the actual cause for the error in the analysis is the fact that units are missing in the info structure.
The missing units can be traced back to an error in the generated update programs. If the value or quantity to be updated is 'zero', or ifupdating is prevented by a requirement, the unit is not determined. If, however, a record already exists in the information structure to which the new value/quantity is to be cumulated, the unit there that has already been correctly updated is overwritten by the unit that is now missing.
In most cases, this incorrect overwriting of units only occurs if requirements which prevent updating of a value are used in updating definitions.

Solution

Coding was corrected for 2.1M and 2.2G.
Advance correction is possible by making changes to the program (new coding lines are marked '<-- new', coding lines to be deleted are marked '<--del'); lines of coding relevant to release levels 2.1M, 2.2G and 3.0ABC are marked '<--new 2.1M, 2.2G, 3.0ABC').

Caution !!

    1. After you have inserted the advance correction, you need to regenerate the updating definitions of the affected information structures (transaction MC25). If values have already been updated without units, you need to perform a setup of statistical data for the info structures.
2. If you do not wish to delete the lines in the sample coding RMCSMUS1, and instead wish to mark them with asterisks, you need to insert a space between the * and the first character of the line of coding!

Additional key words

Updating, units, totals, analyses, update requirements

SAP Note 24504 - MI21: Printing possible despite missing authorizat.

Symptom:

You could still print a physical inventory document in transaction MI21 (Print Physical Inventory Document) if the print authorization in the corresponding plant was missing.

Cause and prerequisites

Program error

Solution
The error is corrected in 2.2F and 3.0A. You can make the following advance correction:

SAP Note 24500 - Microsoft Office support in Rel.3.0a

Symptom:

Customer is interested in desktop integration in Release 3.0

Cause and prerequisites
Solution
All information before the final release of 3.0A is subject to change! !

Use of Word:
- as before: Print report portfolios in EIS
- New from 3.0: Word as an alternative to SAPscript for form printout.
This is currently used only in some applications (HR, PP, ..), but will be expanded to include further applications in later releases if it proves successful.

Use of Excel:
- as before: Data download via XXL (improved version making use of OLE automation)
- new from 3.0: Data download from Report Writer using the Outline function
- New from 3.0: Data import into Excel Sheets with active links to R/3 tables (open new data for recalculation in Excel). This is currently used only in some applications (FI LC), but will be expanded to include further applications in later releases if it proves successful.

Use of Access / Project
- New from 3.0: Data exchange between PP and Project via Access database

SAP Note 24494 - Icon text on pushbuttons is too short

Symptom:

The text of pushbuttons with icons is truncated.

Cause and prerequisites

The defined length of the field is too short, to include the icon text and the Quickinfo. Therefore, the icon text is truncated at the end of the field.

Solution
Find out the screen name and number. (for the popup with the help of the debugger or menu option System -> Status.) Edit the screen with the Screen Painter (SE51) and change the attributes of the field in question (SE51, Full screen, position cursor on the field in question, F20 Field attributes, Delete contents of the field Quickinfo, F5 = Transfer, generate screen.). A repair correction must be made.

Additional key words

Icons, pushbuttons, screen

SAP Note 24492 - Missing validation: Batch split allowed

Symptom:

In the delivery on the batch split screen, no check is performed to determine if a batch split is allowed.

Cause and prerequisites

This function, in this form, is not supported.
From Release 3.0, no check is performed during the batch determintation regarding how many splits are allowed. The information on this point has been taken from the search strategy.

Solution
none => Function 3.0

SAP Note 24490 - MMXPRA06: procedure with error message in log

Symptom:

When upgrading to Release 3.0, conversion program MMXPRA06 is run automatically. This may result in the system issuing the error message "Maintenance status overflow", stating the client and material master field concerned.

Cause and prerequisites

One of the functions of the conversion program is to extend the maintenance status of some material master fields. (You can check the current maintenance status with Customizing transaction OMSR - Assign fields to field groups.)
If, while making modifications, the customer has defined his own maintenance statuses in addition to those defined in the standard SAP R/3 System, it is possible, however, that not all the new maintenance statuses (compare report documentation for MMXPRA06) will be assigned since a maximum of 15 maintenance statuses can be specified for each field. In this case, the maintenance status for the field concerned is not extended in the client.

Solution
The customer should have a look at the current maintenance statuses of the fields concerned and, if necessary, extend these maintenance statuses himself.
Note: You need make no further response to these errors when upgrading to Release 3.0.

Additional key words

Program: MMXPRA06

SAP Note 24483 - Popups "Printing Notification":coupling method "C"

Symptom:

When printing on a network printer via the access method "C" and a local print queue on an NT server, popups containing "Printing Notification" appear on the screen via the NT Messenger Service for every print job.
In addition one or several events are logged in the system log of the NT Event Viewer for every print job.

When you print on a Novell print server from a NT 4.0 server with GSNW, a Novell print banner is printed after importing NT40 SP5 although this does not correspond to the print and Netware Gateway configuration.

Cause and prerequisites

Missing REGISTRY entry to suppress the message popup or NT spooler configuration which is not adjusted.

Solution

To suppress the Printing notification popups, create registry entries with tool REGEDT32.EXE or change the configuration at the NT spooler of the NT server:

  • Deactivate the message popups

Change/Create the following entry in the registry:
HKLM\SYSTEM\CurrentControlSet\Control\Print\Providers


  • Menu call: Edit -> Add Value...

Name: NetPopup

Type: REG_DWORD

Data: 0


Then restart the NT spooler service in order to activate the new REGISTRY entry.


If the gateway service is installed for netware, you can also send popups via this path. The following entry should still be entered in the registry though (EDIT -> Add Value):

HKLM\System\CurrentControlSet\Services\NWCWorkstation\Parameters
CurrentControlSet/Services/NWCWorkstation/ Parameters

  • Menu call: Edit -> Add Value...

Name: DisablePopups

Type: REG_DWORD

Data: 1


  • Deactivating/Configuring NT Event Viewer entries

Procedure for NT3.51
===========================

Change/Create the following entry in the registry:
HKLM\SYSTEM\CurrentControlSet\Control\Print\Providers

Menu call: Edit -> Add Value...

Name: EventLog
Type: REG_DWORD
Data: 0

Then restart the NT spooler service to activate the registry changes.

Procedure for NT4.0
==========================

Open 'Control Panel -> Printers' and select from the file menu item 'Server Properties'. Then select the option 'Advanced' and activate/deactivate the required event in the displayed selection window.

Then restart the NT spooler service to activate the change.

To deactivate the Novell print banner that appears with NT40 SP5, follow the instructions of the Microsoft Knowledge Base Articles Q232559: "Novell Print Banner Always Printed After Applying Service Pack 5".

Additional key words

Print notification, event viewer, event log, popup, messenger service, print banner, banner

SAP Note 24480 - Rescheduling (composite note)

Symptom:

This note groups together all corrections for rescheduling. The note will be continually updated, so please consider the release information in the respective corrections.
Even if the situation described in the respective note does not seem to apply to your case, please use it anyway; we cannot exclude the possibility of side effects (Example: Note 19522 was first released for all background functions that work in a similar way to rescheduling, but was then extended).
As a means of orientation, the release for which the note was released is contained in brackets at the end. Example: 19522(2.2E) means that this error was corrected in Release 2.2E.

Cause and prerequisites

Program error

Solution
Consider the following notes and copy the corrections according to your release:

11700 (2.2E)
16852 (2.2E)
19210 (2.2E)
19522 (2.2E)
20772 (all releases)
20774 (2.2E)
20776 (2.2E)
20780 (2.2E)
20787 (2.2E)
20789 (2.2E)
20798 (2.2E)
20918 (2.2E)
20976 (2.2E)
21362 (2.2E)
21435 (2.2E)
21533 (2.2E)
21678 (2.2E)
23813 (2.2F)
28470 (2.2G)
30104 (3.0C)
31832 (3.0C)
31957 (2.2G)
32461 (3.0C)
33084 (Consultant note for all releases)
33420 (2.2H, 3.0D)
34483 (2.2H, 3.0D)
43736 (2.2J, 3.0E)
47893 (2.2J, 3.0F)
33706 (2.2Z)

Additional key words

Backorder processing, transaction: V_V2, program: SDV03V02

SAP Note 24478 - Matchcode for GMTLs displays deleted task list no.

Symptom:

A matchcode search for general maintenace task lists displays deleted task list numbers.

Cause and prerequisites

Incorrect selection criteria in matchcode definition

Solution
Please change the settings identified by "-->CHANGE .

Correction Matchcode object : PLKS
Matchcode-ID : I
Selection criteria of matchcode ID PLKS-I:
Subfield
NOT MC-Field Lgth Offs Op Constant AND/OR
-------------------------------------------------
PLNTY 1 EQ 'A' AND
LOEKZ 1 EQ ' ' "-->CHANGE

Activate the matchcode afterwards and create it again. Use Transaction
SE14 to create the transparent matchcode ID I again.

Additional key words

General maintenance task list
Matchcode search
PLKS

SAP Note 24471 - VD346: Period indicator 4 is not defined

Symptom:

When you create an order item with date type P (period), error message VD346 is displayed: Period indicator 4 is not defined. However, table TPRG contains an entry with language D, delivery date P, and date type 4. This means, the date type P is proposed as a possible entry by means of F4.

Cause and prerequisites

Date type 4 (period indicator P) is not defined. This is hard-checked when converting the date.

Solution
None. This date type may not be used in purchase orders.

Additional key words

ME21 ME22 PERIOD_AND_DATE_CONVERT_INPUT LVDATU01

SAP Note 24457 - Missing BOM long texts after client copy

Symptom:

After a client copy, all texts in the bill of material cannot be accessed.

Cause and prerequisites

Error in the long text key

Solution
Write the following report and start it in the new client where you only specify the source client as parameter.

If the texts have already been copied with program RSTXTCPY, the source client is = new client. Otherwise, the client from which the client copy was carried out is to be specified as source client.
PROGRAM ZZTXTCPY.

DATA: HLP_COUNT TYPE I.

*-- Textheader
DATA: BEGIN OF THEAD_TAB OCCURS 0 .
INCLUDE STRUCTURE THEAD.
DATA: END OF THEAD_TAB.
*-- Textlines
DATA: BEGIN OF TLINE_TAB OCCURS 0 .
INCLUDE STRUCTURE TLINE.
DATA: END OF TLINE_TAB.
*-- Textnamen in Mandant plus Rest einteilen
DATA: BEGIN OF TDNAME_NEW,
TDMANDT LIKE SY-MANDT,
TDREST(67) TYPE C,
END OF TDNAME_NEW.
*-- Alter Textheader
DATA: BEGIN OF THEAD_SAV.
INCLUDE STRUCTURE THEAD.
DATA: END OF THEAD_SAV.

DATA: OBJECT LIKE THEAD-TDOBJECT VALUE 'BOM '.

PARAMETER: QUELLMDT LIKE SY-MANDT.

*-- Lesen und Umsetzen der Langtextschlüssel
REFRESH THEAD_TAB .
THEAD_SAV-TDID = '*' .
THEAD_SAV-TDNAME = '*' .
THEAD_SAV-TDSPRAS = '*' .
CALL FUNCTION 'SELECT_TEXT'
EXPORTING
CLIENT = QUELLMDT
DATABASE_ONLY = 'X'
ID = THEAD_SAV-TDID
LANGUAGE = THEAD_SAV-TDSPRAS
NAME = THEAD_SAV-TDNAME
OBJECT = OBJECT
TABLES
SELECTIONS = THEAD_TAB.

CLEAR HLP_COUNT.
LOOP AT THEAD_TAB.
HLP_COUNT = HLP_COUNT + 1.
REFRESH TLINE_TAB.
*---- Neuen Textnamen setzen
TDNAME_NEW = THEAD_TAB-TDNAME.
*---- Mandant setzen
TDNAME_NEW-TDMANDT = SY-MANDT.

CALL FUNCTION 'READ_TEXT'
EXPORTING
CLIENT = QUELLMDT
ID = THEAD_TAB-TDID
LANGUAGE = THEAD_TAB-TDSPRAS
NAME = THEAD_TAB-TDNAME
OBJECT = THEAD_TAB-TDOBJECT
IMPORTING
HEADER = THEAD_SAV
TABLES
LINES = TLINE_TAB
EXCEPTIONS
ID = 01
LANGUAGE = 02
NAME = 03
NOT_FOUND = 04
OBJECT = 05
REFERENCE_CHECK = 06.

IF SY-SUBRC EQ 0.
THEAD_SAV-TDNAME = TDNAME_NEW.
CALL FUNCTION 'SAVE_TEXT'
EXPORTING
CLIENT = SY-MANDT
HEADER = THEAD_SAV
INSERT = 'I'
SAVEMODE_DIRECT = 'X'
TABLES
LINES = TLINE_TAB
EXCEPTIONS
ID = 01
LANGUAGE = 02
NAME = 03
OBJECT = 04.
IF SY-SUBRC EQ 0.
CALL FUNCTION 'DELETE_TEXT'
EXPORTING
CLIENT = SY-MANDT
ID = THEAD_TAB-TDID
LANGUAGE = THEAD_TAB-TDSPRAS
NAME = THEAD_TAB-TDNAME
OBJECT = THEAD_TAB-TDOBJECT
SAVEMODE_DIRECT = 'X'
EXCEPTIONS
NOT_FOUND = 01.
ENDIF.
ENDIF.
IF HLP_COUNT EQ 20.
COMMIT WORK.
CLEAR HLP_COUNT.
ENDIF.
ENDLOOP.

SAP Note 24456 - SU12: Abnormal termination

Symptom:

Transaction SU12 terminates when deleting all users.

Cause and prerequisites

Program error: Within a Select statement, a Commit is executed.

Solution
Correction is available in Release 3.0A. You can also make the following modification in program SAPMS010:

SAP Note 24455 - Export control also for domestic transactions

Symptom:

The system's export control is also carried out for sales documents for domestic business transactions and locks the document items for further processing.Cause and prerequisites

Incorrect setting of the sales document or item category in Customizing

Solution

Request from several customers: Export control also for domestic transactions

Status up to now:

Customizing sales document types:
=================================
activating/deactivating export control
' ' - no check
'C' - full check


The control of the display of the error log is also carried out at this point:
Dialog export license (X/ )


Customizing item categories:
============================
Controlling the type of the export license
' ' - no check
'A' - only dispatch (also domestic)
'B' - only export
'C' - dispatch and export (also domestic)
'D' - dispatch and export (excluding domestic)


Note: Option 'D' is available in the standard system as of 3.1F.

A document item is blocked for further processing by export control if system status EXLS is set for the item.
Path in order processing:
Item
--> Status



How to unblock blocked document items: ======================================

    1. In Customizing for the relevant item category (view V_TVAP), set the control of the export license type to ' ' or 'B'.
    2. Access the relevant document in change mode and start the export control again via the path.

Sales document
--> Export license
--> Redetermination

and save the document.
Afterwards, the system resets system status EXLS which caused the blocking of individual items.

    3. After having unblocked a document, you may have to do the following:
    Set the control of the export license type to ' ' in Customizing for the relevant document type (view V_TVAK) and therefore
    completely deactivate the export control.

You cannot create deliveries. Additional key words

Export control
Export
System status
EXLS


SAP Note 24447 - MR08 Error M8356 - Cannot cancel invoice

Symptom:

When trying to cancel an invoice, the error message M8356 - Invoice cannot be cancelled appears.

Cause and prerequisites

MR08 creates the cancellation invoice using batch input in background. If the batch input fails, then the error message M8356 is returned, rather than the actual error message from the batch input run.

Solution
From version 22E onwards, you can debug this easily by using special OK-codes in MR08.

Instead of using the normal POST/SAVE function, enter OK-code:
RBSA - to see the batch input in foreground
RBSE - to see the batch input in errors only mode

Prior to 22E - you need to set a breakpoint in MM08SF10, in form STORNOBELEG_ERZEUGEN and just before executing the statement CALL FUNCTION 'MR_CREATE_INVOICE...' set the value of SBKPF-STYPE to 'A' (foreground) or 'E' (errors only).

There are several corrections in this area already. Please check the following notes for a possible solution:

16416 - Error due to allocation number not ready for input
16922 - Error due to external number assignment
17412 - Error due to vendor required fields such as SCB indicator
17876 - Error due to missing payment terms, payment method, etc.
21841 - Cancellation with additional data
22413 - Error due to non-deductible input tax
22549 - Cancellation with POR data

I have included these in the related notes section.

Additional key words

SAPMM08S SAPLMRBI MR_CREATE_INVOICE

SAP Note 24445 - Error msg. EAF004 for post-capitalization

Symptom:

When you post-capitalize an asset, the system displays error message AF004 "Date 00/00/0000 is not defined".
OR: WHen entering a post-capitalization (transaction AS12) no depreciation start is determined.
This error occurs only when the system is in productive mode. The post-capitalization can be carried out without any problems in test mode.

Cause and prerequisites

Program error.

Solution
Preliminary correction
CAUTION: Portions of the preliminary correction are already present as of 2.2G or 2.1M. If that case please maintain only the following changes.

Additional key words

AS12 SAPMA02S AF004

SAP Note 24441 - CR134 No authorisation to reflect change in HR

Symptom:

Message CR134 "No authorization to reflect the change in the HR System." when attempting to create or maintain a Work Center

Cause and prerequisites

This message arises because the user is not authorised to maintain information in the HR-PD (Personnel Planning and Development) module.
Occurs only if the interface between Logistics and HR is enabled, via Customizing.
In HR, if WorkCenters are changed, a corresponding Work Center is changed in Logistics.
In Logistics, if Work Centers are changed, a corresponding change is made to the HR work center.
To make this change, the user needs HR authorisation.

Solution
Resolution:
If INTEGRATION between Logistics and HR is not required, CHANGE configuration.

< 3.0
Path:Configuration>Logistics>PM>PM Planning>Work center>HR Interface Ensure that the HR Active flag is not selected.
In 3.0, via the IMG,
PM -> Preventative Maintance -> Work Centers -> Activate Interface to Human Resources.

Else,
Give the user the following authorisation object..

Object PLOG,
Infotype 1000,
Planning status 1
Object Type A,
Plan Version to match that specified in the configuration,
Function Code INSE, AEND, DISP etc
Subtype

Additional key words

IR01 IR02 SAPMC68A CR134

SAP Note 24438 - Are processed sessions physically traceable?

Symptom:

A batch input session ran successfully. Is there an option, to display it afterwards?

Cause and prerequisites

You want to be able to reproduce what was done later on.

Solution

Background input sessions are physically stored in the tables APQD and APQI.
After processing, they are only deleted automatically if

  • data transfer was successful and
  • the flag "KEEP" was not set in the function module BDC_OPEN_GROUP when creating the session.
If this is not the case, the session must be deleted manually.

You can see that a session was deleted by choosing "SM35 -> Overview -> Session". If it was deleted, it is no longer listed. There is then no way to "retrieve" it.

The background input logs are in the file /usr/sap//SYS/global/BI (Unix)
\\\sapmnt\\sys\global\BI (NT)
and can be displayed with "SM35 -> Log". Logs are never deleted automatically, but are retained until they are deleted manually. The procedure is described in note 18307.

Old sessions and protocols can be deleted by running RSBCDREO. Note that this report is client specific. For details see Note 18307.

Additional key words

BDC_OPEN_GROUP

SAP Note 24436 - MSC2 error message M3-506 enter a language text

Symptom:

MSC2 error message M3-506 Enter a language for the text. The language doesn't default to the session language for the INTERNAL COMMENT text in the batch master record. When a text is entered, the error message is received. This is inconvenient for sites where only one language is used.

Cause and prerequisites
Solution
In Screen Painter, for program SAPMM03S screen 200, using FIELD LIST, change the ATTRIBS.FOR 1 FIELD for field RM03S-SPRAS to turn on the SPA/GPA parameter flags for parameter id SPR. The SPR parameter should be set in USER PARAMETERS for each user.

Please be aware that only ONE language may be used for each batch. Once the language is set it cannot be changed. Therefore, if different languages are to be used for different batches the SPA/GPA parameter flags should NOT be on, but the language set manually when the text is first entered.

Additional key words

SAPMM03S MSC1 M3506

SAP Note 24429 - Transaction without check object

Symptom:

A transaction can be used by every user without authorization.

Cause and prerequisites

No check object is allocated to the transaction.

Solution

Allocate a check object to the transaction in table TSTC (to be maintained with SM31).

Special examples:
  • Transaction check object CO78 C_AFKO_ATY

SAP Note 24427 - Copying variants between clients and systems

Symptom:

The Report Writer generates ABAP/4 programs from the definition of a report group. The user can create variants for the entries in these programs on the corresponding selection screens.

    1. Because the name of the generated program depends on the client, it is not possible to transport variants from one client to another client using standard means.
    2. It is also not possible to transport such variants from one R/3 system to another, since report group variants are local objects.
Cause and prerequisites
Solution
    1. Using the following program ZZRVARI0 (for Release 2.2) or ZZVARI1 (for Release 3.0), you can copy Report Writer variants from a source client to a current client.
    The 2.2 version of the program is delivered as of Release 2.2F with the name RGRVARIO.
    The 3.0 version of the program is delivered as of Release 3.0D with the name RGRVARI1.
    When you execute the program, you must enter the source client in the selection screen as well as the report groups or libraries for which variants are to be copied.
    The program only copies variants for report groups that exist in the current client. You can copy report groups from a source client by performing the function 'Utilities' -> 'Transport' -> 'Copy from client' in transaction GR55.
    2. Using the following program ZZRVARIX (only for Release 3.0), you can transport variants from one system to another.
    You can export variants to a local file and import from the file into the target system.
    The 2.2 version of the program is delivered as of Release 2.2J with the name RGRVARIT.
    The 3.0 version of the program is delivered as of Release 3.0F with the name RGRVARIX.

    For Releases 2.2A to 2.2I, you can copy program RGRVARIT from SAP server SAPSERV3. Both transport files K017069.P22 and R017069.P22 are available in the directory /dist/permanent/Note.0024427.
    For Releases 3.0A to 3.0E, you can find files K002133.A30 and R002133.A3 which contain report RGRVARIX in the same directory.

    Further information on transferring transport files to your system can be found in OSS note no. 13719.

Additional key words

Report Writer, GR55, transport, ABAP, variant, program. ----- SUPPORTGUIDE 20010329165131 -----
REPORTWRITER, SGRW_VARIANT, SGRW_TRANSPORT, SGRW_DOCU_CONS_NOTE
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS


SAP Note 24422 - Rebate verif. level: Incorrect +/- sign of accrual

Symptom:

The +/- sign of the accrual for cancellation billings and returns is displayed incorrectly in the drill-down.

Cause and prerequisites

Program error.
The note is valid only as of 2.2E.
The problem is corrected in Release 2.2I and 3.0E.

Solution
Program change.

Additional key words

Rebate agreement.

SAP Note 24392 - Posting with incorrect document type in SAPF100

Symptom:

The valuation during a valuation run is also made in parallel currency where different valuation methods are used. However, the postings are not made with the document type which is predefined in the respective valuation method. All postings are made in one document type.

Cause and prerequisites

Program error.

Solution
Maintain correction.

Additional key words

SAPF100

11.3.11

SAP Note 24389 - Unplanned consumption, incorrect update

Symptom:

During a goods movement with reference to a reservation (reservation created manually or automatically), the unplanned consumption is updated incorrectly in the following cases:
a) The quantity issued before the goods movement was greater than the reserved quantity.
b) You post a reversal which does not apply to the entire reserved quantity but only to a part of it.

Cause and prerequisites

Program error

Solution
Please make the following changes in Include MM07MFV0 in FORM routine V-SEGMENTE_GENERIEREN:

SAP Note 24380 - Batch input conditions: Field 'KONP-KONWA'

Symptom:

When importing the condition records, program RV14BTCI terminates with the error message:
"Field KONP-KONWA is not an input field"

Cause and prerequisites

The condition type is set as a percentage condition (calculation type 'A').

Solution
In the external file, in field BKOND2-KONWA enter the character which is specified in the session data as NODATA character (field BGR00-NODATA). If no character is specified there, use the character '/' as NODATA character.

Additional key words

RV14BTCI, batch input for the creation and change of condition records.
Condition maintenance, calculation type, KNTYP, background session

SAP Note 24378 - F4 on matchcode field in the display mode

Symptom:

Message:
"No matchcode selection is possible in display fields".

Cause and prerequisites
Solution
In reviews with application developers, it was determined that F1 and F4 should also work on display screens.
That is, the possible entries pushbutton key always appears on the edge of a field.
With the aid of the key word MODIFY SCREEN and VALUE_HELP = 0, the possible entries pushbutton can be deactivated at runtime. However, this must be coded by the application developers.

SAP Note 24374 - Structure of table TST03

Symptom:

In the ORACLE table TST03 (tablespace PSAPPROTD) the variable length field DCONTENT has a size of 9996 bytes in most cases. As the ORACLE block size is 8Kb on many installations, almosts all rows in TST03 are chained on 2 blocks and the second one is filled only 25%.

Cause and prerequisites

Why you cannot change the structure of TST03?
As you can see from the type of the fields, this table is not handled by ABAP programs, but only by routines of the C kernal. Ant the C kernal knows the maximum length of that field.

Why that strange length?
The length had been 31 kbytes long time ago. I had to reduce this to 9996 at a moment, when the R/3 data dictionary could handle only length information with four digits. At that time we did not know about the 8 Kbyte blocks of ORACLE. Or maybe ORACLE did not use blocks of that size in those early releases. Today I think 8032 bytes would have been better.

Why not to change the length at SAP?
The price for reducing the length is:

  • modify one constant definition
  • recompile the C kernal
  • copy and reformat the table at each customer. And typical customers have 200 to 800 MB data in that table.
  • this reformatting has to be done by a stand alone C program, because
    • R/3 cannot live without this table
    • SQLplus cannot handle that table
    • ABAP neither.

What SAP shall do?
The C kernal has to be modified in a way, that it still can handle data base rows of 10 Kbyte, but that it will insert only new records, which are smaller that 8032 Bytes net data.

Solution
Think about storing spool data in the file system. You can do so by the profile paramter
rspo/store_location = G
Disadvantage: the data backup will not cover the spool data any longer.

Additional key words

Spool, TemSe, TST03, SP12

SAP Note 24370 - Problems after typo in 'Create planning hierarchy'

Symptom:

If '1O0' instead of '100' is entered by mistake for portion when creating a planing hierarchy, the error 'Value cannot be interpreted as floating point is displayed. If 'O' is then replaced with '0' and F2 is pressed to branch to the subordinate level, error MA211 'Invalid cursor position' is displayed. When pressing F3 to return to the superior level and followed by F2 to branch to the subordinate level again deletes the created definition.

Cause and prerequisites

Incorrect program code

Solution
Change to the program code

SAP Note 24368 - Vol.-based rebate: Exclusive indicator in access sequence

Symptom:

  • If the 'Exclusive' field is used during access sequences for volume-based rebate, the exclusive indicator is not considered during pricing or during the rebate payment.
Cause and prerequisites

Program error

Solution
The exclusive indicator cannot be dealt with easily in the case of rebates.

In Release 3.0A, this field has been deactivated.

Basis/Example (in case the exclusive indicator will be used):

For a volume-based rebate condition type (e.g. BO01), an access sequence is stored that refers to two condition tables. The exclusive indicator is set for the first access (e.g. A601):

1.Access e.g. table A601 then
2.Access table A602

In the next stage, a annual agreement is created (e.g. 1) on the first of January, which contains a condition record from table A602. Sales volume is calculated for agreement 1.
If a second agreement (2) is created the first of June, containing a condition record from table A601: agreement 2 implicitly influences agreeemnt one via the exlusive indicator.
As soon as the condition record has been created in agreement 2 for table A601, the record in table A602 is no longer relevant for agreement 1 ( due to the exclusive indicator ) and alters the sales volume in agreement 1 (this is undesirable).
To avoid this, exclusive indicators can not be used for access sequences that are relevant for volume-based rebate.

The access sequences for volume-based rebates need to be edited, and theexclusive indicator should be cancelled.

Carry out the following changes to the program

Additional key words

Rebate, access sequence, exclusive

SAP Note 24361 - Report Writer: Actual line item reports

Symptom:

The customer wants to define an actual line item report using the Report Writer. (table COEP / view COVP)

    1. Report Writer reports cannot be defined with several text columns.
    2. The line item reports defined in the Report Writer have a very long runtime.
Cause and prerequisites
    1. The function is not supported.
    2. The Report Writer is a very general tool for flexible report creation and of course, there are some special cases that do not run with maximum performance.
Solution
    1. Tool KSB1 (actual line item report) is available to display actual line item reports. Customer-specific columns can also be created for this. See Customizing documentation to find out how to define your own display variants for actual line item reports in Cost Center Accounting. For the actual line item reports, you can make a selection from all the fields of COVP (it only contains CO fields!).
    Short guideline: KSBK > Cost objects > Display variants > Insert
    (as of Release 4.0 the display variant is directly defined in the line item report "Settings -> Display variant -> Current ...")
    2. Since they are hard coded, the actual line item reports that are created in this way run with optimized performance.

Additional key words

----- SUPPORTGUIDE 20010208103353 -----
REPORTWRITER, SGRW_DOCU_CONS_NOTE, SGRW_LINEITEM
SGRW_OM


SAP Note 24357 - CM01, Exception condition MISSING_PARAMETER raised

Symptom:

When executing transaction CM01 (Capacity planning) the transaction abends. The abend message reads "Exception condition MISSING_PARAMETER raised".

Cause and prerequisites

MISSING_PARAMETER is not a valid exception for the function CR_CAPACITY_AVAILABLE_PERIODS

Solution
Change the exception MISSING_PARAMETER into HIERARCHY_NOT_FOUND.
Add Message in function module: CY_FILL_KAPAN

Additional key words

Function 'CR_CAPACITY_AVAILABLE_PERIODS'

SAP Note 24353 - Transkation SQUE terminates.

Symptom:

Transaction SQUE (tables/View maintenance) terminates because the function module VIEW_EDIT does not exist.

Cause and prerequisites

The transaction SQUE is now out of date and is no longer supported.

Solution
Instead of transaction SQUE, use transaction SM30.

SAP Note 24350 - EDI: Length of field EDI_Z9-GWERT increased

Symptom:

Field GWERT in structure EDI_Z9 is checked for length 6 although the document field is a 9-character field.

Cause and prerequisites

Program error

Solution
Correction S11K133750 in program SAPLVEDI

SAP Note 24338 - Display asset values with asset subnumber "*"

Symptom:

The "Display asset values" transaction AW01 displays incorrect depreciation values for the depreciation forecast summarized for all subnumbers (Subnumber * in initial screen).

Weitere Begriffe
Cause and prerequisites

The depreciation forecast which is summarized for all subnumbers always uses the useful life of the main asset number as the planned useful life. Deviant useful lives of corresponding asset subnumers are not taken into account in the depreciation prognosis.

Solution
A separate callup of the asset subnumbers (without summarization) displays the correct values.

SAP Note 24336 - NT: Hardware compression does not work

Symptom:

Although a tape unit with hardware compression is available and the compression is switched on as a default on the tape deck, it is inactive during database backups with BRBACKUP/BRARCHIVE. This means that the whole tape capacity (see Note 8707) cannot be used.
For example, on a 4mm DDS-2 disk drive with a 120m tape, you can store only 3800 MB instead of at least 8000 MB (uncompressed).
The cpio command started by the BRBACKUP/BRARCHIVE then runs on to the end of the tape: BR278E Command ... cpio ...
cpio: write error on file "...": The physical end of the tape has been
reached.
BR279E Return code from ... cpio ...
BR222E Copying ... failed.
Caution:
--------
You can use the command "mt -f /dev/mtx status" to determine whether hardware compression is really turned off. The mt.exe command is delivered with the SAP executables.

Cause and prerequisites

The default on the tape deck is reset after running NT Backup, regardless of whether hardware compression was chosen in this case or not.
This is a default function of NT Backup in Windows NT 3.5.

Solution

Option 1:
---------
Some tape decks have the option to define hardware compression not only as a default setting but as a fixed setting. Read the tape unit documentation and use this option if possible.

Option 2:
---------
Activate the hardware compression after running NT Backup:

    • If the tape unit is connected as an external device, turn it off and then back on again, in order to reset the hardware compression mode to the default value.
    • If the tape unit is integrated into the system unit, the NT system must be rebooted.

Option 3:
---------
You can activate the hardware compression manually using the program compression.exe which can be found on sapservx in the directory /general/misc/sapdba/[ntintel|ntalpha].

Option 4:
---------
In the meantime, a corrected version of NtBackup has become available. It does not change the compression status (on/off) of the tape station. It can be downloaded from sapserv3/sapserv4 from directory /dist/permanent/sapdba/[ntintel|ntalpha].
The executable there must be uncompressed before use.
ftp sapserv3/sapserv4
(User/Password): ftp/ftp
cd /dist/permanent/sapdba/[ntintel|ntalpha]
bin
get ntbackup.exe.Z
quit
uncompress ntbackup.exe.Z
Then replace the old file:
ren x:\winnt\system32\ntbackup.exe ntbackup\old
copy ntbackup.exe x:\winnt\system32\ntbackup.exe

Caution:
--------
The corrected version of NTBackup can be found in Service Pack 2 of NT 3.5 and NT 3.51.

9.3.11

SAP Note 24334 - instinf_determine_disk_sizes 3 install error no:18

Symptom:

The installation of Informix terminates with the following error message in the R3INST.LOG:
instinf_determine_disk_sizes 3 Informix installation error no: 18
Smaller than 520424 KB: /dev/vg01/prd22

Cause and prerequisites

When installing raw devices, the size of each raw device is tested to check that it does not drop below or exceed a certain size.

  • The minimal size of a raw device is controlled by the total of the root, phys, log and tmp dbspaces.
  • The maximum size of a raw device is fixed at 2GB.
    (The UNIX call SEEK can only handle addresses from 0 to 2^31-1 = 2GB)
    For this reason, the total of "offset" and "size" of a chunk must also not exceed this limit.
Solution

Please check whether the raw devices adhere to these limits.
If the limits were adhered to, but the error message still appears, please test whether the raw devices physically allow themselves to be read.

  • Stop all programs, which access the raw device in question. Therefore, also shut down the database.
  • Execute the following "dd" command. dd if= of=/dev/null bs=1kExample: > dd if=/informix/QIH/sapdata/physdev1/data1 of=/dev/null bs=1k
    1323540+0 records in
    1323540+0 records outThe size of this raw device is 1323540 kB.

If the output of "dd" does not match the determined operating system values, please get the hard disk manufacturer to check this.

SAP Note 24325 - DBIF_RSQL_INVALID_REQUEST during inv. samplng proc.

Symptom:

During the 'update' in the inventory sampling procedure MIS2, the program terminates with DBIF_RSQL_INVALID_REQUEST in module MM07SFP4.

Cause and prerequisites

The number of the physical inventory documents for an inventory sampling procedure is more than 125 documents.

Solution
Corrected in module MM07SFP4 using editor SE38

SAPNote 24323 - Consulting Issue - SAP Asia Pacific

Symptom:

Solution

Dear Customer,

We confirm the receipt of your message above, which was given due attention. The details of the question do not indicate an error in the SAP system, but a consultancy job.

For consultancy job, please contact our consulting manager in your country to arrange for consulting help. Please note that consultancy is chargeable.

Our consulting managers are:

Country Name Phone Fax
-----------------------------------------------------------------------
Singapore Mr Dickson Ho (65)68901241 (65)68901493
Malaysia Ms Choy Leng Lee (60)321755002 (60)321632688
Hong Kong Mr.Ng Mau Wing (852)25391822 (852)25391818
Philippines Mr Joseph Victor Gloria (63)28480181 (63)28480168
Korea Mr Jong Kwan Choi (82)221942677 (82)221942691
Beijing Mr Eric Li (86)13801028113 (86)1085298588
Shanghai Mr Haining Wu (86)13601762743 (86)2163345758
Indonesia Mr Gun Gun Gunawan (62)215724289 (62)215724292
Thailand Mr.Boonkird Sombathiranvong(66)26311800 (66)26311818
India Mr N Sridhar (91)8041365501 (91)8025095986
Taiwan Mr Vincent Cheung (886)225146469 (886)225146418


Please quote the SAP Problem No to avoid having to reformulate your question. Please contact SAP within 14 days, otherwise your case will be considered as closed.


Kind Regards,
SAP Active Global Support

SAP Note 24315 - RF42BAGV: Amounts are displayed incorrectly

Symptom:

In the clearing procedure display, the cash discount and local currency amounts are displayed with the incorrect number of places behind the decimal point.

Cause and prerequisites

Program error

Solution
Error is corrected with 3.0A and 2.2G, advance correction is possible.

Additional key words RFEPOS00, FBL1, FBL2, FBL3, FBL4, FBL5, FBL6

SAP Note 24312 - Inventory management - system message M7022

Symptom:


With Customizing transaction OMCQ, you can define whether system messages in inventory management should be issued as warning message or as error message.

Despite the warning message setting, message M7022 is issued as error message during the goods receipt posting:

"E: & exceeded by & &"

Cause and prerequisites


During the goods receipt with reference to the purchase order or the production order, overdeliveries are only allowed if this was determined in the purchase order or order (indicator "Unlimited" or definition of the "overdelivery tolerance"). If this is exceeded, the system will always display an error message.

The corresponding system message was hard-coded as error message in the program. In these cases, the Customizing settings have no effect.

The Customizing option for error message M7022 is used elsewhere (for example during the availability check).

Solution
None.

Additional key words

Transaction: MB01, MB31, CO11, CO15, COR6, CORZ, CORK

SAP Note 24311 - BCD_FIELD_OVERFLOW for non-calendar fiscal year

Symptom:

When dealing with dates (for example: setting start date of depreciation), the program terminates (BCD_FIELD_OVERFLOW) when the first day of the fiscal year is being determined.

Weitere Begriffe

AS01, AS02, AS91, AS92, date, start date, T009, T009Y

Cause and prerequisites

Year-dependent fiscal year versions the beginning or end of which falls within the first month of a calendar year have been maintained.

Solution
Please correct the following INCLUDE:

SAP Note 24304 - RPTDSH00 : day program on incorrect weekday

Symptom:

Symptom

If a month is selected from the overview list for detailed display, the
display of the incorrect weekday is taken.

Weitere Begriffe
Cause and prerequisites

Program error.

Solution
This error has been corrected with P21K005503B in 2.1L, P22K007627B
in 2.2F and XWIK112253 in 3.0A. You can carry out an advance correction.
Please include the lines marked "<--new" in report RPTDSH00.

SAP Note 24303 - ORA 600 [2845] or ORA 600 [2846] or ORA 600 [2130]

Symptom:

ORA600 [2845] or
ORA600 [2846] or
ORA600 [2130] appears in trace files

Cause and prerequisites

- bug in ORACLE 7.1.4

Solution
Upgrade to ORACLE 7.1.6 (R/3 2.2F):

There is a patch for the operating system HP-UX (please contact the
hotline!) which solves the problem in ORACLE 7.1.4.

If it is not possible to upgrade to 7.1.6, the problem can possibly be solved by temporarily reorganizing the table in which the error occurred.

SAP Note 24298 - RFFORI07 payment summary - Incorrect CCode total

Symptom:

The total per company code is displayed incorrectly in the payment accompanying list when credit memos and debit memos were processed in one run.

Additional key words

RFFOD__U, RFFOAT_U, RFFOCH_P, RFFOCH_U, RFFOBE_D, RFFOBE_E, RFFOBE_I

Cause and prerequisites

The amounts are totalled regardless of the +/- sign.

Solution
Error is corrected in Release 2.2G / 3.0C.
You can make the following advance correction.

SAP Note 24288 - Deleting sets after deleting structure fields

Symptom:

It is not possible to delete basic sets if you already have deleted the respective fields of the DDIC structure or even the DDIC structure itself.
Error messages
GU142 "The table ... does not exist"
GU141 "The field ... does not exist"
Further key words
Transaction GS04 (Delete set)
Set maintenance

Cause and prerequisites

Program error

Solution
Option 1: From the list of the sets not used, delete the set (program RGSNUS00).
Option 2: Deletion of the set by calling up the function module G_DELETE_SET in the testbed of the function module maintenance (transaction SE37). Call parameters: TAB=table name, SET=set ID.
You can even delete entire set hierarchies using the function module G_SET_TREE_DELETE.

SAP Note 24286 - KE30, termination of SAPLKES1 with RAISE_EXEPTION

Symptom:

Transaction KE30, report SAPLKES1 terminates with RAISE_EXEPTION - VARIABLE_NOT_FOUND:
Path:
Accounting -> Controlling -> Profit. analysis -> Reporting -> Execute report.

Cause and prerequisites

The row/column structure contains a global variable which does not exist in variable table TKESV. The cause for this status is unclear. The incorrect variable is possibly deleted from the variable table.

Solution
Replace the incorrect variable by an existing variable from the variable table.

SAP Note 24281 - User exit docu for electronic account statement

Symptom:

The documentation for the user exit is missing for the electronic account statement.

Reason and Prerequisites

This is caused by a transport error.

Solution
The documentation is delivered correctly as of Release 3.0!
This note contains the complete documentation.


Enhancement for the electronic account statement
Description

By means of this function exit, it is possible to analyze every line item on your electronic account statement and to add additional information.
In particular, it is possible:

    1. to search for clearing information (for example, document numbers, customer numbers and so on) in every sale.
    2. to change the internal activity (for example, on account of information from the note to payee),
    3. to Influence account determination by means of account modification

CAUTION: If you want to post with summarization (i.e. the posting rule of the current line item allows summarization), you must not fill E_FEBEP-KFMOD. Since summarized posting posting to various accounts is not planned for the electronic account statement and would lead to errors.

    4. to distribute the postings to different batch input sessions.
Link to the standard program

The electronic account statement is first imported completely into the bank data buffer. After importing, the so-called interpretation of data is carried out. During this step, every line item on the account statement is searched for clearing information by scanning the notes to payee line for document numbers or reference document numbers. After every interpretation of a individual sales by SAP modules, the function exit described here is called up. Here each customer can influence the further processing individually. After each callup of the function exit, the changed data is updated in the bank data buffer.
The actual creation of the postings is only carried out if all line items of the account statements to be processed were interpreted.

Structure of the transferred data

The function exit imports the following structures:

  • I_FEBKO = header record of the electronic account statement
  • I_FEBEP = line item of the electronic account statement
  • T_FEBRE = table of the notes to payee
  • T_FEBCL = table with clearing information

The function exit exports the following structures:

  • E_XFEBKO = header record of the electronic account statement
  • E_XFEBEP = line item of the electronic account statement
  • E_UPDATE = indicator, whether data in the exit was changed
  • E_MSGTYP = message category (E,S,W,I)
  • E_MSGTEXT = message to be output

The structures FEBKO, FEBEP, FEBRE and FEBCL are defined in the Data Dictionary. Note

Note

Via the structures FEBKO and FEBEP as well as the tables FEBRE and FEBCL, you receive all data which is contained in the SAP System for an individual sale (line item) of an account statement. This is data which come from the bank (e.g. amounts) and data that was extended during the process (e.g. company code).

ad 1.: Finding and transferring clearing information

Procedure: If the standard SAP algorithms for finding clearing information are not sufficient for your purposes, you can complete or reject the information already found (FEBCL). To do this, you must evaluate information from table FEBRE. This table contains the notes to payee which were supplied by the bank for this line item.
Example:
Your customers use your pre-printed money transfer forms. In this case, you know where you can find the clearing information in the note to payee. For the automatic clearing, you either need the document number (BELNR) or the reference document number (XBLNR) or the account number plus additional information for automatic clearing, such as document date.
Once you found the document number, you can fill the table FEBCL as follows:
T_FEBCL-KUKEY = I_FEBEP-KUKEY
T_FEBCL-ESNUM = I_FEBEP-ESNUM
T_FEBCL-CSNUM = 1.
T_FEBCL-KOART = 'D' for customer
T_FEBCL-AGKON = SPACE if clearing with BELNR, no account required
T_FEBCL-SELFD = 'BELNR' the selection field is the document number
T_FEBCL-SELVON = found document number
T_FEBCL-SELBIS = SPACE only to be filled for intervals


In this case, it is not really necessary to specify the customer number. If you do it anyway, you can possibly facilitate the postprocessing of incorrect transactions in the batch input session considerably. You can then choose the correct open items from the open items of the customer.
By means of the table FEBCL, you can transfer any number of clearing information. This is necessary, for example, when a customer settles several invoices by means of one payment. Do not forget here to extrapolate the field FEBCL-CSNUM.
Once you found a customer number and a document number, you can transfer the clearing information as follows:
T_FEBCL-KUKEY = I_FEBEP-KUKEY
T_FEBCL-ESNUM = I_FEBEP-ESNUM
T_FEBCL-CSNUM = 1.
T_FEBCL-KOART = 'D'
T_FEBCL-AGKON = 'TESTDEBITOR'
T_FEBCL-SELFD = 'BLDAT'
T_FEBCL-SELVON = '19940520' for document date 20 May 1994

ad 2.: Changing the internal activity

The internal activity (field FEBEP-VGINT) determines the posting rule and the account determination. It was determined via the allocation of external to internal activities (table T028G). It can happen that not all line items, that received the same external activity from the bank, are to be updated with the same posting rule. In this case, you can allocate another internal activity to certain line items and therefore change the posting rule.
Example:
You have assigned the Telekom and the utility company for service of electronic power a collection authorization for the telephone bills or account statements. On the account statement, you then get the same external activity for both direct debits. As a result, you must use the same posting rule for both activities without function exit, since exactly one internal activity is allocated to this external activity. By means ofthe function exit, you can then filter the telephone bills from the direct debits due to the note to payee and allocate them to another internal activity. You can thus , for example, post the telephone bill with another document type than the electricity bills.

ad 3.: Influencing account determination by means of account modification

CAUTION: If you want to post with summarization (i.e. the posting rule of the current line item allows summarization), you must not fill E_FEBEP-KFMOD.
The accounts to be posted to are determined via the internal activity and by replacing the account symbols. Account determination can be additionally influenced by means of account modification (field FEBEP-KFMOD).
Example:
An insurance company has defined the account symbol GELDEINGANG for the cash receipts of the policyholders. To improve transparency, the accounting department would like to post the cash receipt postings to another cash receipt account, depending on the insurance type. The insurance type is encrypted in the first three characters of the insurance number. The policyholders pay the insurance contributions using the pre-printed money transfer forms of the insurance, on which the insurance number is printed. In the function exit, the account modification can be set equal to the first three characters of the insurance number.
The G/L account for the bank account is 113100. In account determination, the follwoing entries are made:


Acct.symbol Acct.modif. Currency G/L account

GELDEINGANG + + ++++++++01

GELDEINGANG 200 + ++++++++20

GELDEINGANG 300 + ++++++++30

When a cash receipt occurs for the insurance numbers 200.1234.2345.11, the field FEBEP-KFMOD is set = '200' in the function exit. Thus, the postings are made to the account 113120. In case no insurance number is found with the cash receipt, the field FEBEP-KFMOD remains = SPACE and the postings are made to account 113101.
Note:
When defining the account determination, you can check with the function 'Simulation' whether your entries lead to the required result.

ad 4.: Distribution of the postings to different batch input sessions
You can distribute the postings of subledger accounting to different batch input sessions by filling in the field FEBEP-GRPNR with any two-digit identification code. The identification code is then part of the session name.

SAP Note 24279 - Missing billing document numbers in VBRK

Symptom:

Individual billing document numbers are missing from table VBRK - there are gaps in the number range interval.

Other terms

Number range object, RV_BELEG SNRO

Reason and Prerequisites

The problem is caused by update terminations in the billing document creation (transactions VF04, VF06 and VF01).
The billing document number is reserved prior to the update. After a possible update termination, it cannot be used again.
Update terminations are displayed in transaction SM13.

Solution
At present, no solution is possible.

SAP Note 24267 - SAPcomm: Landscape format in outbound fax

Symptom:

Fax documents can only be sent in portrait format.

Cause and prerequisites

Dependent on the fax system in use:

1) GammaFax:
Landscape is not supported by the GammaFax card.
2) Topcall:
Preconditions for landscape format:
- SAPcomm version 3.0A4
- Topcall version which supports the pagination command "++FF".

Solution
To change to landscape, the statement is sent to the fax system as part of the fax document. The statement is usually included in the form which is allocated to the fax document, but it can also be written as part of the text itself. The statement must always be written in the exact format required by the fax system in question.

GammaFax: There is no statement to convert to landscape format. Topcall: the statement is "++A4Q".
Other systems: Please consult the manual for your fax system.

SAP Note 24263 - OnArchive: Volume without save set (empty tape)

Symptom:

When working with the Informix backup tools, for example: ondatartr 'list/tape=(/dev/rmt0)'
the following message appears: ARC-E-01341, Error while reading save-set HDR1.
ARC-E-01342, Save-set file not found.

Cause and prerequisites
  • A tape is accessed on which there are no save sets (empty tape). The tape was labelled, but no backups were stored on it.
  • An incorrect device driver (e.g. for SUN SOLARIS "/dev/rmt/0n") was used to read the archive tapes.
Solution
  • Insert a tape that contains a backup.
  • To read the archive tapes, use a device driver which is able to read records of different length (minimum 512 bytes) and which is a so-called "rewind" driver (for example, for SUN SOLARIS "/dev/rmt/0b")
Additional key words

ARC1341, ARC1342, INF1341, INF1342, no save sets, empty tape

SAP Note 24261 - Vendor evaluation - Scrolling in log

Symptom:

The scrolling functions in the calculation logs of vendor evaluations generated via ME61 or ME63, or in the background via report RM06LBAT were not active.
Above problem also occurred in RM06LBEU, RM06LC00, RM06L001, RM06LBEW.

Cause and prerequisites

The functions were not defined in the CUA interface.

Solution

Transaction SE41:
----------------



Program : RM06L001: Status MAIN
RM06LC00: Status LIBA, SELE
RM06LBEU: Status MAIN
RM06LBEW: Status NEU, KEINE, BAUT

Supplement the function list for the individual statuses and activate
functions:

P+ Next page Next page <====== NEW
P++ Last page Last page <====== NEW
P- Previous page Previous page <====== NEW
P First page First page <====== NEW

Supplement F key assignments for the individual statuses.
---------------------------------------------------------


21 P First page <====== NEW
22 P- Previous page <====== NEW
23 P+ Next page <====== NEW
24 P++ Last page <====== NEW


===> Then generate the CUA interface.

SAP Note 24258 - RFBVD__1 with bank directory by Dresdner Bank

Symptom:

Whe you transfer the bank directory with report RFBVD__1 or RFBVD__2, error message FU808 is displayed if the indicator 'End of record marker' is set and error message FU806, if the indicator 'End of record marker' is not set. The bank directory originates from the Dresdner Bank.
Key words: RFBVD__0, RFBVD__1, RFBVD__2, BNKA, bank data

Cause and prerequisites

The bank directory which is output by the Dresdner Bank has another format than the standard system.

Solution
Please make the following changes in program RFBVD__0: /NSE38, RFBVD__0
Enter 'FI ASSIGN WA' in the header line of the editor


* ------ Passende Workarea assignen ---------------------------------
IF XEOR = SPACE.
IF XDISK = SPACE.
ASSIGN WA(187) TO . " <-- DELETE
ASSIGN WA(189) TO . " <-- INSERT
ELSE.
ASSIGN WA(188) TO .
ENDIF.
ELSE.
IF XDISK = SPACE.
ASSIGN WA(188) TO .
ELSE.
ASSIGN WA(189) TO .
ENDIF.
ENDIF.


You have to repeat this change again after each upgrade.
When you execute program RFBVD__1 (in Release 2.2*) or program RFBVD__2 (as of Release 3.0A) for transferring bank data (Customizing menu of Accounting: Tools -> Data transfer -> Bank directory), the indicators 'End of record marker' and 'File from disk' may both NOT be set.

SAP Note 24253 - OnArchive: Inconsistencies in OnCatlgr tables

Symptom:

The Informix backup tools OnArchive and Autovop do not carry out actions properly even though the hardware is OK.
For example, archive requests by the OnCatlgr are not deleted although the expiry date is already exceeded.

Cause and prerequisites

Inconsistencies have arisen in the OnCatlgr tables due to unusual events, for example, cancellation of OnCatlgr during the current operation.

Solution

To eliminate the inconsistencies, please proceed as follows:

  • Stop the OnCataloger stop_oncatlgr
  • Execute the script "arc_purge" to eliminate the inconsistencies dbaccess -e - $INFORMIXDIR/etc/arc_purge.sql
  • Start the OnCataloger again start_oncatlgr
  • Make sure that no requests have the status 'New' onarchive 'list/req=*/status=new/user=*'
  • Start Autovop so that all requests which have exceeded the expiry date are deleted start_autovop
  • If you can not cancel requests with the status 'New' or 'Executing' with onarchive 'cancel/req=' your only option is to set it to 'Failed' status manually:
    dbaccess sysmaster - << !
    update arc_request set req_status = 'FA' where req_rid = ;
    !
  • You can remove all request with 'failed' status as follows: onarchive 'remove/failed_request'
For all other inconsistencies it is necessary to drop and recreate all concerned vsets/volumes.
Please make a new level 0 archive of the database!

SAP Note 24238 - ArchiveLink: error opening queue

Symptom:

ArchiveLink (Monitor) job queues are not processed, even though the ARCHIVELINK job runs periodically without error. The following error message appears in the job log of the jobs processing the queues: Error opening queue
When the job queues from the ArchiveLink monitor are to be displayed, the error message "Error opening queue" is issued.
Key words: ArchiveLink monitor, queues, jobs

Weitere Begriffe
Cause and prerequisites

the queue is active and, therefore, blocked.

Solution
Use the job queue manager to change and carry out the corresponding jobs again. When you do this, the queue returns to its normal condition.

SAP Note 24237 - arcauto: Log file backup only on separate volumes

Symptom:

When backing up log files with the "arcauto" script, all backups are written to separate volumes.

Cause and prerequisites

These settings were consciously made in such a way to simplify tape handling (for example, one tape per day).

Solution

If the tape is to be changed only when it is full, "/APART" is to be changed to "/NOAPART" in the "arcauto" script (lines 117-119).
The tape then is written up to its end.

In every case, however, make sure that the tape is changed before the expiry date of the requests in the OnArchive Catalog: after this date the Request IDs are used again and having identical IDs on one tape can ruin the restoring the backup.
If you would like to set a tape explicitly to "full," so that a new volume is used for the next backup (for example, daily cron job), you should proceed as follows:

    1. Determine the volume label which is to be characterized as "full" (next volume to be used): arcauto -v -d
    2. Execute the following statement in the database sysmaster where the value 1 must be used for . update arc_volume
    set vol_full = 'Y'
    where vset_name = ''
    and vol_lable = ''
    and vol_vid = (select vset_vid
    from arc_vset
    where vset_name = 'VSet>');

    Caution: Since "Labels" can be assigned more than once during volume definition, all such volumes are marked as full.

Note: When saving with 'onautovop', every tape is taken which belongs to the correct Vset and is marked as 'Free' in the OnArchive tape administration!

We recommend this procedure especially when a separate tape is used for saving the log backup files on each day of the month (e.g., definition of 31 volumes, Expiry Date = 28). In this case, a new tape can be used for each day of the month and the request runs out after 28 days. This means that a free tape will always be available.

The disadvantage of this type of backup strategy is that tapes need to be changed frequently and in case of a log. restore, need to be changed just as frequently. In addition, the arcauto -d option can be used only with limitations, since all free tapes are displayed in descending order here. If this solution in used in conjunction with the day of the month, be attentive only to the day of the month to determine the correct tape: the arcauto -d option must not be used.

SAP Note 24233 - W-M7-158: Could not find sales price for & & & &

Symptom:

The system displays message M7 158
'Could not find sales price for & & & &'
as error message or warning.

Cause and prerequisites

The sales price valuation is activated in the valuation area in question and the system does not find a sales price for the material in question.

Solution
1. Please define the necessary sales prices if you want to carry out the inventory management with valuation for sales prices within R/3 Retail.
2. Otherwise, deactivate the valuation for sales prices for the valuation area in question using transaction SM32 in table T001K.

Additional key words

M7158

SAP Note 24222 - Positive lead-time in BOM for lead time scheduling

Symptom:

A positive lead-time is not taken into consideration for lead time scheduling of planned orders (e.g. during requirements planning).

Other terms

Negative lead time, scheduling, positive lead time, planned order,
NLFZT

Reason and Prerequisites

The entry of a positive lead time in the MRP data of a BOM component makes no sense for lead time scheduling.

Solution
The positive lead time is the number of workdays in which a component must be available after the start date of the higher-level assembly.
The entry of a positive lead time in the bill of material should show the time interval between the starting date of the order and the starting date of the operation to which the component is allocated, for the case in which no lead time scheduling is carried out.
If lead time scheduling is, however, calculated with the help of a routing, the requirements date of material components is derived from the operation date. For this reason, an entered positive lead time is not taken into consideration for lead time scheduling.

SAP Note 24219 - use of raw devices on Sun Solaris

Symptom:

Database has no access permission to its raw devices

Cause and prerequisites

system was booted with boot -r, or drvconfig command from command shell

Solution

When the SPARC system is rebooted using the boot -r command from the boot PROM monitor or when using a drvconfig command as user root from a standard UNIX shell, then the system reconfigures all the attached SCSI devices. This includes the generation of new device drivers in the /devices and /dev directory.
During this process the owner and group of the block and character special device files are set to root. Also permissions are set to 600 (rw-------)
If you try to startup the database (Informix or Adabas) it may complain that it has no access privilege to the raw devices.

Solution: set the right permissions manually

When using for example Informix as database do the following:
as user root: cd /informix/SID/sapdata
chown -R informix *
chgrp -R informix *
chmod -R 660 *

SAP Note 24218 - Same bank account number for different accounts

Symptom:

Customer has several bank accounts with the same account number at one bank for different currencies or other subgroups and has problems when customizing the electronic account statement.

Cause and prerequisites

Design.
So far it was assumed that an account can be clearly identified by the bank number and account number.
This was really the case until the credit institutions extended the account number that were not agreed upon.
A currency or branch code of the credit institution is now often added to the account numbers.
Inconsistently, the banks send the extended account number with the account statement. However, they are not able to receive these extended account numbers during the data medium exchange.

Solution

Solution in Release 3.0 =======================


The Alternative account number field was added to the house bank account table T012K (T012K-BNKN2). There, you have to enter the extened account number.

Solution in Release 2.1 and 2.2: ================================


1. Apply for different account numbers at the bank

If this is not wanted, use solution proposal 2


2. Double entries in the house bank account table T012K

The entries in the house bank table are used by the payment program and the electronic account statement. Since the bank uses two different account numbers and only one field is available for the account number in Release 2.1and 2.2, the problem can only be solved by double entries in the house bank account table T012K.
Here aou have to consider the following:

  • When making entries for the payment program, the field T012K-HKONT must stay empty.
  • When making entries for the electronic account statement, T012K-HKONT must be filled.
    Here it can happen that the account number is longer than the convention valid for the respective country and can therefore not be input. In this case, the account number, which is used for the account statement file, can be changed with the help of note 12038 so that it corresponds to the convention.
Key word: FI13, FF.5, RFEBKA00

SAP Note 24212 - Reference operation set during order creation

Symptom:

    1. A reference operation set is entered during order creation (Transaction CO01). However, this reference operation set is not exploded and taken over into the order. The system generates an order operation.
    2. Inserting a reference operation set manually into a production order does not work.
    3. A reference operation set to be inserted via a trigger point is not transferred to the production order.
Cause and prerequisites

This is caused by missing Customizing settings.

Solution
Add the specifications of the reference operation set to the table for controlling the 'Automatic Selection' in shop floor control Customizing (menu path: Operations -> Routing selection -> Automatic selection (Transaction OPJF)) to allow the transfer of reference operation sets.
The entries must be made for the selection ID of the used order type.

Additional key words

C0 807

SAP Note 24208 - Cut&Paste in the SAPscript editor

Symptom:

Customer inquiry:
How can you enter a text in the SAPscript editor with Cut&Paste without any changes?

Cause and prerequisites

Request for consulting

Solution

Every time a function key or return is pressed, the automatic screen formatting aligns the text according to automatic word wraparound points. This means that words that are split over the end of a line when typing are automatically joined again on the next line to allow faster text entry.

If you want to deactivate this screen formatting, you should use the paragraph format "/(". The "/" symbol stands for new line, the "(" stands for raw line, that is, line which is not to be formatted.

If you want to use this format for a whole screen, you should create this as a template first (for example, with 20 lines) in a user clipboard (Goto - User clipboard 1 - 3).

Reminder: Lines are copied with Mark F2 or a mouse double-click in the format column), then Copy and, as often as required, Insert. The user clipboard is also retained after the session (Clipboard - Save).

The following is recommended before using Cut&Paste:

  • Insert the contents of the user clipboard at the cursor position with the command Insert - User clipboard
  • Afterwards, paste the contents of the paste buffer into the text area

Future:

From Release 3.0, it will be directly possible via the command Insert - Clipboard to insert the Cut&Paste contents into the editor.

From Release 4.0, Cut&Paste will be supported in the new SAPscript editor and in a PC editor.