SAP Note 19585 - VA01, VA02, ME21: Incorrect order unit (Purchasing)

Symptom:

Purchase requisitions that are generated from sales orders have an incorrect (purchase) order unit.

Cause and prerequisites

The order unit (Purchasing) in the purchase requisition was reset.

Solution
Rectified in Releases 3.0A and 2.2H. Prior to this, can be dealt with as follows:

Program LEBNEF01 Routine

*eject
*-----------------------------------------
* Bezugsquelle suchen
*-----------------------------------------
FORM BEZUGSQUELLE_3.

...
...
*BQPIM-MEINS = EBAN-MEINS. "<-- old
BQPIM-MEINS = EBAN-BMEIN. "<-- new
BQPIM-LMEIN = EBAN-MEINS.
BQPIM-FRGDT = EBAN-FRGDT.
PERFORM BQPIM_T160D_SETZEN.
CALL FUNCTION 'ME_SEARCH_SOURCE_OF_SUPPLY'
EXPORTING
COMIM = BQPIM
BANFNUMMER = EBAN-BANFN
BANFPOSITION = EBAN-BNFPO
IMPORTING
COMEX = BQPEX
TABLES
UEQUP = XORD
UORD = XORD.
IF SY-SUBRC EQ 0.
EBAN-QUNUM = BQPEX-QUNUM.
EBAN-QUPOS = BQPEX-QUPOS.
EBAN-VRTYP = BQPEX-VRTYP.
EBAN-KONNR = BQPEX-KONNR.
EBAN-KTPNR = BQPEX-KTPNR.
EBAN-EKORG = BQPEX-EKORG.
EBAN-INFNR = BQPEX-INFNR.
EBAN-RESWK = BQPEX-BEWRK.
EBAN-FLIEF = BQPEX-FLIEF.
EBAN-LIFNR = BQPEX-LIFNR.
IF BQPEX-MEINS NE SPACE. "<-- new
EBAN-BMEIN = BQPEX-MEINS.
ENDIF. "<-- new
CLEAR BQPEX.
ENDIF.

ENDFORM.

Additional key words

fv45efba

SAP Note 19584 - SAPcomm: getting the new version from SAPSERVx

Symptom:

New version of SAPcomm required.

Cause and prerequisites

Various program errors or new functions in SAPcomm.

Solution
The current versions of SAPcomm are stored on the servers 'sapservX' ('sapserv3'...'sapserv7') at SAP and can be downloaded from there via ftp.

Procedure:

1) Exit any 'old' versions of SAPcomm that are currently running
(with 'scmstop').

2) Save the current installation of SAPcomm. The download of the new
version only overwrites programs and grammar files - the SAPcomm
configuration (file sapcomm.cfg) is retained.

3) Change to the current directory.
SAPcomm under UNIX:
Change to the SAPcomm startup directory
(default: '/usr/sap/com/SYS/exe/run').
SAPcomm under OS/2:
Change to the SAPcomm root directory
(default: '\SAP\COM').

4) From this directory, start 'ftp'. Log on to your sapservX host and
change there to the /general/misc/sapcomm directory.
Go to the subdirectory for the newest version of SAPcomm, for
example 'rel31G'.
From here, go to the subdirectory that corresponds to the platform
where your SAPcomm is installed (or where you want to install it)
for example, 'AIX'.

5) Enter 'bin' to change the transfer mode to 'BINARY'.
Transfer the file in this directory using the ftp 'get' command.
After transferring this file successfully, quit FTP ('quit').

The procedure now depends on whether you are installing SAPcomm under UNIX or OS/2:

SAPcomm under UNIX:

6) The file you transferred is a compressed archive, that contains a
complete version of SAPcomm.
The name of the file is 'SAPcomm.tar.Z'.

7) Uncompress the file with the command:
uncompress SAPcomm.tar.Z
The directory should now contain the file SAPcomm.tar
(the original file SAPcomm.tar.Z is deleted).
Unpack the archive file with the following command:
tar -xvf SAPcomm.tar
The result should be a set of SAPcomm programs (executable files
with no extensions), SAPcomm grammar files (*.grm), configuration
examples ('*.cfg' and 'sapcomm.pfl'), as well as the SAPcomm API
files ('scmi.h','scmiux.o','scmitst.c').

8) Move the grammar files into the SAPcomm profile directory:
mv *.grm /usr/sap/com/SYS/profile
Move the non-program files into the SAPcomm directory for other
files (examples and SAPcomm API development):
mv *.* /usr/sap/com/etc

SAPcomm under OS/2:

6) The file you transferred is a self-expanding archive that contains
a complete version of SAPcomm.
The name of the file is 'SCMINST.EXE'.

7) Unpack the archive in the SAPcomm root directory by entering:
SCMINST -y
The result should be a set of SAPcomm programs (executable files
'*.exe'), dynamic libraries ('*.dll'), SAPcomm grammar files
('*.grm'), examples for configuration ('*.cfg' and 'sapcomm.pfl')
as well as the SAPcomm API files ('scmi.h','scmiux.o','scmitst.c').
These files are copied into the various directories, any existing
configuration file SAPCOMM.CFG is not overwritten.

8) Move all dynamic libraries from '\SAP\COM\SYS\EXE\RUN' into a
directory where the DLLs will be recognized when the program is
started, or include '\SAP\COM\SYS\EXE\RUN' in the 'SET LIBPATH'
statement in the 'CONFIG.SYS' file.

Additionally SAPcomm uses the dynamic libraries CPICS.DLL and
CPICT.DLL that are not contained in the archive SCMINST.EXE.
If these DLLs are not stored on your OS/2-PC, or if they are from
a lower release than the SAPcomm you just installed, you can also
get these DLLs via FTP. They are stored in uncompressed form in
the same directory as SAPcomm.

The last steps are the same for UNIX and OS/2:

9) Start the SAPcomm configuration compiler ('scmcfgcc'), in order to
set up your SAPcomm configuration for the new version.

10) Start the new SAPcomm version.

Additional key words

FTP, sapserv, sapcomm.cfg, SAPcomm.tar.Z, SCMINST.EXE

SAP Note 19579 - Transaction OSS1: TDW F08 HOST

Symptom:

Transaction OSS1 terminates with error message: TDW F08 HOST and SERVICE rxpected. Only one command line parameter found:
#/H/......./S/sapdp99/H/......../S/sapdp99/H/oss001/S/sapdp01#

Cause and prerequisites

Incorrect SAPGUI version on the frontend

Solution
To use transaction OSS1, the SAPGUI must be version 2.1J/2.2D or later. The SAPGUI version 2.1J/2.2D can be obtained via FTP from the sapserv3 server in Walldorf. Directory: dist/permanent/21J.
The SAPGUI for Windows supports this transaction from Rel. 2.1J/2.2D in the WinSocket version executable with all network products that are officially supported by SAP.
The two SAPGUI versions shipped for Novell Lan Workplace (older than Rel. 4.1) or Microsoft LanManager (older than Rel. 2.2) do not support the OSS1 function.

SAP Note 19577 - AA629 Balance for transaction type group 10 negative

Symptom:

When you are settling an order or project with a negative balance to an asset (especially an asset under construction), error message AA629 "Balance for transaction type group xx negative" appears.

Cause and prerequisites

The default transaction type 115 for settlement from CO to assets belongs to transaction type group 10. Transaction type group 10 allows only positive fiscal year balances.
The balance of the transaction type group (from an accounting viewpoint) may be negative only when you settle to an asset under construction, which, in turn, has alredy been transfer-posted to a completed asset.
In all other cases, the error message can appear only through postings (not allowed by accounting) to orders/projects or the target asset.

Solution
If the target asset is a completed asset, please check the postings to the asset and, if necessary, cancel posting not allowed by accounting. If the target asset is an asset under construction, you can allow for a negative balance with the following adjustments in Customizing. In the process, however, transaction group type 10 should not be changed.

Solution up to Release 3.0:
Please set up a new transaction type group for the settlement of orders or projects to assets. To do so, copy transaction type group 10 to 11. In the new group, change the "FY Balance sign" from + to *. You can set up a new transaction type group with transaction SM30 (view maintenance) and View V_TABWG.
Then access asset accounting in the customizing system to maintain the transaction types. Choose Tools -> Customizing -> Configuration -> Accounting -> Asset Management. Transactions -> Transaction types.
Create a new transaction type 116. Enter the new transaction type group 11 and then set all the other parameters in the new transaction type exactly as they are in transaction type 115.
Save the new transaction type and then choose Goto -> Default. This brings up the screen for maintaining default transaction types.
Change the default transaction for "Acquisition from settlement of order" from 115 to 116.

Solution from Release 3.0 onward:
From Release 3.0 onward, transaction type 116 and transaction type group 11 are delivered as part of Standard. All you need do is change default transaction type for "Acquisition from settlement of order" from 115 to 116.

Additional key words

SAPLKO77 KO88 CJ88 AiB TABWV

SAP Note 19574 - CC-ADMIN: Controlling data selection during client copy

Symptom:

For which copy scenarios are there client copies?

Can Customizing data be copied into a target client that already contains data? Can clients be mixed?

Cause and prerequisites

Usually special scenarios for copying.

Solution

See also Note 24853.

The following scenarios are supported by the tools for copying clients:

a) Copying a complete client including all master and transaction data.

b) Copying the complete Customizing and deleting the existing master and transaction data.

c) Copying user masters along with all profiles and, as of Release 4.5A, all activity groups.

d) Another mode was implemented before Release 4.x as a special mode, which completely copies Customizing without deleting master data and transaction data. This mode is not recommended because it leads to data inconsistencies between master data, transaction data and Customizing.

e) It is not possible to mix clients (insert a client into an existing one) with the client copy tools (see below). Mixing clients is only possible through a consulting project- which involves a great deal of work.

The above described copying procedures are supported in the R/3 Releases as follows:
------------------------------------------------------------------------

• As of Release 3.0: Choose the profiles that correspond to your copy preferences. SAP does not deliver a profile without initialization. It must be newly created. You can find additional information on the delivered profile in Note 24853.

Importang If you copy customizing without application data in Release 3.x, the address data is partially lost. For more information please see Note 25181.

• As of Release 4.0: Essentially like Release 3.0, however, the initializating of master and transaction data can no longer be deselected for a profile.

Also deactivating the corresponding flag for a program run - in the menu - has no effect. This functionality had to be removed because of technical problems in particular with addresses. At the time, a change in the menu was not possible.

1. Which data belongs to a client?
-----------------------------------

Three different data levels can be distinguished that are based on one another:

a) client-dependent application data, that is, data which is created during the application system operation.

b) client-dependent Customizing data on which the application data is based.

c) client-independent Customizing data and system data which are only mentioned here for reasons of completeness but which are of no relevance to the client copy.

Application data is created when you run application transactions. In this case, a large number of plausibility and consistency checks are executed. These checks are based primarily on the Customizing data of level (b), and in some rare cases on (c). This creates dependencies between application data (a) and Customizing data (b). Since the Customizing data does not refer to the application data, there is only one state of dependence from (a) to (b) with the meaning "(a) dependent on (b)".

2. What is a consistent data environment of a client?
---------------------------------------------------

Consistency is maintained if all dependencies between (a) and (b) are met. When you enter application data online, this is provided by the checks that are part of the maintenance screens. When you copy clients, you have to follow certain rules.

3. Which rules apply to copying clients?
-----------------------------------------

4. Note that you may not work in the source client while copying. Otherwise inconsistencies, particularly in the number range can occur.

To make sure consistency is maintained when copying, only the following two copying procedures are supported:

• All Customizing data and all application data is copied. When copying, the tables in question are switched completely. This means that data that existed in the target client but not in the source client before the copying procedure is deleted by the switch procedure. So, the table is set up again consistently. This ensures the consistency between (a) and (b).

• Only Customizing data is copied. At the same time the contents of all application tables that are not copied are reset. This is a simple way to make sure (a) and (b) are consistent.

The central statement of the two previously decribed procedures is the following: If the target client contains application data before the copying, this data is reset during copying.

When testing the quality, there are requirements whose purpose it is to test the consistency of a changed Customizing environment against an existing (productive) client. For this reason, it is desirable to combine a Customizing environment with an application environment. The subsequent test tries to verify the consistency of the two environments or to detect inconsistencies.

Only in these scenarios is it acceptable to retain the application data of the target client because a possible inconsistency might be part of the plan. In general, however, the target client data must always be reset to guarantee consistency.

This scenario should be typically constructed in such a way that transport requests are imported with the Customizing changes in the test client. This then corresponds to the supply of the production system and, in doing so, offers more security.

The special mode of client copying should only be used in extreme cases. SAP can offer no support for the inconsistencies resulting from its use. As of Release 4.x, the functions were removed due to technical problems, particularly with user and address management.

5. Number ranges:

Number ranges have to be reset if the target client does not contain any application data after the copying. This applies, for example, if you only copy Customizing data. Otherwise, the number range statuses remain unchanged or are copied from the source client. The reset decision is implicitly derived from the copy parameters and does not need to be, or cannot be defined externally. The following table

illustrates the processing of number ranges:
-------------------------------------------------------------
Customizing Master & Delete and Number ranges
Data Transaction Create of target clients
-------------------------------------------------------------
x ' ' ' ' are retained
x ' ' x number ranges are reset
x x x copy from the source client

Note that you may not work in the source client while copying.
Otherwise inconsistencies, particularly in the number range can occur.

6. Variants:

Information for processing variants can be found in Note 24853.
Addresses:
Up to Release 3.1I: Please see Note 25181.
Release 4.0B: Please see Note 130540.
Release 4.5B: Please see Note 350101.

Additional key words

Number ranges, client copy, SCC0, SCCL, SCC2, SCC8, SCC9, delivery class

SAP Note 19565 - RPTDSH00

Symptom:

Various errors in RPTDSH00:

1. 1. The shift schedules displayed do not correspond to the date chosen on the initial screen.

2. 2. If you sometimes start the report using "Overview", and sometimes without "Overview", the day program display is different.

3. 3. There is a runtime error if you select a line which ought not to be selected.

4. 4. Only one shift (period work schedule) is ever selected. The error also occurs if you made the modifications described in this note before 13.02.1996. The note contained an error up until this date, but it has now been corrected. Please pay special attention to point 3 under
'Solution'.

Cause and prerequisites

Program error

Solution

These errors have been eliminated with correction number QKWK005503A for 2.1L, QKWK007627A for 2.2F and QKWK121374 for 3.0A.
You can carry out an advance correction.

1. Please insert the lines marked "<-- new" and deactivate the lines
marked "<-- deact.."

2. CAUTION! In the PARAMETERS part, there are two versions of the source
code: one for 2.1, the other for 2.2 and 3.0! Please modify the
parameters as shown below for the system in question.

3. Make especially sure that the command 'APERIOD = LPERIOD' stays active AFTER the command 'LOOP AT I508A' (Printout view page 4).

4. Please include the following numbered text:
Nr. Text
PE1 Month, Year from
PE2 Month, Year to

5. Then check report RPTDSH00 for errors.

SAP Note 19564 - PPPR: Long texts are not printed

Symptom:

Long texts do not appear in the production order printout.

Cause and prerequisites

After an upgrade change, generally the required table entries are missing in Customizing of print control (table access) in the current client.

Solution
Copy the entries from client 000.
Use transaction COTB for the table accesses - e.g. call transaction COTB in the current client (<>000).

Additional key words

Print out, production order

SAP Note 19561 - RFBVD__1: FU810 File cannot be processed

Symptom:

When you attempt to copy the bank master data, the error message FU810 "File ... cannot be processed" is issued.
Key words: RFBVD__1 RFBVD__0 BNKA

Cause and prerequisites

Incorrect data format of the import file.

Solution
Use the following ABAP program to check the sorted file:
PROGRAM ZZTEST01.
DATA: XEOR.
DATA: BEGIN OF WA,
CHAR1(189) TYPE C,
END OF WA.
PARAMETERS: DS_NAME LIKE RFPDO-F160DSN1.

PARAMETERS: ANZAHL(4) TYPE N.
* ------ Satzendekennzeichen?
OPEN DATASET DS_NAME FOR INPUT IN TEXT MODE.
READ DATASET DS_NAME INTO WA.
READ DATASET DS_NAME INTO WA.
IF SY-SUBRC = 0.
XEOR = 'X'.
WRITE: / 'File has end-of-file indicator'.
ELSE.
WRITE: / 'File has no end-of-file indicator'.
ENDIF.
CLOSE DATASET DS_NAME.
* ------ Die ersten N Sätze ausgeben
IF XEOR = SPACE.
OPEN DATASET DS_NAME FOR INPUT IN BINARY MODE.
ELSE.
OPEN DATASET DS_NAME FOR INPUT IN TEXT MODE.
ENDIF.
DO ANZAHL TIMES.
READ DATASET DS_NAME INTO WA.
WRITE: / WA(8), 9 WA+26(58).
ENDDO.

The result will show whether the file has an end-of-file indicator or not and whether the data has been shifted.
The bank code appears in WA(8).
WA+26(58) contains the bank address when the file could not be created from the disk.
WA+27(58) contains the bank address when the file was created from a disk).
That means: A SPACE between bank code and bank address shows that the file was created from the diskette.

SAP Note 19555 - Account maintenance: PO display

Symptom:

Keyword: MR11
The decimals in the local currency amounts in the PO history are not alway displayed correctly when maintaining the GR/IR clearing account.
Even with those currencies which have no decimal division (such as BEF or LIT), the numbers are divided by 100.

Cause and prerequisites

Error in program FM08REB0 in FORM BESTELLENTWICKLUNG_ANZEIGEN. Since T169-TRTYP in transaction MR11 is 'H' and not 'A', the report
RM06EHBE is called with the parameter LESEN = 'X' instead of 'Y'.

Solution
Corrected as of rel. 3.0. Prior to this: change in program FM08REB0, FORM BESTELLENTWICKLUNG_ANZEIGEN:

*---------------------------------------------------------------------*
form bestellentwicklung_anzeigen using b01_bukrs
b01_ebeln
b01_ebelp
b01_meins
b01_bprme
b01_webre.

if t169-trtyp = trtyp-a
or t169-vgart = 'KP'. "<---NEW : Essential for MR11
submit rm06ehbe and return
with lesen incl 'Y'
with s_ebeln incl b01_ebeln
with s_ebelp incl b01_ebelp
with s_bukrs incl b01_bukrs
with s_meins incl b01_meins
with s_brpme incl b01_bprme
...

SAP Note 19542 - Cancelling a bill of exchange payment request

Symptom:

When you cancel a bill of exchange payment request that was created by the payment program, the indicator from the item that was to be payed by the bill of exchange was not deleted. As a result, the items could not be processed in subsequent payment runs.

Cause and prerequisites

Constellation not supported.

Solution
Starting in Release 3.0A, the indicator will be deleted from all affected items when a bill of exchange payment request is cancelled or explicitly cleared. This also is always the case, if a pure clearing document (no line items) is created e.g. using Transaction F-32 (FB1D) or F.13 (Automatic clearing). If the clearing inlcudes an item with reference to the bill of exchange payment request, the ID is also removed from all items.
If the bill of exchange payment request is cleared because at least one selected invoice was paid, the reference will not be cancelled in the other invoices, as they could still be paid in future referring to the request for the bill of exchange payment (with a changed amount).
No advance correction possible. The number of the bill of exchange payment address can be removed from the corresponding invoices, once the request has been cancelled. To do this, simulate a bill of exchange posting in accordance with a request, as this is the fastest way to find the involved invoices. You can then select and change the invoices from the open item overview.
If you do not want to delete all identifications during clearing, the following workaround is helpful: Create a clearing rule that includes field ANFBN. To be able to do this, please implement the attached modification.
or: Create a new clearing rule (Table TFAGS) in FI Customizing for account type 'D', e.g. for field SGTXT. Change the entry in Table TFAGS using Transaction SE16. Replace SGTXT by ANFBN. Go to FI Customizing for clearing rules again and add a new field which you delete again immediately, e.g. SGTXT. When saving, the program is generated with the clearing rule for ANFBN.
After creating the clearing rule, the clearing documents always contain line items, and field ANFBN is preserved in the other items.

Additional key words

ANFBN, F-32, FB1D, F.13, clearing

SAP Note 19539 - SAPcomm and Topcall: error E1102

Symptom:

Error when sending fax documents. Error message in log file of SAPcomm component "TOP":
E1102 Error sending to Topcall. RC=12.

Cause and prerequisites

The recipient number that Topcall sends to SAPcomm (before sending the document) is different from the original recipient number.
The cause for this may be:
1) The number was changed in Topcall due to specific configuration
for this device.
2) Parameter MASK was set in the SAPcomm configuration file.
As a result, the mask name was added to the recipient number.

Solution
Starting in SAPcomm version V3.0A1, subsequent changes to the recipient number will no longer cause the send transaction to terminate.
Workaround:
1) Change the configuration of the Topcall device in such a way
that the device no longer changes the recipient numbers.
2) Remove the "MASK" parameter from the SAPcomm configuration
file. Instead, refer to the required Topcall mask by adding the
Topcall statement
++INCLUDE
to all the R/3 layout sets you have assigned to documents for
sending via Topcall.

SAP Note 19535 - Changing the batch mgmnt requirement in mat. master

Symptom:

After you have changed the batch management requirement in the material master record, the batch management requirement indicator is not changed in deliveries already created. For these deliveries, you cannot post a goods issue.
No transport order is confirmable.
The message VL210 occurs.

Cause and prerequisites

Handling error.

Solution
You can create the following correction program:

PROGRAM ZZLIPS.
TABLES: LIPS.
SELECT-OPTIONS MATNR FOR LIPS-MATNR.
SELECT-OPTIONS VBELN FOR LIPS-VBELN.
PARAMETERS: XCHPF,
XCHAR.
SELECT * FROM LIPS WHERE VBELN IN VBELN AND MATNR IN MATNR.
LIPS-XCHPF = XCHPF.
LIPS-XCHAR = XCHAR.
UPDATE LIPS.
WRITE:/ LIPS-VBELN, LIPS-POSNR, LIPS-MATNR, LIPS-XCHPF, LIPS-XCHAR.
ENDSELECT.

When you start the program, you have to enter a material. The delivery number entry is optional. The batch management requirement fields XCHPF and XCHAR in the delivery items with the specified materials are overwritten with the fields specified at the start.

SAP Note 19532 - Master data validation account for global ledger

Symptom:

During master data validation account, error messages are generated because no valid accounts are found.

Cause and prerequisites

During master data validation, the account is validated via a standard SAP exit, which checks by account/company code whether the account is valid.
However, with global ledgers you have global companies instead of company codes. Therefore, the master data company code of the global company is used during master data validation. In this case two problems can occur:

• no master data company code is assigned to the global company

• if alternative accounts are written to the ledger, the accounts do not exist for the company code.

Solution

• In the first case, the company code must be assigned to the global company.

• The second case is probably of the following constellation:

• the company code has an alternative chart of accounts

• the alternative accounts are transferred to the ledger

• no company code exists containing these accounts

In this case, a separate user exit for account validation can be created which works similar to the account exit but performs the following functions:

• reading the global company

• reading the assigned company code

• reading the alternative chart of accounts of the company code

• validating the account with chart of accounts

SAP Note 19530 - Accumulated fields won't accept input f. old data

Symptom:

You want to enter assets with takeover of old asset data for an asset whose capitalization date is in the fiscal year still open. As the activation date is thus deemed not to be in the past, you cannot enter values from the past.
Having split a company code or opened a new one, you want to transfer assets from one company code to another. Depending on the depreciation area, the values are then to be taken over either net or gross. Commercial law generally requires them to be taken over net, which means that you must set the capitalization date according to when the company code was opened.

Solution

Until it is possible to transfer assets across centers with the option of transferring them gross or net by depreciation area, the following circumvention is possible:

• Post normal retirements in the selling company code. Instead of retirement transaction types, you may then be able to use transfer transaction types. If you need a combination of the two per depreciation area, you must make separate postings for each of the transaction types or use the facility for retirements to affiliated companies. In general, it is a good idea to set up transaction types specifically for this purpose, and to resepect the very specialized nature of this transaction.

• In the receiver company code, you have two options. The first is to use posting documents to record the transaction. The second is to use old data transfer to ensure that only the correction opening balance appears in the assets. Note that while the second option is a technical possibility, it is not an acceptable business alternative. Only the transfer of assets through posting follows the requirements of adequate and orderly accounting.

• In the acquiring company code, you post the values with special transaction types, which you can copy from either the transaction types for "Transafer of old assets" (e.g. transaction type 310) or that for post capitalization (400). In the process, you can take over different acquisition and production costs, and accumulated depreciation. Before posting these transfers, you must create the required master records with transaction AS12 (Post capitalization), where you also set the historical depreciation start dates for each depreciation area.

• The second possibility exists in the transer of data with the old data transfer function. In any case, a historical date must be entered as the capitalization date. Otherwise, no accumulated values can be entered. In the process, please note that for net transfer areas the depreciation start date and the expected useful life must take each other into account. In general, the transfer date is taken as the depreciation start date and the remaining useful life of the original asset is taken as the exepcted useful life. Following the transfer of old data, the capitalization date can be changed to the transfer date with the asset change function-- insofar as the correct contents of this field are valuable. A change for technical reasons is not required. If, however, the capitalization date is changed, future problems can show up during retirement methods with various depreciation percentages accoring to "age" of the asset. Certain calculation keys take the the "age" of an asset either from the depreciation start date or from the capitalization date. When the capitalization date has been changed, a change may also be necessary to the calaculation key so that it adjects the depreciation percentages on the basis of the capitalization date.

SAP Note 19528 - Sickness certificate

Symptom:

Sickness certificate - Austria
When processing the session (RPIKSHA0) the following error occurs
- MP005600 2000 s00347 field p0056-OBJPS no entries allowed -
the error only occurs for spouses covered by the same insurance, policy
holders and children O.K.

Cause and prerequisites

Error in the coding of report RPIKSHA0

Solution
In report RPIKSHA0, please change the lines marked "<<<---" below:
* IF FAMSA <> '0'. "<<<---
IF FAMSA GE '2'. "<<<---
*--- you may need to supply object ID
CLEAR: BDCDATA.
BDCDATA-FNAM = 'P0056-OBJPS'.
BDCDATA-FVAL = P0021-OBJPS. "object ID
* CONDENSE BDCDATA-FVAL. "conversion necessary
APPEND BDCDATA. ENDIF.

SAP Note 19525 - Price change - ASSIGN_LENGTH_0 - transaction VK12

Symptom:

If you want to change a price via transaction VK12, the following runtime error can occur: ASSIGN_LENTGH_0 (SAPMV13A).
This termination occurs if you want to change the prices via the function -> Edit -> Price change -> Enter 'Absolute amount' -> Transfer. The termination then occurs if you want to return to the fast entry.

Cause and prerequisites

Program error.

Solution
Error corrected in Release 2.2E.
Make the following changes:
Program: MV13AF0P
...
FORM PREIS_MESSAGE.
FIELD-SYMBOLS: , , , , , .

SY-FDPOS = STRLEN( RV13A-KONWAAE ).
IF NOT SY-FDPOS IS INITIAL. "<-- insert ASSIGN RV13A-KONWAAE(SY-FDPOS) TO .
IF RV13A-KONWAAE EQ '%' AND RV13A-KPROAE EQ SPACE.
RV13A-KPROAE = RV13A-KBETRAE.
RV13A-KPROAE = RV13A-KPROAE * 10.
ENDIF.
ENDIF. "<-- insert

IF NOT RV13A-KPROAE IS INITIAL.
* prozentuale Änderung
SY-FDPOS = STRLEN( RV13A-KPROAE ).
IF NOT SY-FDPOS IS INITIAL. "<-- insert ASSIGN RV13A-KPROAE(SY-FDPOS) TO .
ENDIF. "<-- insert
IF RV13A-KPROAE GT 0.
* Preis erhöht ASSIGN TEXT-305 TO .
ELSE.
* Preis verringert ASSIGN TEXT-304 TO .
ENDIF.
ELSE.
* absolute Änderung
SY-FDPOS = STRLEN( RV13A-KBETRAE ).
IF NOT SY-FDPOS IS INITIAL. "<-- insert ASSIGN RV13A-KBETRAE(SY-FDPOS) TO .
ENDIF. "<-- insert
IF RV13A-KBETRAE GT 0.
* Preis erhöht

SAP Note 19519 - MISSING9999 in v$datafile or BR274W in BRBACKUP

Symptom:

Keyword: MISSING
The control file or views v$datafile and sys.dba_data_files contain the
file names "MISSING9999",
where 9999 = [no] is the 4-digit ORACLE file ID (with leading zeros).

Subsequently an error can occur when saving data with BRBACKUP and the
warning "BR274W File MISSING9999 not found" is displayed.
An ONLINE backup will then terminate with the following messages:
"BR301E SQL error -1128 at location BrTsAlter-1
ORA-01128: cannot start online backup - file [no] is offline.
ORA-01111: name for data file [no] is unknown - rename to correct file
ORA-01110: data file [no]: 'MISSING9999'
BR316E Alter tablespace [tspname] begin backup failed."

When a table is exported/selected/changed the following errors occur:
"ORA-00376: file %s cannot be read at this time
ORA-01111: name for data file %s is unknown - rename to correct file
ORA-01110: data file %s: 'MISSING9999'".

Additional key words
Cause and prerequisites

Either a "CREATE CONTROLFILE ..." was performed at some time after the creation of the DB in which a data file was forgotten, or after a structure change (tablespace created or extended), the old control file (which had been saved before the structure change) was reloaded and recovered to a point after the structure change (complete or incomplete recovery).
The "MISSING9999" entry in the control file is issued the moment the DB is opened. In the process the control file is adjusted on the basis of the file IDs in the ORACLE Data Dictionary. For each missing data file an entry of the type "'MISSING9999' SIZE nK,"(as represented in the
trace file) is generated in the control file. Here 9999 is substituted with the four-digit file ID (possibly with leading zeros) and n with the file size from the Data Dictionary.
The missing data file has the status 'RECOVER' (in v$datafile) or 'AVAILABLE' (in dba_data_files) or 'OFFLINE' (in v$recover_file).
The tablespace that it belongs to is 'ONLINE' or 'OFFLINE' (in dba_tablespaces).
A SYSTEM tablespace file can never be 'MISSING...' as the database could then not be opened.
For the same reason no data file with ONLINE rollback segments can be affected (e.g. from tablespace PSAPROLL).

Solution

If the error is noticed during an OFFLINE backup with BRBACKUP due to
a BR274W warning, the backup is not affected by the error, is continued up to the end and will be correct (the error status is saved with the backup. However an ONLINE backup of the tablespace that the missing file belongs to cannot be performed manually or with BRBACKUP.
The faulty state of the DB should be corrected as soon as possible. Above all, you have to check immediately whether any data is already missing in the current DB (see "Information", point b below).
If the error occurs during export/selection/changing of a table, then the table is completely or partially contained in the missing file. Its contents cannot be regained without a restore/recovery. Data of this table from extents in other still existing files is also usually no longer readable. The database is inconsistent!
The problem can be solved in two ways. Either
1. Transport the forgotten data file back to the DB -or-
2. Delete the tablespace that contains the missing data file--if
possible, by losing as little data as possible.

Option 1 is possible without loss of data, however, you must either have a backup of the missing file and all the redo logs created since that file was backed up.
Option 2 is possible without the missing file and without a recovery.
However, all data of tables partially or entirely contained in the missing data file are lost. This is often insignificant, for example, when the missing data file contains only indexes, empty tables, rollback segments or no objects at all. The tablespace contents are exported and imported again when the tablespace has been deleted and restored.


Information on the missing data file:
sqldba lmode=y
SQLDBA> connect internal

a) Which tablespace does the file belong to, file size:
SQLDBA> select * (-> tablespace_name,file_name,status,bytes)
from dba_data_file:
where file_id = [no];

other files of the tablespace:
SQLDBA> select file_name,bytes
from dba_data_files
where tablespace_name='PSAP....';

b) previous contents of the missing files:
SQLDBA> select * (-> owner, segment_name, segment_type)
from dba_extents
where file_id = [no];

or with sapdba (Main menu -> d:Reorg. -> a:Check -> c:)

c) Status, for example, tablespace parameters (selected under a):
SQLDBA> select * (-> status, default storage parameter)
from dba_tablespaces
where tablespace_name ='PSAP...';

d) Status, data file size:
SQLDBA> select * (-> name, status, bytes)
from v$datafile
where file# = [no];


to 1.:
sqldba lmode=y
SQLDBA> connect internal
SQLDBA> alter database rename file 'MISSING9999' to 'filename';
Here, 'filename' is the complete file name with path.
It does not necessarily have to be the previous name and path
of the file.
The backup of the missing file has to be stored under
'filename' again.
Caution: It is not possible to restore the file with
"SQLDBA> alter database create datafile 'filename';"
unless a backup of the previous control file exists which was
up to date when the file in question was created.
(In this case the "rename" above is not required. Instead the
appropriate control file has to be reloaded again, the
"create datafile" executed and then in the next step it is
recovered with the option "using backup controlfile".

SQLDBA> recover datafile 'filename'; or
recover database; (see Note 4161)
(For an incomplete recovery, all DB data files from the backup
have to be reloaded (see Note 4164).
All redo logs of the missing file generated since the backup
have to be available (for "create datafile" all redo logs since
the initial creation).
SQLDBA> alter database open [resetlogs];
(resetlogs only for an incomplete recovery or
"using backup controlfile")
SQLDBA> shutdown
SQLDBA> exit
Backup of the affected tablespace or the complete DB depending on the type of recovery performed (see Notes mentioned above).

to 2.:
A reorganization of the tablespace has to be carried out "with data files." This cannot be performed completely with SAPDBA as SAPDBA only reorganizes tablespaces where all the files are 'ONLINE'.

- Stop the R/3 System with "stopsap r3". The DB remains open.

- Caution:
Do not set the tablespace to which the data file belongs 'OFFLINE'!
It can not subsequently be set to 'ONLINE' because of the
missing data file, i.e., only empty structures and no tablespaces
could be restored, not even from files that still exist in the
tablespace!

- Export of the tablespace structure that the missing file belongs to.
This can be performed with sapdba (Main menu -> e:Export ->
b:Structures), if the tablespace contains no rollback segments.
(Otherwise note the rollback parameters and delete them manually.)
Structures i.e. indexes, empty tables and rollback segments, also of
the missing file can be restored in this way.

- If the tablespace contains tables that are completely included in the
missing data file, their contents are lost.
However, when tables are only partially included in missing files
you can try to regain as much of the still accessible contents as
possible. With luck, you can regain even all the data of the tables
if the missing file's extents were empty.
Caution: The DB will become inconsistent if any individual table
is not recreated completely!
Contacting SAP is essential!
Tables that have no extents in the missing file can always be restored
completely.
The data export can be performed manually or with sapdba
(Main menu -> e:Export -> a:Data export).

- Determine tablespace parameters as described above in "Information"
under a) and c).

- sqldba lmode=y
SQLDBA> connect internal
SQLDBA> drop tablespace psap.... including contents;
(Afterwards either delete the physical data files at the
operating system level (see "information" a!)
or use the reuse-option in the following statement, if the
size remains the same.)
SQLDBA> create tablespace psap....
datafile 'filename1' size ...M [reuse],
'filename2' size ...M [reuse],
...
default storage (initial ...K next ...K
minextents ... maxextents ... pctincrease 0);
Use the initially noted parameters
(see "Information" a and c).
At this point you can also adjust the number and size of the
data files e.g. combine several smaller files to form one
large file.

- Import the data export again manually or with sapdba, if the export
was performed with sapdba. Main menu -> e:Export/import -> d:).

- Restore the remaining structures (indexes, empty tables) with sapdba
(Main menu -> e:Export/import -> f:),
Restore the rollback segments manually on the basis of the previously
noted values.

- Backup the affected tablespace and the contol file
(manually or with sapdba or brbackup)

- Restart R/3.

SAP Note 19514 - Change to PC installation process in Rel. 3.0

Symptom:

Change in procedure for installing the SAP software on PCs

Cause and prerequisites

New R/3 functionality in the PC area in Release 3.0

Solution
This customer letter is intended for system administrators and network administrators who are responsible for installing and updating the SAP software on PCs.

In the past, the PC software was treated as part of the UNIX shipment, which was installed on the PCs via a UNIX server. Due to the ever- increasing number of PC presentation servers and the increasing number of PC components in the R/3 environment, the PC installation continues to increase in importance. For this reason, SAP is providing easy-to-use options for PC installation directly from the CD in Release 3.0. Installation via UNIX is no longer necessary.

You will need a CD-ROM drive on at least one PC in your network to install the SAP software. All the other PCs which are able to connect network drives can be installed via the network.

Advantages of the new procedure:

- PC ease-of-use is fully utilized
- Simplified handling of the installation tool
- Software administration tools can be used in the PC network
- UNIX administration tasks no longer required
- TCP/IP connection to UNIX server no longer required for installation

The PC installation tool, SAPINST, already provides an option for installing direct from CD to PC. We recommend that you take advantage of this feature. You can then install and - more importantly - upgrade the PC software without involving the UNIX installation at all. For more precise information, please refer to the guidelines "Installing SAP software for PCs".

SAP Note 19501 - CUA menu missing in SAPMV13A transactions VB21-23

Symptom:

The following error occurs after transactions VB21, VB22 and VB23:
After you have selected a sales deal, chosen 'Overview', and selected an item, you receive a popup under the menu option 'Edit' -> 'Change validity' from which you cannot return.

Cause and prerequisites

Some entries of the menus AB00V, AB0VV, AB0VH, AB00H and AB00A of program SAPMV13A should not be active.

Solution
Error corrected in Release 2.2E and 3.0B.
Deactivate the following menu items:

Status Item
AB00A Edit -> 'New entries'
Edit -> 'Delete'
Edit -> 'Reset delete'
Edit -> 'Change validity'
AB00H Edit -> 'Change validity'
AB00V Edit -> 'Change validity'
AB0VV Edit -> 'Change validity'
AB0VH Edit -> 'Change validity'


To deactivate the entries, do the following:

1.) Call transaction SE41.
2.) Call program SAPMV13A and enter the status to be edited.
3.) Double-click on the 'Edit' menu of the corresponding status.
4.) Position the cursor on the function to be deactivated (for example, 'Change validity').
5.) Deactivate the menu entries listed above with 'Edit' -> 'Active' <-> 'Inactive'.
6.) Save.

SAP Note 19500 - The priority of your request has been changed

Symptom:

Other terms

*

Reason and Prerequisites

*

Solution

Dear customer,

We have changed the priority you suggested as from our perspective, the preconditions for this priority are not met in this case. However, we will process your message as quickly as possible.

Thank you for your understanding.

If you do not agree with the change in priority we have made, please contact us at support.country@sap.com.

Yours sincerely,
SAP Active Global Support

SAP Note 19498 - More than 150 printers as of Rel. 2.1G

Symptom:

If more than 150 printers are defined for one server, some printers are no longer edited. The dev-file writes:

*** ERROR ==> rspofps: no free slot for printer [rsposhm. 883]
In the status of the output request you have: status unknown

For the most part, you will still also find the message 'lookup
failed' there.

Additional key words

internal, error, printing

Cause and prerequisites

For each printer, one entry is made in the shared memory. The default for this is 150 entries.

Solution
Raise the number of entries in the shared memory:
To do this, you have to set the system profile parameter "rspo/global_shm/printer_list" to a sufficient number of printers. In addition, you have to increase pool 40, in which the data is stored, by 750 bytes for each additional printer. The profile parameter is called "ipc/shm_psize_40". You can determine the current value with ABAP/4 report 'RSPFPAR'. This report is perhaps already explicitly set in your profile. If you have no entries in your profile, set the value to the value determined by RSPFPAR plus 750 bytes extra for each additional printer (see also Note 5076.)
Notice that the adjustment of the pool size is not applicable on
AS/400 since Shared Memory areas in pools do not need to be grouped on
AS/400.
As of Release 4.0A this memory area will be dynamically maintained to prevent the error occurring any longer.

SAP Note 19496 - PM: Print papers, Operations not printed

Symptom:

Operations not printed for various PM papers although expected.

Cause and prerequisites

Controls not properly maintained.

Solution
The controls key (customizing for T430) contain a number of important features for print.
Operation print flag, External/Internal work flag / Timeticket print flag and confirmation print flag.
In the standard print programs these flags are checked before Operations are printed.
Please the controls use are using.
TEST: Transaction IW38: Select an Order.
In operation overview screen, press f4 on a control key you are using. Here you can check the properties of the various control keys.

The keys can be maintained using transaction SM30 and the view V_T430.

SAP Note 19488 - Dely block w. confirmation block only on header lvl

Symptom:

A delivery block that is relevant for requirements is set on schedule line level (for example, shipping item overview). The blocked schedule lines with confirmed quantity reserve stock anyway.

Cause and prerequisites

If you set a requirements-relevant delivery block in the document header, the confirmed quantity is set to zero after you save.
The requirements transfer is performed nevertheless.

Solution
This function is not available.

SAP Note 19465 - Drill-down reporting: Line structure contains error

Symptom:

Drill-down reporting: only COPA
WHen execute a report, you receive error message KH207:
Rep. line structure & contains errors -> Check.

Cause and prerequisites

Possible cause: The line structure formula refers to elements of the line structure that do no longer exist.

Solution
Correct line structure formula via transaction KER1 - Formula editor. First you have to determine the incorrect formula via transaction SE16 for table T237. There, you have to make sure that all elements of the line structure which are used in the formulas (especially the 9000s entries) are actually available.

SAP Note 19456 - ORACLE: Startup fails: "File already exists"

Symptom:

Startup of DB fails ==> File already exists

Cause and prerequisites

When a crash occurs, the $ORACLE_HOME/dbs/sgadef.dbf file gets stuck.

Solution
Rename the file and restart the database.

SAP Note 19422 - Batch input and list processing in the background

Symptom:

You have written a batch input for a transaction that uses the interactive list processing. When you process the session in the background, an error is always issued. Everything works fine in interactive batch input.

Cause and prerequisites

Interactive list processing in the background is not implemented for Release 3.X. List processing under batch input is only capable of generating the lists in the background.
You cannot run a transaction (with list processing) with batch input in the background.

Solution

Interactive list processing in batch input is possible in Release 4.0.

SAP Note 19418 - Manual Results Analysis: Supplement to the Documentation

Symptom:

Problems with manual results analysis

Note: In addition to 'results analysis', the term 'work in process' will also be used.

Cause and prerequisites

Missing documentation

Solution

Manual results analysis is briefly described in the following.

Table of contents

(1) Entering results analysis data for manual additions and changes
(1.1) - with transactions KKA1, KKA2 und KKA3
(1.1.1) - in periodic display
(1.1.2) - in cumulative display
(1.2) - with transactions KKA4, KKA5 and KKA6 (Rel. 2.2 or higher)
(1.3) - with and without derivation of the cost of sales

(2) Deleting manual results analysis data

(3) Interaction of automatic and manual results analysis with
(3.1) - manual additions
(3.2) - manual changes

(4) Display in reporting
(4.1) - with the cost element report (projects, Rel. 2.2 or higher)
(4.2) - with the cost/revenue structure report (projects only)
(4.3) - with the line-item report
(4.4) - with your own reports

(5) Transfer of old data with the transactions KKA4, KKA5 and KKA6
(Rel. 2.2 or higher)

(6) Manual entry of the cost of sales (Rel. 3.0)
(6.1) - Enter with transactions KKG1, KKG2 and KKG3
(6.2) - Interaction with automatic results analysis - derivation of the
work in process and the reserves for unrealized costs
(6.3) - Display in reporting

(7) Currencies

(8) Known errors in manual results analysis

(1.1)
Entering results analysis data for manual additions and changes with transactions KKA1, KKA2 and KKA3

Results analysis for single objects is carried out with transactions KKA1 - KKA3. From the first screen after the transaction is called up, the protocol screen, you go into manual results analysis. A list with all results analysis data in cumulative form is displayed. Choosing Display -> By period' (or 'Display -> Not cumulative' in Rel. 2.1 and Rel. 2.2) you go into the display by period. In these lists you can page and enter the results analysis data manually.

(1.1.1)
Entering results analysis data in periodic display

Example:

Assume the following initial situation:
Period 1 2 3
Value manual by period 100 50 50
Value manual cumulative 100 150 200

You change only the values of period 2 in the periodic display from 50 to 60:
Period 1 2 3
Value manual by period 100 60 50

The system then calculates the following cumulative values:
Period 1 2 3
Value manual cumulative 100 160 210

The result is that a value of 10 is added in period 2.

(1.1.2)
Entering results analysis data in the cumulative display

Example:

Assume the following initial situation:
Period 1 2 3
Value manual by period 100 50 50
Value manual cumulative 100 150 200

You now change the values of period 2 in the cumulative display from 150 to 160:
Period 1 2 3
Value manual cumulative 100 160 200

The system then calculates the following values by period:
Period 1 2 3
Value manual by period 100 60 40

The result is that in period 2 a value of 10 is added and in period 3 a value of 10 is subtracted.

(1.2)
Entering results analysis data with transactions KKA4, KKA5 and KKA6

Transactions KKA4 to KKA6 are available starting with Release 2.2. You can use these transactions to add manual results analysis data.
Example:

Assume the following initial situation:
Period 1 2 3
Value manual by period 100 50 50
Value manual cumulative 100 150 200

To add the value 10 to period 2, call up the transaction, enter the period 2 and the object number, and continue to the list for entering data. In the list you enter the value 10 and fill in the fields 'Typ', 'CUC' and 'LID'. After saving, you have the following new situation:

Period 1 2 3
Value manual by period 100 60 50
Value manual cumulative 100 160 210

(1.3)
Manual entry of results analysis data with and without derivation of the cost of sales

With automatic results analysis, for each line ID the relationship (1.A) holds:

(1.A) Actual costs
- Work in process
+ Reserves for unrealized costs
= Cost of sales

If you did not switch off the 'COS freely' indicator (cost of sales freely) in Customizing for results analysis, then you cannot manually change the cost of sales. The system calculates the change on the basis of the manual change to the work in process and the reserves, so that relationship (1.A) remains valid.
If you switched off the 'COS freely' indicator in the valuation method, then you can also manually change the cost of sales. Whether relationship (1.A) is then still valid depends on your manual changes.

(2)
Deleting manual results analysis data

Manual results analysis data that you entered as described in section 1 can be reset in the same way for specific periods.
Starting with Release 2.2 you can delete an object's entire manual results analysis data at once with transactions KKA7, KKA8 and KKA9.

(3)
Interaction of automatic and manual results analysis

In Customizing for results analysis with the valuation methods there is the field 'Manual RA' (manual results analysis). This field can have the setting 'Z' (manual addition) or 'E' (manual change).

(3.1)
Interaction with manual additions

If you have set the valuation method to 'manual addition', automatic results analysis is not affected by manual changes.

(3.2)
Interaction with manual changes

If you set the valuation method to 'manual change', the manual changes of the closed periods are automatically cancelled in the first open period. This method is used with final results analysis.
Example:

Period 1 is the closing period. Results analysis was started for period 3. The following values result:

Period 1 2 3
Value automatic by period 1000 500 500
Value manual by period 0 100 0
Value automatic cumulative 1000 1500 2000
Value manual cumulative 0 100 100
Value total cumultive 1000 1600 2100

The closing period is now set to period 2. When results analysis is now carried out for period 3, the following values result:

Period 1 2 3
Value automatic by period 1000 500 400
Value manual by period 0 100 0
Value automatic cumulative 1000 1500 1900
Value manual cumulative 0 100 100
Value total cumulative 1000 1600 2000

In period 3 the automatic value was reduced by 100. That is the amount that was manually added in period 2. The period values are stored in the database.
Note: Maintain the closing period in Customizing for results analysis in the version. Starting with Release 2.2 you can change the closing period through the application menu.

(4)
Display in reporting

For better understanding you should know the following: The values from manual results analysis are saved under the same cost element as the values from automatic results analysis. The only difference is that the values of the manual changes are edited under operation KABM and those of the automatic results analysis under KABG. In each case the period values are saved in the database. If you wanted to have the manual changes under a separate results analysis cost element, you would have to reserve separate line IDs.

(4.1)
Display in reporting with the cost element report

With the cost element report you can display the results analysis data according to cost element for specific periods. For projects, this report is available in Release 2.2 or higher.
Up to and including Release 2.2, the cost element report cannot use the operation as a means of differentiation, so the manual and automatic values cannot be displayed separately here.
In Release 3.0 the report for the orders and the sales orders can use the operation as a means of differentiating.
When you have entered manual values with cumulative display, as described under 1.1.2, you can only see the manual changes if the report does not cumulate the values from periods 2 and 3. The manual changes of the two periods would add up to zero.

(4.2)
Display in reporting with the cost/revenue structure report

This report is only for projects. You can see the results analysis data arranged according to cost elemlent groups but there is no breakdown according to period. You can only see the manual changes that were entered with the method described under (1.1.1) and (1.2) The manual changes under as described under (1.1.2) cannot be shown here because they always add up to zero.

(4.3)
Display in reporting with the line-item report

If updating line items is switched on in the definition of the results analysis version, the changes to the results analysis data of a results analysis run are logged in the form of line items.
For orders, there is at present only a standard line-item report that evaluates the line items of a results analysis run. The operation is not shown, so no distinction is made between manual and automatic changes.

(4.4)
Display in reporting with your own reports

The results analysis data are in table COSB. The automatically calculated values are marked with COSB-VRGNG = 'KABG' and the manual changes with COSB-VRGNG = 'KABM'. KABG and KABM are operations.
The line items of the results analysis are in table COEPB, the header of the line-item document in table COBK. The operation is shown in the field COEPB-VRGNG.

(5)
Transfer of old data with transactions KKA4, KKA5 and KKA6

In Release 2.2 or later, you can bring the data into your old system through the batch input interface with transactions KKA4, KKA5 and KKA6. To do this you must go into Customizing for results analysis and turn on the 'Transfer old data' switch. The old data accessed in this way are then written to the object as if they had been automatically calculated. Old data can only be captured for an object in one period.

(6)
Manual entry of the cost of sales

In Release 3.0 it is possible to manually enter the cost of sales. Automatic results analysis then calculates the work in process and the reserves.

(6.1)
Entry with transactions KKG1, KKG2 and KKG3

Transactions KKG1, KKG2 and KKG3 are used to enter the cost of sales manually. In these transactions you can enter the cost of sales for each line ID, or enter the total value under any line ID which is then distributed to the individual line IDs by automatic results analysis.

(6.2)
Interaction with automatic results analysis - derivation of work in process and reserves for unrealized costs

The apportionment of the manually entered cost of sales to the line IDs can be accepted as is or automatically split up equivalent to the planned or actual data.
Work in process and reserves for unrealized costs are calculated from the different between the actual costs and the cost of sales, just as with other similar results analysis methods.

(6.3)
Display in reporting

The manually entered costs of sales are updated under the same cost elements as the values in automatic results analysis, but under the special operation 'KABF'. For display in reporting, see the explanations in section (4).

(7)
Currencies

The results analysis data are always carried in the controlling area currency. In Release 3.0 they are also carried in company code currency.
If the company code currency is not the same as the controlling area currency, please observe the following:
With transactions KKA4 to KKA6 and KKG1 to KKG3, the results analysis data are always entered in the controlling area currency, converted to the company code currency when the function 'Save' is called up, and updated in both currencies.
With transactions KKA1 to KKA3 the data are first processed in the controlling area currency, converted when the Save function is called up, and finally offered for editing in the company code currency. When the converted values are manually changed again in the company code currency, the changes are not converted back into the controlling area currency. Calling up the Save function updates the data.

(8)
Known errors in manual results analysis
Note 18449, 'Manual results analysis, periodic display',
Release 2.1A - 2.1J and 2.2A - 2.2D

Note 18874, 'Manual results analysis, cumulated display',
Release 2.1* and 2.2A - 2.2D

SAP Note 19412 - Incorrect bill of exchange issue date in FBW2

Symptom:

The field 'Issue date of the screen' does not display the issue date of the bill of exchange that is entered manually in the payment run but the execution date (posting date) of the payment run.

Cause and prerequisites

This is intended to be this way in the standard system but may cause some confusion.

Solution
You can display the entered date by making a small modification. In Include MF05AFW0, you have to replace the line
BSED-WDATE = *BKPF-BUDAT.
by:
BSED-WDATE = *BSED-WDATE.
You have to repeat this change after each upgrade, because it is not made in the standard system (status 3.0a).

SAP Note 19410 - INFO: Char.validity check f.external data transfer

Symptom:

1. When you transfer external data to CO-PA, some of the imported records are placed in an error file. The system displays the error message KE100: "The characteristic value & is not allowed".

2. You want to deactivate the validity check for a certain characteristic during an external data transfer.

Cause and prerequisites

The system generates the above-mentioned error message KE100 when

a) you import a characteristic value that does not exist in the corresponding check table,

b) you import a characteristic value that does belong to a characteristic with a value table in the system, but this value table is not recognized as a check table in the data structures for CO-PA because a foreign key text has not been maintained.

Example:
You want to fill field "Cost element" during an external data transfer. Field 'KSTAR' (cost element) has the check table entry "*". The value table for the corresponding domain is 'CSKA'.
Here error message KE100 is displayed because the foreign key dependency is not maintained for field "KSTAR", even though the external data transfer fills a field whose domain has a value table in the CO-PA data structures ("CSKA"). This can be seen in the fact that the CO-PA data structures contain "*" for field "KSTAR" in the ABAP/4 Dictionary for the field "Check table".

In case a) above, the message is correct. In case b), the message is displayed because no check can be performed to ensure that no incorrect characteristic values are transferred to the system.

If, in case b), you do not want to receive the error message (because you can be certain that the data being imported is correct), you can make the modification described below. Note that when you transfer actual data (Transaction KE4X), the records that contain errors are stored in an error file instead of a batch-input session.

Solution

Modify program LKEI1U04 (in Release 4.0, LKEA4U06) as follows (changes are marked with " <--- insert "): ....
LOOP AT PRUEFTAB.
CHECK PRUEFTAB-FIELDNAME NE 'XXXXX'. <--- insert
CHECK PRUEFTAB-CHECKTABLE NE '*'. <--- insert
....
ASSIGN COPA_EINZELPOSTEN+(PRUEFTAB-INTLEN) TO .
....

Caution!:

These modifications make it possible to supply all the characteristics with the check table "*" via external data transfer without a check being run against any existing data in the R/3 System, or to deactivate the check for one characteristic with the field name "XXXXX".
In the above example, one could replace "XXXXX" with "KSTAR" to supply field "Cost element" without any check being run against the value table "CSKA". If you make this modification, you need to make sure yourself that the characteristic is filled with valid values.


Additional key words

KE4X, KE1X, RKEE0000, RKEExxxx, COPA_CHECK_CEEP, CSKA

SAP Note 19409 - XXL: Applications supporting the interface

Symptom:

Customer query: Which applications are currently able to export data via the XXL interface?

Cause and prerequisites

From Release 3.0 onwards this information will be included in the XXL documentation.

Solution

1. CO-PA / EIS (exporting a complete data recall or individual pages)

2. ABAP/4 Query (statistics, rankings, basic lists)

3. Logistics Information System (Sales, Purchasing, Materials)

4. FI account display (A/P, A/R, G/L line items)

SAP Note 19404 - Header conditions in document: E00088

Symptom:

Error E00088 occurs on the pricing screen in the document header (header conditions).

Cause and prerequisites

There are subtotals in the pricing procedure for which the description has not been maintained in the logon language. The same occurs with missing condition descriptions.

Solution
Create the descriptions in the logon language.

Additional key words

VA03, VA02

SAP Note 19402 - Condition update: Cumulative values too large

Symptom:

With the function, Cumulative Values, the values shown are greater than the maxiaml values defined in the condition record

Cause and prerequisites

During the check of the maximal values the statistics record used to record the maximal value is not locked. This can cause the cumulative value to be greater than the maximal value. This can only occur when two users enter sales orders at the same time and use the same statistics record which records the values.

Note: This can also occur because of the asyncronous update-task.

Solution
According to our customers, this problem does not occur in a normal productive enviornment. It only occurs during testing.

SAP Note 19396 - Dotted lines are not dotted

Symptom:

Lines in networks and bar graphs that were defined as dotted lin Customizing are not displayed as dotted under Windows when they are thicker than one pixel.

Cause and prerequisites

Windows does not have a character command that enables drawing of dotted lines that are thicker than one pixel.

Solution
Until we can find an alternative way to solve the problem with a reasonable amount of effort, please set the line thickness in Customizing to 1 (instead of the previous 2-4).

SAP Note 19395 - SAPDBA/BRRESTORE:"device busy" when restoring from

Symptom:

SAPDBA or BRARCHIVE/BRBACKUP/BRRESTORE issue the message "device busy" when verifying or reloading data files on/to tape.

Cause and prerequisites

It is possible (previously observed under OSF1) that the error message "device busy" appears when the tape is fast-forwarding or rewinding because the next action already attempts to access the tape.

Solution
Change the tape access commands in the SAPDBA menu (at the call of BRBACKUP, etc.) or in profile init.sap:

"Position command" (SAPDBA menu) or profile parameter "tape_pos_cmd"
change from "mt -f $ fsf $" to "mt -f $ fsf $; sleep 5"

"Rewind command" (SAPDBA menu) or profile parameter "rewind"
change from "mt -f $ rew" to "mt -f $ rew; sleep 5"

SAP Note 19389 - Using value variables in formulas

Symptom:

For certain requirements, you have to refer to value variables in formulas. Example: In a column of a report, the report should divide a value by the current number of periods in a column. The current period is defined via a value variable in the report.

Cause and prerequisites

Functional requirement.

Solution
Only beginning with Release 3.0C is it possible in computing formulas to refer to value variables used in the report.

Additional key words

Report Writer

SAP Note 19381 - Termination GI212: When reading a record in table &...

Symptom:

Termination GI212 when you post to FI-SL tables containing objects.

Cause and prerequisites

The status of the (unique) index 1 of the object table which is issued in the message differs from the database status (for example, index modification). This can be checked with the database utility (SE14) (Database index -> Compare definitions). As a result, an insert in the object table may fail and the above termination occurs.
Another possible cause: Status of the number range object 'GL_OBJECT' was reset. (Possibily through the transport or client copy). The insert may also fail because of this.

Solution
Case 1: Using transaction SE14, delete and recreate the database index.
Case 2: Increase the number range status. The best way to do this is to use the transaction SE16 to display the object table (sort according to object number, '*' in the object number field, then all will really be selected) and then set the status higher than the highest object number (using transaction SNRO).

SAP Note 19380 - General questions on the installation of IS-H

Symptom:

Information for

• Contracts Department

• Dispatch

• Sales and Distribution

• New customers

Other terms

Industry Business Solution IS-H, delivery dates, new installation

Reason and Prerequisites

Questions concerning new IS-H installations
Current situation, platforms, combinations with other Industry Business Solutions, dates, non-supported SAP releases

Solution

1. Current status:

At present, the following IS-H release is supported (since CW 20/2004):
IS-H 4.72 on Enterprise 47x110 SR1 or Enterprise 47x200
(Patch level 17 of SAP_APPL is the minimum prerequisite. For a productive use of IS-H 4.72, the application of CRT 1 for SAP_APPL 18-20 is mandatory!)
The material number of the current installation CD is 51020649.
Apart from IS-H 4.72, the CD also contains Patch 1.

2. Maintenance levels or Support Packages to be imported additionally

For 4.03A: See release strategy Note 109193
For 4.03x (x > B): See Note 160083
For 4.61 track: See Note 213747
For 4.62 track: See Note 329772
For 4.63: See Note 434223
For 4.63B: See Note 528323
For 4.71: See Note 605628
For 4.72: See Note 703635

As of 4.63, upgrades to IS-H releases are only sent if you place a corresponding order for them with the Contracts Department of the international subsidiary responsible. When placing such orders, remember to include your installation number.
The same applies to Support Releases.
Support Packages are to be downloaded from the SAPNet. A collection of Support Packages is available on the Support Release CDs. Every Support Release CD contains the add-on Support Packages of the previous release (for example, the CD for Support Release 4.62C contains the add-on Support Packages for 4.62B).
If no more Support Releases are to be created within a maintenance track, a collection CD shall still be created for the add-on Support Packages of the last Support Release.

3. Release strategy

Basically, there will be no new installations on functional releases (for example 4.6A).
Also refer to the release strategy Note 212075.

4. Restrictions with specific platforms (OS/DB)

There are currently no restrictions concerning specific platforms.

5. Languages

The following languages are currently supported:

• English

• Dutch

• Spanish

• French

• Italian

• Greek (as of 4.63, shipped by international subsidiary Greece)

• Turkey (as of 4.63, shipped by international subsidiary Turkey)

• Hebrew (shipped by an SAP partner)

6. Combinations of different Industry Business Solutions.

Combinations of different Industry Business Solutions must be released explicitly. At the moment, the following combinations are released:

• Combination IS-H with HR-PSG and/or IS-PS. Express authorization for HR-PSG is necessary only up to 4.0B since HR-PSG is part of the SAP CORE as of 4.5A.

• All other combinations with IS-H are not released. The following add-ons or plug-ins, and so on, do not need a special release and are allowed with all add-ons:

• PI (mandatory as of 4.61A)

• WP-PI

• YEAR2000

• P9M (Ready-to-Run R/3)

• PDB ADD-ON

7. Duration of an IS-H installation

The IS-H installation can take between 2 to 5 hours, depending on the computer. This estimation does not include preparations or data backup activities.

8. Overview of IS-H notes

An overview of all the useful IS-H notes on the topics installation, upgrade, release policy, and so on, can be found in Note 108123 (4.0), Note 212072 (4.6), and Note 605618 (4.7).

SAP Note 19373 - Maint.order: Message CF230 when allocating PRT

Symptom:

IW31, IW32: When you allocate a production resource/tool to the operation of a maintenance order, error message E230(CF) appears on the screen ("Production resource/tool is not intended for this type of task list").

Cause and prerequisites

Concept information:
Every production resource/tool is allocated to a specific task list usage.
For this task list usage there has to exist an allocation to plant maintenance task list types (Customizing Transaction OP88). The default value for maintenance orders is set to "equipment task list". After a general maintenance task list has been allocated to the order, the task list type for the maintenance order changes to "general maintenance task list".
The production resource/tool must have a task list usage in which both "equipment task list" and "general maintenance task list" have been allocated. The other option is to change the customizing data of your system (Transaction OP88).

Note on the correction:
In Release 2.1, the task list type was defined in Customizing. The default value of the field was "equipment task list". The field could not be maintained in the interface.
Note the concept information.

From Release 2.2, the task list type was no longer defined in Customizing. Error CF230 appears when you allocate a PRT in the case of all order types created in PM from this time. The correction
ensures that the default value is entered in the field by the program.
Enter correction P22K005618.

Release 3.0:
Note the concept information.

Solution
The PRT must have a task list usage in which the task list types 'Equipment task list' and 'General maintenance task list' are allocated. The other option is to change the Customizing data in your system (Transaction OP88).

For Release 2.1 and 3.0, no action is necessary

For Release 2.2:
Enter correction P22K005618:
Also enter note 30044!

1.) Program LCOIHTOP

...

* sonstige Konstanten
DATA: Y_ORDER VALUE 'O'. "(O)rder
DATA: STATUS_PRINT(5) VALUE 'I0007'. "Printed
DATA: Y_ZAUN VALUE '#'.
DATA: Y_BLDGR_DETAIL_DARK(2) VALUE 'DD'. "Bldgr für Dunkle Detaildynpro
DATA: Y_KONTIERUNGS_TYP_ORDER LIKE T163K-KNTTP VALUE 'F'.
DATA: Y_BELEGART_BANF LIKE EBAN-BSART VALUE 'NB '.
DATA: Y_ERSTELLUNGS_KZ_BANF LIKE EBAN-ESTKZ VALUE 'F'.
DATA: YX VALUE 'X'. "Flag X
DATA: YIPHAS_ABGESCHLOSSEN LIKE CAUFVD-IPHAS VALUE 3.
DATA: Y_PLNTY_E LIKE CAUFVD-PLNTY VALUE 'E'. "P22K005618


...

2.) Program LCOIHO10


MODULE TRANS_INIT OUTPUT.

*--- Plantyp vorbelegen Default immer 'E' -----------------------------
CAUFVD-PLNTY = Y_PLNTY_E. "P22K005618

*--- nur einmal prozessieren ------------------------------------------
CHECK T490 IS INITIAL.

...

3.) Program LCOIHI10

MODULE CHECK_ORDER_TYPE INPUT.

*... nur bei Anlegen
CHECK TC10-TRTYP EQ Y_TRTYP_ANL.

CALL FUNCTION 'CO_TA_T003O_READ'
EXPORTING
T003O_AUART = CAUFVD-AUART
IMPORTING
T003OWA = T003O
EXCEPTIONS
NOT_FOUND = 1.
IF SY-SUBRC <> 0.
MESSAGE E205 WITH CAUFVD-AUART.
ENDIF.
*--- Statusschema versorgen -------------------------------------------*
CAUFVD-STATS = T003O-STSMA.


CALL FUNCTION 'CO_TA_T003P_READ'
EXPORTING
T003P_SPRAS = SY-LANGU
T003P_AUART = CAUFVD-AUART
IMPORTING
T003P_TXT = CAUFVD-ARTTEXT
EXCEPTIONS
NOT_FOUND = 1.

*...Pruefen ob Auftragstyp fuer diese Transaktion zulaessig ist
IF T003O-AUTYP <> T490-AUTYP.
MESSAGE E202.
ENDIF.

CALL FUNCTION 'CO_TA_T399X_READ'
EXPORTING
AUART = CAUFVD-AUART
WERKS = CAUFVD-IWERK
IMPORTING
STRUCT = T399X
EXCEPTIONS
NO_ENTRY = 01.
IF NOT SY-SUBRC IS INITIAL.
MESSAGE E206.
ENDIF.

*--- Plantyp versorgen ------------------------------------------------*
* CAUFVD-PLNTY = T399X-PLNTY. "P22K005618

...

4.) Program LCOIHF10

FORM ORDER_CHANGE.

DATA BEGIN OF ORD_PRE OCCURS 0.
INCLUDE STRUCTURE ORD_PRE.
DATA END OF ORD_PRE.

...

* Header aus BT lesen
CALL FUNCTION 'CO_BT_CAUFV_READ_WITH_KEY'
EXPORTING
AUFNR_ACT = CAUFV-AUFNR
IMPORTING
CAUFVD_EXP = CAUFVD.

*--- Plantyp vorbelegen -----------------------------------------------*
CAUFVD-PLNTY = Y_PLNTY_E. "P22K005618

...


5.) Program LCODBU04

FUNCTION CO_DB_VAFILOA_READ.
*"----------------------------------------------------------------------
*"Lokale Schnittstelle:
*" IMPORTING
*" CAUFVD_IMP LIKE CAUFVD STRUCTURE CAUFVD
*" EXPORTING
*" *ILOA LIKE ILOA STRUCTURE ILOA
*" CAUFVD_EXP LIKE CAUFVD STRUCTURE CAUFVD
*" RIWO1_EXP LIKE RIWO1 STRUCTURE RIWO1
*" EXCEPTIONS
*" NOT_FOUND
*"----------------------------------------------------------------------
DATA: Y_PLNTY_E LIKE CAUFVD-PLNTY VALUE 'E'. "P22K005618
*--- View AFIH und ILOA einlesen, falls nicht schon gemacht -----------*
IF CAUFVD_IMP-ILOAN IS INITIAL.
SELECT SINGLE * FROM VAFILOA WHERE AUFNR EQ CAUFVD_IMP-AUFNR.
* . . . nix gefunden
IF SY-SUBRC NE 0.
RAISE NOT_FOUND.
ELSE.
* . . . Caufvd_Exp (output = input)
CAUFVD_EXP = CAUFVD_IMP.
* . . . *iloa
MOVE-CORRESPONDING VAFILOA TO *ILOA.
* . . . Caufvd_exp mit VAFILOA ergänzen
MOVE-CORRESPONDING VAFILOA TO CAUFVD_EXP.
* VAFILOA-AUFNR = CAUFVD_EXP-IAUFNR.
* VAFILOA-KOKRS = CAUFVD_EXP-IKOKRS.
* VAFILOA-BUKRS = CAUFVD_EXP-IBUKRS.
* VAFILOA-GSBER = CAUFVD_EXP-IGSBER.
CAUFVD_EXP-IAUFNR = VAFILOA-AUFNR.
CAUFVD_EXP-IKOKRS = VAFILOA-KOKRS.
CAUFVD_EXP-IBUKRS = VAFILOA-BUKRS.
CAUFVD_EXP-IGSBER = VAFILOA-GSBER.
CAUFVD_EXP-AUFNR = CAUFVD_IMP-AUFNR.
CAUFVD_EXP-KOKRS = CAUFVD_IMP-KOKRS.
CAUFVD_EXP-BUKRS = CAUFVD_IMP-BUKRS.
CAUFVD_EXP-GSBER = CAUFVD_IMP-GSBER.
* . . . *AFIH
* MOVE-CORRESPONDING CAUFVD_EXP TO *AFIH.
* . . . RIWO1
MOVE-CORRESPONDING CAUFVD_EXP TO RIWO1_EXP.
ENDIF.
*--- wenn schon eingelesen die WA's füllen
ELSE.
* . . . Caufvd_Exp (output = input)
CAUFVD_EXP = CAUFVD_IMP.
* . . . VAFILOA
* MOVE-CORRESPONDING CAUFVD_IMP TO VAFILOA.
* . . . *ILOA
MOVE-CORRESPONDING CAUFVD_EXP TO *ILOA.
*ILOA-AUFNR = CAUFVD_IMP-IAUFNR.
*ILOA-KOKRS = CAUFVD_IMP-IKOKRS.
*ILOA-BUKRS = CAUFVD_IMP-IBUKRS.
*ILOA-GSBER = CAUFVD_IMP-IGSBER.
* . . . *AFIH
* MOVE-CORRESPONDING CAUFVD_IMP TO *AFIH.
* . . . RIWO1
MOVE-CORRESPONDING CAUFVD_EXP TO RIWO1_EXP.
ENDIF.

*--- Speicherplatz freigeben -------------------------------
FREE VAFILOA.

CAUFVD_EXP-PLNTY = Y_PLNTY_E. "P22K005618

ENDFUNCTION.

6.) Actions

- Generate programm SAPLCOIH
- enerate programm SAPLCODB

SAP Note 19358 - Rebate paymt: Curr. transl. uses incorr. exch. rate

Symptom:

Payment using incorrect exchange rate. There may be two reasons:

• Exchange rate type 'M' is used to generate the rebate credit memo during the rebate payment although another exchange rate type is defined in the customer master record.

• Sales volumes are updated in local currency and must be translated into the currency of the rebate agreement. The translation is done using the validity end date of the bonus agreement. This is incorrect.

Cause and prerequisites

Not provided

Solution
The error is not yet completely corrected in the SAP Standard System. A temporary solution exists for problem 1. Problem 2 is solved in Release 4.0A.

With a modification, you can hard code the exchange rate type.

Additional key words

Rebate, rebate payment, foreign currency translation, exchange rate type, translation

SAP Note 19355 - Screen Painter: Termination during test

Symptom:

The "Test" function is selected in Screen Painter.
A termination occurs with the ABAP/4 runtime error DSTEP_NO_MODULE.
() EUNOTE, EUSCREENPAINTER

Cause and prerequisites

The flow logic of the test screen received a MODULE statement for a module that is not defined in the moule pool.

Solution
The function "Check -> Consistency" will find the MODULE statements that are not defined in the module pool. Please correct the inconsistency in the flow logic and then select the "Test" function again.
In most cases, a termination can only occur when the incorrect MODULE statement appears in one of the two sections PROCESS ON HELP-REQUEST or PROCESS ON VALUE-REQUEST; modules in the sections PROCESS BEFORE OUTPUT and PROCESS AFTER INPUT are usually skipped during the test.
The exception to this is the testing of a screen that is the initial screen of a transaction, and for which the user expressly defined that full flow logic should be tested in the test area popup.

SAP When you call startsap, the following error messages are issued: "Database system startup failed!" "cannot set group id" The database system is

Symptom:

When you create a table maintenance dialog for extended table maintenance, the maintenance screens do not contain all the fields. The dialog was created using report RSVIEWGN or with the transaction "Generate table maintenance dialog".

Cause and prerequisites

The table/view contains too many/too long fields; they do not all fit on the maintenance screen.

Solution
There are several possible solutions:
1. The maintenance dialog was only defined in one level
Generate a two-level maintenance dialog. All fields of the table/
view will then appear on the detail screen.
2. The maintenance dialog is already two-level
2.1: Use the Screen Painter to manually revise the detail screen.
Missing fields must be manually added to the screen. FIELD
statements for the newly added fields must be added in the first
CHAIN...ENDCHAIN statement of the flow logic.
2.2: If the fields cannot be manually placed on the detail screen
using Screen Painter, you must
- For a table: define several views and generate a maintenance
dialog for each one
- For a view: reduce the number of fields in the Data Dictionary,
define an additional view for the fields that you removed from
the first view, and generate a separate maintenance dialog.

SAP Note 19349 - startsap/stopsap report "cannot set group id"

Symptom:

When you call startsap, the following error messages are issued:

"Database system startup failed!"
"cannot set group id"

The database system is not started

or

When sapdba is called the error message 'no execute permission' appears.

Cause and prerequisites

The access privileges of files "infstart" (start Informix OnLine) and/or "infstop" (stop Informix OnLine) are not set correctly.
These files must belong to user "root" and and so-called "s bit" must be set to enable the appropriate Informix commands "oninit" and "onmode -ky" to be called.

Solution
Check the access privileges for files "infstart" and "infstop" in directory "/usr/sap//exe/run".
The owner must be user "root", the group "sapsys", and the s bit must be set.
A list of all inf* files in this directory appears below.
If files other than "infstart" and "infstop" have access privileges in your system that are different from the listing below, please change them as well.

-rwsr-xr-- 1 root sapsys 114688 Dec 9 11:51 infaccess
-rwxr-xr-x 1 qihadm sapsys 540672 Jan 5 14:06 infarcexe
-rwxr-xr-x 1 qihadm sapsys 544768 Jan 5 14:06 infarclog
-rwxr-xr-x 1 qihadm sapsys 974 Nov 9 17:13 infarclog.csh
-rwxr-xr-x 1 qihadm sapsys 544768 Jan 5 14:06 infarcres
-rwsr-xr-- 1 root sapsys 114688 Dec 9 11:51 infcatlgr
-rwxr-xr-x 1 qihadm sapsys 110592 Dec 9 11:51 infgethome
-rwsr-xr-- 1 root sapsys 114688 Dec 9 11:51 infstart
-rwsr-xr-- 1 qihadm sapsys 524288 Dec 9 11:51 infstatus
-rwsr-xr-- 1 root sapsys 114688 Dec 9 11:51 infstop
-rwxr-xr-x 1 qihadm sapsys 561152 Dec 16 15:02 infstrfc
-rwxr-xr-x 1 qihadm sapsys 552960 Dec 13 17:00 infupdstat

Make the changes as user "root".
The following chmod command can be used to set the s bit (-rws):

"chmod 4754 datei_name"

Once you have made the changes, you should once again be able to use startsap/stopsap to start up and shut down the database.

SAP Note 19347 - E812 when creating BOMs via batch input

Symptom:

When you copy BOMs via batch input (report RCSBI010), error message E812 occurs: 'Item category & is not defined (record is ignored)'.

Cause and prerequisites

Structure BICSP, which is used for BOM items, contains a field BICSP-XLINE of type INT4 (internal X). If you now generate the corresponding structure for the external system via the general generation tool, the field corresponding to field BICSP-XLINE is generated incorrectly. As a result, the structures in the external system and the BICSP structure do not match. The item records imported by RCSBI010 are moved.

Solution
In the structure in the external system, you have to insert a dummy field directly before field BICSP-XLINE to compensate the movement.

Additional key words

Batch input

SAP Note 19341 - Release R/3 Releases for SAP R/3 add-ons

Symptom:

When you upgrade an SAP R/3 System to a new R/3 source release you are prompted for an additional password for installed add-ons in phase KEY_CHK.

Cause and prerequisites

1. Your system is a ready-to-run installation.

2. A release upgrade is carried out in a system in which at least one SAP R/3 Add-on (for example, an industry solution) was installed. The upgrade to a new R/3 standard release can only be carried out if the upgrade is released for all additional products installed.

This is checked by a password required in phase KEY_CHECK (as of SAP Release 2.2E). Solution

ad (1): Refer to Note 111601.

ad (2):
For each R/3 release (as of 2.2E), you will find information below on the release of the above-mentioned SAP R/3 additional products.
If a reference is made to a note, the SAP Add-on is released on this SAP release. This note contains the password as well as further information important for the upgrade.
In all other cases, the SAP release for this SAP R/3 Add-on is (still) not released. You have to cancel the SAP upgrade.
If several more products are installed in one system, all installed SAP R/3 Add-ons must have been released.
Most add-ons will not support functional releases (for example, 3.1G).
------------------------------------------------------------------------

Upgrade to R/3 Release 2.2E:
IS-H: Note 20851
IS-IS: Note 23188
IS-P: Note 29177
IS-OIL: not supported
------------------------------------------------------------------------

Upgrade to SAP R/3 Release 2.2F:
IS-H: Note 26570
IS-IS: Note 27443
IS-PSD: Note 29177
IS-OIL: not supported
------------------------------------------------------------------------

Upgrade to SAP R/3 Release 2.2G:
IS-H: Note 34708
IS-PS: Note 35659 (new installation 2.23/1 March 96)
Note 45684 (spec. upgrade Netherlands August 96)
IS-IS: not supported, next release is 2.2I
IS-PSD: not supported, next release is 2.2I
IS-OIL: not supported
------------------------------------------------------------------------

Upgrade to SAP R/3 Release 2.2H:
IS-H: Note 45409
IS-PS: not supported
IS-IS: not supported, next release is 2.2I
IS-PSD: not supported, next release is 2.2I
IS-OIL: not supported
------------------------------------------------------------------------

Upgrade to SAP R/3 Release 2.2I:
IS-H: Note 52506
IS-PS: not supported
IS-IS: Note 60009
It is absolutely necessary that you read the instructions in Note 60009 during the upgrade to SAP maintenance level 2.2I! Otherwise, data may be lost.

IS-PSD: Note 60120
IS-OIL: not supported

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

Upgrade to SAP R/3 Release 3.0A or 3.0 FCS:
IS-H: not supported
IS-IS: not supported
IS-PS : not supported
IS-PSD: not supported
IS-OIL: Note 39206
------------------------------------------------------------------------

Upgrade to SAP R/3 Release 3.0B:
IS-H: not supported
IS-IS: not supported
IS-PS : not supported
IS-PSD: not supported
IS-OIL: not supported
------------------------------------------------------------------------

Upgrade to SAP R/3 Release 3.0C:

R/3 Retail: not supported at present
IS-H: not supported
IS-IS: not supported
IS-PS : not supported
IS-PSD: not supported
IS-OIL: Note 44261
-----------------------------------------------------------------------
Upgrade to SAP R/3 Release 3.0D:
R/3 Retail: Note 52572
IS-H: Note 43948 only upgrade to 3.0F.
IS-PS: not supported
IS-IS: Note 46445 deadline: see 18590
IS-PSD: Note 53042
IS-OIL: Note 48563 -----------------------------------------------------------------------
Upgrade to SAP R/3 Release 3.0E:
IS-H: Note 53085 only upgrade to 3.0F.
IS-PS: Note 52850 deadline: 25/10/1996
IS-IS: Note 60436 deadline: 09/12/1996
IS-PSD: Note 60131 deadline: 20/12/1996
IS-PAM: Note 62347 deadline: 13/01/1997
IS-OIL: not supported -----------------------------------------------------------------------
Upgrade to SAP R/3 Release 3.0F:
CIN: Note 83675
HR-PSG: Note 73508
IS-H: Note 67149
IS-IS: Note 68874 (3.01D, 3.0D2,3.0D3) deadline 27/03/1997
Note 74827 (2.22F9)
IS-PS: Note 70838 deadline 27/03/1997
IS-PSD: Note 70147 Release 3.01/2 deadline 14/04/1997
IS-PSD: Note 74589 Release 3.02 deadline 30/06/1997
IS-PAM: Note 67619(3.01), 71587(3.01/1) deadline 10/03/1997
IS-OIL: not supported
IS-SW: Note 72972 deadline 25/04/1997
LSA: Note 67062 deadline 27/03/1997
R/3 Retail Note 70737
SD-BIL-RR Note 83294
-----------------------------------------------------------------------
Upgrade to SAP R/3 Release 3.1G:
CIN: not supported
HR-PSG: not supported
IS-AD: not supported
IS-H: not supported
IS-OIL not supported
IS-PS: not supported
IS-SW: not supported
LSA: not supported
IS-U/FERC: Note 83957
-----------------------------------------------------------------------
Upgrade to SAP R/3 Release 3.1H:
BW-BCT 1.2A: Note 107215 Upgrade deadline: 06/1998
BW-BCT 1.2B: Note 137347 Upgrade deadline: 03/1999
CIN: Note 100080 Installation deadline: 05/1998
Upgrade: 07/1998
HR-PSG: not supported
IS-AD: Note 98258 Upgrade deadline: 06/05/1998

IS-H: not supported
IS-OIL: Note 85746 Upgrade deadline: 02/01/1998
Installation: 03/01/1998
IS-PS: not supported
IS-SW: Note 86058 deadline: 12/12/1997
LSA: not supported

SD-BIL-RR Note 99918 deadline: 04/17/1998
IS-U/WCM: Note 105652 deadline: 06/22/1998
IS-U/FERC: Note 86626 deadline: CW 43, 1998
-----------------------------------------------------------------------
Upgrade to 3.1I
BW-BCT 1.2A: Note 107213 Upgrade deadline: 09/1998
BW-BCT 1.2B: Note 137352 Upgrade deadline: 03/1999
HR-PSG: not supported
IS-U/FERC: Note 109626 deadline: 08/1998
IS OIL: not supported.
IS-AD: not supported.
PDB-IF: Note 143456 Upgrade deadline: 05/1999
PDB-ADD-ON: Note 145738 Upgrade deadline: 05/1999
B2B-PRO-PI: Note 146638 Upgrade deadline: 05/1999
PI-A 2000.1: Note 302602 Date Upgr.: 06/2000
PI 2000.1: Note 302601 Date Upgr.: 06/2000

----------------------------------------------------------------------
Upgrade to 3.1I Support Release 1
PI: Note 328371 Date Upgr.: 09/2000
PI-A: Note 328372 Date Upgr.: 09/2000
----------------------------------------------------------------------
The following applies to all repository switch upgrades in systems with add-ons/IS installations as of 3.0x:
You can only install from the SAP standard CD if you also have one (or more) additional IS-CDs.
There will be a separate IS-CD for each IS system. If you use combinations of IS solutions, you need all appropriate IS CDs.

Additional key words

KEY_CHK, R3up password, SAP R/3 Add-on, industry solution, country version Brazil / Argentina, country version India, ready-to-run R/3
IS-H, IS-IS, (IS-B, TR-TM, IS-R) IS-PS, IS-PAM, IS-PSD, IS-OIL, IS-SW, LSA, CIN, IS-AD, SD-BIL-RR, IS-U/WCM, IS-U/FERC, Banking, BW-BCT