SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
Upgrading application servers that do not run with the DB server in
a cluster
The upgrade only involves the central system.
Program : SAPMV60S
No billing document is posted in the billing due list.
The entry Item category ' ' is not defined (TVAP) appears in the
error log of all item categories.
The billing quantity is not maintained in the document flow table.
The init
From Oracle version 7 onwards, the DC parameters are
calculated internally by Oracle, and are therefore no longer
listed individually in init
is parameter shared_pool_size. The SAP system uses transaction
ST04, Detail analysis menu, Dictionary buffer to access internal
Oracle tables, in order to display the dc values.
A red alert occurs in the global Alert Monitor due to missing
indices, although the text "Missing db indices: 0" is also
issued.
Indices that exist in the database, but that are not defined
in the SAP system, were also counted as defective.
Program : SAPMF82T
Time-dependent taxes should be created.
Requirement of the American market.
Abend 'GETWA_WRONG_LENGTH' occurs for Table KOMP. This can occur in all
programs at any point where Table KOMP is used.
When you generate an operating concern, the system adds new fields to
Table KOMP and then generates it. When this happens, the nametab is
rewritten on the application server. Consequently, the change remains
unknown to the other application servers until they read the new
nametab from the database after two minutes (synchronization). Until
that point they are inconsistent.
INFOREQ:
The reported error symptoms are not sufficient for a complete
diagnosis. Please send additional information.
None.
Key word: SAPLPD/info
The print output from remotely connected printers can terminate occasionally or often. The printers are connected by means of a relatively slow line (for example, 9,600 baud).
The printers are connected with access method 'U' or ' S'.
(This note does not apply if the data is already controlled by the host spooler - in other words, if access method 'L' is used).
WAN
Reason and PrerequisitesTimeouts occur during the data transfer.
The minimum throughput is 1 kbyte per minute for the LPD connection.
Run-time error during customer open item analysis with
RFDOPR00: BCD_FIELD_OVERFLOW in line
NTAGE = BSEGA-NETDT - DD_STIDA.
The same problem occurs during vendor open item analysis:
RFKOPR00.
1. No baseline date for payment (BSEG-ZFBDT) has been entered in
the relevant line item or has been entered incorrectly.
2. Field NTAGE can only include up to 999 days.
If inconsistencies still occur in the leave reduction (the leave reduction from infotype 2001 does not match the reduction in infotype 0005) once you have applied the corrections described in note 21216, you can correct them as follows.
(The procedure for Releases 2.1G - 2.1L, 2.2* and 3.0A - 3.0C only. The procedure for later releases is decribed in the collective note).
You can correct leave deduction by carrying out the following steps:
...
form fill_tab_holiday.
move-corresponding ptabs to holiday.
move ptabs-datum to holiday-date.
move ptabs-datum(4) to holiday-kjahr.
move p2001-beguz to holiday-beguz.
move p2001-enduz to holiday-enduz.
move t554s-ktart to holiday-ktart.
move-corresponding t554x to holiday.
* if ptabs-zeinh eq '01'. "Stunden ---> deactivate
if ptabs-zeinh eq '001'. "Stunden <--- insert
move ptabs-abrst to holiday-anzhl.
move ptabs-abrtg to holiday-anzh1.
else.
...
This report rectifies the leave account. You can delimit the choice of records to be corrected by specifying various selection criteria relating, for example, to the personnel number, payroll area and period. Select the 'Correct leave deduction' and 'Save leave deduction' fields, and 'Log output' if you wish the system to display a log afterwards.
This report regenerates the personal calendar necessary for maintaining the annual and monthly calendars. (When generating a calender with 'U' in Austria, problems can occur.)
Leave, leave entitlement, leave reduction, leave account, remaining leave, P0005, I0005, P2001, I2001.
The company code cannot be entered in master data maintenance.
No default company code appears, either.
Table T001K not maintained correctly.
A valuation area is assigned to each plant in table T001W.
T001K is used to assign the valuation area a company code.
During master data maintenance, the company code is then taken
from T001K. If no entry has been made in T001K, the company code
is not filled.
When processing partners in the order, the following errors occur:
The errors are corrected as of Release 2.2I or 3.0E. This means they
only occur up to Release 2.2H or in Release 3.0A - 3.0D.
After implementing this note, you also need to apply note 64119 (tax
determination when changing partner om item level).
Missing clear in the corresponding transfer flag (SAPMV45A).
Error in SAPDV02P
SAPDV02P Partner addresses
After an offline backup has been restored, brbackup demands a tape that was just used for this backup, therefore one that is normally still "physically" blocked (based on the information on the tape label).
Cause and prerequisitesbrbackup stores information on the tapes used in the database. During a restore, it is reset to the status during the backup. In this way, all the tapes that were used in this or the next backup are "logically" free (based on the information in the database).
SolutionThe following error message occurs during run-time of batch input:
00346 Field name does not exist in batch input data.
1. You tried to provide a field name in a screen with data using batch
input, and the field does not exist
The error message appears as follows:
00346 Field name HUGO does not exist in batch input data.
Field name HUGO does not exist in screen.
2. You tried to provide a field name in a screen with data using
batch input, and the field's name is "Space" and/or has "Space"
as field value.
The error message appears as follows:
00346 Field name does not exist in batch input data.
Field name is space.
Customer inquiry about the semantics of the ABAP/4 statements
SORT, AT NEW, and AT END OF when processing an extracted dataset
when the extract dataset contains fields set to hex zero.
In extracts, the value hex zero is the same as a ZERO value.
Within extracts, fields set to hex zero
- are always sorted before all occupied fields during a sort,
regardless of the sort sequence (ascending, descending)
- Are always skipped with AT NEW and AT END OF in control break.
Using hex zeros as ZERO values in extracts is especially important
when the data for extraction is read using a multi-level logical
database, and when subordinate segments of that logical database
are not always filled.
If both a cost center and an order are stored in the asset master, depreciation is only assigned to the order as of Release 2.2, although both the cost center and the order in the depreciation area should be posted.
Cause and prerequisitesDouble account assignments to the order and cost center must be avoided.
SolutionRABUCH00
In maintenance of actual times (infotype 2010), menu
item -> Goto -> Cost distribution
is not active. It is not possible to maintain cost distribution.
Table T582Z maintained incorrectly in field "Cost distribution".
When you process a BTCI session for transaction PA61, an error
message is issued: no input for screen MP200000 2450.
The session was created by a customer-written report.
In contrast to master data, module pool MP200000 is always used for
batch input for time data. Therefore the module pool name cannot
be derived from the number of the infotype.
Fetching of user parameters from the parameter pool or setting of parameters in the parameter pool must be explicitly programmed or accessed in the screen. Therefore, the parameters that are set do not automatically apply to all transactions. Example: Business areas (GSB) are not set for FI postings.
To determine whether parameter values have been set in the standard system, use SE51 to check the attributes (SPA/GPA) of the relevant screen field to see if it is active; then check the PBO (process before output) module in the flow logic to see whether "GET PARAMETER ID..." has been explicitly programmed.
Consumption-based (stochastic) planning.
If the lot size relates to weeks and the forecast period to months,
purchase requisitions to the amount of the forecasted monthly
requirements are created. Because of the weekly lot size, however,
you might expect that a planned order/purchase requisition to the
amount of the expected weekly requirements will be created.
A forecast based on the period "month" calculates monthly requirements.
Fronm the point of view of the system, these fall on the first workday
of the month and are scheduled by requirements planning for this date.
The weekly lot size groups together all requirements in the relevant
week, including the (monthly) requirements created by the forecast;
however, it does not divide up the latter into weekly quantities.
The OK code entered during batch input using field BDC_OKCODE
has no effect.
There are several reasons why the OK code might not work.
1. You made a typing mistake. Valid batch input OK codes are
type /11 or =upd. "/" and "=" are important.
2. The ENTER key has been assigned an OK code in the screen that
is provided with batch input data. click the right mouse button
or check in GUI Painter. The assigned value overwrites the
batch input OK code.
3. The application does not react to the OK code
4. You are processing the session in the foreground. A pushbutton
is active and you press ENTER to continue.
The OK code triggered by the pushbutton overwrites the
batch input OK code.
Program : MV50AF0F
Not possible to delete deliveries using function LOES
Not programmed
V0110
Low-value assets with a useful life of 1 month are not
written off immediately in the month of acquisition; instead,
the depreciation is distributed.
For example: depreciation start date of a fixed asset is 06/01/FY. Depreciation is planned as of this point in time until the fiscal year-end.
However, if a depreciation posting run is executed earlier, for example in March, proportional depreciation is already posted for the above-mentioned fixed asset, although the depreciation start date is 06.01.FY.
Proportional distribution is set in the depreciation posting rules.
SolutionMultiple logon, logon, number, session, window, APPC-TM, terminal
Information requirement or customer's security policy
The settings that have to be made to define a new font for an R/3 device type (in other words, a new printer font) that can be used to output SAPscript documentation.
Other termsPrinter, font, printer font, device type, font metrics, AFM file, SE73
Reason and PrerequisitesYou want to use a new font on the printer.
SolutionGeneral remarks:
Solution procedure:
If the font is a proportional font (HELVE or TIMES), an AFM file that contains the width values for the individual characters in the font must be entered under "Printer fonts" in SE73. Maintain the AFM file directly in the list of the printer fonts by choosing "Edit -> Edit font metrics".
As of Release 3.0A, you can choose a menu option to copy existing font metrics. To do this, place the cursor on the line with the newly created printer font, and choose "Edit->Copy font metrics". If you have created, for example, a new printer font
ZHPLJ3 HELVE 200 _ _
you can copy the metrics of
ZHPLJ3 HELVE 160 _ _
Releases earlier than Release 3.0A do not have this menu option, and you must use the XX.XX function in the AFM editor to manually copy the AFM files from the group box to the new printer font. The new AFM files can then be checked to ensure they are correct (choose "Font metrics ->Check") and saved.
As of Release 3.0, it is also possible to copy font metrics, create a reference to the font metrics of another device type or to a default metric (all characters have the width 500), instead of copying the font metrics. In SE73, in the list of printer fonts, you can check that the complete font definition is correct by choosing "Edit->Generate font def.".
The problem only occurs after logon in a language other than D.
After pressing F3 or F15 on a screen to leave the transaction,
a screen appears that contains no text.
The screen sequence tables are client-specific.
If a new client is set up and table T185T is not copied,
empty windows appear.
The display of the number of dialog steps does not agree
with the number specified in the workload statistics.
Since version 2.1D, the default settings of the survey graphics
will only show "online" dialog steps - this means that background
and update dialog steps are no longer taken into account in the
graphics. As a result, a lower number than the total is displayed.
The CO planning data is not posted directly to the Special Purpose Ledgers even though the relevant activities have been assigned to a ledger.
Planning data is only transferred if the plan version is also allowed in the Special Purpose Ledgers.
If a version is not allowed, the system does not return an error message because it would not otherwise be possible for specific ledgers to accept data for specific plan versions only.
Example:
Ledger Z1 should store planning data with version 002 and ledger Z2 should store planning data with version 003. The same activities have therefore been assigned to both ledgers.
If CO now transfers planning data with version 002, the system would issue an error message for ledger Z2; with version 003, the system would issue an error message for Z1.
In addition, integrated planning must have been activated in CO.
You should maintain the settings in FI-SL Customizing so that the plan versions transferred from CO are allowed in FI-SL.
To do so, call up the following menu options:
Planning -> Plan versions
The plan version transferred from CO must be assigned to the ledger that is to store the planning data.
Planning -> Version parameters -> Local/global
Here you must maintain the ledger/version/company code/fiscal year assignment accordingly. If you want to write line items when the data is transferred to FI-SL, you must set the appropriate indicator.
If you want line items to be written when the planning data is transferred, you must also perform the following step:
Planning -> Activate line item -> Local/global
Here you can activate the line item update at ledger/version/ company code/fiscal year level.
Afterwards, you must then activate the plan integration in CO.
Cost center acctg -> Planning -> Planning aids -> Plan version ->
LIs and integration
Here you can activate the plan integration for each controlling area/version and fiscal year.
Planning data, direct posting
brbackup (brarchive) does not accept a tape which was previously successfully initialized or used for a backup. Error message: BR214E Label on tape in drive ... not found.
Cause and prerequisitesThe rewind und no-rewind drivers have been mixed up in the tape_address and tape_address_rew init
When a planned order is converted, either the purchase order type
from the planned order or the externally entered purchase order
type is copied to the purchase requisition. No changes to this
procedure are supported in Customizing.
Works as designed.
In displaying master data info types for in structure graphics, the
associated master data info type is not to be entered explicitely in
table T77PC, rather the allocation is carried out implicitely in the
edit routine in report RHSTRU01 (compare e.g., FORM P_GBDAT). The
linking to the superiorily allocated object in the hierarchy is to be
entered always as infotype/subtype per person (object type P).
Program design
When the user presses F4 Help for the entry fields "movement type"
or "special stock", the system displays a dialog box with a list of
all valid combinations of movement types and special stock indicators.
The system automatically uses the selected combination from the list,
overwriting any existing values for movement type or special stock
indicator.
This function has been intentionally designed to work this way since
it makes sense to only use valid combinations that are relevant to
the user.
When working with the transactions CR02 (change work center) or CR01
(create work center) it is not possible to delete an activity
on the 'Cost Center Assignment' screen. Releases prior to 2.2A
Program error
Batch input for customers issues the error message:
'Batch input data for Screen nnnn does not exist'
Error in batch input handling: Data interface is supplied with
input for fields which are not ready for input.
Prenumbered checks are printed using the payment transfer medium program RFFOUS_C. For control purposes and for organizational reasons, the check numbers which are managed in the SAP system should be printed on the form.
This does not function in the way that the user expects.
The fields which ensure that the check numbers appear on the form are only supplied at the start of a check page in Release 2.1. If the list is longer than one page, the incorrect number is printed starting on the second page.
RFFOUS_C, Checkinfo
When sqldba is called, "connect internal" must be entered explicitly.
If the ORACLE upgrade is performed as described in note 11966 or 9982 and the specified directories under $ORACLE_HOME are deleted, the following error can occur during startsap:
DBA302 not connected to a database
"connect internal" missing to start DB.
Program : SAPMUNIT
Error-ID: BM302
When accessing the dimensions maintenance transaction (OMSC,
pushbutton 'Dimensions') you get the error message BM302
'Internal unit X, language Y is not maintained'.
If you confirm this message with ENTER, the error message BM305
'Unit *** is not created in language Y'.
The dimension concerned is highlighted. The field 'SI unit'
contains '***'.
In the dimensions table, an SI unit is specified for the highlighted
dimension that is not defined in the units of measure table.
When the unit is displayed on the screen, a conversion exit is
processed automatically. Processing is terminated because the unit
to be converted does not exist. '***' is displayed.
In the SAPscript editor, Japanese characters are divided by CUT & PASTE.
SAPtemu does not work with Japanese
In the remuneration settlement, wage types are printed for which the amount, the number and the rate equals zero (0). This occurs especially in connection with retroactive accounting differences, for which variable splitting is present.
Syptoms vary. This depends for the most part on corresponding payroll results or on the form definition.
Example (payroll result):
Wage type WPBP split ... Amount For-period In-period
MA10 01 1000,00 01/1995 01/1995
MA10 01 750,00 01/1995 02/1995
MA10 02 250,00 01/1995 02/1995
As per encoding in the T512E (split indicator management) the following output is printed in the remuneration settlement:
MA10 250,00-
MA10 250,00
or
MA10 0,00 (Split indicators were removed)
The wage type has different split indicators on the retroactive
accounting run as opposed to the original payroll.
Errors occur when you print using the SAP standard device types (for printer list, see Note 8928). These errors can be corrected by correcting the device type.
Other termsDevice types, printers
Reason and PrerequisitesThe problem is caused by errors in the R/3 device type.
SolutionGenerally, the SAP original device types should NOT be modified. Instead, copy the originals to a name starting with Z.. (see Note 3166). Then implement the correction (see below) to the copied device type Z... and use the copied device type Z... instead of the SAP original as device type of the output device (under "Output devices" in the Spool Administration transaction SPAD). For example: An error in DECLN07 is described. DECLN07 is then copied to ZDECLN07, the error is corrected in ZDECLN07, and device type ZDECLN07 is used (instead of DECLN07) for output device LP02.
List of discovered errors:
Device type DECLN07 ***********************************************
IMPORTANT: IMPORTANT: The problem described below occurs only when printer type DECLN07 is used for the DEC LN03 printer, rather than for the DECLN07 or the DECLaser 1100 (not supported in the standard system). The DEC LN03 does not know the command that is to be changed.
Incorrect command for setting portrait/landscape format. Effect: In X_65_132, X_44_120, X_58_170, printing is in portrait mode instead of landscape. The error has no effect in X_65_80, X_90_120.
Correction:
Transaction SPAD, "Device formats". In the "Printer initialization" action for X_65_132, X_44_120, and X_58_170, you must correct the following:
Incorrect (for use only in LN07, not for use in LN03):
# Select landscape page format
\0x9B\0x32\0x7A
Correct:
# Select landscape page format
\0x9B\0x37\0x20\0x4A
For the formats X_65_80 and X_90_120, the relevant
command for portrait format must be corrected:
Incorrect (for use only in LN07, not for use in LN03):
# Select portrait page format
\0x9B\0x30\0x7A
Correct:
# Select portrait page format
\0x9B\0x36\0x20\0x4A
Device type HP256X **************************************************
For character set 1126 for HP256X, many characters are missing and/or it has an incorrect Hex code:
287 (Udieresis, Ü) must have the Hex code DB
319 (icircumflex) D1
322 (igrave) D9
284 (Thorn) F0
354 (thorn) F1
267 (Eth) E3
315 (eth) E4
262 (Ccedilla) B4
270 (Iacute) E5
274 (Igrave) E6
Correction:
Transaction SPAD "Character Sets". Call "edit" for character set 1126. Then, for example, look for character number 287: Enter DB instead of EE in field X1. Do the same for the other missing or incorrectly defined characters. Then save the character set.
The device type HP256X must not be copied to Z..... The correction noted above must be corrected after each release upgrade until the correction is part of the program itself in a later release!
Device type HP256X **************************************************
Format X_65_132 is printed with 16.6 cpi, although several printers of the HP256x series can perform the pitch 12 cpi, which is more suitable for this format.
Device type POSTSCPT *************************************************
The line spacing in the format X_58_170 of the POSTSCPT device type is set too large, only approximately 52 lines instead of 58 lines fit on the page.
Correction:
Transaction SPAD, "Device formats". In the action "Printer initialization" for X_58_170, the following lines must be corrected:
Incorrect:
# line spacing
/linesize 9.000 def\n
Correct:
# line spacing
/linesize 7,500 def\n
Device type HPLJIIID *************************************************
Character widths for numbers 0,1,2...9 in the print fonts TIMES 060, 080, 100, 120, 140, 160 (normal, bold, italic and bold italic) are incorrect. The incorrect value 428 or 505 must be replaced with the value 500.
Device type COMPU960 ***********************************
Printing with COURIER 120 normal or COURIER 120 bold may not print with 10 char/inch as required, but with a different pitch. Reason: In the print controls SF001 and SF002, the command sequence for setting 10 char/inch printing is missing.
Correction:
Create a client-specific copy of the affected printer type (for example, ZCOMPU96). For more information, see Note 3166. Do not change the original!! Transaction SPAD, Choose "Print controls for device type," device type ZCOMP.. Define the two print controls SF001 and SF002 as follows:
PrCtl V H D
SF001 1 X 1B501B57021B46
SF002 1 X 1B501B57021B45
Save print controls.
Device type COMPU960 ***********************************
In character set 1119 for COMPU960, many characters for framing lists have incorrect Hex codes:
Character 461 must have hex code 49
471 D1
472 2D
473 2D
474 2D
475 5F
Correction:
Transaction SPAD "Character Sets". Call "edit" for character set 1119. Then, for example, look for character number 461: Enter 49 in Field X1 instead of 7C. Do the same for the other characters. Then save the character set.
Device type COMPU960 must not be copied to Z..... The correction noted above must be corrected after each release upgrade until the correction is part of the program itself in a later release!
Device type KYOF1000, KYOF1200, KYOFS150 *****************************
You cannot change the line spacing with the ABAP command PRINT-CONTROL, since no LIxxx print controls are maintained. We added print controls LI004, LI006, LI008, LI010 for setting 4,6,8 or 10 lines per inch.
Correction:
Create a client-specific copy of the affected printer type (for example, ZKYOF100). For more information, see Note 3166. Do not change the original!! Transaction SPAD, Choose "Print controls for Device type", printer type ZKYOF.. Add the following print controls:
PrCtl V H D
LI004 5 SLPI 4
LI006 5 SLPI 6
LI008 5 SLPI 8
LI010 5 SLPI 10
Save print controls.
Device types MT600, MT600GER, MT600NDA ***************************
These device types were assigned character sets that did not contain OCR-A special characters (hook, fork, chair). All three device types were provided with printer character sets that contain the three special characters:
MT600 - Character set 1122
MT600GER - Character set 1136
MT600NDA - Character set 1120
Device type KYOFS150 *****************************************
The print controls COLxx (COL0N, COL0H, and so on) contain an incorrect command ("Exit,E;") at the end. It is incorrect because it suppresses the line feed when the print control is at the end of a line. In all print controls COL,
EXIT,E;
is replaced with
EXIT;
Device type HPLJ4 **************************************************
Font LNPRINT 085 is printed incorrectly. Instead of font Line printer 8.5 normal, Courier 8 point normal is displayed.
Reason: Printcontrol SF300 is defined incorrectly.
Correction: For all three device types, you can carry out the correction according to the following description:
Create a customer-specific copy of the affected printer (for example, ZHPLJ4). For more information, see Note 3166. Do not change the original! Use Transaction SPAD, "Print control for device type", and choose ZHPLJ4. Now for ZHPLJ4, change the replacement text of print control SF300 to the following values:
1B28304E1B2873307031362E363768382E3576307330623054
Save print controls.
Device type SNIZD13 **************************************************
IMPORTANT: The problem described below occurs only for newer models of ZD13. The version of ZD13 tested by SAP in 1994 did not have this problem.
Incorrect command for deactivating the expanded font. Effect: When you print with SAPscript, the printer "hangs".
Correction:
Transaction SPAD, "Device types", "Formats" for SNIZD13. In the action "Printer initialization" for DINA4, LETTER, INCH12 (all SAPscript formats, see Note 3102) change the following:
Problematic:
# cancel expanded mode
\e\0x5B\0x3B\0x20\0x42
Correct:
# cancel expanded mode
\e\0x5B\0x31\0x30\0x30\0x3B\0x31\0x30\0x30\0x20\0x42
Device type HPLJ5 **************************************************
Activated "PostScript" flag for format X_65_132 leads to incorrect printout of the characters
) ( \
(parentheses and backslash) in ABAP list printing with X_65_132.
Correction:
Transaction SPAD, "Device types", display "Formats" for HPLJ5. The checkbox "Postscript formats" must not be activated in the attributes of format X_65_132 for HPLJ5!
Device type POSTSCPT (POST2) *****************************************
Not all special characters required for character set ISO 8859-1 (Latin-1) are defined in the PostScript encoding vector (character set coding) of the SAP cover page (defined by TITLE action of the format X_PAPER). For this reason, you cannot print a French "eacute" on the cover page. This also affects device type POST2, because it adopts the cover page definition of POSTSCPT.
Device types HP1200, HP2200, HP2550, HP2500, HP3200, HP4100, HP8150, HP9000
Activated "PostScript" flag for format X_65_132 leads to incorrect printout of the characters
) ( \
(parentheses and backslash) in ABAP list printing with X_65_132.
Correction:
Call Transaction SPAD, "Device types", "Formats" for HPxxx. In the attributes for format X_65_132 for HPxxx, the checkbox "Postscript format" must not be activated!
Device type I2HP4
ORA1552 cannot use system rollback segment for non-system tablespace
Cause and prerequisitesa) No additional rollback segment was defined, or
b) The defined rollback segments were not activated (status: offline)
Program : SAPMM06E
In the case of purchase order items with account assignment, there are problems on the account assignment screen SAPLKACB 0002 (for example, it is not possible to move on from this screen).
The problem is caused by a conversion to account assignment block (coding block).
Solution511 113
Key word: BTCI ME21 ME31
A batch input session for creating a WBS with
transaction CJ01 does not work. Reason: field PROJ-PSPID
is not filled.
While field name PROJ-PSPID is displayed for the project
definition field in the request screen under F1 "Technical
info", the actual field name is *PROJ-PSPID.
When you create a customer, the system terminates with
'Insert Error table KNVD' - error message F2802
As a result of an upgrade or a language import, table entries can be
copied in certain cases (only for tables with language
in the key).
When you enter a sales activity, a message is issued once you enter the customer number:
E062: Customer ... has partner function ...
Two possible causes:
1. Either the function AG is not in the partner determination
procedure assigned to the sales activity type, or
2. The partner function AG is not permitted in the account group
assigned to the customer.
Program : RACKONTO
When calling up the consistency check for accounts, the error E303
'Account may not have open item management' occurs for the
account 'Offsetting account acquisition value'
The account is taken during the internal asset posting
transaction. In particular no clearing number is set here.
The account for providing open item management is only necessary
if an asset acquisition is carried out, for example, with the
following steps:
o Invoice receipt : Clearing account at vendor
o Asset acquisition : Asset to clearing account
o Clearing via FI means.
Program : RKEBATCH
Error-ID: KH058
When you print a report using RKCBATCH (CO-BPC) or RKEBATCH (CO-PA), error message KH058 appears repeatedly in the job log.
No print specifications were entered in the job definition. The report is therefore printed on too small a page and consequently cut off.
1. If partial remuneration is to be calculated, days >9 are
are displayed with an asterisk (overflow).
2. The basis of calculation of partial remuneration is not displayed.
Please change the lines marked '<<<----' in
Report RPCBGNA0:
*----------------------------------------------------------------------*
* FORM GET_TE_ANZHL_BETRG *
*----------------------------------------------------------------------*
* Beitragsgrundlage Teilentgelt fuer den Monat ermitteln *
*----------------------------------------------------------------------*
FORM GET_TE_ANZHL_BETRG.
LOOP AT RT WHERE LGART = P/TE_LGA. "BG Teilentgelt bis HBG
*---Alle allgemeine Beitragsgrundlagen lesen
* LOOP AT SPLITTAB WHERE APZNR = RT-APZNR <<<-------
* AND CNTR1 = RT-CNTR1. <<<-------
LOOP AT SPLITTAB WHERE APZNR = RT-APZNR. <<<-------
*---- Zugehoerigen BGN-Split ermitteln
LOOP AT BGN WHERE SPLIT = SPLITTAB-SPLIT.
*------ Zugehoerigen BGN-Satz ermitteln
BGN-TE_ANZHL = BGN-TE_ANZHL + RT-ANZHL.
BGN-TE_BETRG = BGN-TE_BETRG + RT-BETRG.
MODIFY BGN.
*------ Beitragsgrundlage wird gesammelt
ENDLOOP.
ENDLOOP.
ENDLOOP.
ENDFORM.
.
.
.
***********************************************************************
* Personen ausgeben *
***********************************************************************
FORM LISTE.
.
.
.
WRITE: 64 BGN-BEGDA DD/MM/YY,
73 BGN-ENDDA DD/MM/YY,
82 LFD_NUMMER,
88(09) BGN-ALLGB NO-SIGN.
IF BGN-SONDR GT 0.
WRITE: 98(09) BGN-SONDR NO-SIGN.
ELSE.
WRITE: 98(09) ' 999999'.
ENDIF.
* WRITE: 108(04) BGN-TE_ANZHL NO-ZERO, <<<-------
WRITE: 108(04) BGN-TE_ANZHL DECIMALS 0 NO-ZERO, <<<-------
113(09) BGN-TE_BETRG NO-SIGN NO-ZERO,
123 'Mo'.
SKIP.
ENDFORM. "end of LISTE
Program error
Errors occur when you access TemSe objects (spool data, background logs, and so on). The SysLog contains File I/O error (F3V) as follows:
The F3V error xx occurs in the write access or read access to a file.
However, the files appear to exist.
NFS, Global Directory
Reason and PrerequisitesPossible error: the global directory is shared via NFS
in systems with several application servers.
One of the computers may have (temporary) problems with
NFS access.
If a company code also settles for others and an alternative payee
is entered in an account, the message that account KKKKKKKKKK is
not processed because alternative payee is missing might be output
in the log.
The alternative payee is not created in all involved company codes
but, for example, only in the paying company code.
If negative base contribution results from retroactive payroll
accounting (e.g., change of tax office), the contributions are not
correct.
Program error
Facsimile transmission from R/3 via Windows PC with SAPLPD, SAPFAX.DLL, WinFax PRO: when a facsimile message for transmission arrives in SAPLPD on the PC, WinFax PRO opens a pop-up window querying the fax number of the recipient. The field does not contain a suggested value.
Depending on the versions of the programs involved (SAPlpd, SAPfax), the system reacts differently:
Transactions "Manual account statement" and "Check deposit".
When maintaining screen variants, the error F4308 occurs:
SYST: Error in routine SAPMF40xyyyy "CURSOR"
could not be interpreted.
Or:
After a release upgrade, the transactions FF67 and FF68 cancel
with the error F4308
SYST: Error in routine LINE_LAYOUT_GENERATE.
A table "TAB1" was created in the Data Dictionary.
The command
LOOP AT TAB1 CURSOR COUNT.
is processed in the entry screens.
This command is only syntactically correct for internal tables.
However, the ABAP interpreter now assumes that the DDIC table is
meant by "TAB1".
If a company code transfers the old data during the fiscal year,
that is, not at the fiscal year-end, you have the option of
specifying a date up to which depreciation was posted in this
fiscal year.
If the specified date is not a posting period within this fiscal
year, the following error messages can occur:
AC363 Please complete specifications on the posting date of the
depreciation
or
AC365 Incorrect fiscal year specified for the posting date of the
depreciation
Input error
When saving an SD document, the statistics update is terminated with error message "M2012 Error during posting period determination with variant xx", with "xx" being a fiscal year variant.
SIS, M2012, posting period, fiscal year variant
Error in Customizing
ME90: Output of messages (purchasing documents) (RM06ENDR),
ME91: Purchasing documents: reminders and urging purchasing documents (RM06ENMA) and
ME92: Monitor order acknowledgment expediter purchasing documents (RM06ENAB)
have been enhanced as follows for release 3.0A:
A new parameter has been added to the initial screen of the above
transactions ('With message detail function').
This parameter controls the type of read access for the messages to
be processed.
If the parameter is set, the programs are run through as previously.
That is, it is necessary to limit the document numbers, since otherwise
too much will be read. In this case, however, the function "Message
details" is active and the messages can be displayed and changed.
If the parameter is not set, as suggested, the document numbers need
not be limited. In this case, the read accesses are minimized. However,
the function "Message details" is then not active.
This means that the listed purchasing documents can only be outputted:
the associated messages cannot be changed.
In the case of transactions ME91 and ME92, a further parameter has
been added ('Generate and save messages').
If this parameter has been set, the messages (reminders/order
acknowledgement expediters in respect of POs and order acknowledgments)
are generated and saved prior to list output. The list displayed after
this serves the purpose of checking only.
Messages generated in this way can then be outputted with ME90 as
previously.
As the new parameter 'Generate and save messages' has now also been
included in the standard transactions ME91 and ME92, the programs
RM06ENMB and RM06ENAA supplied with Release 2.1 are superfluous and
will be deleted as of Release 3.0A.
The authorization for blocking and deleting an asset master record or an asset class was included under the activity 'Change' instead of being identified separately.
SolutionThis problem is corrected completely in Release 3.0D.
For 3.0A to 3.0C, you must carry out points 1 and 3 of the solution.
As of Release 3.0D and after, these problems can still occur, if you use your own authorizations (which you defined yourself) and have not updated these authorizations accordingly.
You can install the following advance correction: