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).
      d) [YSS] must be replaced by the service under which the SAPRouter runs, usually 'sapdp99'
      (YSS = Your SAPRouter's Service).
      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.
      g) Make sure that you replace [YS], [YSS] and [sapservx] with the same data that you have configured in OSS1.


      The following output should appear on your screen:

      using trcfile: dev_lg
      list of reachable application servers
      -------------------------------------
      [oss001_O01_01] [oss001] [155.56.5.5] [sapdp01] [3201] [DIA ]
      [hs2130_O01_01] [hs2130] [155.56.5.33] [sapdp01] [3201] [DIA VB ENQ BTC
      [oss002_O01_01] [oss002] [155.56.5.53] [sapdp01] [3201] [DIA ]
      [oss003_O01_01] [oss003] [155.56.5.47] [sapdp01] [3201] [DIA ]

      list of selectable login-classes with favorites
      -----------------------------------------------
      [PUBLIC] [155.56.5.53] [3201] []



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
      c) Incorrect SAPRouter configuration


      To find out the reason why the attempt to establish the connection to the message server has failed, choose 'Tools -> Case, Test -> Developer trace' (Transaction ST11). The trace contains an entry for 'dev_lg'; this file contains the error log. If a line 'LOCATION' exists, the computer where the error occurred is described there. The problem is described in the line 'ERROR'.


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.

SAP Note 24136 - Missing storage of follow-up time for components

Symptom:

When a planned order was created, the lead time or follow-up time of the components is not stored.

Cause and prerequisites

Error in program LM61ZF50

Solution
Please consider note 24276.

Correction of program LM61ZF50:
001400 001400 FORM CHECK_MATERIAL_POSITION.
...
001890 001890 MOVE MDSPX-AVOAS TO MDPMI-AVOAS.
001900 001900 MOVE MDSPX-AVONT TO MDPMI-AVONT.
001910 001910 MOVE MDSPX-VERTI TO MDPMI-VERTI.

The following lines were inserted: 001920 MOVE MDSPX-NLFZT TO MDPMI-NLFZT.

Contents unchanged: 001920 001930 * > Bedarfstermin bestimmen
001930 001940 PERFORM BDTER_BESTIMMEN

SAP Note 24132 - Vendor evaluation - price level, price history

Symptom:

1. The scores for the subcriteria price level and price development were not determined correctly in the background via report RM06LBAT. With transactions ME61 or ME63, the scores were determined correctly.

2. The scores of the manual subcriteria were initialized via the background report RM06LBAT.

Cause and prerequisites

1. The callup of function module ME_READ_INFORECORD_MAT_ML was missing.
2. The scores for the manual subcriteria were not set.

Solution
ABAP RM06LBAT:--------------
Re 1:
-----
...
...
FORM PREISNIVEAU.
DATA: R1 TYPE P, R2(3) TYPE P.
PERFORM WAEHRUNG.
CALL FUNCTION 'ME_READ_INFORECORD_SUPPLIER_ML'
EXPORTING
CURRENCY = SY-WAERS
SUPPLIER = T-LIFNR
PURCHORG = T-EKORG
TABLES
TEKOND_ML = LINFO.
*... Durchschnittspreise über Infos ohne Marktpreis ....<======= NEW
CALL FUNCTION 'ME_READ_INFORECORD_MAT_ML' <======= NEW
EXPORTING <======= NEW
SUPPLIER = ELBK-LIFNR <======= NEW
TABLES <======= NEW
TEKOND_ML = LINFO. <======= NEW
T147K-EKORG = T-EKORG.
T147K-KRTYP = '4'.
...
...
FORM PREISENTWICKLUNG.
...
...
CALL FUNCTION 'ME_READ_INFORECORD_SUPPLIER_ML'
EXPORTING
CURRENCY = SY-WAERS
SUPPLIER = T-LIFNR
PURCHORG = T-EKORG
DATE = DAT01
TABLES
TEKOND_ML = OLD_PW.
*... Infos ohne Marktpreis verarbeiten ............. <======= NEW
CALL FUNCTION 'ME_READ_INFORECORD_MAT_ML' <======= NEW
EXPORTING <======= NEW
SUPPLIER = ELBK-LIFNR <======= NEW
TABLES <======= NEW
TEKOND_ML = OLD_PW. <======= NEW
T147K-EKORG = T-EKORG.
T147K-KRTYP = '5'.
...
...
Re 2:
-----
...
...
FORM FILL_XKR.
...
...
XKR-LEBEW = HKR-LEBEW.
XKR-LEBDT = HKR-LEBDT.
LOOP AT TKR WHERE HKRIT EQ HKR-HKRIT. <======= changed
PACK TKR-TKRIT TO OFFSET.
OFFSET = ( OFFSET - 1 ) * 2.
...
...

SAP Note 24127 - Error in internal number assignment

Symptom:

Situation where this occurs:
An internal interval exists for object 01S. (1.000 - 10.000)
The current number level is 2771. This previously meant that 1770 positions could be created. Now, further positions are to be created via report RHMULT00. However, the program terminates, and issues the following message: "Information 5A369 - number is in reserve area, please maintain number range RP_PLAN 01S".

Cause and prerequisites

a) The assigned numbers in the corresponding number range have reached the predefined percentage rate from which a warning message is issued to the effect that the number range should be maintained (extended).

Solution
a) Please check the percentage value via transaction SNRO and the number range object in question (for example, RPPLAN for PD)

b) -Please reduce the value of 80 %, to, say, 20 %. This means that a warning message is only issued when the last 20 % of the number range has been reached.

-If, for example, the percentage value is set at 10 %, 20%, please think about extending the existing number range.

SAP Note 24121 - FCS syntax error in SAPLCOSF object M_PSFCK

Symptom:

When a transaction was called from an area within PP, a syntax error sometimes occurred in Program SAPLCOSF. This was caused by the fact that Table M_PSFCK was not defined. The problem only occurs for FCS customers.

Cause and prerequisites

The matchcode Id 'K' for matchcode object PSFC was not delivered.

Solution
The object can be imported from SAPSERV3 (internal transport order S11K134954). It is located under the directory /dist/permanent/Note.0024121. Note 13719 describes, how to import a correction from SAPSERV3 into a customer's system.

SAP Note 24116 - Purchase requisition number not printed: PM

Symptom:

PM shop papers: material provision and material issue slip -
request number not printed
RESBD-BANFN blank

Cause and prerequisites

Program fields have changed page 2.1

Solution SAPSCRIPT FORMULARE must be changed.

Transaction SE71.
Layout sets: PM_GOODS_ISSUE, PM_PICK_LIST, PM_PICK_LIST2, PM_JOB_TICKET

Go into page window.
Editing -> Text elements

The string "&RESB-BANFN" must be replaced with "&RESB-BANFNR".
IN 4 layout sets (PM_GOODS_ISSUE, PM_PICK_LIST PM_PICK_LIST2
PM_JOB_TICKET)

for example: Find the string in the text elements and correct it. Example: PM_GOODS_ISSUE

The correct variable for the purchase requision field is

Additional key words

RESBD-BANFNR is the correct field.


.

SAP Note 24103 - NT: starting BRBACKUP/BRARCHIVE via AT command

Symptom:

Failed start of BRBACKUP/BRARCHIVE via the AT command in Windows NT. Various error messages issued:
BR152E Environment variable ... not set.
or
BR278E command ' (...) ':
The name specified is not recognized as an internal or external command, operable program or batch file
- or -
Access is denied.
BR279E Return code from ' (...) ' : 1
- or -
BR252E Function NetShareGetInfo() failed for 'sapmnt' at location
BrEnvProcess-15
BR253E errno 5: Access is denied.

Other terms

WINAT, WIN-AT, AT command
Caution: After the installation of the Internet Explorer 5.01 you may also use the task scheduler for scheduling BRBACKUP/BRARCHIVE jobs (My Computer -> Scheduled Tasks).

Reason and Prerequisites

The environment variables are not set correctly for the AT command because, in the standard system, the environment of the user who scheduled the AT command is not transferred.

Solution
Create a batch file in which the correct environment is defined before you call BRBACKUP/BRARCHIVE. This file is then scheduled in the AT job.
Example: set PATH=%PATH%;d:\orant\bin;d:\usr\sap\C11\SYS\exe\run
set ORACLE_SID=C11
set ORACLE_HOME=d:\orant
set SAPDATA_HOME=e:\oracle\C11
set SAPARCH=f:\oracle\C11\saparch
set SAPBACKUP=g:\oracle\C11\sapbackup
set SAPREORG=h:\oracle\C11\sapreorg
brbackup -c ...

Caution:
The schedule service which executes AT jobs should NOT be started under the system account, since the service allows no access via UNC names (for example, to \\%COMPUTERNAME%\sapmnt) and the system function NetShareGetInfo() must not be called. It can be started under the user adm, assuming that this user belongs to the group of the
"Power Users", "Server Operators" or "Administrators" .

Caution :
The current console user must not log off during the backup run because otherwise all active processes (also those that were started by the AT scheduler! Windows NT problem?) will receive the CTRL_LOGOFF_EVENT signal. As a result, the backup terminates with the following error message:
BR261E Program interrupted by signal 15!
The problem was solved in the BRBACKUP/BRARCHIVE version 3.1G.

SAP Note 24101 - Update insurable values

Symptom:

You cannot change insurable values after year-end closing.

    1. Due to a change of the index figures of the previous fiscal year which became known later, you must recalculate the insurable values for the last closed fiscal year.
    You must not do this if only a single year-end closing has been carried out so far and if you want to recalculate the base insurable values for exactly this year. (In this case, apply case 2.)
    2. Due to an incorrect legacy data transfer, the insurable values have not been transferred correctly. A recalculation including the transferred cumulated acquisition and production costs is necessary.
    3. You want to recalculate the insurable values for a new index series or a completely changed index series.
Other terms

Insurable value, Price index, AS02, Index marker, Base value, RAVERS01, Index series, Insurance, RAVRSN00, INSURANCE_VALUE_CALCULATE

Reason and Prerequisites

The function has not been implemented.
The year-end closing should always be executed after indexes have been updated.
If this is not possible, you can carry out the following workaround solution to recalculate the base insurable values. The system then uses the base insurable values to calculate the insurable values (RAVERS01 and master data display).

Solution

The cases described here are generally consulting requests. Therefore we ask for your understanding for the fact that all other questions regarding insurable values that go beyond this note cannot be answered in the frame of SAP Support.

    1. The transactions of the last closed fiscal year must be revaluated with a changed index figure which became known later.

You can deal with this case via the Asset Accounting menu "Tools -> Recalc.base ins.val." (Report RAVRSN00). Please specify the assets for which the insurable values are to be recalculated as exactly as possible.

    2. It is the case of Symptom 2, for example if the insurable values were not calculated by the system from the transferred cumulated acquisition and production costs during old data transfer, yet you still decide on this option on completion of the old data transfer.

You can use the following solution, if you have not yet carried out a year-end closing or carried out at the most one year-end closing in R/3.

  • Copy Report RAVERS01 to ZAVERS01 and apply the enclosed modifications to the copied report.
  • Start Report ZAVERS01. Make sure that case 2 (default) is selected in section 'Calculation in analogy with ...'. As report date, you have to use the beginning of the fiscal year after the legacy data transfer (e.g. legacy data transfer on 12/31/1998 -> report date in program ZAVERS01 is 01/01/1999). In case of a transfer during the year, the report date must be in the year of the legacy data transfer. The system then calculates the base insurable values from the accumulated APC of the fiscal year containing the report date.
  • If you have already carried out a year-end closing, start Report ZAVERS01 again, and enter the fiscal year closing date after the legacy data transfer as report date.
  • After adjusting the base values, you get the insurable values by starting Report RAVERS01 with a report date at the fiscal year end after the date of the legacy data transfer.
    3. If you have already carried out several fiscal year closings but need to carry out a revaluation of the base insurable values with a new index series or a completely changed index series also for the previous years, please proceed as follows (please contact your consultant before using this workaround):
  • Copy Report RAVERS01 to ZAVERS01 and apply the enclosed changes to the copied report.
  • Start Report ZAVERS01. Make sure that case 3 (NOT default) is selected in section 'Calculation in analogy with ...'. The report date is the last day of the closed fiscal year.
  • Carry out these steps for the individual closed fiscal years after the legacy data transfer.


2.3.11

SAP Note 24097 - CO01/CO40:Termination: "ERROR DURING STATUS_UPDATE"

Symptom:

When you create a production order, the system generates error message: "ERROR DURING STATUS_UPDATE" The update was canceled
ABAP processor: SAPSQL_ARRAY_INSERT_DUPREC;
The termination occurred in the ABAP/4 program "SAPLBSVU"

Cause and prerequisites

The copying of sales order data between clients means that objects were transferred with numbers that are higher than the current status of the respective number range objects in the target client. When a new order is created, number assignment according to the status of the number range objects results in double entries.

Solution
You must adapt the status of the number range objects according to the copied data: In the configuration menu of Master Planning (Transaction OLPF) under Master Data -> Order -> Number ranges (Transactions CO80, CO81, CO82, CO83, CY89).
You can transport the statuses of the number range objects from the source client of your copied sales order data into the target client.
However, you should always be careful when changing the number ranges since multiple assignment of the same numbers can result in IRREPARABLE inconsistencies in your system.
You should only ever INCREASE the current status of a number range object !!!
You can determine the highest number status of the respective objects with attached selection report. For the order numbers, you must note that the highest current number status can only be determined correctly if no external number assignment was used.

Additional key words

CO01, CO40, CO41, MD04, VA01, COR1, Create order

SAP Request: How are background jobs distributed to the servers? Other terms Target server Reason and Prerequisites There is some ambiguity as to wh

Symptom:

Although a program runs for what is clearly a long time, the System time field remains at the same value.

Cause and prerequisites

The system time is only occasionally updated (usually only after screen display).

Solution
Use the key word GET TIME, ....

SAP Note 24092 - Distribution of background jobs on application server

Symptom:

Request: How are background jobs distributed to the servers?

Other terms

Target server

Reason and Prerequisites

There is some ambiguity as to what is processed when and where. Jobs are hanging in the status 'released'.

Solution
Processing of jobs with a predefined start time:

On every server with at least one background work process, a background processing scheduler runs periodically (the period is defined by the parameters rdisp/btctime): On every run, this checks whether background work processes are free on its application server. If this is the case, pending jobs are selected from table TBTCS (job queue) and are distributed to the processes according to the following criteria (in order of priority):

    1. Jobs with class A have priority over jobs with class B, which has priority over class C.
    2. Jobs that are especially scheduled for this server have priority over jobs of the same class that are not scheduled for a particular server.
    3. If two jobs are equal after having applied the criteria mentioned above, jobs with a longer waiting time have priority. This gives a maximum job throughput per hour per server (only for short-running jobs) of:
    Jobs/Hour = No. of background processes * 3600 / 'rdisp/btctime'

The background processing schedulers work independently of each other. If a background work process is free on more than one background processing server, the server chosen is the one whose background processing scheduler is randomly activated first.

Processing of jobs with start time "immediately:"
  • Job with target host: The target host is checked immediately, to see whether at least one background work process is free for the required job class. If so, a request then is sent to the host to start the job immediately. If no work process is free, the job is put in the job queue with the current date/time, in the same way as any other job with a predetermined start time.
  • Job without target hosts: A host is randomly chosen from the list of all available hosts where free background work processes are available for the required job class. If no free work processes can be found, the job is also put in the job queue with the current date and time.
Processing of event-started jobs:
  • If an event is triggered in the SAP system, the event scheduler is immediately started. The event scheduler runs on a particular application server (see below). It selects all jobs that have been waiting for the triggered event. The event scheduler can only start jobs on the server on which it is running. If there are insufficient background processing resources on this server, the system changes the remaining jobs to time-controlled jobs.
    Even jobs that have a different target server are changed to time- controlled jobs.

    There are three ways of triggering an event in the SAP System. When an event is triggered, the server on which the event scheduler is running is also specified (explicitly or implicitly):

    1. BP_EVENT_RAISE function
    The TARGET_INSTANCE parameter specifies the server on which the event scheduler is running. If this parameter is empty, the event scheduler runs on the server specified in the rdisp/btcname profile parameter. In this case, the profile parameter is analyzed on the server on which BP_EVENT_RAISE was called.

    2. Transaction SM64
    The system calls BP_EVENT_RAISE internally with an empty TARGET_INSTANCE parameter (see 1).
    In future releases, it may be possible to specify the TARGET_INSTANCE parameter.

    3. sapevt program
    This is a program written and executed in C; it is located by default in the same directory as the kernel executables. If an event is triggered using sapevt, the event scheduler runs on the application server that has been active for the longest time.
Processing of jobs with start time 'After job' or 'At operation mode'.
  • Both start conditions are executed using events, so the system behaves in exactly the same way as with event-started jobs.
Note:
  • When defining operation modes (RZ04), you can reserve one or more background work processes for jobs with class A.
    This is done as follows: RZ04 -> "New operation mode" -> save -> doubleclick on the name of the operation mode -> "New instance" -> "Current settings" -> cursor to "Job-Cl.-A" -> "More" -> save.
    The individual background work processes will still be equal. Reserving n background work processes for jobclass A means that jobs of class B and C will only run on this server if there are at least n+1 free background work processes.
    The number of background work processes reserved for job class A must of course be smaller than the total number of background work processes (shown on the same screen); otherwise jobs of classes B and C won't run. The new operation mode can only be activated if it is scheduled with Transaction SM63.
  • Note concerning the workload:
    Since the job schedulers run independently on each application server, a job WITHOUT a target computer can be taken from any scheduler and run on the corresponding application server. Thus, the workload is distributed equally on all servers.
If the jobs you plan always have a defined start time and want free work processes on several servers, it is possible that one server is used more than the others. Imagine this situation: The batch scheduler on two separate servers is set to 60 seconds. When the scheduler on server A always becomes active at xx:xx:10 and the one on server B at xx:xx:20, server A will always come to the fore, since background jobs are planned for full minutes. If, for any reason, you want to divide the jobs equally between two servers, you will need to change the parameter rdisp/btctime: e.g., 61 seconds for server A and 62 seconds for server B.

Each scheduler distributes as many jobs as there are background work processes on the corresponding application server. When the scheduler is running, the system load on the respective application server is not considered. Therefore the number of configured background work processes should not cause any performance problems - even if all background processes are used

SAP Note 24084 - Customer hierarchy: Time-out error during transaction start

Symptom:

When displaying or maintaining customer hierarchy data, a time-out error occurs at the start of the transaction if too many records are stored in the hierarchy.

Cause and prerequisites

The entire table is read at the start of the transaction as a check.

Solution
The problem can be solved as of Release 2.2F (correction P22K007808) by creating additional selection parameters and as of Release 2.2G/3.0B with further tuning measures.
The tuning measures only apply to the following items 2.2 and 2.3 (form READ_KNVH_LINKS and form READ_KNVH_START).
For Releases 2.2F and 3.0A, only items 2.2 and 2.3 are relevant, i.e. you must change the coding in both routines. For these releases, you must also change module D0002_CHECK (see item 3) which is relevant for Release 3.0 as well.
The same applies if you have already installed the original note in Releases < 2.2F.

Carry out the following steps (if they are not already present in your release).

1. SE38 / Report RVKNVH00 / Change text elements / process selection texts / create the following new parameters:

KUNNRX / Debitoren
VKORGX / Verkaufsorganisationen
VTWEGX / Vertriebswege
SPARTX / Sparten (Do not delete German text. DMK)

KUNNRX / Customers
VKORGX / Sales organizations
VTWEGX / Distribution channels
SPARTX / Divisions

If you require the selection text in a foreign language, you must first
maintain the original German text using SE38. With Transaction SE63,
you can then translate the text into the required language.

2. SE38 / RVKNVH00 / Source text in order to expand the following rou-
tines:
2.1: Form NODE_NEW_CHECK
2.2: Form READ_KNVH_LINKS
2.3: Form READ_KNVH_START

These routines can be placed at the end of the report and must appear
as follows:

2.1. NODE_NEW_CHECK:

FORM NODE_NEW_CHECK USING S_KUNNR S_VKORG S_VTWEG S_SPART.
CHECK NOT S_KUNNR IS INITIAL.
SUBRC = 4.
SELECT * FROM KNVH INTO KNVH WHERE HITYP = SAVE_HITYP
AND KUNNR = S_KUNNR
AND VKORG = S_VKORG
AND VTWEG = S_VTWEG
AND SPART = S_SPART.
CHECK KNVH-DATBI IS INITIAL
OR KNVH-DATBI GE SAVE_DATUM
OR KNVH-DATBI GE SY-DATUM.
CLEAR SUBRC.
EXIT.
ENDSELECT.
IF SUBRC IS INITIAL.
LOOP AT YKNVH WHERE KUNNR = KNVH-KUNNR
AND VKORG = KNVH-VKORG
AND VTWEG = KNVH-VTWEG
AND SPART = KNVH-SPART
AND DATAB = KNVH-DATAB.
EXIT.
ENDLOOP.
IF SY-SUBRC IS INITIAL.
EXIT.
ELSE.
MESSAGE E092 WITH S_KUNNR S_VKORG S_VTWEG S_SPART.
ENDIF.
ELSE.
SELECT * FROM KNVH WHERE HITYP = SAVE_HITYP
AND HKUNNR = S_KUNNR
AND HVKORG = S_VKORG
AND HVTWEG = S_VTWEG
AND HSPART = S_SPART.
CHECK KNVH-DATBI IS INITIAL
OR KNVH-DATBI GE SAVE_DATUM
OR KNVH-DATBI GE SY-DATUM.
CLEAR SUBRC.
EXIT.
ENDSELECT.
CHECK SUBRC IS INITIAL.
LOOP AT YKNVH WHERE KUNNR = KNVH-KUNNR
AND VKORG = KNVH-VKORG
AND VTWEG = KNVH-VTWEG
AND SPART = KNVH-SPART
AND DATAB = KNVH-DATAB.
EXIT.
ENDLOOP.
IF SY-SUBRC IS INITIAL.
EXIT.
ELSE.
MESSAGE E092 WITH S_KUNNR S_VKORG S_VTWEG S_SPART.
ENDIF.
ENDIF.
ENDFORM.

2.2: READ_KNVH_LINKS:

FORM READ_KNVH_LINKS USING S_KUNNR S_VKORG S_VTWEG S_SPART.
CHECK NOT S_KUNNR IS INITIAL.
IF XKNVV-BOKRE IS INITIAL.
SELECT * FROM KNVH INTO KNVH WHERE HITYP = SAVE_HITYP
AND KUNNR = S_KUNNR
AND VKORG = S_VKORG
AND VTWEG = S_VTWEG
AND SPART = S_SPART
AND ( NOT KUNNR IN KUNNRX
OR NOT VKORG IN VKORGX
OR NOT VTWEG IN VTWEGX
OR NOT SPART IN SPARTX )
AND ( NOT HKUNNR IN KUNNRX
OR HKUNNR = *KNVH-KUNNR
OR NOT HVKORG IN VKORGX
OR NOT HVTWEG IN VTWEGX
OR NOT HSPART IN SPARTX )
AND ( DATBI GE SY-DATUM
OR DATBI GE SAVE_DATUM
OR DATBI = *KNVH-DATBI )
ORDER BY PRIMARY KEY.
LOOP AT YKNVH WHERE KUNNR = KNVH-KUNNR
AND VKORG = KNVH-VKORG
AND VTWEG = KNVH-VTWEG
AND SPART = KNVH-SPART
AND DATAB = KNVH-DATAB.
EXIT.
ENDLOOP.
CHECK NOT SY-SUBRC IS INITIAL.
MOVE-CORRESPONDING KNVH TO YKNVH.
MOVE-CORRESPONDING KNVH TO XKNVH.
APPEND XKNVH.
APPEND YKNVH.
ENDSELECT.
ENDIF.
IF XKNVV-PRFRE IS INITIAL.
SELECT * FROM KNVH INTO KNVH WHERE HITYP = SAVE_HITYP
AND HKUNNR = S_KUNNR
AND HVKORG = S_VKORG
AND HVTWEG = S_VTWEG
AND HSPART = S_SPART
AND ( NOT KUNNR IN KUNNRX
OR NOT VKORG IN VKORGX
OR NOT VTWEG IN VTWEGX
OR NOT SPART IN SPARTX )
AND ( NOT HKUNNR IN KUNNRX
OR NOT HVKORG IN VKORGX
OR NOT HVTWEG IN VTWEGX
OR NOT HSPART IN SPARTX )
AND ( DATBI GE SY-DATUM
OR DATBI GE SAVE_DATUM
OR DATBI = *KNVH-DATBI )
ORDER BY PRIMARY KEY.
LOOP AT YKNVH WHERE KUNNR = KNVH-KUNNR
AND VKORG = KNVH-VKORG
AND VTWEG = KNVH-VTWEG
AND SPART = KNVH-SPART
AND DATAB = KNVH-DATAB.
EXIT.
ENDLOOP.
CHECK NOT SY-SUBRC IS INITIAL.
MOVE-CORRESPONDING KNVH TO YKNVH.
MOVE-CORRESPONDING KNVH TO XKNVH.
APPEND XKNVH.
APPEND YKNVH.
ENDSELECT.
ENDIF.
ENDFORM.

2.3: READ_KNVH_START:

FORM READ_KNVH_START.
DATA: SELECTION(1) TYPE C.
READ TABLE KUNNRX INDEX 1.
IF NOT SY-SUBRC IS INITIAL.
READ TABLE VKORGX INDEX 1.
IF NOT SY-SUBRC IS INITIAL.
READ TABLE VTWEGX INDEX 1.
IF NOT SY-SUBRC IS INITIAL.
READ TABLE SPARTX INDEX 1.
ENDIF.
ENDIF.
ENDIF.
IF SY-SUBRC IS INITIAL.
SELECTION = 'X'.
ELSE.
CLEAR SELECTION.
ENDIF.
CLEAR *KNVH-DATBI.
SELECT * FROM KNVH INTO KNVH WHERE HITYP = SAVE_HITYP
AND KUNNR IN KUNNRX
AND VKORG IN VKORGX
AND VTWEG IN VTWEGX
AND SPART IN SPARTX
AND ( DATBI GE SY-DATUM
OR DATBI GE SAVE_DATUM
OR DATBI = *KNVH-DATBI )
ORDER BY PRIMARY KEY.
MOVE-CORRESPONDING KNVH TO YKNVH.
MOVE-CORRESPONDING KNVH TO XKNVH.
APPEND XKNVH.
APPEND YKNVH.
LOOP AT XKNVV WHERE KUNNR = KNVH-KUNNR
AND VKORG = KNVH-VKORG
AND VTWEG = KNVH-VTWEG
AND SPART = KNVH-SPART.
EXIT.
ENDLOOP.
IF NOT SY-SUBRC IS INITIAL.
CLEAR XKNVV.
XKNVV-KUNNR = KNVH-KUNNR.
XKNVV-VKORG = KNVH-VKORG.
XKNVV-VTWEG = KNVH-VTWEG.
XKNVV-SPART = KNVH-SPART.
XKNVV-BOKRE = 'X'.
APPEND XKNVV.
ENDIF.
ENDSELECT.
IF SELECTION IS INITIAL.
REFRESH XKNVV.
CLEAR: XKNVV, WKNVH.
ENDIF.
CHECK NOT SELECTION IS INITIAL.
CLEAR *KNVH-KUNNR.
SELECT * FROM KNVH INTO KNVH WHERE HITYP = SAVE_HITYP
AND HKUNNR IN KUNNRX
AND NOT HKUNNR = *KNVH-KUNNR
AND HVKORG IN VKORGX
AND HVTWEG IN VTWEGX
AND HSPART IN SPARTX
AND ( NOT KUNNR IN KUNNRX
OR NOT VKORG IN VKORGX
OR NOT VTWEG IN VTWEGX
OR NOT SPART IN SPARTX )
AND ( DATBI GE SY-DATUM
OR DATBI GE SAVE_DATUM
OR DATBI = *KNVH-DATBI )
ORDER BY PRIMARY KEY.
LOOP AT YKNVH WHERE KUNNR = KNVH-KUNNR
AND VKORG = KNVH-VKORG
AND VTWEG = KNVH-VTWEG
AND SPART = KNVH-SPART
AND DATAB = KNVH-DATAB.
EXIT.
ENDLOOP.
IF NOT SY-SUBRC IS INITIAL.
MOVE-CORRESPONDING KNVH TO YKNVH.
MOVE-CORRESPONDING KNVH TO XKNVH.
APPEND XKNVH.
APPEND YKNVH.
ENDIF.
LOOP AT XKNVV WHERE KUNNR = KNVH-HKUNNR
AND VKORG = KNVH-HVKORG
AND VTWEG = KNVH-HVTWEG
AND SPART = KNVH-HSPART.
IF XKNVV-PRFRE IS INITIAL.
XKNVV-PRFRE = 'X'.
MODIFY XKNVV.
ENDIF.
EXIT.
ENDLOOP.
IF NOT SY-SUBRC IS INITIAL.
CLEAR XKNVV.
XKNVV-KUNNR = KNVH-HKUNNR.
XKNVV-VKORG = KNVH-HVKORG.
XKNVV-VTWEG = KNVH-HVTWEG.
XKNVV-SPART = KNVH-HSPART.
XKNVV-PRFRE = 'X'.
APPEND XKNVV.
ENDIF.
ENDSELECT.
CLEAR INDEX.
DO.
ADD 1 TO INDEX.
READ TABLE XKNVH INDEX INDEX.
IF NOT SY-SUBRC IS INITIAL.
EXIT.
ELSE.
MOVE-CORRESPONDING XKNVH TO WKNVH.
ENDIF.
LOOP AT XKNVV WHERE KUNNR = WKNVH-KUNNR
AND VKORG = WKNVH-VKORG
AND VTWEG = WKNVH-VTWEG
AND SPART = WKNVH-SPART.
TABIX = SY-TABIX.
EXIT.
ENDLOOP.
IF NOT SY-SUBRC IS INITIAL
OR XKNVV-BOKRE IS INITIAL
OR XKNVV-PRFRE IS INITIAL.
IF NOT SY-SUBRC IS INITIAL.
CLEAR XKNVV.
ENDIF.
PERFORM READ_KNVH_LINKS USING WKNVH-KUNNR WKNVH-VKORG
WKNVH-VTWEG WKNVH-SPART.
IF XKNVV IS INITIAL.
MOVE-CORRESPONDING WKNVH TO XKNVV.
XKNVV-BOKRE = 'X'.
XKNVV-PRFRE = 'X'.
APPEND XKNVV.
ELSE.
XKNVV-BOKRE = 'X'.
XKNVV-PRFRE = 'X'.
MODIFY XKNVV INDEX TABIX.
ENDIF.
ENDIF.
CHECK NOT WKNVH-HKUNNR IS INITIAL.
CLEAR TABIX.
LOOP AT XKNVV WHERE KUNNR = WKNVH-HKUNNR
AND VKORG = WKNVH-HVKORG
AND VTWEG = WKNVH-HVTWEG
AND SPART = WKNVH-HSPART.
TABIX = SY-TABIX.
EXIT.
ENDLOOP.
IF NOT SY-SUBRC IS INITIAL
OR XKNVV-BOKRE IS INITIAL
OR XKNVV-PRFRE IS INITIAL.
IF NOT SY-SUBRC IS INITIAL.
CLEAR XKNVV.
ENDIF.
PERFORM READ_KNVH_LINKS USING WKNVH-HKUNNR WKNVH-HVKORG
WKNVH-HVTWEG WKNVH-HSPART.
XKNVV-BOKRE = 'X'.
XKNVV-PRFRE = 'X'.
IF TABIX IS INITIAL.
XKNVV-KUNNR = WKNVH-HKUNNR.
XKNVV-VKORG = WKNVH-HVKORG.
XKNVV-VTWEG = WKNVH-HVTWEG.
XKNVV-SPART = WKNVH-HSPART.
APPEND XKNVV.
ELSE.
MODIFY XKNVV INDEX TABIX.
ENDIF.
ENDIF.
ENDDO.
REFRESH XKNVV.
CLEAR: XKNVV, WKNVH.
ENDFORM.

3. SE38 / RVKNVH00 / Change source text as follows:

REPORT RVKNVH00
NO STANDARD PAGE HEADING
LINE-SIZE 132
MESSAGE-ID VC.
TABLES: ...
DATA: ...
...
SELECTION-SCREEN SKIP 1.
PARAMETERS: S_HITYP LIKE THIOZ-HITYP OBLIGATORY
MEMORY ID VHT,
S_DATUM LIKE SY-DATUM OBLIGATORY
DEFAULT SY-DATUM.

>>>>>>>>>>>>> Beginning of new lines <<<<<<<<<<<<<<<<<<<<<<<<<

SELECTION-SCREEN ULINE.
SELECT-OPTIONS: KUNNRX FOR KNVH-KUNNR,
VKORGX FOR KNVH-VKORG,
VTWEGX FOR KNVH-VTWEG,
SPARTX FOR KNVH-SPART.

>>>>>>>>>>>>> End of new lines <<<<<<<<<<<<<<<<<<<<<<<<<<<
...
...
MODULE D0002_CHECK.
...
CASE SAVE_UCOMM.
WHEN 'KDET'.
...
WHEN 'KNEU'.

*------ Zuordnung prüfen ------------------------------
PERFORM ZUORD_CHECK_1.
IF NOT SUBRC IS INITIAL.
...
ELSE.

>>>>>>>>> Beginning of new lines <<<<<<<<<<<<<<<<<<<<<<<<<<<

MOVE-CORRESPONDING KNVH TO WKNVH.
PERFORM NODE_NEW_CHECK USING WKNVH-KUNNR WKNVH-VKORG
WKNVH-VTWEG WKNVH-SPART.
IF NOT WKNVH-HKUNNR IS INITIAL
AND SAVE_STUFE IS INITIAL. <-- 3.0A+B, 2.2A-F
PERFORM NODE_NEW_CHECK USING WKNVH-HKUNNR WKNVH-HVKORG
WKNVH-HVTWEG WKNVH-HSPART.
ENDIF.
MOVE-CORRESPONDING WKNVH TO KNVH.

>>>>>>>>>> End of new lines <<<<<<<<<<<<<<<<<<<<<<<<<<<<<
...
ENDIF.
...
WHEN 'KUEB'.

*------ Zuordnung prüfen --------------------------------
PERFORM ZUORD_CHECK_1.
IF NOT SUBRC IS INITIAL.
...
ELSE.

>>>>>>>>>>> Beginning new lines <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

MOVE-CORRESPONDING KNVH TO WKNVH.
PERFORM NODE_NEW_CHECK USING WKNVH-HKUNNR WKNVH-HVKORG
WKNVH-HVTWEG WKNVH-HSPART.
MOVE-CORRESPONDING WKNVH TO KNVH.

>>>>>>>>>>> End of new lines <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
...
ENDIF.
...
WHEN 'KUNT'.

*------ Zuordnung prüfen ------------------------------
PERFORM ZUORD_CHECK_1.
IF NOT SUBRC IS INITIAL.
...
ELSE.

>>>>>>>>>>>> Beginning of new lines <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

MOVE-CORRESPONDING KNVH TO WKNVH.
PERFORM NODE_NEW_CHECK USING WKNVH-KUNNR WKNVH-VKORG
WKNVH-VTWEG WKNVH-SPART.
MOVE-CORRESPONDING WKNVH TO KNVH.

>>>>>>>>>>>> End of new lines < < <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
...
ENDIF.
ENDCASE.
ENDMODULE.
...
FORM READ_TABLES.
DATA: ...
...
*------ Abgelaufene Zuordnungen nicht anzeigen -----------------
PERFORM READ_KNVH_START. <--- new line

>>>>>>> Mark the following lines with an asterisk <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

* SELECT * FROM KNVH INTO KNVH WHERE HITYP = SAVE_HITYP.
* CHECK KNVH-DATBI IS INITIAL
* OR KNVH-DATBI GE SAVE_DATUM
* OR KNVH-DATBI GE SY-DATUM.
* MOVE-CORRESPONDING KNVH TO YKNVH.
* MOVE-CORRESPONDING KNVH TO XKNVH.
* APPEND XKNVH.
* APPEND YKNVH.
* ENDSELECT.

>>>>>>> End of asterisk marking <<<<<<<<<<<<<<<<<<<<<<<<<<<<
...
ENDFORM.
4. Create new message VC092:

SM31 / Table T100 / Message class 'VC' -> Message number 092: Create
with the following text:

'Nodes & & & & cannot to be allocated because they were not selected'

Maintain the following long text:

Diagnosis
For the node to be newly allocated, there are active allocations which
are not contained in the selection criteria and whose hierarchical
structures were therefore not read. In order to avoid
incorrect allocations, do not allocate these nodes.
Procedure
In order to be able to allocate the new node, it must be present in
the selected hierarchical structure. Therefore, select the transaction
again and expand the selection criteria to include the node in question.

SAP Note 24081 - Cash Management and Forecast: Meaning of expiration date

Symptom:

This note applies to R/2 and R/3:
The meaning of the expiration date for the memo records (payment advice notes and planned items) in cash management and forecast causes difficulties in understanding because in the display of the cash management position/liquidity forecast, the memo records do not disappear although the expiration date is exceeded.
In addition, the risks which are affiliated with the usage of the expiration date are explained.

Other terms

Expiration date, FF7A, FF7B, payment advice

Reason and Prerequisites

Logic of the expiration date

Solution

The expiration date for the memo records causes the following in cash position, liquidity forecast and also for cash concentration:
If today's date is earlier than or equal to the expiration date, the record is selected.
If today's date is later than the expiration date, the record is not selected.
For example, if the record expires tomorrow, it is selected and appears in the cumulative display as of the planning date and also remains in all the following amount columns, thus also on those days that are later than the expiration date. In the delta display, the amount appears only for the planned date.
If the record expired yesterday, it is not selected.
If the record expires tomorrow, why does it still appear in the display the day after tomorrow?
The reason is that it is assumed that a record which expires tomorrow is replaced by a posting the day after tomorrow, that is, a smooth transition from the memo record to the posting occurs.
Example:
Time deposit investment from 01/01/1995 to 02/01/1995, expiration date 02/01/1995
The system assumes that the due fixed-term deposits appears on the account statement of 02/02/1995 and is also included in cash management and forecast on 02/02/1995 via the posting.
The amount then appears in the cash management position either as a memo record (if today's date is 02/01/1995 or 01/31/1995, and so on) or the amount appears in the form of the posting (if today's date is 02/02/1995 or 02/03/1995, and so on).
The memo record must therefore be displayed until it is replaced by the posting and must therefore even still appear in the display if the display date is later than the expiration date because otherwise the amount would not remain without gaps.
Risks involved in the use of the expiration date:
If you use the expiration date you do not have to remove the memo records which were replaced by postings manually or automatically, but you risk that a too early or too late posting falsifies cash management and forecast.
If, in the above example, the posting already appears in the account statement of 02/01/1995, the amount exists twice in cash management and forecast on 02/02/1995 because it is not until 02/02/1995 that the memo record is no longer selected. In this case, you must archive the memo record manually or automatically just as it is to be done with the memo records without expiration date.
However, if the posting appears as late as in the account statement of 02/03/1995, the amount is missing in cash management and forecast on 02/02/1995 because the memo record is no longer selected and the posting is not available yet. In this case, it is of little use if the posting is made on 02/03/1995 to 02/01/1995 correctly dependent on value date because you planned using incorrect numbers on 02/02/1995.
Therefore, you should use the expiration date only if the date at which the posting appears on the account statement is known for sure. In this case, the expiration date is to be set a day before this date in order to ensure the continuous transition.

If the amount is to disappear from the display of the cash management position or liquidity forecast after the expiration date has expired, for example to illustrate a temporarily granted credit limit, you can achieve this by entering two payment advice notes:

  • Define a new planning type for illustrating the credit limit.
  • For example, if you want to illustrate a credit limit granted for the entire month of October, enter the first payment advice note as of October 01 and the offsetting payment advice note with negative amount as of November 01.
  • If you use the expiration date for this planning type, both payment advice notes must have the same expiration date and in the above example, the date must be later than or equal to the last day of October.
  • If you do not use any expiration date, the payment advice notes should be archived as soon as they are no longer required.
  • If one of the two payment advice notes is changed, the other one must also be changed correspondingly.

SAP Note 24080 - Create order with reference - Address changes

Symptom:

Transaction VA01
In creating an order with reference to another order, the changes of the addresses of the partner are taken over into the original document if an address change already took place in the original document.

Solution
Please choose the following method in order creation with reference in
case address data was changed in the original document:
- Create order (VA01) and newly enter the ordering party in the order
entry screen.
-> Sales document -> Create order with reference ...

SAP Additional key words AAPO123

Symptom:

With the bill of exchange charges statement, the error messages FB563
and FB827 are generated, although the document is O.K.

Cause and prerequisites

Small difference due to different calculation.

Solution
Corrected in the standard system in Release 4.6A.

Advance correction:

Program RFKORD20:

If activated deactivate the parameter Fixed point arithmetic using Transaction /NSE38 in the attributes.

SAP Note 24065 - AA641 or fixed asset not deactivated f.complete retirement

Symptom:

For complete retirement on fixed assets with an indexed depreciation area, the system might generate error message AA641 "Net book value negative in area &" or a positive net book value remains after asset retirement posting.The latter results in the fixed asset not being deactivated despite the complete retirement.
The error may also occur for fixed assets, which had a partial retirement before change of the index in the current year.
Key words: Retirement date, revaluation, replacement value

Cause and prerequisites

Change the index series, without depreciation recalculation

Solution
Reverse retirement, if posted.Via master data maintenance carry out a 'Recalculate values'. Post retirement (again).

Additional key words

AAPO123

SAP Note 24059 - Fast entry: Error F4655 when inserting

Symptom:

When generating variants of the fast entry, the error F4655 (not enough space) occurs when inserting a new field.
However, the variant can be created again in unchanged form.
Key words: SAPDFKA6 OT43 OT45 FAKP T021D T021F T021I

Cause and prerequisites

Error.

Solution
Correction for Releases 2.2F/3.0A.
Advance correction:
/NSE38 - SAPDFKA6
FORM AT021I_EINFUEGEN.
...
* REFE1 = REFE1 + VORTAB-LENG + 1. <-- delete
REFE1 = REFE1 + VORTAB-LENG. <-- insert

* ------ Noch Platz für ausgewähltes Feld? -----------
IF REFE1 > CONST-MAXCO.
MESSAGE S655 WITH REFE2 VORTAB-LENG CONST-MAXCO.
PERFORM STEHENBLEIBEN.
ENDIF.
...

SAP Note 24057 - Freespace requirements 3.0 FCS

Symptom:

Freespace requirement for 3.0 FCS Upgrade

Cause and prerequisites

nn

Solution
In 3.0 FCS, the following freespace is required:
Tablespace Free space
PSAPES300D 1.4 GB
PSAPES300I 0.55 GB
PSAPEL300D 0.4 GB
PSAPEL300I 30 MB
PSAPBTABD 90 MB
PSAPBTABI 90 MB
PSAPCLUD 2 MB
PSAPCLUI 1 MB
PSAPDDICD 13 MB
PSAPDDICI 3 MB
PSAPDOCUD 2 MB
PSAPDOCUI 1 MB
PSAPLOADD 1 MB
PSAPLOADI 1 MB
PSAPPOOLD 205 MB
PSAPPOOLI 135 MB
PSAPPROTD 23 MB
PSAPPROTI 3 MB
PSAPSOURCED 6 MB
PSAPSOURCEI 1 MB
PSAPSTABD 120 MB
PSAPSTABI 110 MB
PSAPTEMP 80 MB
SYSTEM 50 MB

By carrying out some reorganization after the upgrade, you can regain more than 1 GB. This reorganization is only necessary after the first upgrade with the new repository switch.

SAP Note 24000 - Tape always ejects on AT&T 3416 Server Machine

Symptom:

Tape always ejects after insertion in Wang DAT Tape drive in AT&T 3416.

Cause and prerequisites

Tape drive does not support the use of 120 meter / 4MM DAT Tapes.

Solution
Use 90 meter or 60 meter 4mm dat tapes.

1.3.11

SAP Note 23995 - Cut and Paste in the SAPScript Editor

Symptom:

How can the automatic formatting in the SAPscript editor be suppressed?
Problem: If you use Cut and Paste to copy a text where line breaks are important (for example: ABAP/4 source code), these line breaks are distorted by the automatic formatting, and the text becomes illegible.

Cause and prerequisites

The automatic formatting feature in the editor is user-friendly, but it can unfortunately be counterproductive in some cases.

Solution
A workaround does exist: upload the file. Here, "/" is automatically set by the editor for every line.
If you really want to use the Cut & Paste feature, you must first provide every line with a "/" (for line break) by pressing F6 as often as required and then transfer the text. You can make life easier for yourself by first generating several lines with "/", and then duplicating these lines with the help of the SAPscript Editor: mark the beginning and the end by double-clicking, press "Copy" and then "Paste" often as required.
As of Release the Cut&Paste feature in the new SAPsript editor is supported like a computer editor.

Additional key words

SAPscript, editor, cut, paste

SAP Note 23993 - Incorrect data in reporting

Symptom:

The data displayed after executing a report is partially incorrect.

Cause and prerequisites

The incorrect data in the report can be caused by two errors:

    1. Program error
    2. Incorrect settings for the report parameters
Solution

Go through the following steps individually to verify incorrect data in the report:

    1. Step: Check formatting ======================


First perform the incorrect report and then display the incorrect value in the overview list or the detail list. Now choose 'Formatting on/off' under the menu option 'Settings' (as of Release 3.0) or the function 'Display on/off' (up to and including Release 2.2).
The function shows the decimal point formats that apply to the respective report.

Make sure that the incorrectly displayed values do not result from a roundoff!

Example:
The number value in the report is 1233.35 DM.
The report is made according to the decimal point format in units of DM 10,000 without any decimal places.
As a result, the value displayed in the report is zero!


    2. Step: Create an AD-HOC report for checking the selection criteria ===================================================================


This procedure is advisable for reports which form the basis of a (complex) form.

Create an AD-HOC report for each incorrect number value according to the following template:

      a)

Perform the report with the incorrect data.
Then choose 'Report parameters' (menu option 'Extras'). Now copy the listed characteristics (and key figures) including their functional specifications into the AD-HOC report.

      b)

Search for the cell to be assigned to the incorrect value in the report in the underlying form.
(The easiest way to find this cell is to compare the columns and lines belonging to the incorrect value in the detail list in the report with the cells in the form)

      c)

Check whether exceptions are defined for the cell (double-click on the cell in question).
If yes, copy the characteristics and key figures including their restrictions into the AD-HOC report.
If no, copy the characteristics and key figures including their restrictions from the form assigned to the cell.

      d)

Copy the values for the characteristics from the general selections (menu option 'Edit', function 'General selections --> Change') into your AD-HOC report.


Now execute the AD-HOC report created this way and compare the result with the incorrect number value from the initial report.
If the results are the same, there are no incorrect values.

    3. Step: Check available notes

==========

The following notes concerning incorrect data in reporting are already available:

Release 2.1*:
-- 0010328 CO-BOC: Data is missing in some reports
-- 0010331 CO-BPC: Incorrect calculation (Addition)
-- 0010457 Problems with PERDE
-- 0013595 No data found, KEYs contain SPACE (2.1A-2.1F)
-- 0013631 Data is missing in large row/column structures
-- 0015489 Drill-down reporting: Error with lines of the form =Ynnn
-- 0017680 Reverse +/- sign in line/column structure (2.1A-2.1J)
-- 0019703 Incorrect data in the segment level (2.1A-2.1Z)
-- 0023019 Drill-down reporting: Line items missing COBPC2 (2.1H-2.1K)
-- 0026934 Drill-down rep.: incorr.calc.comps. f. 1Dim w.ID (2.1A-2.1K)

Release 2.2*:
-- 0008729 KE30: Quantities and values are added/multiplied (*)
-- 0013595 COBPC: No data found, KEYs contain SPACE (2.2A)
-- 0017660 drill-down COBPC2 Incorrect values and exception cells
(2.2A-2.2D)
-- 0017680 reverse +/- sign in line/column structure (2.2A-2.2D)
-- 0017733 commitment COPA3 incorrect figures (2.2A-2.2D)
-- 0019235 Drill-down reporting: incorrect key figure calculat
(2.2A-2.2D)
-- 0019703 Incorrect data in the segment level (2.2A-2.2G)
-- 0021539 Miss.no. for rep. covering more than one fisc.yr.
(2.2A-2.2E)
-- 0023019 Drill-down reporting: Line items missing COBPC2 (2.2A-2.2E)
-- 0026934 Drill-down rep.: incorr.calc.comps. f. 1Dim w.ID (2.2A-2.2F)
-- 0028993 drill-down report: Wrong data if value types differ
(2.2A-2.2F)
-- 0033688 Incorrect numbers: all cells special cells (2.2A-2.2G)
-- 0038107 Number variables: Incorrect replacement (characteris
(2.2A-2.2G)
-- 0040536 Large form: incorrect numbers; KH125 (2.2a-2.2g)
-- 0046470 Division problems caused by rounding differences (2.2A-2.2H)
-- 0048321 Drill-down reporting: incorrect data selection (2.2A-2.2H)

Release 3.0*:
-- 0019703 Incorrect data in the segment level (3.0A-3.0B)
-- 0026934 Drill-down rep.: incorr.calc.comps. f. 1Dim w.ID (3.0A)
-- 0028993 Drill-down report: Wrong data if value types differ (3.0A)
-- 0033688 Incorrect numbers: all cells special cells (3.0A-3.0B)
-- 0034285 Form: KH253 (recursive formulae) (3.0A-3.0C)
-- 0034476 Incorr.figures: foreign curr.w/o decimal places (3.0C)
-- 0034896 Incorr.figures: compnts. w. characteristic sel. (3.0A-3.0B)
-- 0036902 Drill-down rep.: Value display w. incorr. factor (3.0A-3.0B)
-- 0038107 Number variables: Incorrect replacement (characteristic)
(3.0A-3.0E)
-- 0038789 Wrong compounding of general selection conditions
(3.0A-3.0E)
-- 0040536 Large form: incorrect numbers; KH125 (3.0A-3.0D)
-- 0040647 Drill-down: Incorrect numbers after text change (3.0A-3.0D)
-- 0041024 Drill-down report: too many 'x' on detail list (3.0D)
-- 0041675 Drill-down rep.: Hierar.node compound criteria (3.0D)
-- 0041747 Drilldown: Characteristic value '#' does not work (3.0D)
-- 0043244 Drill-down: CONVT_OVERFLOW in SAPMKCBE (3.0A-3.0D)
-- 0046470 Division problems caused by rounding differences (3.0A-3.0E)
-- 0046513 Incorr. numbers: foreign currency w/o dec. places
(3.0C-3.0E)
-- 0047607 Error when navigating (3.0E)
-- 0047634 Optional node variable (3.0D-3.0E)
-- 0047723 Wrong figures: variable in several columns (3.0C-3.0E)
-- 0048097 Hierarchy node: Node selection is not correct (3.0D-3.0E)
-- 0048158 Drill-down for several hierarchies (3.0A-3.0E)
-- 0050721 Incorrect numbers in online mode and when printing
(3.0A-3.0E)
-- 0050727 Drill-down: Inc.nos for ownership list %S, %T (3.0D-3.0E)
-- 0051099 Drill-down: Too many selection criteria sent
via report/report interface (3.0B-3.0E)
-- 0051857 Reporting: Inc. numbers/no records selected (3.0A-3.0E)
-- 0052332 Inc.nos.: Cells w.special key figure selection (3.0A-3.0E)
-- 0062091 Drill-down rep.: incorr. replaced number variables
(3.0A-3.0E)
-- 0064839 Drill-down rep.: wrong numbers because of inc. sel. (3.0C)
-- 0067390 Drill-down reporting: navigation error (3.0D-3.0F)
-- 0070584 Incorrect data: Hierarchy node for sets (3.0D-3.0F)
-- 0071827 Drill-down rep., non-cumulative values, values = 0
(3.0F-3.1G)
-- 0071943 Drill-down rep: Form.prior. w. spec.cells in formu.
(3.0A-3.1G)
-- 0072646 Incorrect numbers for factual aggregation ne SUM (3.0A-3.1G)
-- 0075000 Incorrect numbers with complicated key figures (3.0A-3.1G)
-- 0097694 Incorrect nos for complicated key figures; KH264 (3.0A-3.1G)
-- 0075486 Incorrect list for saved data (3.0D-3.1G)
-- 0075835 Incorrect numbers with temporal aggregation AV0 CNT
(3.0D-3.1G)
-- 0076373 Wrong numbers during elim. of int. business volume
(3.0F-3.1G)
-- 0078755 Missing numbers for individual characteristic values
3.0D with Hot Package 19 or 3.0F with Hot Package 4 or
3.1G up to 3.1H
-- 0083094 Incorrect data for hierarchy nodes (sets) (3.0D-3.1H)
-- 0083346 Wrong data after navigation and drill-down change
(3.0D-3.1H)
-- 0084462 Drill-dwn rep.: 7-digit period selec. via intervals
(3.0A-3.1H)
-- 0087978 Incorrect selections for view aspects (3.1G-3.1H)
-- 0088293 Incorrect numbers for complicated key figures (3.0E-3.1H)
-- 0088295 Drill-down report: incorr data, report line struct.
(3.0D-3.1H)
-- 0095099 Drill-dwn rep.:incorr. values for hierarchy nodes(3.0D-4.0A)
-- 0092079 Drilldwn rep.: incorrect Nos. for aggregation AV0(3.0D-4.0A)
-- 0089564 Drill-down rep: Error in aggreg. not equal to SUM(3.0D-4.0A)
-- 0097745 Drill-dwn rep.:incorrect numbers when navigating (3.0D-4.0B)
-- 0053023 Drilldwn rep.: wrong numb. for large data amounts(3.0E-3.1I)
-- 0101557 Drill-down reporting: cost element node in form (3.1G-4.0B)
-- 0112339 Drill-down rep.: Incorr. fig. f. aggreg. MAX, MIN(3.0F-4.0B)

Notes that are only valid for individual applications:
======================================================

  • CO-PA (or IS-B)

-- 0050806 Drill-down rep.: incorrect figures for calculation schema
(2.2A-2.2H, 3.0A-3.0E)
-- 0060118 COPA: incorrect numbers from summarization levels (3.0B-3.0C)

  • EIS
-- 0046526 Drill-down rep.: Figures = zero (only in 3.0C)
-- 0053023 Drill-down rep.: wrong numb. for large data amounts (3.0E)

Additional key words

Drill-down reporting, KE30, KCR0, information; overview note; SLCSInfo

SAP Note 23985 - Printing name and address in RPCKTOx0

Symptom:

In the wages account, the current name or the current address are not displayed.

Cause and prerequisites

The data selection period (PN/BEGDA and PN/ENDDA) positions infotypes 0002 and 0006. This means that, for evaluations for the past, the current situation is not printed.

Solution
If you really want to print the cirrent name or the current address, then change Include RPCKT400 at the lines marked "<-- here" below, and then regenerate the main report RPCKTOx0 (x = country abbrev.).

Excerpt from coding:

....
FORM MAKE_NAME.
* Ausgabe des Namens (Titel Nachname, Vorname)
DATA:
RET_CODE LIKE SY-SUBRC,
CNM_MOLGA LIKE T001P-MOLGA.
* RP-PROVIDE-FROM-LAST P0002 SPACE PN/BEGDA PN/ENDDA. <--here
RP-PROVIDE-FROM-LAST P0002 SPACE LOW-DATE HIGH-DATE. <--here
CNM_MOLGA = MOLGA.
...

FORM VAR-ADRS.
* Bereitstellen der Adresse
IF SW_ADDRESS = FALSE.
SW_ADDRESS = TRUE.
* creates national name
PERFORM MAKE_NAME.
RP-PROVIDE-FROM-LAST P0001 SPACE PN/BEGDA PN/ENDDA.
* RP-PROVIDE-FROM-LAST P0002 SPACE PN/BEGDA PN/ENDDA. <--here
RP-PROVIDE-FROM-LAST P0002 SPACE LOW-DATE HIGH-DATE. <--here
* RP-PROVIDE-FROM-LAST P0006 '1' PN/BEGDA PN/ENDDA. <--here
RP-PROVIDE-FROM-LAST P0006 '1' LOW-DATE HIGH-DATE. <--here
* creates national address
RP-MAKE-ADDRESS P0001 P0002 P0006 NAMEN CNT_ADRS_LINES.
ENDIF.
ENDFORM.
.....

FORM VAR-P0002.
* RP-PROVIDE-FROM-LAST P0002 SPACE PN/BEGDA PN/ENDDA. <--here
RP-PROVIDE-FROM-LAST P0002 SPACE LOW-DATE HIGH-DATE. <--here
CHECK PNP-SW-FOUND NE '1'. "not found?
CLEAR P0002.
ENDFORM. "VAR-P0002.

SAP Note 23984 - Workload analysis: duration of data storage

Symptom:

It is not clear where the settings for the duration that the data of Workload analysis is stored are made.

Cause and prerequisites

In the standard system, these storage periods are already preset. These settings are: 2 periods for daily data, weekly data and monthly data.

Solution
If the workload analysis data is to be deposited for longer periods, you can carry out the following:
Select Workload Analysis via: Tools > Administration > Monitor > Performance > Workload analysis. In this transaction, under: "Goto > Parameters (Performance Database)", you will find the change screen for the storage periods.
Via "Modify parameters", you can maintain the residence times, that is, they are ready for input. Under the column "Standard statistics", you can set the storage periods. Under the column "Time comparison data", you set the storage periods for long-term data (for example, performance comparisons of application hosts, time series, and so on). This data only takes up a small amount of space in the database.

SAP Note 23974 - ME56, ME57: Cancellat. in popup 'Manual Allocation'

Symptom:

Transaction ME56/ME57
If several list entries are selected and you allocate a source of supply manually, you cannot cancel the entire transaction in the popup using the 'Cancel' function but you can only skip the current entry.

Cause and prerequisites

The required function of the immediate 'Exit' is currently not supported.

Solution
'Temporary workaround':
Enter, for example, a nonexisting vendor and press the 'Cancel' key after the error message.

SAP Note 23969 - Error message 'Overflow of the literal table'

Symptom:

The error message 'Overflow of the literal table' (GEN_LITERAL_OVERFLOW) occurs when compiling an ABAP/4 program.

Cause and prerequisites

During the generation of an ABAP program the following data is stored in the literal table.

    • Strings of the form '.....' and '.....' (number)
    • Constants of type I and P
    • Names of procedures (forms, functions and methods) and modules

The literal table has a maximum size of 64K (the ABAP/4 runtime environment uses 16-bit offsets to address in this area).

Solution
Replace larger strings with text constants TEXT-###.
Use shorter names for procedures and modules.

Furthermore, the only real option is to split the program into several subroutines.

Store the program components in a separate subroutine pool and call them using an external Perform or by using function modules.

The 64K restriction is mitigated after Release 3.0. This means that when using multiple identical literals, the corresponding literal is only stored once in the literal table.

As of Release 4.6 you can use a maximum of 64K of different literals. The literal table size must not exceed 4GB.

SAP Note 23965 - Dunning area for down payment clearing

Symptom:

Dunning areas specified in down payments are not copied to the down payment clearing item or to the credit memo item in the event of a full or partial clearing of such down payments.
Key words: transactions FBA3, FBA8

Cause and prerequisites

Program error

Solution

Corrected in Release 2.2F and Release 3.0D
Advance correction:
Include MF05AFA0

FORM ANZAHLUNG_UMBUCHEN.
...
...

*-----------------------------------------------------------------------
* Erzeugen Ausgleichsbuchung / Verrechnungsbuchung
* pro Anzahlung
*-----------------------------------------------------------------------
...
...

*------- Feldinhalte uebernehmen ---------------------------------------
...
...
BSEG-GSBER = POSTAB-GSBER.
BSEG-MABER = POSTAB-MABER. <- INSERT
BSEG-VBUND = POSTAB-VBUND.
...
...

*-----------------------------------------------------------------------
* Erzeugen der Gutschrift
*-----------------------------------------------------------------------
...
...

*------- Feldinhalte uebernehmen ---------------------------------------
...
...
BSEG-GSBER = POSTAB-GSBER.
BSEG-MABER = POSTAB-MABER. <- INSERT
BSEG-VBUND = POSTAB-VBUND.
...
...
ENDFORM.

SAP Note 23963 - RFFOD__L, etc. - account currency in DME

Symptom:

In data medium exchange (DME), the currency of the corresponding bank sub-account is no longer used as the currency for the account to be debited with the order value ( as of Release 3.0A).

Key words: RFFOD__L, RFFOAT_L, RFFOAT_U, RFFOCH_U, RFFONL_I.

Cause and prerequisites

Program design changed

Solution
As of Version 3.0A, the currency of the house bank account is taken as the basis for the currency of the account to be debited with the order value (table T012K) and not - as was previously the case - the currency of the respective bank sub-account (G/L account master record table SKB1).
This means it is no longer necessary to create a corresponding bank sub-account with the same currency for each individual currency.

SAP Note 23949 - Incorrect date calculation cycle counting OMCO

Symptom:

In fiscal year variants that are not calendar-dependent, the annual intervals could calculated incorrectly during the cycle counting Customizing.

Cause and prerequisites

Program error in L0MI0FI0

Solution
SE38 -> Module L0MI0FI0.
FORM INTERVALL_BERECHNEN USING LOC_WERK
LOC_ANZ
CHANGING LOC_INT
LOC_PZ.
..
..
*-- Im ersten Fall gibt es eine jahresspezifische Periodenbestimung
SELECT * FROM T009B WHERE PERIV EQ T001-PERIV
AND BDATJ EQ MARV-VJGJA
* AND BUMON EQ MARV-VJMON. <-OLD
AND POPER EQ MARV-VJMON. <-NEW
ENDSELECT.
IF SY-SUBRC IS INITIAL.
IF T009B-RELJR EQ '0 '. <-INSERT
DATUM-JAHR = MARV-VJGJA.
ENDIF. <-INSERT
DATUM-TAG = T009B-BUTAG.
DATUM-MONAT = T009B-BUMON.

*-- Im zweiten Fall ist die Periodenbestimmung jahresunabhängig
ELSE.
SELECT * FROM T009B WHERE PERIV EQ T001-PERIV
AND BDATJ EQ SPACE <-INSERT
* AND BUMON EQ MARV-VJMON. <-OLD
AND POPER EQ MARV-VJMON. <-NEW
ENDSELECT.
IF T009B-RELJR EQ '0 '. <-INSERT
DATUM-JAHR = MARV-VJGJA.
ENDIF. <-INSERT
DATUM-TAG = T009B-BUTAG.
DATUM-MONAT = T009B-BUMON.
ENDIF.
..

SAP Note 23948 - Customer / vendor: Screen 'dunning areas'

Symptom:

The error only occurs if a user does not have authorization to change the fields 'Dunning area' and 'Dunning procedure' via the authorization object 'Change authorization for certain fields'.
If he now tries to delete the value of all fields he can change, he cannot do this. After pressing the key, the values reappear.
Key words: FD01, FD02, XD01, XD02, FK01, FK02, XK01, XK02

Cause and prerequisites

Program error

Solution
A) Customer
SE51 - Program 'SAPMF02D' Screen '1221' - Change flow logic PROCESS AFTER INPUT.
...
LOOP.
...
MODULE XKNB5_AUFBAUEN ON CHAIN-INPUT. <-- DELETE
MODULE XKNB5_AUFBAUEN. <-- INSERT

B) Vendor
SE51 - Program 'SAPMF02K' Screen '1221' - Change flow logic PROCESS AFTER INPUT.
...
LOOP.
...
MODULE XKNB5_AUFBAUEN ON CHAIN-INPUT. <-- DELETE
MODULE XKNB5_AUFBAUEN. <-- INSERT

SAP Note 23938 - Error GR696 when generating a report group

Symptom:

When you try to generate a report group, the generation terminates with error message GR696. When you check the reports of the report group individually, the error message does not occur.

Additional key words ----- SUPPORTGUIDE 20010411140028 -----


REPORTWRITER, SGRW_GENERATION, SGRW_MESSAGE, SGRW_DOCU_CONS_NOTE
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS

Cause and prerequisites

One or more column blocks in the column definition were set to "Inactive" in a report. In addition, certain column blocks were also deactivated in the line definition of the line blocks. Report Writer does not process this situation properly.

Solution
If the inactive column blocks are no longer required for the report, please delete them from the column definition. Otherwise, activate the column blocks in the definition.

SAP Note 23932 - KSB1/KOB1: TIME_OUT in program SAPFK00B

Symptom:

Message: Program terminates, the dump shows a TIME_OUT because the maximum runtime was exceeded.
Key words: Termination, Dump, Time_Out, rum time error
Transactions: KSB1, KSB2, KOB1, KOB2, KOB3 CJ74, CJ76,

Cause and prerequisites

Too many data records are read.
Groups are used.

Solution
    1. If you use Release 2.2, start the transaction with the same parameters in background processing mode.
    2. For the transactions not yet supported by the background processing, the group must unfortunately be reduced.
    3. If you use Release 2.1 or the transaction terminates in background processing as well, you will have to use smaller gorups. Example: request only a small portion of the cost center/order/project hierarchy.



The following procedure can be used on-line to see how many data records are processed:

    1. If the program terminates with a dump, call the debugger. From there, display the tables.
    Display table ITEM_TABLE. Use F24 to go to the end of the table. What does the index show? The index indicates the line items that were read up to the termination point.
    If the index is less than 10,000, then the selection of records actually can last that long, and you must execute the above mentioned procedures.

SAP Note 23927 - SE30: Authorization objects (see SAP System trace)

Symptom:

Authorization objects are no longer displayed within the runtime analysis.

Cause and prerequisites

New design.

Solution

A comprehensive analysis is now performed using the SAP System trace instead of (ABAP/4 Development Workbench -> Administration -> System administration -> Monitor -> Traces -> SAP System trace).
See also:

    • Release notes on runtime analysis
    • Note 66056 and 18529

  • Additional key words

    ABAP, System trace, ST01

SAP Note 23925 - SE30: Source text with line 0

Symptom:

During runtime analysis (SE30), the position of the source text is displayed as line 0.

Cause and prerequisites

Generation error in the program.

Solution
Branch to the source text and generate the program again.

Additional key words

ABAP

SAP Note 23922 - MRP: Creation indicators, PReq. or planned order

Symptom:

During the planning run of material requirements planning (MD01/MDBT or MS01/MSBT) or during master production scheduling (MD40/MDBS), the control parameters of materials planning that were entered on the initial screen of the transaction (creation indicator "Create purchase req.", "Schedules lines", "Create MRP list" or "Display list") appear to have no effect.
As a result, the single-item planning for a material may return a different result from total planning even if the indicators on the initial screen are the same.

Enhancement

In addition, the following may occur under certain conditions:
A total planning run with the indicator "Create purchase req." set to "Purchase requisition in opening period" (BANER = 2) generates a purchase requisition (PReq) for planning on a working day. However, for planning on a non-working day, it generates a planned order.
This can occur, for example, for materials planned using consumption-based planning with an opening period from the scheduling margin key of 0 days.

Other terms

Creation indicator, material requirements planning run, MRP run, materials planning, material requirements planning, MRP, MD01, MD02, MD03, MD40, MD41, MD42, MDBT, MDBS, requirements planning, planned order, purchase requisition, req, PL-AUF

Reason and Prerequisites

Single-item planning and total planning follow a different logic in relation to the creation indicators.
This is also described in the documentation for production planning/material requirements planning (Chapter 4, Section 2) and in the Implementation Guide (IMG).
Single-item planning:
The specified creation indicators apply in general.


Total planning:
The specified creation indicators are default values.
For materials with an MRP group, the values from the MRP group apply (if they exist).
The creation indicator for schedule lines can be determined additionally for each plant. This is used if nothing is determined using the MRP group.
Therefore, the priority is as follows:

    1. MRP group
    2. Plant
    3. Initial screen



Solution

Check the settings in Customizing for MRP:

    1. Planning -> Creation Indicator
    2. Planning -> Procurement Proposals -> Define External Procurement -> Plant:

Creation of delivery schedules.

    3. Planning -> Activate Runtime Statistics


With a MODIFICATION, the logic of the total planning run can be transferred to the single-item planning transactions. The modification is specified in the attachment.
As of Release ECC 5.0, this modification can also be replaced by implementing the BAdI method ADJUST_PLANNING_PARAMS (BAdI MD_MRP_PARAMETERS).

Additional information
  • An opening period of 0 days means that, together with the indicator "Create req. order" from "2", purchase requisitions can be created only if the opening date is the same as the planning date.
  • For reorder point planning, the requirement date is set to the planning date when there is a shortfall of reorder point.
  • Therefore, if scheduling is carried out on a non-working day, the requirement date is set to a non-working day and the delivery date or start and opening dates are set to the previous working day.
    As a result, the opening and planning dates no longer fall on the same day and the system generates corresponding planned orders.

To avoid this phenomenon, you should always maintain the purchase requisitions creation indicator in the planning group for the affected materials or you should maintain an opening period greater than 0.