SAP OSS Notes: 1/2/11

6.1.11

SAP Note 17375 - Update termination "Too complicated SQL statement"

Symptom:

Update termination with the message "SQL statement too complex" and the error number ADA-1101 in program SAPLGLIV.
This note is relevant for all ADABAS customers using any release following Release 2.2C.

Cause and prerequisites

The update statement is too long in the ADABAS environment.

Solution
Make the changes listed below in Include program FGIDBF33, then run program SAPFGIDB. Because the changes may have far-reaching circumstances, please test its effects before implementing the change in your production system. Changes may only be made when other users are not posting transactions in a productive system.
FORM CREATE_UPDATE_USED.
************ Control constants *****************************************
* ANZ: Nbr of periods updated with one update statement
* NO_IF: if flagged no if is generated before the update
* DATA: ANZ LIKE T800A-FLDGR VALUE 17, "<-- delete ---
* DATA: ANZ LIKE T800A-FLDGR VALUE 09, "<-- insert ---
NO_IF(1) TYPE C VALUE ' '. ***********************************************************************

SAP Note 17368 - Logical databases C_K make no selections

Symptom:

The selection screen of the logical database does not appear for reports that you have written yourself for the logical databases CRK, CIK, CPK or CEK. Independently of whether PARAMETERS/SELECT-OPTIONS is defined in the report or not, no cost centers and, therefore, also no dependent data records in the logical database are determined.

Cause and prerequisites

To display the selection screen of the respective logical database, reports that you have written yourself must include the ABAB/4 statement
TABLES: XXLDB, RKLDB .
If this statement is missing, the selection screen of the logical database is not processed. When this happens, the limitation of the cost center to the fiscal year always takes the validity period of the cost center 00.00.000 - 00.00.000. As a result, no data can be selected.

Solution
Include the statement
TABLES: XXLDB, RKLDB .
in the report.
Please note that the 4 logical databases listed were designed specifically for archiving (see note number: 12937) and that the selection screens for these databases do not allow all the possible limitations (for example, for individual cost centers).
If you want to add further program limitations in addition to the limitations of the logical database, you must define these yourself (PARAMETERS or SELECT-OPTIONS) in your report.
Extensions to the selection conditions of the logical database (for example, selection in several fiscal years at the same time) is not possible!

SAP Note 17348 - Suppressing Message CO266

Symptom:

The message CO266 ("Standard sequence and operation & created") appears.
The customer would like to suppress this message (which appears when a
routing could not be selected).

Solution
Program modification in Module LCOSDU08 :

.
.
PERFORM OPR_SEQ_STATUS_INIT USING CAUFVD.

CAUFVD_EXP = CAUFVD.
* nur Message wenn nicht extern aufgerufen
IF PROD_COST IS INITIAL.
* MESSAGE I266 WITH AFVGB_APP-VORNR. <---- delete statement
ENDIF.

ENDFUNCTION.

SAP Note 17347 - Change Default transaction type

Symptom:

The customer wants to be able to call up the posting transactions in Asset Accounting using different transaction types.
Changing the default transaction types does not have the desired effect.

Additional key words

TABWV TABW OA81 ABAO AB01

Cause and prerequisites

The default transaction types in Table TABWV (which can be maintained with transaction OA81 in customizing) are effective only for auto- matic postings, e.g., Depreciation postings with ABF1, Assets under construction settlement with AIBU....

Solution
Changing the default movement types for manual postings from special transactions is possible only by modifying the definition of the trans- action using SE93. You can change the transaction type in this transaction (field BWASL). You can find the name of the transaction you want to change via the path SYSTEM -> STATUS.

SAP Note 17321 - DBIF_RSQL_SQL_ERROR in system log or short dump

Symptom:

DBIF_RSQL_SQL_ERROR
DB error -874 at SEL access to table VBBS
floating point exception
Module name : absapsql ; line 1408 or similar messages

Cause and prerequisites

The tables are possibly generated incorrectly.

Solution
Reactivate the DDIC structure. The database structure possibly also needs to be recreated.

SAP Note 17307 - Message CZ140 / CZ141 during material master update

Symptom:

When updating the material master with transaction CA96 or CA97, the following error messages occur when executing the function 'Transfer':
CZ140 'Length of material number is larger than the current setting'
or
CZ141 'Entry to long, format ......"

This error occurs if the length of the material number set in Customizing (view "Material Number Format change -> Transaction OMSL) is less than 18.

Cause and prerequisites

Error in function module CP_MA_SCHEDULING_UPDATE, LCPMAU02

Solution
Correction P22K003903 in Release 2.2C:

Additional key words

material master update

SAP Note 17304 - MR01 MRHR Consignment stock acct. w/net posting

Symptom:

If you post consignment stock accounting with a net document type (e.g. RN), a balance remains on the consignment liabilities account.

Other terms

MRKO, M8 733, M8733

Reason and Prerequisites

Net postings are not logical for consignment stock accounting, as the goods issue that constructs the liabilities account can only be posted gross.

Solution
In the accounting, make sure that you use a gross document type (for example document type RE) in Customizing (transaction OMR4).

SAP Note 17293 - KE21/screen SAPLKEA30300

Symptom:

Problems during batch input from trasaction KE21 or KE11 (Create profitability analysis line items or profit planning):
If the batch input session contains screen SAPLKEA30300, then after carrying out the first transaction (KE21) the next transaction has no data in the first screen.

Cause and prerequisites

Transaction KE21 sends screen SAPLKEA30300 depending on whether the parameter ERG (operating concern) is set or not. If the parameter is not present at the start of the session, the pop-up appears in the first KE21 transaction, but not in the second.

Solution
A new transaction KEBI has been implemented which must be executed as the first transaction of a batch input session for KE21 or KE11. The transaction sets the operating concern at the start of the session independent of the user. The new transaction will be delivered as a correction to 2.1J/2.2D/3.0.
In the meantime, you can install transaction KEBI into the system by carrying out the following steps:
- Call transaction SE93, enter transaction code "KEBI",
Choose the function "CREATE", select "Report transaction"
in the pop-up and the function "PROCEED", in the next
pop-up enter the transaction text "Set operating concern
(batch input)" and program "RKEERKRS", (no check object),
then choose the function "SAVE". A corresponding repair
must be created so that this can be saved; 'Confirm' this
after completing the correction so as not to prevent
transports for a later maintenance level.
- Call transaction SE38 and supplement program RKEERKRS as follows:

REPORT RKEERKRS MESSAGE-ID KE.

DATA: ERKRS LIKE TKEB-ERKRS.

CASE SY-TCODE.
WHEN 'KEBC'.
CALL FUNCTION 'RKE_CHANGE_ERKRS'
EXPORTING FCODE = 'AE'
I_ERKRS = ERKRS.
WHEN 'KEBA'.
CALL FUNCTION 'RKE_CHANGE_ERKRS'
EXPORTING FCODE = 'AZ'
I_ERKRS = ERKRS.
WHEN 'KEBI'. "<==== New
CALL FUNCTION 'RKE_CHANGE_ERKRS' "<==== New
EXPORTING FCODE = 'EE' "<==== New
I_ERKRS = ERKRS. "<==== New
ENDCASE.

SAP Note 17274 - Update from modified SD documents

Symptom:

Updating SD sales and distribution documents in SIS, in cash management and forecast, in profitability analysis, to the profit center, to the project revenues, and so on, does not work.

Cause and prerequisites

The customer has included additional INTEGER fields in SD tables (LIPS, VBRP, and so on). This moves key terms.

Solution
Definitions which are used for accessing the SD tables must be adapted in reports LMCS1TOP, LMCS5TOP and LMCS6TOP.
Example: VBRP was modified: The following definition must be adapted in report LMCS6TOP:
...
DATA: BEGIN OF XMCVBRP_KEY,
SUPKZ LIKE RMCS1-SUPKZ,
* jetzt neu das Feld FUELL, n zwischen 1 und 7
FUELL(n) TYPE X VALUE 0, <----- must be inserted
MANDT LIKE VBRP-MANDT,
VBELN LIKE VBRP-VBELN,
END OF XMCVBRP_KEY.

The length of field FUELL must be found by debugging:
In routine MCINF_UPDATE_ALL in report LMCS6F10, you have to set a breakpoint when accessing internal table XMCVBRP with XMCVCBRP_KEY. On debugging, the length of n is given by the number of # characters in table XMCVBRP:
...
* VBRP Fakturaposition
MOVE XMCVBRK-SUPKZ TO XMCVBRP_KEY-SUPKZ.
MOVE XMCVBRK-MANDT TO XMCVBRP_KEY-MANDT.
MOVE XMCVBRK-VBELN TO XMCVBRP_KEY-VBELN.
READ TABLE XMCVBRP WITH KEY XMCVBRP_KEY BINARY SEARCH. <----
IF SY-SUBRC EQ 0.
...

SAP Note 17271 - Net posting: cash discount taken at invoice time

Symptom:

system deducts discounts, in spite of late payment

Cause and prerequisites

is designed this way - additional training and explanation needed

Solution
Net posting (document type ins net) means that discounts are taken at invoice time and are distributed according your configuration and posting decisions. It also means that you have reduced the value of your material or asset accordingly and that you consider this to be the correct final price. The payment program as well as any manual payment is going to follow this principle and is going to ALWAYS take the cash discount, now matter how late the payment occurs. If the late discount results in a necessary refund to your vendor for the late payment you have to make a new entry to reflect this charge. The next posting run will then issue a check for the discount refund. There is no automatic process for this and the payment program cannot be configured to refrain from paying the reduced amount in the first place. Please notice that this has the benefit for you that the integration works correctly.
****
a. The additional cash discount is an unexpected surcharge and can be shown as such. As it is a separate posting, you can choose to distribute or not to distribute back to the charged costcenter/asset etc., depending on what caused the late payment in the first place.
***

b. The price of material, service etc. does not get distorted by a isolated late payment.

If the general procedure in your company is such that late payments are frequent, net payment (that is the aticipation of a reduced cost) is not for you. Please use gross document types then. This means that one cost center will receive the credit for timely pay, but it will certainly save you from many manual refund postings.

SAP Note 17267 - SQL Error "ISAM-134: no more locks"

Symptom:

When you
create/process batch input sessions

or
perform a client import, export, copy, or delete

or
import/complete a language

the following message occurs:
Informix SQL error -134 "ISAM error: no more locks"

together with
Informix SQL error -240 (INF240) "Could not delete a row"

or
Informix SQL error -246 (INF246) "Could not do an indexed read to get the next row"

or
Informix SQL error -271 (INF271) "Could not insert new row into the table"

or
Informix SQL error -418 "NULL SQLDA descriptor or host variable list encountered"

or
Informix SQL error -603 (INF603) "Cannot close blob"

or
Informix SQL-Fehler -605 (INF605) "Cannot write blob"

in operations on any tables.

Additional key words

INF240 INF246 INF271 INF418 INF603 INF605 INF134 ISAM134
RSCLICOP RSCLIEXP RSLANGIM RSLANGCP R3TRLANZ

Cause and prerequisites

The number of database locks which can be held simultaneously in a database is limited. A lock request which exceeded this maximum value led to the termination of the relevant transaction.
Usually the DB transaction which terminated is also the one which requested the large number of locks. However, the termination of the DB transaction responsible generally causes a very lengthy rollback, during which the same symptoms can also occur in other transactions.

Solution

As soon as the rollback of the DB transaction responsible is complete, the DB locks held by it exclusively are freely available again. If the SAP transaction responsible is executed again, the same situation generally arises. This can be solved only by carrying out one of the following actions:

-
> begin work;
> lock table in exclusive mode;
> delete from

where ;
> commit work;
>

After this, the transaction which was terminated can be started again.

-
> alter table

lock mode (page);
>

After successfully executing the transaction which terminated previously, it is important that you cancel the change, because the higher granularity of locks is always accompanied by a deterioration in the serialization of transactions.

The change can be canceled as follows:

$ dbaccess -
> alter table

lock mode (row);
>
3. Splitting the critical DB transaction:

Because batch input sessions, for example, run within one DB transaction, the DB locks are not released (COMMITed) until its completion.
Therefore, if you use COMMITs more often in the batch input session, the locks will be released more quickly.

SAP Note 17263 - EDI/IDoc: processing 2.1 IDocs in Release 3.x

Symptom:

When the IDoc types
ORD_ID01
INV_ID01
DES_ID01
are used in Releases as of 3.0, syntax errors (status 26) occur in the following areas of outbound processing:
Purchasing:
Request for quotation (REQOTE / 840)
Purchase order (ORDERS / 850)
Order change (ORDCHG / 860)
Sales:
Delivery advice (DESADV / 856)
Invoice (INVOIC / 810)
If these messages are used for testing inbound processing via program "EDI: Switch control record" (transaction WE12), syntax errors (status 60) occur in the following inbound processing areas:
Sales:
Request for quotation (REQOTE / 840)
Order (ORDERS / 850)
Order change (ORDCHG / 860)
Purchasing:
Delivery advice (DESADV / 856)
Invoice (INVOIC / 810)
Accounting:
Invoice (INVOIC / 810)

Cause and prerequisites

Starting in Release 3.0, a syntax check is performed of all IDoc types at segment level, against syntax table "EDISYN".
In the above messages/IDoc typea, the syntax check detects a variance from the syntax table. This variance cannot be corrected, however, as the EDI subsystems in Release 2.1 and 2.2 use it.

Solution

You can ignore the syntax errors for the messages / IDoc types listed above. You can also deactivate the syntax check in the partner agreement for the EDI interface:

in table "Outbound parameters" for outbound processing

in table "Inbound parameters" for inbound processing.

The errors will continue to be logged, but the documents will be processed despite the syntax errors (status 25 for outbound and status 61 for inbound).
You can configure the number of logged errors via the "IDoc administration" table, parameter "MAXSYNERR".

Additional key words

EDI, EDIFACT, IDoc type, IDoc

SAP Note 17259 - Error message sap_dext called with msgnr 900

Symptom:

Keyword: client copy, DSYOL, DSYO1, DBRCLU2, OLF

The following error is recorded in SLOG during client transport with RSCLIEXP/RSCLIIMP:

DBI LOG (BZ3): invalid return code OLF received [FILE dbrclu2, LINE 4567]
DBI LOG (BZE): invalid sql error 0 [FILE dblink, LINE 400]
SQL LOG (BY2): sql error 0 occured while performing COM [FILE dblink, LINE 400]
unknown error message 0 [FILE dblink, LINE 400]
2EETW150 sap_dext called with msgnr "900"
This problem can also occur in a language transport.
Error message: inf100 "duplicate value for a table with unique key"
Table affected: DSYxx (logical cluster table).

Additional key words
Cause and prerequisites

Problem with timestamps from old cluster tables (type 1)

Solution
Please call the following commands with "dbaccess" as user "informix" in both the source and target system:

1. select count(*) from dsyo1 where (timestmp not like '19%'
and timestmp not like '0%') or timestmp is null
2. select count(*) from dsyo2 where (timestmp not like '19%'
and timestmp not like '0%') or timestmp is null

If a value other than 0 is displayed, call the following statement for the involved tables (DSY01 and/or DSY02) on the appropriate system(s):

3. update dsyo1 set timestmp = '19920000000000'
where (timestmp not like '19%' and timestmp not like '0%')
or timestmp is null

This statement can also be used for table DSYO2.

When you call the select statments from steps 1 and 2 again, no records should be found.

SAP Note 17256 - Job log message "Exec format error"

Symptom:

When you execute an external program within a job, the job terminates. The job log contains the message:
'Ext. Prog.: Exec format error'

Cause and prerequisites

The program for execution is an interpreter file (e.g. a shell script) which does not have an interpreter ID.

Solution
Correct the interpreter file.
According to man-page of the exec() command, an interpreter file must be defined as follows:
An interpreter file is a text file that begins with the line
#! pathname [arg]
Typical example: #! /bin/sh
This line must(!) be contained at the very start of the interpreter file, otherwise the operating system cannot tell how to interpret the file.
Other examples:
#! /bin/csh
#! /bin/awk -f

SAP Note 17246 - MF40 Run schedule cannot be processed

Symptom:

In repetitive manufacturing, when backflushing to cost collector, the message M7162 appears.
Run schedule X cannot be processed

Cause and prerequisites

In Table T158, for TCodes MF40, MF41 and MF45, WR is entered instead of WS in field TETy (transaction/event type).

Solution
In Table T158, enter WS in the field TETy for transaction codes MF40, MF41 and MF45.

Additional key words

Run schedule header

SAP Note 17242 - ME51 ME57 ME21, performance problems under INFORMIX

Symptom:

The Purchasing transactions take unusually long. For example, several
minutes are required for source determination.

Cause and prerequisites

Select statements are not suitable for the Informix Optimizer.

Solution
Make the following changes in the program LMEQRF03 in the routines 'VERTRAEGE' and 'VERTRAEGE_OHNE_MATERIAL':

*eject
*----------------------------------------------------------------------*
* Suchen Rahmenverträge
*----------------------------------------------------------------------*
FORM VERTRAEGE.

...
...
IF COMIM-MATNR NE SPACE.
IF COMIM-WERKS NE SPACE.
* SELECT * FROM EKPO WHERE ( MATNR EQ COMIM-MATNR AND "<-- old
* WERKS EQ COMIM-WERKS AND "<-- old
* BSTYP EQ BSTYP-LFPL AND "<-- old
* LOEKZ EQ SPACE AND "<-- old
* ELIKZ EQ SPACE ) OR "<-- old
* ( MATNR EQ COMIM-MATNR AND "<-- old
* WERKS EQ COMIM-WERKS AND "<-- old
* BSTYP EQ BSTYP-KONT AND "<-- old
* LOEKZ EQ SPACE AND "<-- old
* ELIKZ EQ SPACE ) OR "<-- old
* ( MATNR EQ COMIM-MATNR AND "<-- old
* WERKS EQ SPACE AND "<-- old
* BSTYP EQ BSTYP-KONT AND "<-- old
* LOEKZ EQ SPACE AND "<-- old
* ELIKZ EQ SPACE ). "<-- old

SELECT * FROM EKPO CLIENT SPECIFIED "<- new
WHERE ( MANDT EQ SY-MANDT AND "Liefe"<- new
MATNR EQ COMIM-MATNR AND "<- new
WERKS EQ COMIM-WERKS AND "<- new
BSTYP EQ BSTYP-LFPL AND "<- new
LOEKZ EQ SPACE AND "<- new
ELIKZ EQ SPACE ) OR "<- new
( MANDT EQ SY-MANDT AND "Kontr"<- new
MATNR EQ COMIM-MATNR AND "<- new
WERKS EQ COMIM-WERKS AND "<- new
BSTYP EQ BSTYP-KONT AND "<- new
LOEKZ EQ SPACE AND "<- new
ELIKZ EQ SPACE ) OR "<- new
( MANDT EQ SY-MANDT AND "Zentr"<- new
MATNR EQ COMIM-MATNR AND "<- new
WERKS EQ SPACE AND "<- new
BSTYP EQ BSTYP-KONT AND "<- new
LOEKZ EQ SPACE AND "<- new
ELIKZ EQ SPACE ). "<- new

...
...
IF COMIM-MATKL NE SPACE AND COMIM-MATNR EQ SPACE.
IF COMIM-WERKS NE SPACE.
SELECT * FROM EKPO "<-- old
WHERE ( MATNR EQ SPACE AND "<-- old
MATKL EQ COMIM-MATKL AND "<-- old
WERKS EQ COMIM-WERKS AND "<-- old
BSTYP EQ BSTYP-LFPL AND "<-- old
LOEKZ EQ SPACE AND "<-- old
ELIKZ EQ SPACE ) OR "<-- old
( MATNR EQ SPACE AND "<-- old
MATKL EQ COMIM-MATKL AND "<-- old
WERKS EQ COMIM-WERKS AND "<-- old
BSTYP EQ BSTYP-KONT AND "<-- old
LOEKZ EQ SPACE AND "<-- old
ELIKZ EQ SPACE ) OR "<-- old
( MATNR EQ SPACE AND "<-- old
MATKL EQ COMIM-MATKL AND "<-- old
WERKS EQ SPACE AND "<-- old
BSTYP EQ BSTYP-KONT AND "<-- old
LOEKZ EQ SPACE AND "<-- old
ELIKZ EQ SPACE ). "<-- old
SELECT * FROM EKPO CLIENT SPECIFIED "<-- new
WHERE ( MANDT EQ SY-MANDT AND "Lieferpläne "<-- new
MATNR EQ SPACE AND "<-- new
MATKL EQ COMIM-MATKL AND "<-- new
WERKS EQ COMIM-WERKS AND "<-- new
BSTYP EQ BSTYP-LFPL AND "<-- new
LOEKZ EQ SPACE AND "<-- new
ELIKZ EQ SPACE ) OR "<-- new
( MANDT EQ SY-MANDT AND "Werkskontrak"<-- new
MATNR EQ SPACE AND "<-- new
MATKL EQ COMIM-MATKL AND "<-- new
WERKS EQ COMIM-WERKS AND "<-- new
BSTYP EQ BSTYP-KONT AND "<-- new
LOEKZ EQ SPACE AND "<-- new
ELIKZ EQ SPACE ) OR "<-- new
( MANDT EQ SY-MANDT AND "Zentralkontra"<-- new
MATNR EQ SPACE AND "<-- new
MATKL EQ COMIM-MATKL AND "<-- new
WERKS EQ SPACE AND "<-- new
BSTYP EQ BSTYP-KONT AND "<-- new
LOEKZ EQ SPACE AND "<-- new
ELIKZ EQ SPACE ). "<-- new

*eject
*---------------------------------------------------------------------
* Suchen Rahmenverträge ohne Material für Material
*---------------------------------------------------------------------
FORM VERTRAEGE_OHNE_MATERIAL.

...
...
IF COMIM-MATKL NE SPACE AND
COMIM-MATNR NE SPACE.
IF COMIM-WERKS NE SPACE.
SELECT * FROM EKPO "<-- old
WHERE ( MATNR EQ SPACE AND "<-- old
MATKL EQ COMIM-MATKL AND "<-- old
WERKS EQ COMIM-WERKS AND "<-- old
BSTYP EQ BSTYP-LFPL AND "<-- old
LOEKZ EQ SPACE AND "<-- old
ELIKZ EQ SPACE ) OR "<-- old
( MATNR EQ SPACE AND "<-- old
MATKL EQ COMIM-MATKL AND "<-- old
WERKS EQ COMIM-WERKS AND "<-- old
BSTYP EQ BSTYP-KONT AND "<-- old
LOEKZ EQ SPACE AND "<-- old
ELIKZ EQ SPACE ) OR "<-- old
( MATNR EQ SPACE AND "<-- old
MATKL EQ COMIM-MATKL AND "<-- old
WERKS EQ SPACE AND "<-- old
BSTYP EQ BSTYP-KONT AND "<-- old
LOEKZ EQ SPACE AND "<-- old
ELIKZ EQ SPACE ). "<-- old
SELECT * FROM EKPO CLIENT SPECIFIED "<-- new
WHERE ( MANDT EQ SY-MANDT AND "Liefer "<-- new
MATNR EQ SPACE AND "<-- new
MATKL EQ COMIM-MATKL AND "<-- new
WERKS EQ COMIM-WERKS AND "<-- new
BSTYP EQ BSTYP-LFPL AND "<-- new
LOEKZ EQ SPACE AND "<-- new
ELIKZ EQ SPACE ) OR "<-- new
( MANDT EQ SY-MANDT AND "Werks "<-- new
MATNR EQ SPACE AND "<-- new
MATKL EQ COMIM-MATKL AND "<-- new
WERKS EQ COMIM-WERKS AND "<-- new
BSTYP EQ BSTYP-KONT AND "<-- new
LOEKZ EQ SPACE AND "<-- new
ELIKZ EQ SPACE ) OR "<-- new
( MANDT EQ SY-MANDT AND "Zentra "<-- new
MATNR EQ SPACE AND "<-- new
MATKL EQ COMIM-MATKL AND "<-- new
WERKS EQ SPACE AND "<-- new
BSTYP EQ BSTYP-KONT AND "<-- new
LOEKZ EQ SPACE AND "<-- new
ELIKZ EQ SPACE ). "<-- new

SAP Note 17232 - Req. consumption, req. reduction, planning material

Symptom:

The conversion factor specified in the material master does not seem to be included in the consumption result during the requirements consumption (availability check, requirements reduction, display consumption) of the planning material.

Cause and prerequisites

The conversion factor for the planning material is recorded when the sales order is being entered. Later changes to the conversion factor in the material master are not considered for this sales order.

Solution
*

SAP Note 17222 - Termination during bulk processing of work centers

Symptom:

Termination during bulk processing (batch) of work centers.

Additional key words
Cause and prerequisites

Insufficient buffering of the work centers in internal table LRU_ARBID and error in the maintenance software of this table.
(Form LRU_ARBID_REMOVE)

Solution
Make the following program changes with transaction SE38.

1)LCR01TOP

*---------------------------------------------------------------------*
* Konstanten
*---------------------------------------------------------------------*
DATA:
................
ENT_ARBID LIKE SY-TABIX VALUE 1000, <-- change to 1000
................

2)Form LRU_ARBID_REMOVE (in program LCR01F00).

*---------------------------------------------------------------------*
* FORM LRU_ARBID_REMOVE
*---------------------------------------------------------------------*
* --> UP_OBJID
*---------------------------------------------------------------------*
FORM LRU_ARBID_REMOVE.

EXIT."bis auf weiteres stillgelegt <--- insert

DESCRIBE TABLE XCRHD LINES SY-TFILL.
WHILE SY-TFILL >= ENT_ARBID.
READ TABLE LRU_ARBID INDEX SY-TFILL.
..........................
..........................

SAP Note 17212 - SPADBA: Termination during reorg. leads to missing ind.

Symptom:

Indices are missing from certain tablespaces that were previously reorganized.

Cause and prerequisites

Oracle error complicated by a user error:
ORACLE error ORA-00902 may occur during the import step, particularly when the export was to tape (tape read error). SAP DBA detects the error and reports it. If the user terminates the operation, then the information (indices, grants) on the subsequent scripts is, of course, missing. If you then start R/3, the danger of duplicate records then exists (ORA-1452 when creating the indices).

Solution
Depending on the ORACLE error that occurred, you may have to modify the restart script, as when the import fails, SAPDBA automatically sets the restart plan: $ORACLE_HOME/sapreorg//restart.* such that it starts at deletion of the object.
If you can ignore the ORACLE error, modify the restart plan in such a way that it starts with creating the indices: all scripts before ind*.sql must be set to "Y".

SAP Note 17194 - Telefax in various SAP Releases

Symptom:

How can faxes be sent from and received in SAP systems?
Which SAP components are required, and what are the hardware and software requirements?
What documentation is available about installation, configuration and administration?

Other terms

SAPcomm, ComServer, SAPLPD, SAPFAX.DLL, WinFax PRO, SAPconnect

Reason and Prerequisites

There is an information deficit.

Solution

Currently, you can connect a fax to an SAP system in the following ways:

Lower throughput

Status tracking only possible locally on the PC, no confirmation in the SAP system

Faxes are not received

Instead of WinFax, you can also use fax systems created by other manufacturers if these meet one of the following requirements:

They are WinFax DDE compatible

The manufacturer offers a seperate SAPFAX.DLL

The fax number can be transferred in the message text
Note 44062 describes exactly how to proceed in such cases.

The SAPcomm and SAPLPD+SAPFAX solutions are still supported in SAP releases 3.1 and 4.0/4.5/4.6. For each of the communication services fax, X.400 and RML (SAP-to-SAP mail), you can use either SAPconnect or SAPcomm (or for fax, ComServer and SAPLPD+SAPFAX).

5.1.11

SAP Note 17171 - Execute report group: error GR205

Symptom:

A report group is executed. Selection terminates with error message GR205:
Internal error: entry in COLUMNS does not exist (MERGE-RC)

Cause and prerequisites

Program error

Solution
The error has not been localized yet, however, the following workaround is available:
If the report has a multi set in the column that contains a data set, please position the data set as the last item.

SAP Note 17161 - Foreign key from included tables

Symptom:

The following error messages referring to foreign keys from included tables occur during activation: W AD280 Frd. &-&: Check table & is not transitive re. value tables
E AD274 Frd. &-&: & and & refer to different domains

Cause and prerequisites

In earlier versions, foreign keys were included once and were then handled like the foreign keys of the including tables. This means that changes to the foreign keys of the included table did not affect the including table.
As of Release 3.0, you can determine in the including table whether changes to the foreign key of an included table should be inherited by the including table or not. The inheritance is switched on as a default.
However, for reasons of upward compatibility, all existing foreign keys must be considered as "not inherited".

Solution
The best thing is to check all foreign keys of the affected table to see whether they would be better as "inherited" foreign keys.
To do this, dissolve the sub-structure in the table maintenance where the check field is located. Then switch on the flag "Inherited from the included sub-structure" in foreign key maintenance. The foreign key of the sub-structure will then be copied immediately, and future changes to the included key will affect the including keys.
Important: the display of the check table has not been corrected yet. This only involves an error in the display, however. Once you save and call the sub-structure again, the display of the check table will be corrected.

SAP Note 17148 - Missing planning-/order long text after client copy

Symptom:

After a client copy of the routings or orders, you cannot call the long texts

Cause and prerequisites

Error in long text key

Solution
Start the following report in the new client and specify the source client as the only parameter:

Additional key words

text_problems long_text client_copy

SAP Note 17131 - MM02 Maintaining production version for a material

Symptom:

Error message M3659 is issued when you maintain the production version of a material.
'No management of aggregated fields for repetitive manufacturing'.

Cause and prerequisites

The entry for the respective client does not exist in table T437A.

Solution
Make the following entry in Customizing (transaction OSP1):

Tools --> Customizing --> Configuration --> Logistics --> Production --> Repet.manufacturing --> Settings --> General settings

Example :

Release 2.2*

PLine/plID PLine/plID Suppress Line text SelP. SelP.
1 0 1 1 10 60

Release 3.0*:
Aggregation fields Lines for extended material data
1 field: ProdLine/PlngID 1 Display demands x
2 field: ProdLine/PlngID 2 Display availability x
Display range of coverage x
Display other versions x
Selection period Display non-assigned qties x
For planning table 90
For coll. assignment 10 Planning table
View selection 3
Line text 2
Periods; plng figures statistics Sched. pld order 2
Start: current date+ 1 days ProductionDates
Finish:current date+ 7 days

Completion confirmation
Suppress planned order 1
Suppress run schedule header 1

Additional key words

MM01, MM02, material master, C201, C202, master recipe

SAP Note 17127 - SD/CO-PCA Processing of accruals

Symptom:

Conditions that are relevant for accruals are not transferred from SD to CO-PCA.

Cause and prerequisites

Incorrect setting of the customer in Customizing
Explanation:
2 G/L accounts are allocated for conditions that are relevant to accruals in SD. The 1st G/L account is for the (planned) sales deduction, the 2nd G/L account is for the accrual.
Example:
Billing item
Price 100 DEM
Condition, rel. to accruals 10 % - 10 DEM -
Net 100 DEM

Corresponding FI posting

Debit Credit
Customer 100
Revenues 100
1. G/L account 10
2. G/L accoun 10

The following rules apply to transferring from SD to CO-PCA:
- Only the 1st G/L account is taken into account.
- Only revenue accounts and sales deduction accounts are taken into account, that is, only accounts with cost element type 11 or 12. In particular, no balance sheet accounts are taken into account.

Solution
For conditions that are relevant to accruals which should be transferred to CO-PCA, the 1st G/L account must be a sales deduction account.

SAP Note 17123 - MF41 Backflushing cancelled; material shortfall GR

Symptom:

When cancelling backflush data in repetitive manufacturing MF41, the error message M7021 appears. Production order goods receipt quantity shortfall amounting to & &. Cancellation cannot be carried out.

Cause and prerequisites

In Table T437S, the valuation type 101 has been entered for the field Movement type goods receipt (T437S-BWAWE). Thus, the check of the GR quantity shortfall is carried out via the control of T156S.

Solution
In Table T437S, enter the movement type 131 for all profiles in field T437S-BWAWE.

Menu path for the change:
Tools -> Customizing -> Configuration -> Logistics -> production
-> Repetitive manufacturing -> Transactions -> With cost collector
-> Confirmation data

Additional key words

Run schedule header, goods receipt, cancellation

SAP Note 17112 - How do you recognize a quantitative characteristic

Symptom:

You want to see in a report whether a characteristic is qualitative or quantitative. How do you recognize this when using table QAMV ?

Solution
Include the following lines into your program:

TABLES QMKST.

....
MOVE QAMV-STEUERKZ TO QMKST.
IF QMKST-QUANTITAT IS INITIAL.
* qualitatives Merkmal
ELSE.
* quantitatives Merkmal
ENDIF.
IF QMKST-MESSWERTE IS INITIAL.
* qualitative Erfassung
ELSE.
* quantitative Erfassung
ENDIF.

SAP Note 17108 - Shared memory still present, startup fails

Symptom:

Shared memory segments remain during shutdown stopsap. Startup of the application serve fails.
Error messages appear in the dev_w... trace files:
ERROR .. ShmCreate ... shmget or shmat
ERROR .. ShmGet ...

Cause and prerequisites

Due to a program error or a crash of the application server, IPC objects (like shared memory segments and semaphores) remain and prevent a restart. The problem also appears when the application server crash takes longer than 20 seconds, e.g., because of a slow databank reaction during a rollover.

Solution
Quick fix: use program "cleanipc" to delete all the shared memories of an R/3 instance once that instance has been shut down.
Call: cleanipc remove
Example: cleanipc 00 remove ; for SAP System no. 00
Calling 'cleanipc' can be automated by adding the following
instruction in START_D....

Stop_Program_ =local cleanipc remove

Example:
#------------------------------------------------------------------
# cleanup ipc objects
#------------------------------------------------------------------
Stop_Program_01 =local sleep 10
Stop_Program_02 =local cleanipc 00 remove
CAUTION!!
'cleanipc' cannot be used while an instance is running because it
will cause the application server to crash.
Side effects:
"cleanipc" also deletes a shared memory segment "SCSA", which contains the current write pointer for the SysLog file. Therefore, during the next restart, a delay of several seconds will take place, and the system will issue the message:
"searching for overlap point in pre-existing syslog file"

SAP Note 17105 - DME Germany - control total with errors

Symptom:

The control total (total of account numbers - field 6 in data record E) does not correspond with the actual control total of the numbers.

Cause and prerequisites

One of the used account numbers has 11 figures. This value is shortened to 10 figures when the data record C is written, but is nevertheless completely considered for the calculation of the control total.
Therefore, the last 10 figures of the calculated and actual total do not correspond.

Solution
First determine the involved recipient of the bank transfer/party liable to pay and correct his bank details.
Determine the payment document number in question. You can create a data carrier for the remaining items by excluding this payment document number in the respective selection conditions when starting the payment medium report.
Settle the items of the incorrect bank details manually.

SAP Note 17100 - RM06BFE0 does not select by requisitioner

Symptom:

Report RM06BFE0 (release reminder for purchase requisitions) does not select by parameter "Requisitioner".

Cause and prerequisites

The corresponding query for the parameter is missing in the program.

Solution
See the correction numbers listed in this note.
Advance correction possible:

Program RM06BFE0, FORM BAN_AUFBAUEN:

*------- Check Select-Options ----------------------------
CHECK S_WERKS.
CHECK S_BSART.
CHECK EBAN-PSTYP IN R_PSTYP.
CHECK S_KNTTP.
CHECK S_LFDAT.
CHECK S_FRGDT.
CHECK S_DISPO.
IF P_AFNAM NE SPACE. <--- new
CHECK EBAN-AFNAM = P_AFNAM. <--- new
ENDIF. <--- nEW

SAP Note 17099 - IS-H: Explanation of priority specifications

Symptom:

Priority of a notified problem is too high or too low.

Cause and prerequisites

Incorrect determination of the priority.

Solution
Explanation of the individual priorities.

Priority 1: very high
(e.g. system shutdown)
Priority 2: high
(considerable losses in production,
missing, unexecutable functions)
Priority 3: medium
(defective individual functions)
Priority 4: low
(customer requests, lack of documentation,
help requests)

Unfortunately, we had to correct your proposed priority after basic analysis of your problem. Please have understanding for this procedure.

The correct categorization of a problem is of great importance for adequate, smooth processing. Please take this into account for all further priority specifications.

SAP Note 17097 - CALL_FUNCTION_CONFICT-LENGTH when creating orders

Symptom:

Key word: VA01, VF01 (Create billing document), KOMP, KOMK
When calling the function module 'PRICING_DIALOG_PAI', a runtime error occurs. The KOMP and KOMK fields do not have the correct length.

Additional key words

CALL_FUNCTION_CONFLICT_LENGTH CALL_FUNCTION_CONFLICT_LENG

Solution
Generate the following programs:
SAPLV61A SAPMV45A SAPLV60A
SAPMV61A SAPFV45P SAPMV60A
SAPLV61C SAPFV45K SAPLV14A

SAP Note 17094 - Main asset number text

Symptom:

Since Release 2.1 there has been a text for the main asset number. What is it used for? How is it used?
Keywords: ANLH, ANLHTXT, asset subnumber summary

Solution

If you structure your assets strongly using subnumbers (for example a large production machine or a building), you can assign a special text to the construct as a whole next to the individual description of each part (represented by a subnumber) with the text for the asset main number.
Do do this, you must create the corresponding field during master record maintenance.
As a result, all summaries (represented in the individual transactions by subnumber '*') immediately contain this text as in reporting (the request 'only main asset numbers').
If you do not want to use this option, you have the following
possibilities:

Deactivate screen group '07' in the screen layout rule for asset classes

Do not enter any different text for the text for the main asset number.

In both cases, the text of the first subnumber (normally '0000') is put into the text for the main asset number according to programming logic and shown as described above.

SAP Note 17088 - HR: RPCALCx0 in infinite loop for loans

Symptom:

Payroll accounting with RPCALCD0, RPCALCC0, RPCACLA0, RPCALCE0, and RPCALCX0 terminates with a TIME-OUT; employer loans were being calculated.
Using TOOLS->ADMINISTRATION to access MONITOR-SYSTEM MONITOR- PROCESS OVERVIEW, you will see that SAPLRPAI remains as the report in the process where the payroll is running, and does not change. If you switch to DEBUGGING, the report stops at the following coding:
DO
CORRDATE = CALCDATE.
CORRDATE = 1 + CORRDATE - 1.
IF CORRDATE EQ CALCDATE.
MERKDATE = CALCDATE.
EXIT.
ENDIF.
CALCDATE+6(2) = CALCDATE+6(2) - 1.
ENDDO.
Using GOTO->ACTIVE_CALLS, you will see that the program was selected from RPCERL00.

Cause and prerequisites

This effect occurs during loan calculations for a calendar year for which all periods have not yet been maintained in T549Q and the starting point for the repayment, interest, or annuity cycle is in a payroll period which has not yet been specified.
Example:
Interest cycle 03 03 with Period modifier 01 monthly (i.e., interest calculation at end of quarter), payroll for 01 1995 and no entries in T549Q for the periods 02, 03, ... 1995.

Solution
1st approach:
Generate the missing payroll periods for the calendar year in which the payroll is to be performed.
We will modify the payroll so that you no longer get an infinite loop. Rather, in this situation the personnel number will be rejected.

SAP Note 17083 - Adapting the sapsys groups in a system network

Symptom:

The transport system does not work properly. Various authorization problems occur during transport.
The sapsys group was not installed with the same group identification number on all the computers of the SAP R/3 system network.

Cause and prerequisites

The sapsys group was not installed with the same group identification number on all the computers of the SAP R/3 system network.
When an SAP R/3 System is installed, the sapsys group must always be created under the same group identification number (gid).

Solution
Contents

1. Checking the gids
2. Determining a master gid (Mgid)
3. Changing the assignment of gids to the master gid (Mgid)
4. Changing the gid of existing files
----------------------------------------------------------------------

1. Checking the gids

Log on to all the computers of your SAP R/3 system network, one after another, as user root and issue the following command:
grep sapsys /etc/group
This command will display the entry of group sapsys from the operating system file /etc/group. This entry will appear as follows (example):
sapsys:*:201:...................
The third field (separated by ":") contains the gid of the group.

We recommend recording all the gids in a three-column table: host name, gid, and mgid. In this step, the Mgid field is still empty.
When all the determined gids are the same, there is nothing else to do. The described problem does not have the cause assumed here, and this note is not relevant for solving your problem.
----------------------------------------------------------------------

2. Determining the Mgid

Now determine one gid as Mgid according to the following perspectives:
On all the computers of the SAP R/3 system network, the Mgid must either be set to the sapsys group or must still be available
(Help: command (as user root):
sort -t: -k 3n,3 /etc/group
Generates a list of file /etc/group sorted by the third column.)
For safety's sake, once you have decided on an Mgid, you should make sure that this gid can be used as Mgid. To do this, log on to all the hosts of your SAP R/3 system network as user root and issue the following command:
grep Mgid /etc/group
If the system does not issue any messages, or outputs "sapsys:*:Mgid:...." (or similar), that Mgid is fine.

Comment:

You have now determined a usable Mgid; enter it in the list you created in step 1.
Now, for every computer in the SAP R/3 system network where the gid and Mgid differ, perform the actions described in steps 3. and 4. below.
----------------------------------------------------------------------

3. Changing the assignment of gid to Mgid

Log on to the appropriate computer as user root. Edit the /etc/group file. In the file, change the gid of group sapsys to the Mgid.
Example: if the line
sapsys:*:203:....................
appears in the /etc/group file, 203 is the gid you determined for this computer in step 1, and 304 is the Mgid you selected, change the line to:
sapsys:*:304:...............
(The ".................." stands for the end of the line, which you should not alter.)

4. Changing the gid of existing files

At this point, all the R/3 systems in the system network must be stopped, as the files changes required cannot be performed when the system is running.
Log on to the appropriate computers as user root and enter the command that changes the group identification number for the following five directories (or mount points):
Directories:
/usr/sap/trans/
/usr/sap//
/sapmnt//
/usr/sap/tmp/
~adm/ (Home directory of adm)
Command to change the gid:
find

-print | xargs chgrp sapsys
or
find -exec chgrp sapsys {} \;
(The "\;" at the end of the line is particularly important.)
Replace by each of the five directories specified above.
-----------------------------------------------------------------------

Closing comment:
Once you have performed steps 3. and 4. of this note for all the computers in your SAP R/3 system network, we recommend making sure that all the gids of the sapsys group now agree by repeating the procedure described in step 1.
You can now restart your R/3 systems.

SAP Note 17081 - Determining billing date if SD installed without MM

Symptom:

The billing date is not determined from the goods issue date.
It is predetermined from the date of creation of the delivery note
(requested delivery date).
The error occurs only for materials that are not subject to inventory management (standard item type TAX) or if MM is not used.

Additional key words

VL01, VL02, VL19, goods issue, goods issue date, billing date,
actual goods issue date, LIKP-WADAT_IST, LIKP-WADAT, V134W, T134W,
LIKP-FKDAT.

Cause and prerequisites

For deliveries whose goods issue is not posted in MM because quantity and value update is inactive for the material in table T134W or V134W as of Release 3.0, the billing date is not set to the goods issue date.
The same applies for the actual goods issue date as of Release 3.0. This date is not transferred to the billing date if the value or quantity update is inactive.

Solution
Make the following corrections in INCLUDE FV50WF0W:

Caution!
The changes for Releases 2.1 and 2.2 differ from the change for
Release 3.00 - 3.0E.

As of Release 3.0, see also note 46892.

SAP Note 17069 - ME21 ME31 Referencing: "Function not defined/supported"

Symptom:

If you create a purchase order with reference to a requisition or
contract, or create a contract with reference to a reference document,
and use "Copy + detail" to go from the overview screeen (125/124/122)
to the detail screen, unf from there to the account assignment screen
(item must be assigned), and then press "Continue", the program returns
you to the overview screen with the error message "E: Function not
supported here".

Cause and prerequisites

Program error: Fields OK-CODE and SELFCODE are both still set to KN,
and this function code is not possible on the overview screen.

Solution
See the correction numbers in this Note.
The correction can be implemented in advance as follows:

Program MM06EFAB, FORM ABT_BLAETTERN:

CASE OK-CODE.
.
.
WHEN SPACE.
IF RM06E-EBELP NE 0.
EXIT.
ENDIF.
A-AKTIND = A-AKTIND - A-PAGIND + 1.
WHEN OTHERS. <--- new
IF SELFCODE EQ KNTI. <--- new
CLEAR OK-CODE. <--- new
CLEAR SELFCODE. <--- new
CLEAR DUNKEL. <--- new
A-AKTIND = 0. <--- new
ENDIF. <--- new
ENDCASE.

Program MM06EFBA, FORM BAT_BLAETTERN:

CASE OK-CODE.
.
.
.
WHEN SPACE.
B-AKTIND = B-AKTIND - B-PAGIND.
PERFORM BAT_BLEIBE.
WHEN OTHERS. <--- new
IF SELFCODE EQ KNTI. <--- new
CLEAR OK-CODE. <--- new
CLEAR SELFCODE. <--- new
B-AKTIND = 0. <--- new
ENDIF. <--- new
ENDCASE.

Program MM06EFRF, FORM RFT_BLAETTERN:

CASE OK-CODE.
.
.
.
WHEN SPACE.
IF RM06E-EBELP NE 0.
EXIT.
ENDIF.
R-AKTIND = R-AKTIND - R-PAGIND + 1.
WHEN OTHERS. <--- new
IF SELFCODE EQ KNTI. <--- new
CLEAR OK-CODE. <--- new
CLEAR SELFCODE. <--- new
CLEAR DUNKEL. <--- new
R-AKTIND = 0. <--- new
ENDIF. <--- new
ENDCASE.

SAP Note 17058 - Arbeitgeber in int. Tab. AGDATA nicht gefunden

Symptom:

Fehlermeldung des Reports RPCL16A2.

Weitere Begriffe
Ursache und Voraussetzungen

Bei der Erstellung des Datenträgers (Lohnzettel L16) müssen im Info-Satz nähere Angaben zum Arbeitgeber (Nummer, Anschrift etc.) gemacht werden.

Die entsprechenden Daten wurden von Ihnen noch nicht gepflegt.

Lösung
Entsprechende Daten im dafür vorgesehenen Kunden-Member pflegen.

Eine ausführliche Erläuterung finden Sie in der Dokumentation des Reports RPCL16A2.

Nachdem die Daten gepflegt wurden, muß der Report RPCL16A2 neu generiert werden.

SAP Note 17054 - How to copy or change a device type

Symptom:

Problems with copying a device type

Cause and prerequisites

Various

Solution
Copying a device type:

Call transaction SPAD (spool administration). The initial screen contains a menu path "Utilities -> Copy device type". (As of Release 4.0A: "Utilities -> For dev. types -> Copy device type").
IMPORTANT: Do NOT use the "Create with template" menu item under Device types. This will only create a blank device type.
Select the "Utilities -> Copy device type" item and, in the subsequent dialog box enter the existing device type name as the first parameter and the new name as the second. The new name should not exist yet.
You must use a name from the customer name range: the name must begin with "Z". Otherwise your new device type could be overwritten by an SAP device type during the next upgrade. The device type name should only consist of UPPER CASE LETTERS and should not contain any special characters since otherwise, problems could occur, for example, when this new device type is used as a reference in a printer initialization.

Once you have entered the names, press "Proceed" to start copying. The system should now ask you whether you want to create the new device type. If a different message appears, this means that the device type name probably already exists. Make sure you really want to overwrite the existing device type; if not, select another name.
Please also remember to change the device type used for output devices that have already been defined.

Changing a customer device type

You can change the formatting, the print control replacement, and the printer character set from within the spool administration transaction.

Modifying a format type

You can now modify the device type you just created. Call transaction SPAD and select menu item "Formatting for device type". In the subsequent screen, enter the name of your device type (starting with Z...) and the formatting you want to change. Formats that start with A-W are used by SAPscript. Formats starting with X are used for list output. Customer-defined formats should begin with Z. For more details, please refer to the online documentation.
As of Release 4.0A, you select your new device type in change mode and then choose formats or print controls.
The online documentation also describes how to change the print controls and the character sets.
Refer to Note 17895 for instrucstions on how to create new format
types.

Changing an SAP device type
Don't! Even if you "only" want to add your own formats, you should always make a copy of the SAP device type and modify the copy.
THESE CHANGES DISAPPEAR AFTER AN UPGRADE.

SAP Note 17046 - Delivery list - cut off information

Symptom:

In the 'Deliveries list' application, places on the display are cut off for the display variants 'Deliveries of the partner' or 'Delivery items of the partner' for the delivery date field.

Cause and prerequisites

Headings are not set up in columns.

Solution
1. Set up the headings correctly via the Customizing transaction.
2. If they are standard display variants, you can help things by maintaining table T180U.
a) Determine the underlying program via the status display.
b) Transaction SM31 and maintain table T180U.
c) Set up heading(s) in question.
d) Run report RV76A001 for the underlying program.

SAP Note 17043 - Creating authorization object is not possible

Symptom:

When trying to create an authorization object using transactions KE17, KE37, KCR7, you get message KH705 with the text (2.1, 2.2):
The authorization object does not exist (please choose another).
In 3.0, the error message has the text: Authorization object is being used by another application or client.

Cause and prerequisites

The authorization object does exist, but it cannot be changed here because it is already being used in another application, or it was created in the current application for a different client.
Possible applications are: CO-PA Planning, CO-PA Reporting, CO-BPC Reporting.

Solution
You can access an overview of the use of authorization objects per application by displaying table TKEB3 using transaction SE16.
The entries are divided according to application class and subclass.
Application class KE: Objects for CO-PA, Subclass 01 - reporting, 02 - planning.
Application class KC: Objects for CO-BPC.
In addition, all applications are divided according to table name. In this case, in application class KE the table name in the last 4 characters corresponds to the operating concern, and in KC the last 3 characters correspond to the aspect.
You can use the authorization object in a different client for the authorization check if you transport the corresponding entry from table TKEB3 into the other client.

SAP Note 17041 - Availability check is not performed

Symptom:

The full quantity of a material is confirmed on the requested delivery date, although the ATP quantity is zero and the availability check is active.

Solution
Please check whether the replenishment time is checked. (Transaction OVZ9)

If so, one of the following times must be maintained in the material master record:

o Goods receipt processing time (purchasing view)
o Planned delivery time (MRP view 1)
o Goods receipt processing time (MRP view 2)

SAP Note 17039 - Head.net value contains prop. amounts from TANN item

Symptom:

The net value of the customer order on header level contains proportionately the amount of an item with item category TANN.

Cause and prerequisites

Incorrect system settings.

Solution
Set "Statistical value" for item category TANN

or

set the condition (2) "Item with pricing" in the pricing procedure used.

SAP Note 17037 - 06255: Please maintain period indicator for language X

Symptom:

When creating a purchase order document, error message 06255 is displayed: 'Please maintain period indicator for language &'.

Cause and prerequisites

Table TPRG is not maintained in this language.

Solution
Add the following data records with SM31 in table TPRG:
Language Dlv. date Date type DateTypeDescrip Printout
E D 1 Format for day
E M 3 Format for month Month
E P 4 Period format
E T 1 Format for day
E W 2 Format for week Week
This example applies to the English language.

SAP Note 17035 - ORACLE and SQL*NET V2

Symptom:

When will SQL*NET V2 be supported?

Cause and prerequisites

See above.

Solution
ORACLE 7.1.4 will be delivered from Release 2.2 D+.

From this Release, SQL *NET V2 will be installed and can be used under
the following restrictions:

1. NET*V2 cannot yet be used for SAP R/3

2. The customer is responsible for configuring the necessary files
(tnsnames.ora, ...).

SQL *NET V2 will probably be available with SAP R/3 as of Release 3.0D (7.2.x). The customer will be supplied with the relevant templates.

General support from Oracle for NET*V1 will stop when 7.3 is released.
This does not necessarily mean that the old products will automatically
be banned, but bugs will no longer be fixed.

NO SAP CUSTOMER WILL HAVE SUPPORT PROBLEMS USING THE HOTLINE IN
WALLDORF.

We will log all the necessary steps and notes in the Notes and Guidlines

SAP Note 17034 - No. of purchase orders in Purch. Info. Sys. = 0

Symptom:

The number of purchase orders equals zero in the purchasing group analysis of the Purchasing Information System. The same applies, for example, to the number of requests for quotation and all other counters that are determined per document(header).

Cause and prerequisites

Incorrect customizing of the document type. Particularly relevant for new customer-defined document types.

Solution
In customizing of the document types for purchasing, field "UpdateGroup" must be filled. For the counters per document (header) to be updated in purchasing standard information structure S011, "SAP" must be entered. If nothing is entered, the counters per document (header) will not be updated.

SAP Note 17033 - Create RfQ: error 06130 New document language...

Symptom:

When you create a request for quotation (transaction ME41), the error:
06130: New document language (please translate texts as required) is issued.

Cause and prerequisites

The language key of the request for quotation is different than that of the vendor.

Solution
Change the language key in the vendor master record (view "Address). You can also ignore error message 06130 when creating the request for quotation. The message only refers to the fact that texts that are copied from the master record are in a different language than the request for quotation. These texts should be translated in the request for quotation when necessary.

SAP Note 17031 - ME21 w. ref. to pur. req.; pur. req. remains open

Symptom:

A purchase order is created with a reference to a purchase requisition. If you then branch to the schedule screen and distribute the quantity among several dates, the ordered quantity in the purchase requisition is only reduced by the amount from the first schedule line.

Cause and prerequisites

Handling error

Solution
If you want to distribute the quantity among several dates, and the reference to the purchase requisition should apply to all the dates, select function "Purchase order -> Create with ref. -> To pur. req." on the schedule screen. Otherwise, the reference to the purchase requisition will not be retained, and the open quantity of the purchase requisition will not be reduced like you want.
This, however, is not possible with purchase requisitions that were generated from a sales and distribution document. You can only copy those purchase requisitions into one single schedule line.

Additional key words

ME21, ME22, scheduled quantity, subset, purchase requisition,
purchase requisition reference

SAP Note 17021 - Aspect has not yet been generated

Symptom:

KH507 Termination in SAPMKES1; Error when reading database structure 00000
KX760 Data transfer program has not been generated MSTT242S

Cause and prerequisites

The aspect has not yet been generated

Solution
The aspect must first be generated before you can use it. This can be done using transaction KCA0; on screen 2000 you have to call the function 'Structure --> Generate'.

SAP Note 17009 - Conditions: Sales deal and promotion are not reset

Symptom:

Sales deal and promotion were transferred from copied record in transaction 'Create with reference'.

Cause and prerequisites

Missing code.

Solution
In MV13AF0K

FORM KONH_SELECT.
.
.
LOOP AT KONH_TMP.
XKONH = KONH_TMP.
* Anlegen mit Vorlage ?
IF ORIGINAL_AKTYP = AKTYP-MODEL.
....
* Promotion und Verkaufsaktion
CLEAR XKONH-KNUMA_PI.
CLEAR XKONH-KNUMA_AG.
...
ENDIF.
APPEND XKONH.
ENDLOOP.

FORM KONP_SELECT.
.
.
LOOP AT KONP_TMP.
MOVE-CORRESPONDING KONP_TMP TO XKONP.
* Anlegen mit Vorlage ?
IF ORIGINAL_AKTYP = AKTYP-MODEL.
* Promotion und Verkaufsaktion
CLEAR XKONP-KNUMA_PI.
CLEAR XKONP-KNUMA_AG.
ENDIF.
APPEND XKONP.
ENDLOOP.
ENDFORM.

SAP Note 17006 - Copying: Wrong material short text

Symptom:

You create a returns document or a credit memo or debit memo with reference to a billing document (copying).
All items of the existing document contain an identical material short text, which is the short text of the last invoice item.

Cause and prerequisites

Wrong Customizing

Solution
In Customizing SALES - TRANSACTIONS - DOCUMENT FLOW - FOR SALES ACTIVITIES, an entry with the key 'Target sales document type' - 'Billing type' - 'Item category' (for example, G2 - F2 - TAN) exists.
On the detail screen a number for the control of the data transfer for the item (key word 'VBAP') exists. The error occurs, if the number 151 is found there. The number 153 should be there. Please correct the table entry and check the other numbers for the control of the data transfer of the table entry (VBKD = 104, VBPA = 004).

3.1.11

SAP Note 169936 - ISM:Transaction JD81 terminates with MESSAGE_TYPE_X

Symptom:

If you try to display the 'Created by' data in Transaction JD81 without having selected an entry before, then runtime error MESSAGE_TYPE_X occurs.

Cause and prerequisites

The problem is caused by a program error in the source code of report MJD05F10.

Solution
The error is corrected with add-on patch 4.02/2. You can make the attached advance corrections.

Additional key words

JD81, MESSAGE_TYPE_X

SAP Note 16991 - RM07MMBL: New batches with split valuation

Symptom:

Inwards goods movements for new batches for a material with split valuation could not be performed with batch input for goods movements (RM07MMBL). You cannot enter the original goods receipt date, either, especially for initial entry of stock balances.

Cause and prerequisites

The involved fields "Valuation type" and "Goods receipt date" are not supported in the screens and interface structure BMSEG.

Solution
Please use the material master record menu to define the batch, maintaining fields "Movement type" and "Goods receipt date" before you process the involved batch input sessions.

SAP Note 16983 - RSTG chain destroyed

Symptom:

You receive an error message telling you that the RSTG chain is destroyed.
The developer traces contain extracts that indicate that memory has been overwritten.

Other terms

rstg_

Reason and Prerequisites

Due to an error in the application server, memory is overwritten in the
memory chains.

Solution
If you can reproduce the memory overwriter, you may be able to
determine what triggered the error by activating the memory monitoring within the ABAP Debugger.

Kernel extensions: Trace ouputs and further memory checks

As of kernel patch level 2037, the system outputs the contents of the affected memory area in the trace file of the work process for 46D kernels. You may be able to determine the cause of the error from the data content.

Check of PERM and TASK memory areas as of the following patch levels:
46D 2137
640 95
700 29

The new checks resulted in terminations (core dumps) and trace outputs:
PERM block defect
id ROLEPT addr ... len ...
or
id SHORT addr ... len ...,

This problem in the check function is solved in the following patch levels:
46D 2156
640 100
700 32

Trace output of the first 500 bytes of a deficient PERM memory block
46D 2286
640 150

SAP Note 16968 - ME49: All one-time customers have the same name

Symptom:

Transaction ME49 (Price Comparison List): If you choose "Additional info: quotations", go back and choose again "Additional info: quotations", the same name is allocated to all one-time customers.

Cause and prerequisites

Program error.

Solution
See the correction numbers listed below. Advance correction possible; you only need to change one line:
Program FM06IFPS, FORM KOPF_INFO_PS:

IF LFA1-XCPDK NE SPACE.
*--- CPD-Lieferant --> Name aus Beleg holen ----------------
PERFORM EKAN_DAZULESEN USING XEKKO-EBELN.
LFA1-NAME1 = XEKAN-NAME1. <--- modified
ENDIF.

SAP Note 16966 - Update termination in MCV_STATISTICS_UPD modules

Symptom:

When you create or change a document (VA01, VA02, VL01, VL04, VL02, VF01, VF04, VF02 etc.) update terminations occur in the ABAP processor: DBIF_RSQL_SQL_ERROR

in function modules

MCV_STATISTICS_UPD_V1_ORDER or MCV_STATISATICS_UPD_V2_ORDER or

MCV_STATISTICS_UPD_V1_DELIVER or MCV_STATISATICS_UPD_V2_DELIVER or

MCV_STATISTICS_UPD_V1_INVOICE or MCV_STATISATICS_UPD_V2_INVOICE.

A table from one of the following information structures is involved: S001 through S006 or S500 through S999.

Cause and prerequisites

DB parameters NextExt and MaxExt of the table are not sufficient.

Solution
Change the DB parameters of the involved table:
Increase NextExt by a factor of 10 and increase MaxExt to < 500. For detailed information on the procedure, please refer to the "Data Dictionary manual".

SAP Note 16958 - Conditional output of NEXTPAGE in SAPscript

Symptom:

The SAPscript system symbol NEXTPAGE also contains a value on the last page of output.

Cause and prerequisites

The end of the text is not recognized until the last character in the main window is output. The symbol value, however, has already been replaced at that point.

Solution

You can suppress the output of NEXTPAGE only in type VAR windows, as these process the end-of-page after the main text.
This can be achieved in the following manner:

Release prior to 3.0:

As of Release 3.0

On the last output page in all windows that are not type MAIN, the variable &NEXTPAGE& has the value of 0. For example, the following constructs will not be printed. On all other pages the variable NEXTPAGE has a value other than 0. The text "following page" and the variable will, therefore, be printed.

Examples:
&NEXTPAGE(I)&

&'following page: 'NEXTPAGE&

IF &NEXTPAGE& <> '0'
Following page: &NEXTPAGE&
ENDIF

Additional key words

Form, SAPscript, se71, nextpage, command

SAP Note 16922 - Invoice verification: reversal, ext. no. assignment

Symptom:

Key word: MR08
Reversing invoices: if the reversal document type for the invoice document type has external number assignment, the action is prevented from Release 2.2 onwards with error message F5092 "Document type ... must have internal number assignment for reversal" or M8365 "Document cannot be reversed". Up to Release 2.1, a screen was displayed in this situation that enabled entry of an external document number for the reversal document.

Cause and prerequisites

Not an error. It should no longer be possible to perform reversals using document types with external number assignment. This activity was erroneously allowed until Release 2.1, and was corrected in Release 2.2.

Solution
You must make sure that a reversal document type is specified with internal number assignment for every relevant document type.
In Customizing for invoice verification, the reversal document type is found under Activities -> Incoming invoice -> Document number/number range, sub-item Document type. The detail screen for the document type contains the field "Reversal document type" in the "Properties" group.
To enable reversal using document types with external number assignment in invoice verification, you can make the following modifications.
Change program LMRBIU01; insert the lines marked with "INSERT below:
...
SELECT SINGLE * FROM TCURM.

IF SY-TCODE = 'MR08'. "INSERT
MODUS = 'E'. "INSERT
ENDIF. "INSERT

CLEAR: BDCTAB,
...

SAP Note 16915 - Error binding Oracle: can't find -lm

Symptom:

Error binding Oracle, can't find -lm.

Cause and prerequisites

Software developer kit OSFPGMRnnn not installed.

Solution
OSF/1 can be installed without the SDK. The compiler and linker are still present in this case, but only the libc.a is installed. The library is contained in packet "OSFPGMR2??". As far as we know, the packet is contained in the pre-requirement guidelines. It is contained on the OSF/1 installation CD and has to be installed using the command "setld -l directory SUBSETNAME"

Example:
root> setld -l /mnt/ALPHA/BASE OSFPGMR2nn (CD mounted on /mnt)
root> setld -i | grep OSFPGMR (for checking)
When checking, make sure that the packet not only appears, but is also marked as installed!
PS: The error noted above can, in certain circumstances, not find -ltr
as well. The affects the upgrade to Oracle 7.0.16 after 7.1.4.

Here the error is:
LINKING and INSTALLING TNS Listener executables
Can't locate file for: -ltr
Further, please note that the temporary install directory
(e.g., /tmp as suggested by the installation) has the requisite
Permission (777).

SAP Note 16908 - Central SYSLOG does not work

Symptom:

The central SYSLOG cannot be reached/used.

Cause and prerequisites

The central SYSLOG unavailable on Windows NT.

Solution
The Alert Monitor in CCMS (Computer Center Management System) replaces most of the functionality of the central SYSLOG. As a result, the further availability of the central SYSLOG on UNIX systems has also been placed in question; porting the central SYSLOG to Windows NT is not planned.
Please use the appropriate function in CCMS.

SAP Note 16907 - New entries in table GB01C

Symptom:

1. Syntax error in FGBB2*, FGBB3* or GB* after adding a new field to the GB01C table.

2. Message GB081, GB082, GB083 ("Table ... cannot be used in the rule validation/substitution"). The message is displayed during the evaluation of a rule, validation or substituition (e.g. during a posting or simulation). Cause and prerequisites

Table GB01C (view V_GB01C) is used to add or exclude fields from a Boolean class. This means the fields that can be used or substituted in conditions of the validations, substitutions or rules.
However, new tables may not be added to the class. Only if fields already belong to a structure of the Boolean class, can additional fields be added to the same structure.

This is because the application supplies the rule-processor with a limited number of tables and this cannot be increased dynamically at runtime.
As a result, the system displays GB081, GB082 or GB083 even if the following conditions are fulfilled:

1. With a modification of the standard system (tables or programs of the Boolean processor), you have added a field to the Boolean class.

2. The field is part of a structure (table) whose other fields are not contained in this class.

3. The field is used or substituted in a condition. Solution

If you have used a modification to add fields from new structures to the Boolean class, reverse this modification. Change the validations, substitutions and rules of the Boolean class in question so that you can no longer use this field. Run report RGUGBR00. In the selection screen, activate all checkboxes.

Examples are:

- R/3 master data, e.g. : cost center data from table CSKS

- non-SAP data; user-defined tables

Additional key words

GB081, GB082, GB083

SAP Note 16906 - Balance sheet/P+L acct. assignments disappear

Symptom:

Key words: Balance sheet, P+L, FSE2, FSE3 Interval account
Maintenance of account assignments works properly. When you save and display again, the old items may still appear.

Cause and prerequisites

This case involves pure credit or debit assignments. The interval breakdown is different for debit than for credit.

Assets: 1000 - 1999 Debit
Liabilities: 1000 - 1500 Credit
1501 - 1999 Credit

Solution
Problem can be solved in the application.
The error does not occur when account assignment is identical in debit and credit:

Assets: 1000 - 1500 Debit
1501 - 1999 Debit
Liabilities: 1000 - 1500 Credit
1501 - 1999 Credit

Additional key words

FSE2 FSE3 SAPMF02E

SAP Note 16897 - SIS: Problems with key figure "workload" (S005)

Symptom:

Termination BCD_FIELD_OVERFLOW or CONVT_OVERFLOW ...
when updating info structure S005 (shipping point) and with standard analysis "Shipping point". The same applies for the structures S005BIW1/-BIW2 (for the use of SAP-BW).

Cause and prerequisites

The "delivery workload" and "returns delivery workload" key figures are included in info structure S005. The workload is made up of the time needed to set up and process the material being used. This data is included in the material master.
The current definition of the workload key figures in the info structure only allows you to update up to the maximum sum of 999.99. If you exceed this number while updating, you will receive a termination message.
When the total of the standard analysis is made up of very high values for the key figures in an information structure, the standard analysis is terminated.

Solution
Check whether the setup times/processing times in the material master have been maintained correctly as the workload is determined from these times.
If the correct setup times and processing times still lead to the error, you need to increase the key figures in the info structure using the DDIC maintenance transaction. This is done either by assigning a new larger domain or by changing the domain already being used (DECV5_2). There is no problem about extending the field length from 5 to 7. The database table S005 must then be converted. For the exact procedure, refer to Note 62182.

Additional key words

MCV_STATISTICS_UPD_V1_DELIVER, MCV_STATISTICS_UPD_V2_DELIVER

SAP Note 16892 - ME21: Conversion factors are not generated

Symptom:

When creating a purchase order with different order unit, the conversion factors for quantity units stored in the material master records are sometimes not generated. The user then receives a popup in which he/she is requested to enter conversion factors.

Cause and prerequisites

This is a restriction in function module UNIT_CONVERSION which only allows figures up to a certain value for the numerator and denominator of the conversion factor. If it is exceeded, then raise exception OVERFLOW occurs. If this applies in this case can be determined by setting a breakpoint in function module ME_CONVERSION_BPRME and by analysing the return code of UNIT_CONVERSION (which is called UNIT_CONVERSION_WITH_FACTOR as of lately).

Solution
The solution is differs from case to case. The conversion factors 9857 G (grams) = 100 BG (sheets) were maintained in the concrete customer example and DEM 100 / 100 KG (kilograms) were specified as price in the purchase order. The conversion KG --> G was avoided by entering the (equivalent) data DEM 1 / 1000 G and the OVERFLOW did no longer occur.

SAP Note 16883 - ArchiveLink: Error from the archiving system

Symptom:

When accessing an archived document or when trying to archive a document, the following error message occurs: "ArchiveLink: Error from the archiving system." Error messages OA 201 to OA 211 with different long texts.

Cause and prerequisites

An error occurred in the addressed archiving system.

Solution
The error must be corrected in the addressed archiving system. This is generally no R/3 problem. If the user cannot solve the archiving problem himself, he has to contact his archiving offerer.
An exception would be an user error, such as the attempt to add an already archived document to another SAP document without a document being displayed in the viewer for archived documents.

SAP Note 16875 - TemSe objects do not match TemSe files

Symptom:

There are files of TemSe objects for which no TemSe objects exist.

Reason and Prerequisites

Only TemSe administration knows which files belong to which TemSe objects.
If you copy databases, restore from a data backup, delete clients without deleting their objects first, or copy clients using the improper tools, the relation may be lost.

Solution

When files are missing, you can use program RSTS0020 (TemSe consistency check) to delete the orphaned TemSe objects.

When there are too many files, there is no simple way, as the necessary information on the database no longer exists. The following method is relatively certain:

Check the log. Depending on your authorization, the consistency check will run either only the current client or in all clients.

Example: /usr/sap/C11/SYS/global/003SPOOL/000122334 for TemSe object [003]SPOOL22334,1 for spool request 22334.
Each TemSe object can store its files in other places, however, this is not normally the case.

Move these files to a different directory.

Run a new consistency check to make sure step 5 did not cause any damage.

7.
Delete the files.

SAP Note 16874 - Credit management: duplicate document value classes

Symptom:

Credit management: it is possible to assign document value classes more than once during the assignment to credit control areas and document values, although it would be desirable to have unique combinations of credit control area, credit value, and document value class.

Solution
You must make sure yourself that the combinations of credit control area, credit value, and document value class are unique.

SAP Note 16857 - Display of add.: PO box instead of mailbox/P.O. Box

Symptom:

In English addresses, the text for 'Postfach' reads
Mailbox or
P.O. Box or
PO box
However, the preferred translation is PO Box.

Cause and prerequisites

Numbered text 001 in program SAPLSADR has been translated differently.

Solution
Use Transaction SE63 to translate numbered text 001 in program SAPLSADR.
Translation ---> Short texts ---> Program ---> Numbered texts
Program SAPLSADR
Source lang.D
Target lang.E
Proofread + translate
Enter new translation for text 001 and save.

Additional key words

BAS_PRINT

SAP Note 16853 - ME21: Text field not ready to accept input (consignment/mate

Symptom:

Two lines in entered text lost.

Cause and prerequisites

The item text field is not ready to accept input in the case of consignment items or material group items. If you nevertheless select (mark) the item text and choose "long text", you are able to enter text but the first two lines are overwritten with "space".

Solution
In Purchasing Customizing, you have to set the field in question to "ready to accept input" (via transaction OMLE, Purchasing Customizing). Then: "Transactions -> PO processing -> Screen layout, document level". There, position the cursor on PT2F (or via "Transactions -> Contract -> Screen layout, document level" PT8K for material groups) and choose "Details". Then choose "Reference data, item" and select "Optional entry" for "Texts". The problem should then no longer re-occur.

SAP Note 16851 - 2.2x documentation CD-ROM and 2.1x R/3 System

Symptom:

No connection from the R/3 System Rel. 2.1x to the documentation CD-ROM version 2.2x

Cause and prerequisites

Version 2.1 of the documentation CD-ROM for Release 2.1 is based on the retrieval software from LASEC.
Version 2.2 of the CD-ROM documentation for Release 2.2 is based on the WinHelp mechanism from the Windows operating system.

Solution

The two procedures are completely incompatible. No solution available.

Additional key words

Online_Docu

6.1.11

5.1.11

3.1.11

MCV_STATISTICS_UPD_V1_ORDER or MCV_STATISATICS_UPD_V2_ORDER or

MCV_STATISTICS_UPD_V1_DELIVER or MCV_STATISATICS_UPD_V2_DELIVER or

MCV_STATISTICS_UPD_V1_INVOICE or MCV_STATISATICS_UPD_V2_INVOICE.

Subscribe

Articles