SAP OSS Notes: 12/19/10

24.12.10

SAP Note 15679 - Termination ASSIGN_OFFSET_NOTINFIELD in SAPMKCBR

Symptom:

Termination ASSIGN_OFFSET_NOTINFIELD in SAPMKCBE/SAPMKCBR during VLINES.

a) Problems with ASSIGN_OFFSET_NOTINFIELD in SAPMKCBR when
printing reports are corrected in Release 21E.

b) In Routine PRINT_TABLEAU (MKCBEF04) termination occurs:
"Error in ASSIGN instruction: Memory protection error
What happened?
The ABAP/4 program now running must be cancelled."

This error occurs only when the following conditions are fulfilled:
1.) It deals with a form report for which the form contains exactly
only line and several columns.
2.) After executing the report, at least one column from the form is
suppressed.

Termination "ASSIGN_OFFSET+LENGTH+TOOLARGE" in SAPMKCBE during ULINE. This abend might occur during printing the columns of a large report.

Additional key words

ASSIGN_OFFSET+LENGTH+TOOLARGE: drill-down reporting; KE30: KCR0; ASSIGN_OFFSET_NOTINFIELD; MKCBEF20

Cause and prerequisites

Program error (the special case noted above was not considered).

Solution

Apply source code corrections as follows.

SAP Note 15675 - Usage of undocumented ORACLE parameters

Symptom:

See solution

Cause and prerequisites

See solution

Solution
USAGE OF UNDOCUMENTED ORACLE PARAMETERS

With good reason, I must once again stress that so-called undocumented
ORACLE parameters are NOT to be used in customer systems.

In particular, this applies to all '_' parameters.

Using these parameters can lead to fatal consequences for the customer.

Example: If a database is used with _disable_logging and the host
crashes during this time (power failure, disk crash, ...),
the database can normally NOT BE RESTARTED!

In this case, the customer must retrieve a backup.

If you forget to disable this parameter and the Archive mode
activates the database, this leads to an 'Archive Stuck.' In
this case, the database can only be exited using 'Shutdown

abort'. If you then try to start the database with
'_disable_logging', the database may allow itself to be
opened. However, there is a much higher probability that an
ORA 600 error occurs which means that the customer must
retrieve a backup anyway.

This parameter can only be used when restructuring a database
(orabuild).

The usage of this parameter is forbidden by ORACLE and if used, the
customer normally receives NO support.

Juergen Kirschner (ORACLE Germany)

Usage of this parameter is also forbidden by SAP (Exception: in
connection with orabuild).

Hans-Georg Oberhauser (SAP)

Additional key words

ORA-600 [2662]

SAP Note 15670 - RPCLGA00 Problems with forms for wage types

Symptom:

The form defined in T512E is not evaluated and printed.

Cause and prerequisites

No complete form definition with RPCLGA00. Only T512E used.

Solution
In 4.3, the definition of wage types in table T512E was sufficient for form output. Very easy forms were able to be done. In R/3, the form driver is used for form creation. This requires a complete definition of a form so that it is output. The advantage is that also more meaningful forms can be created. The disadvantage is that not only the necessary wage types from T512E must be specified, but also a form background (T512P), windows to the form, etc. On the form, values from the RT and from the WPBP can be used. Please check whether or not your form is defined in T512E. Define a form with the necessary items in the form tables.

SAP Note 15669 - Changability of posting date during goods movements

Symptom:

When you enter a goods movement (goods receipt, goods issue, transfer posting), the posting date is recorded. This posting date can then no longer be changed.

Cause and prerequisites

Based on the posting date, the system determines whether the goods movement is to be posted to the current period or the previous period. When goods movements are entered, the stock changes are internally checked and updated internally against the corresponding period fields of the material master. A subsequent change of the posting date would therefore require development of an incredibly complicated (and minimally useful) subroutine.

Solution
When necessary, please cancel the entry transaction (using F12 or F15) and re-enter the goods movement with the appropriate posting date.

SAP Note 15657 - Setting the work center category is not permitted.

Symptom:

If you want to create a work center with transaction CR01, you get the error message CR068 'Setting the work center category is not permitted' although the work center category has been maintained.

Cause and prerequisites

The task list application 'P' of the work center category is missing.

Solution
In Customizing transaction 'OP40' for setting the task list application of a work center category, you have to insert the application 'P' (routings for the production).

SAP Note 15656 - OnArchive: error ARC-E-01341

Symptom:

ARCHIVE from Informix does not work under SOLARIS.
Written archives cannot be reimported, for example customer defined:
VSET/Volume/DBSPACESET and ARCHIVEREQUEST, ARCHIVEREQUEST executed.

->To check: command ondataRTR 'LIST/TAPE=(/dev/rmt/0)'
FM:ARC-E-01342 Save-Set file not found ( INF1342 )
FM:ARC-E-01341 Error while reading PhasesetHDR1 ( INF1341 )

Cause and prerequisites

OnArchive requires a special tape driver under SOLARIS.

Solution
OnArchive only works properly under the SOLARIS operating system when the proper tape driver is used. You should use device driver /dev/rmt/0hb. The proper entry in the OnArchive configuration file config.arc is then:
DEVICE TAPEXY_VOP = /dev/rmt/0hb
If this driver has not been installed yet, use the SOLARIS maintenance tools "drvconfig" and "tapes" to install it.

SAP Note 15655 - Always print payment advice during DME

Symptom:

Customer wants to always print payment advice forms when using RFFOD__U to create DME.

Cause and prerequisites

Customer request

Solution
Option 1:
If you set parameter "Number of additional parts" to 0, only payment advice notices will be issued on the data carrier, and all line item information will be output in separate payment advice notices.
Option 2:
In Customizing for the payment program (layout set data in the method of payment for the company code), set the number of items per form to 0 and select the indicator "Payment advice when form overflows". Now start program RFFOD__U twice: only select DTA the first time, and only payment advice printing the second. In the process, line item information (provided the space for the additional parts is sufficient) is output on the data carrier, and a payment advice notice will be generated for each item.
Comment:
The disadvantage of both options is that the payee receives the information about paid items either only on paper (1) or in duplicate- DME and payment advice (2). This may result in problems interpreting the electronic account statement. We therefore recommend using the program as foreseen in standard: payment advice notices are only output when the space for the additional parts is not sufficient.

SAP Note 15642 - US taxes

Symptom:

Problems handling taxes in USA.
(Keywords: TXJCD, TTXD, TTXJ )

Cause and prerequisites

Handling is somewhat more complicated because a jurisdiction code is also involved.

Solution
We recommend the following procedure:
Until Rel. 2.1: Enter tax indicator "**" as the default value in table T169V.
From Rel. 2.2: Enter tax indicator " " as the default value in table
T169V.

This default value then appears on the vendor screen, and should not be overwritten.
Taxes are then entered for each position. If the tax indicator and jurisdiction code exist, they are copied to the invoice items; they can be changed there. Otherwise, the indicator, jurisdiction code, and (possibly) amount should be entered for each item.

SAP Note 15639 - Removing CARRIAGE RETURNS from device types

Symptom:

A device type is used that works with CARRIAGE RETURN (CR, hex 0D) and NEWLINE (NL, hex 0A). However, you do not want to use CARRIAGE RETURNS.

Cause and prerequisites

Consulting

Solution
You will find information on maintaining device types on the CD Online Documentation (see Note 7363).
You should copy the original SAP device type (for example, ASCIIPRI) (see Note 3166) into the customer namespace (for example, ZASCII).
In Transaction SPAD you find the CARRIAGE RETURNS at the following points:
Print control for device type:
'SLINE' and 'SPAGE' contain CR in hex code: '0D'.

Formats for device type:
Title page of X_PAPER, appearance: '\r'.
End of a page of formats: '\r'
End of a line of formats: '\r'

After removing the CR character save the formats.
Now the print outputs with the copied device type should not contain any more CRs.

Additional key words

SPAD, CR, LF, \r, \n

SAP Note 15632 - Material number despite text item in bid

Symptom:

In a bid, the system demands a material number for a text item (AGTX), although no corresponding entry appears in the incompletion procedure in Customizing.

Cause and prerequisites

While field MATNR is not in the Customizing view of the incompletion procedure, it is present in the underlying table, TVUVF.

Solution
Use transaction SM31 to maintain table TVUVF and delete the entry for MATNR from procedure 27.

SAP Note 15626 - SAPDBA: Invisible password for SAPDBA

Symptom:

Password input for SAPDBA

Other terms

ops$, OS_AUTHENT_PREFIX

Solution
The ORACLE username and password can be transferred to sapdba with the flag "-u username[/password]".
The default is "-u system/manager", that is, in this case the flag can be omitted in the call up.

From Version 3.0C onwards, the entry is invisible. In any case, there are limits to the length of the password (BS-dep. > 8 characters). If a longer password must be used, it can be entered with "-l " but once again transparently. This option is also needed to store a password in a file and have the password transferred via diversion
" -u system < ".

As a thrid solution, the OPS$-User-Mechanism can be used: (see ORACLE Documentation under "OPS$" or SAP Problem Note 8523).
The call would then be:
"sapdba -u / ..." (... for possible additional flags depending
on the purpose)

SAP Note 15622 - Statistical performance figures are not added

Symptom:

Keywords: Report Writer, CO reports
Error message: KB502 - statistical performance figures of different types cannot be added.

Cause and prerequisites

The attempt was made, to add performance figures of different types. The report uses a set for for which an area or interval of individual values has been suppressed by the 'S' flag for the statistical performance figures. These figures in this area have different performance figure types.
Caution: Using a set in the column definition basically suppresses the individual values.

Solution

1. If possible, the set should be used in the definition of the report line and the 'S' flag should no longer be set.

2. The intervals in the statistical performance figures are to be chosen so that they only contain performance figures of one type. The set can then also be used in the column.

Additional key words

.. ----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_MESSAGE, SGRW_DOCU_CONS_NOTE, SGRW_DATAMODEL
SGRW_OM

SAP Note 15608 - Error message GR666 with report for line items

Symptom:

Attempt to define a report that accesses the line item table. When the library for the line item table is defined, error message GR666 is issued: Table not installed in Report Writer.
Transaction: GR21.
Keyword: Report Writer

Cause and prerequisites

Report Writer uses logical views of database tables. Logical tables can contain several physical tables. In extended general ledger (FI-GLX, FI-SL), the name of the logical table is the same as the name of the totals table; however, this logical view also includes the line item tables.

Solution
Please define the library for the logical table - that is, the table name is the same as the name of the totals table. To report on line item data, use the corresponding dataset entries.

Additional key words

----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_LIB, SGRW_MAINTENANCE, SGRW_MESSAGE, SGRW_DOCU_CONS_NOTE, SGRW_LINEITEM
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS

SAP Note 15606 - Overflow of dispatcher request queue

Symptom:

SysLog Q0H (error adding a request to the dispatcher queue).

Reason and Prerequisites

Usual cause: queue defined too small.

Solution
Check the value of profile parameter rdisp/elem_per_queue. If required, increase the value.

If the problem continues to occur: check the SysLog entry to find out which queue type is involved (DIA, VB, ENQ, BTC, SPO) and find the causes why the work processes for these types do not process the requests quickly enough or check why so many requests are generated.

SAP Note 15595 - Availability of BRRESTORE

Symptom:

Entire DB (or individual files) defective

Cause and prerequisites

Database completely or partially restored.
Parallel restore from several tape stations
Restore in different target directories.

Solution
SAPDBA/BRBACKUP uses CPIO to back up DB files. Previously, this had to be done manually with cpio. Starting with R/3 Release 3.0, a new BRRESTORE tool will be shipped, which can be used to restore DB backups created with SAPDBA/BRBACKUP (complete DB, one tablespace at a time, directories, or individual files). In addition, an SAPDBA function for complete or partial restore of the DB is available from 2.2C onwards (see main menu of SAPDBA).

Customer who have an X.25 connection can fetch the BRRESTORE tool (regardless of the customer R/3 version) from sapserv3 via ftp:

ftp sapserv3 (|sapserv3a|sapserv4)
> username: ftp
> password: ftp
> cd dist/permanent/sapdba
> get brrestore.readme.e (description of BRRESTORE,
identical to note no. 14004)
> cd hp (|sni|ibm|sun|dec|nt - depending on operating system)
> bin
> get brrestore.Z
> quit

uncompress brrestore.Z (decompress)
cp brrestore /usr/sap//SYS/exe/run
Set Owner,Group,Permissions as with sapdba,brbackup, e.g.
chmod 755 /usr/sap//SYS/exe/run/brrestore
chgrp sapsys /usr/sap//SYS/exe/run/brrestore
chown c11adm /usr/sap//SYS/exe/run/brrestore
Before you start BRRESTORE, you must enter 3 additional parameters in
profile
$ORACLE_HOME/dbs/init<>.sap (see brrestore.readme.e
cpio_in_flags, uncompress_cmd, tape_pos_cmd or note no. 14004)

Because BRRESTORE will not be officially released until Version 3.0, these 3 new parameters will not be compatible with BRBACKUP and BRARCHIVE until then, and must therefore be deactivated once you exit BRRESTORE.

SAP Note 15581 - Rollup: Optimizing performance when using rules

Symptom:

When using rules in rollup substitutions, runtimes can be relatively slow even though generated rules are used.

Cause and prerequisites

This is because the old Boolean processor is called up (-> a lot of overhead).

Solution

The problem is corrected as of Release 4.0A.
Solution for all 3.x Releases:
You can avoid calling up the old Boolean processor if you only use rules (subrules) in the rollup substitution. In this case, you can call up the FORM routines generated from the rules directly; this will improve runtimes considerably.
Via a control indicator, you can now define whether these FORM routines are to be accessed directly if you are having runtime problems.
In this case, however, you must make sure that ONLY RULES are entered in table T892U (these rules have already been created in system configuration via the menu options Tools -> Rules).
If rules are not used, the old form must still be used with longer runtimes because inevitable errors will otherwise occur.

The following correction in program RGLCRP00 (as of Rel. 3.0F in the described Include programs) is needed
(only add the lines marked with "P21K003284):

Caution: The flag USE_ONLY_RULES at the beginning is important:
USE_ONLY_RULES = 'X' -> only rules can be used in the substitution -> improvement in performance
USE_ONLY_RULES = ' ' -> complex conditions can be used in the substitution (they function as before)

1. Up to 3.0E approx. line 840 in RGLCRP00 (as of 3.0F approx. line 970 in RGLCRTOP)

OFFSET_CODE TYPE I. "Linker Rand im Coding

*Performance-Optimiziation for generated rules "P21K003284
DATA: USE_ONLY_RULES VALUE 'X', "Steuerungsflag!!!! "P21K003284
BOOL_POOL LIKE SY-REPID. "P21K003284

*---------------------------------------------------------------------*
* FORM E01_CREATE_PROCESSOR *
*---------------------------------------------------------------------*

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

2. Up to 3.0E in RGLCRP00 (as of 3.0F in RGLCRP05)

(end of the routine CREATE_E02_INIT_PROCESSOR)

* CYCLE_SET sortieren
SORT CYCLE_SET.

IF NOT USE_ONLY_RULES IS INITIAL. "P21K003284
*Import Structure for bool processor "P21K003284
IF BOOL_POOL IS INITIAL. "P21K003284
PERFORM E01_MAKE_BOOLFORM_FILENAME(SAPFGBBA) "P21K003284
CHANGING BOOL_POOL. "P21K003284
ENDIF. "P21K003284
C = 'PERFORM IMPORT_TABLE($)'. "P21K003284
REPLACE '$' INTO C WITH BOOL_POOL. "P21K003284
PERFORM APPEND_CODE USING: "P21K003284
0 0 C SPACE, "P21K003284
0 0 'USING' SPACE. "P21K003284
C = '''$'''. "P21K003284
REPLACE '$' INTO C WITH HEADER-STABKEY. "P21K003284
PERFORM APPEND_CODE USING 0 0 C SPACE. "P21K003284
C = '$.'. "P21K003284
REPLACE '$' INTO C WITH HEADER-STABKEY. "P21K003284
PERFORM APPEND_CODE USING 0 0 C SPACE. "P21K003284
ENDIF. "P21K003284

PERFORM APPEND_CODE USING -2 0 'ENDFORM.' SPACE.
ENDFORM.

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

3. Up to 3.0E in RGLCRP00 (as of 3.0F in RGLCRP06) ...
IF SUB-CONDITION = SPACE.
*Substitution generieren
PERFORM CREATE_KEY_SUBSTITUTION.
PERFORM APPEND_CODE USING 0 0 C SPACE.
PERFORM APPEND_CODE USING:
0 0 'EXIT.' SPACE.
EXIT.
ELSE.
*Regel eingegeben
IF USE_ONLY_RULES IS INITIAL. "P21K003284
PERFORM APPEND_CODE USING 0 0:
'PERFORM E05_NEW_SEGMENTS(SAPFGBO0).' SPACE,
'PERFORM E03_EVALUATE_FORMULA_STRING(SAPFGBO0) USING' SPACE
* Apostrophe in Formeln verdoppeln
C = ''''.
C+1 = SUB-CONDITION.
CLEAR SY-SUBRC.
WHILE SY-SUBRC = 0.
REPLACE '''' INTO C+1 WITH '!'.
ENDWHILE.
CLEAR SY-SUBRC.
WHILE SY-SUBRC = 0.
REPLACE '!' INTO C+1 WITH ''''''.
ENDWHILE.
C+78 = ''''.
CONDENSE C.
PERFORM APPEND_CODE USING 12 -12 C SPACE.
C = 'SY-CTYPE ''$'' ''$'' '''' ''''.'.
REPLACE '$' INTO C WITH .
IF HEADER-STABKEY = HEADER-STABDAT.
REPLACE '$' WITH SPACE INTO C.
ELSE.
REPLACE '$' WITH INTO C.
ENDIF.

PERFORM APPEND_CODE USING: 12 -12 C SPACE,
0 2 'IF SY-CTYPE = ''T''.' SPACE
*Use only rules in table T892U "P21K003284
ELSE. "P21K003284
IF BOOL_POOL IS INITIAL. "P21K003284
PERFORM E01_MAKE_BOOLFORM_FILENAME(SAPFGBBA)"P21K003284
CHANGING BOOL_POOL. "P21K003284
ENDIF. "P21K003284
C = 'PERFORM E17_SUBRULE_CALL($)'. "P21K003284
REPLACE '$' WITH BOOL_POOL INTO C. "P21K003284
PERFORM APPEND_CODE USING: 0 0 C SPACE, "P21K003284
0 0 'USING' SPACE. "P21K003284
SHIFT SUB-CONDITION UP TO '&'. "P21K003284
SHIFT SUB-CONDITION. "P21K003284
C = '''$'''. "P21K003284
REPLACE '$' WITH SUB-CONDITION INTO C. "P21K003284
PERFORM APPEND_CODE USING: "P21K003284
0 0 C SPACE, "P21K003284
0 0 '''RL''' SPACE, "P21K003284
0 0 'CHANGING' SPACE, "P21K003284
0 0 'SY-CTYPE.' SPACE, "P21K003284
0 2 'IF SY-CTYPE = ''T''.' SPACE. "P21K003284
ENDIF. "P21K003284

PERFORM CREATE_KEY_SUBSTITUTION.

*************************End of the correction*************************

Additional key words

Rollup, T892U

SAP Note 15569 - Double-click on message number

Symptom:

Call transaction SE38 and change a program. Double-click on a message number leads to a dialog box where you have to enter the message class although the message class is defined for the program. () EUNOTE message

Cause and prerequisites

The index of the corresponding program is not current.

Solution
You must use the "Update index" function in the "Utilities" menu to update the index of the program.

SAP Note 15564 - GR850: No authorization for selected data

Symptom:

Key word: REPORTWRITER, CO reports
When outputting a CO report, message GR850 appears: 'You do not have authorization to display the selected data'.

Cause and prerequisites

Possibly the authorization for authorization object K_REPO_CCA 'CO: Reporting on cost centers / cost elements' is too restrictive.

In the Report Writer, an authorization check is run at two different times:

- The first check is made with activity 27 (display totals record)
or 28 (display line item) during database selection for records.
Each database record for which the user does not have authorizations
for the activities above is not processed. Here the system validates
the characteristics of the fields Cost element, Controlling area,
and Cost center.

- The second check is made with activity 29 (display stored data)
before the edited list is displayed.
At this time an authorization check for records and therefore for
single values is not possible. The system validates the sets
used in the report for cost element, controlling area, and cost
center:
If a set only contains a single value or if a representative value
has been maintained for the set, the user must have authorization
for this value. In all other cases the user must have authorization
for all values.
If separate authorizations have not been assigned to activities 27
and 29, the error message outlined above can occur.

Solution

Also see Note 15211.

The following alternatives are available when setting up authorizations for the authorization object K_REPO_CCA

1. The user displaying the report also selects the data:

The authorization check can be made at the time of selection.
The user's authorization should be limited to activity 27 (display
totals records) and 28 (display line items). As far as activity 29
(display stored data) is concerned, the user should be authorized
for all cost centers and cost elements.

Example:

The cost center report 1SIP (actual/plan/variance) is run for a
single cost center. The user selects the data and displays the
report onscreen.
The user should only have authorization to display data for cost
center 1000 in controlling area 0001.

The user has limited authorization for selection:

Activity: 27, 28 totals recs + line items
Cost element * all
Controlling area : 0001
Cost center : 1000 only cost center 1000

The user has all authorizations to display the stored data:

Activity : 29 Display stored data
Cost element: * all
Controlling area: * all
Cost center: * all

Here all authorizations are checked at the time of selection so
restricting the authorization for report display is not necessary.

2. The user only accesses the stored data selected by a super user.
This can be useful if a selection has been run in the background
for all cost centers in a hierarchy and the selected data is stored
in a data extract.
The user only has access to the data extract and should only be
allowed to display reports on certain cost centers.
Here the authorization check cannot be made at the time of
selection.

Example:

A super user runs cost center report 1SIP (actual/plan/variance)
for the entire standard hierarchy of controlling area 0001.
The cost center hierarchy is varied over the entire hierarchy
area and the result is stored in a data extract. A report is
generated for each cost center and each cost center group in the
data extract.
A user is only to be permitted to access the data extract and only
be authorized to display the report for cost center 1000.

The super user has all authorizations for selection:

Activity: 27, 28 tot.records + line items
Cost element: * all
Controlling area: * all
Cost center: * all

The user is only authorized to display the stored data:

Activity: 29 display stored data
Cost element: * all
Controlling area: 0001 all
Cost center: 1000 only cost center 1000

If the user is to be authorized to display a report for a cost center
group, a representative cost center must be assigned to the cost
center group (hierarchy maintenance: report info, representative
value) and the user must have authorization for this representative
cost center.

Details about activity 29:

When the report is output, it is not possible to determine which
database records were actually used in the report. An authorization
check is therefore run for the cost center group/cost element group
used in the report. If the group contains more than one cost center/
cost element and if no representative value is assigned to the group,
the user must have authorization for all cost centers/cost elements.

If a group is used to define the row structure and the user is
authorized to display the group, the group total and all report
rows in the group total are shown.

You can find further information on authorization checks in Note 15211 'Standard reports: authorization concept' and the release note 'Report Writer: Authorization check for stored data' for release 2.1A

Additional key words

----- SUPPORTGUIDE 20010208103353 -----
REPORTWRITER, SGRW_AUTHORITY, SGRW_DOCU_CONS_NOTE
SGRW_OM

SAP Note 15549 - Maintaining exception table DBCHK

Symptom:

Caution: this note applies, depending on the database system,
only up to the following release statuses (including):
ORACLE: till Rel. 3.0A
INFORMIX: till Rel. 3.0C
ADABAS: till Rel. 3.0D
DB2 for AIX: till Rel. 3.0F
others: till Rel. 3.0B
Please consult note 33814 for newer release statuses.
Keyword: Maintain DBCHK, DB02, ST04, Alert Monitor
In transaction DB02, tables or indexes are displayed as missing in the database or in the ABAP/4 Dictionary.

Please also see the comment at the end of this note.

Cause and prerequisites

Incorrect entries in table DBCHK due to upgrades and renaming.
Exceptions are documented in table DBCHK.
The problem is caused by tables/indexes which due to technical reasons can or could not be created in the ABAP/4 Dictionary.

Solution

Typical candidates for apparently missing indexes are the Dictionary/
kernel tables, such as DD03L, DD04L, DD08L, D300T, D301T, D010TINF, D010INC, D010TAB. These are SAP kernel tables that should not exist in the SAP DDIC because they should not be manipulated. The correct table entries are listed individually below.

The following is an explanation of DBCHK entries:

Entry for index name with CHECKTYPE=7:
Even if an index is not described in the SAP-DDIC, it MUST
exist on the database. If index is not found in the database,
the Alert Monitor issues an error message.

Entry for table name with CHECKTYPE=5:
Table has no index on the database.
Such tables are either non-SAP tables that the SAP software must
access (e.g. the ORACLE $-tables), or SAP tables with only a single
entry for which an index would be a waste of space.

Entry for index name with CHECKTYPE=4:
This means that no corresponding entry is required in the SAP DDIC if
an index is found on the database. It does NOT mean, however, that
the index must exist on the database (see CHECKTYPE=7).
Note: Indexes which have to exist in the database but which are not
defined in the SAP DDIC should be entered with CHECKTYPE=7 and with
CHECKTYPE=4 (see CHECKTYPE=7).

Entry for table name with CHECKTYPE=3:
This means that table can have a primary index that does not
correspond to the SAP standard name. These are normally tables
that are created outside the R/3 system and therefore do not
conform to the SAP naming conventions.

Entry for table name with CHECKTYPE=2:
This means that these tables do not have to be present and active in
R/3. However, this value does not define that the table must be
present in the databank.
Table LICHECK belongs to this category.

Entry for table name with CHECKTYPE=1:
Table exists in the DDIC, but not in the database.
Caution: It should only be maintained if there is an error.
One well-known case is the matchcode pools M_DEBI, M_SAKO, M_MAT1,
M_MAT2, M_KRED, which no longer exist as of 2.2 because of the
transparent matchcodes. Because of an error in the Alert Monitor, the
indexes of the tables are displayed as incorrect although the tables
in the database have disappeared. In this case the matchcode pools
can be entered in the DBCHK.
The pools should be created in all other cases. The monitor
error in the display should be corrected as of version 2.2D.

All the table and index names marked with <-3 shouldexist for Release
3.0A. The superfluous entries must be deleted for CHECKTYPE 7.

The following entries with CHECKTYPE = 2 should exist in the SAP
table DBCHK:
CHECKTYPE TABORINDEXNAME | CHECKTYPE TABORINDEXNAME
2 ARCH_HIST <-3 | 2 STATS$FILESTATS
2 ARCH_JOB <-3 | 2 STATS$LATCHES
2 CEP02 <-3 | 2 STATS$LIBRARYCACHES
2 D010L | 2 STATS$LOCKACTIVITY
2 D010LINF | 2 STATS$LOCKWAITS
2 D010Q | 2 STATS$LRUSTATS
2 D010S | 2 STATS$PARAMETER
2 D010SINF | 2 STATS$ROLLSTATS
2 D010T | 2 STATS$ROWCACHES
2 D010TAB | 2 STATS$SEQUENCES
2 D010TINF | 2 STATS$SGA
2 D010Y | 2 STATS$SGASTATS
2 D020LINF | 2 STATS$SGASTATXS
2 D020SINF | 2 STATS$SNAPSHOTS
2 D021LINF | 2 STATS$STATNAMES
2 D021S <-3 | 2 STATS$SYSSTATS
2 D022S <-3 |
2 DDLOG <-3 | 2 STATS$WAISTATS
2 DDNTF <-3 | 2 STATS$WAITSTATS
2 DDNTT <-3 | 2 TSA_COL_HIST <-3
2 FLAGS_TEXT_R3 <-3 | 2 TSA_COL_STATS <-3
2 FTMAC <-3 | 2 TSA_ROW_HIST <-3
2 INSCHK <-3 | 2 TSA_ROW_STATS <-3
2 LICHECK <-3 | 2 UH <-3
2 OCCUI <-3 | 2 VBDATA <-3
2 OCCUT <-3 | 2 SDBAS <-3
2 ONSTATOPT <-3 | 2 SAPUSER <-3
2 ONSTATOUTC <-3 |

The following entries with CHECKTYPE = 3 should exist in the SAP
table DBCHK:
3 DD03L <-3 | 3 STATS$SGASTATXS
3 DD03L__0 | 3 SVERS <-3
3 STATS$FILESTATS | 3 SVERS__0
3 STATS$ROWCACHES | 3 Y0064 <-3
3 STATS$SGASTATS |

The following entries with CHECKTYPE = 4 should exist in the SAP
table DBCHK:
4 ARCH_HIST0 <-3 | 4 DD03L__1
4 ARCH_HIST1 <-3 | 4 DD03L__2
4 ARCH_JOB0 <-3 | 4 DD03L__3
4 D010INC1 | 4 DD03L__4
4 D010LINF_0 | 4 DD03L__5
4 D010S | 4 DD03L__6
4 D010SINF1 | 4 DD04L__1
4 D010SINF_0 | 4 DD08L__1
4 D010S__1 | 4 DDNTF__1 <-3
4 D010TAB1 | 4 DDNTT__0 <-3
4 D010TINF0 | 4 FLAGS_TEXT_R3_IX1 <-3
4 D010T__0 | 4 STATS$LATCHES_PK
4 D020LINF0 | 4 STATS$LIBRARYCACHES_PK
4 D020LINF_0 | 4 STATS$LOCKACTIVITY_PK
4 D020SINF0 | 4 STATS$LRUSTATS_PK
4 D020SINF_0 | 4 STATS$ROLLSTATS_PK
4 D021LINF0 | 4 STATS$SNAPSHOTS_PK
4 D021LINF_0 | 4 STATS$SYSSTATS_PK
4 D300T__1 <-3 | 4 STATS$WAITSTATS_PK
4 D301T__1 <-3 | 4 STATS$SYSSTATS_PRIME
4 DD01L__1 | 4 DDSTAMP1 <-3
4 DD02L__1 | 4 SNAP___S <-3
| 4 SNAP___D <-3

The following entries with CHECKTYPE = 5 should exist in the SAP
table DBCHK:
5 FTMAC <-3 | 5 STATS$SGASTATS
5 OCCUI <-3 | 5 STATS$SGASTATXS
5 OCCUT <-3 | 5 SVERS <-3
5 ONSTATOPT <-3 | 5 TSA_COL_HIST <-3
5 ONSTATOUTC <-3 | 5 TSA_COL_STATS <-3
5 STATS$FILESTATS | 5 TSA_ROW_HIST <-3
5 STATS$PARAMETER | 5 TSA_ROW_STATS <-3
5 STATS$ROWCACHES | 5 UH <-3
5 STATS$SGA |

No entries in CHECKTYPE = 6 for SAP.
The following entries with CHECKTYPE = 7 should exist in the SAP
table DBCHK:
7 D010INC1 | 7 DD03L__1
7 D010LINF_0 | 7 DD03L__2
7 D010S__1 | 7 DD03L__3
7 D010TAB1 | 7 DD03L__4
7 D010TINF0 | 7 DD03L__6
7 D010T__0 | 7 DD04L__1
7 D020LINF_0 | 7 DD08L__1
7 D020SINF_0 | 7 DDNTF__0 <-3
7 DD01L__1 | 7 DDNTT__0 <-3
7 DD02L__1 |

If R/3 runs on INFORMIX, the following entries should also
exist:
The following entries with CHECKTYPE = 4 should exist in the SAP
table DBCHK:
4 VBLOG__1

The following entries with CHECKTYPE = 7 should exist in the SAP
table DBCHK:
7 VBLOG__1

Note:
Please note that the new or changed entries only take full effect after the next run of the COLLECTOR_FOR_PERFORMANCEMONITOR job. Only this job fully recalculates the statistics that are shown in DB02. The function REFRESH here, only recalculates some of the statistics. It is quite possible that missing indices are still displayed after a REFRESH in DB02. In the named job, the program RSORATDB is executed. This generally occurs 3 times a day. This procedure is controlled by the table TCOLL.

Additional key words

Maintain DBCHK, DB02, ST04, Alert Monitor
Examples: SDBAS, LICHECK

SAP Note 15533 - Differences between RAGITT01 and RFBILA00

Symptom:

If you call RAGITT during the fiscal year, the depreciation may not agree with the general ledger, although the correct report date was used for delimitation.
This error can only occur when distribution of the declining balance is used for depreciation posting with RABUCH00.

Cause and prerequisites

RAGITT01 uses depreciation for past periods in a lump sum.

Solution
RAGITT01 or RAGITT_ALV01

SAP Note 15509 - Change documents: changes to bank data

Symptom:

SAPMF01A MF01ADEB FD04 XD04 VD04 KNBK LFBK MF01AKRD
Changes to bank data do not appear in the list of change fields, but instead only when the functions "Entries" or "Deletions" are called. This is because changing a bank account number actually means deleting one set of bank data and entering a new set.
The same applies to all data entered in LOOP screens, e.g. for dunning data, unloading points, etc.

Cause and prerequisites

See Symptom

Solution
See Symptom

SAP Note 15505 - Taking over selected reservations

Symptom:

If a material for a reservation list (RM07RMAT) was generated using transaction MB1A (enter goods receipt), and all reservations were selected and taken over, then reservations that were not in the basic list were also taken over. Affects reservations for movement type 521, for example.

Cause and prerequisites

All reservations were placed in an internal table and taken over in unfiltered form.

Solution
REPORT RM07RMAT MESSAGE-ID M7 NO STANDARD PAGE HEADING LINE-SIZE 126.

*---- Include-Reports -------------------------------------------------*
INCLUDE: MM07MABC,
RM07MSEL,
RM07MSQL,
.
.
.
*---------------------------------------------------------------------*
* FORM AUSGABE_YRSEG
*---------------------------------------------------------------------*
* Formroutine, die die selektierten Belegpositionen sortiert
* und aufbereitet ausgibt.
*---------------------------------------------------------------------*
FORM AUSGABE_YRSEG.
SORT YRSEG BY MATNR WERKS BDTER.
LOOP AT YRSEG.
IF NOT XCALL IS INITIAL AND NOT XCALL = A.
SELECT SINGLE * FROM T158B WHERE TCODE = SY-TCODE
AND BWART = YRSEG-BWART.
IF SY-SUBRC IS INITIAL.
PERFORM YRSEG_SCHREIBEN.
*---- New coding: please insert -------------------*
ELSE.
DELETE YRSEG. "Reservierungen nicht erlaubt.
*---- End of new coding ---------------------------*
ENDIF.
ELSE.
PERFORM YRSEG_SCHREIBEN.
ENDIF.
ENDLOOP.
PERFORM CLOSE_GRID.
ENDFORM.

SAP Note 15504 - HR-TRV: authorization for trip costs accounting

Symptom:

Trip costs accounting with RPRTEC00 terminates since the master data authorization for infotype P0008 (basic pay) does not exist. The administrator is not able to receive authorization either.
Similar problems may occur with RPRTEF00.

Cause and prerequisites

Program RPRTEC00 reads infotype P0008, since this infotype can be used in the feature TRVCT.

Solution
You can deactivate the authorization check of the master data for program RPRTEC00 by creating an authorization with the specification
RPRTEC00 *
for the authorization object
HR: Reporting (P_ABAP)
and allocating it to the administrator.

If necessary, this can also be performed for RPRTEF00.

Remark: The authorization check of the master data is in no way
connected to the authorization check of the trip data.

SAP Note 15462 - The cost in the billing document is '0'

Symptom:

When you create a billing document, the cost is displayed as "0" even though a value is specified in the order.
The correct cost appears after pricing is carried out again.

Reason and Prerequisites

Prerequisites:

The billing is delivery-related.

Two or more costs have been defined in the pricing procedure.

Reason:
For technical reasons, after determining the first cost, the system resets the value from the goods issue document to "0" so that the subsequent costs are also assigned the value "0".
When pricing is carried out again, the cost is transferred from the material valuation segment.

Solution

In the standard system, only one condition type is provided for the costs for each item (condition category "G").
Set up your pricing procedure in such a way that only one cost occurs.

Other solutions are only possible through modifications. For more information, contact your SAP consultant. See also the attached Note 170183.

One possible solution is as follows:

Use transaction VOFM to create a new condition value formula, (for example, 900).
Take the attached solution proposal into account.

Enter this condition value formula in the pricing procedure in the second cost condition.

In the pricing procedure for the first cost condition, "B" is assigned to the condition subtotal (value transfer to KOMP-WAVWR).
(As a result, the value from the goods issue (field KOMP-WAVWR) is not reset after the first cost is determined.

Other terms

VPRS, WAVWR, KNTYP, KZWI
Cost, costs, duplicate

SAP Note 15461 - Delivery and invoice split due to credit currency

Symptom:

When creating invoices with VF01 and VF04, an invoice split occurs because the credit currency in the order has been filled although the payer has no credit master data.
The same applies to the collective processing of deliveries.

Cause and prerequisites

Program error

Solution
The following correction prevents the credit currency from being copied into the sales order if credit management is not active.
In order to avoid that incorrect documents result in a split, data transfer for header data in the delivery and billing document must be adjusted.
Preliminary correction in program FV45KFAK:
...
FORM VBAK_FUELLEN_KURGV.
LOCAL: VBAK-KUNNR.

CHECK KURGV-KUNNR NE SPACE.
MOVE-CORRESPONDING KURGV TO VBAK.
IF NOT VBAK-KKBER IS INITIAL. <<<< insert
MOVE KURGV-WAERS TO VBAK-CMWAE.
ENDIF. <<<< insert
ENDFORM.
*eject

Generate SAPFV45K.

Data transfer of header data in delivery:
e.g.: FV50C001 or the active data transfer routine (TVCPL)
FORM DATEN_KOPIEREN_001.
.
.
.
IF NOT CVBAK-KKBER IS INITIAL. <<<< insert
MOVE CVBAK-KKBER TO LIKP-KKBER.
MOVE CVBAK-KNKLI TO LIKP-KNKLI.
MOVE CVBAK-KKBER TO LIKP-KKBER.
MOVE CVBAK-GRUPP TO LIKP-GRUPP.
MOVE CVBAK-SBGRP TO LIKP-SBGRP.
MOVE CVBAK-CMWAE TO LIKP-CMWAE.
MOVE CVBAK-CTLPC TO LIKP-CTLPC.
ENDIF. <<<< insert
.
.
.

Additional key words

VL04, delivery split, order combination

SAP Note 15456 - Availability control without mail for action 2

Symptom:

Availability control with action 2 "Mail to project manager" does not send a mail.
An error message may appear instead of a warning.
When you try to save, a warning is displayed, which is correct. This warning is issued each time you try to save, so that you get the impression that you cannot just ignore it.

Cause and prerequisites

You must distinguish between three cases:

1. An error message appears

2. A warning message appears

3. No message appears

4. The warning message reappears each time you try to save

3. Availability control is not active or the tolerances have not been exceeded.

Solution

1. Maintain the project manager via the master data maintenance function

2. Maintain the Office user of the manager in Customizing (Transaction OPS6)

3. Activate availability control or adjust the tolerances accordingly. 4. Please confirm the warning message with ENTER or with the Enter button in order to save.

Additional key words

Project, order, budget, posting, purchase order, CJBV, OPSC, BP601, BP602, BP603, BP604, BP605, BP606, BP607, BP608, BP611, BP612, BP613, BP614

SAP Note 15454 - Syntax error in SAPLGLIN

Symptom:

Syntax error in program SAPLGLIN, Include LGLINF90

Cause and prerequisites

Incorrect entries in table T800A

Solution
See Cause and Solution sections in note nos. 8673 and 9142.
If you need to send the problem to the SAP Hotline, use transaction GCI3 to print a standard list of the FI-GLX table directory and send the list (specifying your problem number) per fax to the SAP Hotline.

SAP Note 15451 - RAALTD01: subnumbers assigned incorrectly

Symptom:

When creating subnumbers using batch input, subnumbers are assigned to the wrong asset main numbers. The error only occurs in connection with internal main number assignment.
Keywords: RAALTD01 AS91 AS94

Cause and prerequisites

The error can only occur when the main number for the subnumber could not be created because an error occurred.

Solution
The error in the asset main number for the subnumber should be corrected in the input file of batch input program RAALTD01. When the corresponding main number is created correctly, the error will no longer occur.

Error corrected in Rel. 2.2C.
Advance correction: change program RAALTD01 as follows:
:
* Merker: Batch-Input-Mappe eroeffnet.
DATA: FLG_BDC_OPEN(1) TYPE C, <<< change
* AS94-Skip, d.h. bei Fehler in AS91 <<< insert
* folgende Unt.nrern überspringen <<< insert
FLG_AS94_SK(1) TYPE C. <<< insert
:
FORM AS94_FEHLER_ERMITTELN USING L_SUBRC.

DATA:
* Zwischenspeicher für Feldinhalte.
L_CHAR_VALUE LIKE BDCDATA-FVAL,
* Aktueller Suffix.
L_AKT_SUFFIX(2) TYPE C,
* Aktueller AfA-Bereich.
L_AKT_AFABE LIKE ANKB-AFABE.
* Default: Keine Fehler festgestellt.
L_SUBRC = 0.
" Hauptnummer kann hier nicht gefüllt sein, da erst später per Set-/get-
" besorgt.
* Hauptnummer nicht gesetzt.
* IF BALTD-ANLN1(1) EQ '/'.
* IF L_SUBRC EQ 0.
* SY-MSGTY = 'E'.
* SY-MSGID = 'AU'.
* SY-MSGNO = '033'.
* SY-MSGV1 = SPACE.
* SY-MSGV2 = SPACE.
* SY-MSGV3 = SPACE.
* SY-MSGV4 = SPACE.
* PERFORM FEHLER_MERKEN.
* L_SUBRC = 4.
* EXIT.
* ENDIF.
* ENDIF.

* Nachfolgende AS94-Sätze überspringen, <<< insert
* wenn AS91 vorher schief ging. <<< insert
IF FLG_AS94_SK = 'X'. <<< insert
IF L_SUBRC EQ 0. <<< insert
SY-MSGTY = 'E'. SY-MSGID = 'AU'. SY-MSGNO = '255'. <<< insert
SY-MSGV1 = BALTD-ANLN2. SY-MSGV2 = BALTD-OLDN1. <<< insert
SY-MSGV3 = SPACE. SY-MSGV4 = SPACE. <<< insert
PERFORM FEHLER_MERKEN. <<< insert
L_SUBRC = 4. <<< insert
EXIT. <<< insert
ENDIF. <<< insert
ENDIF. <<< insert
:
ENDFORM.

FORM AS91_ERZEUGEN.

DATA: L_SUBRC LIKE SY-SUBRC.

L_SUBRC = 0.
* Zuerst Formalfehler checken ...
CASE BALTD-TCODE.
WHEN 'AS91'.
* Skippen von AS94-Sätzen wieder ausschalten. <<< insert
FLG_AS94_SK = ' '. <<< insert
PERFORM AS91_FEHLER_ERMITTELN USING L_SUBRC.
WHEN 'AS92'.
PERFORM AS92_FEHLER_ERMITTELN USING L_SUBRC.
WHEN 'AS94'.
PERFORM AS94_FEHLER_ERMITTELN USING L_SUBRC.
ENDCASE.
* Fehler ...
IF L_SUBRC NE 0.
* ... dann Fehler-Counter hochsetzen.
XSTAT-ERCNT = XSTAT-ERCNT + 1.
* ... bei fehlerhaftem AS91 sollen alle nachfolgenden <<< insert
* AS94-Sätze übersprungen werden. <<< insert
IF BALTD-TCODE = 'AS91'. <<< insert
FLG_AS94_SK = 'X'. <<< insert
ENDIF. <<< insert
ENDIF.
:

* Interne Hauptnummernvergabe ==> Hauptnummer erst besorgen.
IF NRIV-EXTERNIND IS INITIAL AND
( BALTD-TCODE EQ 'AS92' OR
BALTD-TCODE EQ 'AS94' ) .
* Bei AS92: Wird Hauptnummer bereits mitgegeben?
IF ( BALTD-ANLN1(1) = '/' OR <<< change
BALTD-ANLN1(1) IS INITIAL ) AND <<< change
FLG_AS94_SK = ' '. <<< insert
GET PARAMETER ID 'AN1' FIELD BALTD-ANLN1.
ENDIF.
ENDIF.
* Interne Unternummernvergabe ==> Unternummer erst besorgen.
IF ANKA-XUNTV IS INITIAL AND
BALTD-TCODE EQ 'AS92' .
GET PARAMETER ID 'AN2' FIELD BALTD-ANLN2.
ENDIF.
:

* Fehlerfreie Transaktion oder kein echter Fehler.
IF SY-SUBRC EQ 0. ""OR
** ( SY-MSGID EQ '00' AND
** SY-MSGNO EQ '344' ) .
IF XTEST EQ SPACE.
* Update-Counter hochsetzen.
XSTAT-UPCNT = XSTAT-UPCNT + 1.
ENDIF.
* Fehlerhafte Transaktion.
ELSE.
* ... bei fehlerhaftem AS91 sollen alle nachfolgenden <<< insert
* AS94-Sätze übersprungen werden. <<< insert
IF BALTD-TCODE = 'AS91'. <<< insert
FLG_AS94_SK = 'X'. <<< insert
ENDIF. <<< insert
* Echtlauf.
IF XTEST EQ SPACE.
* Eventuell Batch-Input erst mal eroeffnen.
IF FLG_BDC_OPEN = ' '.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING CLIENT = SY-MANDT
USER = SY-UNAME
GROUP = MAPPE.
:
ENDFORM.

In addition, use the "Maintain message class" transaction (SE91) to define the following message:
1. Specify message class "AU"
2. Subobjects: "Messages" -> Change
3. Enter message number 255 and "Single entry" 4. Text: Subnumber & for old asset & could not be created.
When you process the batch input session that contains all the faulty records, observe the following:
1. When you correct the erroneous asset main number (AS91), you
will have to note the asset main number that the system assigns.
2. This asset main number must be entered manually on the first screen
when the subnumbers are created (AS94).

SAP Note 15447 - Error in navigation / inconsistent object list

Symptom:
Workbench:
1. An object is not found when you navigate by double-clicking the
mouse, or the system asks whether you want to create the object,
although it already exists.
2. Double-clicking on a program object causes message "Main program
for include ... not found" (MSG EU127) to be issued
3. The object list of a program (or function group) is inconsistent.
That is, entries are missing or some entries are doubled.
4. Displaying the program object list or double-clicking on a
program object causes an endless loop.
() EUNOTE, EUNAVIGATION, EUWORKBENCH Additional key words
Cause and prerequisites

Error in the program index (of the main program)

Solution
You can reconstruct the program index (for the main program) at any time.
Option 1: Transaction SE80 (Workbench) -> Program -> Generate
(or object list Program -> Update). This option is
available in Release 2.1A and later.
For error case 4 (endless loop), a problem exists if
a user has set the critical program as an entry point
in the Workbench.
In this case, the initial screen of the Workbench will
never appear, and you cannot generate the index as a
result. The colleague who set the program as a entry point
should be able to help you in this case.

Option 2: Load the main program into the program editor and update
the index.
This option is available in Release 2.1I/2.2C and later.

If, once you have carried out the above actions, the error situation still occurs, this means that the syntax error in the program is so serious that the system is not capable of analyzing it. This usually involves a literal error in which the single quote (') at the end of the literal is missing. Once you correct the syntax error, you can reconstruct the program index.

SAP Note 15446 - CMOD: Function exit is not active

Symptom:

An enhancement project (transaction CMOD) is created and activated, however, the activation has no effect (at least not for all components of the enhancement project).

Cause and prerequisites

1. The function group containing the customer coding was not regenerated.

Solution
Regenerate the function group (that is, program SAPLXaaa), or regenerate the SAP programs belonging to the enhancement project.
Note 12831 contains a check report which lists all inactive function modules in active projects or all active function modules in inactive projects.

SAP Note 15440 - FZ095

Symptom:

When creating payment carriers (e.g. with RFFOCH_U), error message FZ095 is issued: "Entry ... missing in table T042E"; the company code and method of payment " " is specified as the key.

Cause and prerequisites

A zero balance clearing takes place in the payment run, and an entry with method of payment " " appears in REGUH as a result.
The user, however, forgot to exclude this case from the print program variant.

Solution
Create the variant for the print program in such a way that the character " " cannot be selected as a possible method of payment.

SAP Note 15437 - Sales activity type 0101: Text is incorrect

Symptom:

The text for sales activity type 0101 is incorrect. It says 'telephone call'. It should be 'Direct mailing campaign'.

Cause and prerequisites

unknown

Solution
Correction in 3.0 or before: Change the text for the sales activity type in Customizing.

SAP Note 15430 - Translating units of measure

Symptom:

Units of measure cannot currently be translated from the maintenance transaction for units of measure (OMSC).

Other terms

CUNI

Solution

To translate the UoMs into an installed system language, we recommend the following procedure:

Log on in both the source language and the target language.

Call the transaction for maintaining units of measure in the target language (Transaction CUNI). In the field to the right of pushbutton "Units of measure, select the dimension to maintain using F4 and press the "Units of measure" pushbutton.

Do the same for the source language (only display is possible, as the data is already being maintained in the target language).

You can now maintain the language-specific entries in the target language, using the display of the source language as a reference.

This procedure guarantees data consistency.

If this procedure is not possible because the target language has not been installed, then you have to use the translation tool to perform the translation. Proceed as follows:

Use Transaction SM31 to check whether the keys of the languages to be used are maintained in Table TSKT9. If this is not the case, maintain the table using Transaction SM31.

Call the translation tool (Transaction CUNI, Go to -> Translation -> Units of measure).

Enter the language keys of the required source and target languages and confirm. You can now translate both the language-specific keys (business and technical display of the UoM) and the short texts. Please note that the language-specific key must be uniquely assigned. One language-specific key must always be used for one unit only.

SAP Note 15412 - Taking over balances for tax accounts

Symptom:

Customer wants to configure balances in the tax accounts within the framework of tranferring old data from another system.

Cause and prerequisites

System changeover

Solution
The same transaction is used that reposts the tax payable.
This is transaction FB41.
The transaction is in the menu path:
General ledger -> Periodic tasks -> Monthly closing -> VAT -> Post tax payable.
Because the posting is made to a closed period, you can also perform a normal transfer posting.
In this case, the "Only automatic posting" indicator must be temporarily deactivated in the tax account.
You can then make the posting with the tax amount for transfer, a valid tax indicator, and the automatic calculation for the tax base.

22.12.10

SAP Note 15399 - SQL Error "INF-952: User's password not correct."

Symptom:
The connection to the database can not be opened. In more detail, the following symptoms can occur:

1. Starting the R/3 System with 'startsap' terminates with the error message:

R3trans test connect to the database failed
Return code: 12

The explicit check of the connection to the database with 'R3trans -d' terminates with the error message:

2EETW169 no connect possible: "DBMS = INFORMIX --- ...

The log file of R3trans contains entries such as:

***LOG (BY2): sql error -952 performing CON
***LOG (BY0): INF-952: User's password is not correct
for the database server

2. The R/3 processes cannot connect correctly to the database. In the R/3 trace files (2.xy: 'dev_db*'; 3.xy: 'dev_w*'), there are entries such as:

***LOG (BY2): sql error -952 performing CON
***LOG (BY0): INF-952: User's password is not correct
for the database server

..log') contains the error message:

listener-thread: err = -952: User's password is not correct
for the database server

4. The execution of 'update statistics' via transaction DB02 using the program 'infupdstat' terminates with the SQL error -952. The file 'infupdstat.log' contains entries such as:

SQL-Error: -952. command failed.
User's password is not correct for the database server.

5. The execution of an 'archive' or 'backup' via Transaction DB13 using the program 'infarcexe' or 'infbarexe' terminates with the SQL error -952. The backup with the Informix programs ('ontape', 'onarchive' 'onbar') may still work.

Additional key words

STARTSAP, STARTDB, TP, R3TRANS, UPDATE STATISTICS, INFUPDSTAT, DB02, INFARCEXE, DB13, SAPLICENSE, INFORMIX_DB_PASSWD, SAPUSER, INF952

Cause and prerequisites

This error may have the following causes (sorted according to their likelihood):

1. The password used by the programs to connect to the database is wrong.

The database connect is usually performed as the user 'sapr3'. The password to connect to the database must correspond to the login password for the operating system user 'sapr3' on the database host. Depending on the R/3 version, the individual programs determine the password for 'sapr3' as follows:

Up to R/3 Release 2.1I/2.2C:

The password is always determined from the environment variable INFORMIX_DB_PASSWD of the parent process.

From R/3 Release 2.1J/2.2D:

The password is determined from the database table '<>adm'.sapuser.

Caution:

In R/3 Release 2.1J/2.2D, some programs have not been switched to this logic. They still determine the password using the old method via the environment variable INFORMIX_DB_PASSWD of the parent process. From R/3 Release 2.1L/2.2E, these programs have also been changed.

These programs are: saplicense, infupdstat, infarcexe.

The password used by the programs is too long.

2. The database system cannot read the file '/etc/shadow', as the program 'oninit' has the wrong authorizations.

' cannot be accessed by the user 'adm'.

Solution

The problem can be corrected as follows (the numbering for the solutions corresponds to the listed causes):

1. Adjust the logon password used by the the programs to match that of the operating system user 'sapr3' (notice the overlap in the two procedures for R/3 Releases 2.1K and 2.2D):

Up to (and including) R/3 Release 2.1J/2.2D:

Set the value of the environment variable INFORMIX_DB_PASSWD for the user 'adm' to the password of the user 'sapr3'.

Adjust the login files for the user 'adm'

. informix.csh and .informix.sh (up to 2.1F)
.dbenv.csh and .dbenv.sh, (from 2.1G/2.2A)
.dbenv_.csh and .dbenv_.sh (from 3.0C)

correspondingly, to permanently eliminate the problem.

From (and including) R/3 Release 2.1J/2.2D:

Check the password used by the programs to log on to the database with:

$ su - adm
echo "select * from sapuser
where userid = 'sapr3';" | dbaccess

If this does not match the password for the operating system user 'sapr3' on the database host, correct this value, for example, with:

$ su - adm
$ echo "update sapuser set passwd = ''
where userid = 'sapr3';" | dbaccess

Restart the R/3 System after this.

2. Check whether the password for the user 'sapr3' is longer than 6 characters. Depending on the operating system only 6 or 8 characters are evalued. It then seems as if the passwords match. However, when connecting the SAP programs (tp, R3trans, sapdba) this results in an error. If this is the case, reduce the length of the password.

3. Check the authorizations of the program 'oninit' with:

$ ls -la $INFORMIXDIR/bin/oninit

The output should look like this:

-rwsr-sr-- root informix /informix//bin/oninit

If this is not the case, the software installation on the database system cannot be used, and the software must be re-installed. R/3 and the database must be stopped to do this. It is then sufficient, depending on the hardware platform to run 'installesqrt/installonline' or 'pkgadd' according to the installation guide, chapter 'Installation of the Database Software', 'Understanding the Installation Phase' (sections 2.a and 2.b).

4. Check the permissions for the directory '/INFORMIXTMP' with:

$ ls -ald /INFORMIXTMP

The output should look like this:

drwxrwxr-x root informix /INFORMIXTMP

If this is not the case, correct it with:

$ su - root
$ chmod 775 /INFORMIXTMP

5. Check the current value for the 'Maximum number of file descriptors' for the operating system user with:

$ limit descriptors

The output should look like this:

descriptors 1024

If the entered value is significantly smaller than 1024, increase this by using the statement

$ limit descriptors 1024

to explicitly increase the value for the duration of the logon. You should add this statement to the login file of the user 'informix' to eliminate the problem permanently.

SAP Note 15391 - KEU1/KEU2: Selection of field group for tracing factor

Symptom:

When you press F4 on the field group, not all the value fields of the operating concern are displayed.

Cause and prerequisites

The number of the field group only has one character, so only nine value fields can be selected.

Solution
In Release 2.1x, only the first nine value fields of an operating concern can generally be selected as a tracing factor. In Release 2.2x, only the first ninety-nine value fields can be selected as a tracing factor. If you want to use other value fields, you must enter a digit different to 0 in the column RC of table T811J. The digits must however be uniquely assigned to the value fields, that is, 0 must be entered for other value fields.
Key to the affected entries:
CE7nnnn U I xxxxx (nnnn - operating concern, xxxx - name of value field)

SAP Note 15384 - Delivery for a stock transfer order and batch

Symptom:

When a batch is entered in a delivery for a stock transport order, that batch is not reserved. This causes errors in the availability check and in displays.

Cause and prerequisites

Planning in the delivering and receiving plant only takes data from the order. The order does not recognize the batch, however.

Solution
Due to the high degree of modification required, this problem cannot be solved in Release 3.0 or earlier.

SAP Note 15374 - Checklist: Performance analysis

Symptom:

Customer has Performanceproblems but no connection or only a poor remote connection to SAP.

Cause and prerequisites

Many possible reasons.

Solution

We strongly recommend every customer to install a usable remote connection to an SAP SUPPORT Center as soon as possible.
Without this connection, the solution of problems will be delayed. In critical problems it also might be necessary to have an SAP consultant analyze the system on-site.

In the case of serious perfomance problems, the following lists have to be printed:

Once for the whole system:

SM51

ORACLE :

ST04 -> Goto -> State -> Parameter Changes -> History of file

ST04

DB02 -> Missing indices

DB02 -> Freespace statistics

DB02 -> Goto -> Check -> Reorganisation -> Extents/Table;Index

INFORMIX :

ST04 -> Button Shared memory incl.

ST04 -> Goto -> Activity -> Current statistics -> Wait statistics

ST04 -> Goto -> Activity -> Database log
(for the last 3 days!)

ST04 -> Goto -> State -> Parameter changes

DB02 -> Missing indices

DB02 -> Freespace statistics

DB02 -> Goto -> Check -> Reorganisation -> Extents/Table;Index

How often do you run an update statistics for the database?

ADABAS D :

ST04

ST04 -> Goto -> State -> Parameter Changes -> History of file

ST04 -> Goto -> State -> Configuration

ST04 -> Goto -> State -> tables/indices -> Select table : *
-> Missing indices

How often do you run an update statistics and an update columns
for the database ?

For DB2 database server on UNIX and Windows NT

ST04

Do lock escalations exist that caused long lock-wait times or deadlocks?

If the lock list full?

DB12

Were the RUNSTATS runs (ALL or DBSTATC) carried out properly?

For every SAP instance:

SM50 -> CPU

ST06

ST06 -> Goto -> Current local data -> Snapshot -> Top CPU process.

ST03 -> Goto -> Current local data -> Today's workload --->>>
--->>> Tasktype profile
--->>> Tasktype profile and double click on Dialog
--->>> Transaction profile

ST02

ST02 -> Goto -> Current local data -> Storage

ST02 -> Goto -> Current local data -> Storage -> Shared memory detail

SA38: RSPFPAR -> Execute

Print these lists and forward them to SAP.

This procedure can only be used in emergency situations, and is not intended to replace the Early Watch Service or Remote Support.

SAP Note 15372 - SAPcomm: error after SAP System restart

Symptom:

SAPcomm error after SAP System restart.
Various SAPcomm error messages, e.g.
E0011: Error write queue.
Component error: get sapcomm.mid semaphore.

Cause and prerequisites

Operating system resources (semaphores, etc.) have been deleted.

This may be due to the following reasons:

1) The resources were deleted by operating system commands (iprcm
or corresponding commands).

2) The resources were "automatically" deleted due to shutdown of a
running SAP System. This is only possible when the same computer
runs both SAPcomm and the SAP database, application, or presentation
server. If this is the case, the cause of the problem is an
error in the SAPcomm configuration.

Solution
Delete any running SAPcomm processes and existing SAPcomm resources (shared memory, semaphores, event flags, and system queues):
SAPcomm programs: Operating system command "kill".
Shared memory, semaphores
and event flags: SAP program "cleanipc ", "no."
is the number of the "SAPSYSTEM"
from SAPcomm profile file sapcomm.pfl

System queues: Operating system command "ipcrm".

Re Cause 1):
You should never delete operating system resources that SAPcomm is using while SAPcomm is running.

Re Cause 2):
The root of the configuration error: SAPcomm and an SAP System have the same value for profile parameter "SAPSYSTEM". Set this parameter (in sapcomm.pfl, the SAPcomm profile file) to a value that is not used by any SAP System.

SAP Note 15365 - CONVERT_NO_NUMBER

Symptom:

The payment print and tape generation program for POR (RFFOCH_U) terminates with CONVERT_NO_NUMBER.
Upon closer examination, you see that field REGUP-ESRRE contains non-numeric characters; this causes the error.

Cause and prerequisites

Account assignment errors with the POR reference number should really be trapped by a check routine in the invoice document. However, the customer did not activate that check in the country table, T005.

Solution
Menu path:
Tools -> Customizing -> Configuration menu -> Global settings Countries -> Field checks
Activate the check for Other checks, Other data.

SAP Note 15355 - Command line parameter for access type L

Symptom:

Executing UNIX commands depending on properties of an output request
-or-
Is there a way to call a script in UNIX (during initialization for editing types) which calls a specific layout on the printer, provided the printer supports the layout?
Keywords: rspo/host_spool/print
As a rule, the parameters can be used in an NT system in the same way.

Cause and prerequisites

Request for specific printer adaptation

Solution
The list of possible host spooler commands (profile value rspo/host_spool/print) has been enhanced in Release 2.1g/2.2a: && : a single '&'&P : output device (as before)
&F : transfer file (as before)
&f : name of transfer file without path name share (as of 4.0A)
&p : path name of transfer file (as of 4.0A)
&C : number of copies (as before)
&I : job name of SAP spooler
&J : job name of SAP spooler with database name
&L : layout
&M : client of owner
&O : owner
&m : printing client
&o : printing user
&t : phone number (FAX)
&T : title
&R : recipient (cover sheet)
&D : department (cover sheet)
&S : SAP name of output device
&Y : priority
&U : UNIX cover sheet requested? ('N'=No, 'X'=Yes, 'D'=Default)
&N: number of the spool request (as of Release 4.5A)
&n: number of the output request (as of Release 4.5A)
&c: number of pages (as of Release 4.0A)
&s: field 'Suffix2' of the spool request (as of Release 4.0A)
This information can be used to provide a shell script or UNIX command with data by taking the profile value of "rspo_host_spool/print", which normally appears somewhat like the following: /usr/bin/lpr -P&P -J&F -h -#&C &F 2>&&1; /bin/rm &Fand replacing it with something like: /usr/local/bin/print &P &F &C &L &R &D

Additional key words

Access method L, command pattern, command line, command parameter, parameter

SAP Note 15348 - New Countries: how to modify RFFODOWN

Symptom:

Report RFFODOWN aborts with error 302 or 303.

Cause and prerequisites

There exists hard-coded information for each country using RFFODOWN. A program modification has to be made to enable new countries to use the report.
Why country-specific information ?
Banks of different countries require different file-formats. The report checks whether the first record read contains a country-specific pattern. This is done to make sure, that a file for country A will not be sent to a bank in country B.
When deleting a file the same check is done. Only files with typical patterns can be deleted. This is done to avoid the deletion of arbitrary files on the file-system.
Most of the banks require, that the DME file has to have a specific name, e.g. DTAUSxxx for German data medium exchange. A check for a correct name is done before generating a new file on the PC.

Solution

What's to do now ?
The first step should be to contact SAP to find out, whether a modification for the country in question is planned.
If not, the report has to be modified as following:

Copy the report to a name of your own, e.g. ZFFODOWN

Edit the report:

1) Modify name-check of the new file, e.g. ETEBAC for France:

Find 302:

IF PAR_FILE(6) NE 'DTAUS0' AND

PAR_FILE(6) NE 'ETEBAC' AND "<-- Insert your name requirements

PAR_FILE(3) NE 'PBS'.

SET CURSOR FIELD 'PAR_FILE'.

MESSAGE E302.

2) Modify the pattern-check:

Example: The first record of a French file contains one the following

patterns: record+0(4) = '0302' OR

record+0(4) = '0308'

If the first record contains the bank key of the house bank,

this key is to be copied to HLP_BLZ - otherwise the field has

to be SPACE !

Find 303:

IF PAR_COPY NE SPACE.

IF HLP_RECORD(5) EQ '0128A' AND PAR_FILE(6) EQ 'DTAUS0'.

HLP_BLZ = HLP_RECORD+7(8).

* begin of insertion

ELSEIF HLP_RECORD+0(4) EQ '0302' AND PAR_FILE(6) EQ 'ETEBAC'.

HLP_BLZ = SPACE.

ELSEIF HLP_RECORD+0(4) EQ '0308' AND PAR_FILE(6) EQ 'ETEBAC'.

HLP_BLZ = SPACE.

*end of insertion

ELSE.

MESSAGE E303 WITH PAR_PATH.

ENDIF.

Find 303:

IF PAR_DELE NE SPACE.

IF PAR_COPY EQ SPACE

AND HLP_RECORD(5) NE '0128A'

AND HLP_RECORD+(4) NE '0302' "insert pattern check

AND HLP_RECORD+(4) NE '0308' "insert pattern check

AND HLP_RECORD(5) NE 'BS002'.

MESSAGE E303 WITH PAR_PATH.

ENDIF.

SAP Note 15330 - System operation stops during word processing

Symptom:

Within word processing (up to now, always in connection with the processing of forms or when importing texts with report RSTXR3TR), SAP System operation stops when Table STXL is accessed.
This frequently occurs on SINIX computers, but has also happened on other hardware platforms. The session cannot be ended using normal means (SM04 -> Delete session), either.

System environment: SINIX version <=5.41,
Oracle version <=7.0.16.6.2
Windows NT (SAP Release 3.0)

Cause and prerequisites

The reason is unknown. All attempts to analyze the problem have failed. The error is caused by a bug in ORACLE communication.

Solution
If the session can no longer be ended, you can restart the work process with SM50/Click on WP/Menu: Process -> Cancel w/o core
Connect to the database with TWO-TASK set to avoid the problem. The problem has never appeared with this connection.
The problem has occurred only in connection with Table STXL.

The following procedure is valid only for UNIX Platforms. If the problem occurs on Windows NT, please see related Problem Notes 31559 and 31563.

To connect the R/3 Work processes to the database via Two Task, the startup script for the alias 'startsap' in the Home Directory of the User:
$HOME(adm)/startsap__
z.B. /usr/sap/DEC/home/startsap_da5201_00

( is the SAP System name, e.g., C11) must be chaned as follows: (lines 163-169):
#
# Start SAP-Instance
#
TWO_TASK="T::" <=========== Insert !!
export TWO_TASK <=========== Insert !!
if [ $TASK = "ALL" -o $TASK = "R3" ];then
if [ -f $EXEDIR/sapstart ];then
echo "\nStarting SAP R/3 Instance " tee -a $LOGFILE

Here stands for the computer name (e.g. hs0013) and for the database name (usually C11).

Additional key words

SAPACRIPT SE71 SAPLSTXD RSTXR3TR SCC1 CLIENTCOPY CLIENT-IMPORT

SAP Note 15327 - Bank data

Symptom:

During a payment run, the customer's bank data is not copied to the bill of exchange or bill of exchange payment request.

Cause and prerequisites

Customizing

Solution
The method of payment must be configured such that the bank information is marked as "Required" under "Required information in master record".

SAP Note 15322 - Change ArchiveLink call with SAPGUI (UNIX)

Symptom:

error from the SAP kernel

Cause and prerequisites

Start script archlink is not found by SAPGUI

Solution
SAPGUI version 2.1F and above searches for the ArchiveLink Archive connection in its exe directory (standard: /usr/sap/SID/SYS/exe/run, where SID is replaced by the system ID of the R/3 System, for example C11). The start script archlink must be installed in this directory.

SAP Note 15315 - Version management does not display versions

Symptom:

The customer has imported objects from a source system to a target system using a transport order. Version management does not display a version for these objects.

Cause and prerequisites

The objects have not been modified in the target system using the correction and transport system. After an import, versions are used only if modifications (versions) already exist in the target system. Keyword: R3SLMODVERS

Solution
After an import, version management uses only versions for objects which also had versions before the import. This is a principle for improving the performance of the system: imported versions already exist in the source system, so you only have to save the local modifications in the target system and keep them as versions. Versions are used in this way and the storage area required for the versions in minimized.
If you have the problem of carrying out a version verification in the target system, for example for revision purposes, you must make sure that the transport system logs are kept on the operating system level. The logs are not deleted by the correction and transport system, only within the system administration on operating sytem level. From the ALOG file, you can find out which transport was successfully carried out into which system. From the transport number, you can find out which source system the transport came from. The object list for the transport contains a reference to the correction which can be used to find the version in the source system.

Additional key words

R3SLMODVERS

SAP Note 15313 - Creating asset history sheet version

Symptom:

If you create an asset history sheet version (transaction OA79, program SAPMA06C), the line and column specifications are not saved if there was no value assignment to the item.

Cause and prerequisites

This is not a program error because it is used for the subsequent processing - especially for the asset history sheet.

Solution
There is only this one solution:
Before saving, enter at least one value assignment for each of the coordinates you have specified. For the time being, this can just as well be a pseudo assignment until you have made the correct assignment.

SAP Note 15311 - RFBIBL00, RFBIDE00, RFBIKR00: error message 00344

Symptom:

Error message: 00344 with screen 360, for example

Cause and prerequisites

A batch input data record was passed on with only initial values (NODATA).

Solution
If a record does not have at least one field that is set to a non- initial value, it cannot be written to the batch input file.

Additional key words

RFBIBL00, RFBIDE00, RFBIKR00, RMBIKR00

SAP Note 15307 - Performance

Symptom:

Poor performance when creating/editing production orders, networks, plant maintenance requests, projects ( CO01, CN21, ...)

Solution
Performance is affected by a large number of factors. In addition to
hardware installed by the customer, which of course cannot be considered in this note, there are a number of parameters that
the customer can check and influence. Only the most important ones are
listed in this note. Should you have further questions, the SAP 'Early Watch Service' is available for you to take advantage of.

The following aspects should be taken into account when judging performance:
1) Data volume and constellation (extensive BOMs/routings; complex conditions in pricing/calculating overhead rates)
2) Scope of the functions performed (operation checks when routing is copied, type of availability check)
3) Technical parameters (buffer situation, network architecture, number of dialog processes)

Re 1)
Whenever possible, avoid using complex access sequences when selecting BOMs and routings.
Also check the conditions for pricing (They are used to determine overhead rates). If you are not interested in the planned costs of production orders, you can switch off the calculation of planned costs by not entering a costing variant for determining planned costs (Order Type Dependent Parameters in the customizing menu of Production Activity Control).

Re 2)
To improve performance, you should deactivate the availability check during order creation (customizing menu of Production Activity Control: Operations -> Availability Check -> Control).
Checking of the routing data during order creation should be deactivated (Customizing: Order Type Dependent Parameters) as well as
checking of the component data from the BOM via detail screens.

Performance problems in lead time scheduling and calculation of capacity requirements can be traced back to calculation of the formula analysis. Here one must be careful that the formulas in Include
FCR05xxx ('xxx' stands for the respective command) are present in
generated form. The formulas can be generated explicitly via report
RCR05GEN.

Re 3)
A monitoring tool exists within the SAP System (Tools -> Administration -> Monitoring -> Performance -> Tune/setup buffers that can be used to judge the quality of the system buffers). The qualities of the DDIC-relevant buffers should always be > 95%. The size and quality of the program buffer are equally important. In PP, the program buffer should be at least 40 MB. The allocation of applications per application server is also important for good quality. The optimal configuration is one work area per application server. i.e. users from different work areas (PP, SD, CASE) do not work on one application server; instead, separate servers are configured for PP, SD, CASE, etc. You should select the number of dialog processes in such a way that at least one dialog process is always available. This and the possible size of the system buffer are dependent on the memory available on the application server. For sufficient performance, the memory capacity should be at least 256 MB.

SAP Note 15301 - Physical inventory: Incorrect moving average price for stand

Symptom:

This note is no longer valid. Please see note 37162!!

You have a material with standard price control. This material has a stock in the previous period. If you now create a physical inventory document for this material in the previous period and make an adjustment posting for this material document from the previous period, the moving average price is incorrect after making the adjustment posting of the inventory difference.
The exact value is: standard price * total stock.

Cause and prerequisites

Program error.

Solution
To correct the error, you have to insert the line marked below in the following Include of module pool SAPLMBWL:
Include LMBWLU02:

FUNCTION MB_CREATE_INVENTORY_DIFFERENCE.
...
MSEG-KZBEW = T158-KZBEW.
MSEG-MJAHR = MKPF-MJAHR.
MSEG-PARBU = MTM07I-BUKRS.
MSEG-WAERS = MTM07I-WAERS.
MSEG-BWART = MVM07I-BWART.
MSEG-ERFMG = MVM07I-DIFME.
MSEG-MENGE = MVM07I-DIFMG.
DM07M-MONAT = MONAT.
DM07M-XLORT = X.
-> DM07M-VMSAV = DM07M-VMSAL. "New
RM07M-BUKRS = MTM07I-BUKRS.
...
ENDFUNCTION.

SAP Note 15298 - Sender with costs is not settled

Symptom:

Description : A sender with costs is not settled.
The error can occur with WBS elements at billing level,
with sales orders and internal orders with revenues.
Message KD213: The sender has already been settled or there is
nothing to be settled.
Transactions : KO88, VA88, CJ88

Cause and prerequisites

Operating error

Conditions :
1. A results analysis key is entered in the master record of the sender.
2. Results anaylsis has not yet been carried out for the settlement
period.

Solution
Remove the results analysis key from the master data of the sender or start results analysis before the settlement.
In case of wbs elements created in release 2.1 or 2.2 resp. which are not relevant for results analysis note 42723 describes how to remove the results analysis key from the master records.

SAP Note 15297 - Materials planning: No valuation type defaulted

Symptom:

If purchase requisitions for materials subject to split valuation are generated within materials planning (Transactions MD01, MD02, MD03), the system does not supply a default value for the valuation type.
The header record is generally used (without valuation type).

This behaviour is also observed when you convert planned orders into purchase requisitions, regardless if the planned order has been generated by material requirements planning or created manually.

Cause and prerequisites

This has not been intended and currently cannot be implemented either.

Solution
None.
When you enter the valuation type during conversion PReq -> purchase order, an account determination is performed with the corresponding valuation type automatically.

Additional key words

Materials planning, split valuation, material requirements planning,
MRP, planned order, PReq, MD14, MD15, MD16, MD04

SAP Note 15291 - SysLog daemons terminate immediately

Symptom:

SysLog deamons terminate immediately.
Their names: rslgcoll = co.sap....
rslgsend = se.sap....

Diagnosis:

Check the "stderr1", "stderr2", etc. files in the work directory (UNIX more or transaction ST11). The first three lines show the program the file refers to. A reason for the termination should appear at the end of the line. Some of the possible messages:

With exit code 0 :
I become a daemon.
With exit code 1 :
Assertion failed: ...
Central SysLog file has wrong format. ...
Central SysLog file has many format errors. ...
rslgcoll(3).read: ...
I read half of a record.
rslgcoll(8): socket: ...
rslgcoll(9): bind: ...
rslgcoll(10): listen: ...
With exit code 2 :
other daemon is still alive.
PId-file does not contain a number.
PId-file seems to be empty.
rslgsmcc(72).rslgsm1_write_pid_file: open(,O_RDONLY,0)

For messages with exit code 1 or 2 :
If the stderr files do not contain enough information, you can start the corresponding daemon again in logging mode. The stderr file lists the command used to start the daemon. Copy this command, copy it to a single line, and add "-v" at the end. The daemon will then start in logging mode.

For messages with exit code 2 :
Check files "rslgcpid" and "rslgspid" in the data directory. When a daemon is active, its process number should appear therein. A negative value means that the corresponding daemon is blocked. Empty files are not allowed.

Cause and prerequisites

Exit code 0 and "I become a daemon." :
Option "-F" missing in the command line (see STARTUP profile)

Exit Code 1 :
Various.

Exit code 2 and empty PID file:
Disk full when daemon was started.

Exit code 2 and negative number in PID file on AIX:
When the process number is greater than 32768, the number is sometimes entered in an incorrect format.

Solution
Exit code 0 and "I become a daemon." :
Add option "-F" to the STARTUP profile.

Exit code 1 :
Read the entire error message. Check the SysLog. Check whether the involved SysLog files display documentation when F2 is pressed.

Exit code 2 and empty PID file :
Wait a minut. It it stays empty: delete it.
Should work again during the next system start.

With exit code 2 and PID file with negative number:
Delete the file.
Should work again during the next system start.