SAP OSS Notes

3.3.11

SAP Note 24207 - Platform-independent file names do not function

Symptom:

The application programs which use the function module FILE_GET_NAME always receive a file name in the global directory from this function module. The definitions in the Customizing tables of the platform-independent file names are apparently ignored. Changes in the transactions SF01, SF02 and SF03 have no influence on this problem. It appears that the file name is permanently linked to the application program in the global directory.

Cause and prerequisites

The function module FILE_GET_NAME always returns a file name in the global directory if no file name could be generated using the settings in the Customizing tables.
In addition, the function module supplies the message that such a problem has occurred in the parameter EMERGENCY_FLAG. The application program which uses the file names in the global directory, does not respond to this message from the function module FILE_GET_NAME

Solution
The most frequent cause for this problem is a missing entry for the underlying operating system. You can make this entry via the transaction SF04. The transaction SF04 recognizes the current operating system automatically and makes an entry. You can recognize this entry because it is displayed selected. Please go into the detail maintenance for this entry and enter the respective syntax group there. Only now is the function module FILE_GET_NAME able to find the physical path which you can maintain per syntax group via the transaction SF03. After saving your changes, the problem should be solved.
If the problem occurs even though an entry exists, you must check the entries again in the transaction SF01 and SF03.
You can use the transaction SF07 to check your settings in the Customizing tables of the platform-independent file names.

SAP Note 24199 - Vendor evaluation - valuations > Max. points

Symptom:

The note is only valid for Release 3.0 !

Preconditions: subcriteria which are determined via user exits -----------------------------------------------------------------
During the automatic evaluation of a vendor via ME61, ME63, or in the background via report RM06LBAT, the system determines scores higher than the maximum number of points according to table 147 ( Customizing - Purchasing - Functions - Vendor evaluation - Purchasing organization - Control parameters).

Cause and prerequisites

The user exit does not take the maximum score defined in Customizing into account.

Solution
Carry out a check on the maximum score in table 147 ('best score') in the user exit also.

SAP Note 24189 - Informix: Disk layout / moving dbspaces / chunks

Symptom:

Bad performance due to unbalanced I/O.

Cause and prerequisites

Unfavorable dbspace/chunk distribution on the hard disks.

Solution
Dbspace/chunk layout

Different criteria can be used as a base for favourable distribution of the Informix dbspaces/chunks on the hard disk.

1. Distribution with regard to I/O rate on dbspaces.

'Early Watch' analyses have shown that the following distribution can be recommended on account of the I/O rates.

Put ROOTDBS, PHYSDBS and LOGDBS on 3 separate, fast hard disks.

Put their respective MIRRORS on 3 separate, fast hard disks as well.
It is mandatory to mirror ROOTDBS, PHYSDBS und LOGDBS.

PSPABTAB, PSAPCLU and PSAPSTAB have high I/O rates and should therefore be kept separate. Use fast hard disks if possible. They can be combined with dbspaces that are used less often (see below).

PSAPSOURCE, PSAPDDIC, PSAPDOCU, PSAPLOAD, PSAPESxxx and PSAPELxxx, have low I/O rates and should also be separated in order to avoid unbalanced disk utilization. Slower disks can be used here.

2. Heuristic rules

You should not put dbspaces with high I/O rates on disks which are used as system SWAP. This can result in very poor performance if the disks are used as SWAP area and for dbspaces LOGDBS and PHYSDBS.

As of Release 3.1G, three temporary dbspaces with 400 MB each are created by R3INST. The temporary dbspaces should be located on different disks, and they should only contain one chunk each. (also see Note 49381).

Influence on disk configuration with UNIX-R3INST

The R/3 Standard Installation program (R3INST) can approach optimal disk configuration only if the dbspaces in the file INSTINF.PFL are sorted according to access frequency: for example,
rootdbs \ /
physdbs \ /
logdbs* \ /
tmpdbs* \ /
psapbtab \ /
psapclu \ /
psapstab \ /
psappool \ /
psapprot \ /
psapsource \ /
psapddic \ /
psapdocu \ /
psapload \ /
psapuser1 \/
Optimizing the distribution of dbspaces/chunks MUST be done manually: modify the buildinf.pfl file before the db-build step: ('Shall dbspaces be created?').

Subsequent changes to the disk configuration is currently not supported by Informix.

The only solution is as follows:
Unload all the tables of a dbspace, delete them, create them again and load them. We recommend that you use the DB administration tool SAPDBA to do this.

Additional key words

INF, DBA, installation, PERF, layout, dbspace, chunk

SAP Note 24182 - Allocation - INFORMIX: Locking problems INDX

Symptom:

Key word: Allocation
Description: When an allocation is being carried out in the INFORMIX database, exclusive lock indicators are set for table INDX by the database system. This means that, when you work online, increasing numbers of transactions encounter this INDX lock indicator and are forced to wait.
Consequence: Considerable restrictions when working online
Transactions: KSU5, KSV5, KSUB, KSVB, KSW5, KEU5, GA15, GA35, GA2B GA4BProgram name: SAPMKGAL, ALxxYYYR (xx: serial number, yyy=client)

Cause and prerequisites

INFORMIX problems when an EXPORT statement is executed on table INDX

Solution
1. How to avoid error:
The only way to avoid the above-mentioned 'lock' problems is to let the allocation run on its own without online mode being activated or other background jobs running in parallel.

2. In order to avoid the locking problems completely, you must insert the correction shown below.
************************************************************************
* Programm: LKGA2U01
* Funktionsbaustein: K_ALLOCATIONS_RUN
************************************************************************

FUNCTION K_ALLOCATIONS_RUN.
:
:
:
:
*.generate specific report for allocation
PERFORM E01-GEN-ALLOCATION-JOB(SAPFKGA2)
TABLES
IT811CT
USING
IRKGA2U
RNAME
TITLE
RCODE.

IF RCODE <= EL-INFOR.
*...check if reverse already complete
IF REVERSE = TRUE.
CALL FUNCTION 'ENQUEUE_EK811D'
EXPORTING
TAB = EQ_T811D-TAB
CYCLE = EQ_T811D-CYCLE
SDATE = EQ_T811D-SDATE
GJAHR = EQ_T811D-GJAHR
PERIO = EQ_T811D-PERIO
DPOS = EQ_T811D-DPOS
_WAIT = TRUE
EXCEPTIONS
FOREIGN_LOCK.
IF SY-SUBRC <> 0.
MESSAGE A534 WITH SY-MSGV1 TITLE RAISING FOREIGN_LOCK_REV.
ENDIF.
ENDIF.

*...INFORMIX: dequeue all locks made by EXPORT commands <<<< if sy-dbsys = 'INFORMIX '. <<<< commit work. <<<< endif. <<<<
*...run generated report
IF SY-BATCH = TRUE.
:
:
:

SAP Note 24177 - OSS1: Message S1452: Connection to Message Server

Symptom:

When you try to log on to the OSS system using Transaction OSS1, the error message S1452 appears: 'Unable to connect to OSS message server. Default connection will be used ...'.

Cause and prerequisites

Program 'lgtst' not installed
or
configuration not correct. Solution

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Program 'lgtst' not installed
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Please install the program 'lgtst', which is available on the 2.2D CD, in the executables directory of your system (usually this is /usr/sap/[SID]/SYS/exe/run ).

This program is used by Transaction OSS1 to establish the connection to the OSS message server and determine the logon groups available and the OSS application server with the best performance. When this program is missing, the connection to the message server cannot be established, i.e., the server cannot be determined. The system will then log you on to the standard OSS application server.

The program 'lgtst' should be started manually only when problems occur.

To start the program manually, enter the following command at the shell level of the database or application server:
/usr/sap/[SID]/SYS/exe/run/lgtst
-H /H/[YS]/S/[YSS]/H/[sapservX]/S/sapdp99/H/oss001/S/sapmsO01
-S x -W 30000

Please note:

a) This is ONE command with many parameters.

b) [SID] must be replaced by the system ID (e.g. C11) of your system.

c) [YS] must be replaced by the name of the computer on which the SAPRouter runs (YS = Your SAPRouter).

e) If you are working with two SAProuters, please repeat /H/[YS]/S/[YSS] with the data of the second SAProuter before the sapserv specifications.

f) [sapservx] must be replaced by the IP address of the server that you are connected to.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Configuration not correct
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In cases where the program 'lgtst' has been installed correctly, but the connection to the message server cannot be built up, the configuration is not correct.

There are many possible reasons. The most frequent causes:

a) Technical OSS1 settings

b) Service entries missing in /etc/services

Examples:
~~~~~~~~~
************************************************************************
*
* ERROR partner not reached (host abc.def.gh.i, service sapdp99)
*
* TIME Thu Aug 10 09:17:57 1995
* RELEASE 21J
* COMPONENT NI (network interface)
* VERSION 15
* RC -10
* MODULE niuxi.c
* LINE 773
* DETAIL NiPConnect
* SYSTEM CALL connect
* ERRNO 239
* ERRNO TEXT Connection refused
* COUNTER 1
*
************************************************************************

In this case, the system was unable to reach the SAPRouter, i.e., under Service 99 (Port 3299) no SAPRouter can be reached on the host with the IP address abc.def.gh.i. The SAPRouter process is not running, or the IP address is configured incorrectly in OSS1.

************************************************************************
*
* ERROR service 'sapdp99' unknown
*
* TIME Thu Aug 10 09:22:00 1995
* RELEASE 30A
* COMPONENT NI (network interface)
* VERSION 17
* RC -3
* MODULE niuxi.c
* LINE 404
* DETAIL NiPServToNo
* SYSTEM CALL getservbyname
* COUNTER 1
*
************************************************************************

This message indicates that the service 'sapdp99' has not been entered in /etc/services. Please add this entry to /etc/services. The entry must exist on all R/3 servers and all frontends.

************************************************************************
*
* LOCATION SapRouter on abc.def.gh.i
* ERROR route permission denied (XXXXXXXX to sapservX, sapdp99)
*
* TIME Thu Aug 10 09:37:44 1995
* RELEASE 30A
* COMPONENT NI (network interface)
* VERSION 17
* RC -94
* MODULE nixxrout.c
* LINE 1426
* COUNTER 1
*
************************************************************************

In this case the 'routtab' where the valid connections are specified is not correct. The SAPRouter on the host abc.def.gh.i does not build up the connection to sapservX. Please check the 'routtab' of the SAPRouter. 'routtab' must contain all R/3 servers and all frontends.

************************************************************************
*
* LOCATION SapRouter on abc.def.gh.i
* ERROR internal error
*
* TIME Thu Aug 10 10:50:18 1995
* RELEASE 21J
* COMPONENT NI (network interface)
* VERSION 15
* RC -93
* MODULE niuxi.c
* LINE 773
* DETAIL NiPConnect
* SYSTEM CALL connect
* ERRNO 242
* ERRNO TEXT No route to host
* COUNTER 1
*
************************************************************************

This error message indicates that the host abc.def.gh.i cannot handle the IP address of the next host configured in OSS1.
When the SAPRouter error message appears and the next host is sapservX, please check the IP address for sapservX.
OSS1 is delivered with the default setting 'sapserv3' and the IP address '147.204.64.1'. Change this IP address to IP address 147.204.2.5. IP addresses 147.204.63.1 and 147.204.64.1 no longer exist.

************************************************************************
*
* ERROR internal error
*
* TIME Thu Nov 23 00:11:20 1995
* RELEASE 21J
* COMPONENT NI (network interface)
* VERSION 15
* RC -1
* COUNTER 1
*
************************************************************************

This message indicates that for at least one of the SAPRouters defined in the technical settings of OSS1 the specified instance number is not correct. The default instance number for SAPRouter is '99'. Do not specify the instance number of your R/3 System under any circumstances! For the sapservX computers the specification of instance number '99' is mandatory; otherwise logon to OSS is not possible.

************************************************************************
*
* LOCATION SapRouter on sapservX
* ERROR route permission denied (XXXXXX to oss003, sapmsO01)
*
* TIME Mon Nov 27 19:25:54 1995
* RELEASE 30A
* COMPONENT NI (network interface)
* VERSION 15
* RC -94
* MODULE nixxrout.c
* LINE 1390
* COUNTER 1
* ************************************************************************

An incorrect server was specified for the O01 message server, in this example the server oss003. oss01 is the message server for O01.

These examples do not cover all possible cases; other error messages may occur. In individual cases the reason for the problem may be different from the reason specified in the examples.

Example for the technical settings of OSS1:

Router data for logging on to OSS

+-SAPRouter (customer) -----------------------------------------+
| +-SAPRouter 1------------------+ +-SAPRouter 2-----------------+ |
| | Name XYZ | | Name | |
| | IP address a.b.c.d | | IP address | |
| | Instance no. 99 | | Instance no. | |
| +------------------------------+ +-----------------------------+ |
+---------------------------------------------------------------------+

+-SAPRouter and OSS Message Server------------------------------------+
| +-SAPRouter (SAP)--------------+ +-OSS Message Server----------+ |
| | Name sapserv3 | | Name oss001 | |
| | IP address 147.204.2.5 | | DB name O01 | |
| | Instance no. 99 | | Instance no. 01 | |
| +------------------------------+ +-----------------------------+ |
+---------------------------------------------------------------------+

In this example the following situation is assumed:

a) A customer SAPRouter is running on the host XYZ with the IP address a.b.c.d. Please adjust the host name and IP address accordingly. If you have not reconfigured your SAPRouter for another instance, the instance number '99' is correct.

b) You are connected to sapserv3, IP address 147.204.2.5. If you are connected to sapserv3 under another IP address (147.204.64.1 or 147.204.63.1) or another sapservX (sapserv4, sapserv5, sapserv6 or sapserv7), please choose the appropriate connection from the menu 'SAPRouter (SAP)'.

SAP Note 24169 - ORA 1157

Symptom:

When starting the database, ORA 1157 appears

Cause and prerequisites

A datafile cannot be opened or found.

Solution
Following ORA 1157, an operating system error message appears. This is the reason why ORACLE cannot open the file.

SAP Note 24167 - Part. divestiture: Automatic subseq. consolidation

Symptom:

Consolidation of investments (RGCKAP00) does not at present support partial divestiture. The customer is ready to perform the necessary activities (adjusting entry, correction goodwill / hidden reserves in the financial reporting table) manually.
However, FI-LC should at least perform subsequent consolidation (on group / minorities, amortization goodwill distribution annual net income) automatically.

Cause and prerequisites

Missing functionality

Solution
Correction VSK135874h performs the required activities:
RGCKAP00:
...
perform vorgang-testen using vorg-abga t869-type.
if vorg-rc = 0.
perform voll-kons-abga.
perform listart4-plausi.
* Voll-Abgang kann nur allein auftreten
if konzant = 0. "VSK135874h
exit.
endif. "VSK135874h
endif.
...

RGCKAPV0
...
* if plistart = vier. "VSK135874h
if konzant ne 0.
* write: / t852g-rcomp, t852g-ryear, bperiode, text-814. "VSK135874h
write: / 02 text-814. "VSK135874h
exit. "VSK135874h
endif.
refe = konzabg - ( konzant - vjkonzant ).
if refe ne 0.
* write: / t852g-rcomp, t852g-ryear, bperiode, text-815. "VSK135874h
write: / 02 text-815. "VSK135874h
exit. "VSK135874h
endif.
* endif. "VSK135874h
...

SAP Note 24156 - KVD4: data transfer not carried out

Symptom:

Message: Data transfer for cost center and activity type does not function correctly. When you press Execute, the transaction remains in the initial screen and no comment is made.
Transaction: KVD4

Cause and prerequisites

Program error
Preconditions:
FCS customer

Solution
Change program LKWA0U01:
FUNCTION K_STATISTICAL_RATIOS_TAKE_OVER.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
:
:
:
*..read the master record and fill the COIOB-structure
PERFORM READ_MASTER_RECORD TABLES I_GROUPS
I_CCSEL
INT_PERIODS
INT_COIOB
USING I_CCSS
CHANGING GD-FLG_BOOK
GD-SUBRC.
CHECK GD-SUBRC = 0. "<--Delete
CHECK GD-SUBRC <= CON_EL-WARNG. "<--Insert
*..set the object type
PERFORM OBJECT_IDENTITY TABLES INT_COIOB
CHANGING GD-TRVOG.
:
:

SAP Note 24149 - Endless loop when importing a set

Symptom:

Problems when processing BI sessions with semaphore 22. Situation description :
No Type PID Status reason Start Err Sem CPU Time Report Man User

0 SPO 992 waiting yes
1 DIA 993 waiting yes
2 DIA 994 running yes RSMON000 066 EARLYWAT
3 BTC 995 running yes 22 6131 RSBDCBTC 001 HUGO
4 BTC 996 running yes 22 1722 RSBDCBTC 001 HUGO
5 BTC 997 running yes 22 1712 RSBDCBTC 001 HUGO
6 BTC 998 running yes 7396 RSBDCBTC 001 HUGO At this time, several BI sessions are waiting to be processed. The last BTC process uses 90% of the CPU and never terminates.

Cause and prerequisites

Incorrect log file.

Solution
1. Delete the work process which is taking CPU time.
2. Delete the defective batch input log files.
3. Process the batch input again.
Please also read the notes numbered 18307 and 18319

SAP Note 24141 - Program terminates on COMMIT WORK

Symptom:

A program started via a background input or via CALL Transaction...using... terminates on COMMIT WORK. Statements which were located behind the COMMIT WORK command are no longer called up.
If you call the program directly, and not as described above via CALL Transaction...Using... or via background input, the program is processed correctly.

Cause and prerequisites

Via COMMIT WORK, a transaction cannot be taken back and is therefore closed.

For this reason, processing terminates after COMMIT WORK in the background input mode or for CALL Transaction...Using.

Solution
Programs which need to edit things after COMMIT WORK consist of several 'Units of Work'. Thus it is not possible to report whether a transaction has successfully run or not.

Ensure that all operations that are essential to the transaction occur before the COMMIT WORK.