SAP Note 11051 - Customer-specific posting strings (Customizing) .

Symptom

As of IS-H Release 2.11 (July 1994), it is possible to lay out the line item texts for a specific customer for copayment. The following conventions apply in this case:

- the customer function module must start with 'ZZ_'
- the following interface is mandatory:

Import parameter EINRI Reference structure TN01-EINRI
FALNR Reference structure NFAL-FALNR
PATNR Reference structure NPAT-PATNR
Export parameter POPTEXT Reference structure BSEG-SGTXT
- Example:
FUNCTION ZZ_POSTING_STRING.
*"
*"Lokale Schnittstelle:
*" IMPORTING
*" EINRI LIKE TN01-EINRI
*" FALNR LIKE NFAL-FALNR
*" PATNR LIKE NPAT-PATNR
*" EXPORTING
*" POSTEXT LIKE BSEG-SGTXT

TABLES: NPAT, NBEW,...
DATA: ...

* Datenbeschaffung
SELECT SINGLE * FROM NPAT WHERE PATNR = PATNR.
...

* Zuweisung an Belegpostionstext
POSTEXT = ...

ENDFUNCTION.

Cause and prerequisites

If the conventions are not adhered to, a runtime error can occur (incorrect interface) or the customer function module is not called at all (incorrect name)

Solution
Please check the interface and the syntax.

Key word: Copayment

SAP Note 11047 - Display/maintain G/L account name .

Symptom

Customer carries out G/L account master data display (FS03) and
G/L account master data change; he is surprised that the G/L
account name (short text and long text) are different in both
transactions.

Cause and prerequisites

You can allocate a maintenance language and several alternative
languages to a chart of accounts. (Customizing; Master records;
G/L accounts; Chart of accounts)
For G/L account display, the name is displayed in the logon
language if this language is defined as an alternative language.
For G/L account master data change, the name is always displayed
and maintained in the maintenance language.
If the logon language is not equal to the maintenance language,
the different names are held.
By the way: the name is translated with (FST2):
General ledger menu: Master records; Chart of accounts; Maintain
acct name

Solution
See cause

Key word: FS03

SAP Note 11040 - FM: No CLOSE operations performed due to OFFLINE.

Symptom

After a successful backup, the UNIX mt program reports the following when trying to set a tape in the tape drive to offline:
mt lu 0: No CLOSE operations performed due to OFFLINE.

Cause and prerequisites

Tape drive hardware error which is confirmed be the following UNIX command sequence:
mt -t /dev/rmt/0hnc offline
mt lu 0: No CLOSE operations performed due to OFFLINE.
mt -t /dev/rmt/0hnc rewind
/dev/rmt/0hnc: I/O error

Solution
Check the tape drive hardware.
Temporary workaround: mark the rewind_offline parameter in the init.sap profile as a comment (add a "#" sign at the start of the line). In this case tapes remain in the tape drive after a backup.

Keyword: BRBACKUP

SAP Note 11026 - For FI planning (FSE5), error message A044 is outpu.

Symptom

The error message reaches during planning with FSE5
A044 : Item & cannot be planned, no accounts allocated
However, accounts are allocated.

Cause and prerequisites

The balance sheet version was changed again following the planning
preparation; thus the sets generated beforehand are no longer
up-to-date.

Solution
Carry out planning preparation once more.
The planning data already entered remains unchanged in any case.

Key word: FE044

SAP Note 11024 - IS-H: Line item text is not printed.

Symptom

The line item text should be output on the FI forms, however the text is not printed on the should the Financial accounting forms.

Cause and prerequisites

The text is only printed on the form if it starts with an '*'.

Solution
Specify '*' as the first character of constant text or use format variant '=P3'.

Additional key words

Copayment, form printout, print, NE11, consulting

SAP Note 11013 - Transporting profiles and authorizations.

Symptom

Question:
How can profiles and authorizations be transported between clients
or systems?

Solution
First create a correction using Transaction SE01.
Then call up profile maintenance: Tools -> Administration ->
User maintenance -> Profile -> Restrict work area; press ENTER,
-> Profile -> Transport. All existing active profiles are then
displayed in alist where you can select the profiles to be transported
(or all profiles). After you press ENTER, you are prompted to
enter your correction number. Press ENTER once more. The system
asks you whether all dependent objects (lower-level profiles and
authorizations) are to be included in the transport.
If you want to transport the profiles without dependent objects,
you can also include selected authorizations in the correction
(access via authorization maintenance).

Use Transaction SE01 to release the correction to a transport request.
Note # 10101 explains how you transport objects from a source client
to a target client or from a source system to a target system.

Please note: The transport overwrites profiles and authorizations
with the same name in the target system. Therefore profiles with
the same name in different systems and clients should have the same
content.
If you want to change an SAP standard profile, please first copy
the profile and then change the copy.
You can assign arbitrary names to your profiles except those reserved
for SAP, i.e., the profiles and authorizations whose name have an
underscore as the second character or the profile names SAP-ALL
and SAP_NEW... .
The SAP profiles are overwritten by every upgrade, i.e., changes
that you have made in the SAP standard profiles will be deleted.

Key word: Transport auth.

SAP Note 11006 - Posting to special periods not possible using MR01.

Symptom

When the user attempts to post an invoice using MR01 to a period defined
as a special posting period, the error message M8 022 appears: Allowed
posting periods..
The invoice cannot be posted to a special posting period.

Cause and prerequisites

It is not possible to post an invoice to a special posting period using
MR01.

Solution
An invoice must be posted in all cases to a period defined as a
normal posting period (and not as a special posting period).

Key word: Special periods

SAP Note 20307 - Field overflow when converting quantities VA01 etc. (BM398).

Symptom

Field overflow in VA01
Field overflow field: O_UMREZ; Value; +1.0000 etc.
System message BM398.

This error always occurs when five decimal places are not sufficient when converting between the unit of measure entered and the stockkeeping unit.
Example: Stockkeeping units in grams and sales in tons. Six decimal places are needed for this conversion.
When converting between metrical and non-metrical units, see also note 23771.

Cause and prerequisites

The conversion factor is saved in the item with numerator and denominator having only five decimal places.

Solution
There is no solution at this time.

SAP Note 20302 - OBXR Down payments.

Symptom

In der Standardauslieferung sind unter "Anzahlungen" auch Bürgschaften
enthalten. Unter Anzahlungen fallen meines Wissens nur die SHB-Vorgänge
A und F.

Cause and prerequisites

For Russia was defined a Down payment for Goods bought and sold as they are to customers.

Solution
Definition of a new downpayment for customers -goods- T
In the chart of accounts CARU there are some defined accounts for it.

SAP Note 20295 - Reports with fixed print parameters.

Symptom

Reports should print output with fixed defaults, for example, the print format should always be assigned a fixed value (e.g. X_65_132).

Cause and prerequisites

Various. Example: to prevent users from starting a print request with an incorrect format.

Solution
Report must be started from a new report:
REPORT Start_.
SUBMIT TO SAP-SPOOL WITHOUT SPOOL-DYNPRO .

The are the familiar print parameters:
DESTINATION ''
COPIES
LAYOUT ''
IMMEDIATELY <1/0>
RECEIVER
KEEP IN SPOOL <1/0>
COVER PAGE <1/0>
and so on. Use only the appropriate options for the user.
If the user calls the new Start_Report instead of the old report, this guarantees that the report will never inadvertently be started with incorrect print parameters, since the screen for entering the screen parameters is no longer displayed. Instead, the report output is sent directly to the spool with the selected parameters.
Of course, there is no way to prevent the old report from being called with the wrong print parameters again.

SAP Note 20279 - Unit of measure in delivery for stock transp. order.

Symptom

The unit of measure of the delivery quantity cannot be changed if this delivery is based on a transport order.

Cause and prerequisites

The purchase order update can only be made in the unit of measure of the order item. A change to this unit of measure in the delivery is therefore not possible.

Solution
none

Additional key words

stock transport order

SAP Note 20272 - Credit management: F4778 Data to be reset.

Symptom

When you display the credit master data, message F4778 is issued: "Credit limit for control area & is to be reset".

Cause and prerequisites

The assignment of company codes to control areas has been changed, and the credit data of the affected control areas must be reset as a result.

Solution
As described in the long text of the message, start program RFDKLI20. The program must run for all accounts in the control area, not only for the account that caused the message! Make the following entries on the selection screen:

From account (initial)
To account (initial)
From control area EURO
To control area EURO

The message should no longer appear.
If it continues to appear, you can use transaction SM31 to remove the entry (EURO) from table T014N. Please install the correction described in note no. 17173 before you run RFDKLI20.
Other relevant notes: 15723 and 19040

Key words: FD32 FD33 SAPMF02C RFDKLI20 KNKK T014N

SAP Note 20254 - INFO: Values from SD not transferred to CO-PA .

Symptom

During the transfer of billing documents from Sales and Distribution (SD) to Profitability Analysis (CO-PA), some condition values or entire billing documents are not transferred.

Cause and prerequisites

Incorrect or missing settings in Customizing.

Solution

For repetitive manufacturing, billing data should always be transferred from SD to CO-PA at the same time as it is released for accounting.

For transferring conditions into CO-PA, the following applies:

Those conditions can be transferred to CO-PA that have been assigned to a CO-PA value field in the value field assignment in the configuration menu for the Profitability Analysis.

Regardless of this value field assignment, you also must observe the following restriction:

Only certain conditions created in SD can be transferred to CO-PA. The following conditions are sufficient:

a) revenues and sales deductions whose G/L account was created in CO with cost element type 11 = "Revenue element" or 12 = "Sales deduction" (such as revenues or discounts),

b) conditions that are defined as statistical in SD (such as the internal allocation price).

c) If a condition can be statistical or non-statistical (this is the case, for example, for conditions for rebates or invoice lists), the cost element defined for the G/L account must be of type '11' or '12'.

d) Tax conditions are not posted in CO-PA.

e) Active conditions (inactive conditions are not transferred. If all the conditions in an item are inactive, the order item is not transferred to CO-PA).

f) Conditions for special valuation methods (for example in Release 4.0 condition category 'b' = 'Transfer price for group valuation for reporting purposes' or 'c' = 'Transfer price for profit centers'), that update a different currency type than the document or company code currency are not transferred!

For make-to-order production, data must be transferred via order settlement.

Additional key words

SD/CO-PA, VF01

SAP Note 20251 - Delete BOM: DBIF_RSQL_NO_MEMORY.

Symptom

Update termination when you delete large BOMs: error DBIF_RSQL_NO_MEMORY

Cause and prerequisites

When you delete a BOM, a change document line is created for every field of every item. Because this is created in the main update task, the cluster for tables CDPOS, CDHDR reaches the maximum value of 7.5 megabytes without a COMMIT taking place.

Solution

There are currently two ways of deleting the BOM:

1. Multiple-step procedure: delete and post around 200 items, then delete the BOM itself at the end of the process.

2. Alter the change document object such that the individual field names are not listed.

You can then delete the BOMs normally. To do this, call Transaction SCD0; then select change document object STUE for maintenance.

In this object, reset the flag "Documentation of individual fields when deleting" in table STPO. Then call the function "Generate update task" in the Utilities menu to regenerate the update task.

Additional key words

CS80

SAP Note 20223 - No picking message in VL04 .

Symptom

Deliveries exist that were created in a collective run and do not have a picking message (NAST record with application V4), although picking status VBUK-KOSTK = A is set.

Cause and prerequisites

Unknown.

Solution
The affected deliveries can be found with the following test program:

REPORT ZZNAST .
TABLES: NAST, VBUK, VBUP.
SELECT * FROM VBUK WHERE ( KOSTK = 'A' OR KOSTK = 'B' ).
IF VBUK-LVSTK NE SPACE.
SELECT * FROM VBUP WHERE VBELN = VBUK-VBELN AND
( KOSTA = 'A' OR KOSTA = 'B' ) AND
( LVSTA = SPACE ) .
ENDSELECT.

CHECK SY-SUBRC = 0.
ENDIF.
SELECT * FROM NAST
WHERE KAPPL = 'V4'
AND OBJKY = VBUK-VBELN.
EXIT.
ENDSELECT.

IF SY-SUBRC NE 0.
WRITE:/ VBUK.
ENDIF.
ENDSELECT.

The deliveries that appear in the list will not have a picking message. The messages will be generated once you save the delivery in the change transaction (VL02).

In addition, add the following line in program FV50XF0B, form routine BELEG_SICHERN:

* 9. die Nachrichten umbenannt
* 10. die Lieferungen gesperrt beim Hinzufuegen
*--------------------------------------------------------------------

LOOP AT XLIKP.
LIKP = XLIKP. "<-- New line
KOPF_TABIX = SY-TABIX.
TEMP_VBELN = XLIKP-VBELN.

Lastly, install the corrections described in note nos. 11166 and 11869.

SAP Note 20219 - Remaining variance due to wrong system setting .

Symptom

When you calculate variances for production orders and cost object IDs, the message "Remaining variance occurred" is issued because the delivery was allegedly valuated with a different price than the standard price of the material, which was not the case.
Message: KV103
Transactions: KKS1, KKS2, KKS3
Programs: SAPMKKS0, SAPMKKP2

Cause and prerequisites

The program does not check that the delivery value equals the delivered quantity times the standard price. Instead, it checks whether the delivered value is equal to the target costs of the order according to the delivery quantity, which makes more sense. However, because target costs are calculated with the formula "Planned costs divided by planned quantity times actual quantity (= delivered quantity)", rounding differences may arise if the quantity ratios are unfavorable, resulting in a small remaining variance for the delivery value.

Solution
1. Check the valuation variant for valuating the delivery of orders in
Customizing: the standard price should be set.
2. Check whether the remaining variance identified under the delivery
cost element is small enough that it can be explained by rounding
differences (e.g., using the target/actual/variance report). If so,
you can ignore the message.
3. If the message comes up often and is bothersome, it can be prevented
by advance installation of the correction below.

SAP Note 20217 - Remaining variance for materials .

Symptom

For a material with excess consumption or under-consumption, when calculating variances for production orders or cost object IDs, either

1. a quantity variance different than what was expected is calculated, or

2. an input variance or a remaining variance is calculated instead of a quantity variance.

Transactions: KKS1, KKS2, KKS3, KKP5
Programs: SAPMKKS0, SAPMKKP2

Cause and prerequisites

Quantities and costs for orders are not updated separately for individual materials but summarized on cost element and origin group (origin). This leads to mixed variances. Example:
It is assumed that the planned output quantity and the yield are the same, and therefore plan equals target.
Cost elem. Mat. number Target qty Target costs Act.qty Act.costs 400000 M1 10 KG USD 10 11 KG USD 11
400000 M2 20 KG USD 2000 20 KG USD 2000
-----------------------------------------------------------------------
400000 Materials total 30 KG USD 2010 31 KG USD 2011

1. The quantity variance is equal to (actual quantity - target quantity) * planned price.

The planned price is calculated as target costs / target quantity. In the example, material M1 has a planned price of USD 1. This results in a quantity variance of (11 KG - 10 KG) * USD 1 = USD +1. However, since the costs/quantities are not available for the individual material in the order, as described above, the calculation is made with the totals for the cost element. The following applies in this case: planned price for cost element 400000: USD 2010 / 30 KG = USD 67. The quantity variance equals (31 KG - 30 KG) * USD 67 = USD +67.

The actual price equals actual costs / actual quantity, in the example, USD 2011 / 31 KG = USD 64.87. The price variance equals (actual price - planned price ) * actual quantity, thus (USD 64.87 - USD 67) * 31 KG = USD -66.

2. If the materials have units of measure that cannot be added, the cost element has no quantity. As a result you can neither calculate the planned price nor the quantity variance and price variance. Instead, a remaining variance is calculated (in the example: USD 2011 - USD 2010 = USD +1).

3. If the "Manage quantities" indicator is deselected in the cost element master for the material cost element, or if a different unit of measure is defined here than for the material, no quantities are updated in the plan and actual. Then only a remaining variance is calculated here as well.

Solution

1. and 2.
In Releases 2.1 and 2.2, the data can be updated on the lowest level on cost element and origin group. The origin group is defined in Customizing and assigned to the material in the material master. If another origin group is assigned to each material, the data is updated as precisely as possible. You can also create larger groups of materials with the same unit of measure, or assign origin groups only for important (valuable) materials.
In Release 3.0 you can additionally update costs and quantities under the material number, if necessary. Therefore you need to select the "Material origin" field in the material master. The quantity will then always be updated in the consumption unit of the material.

1. Select the "Manage quantities" indicator in the material master and enter an appropriate unit of measure. Caution: This change only applies to production orders and product cost estimates created after this change; existing cost estimates are not affected.

In Release 3.0, the quantities and units of measure are always updated if they can be totalled. The indicators in the cost element master then have no influence.
In Release 3.0, an input variance is calculated in the above cases instead of a remaining variance.
The use of origin groups and material origin leads to an increased dataset and to longer runtimes during period-end closing. Its use should therefore be restricted to important (valuable) materials.
For information on the calculation of resource-usage variances, see Note 23617.

SAP Note 20214 - Unexpected sort sequence .

Symptom

Strange sort sequence for numbers when numeric and alphanumeric data is mixed.
Example: G/L account number
SAKNR CHAR 10
external internal
1 '0000000001'
123 '0000000123'
123A '123A '
A123 'A123 '

It is sorted by the internal representation.

Can be seen in matchcode and all other sorted lists

Cause and prerequisites

The problem is conversion routine "ALPHAEXIT", which is attached to many domains. It handles numeric data differently than alphanumeric data. You cannot remove the conversion routine, however.

The conversion routine is required in many places to guarantee that the system sorts 1,2,9,10, and not 1,10,2,9.

Solution
A) Fill the identifier ("numbers) to the full internal length

B) Have at least one letter in all identifiers

C) Have no letters or special characters in the identifier

D) Get accustomed to the special sort sequence.

Key words: Sort, Account number

SAP Note 20208 - IS-H: Stornierte Zuzahlung erscheint umgebucht .

Symptom

Es werden Zuzahlungen storniert (entweder über die Zuzahlungstransaktion oder direkt in der Finanzbuchhaltung). Die Stornierung wird korrekt durchgeführt, beim erneuten Aufruf der Zuzahlungstransaktion erscheinen die stornierten Zuzahlungen mit dem Kennzeichen "Umgebucht".
Unter Umständen werden Zuzahlungen scheinbar doppelt ausgewiesen.

Weitere Begriffe

Zuzahlung, Eigenbeteilligung, SAPLN019, NE11, Beratung

Ursache und Voraussetzungen

Fehlerhaftes Customizing.
Unter Parameter Zuzahlung wurde für die geleistete Zuzahlung die gleiche Belegart wie für die Gutschrift bzw. Umbuchung der Zuzahlung eingetragen. Dies führt dazu, daß das Programm ein "echtes" Storno einer geleisteten Zuzahlung nicht von einer Umbuchung unterscheiden kann. Bei der Umbuchung wird ja ebenfalls ein Storno Zuzahlung gebucht, allerdings mit einer Gutschrift an den Kostenträger als Gegenbuchung unter der Verwendung der hierfür eigens im Customizing hinterlegten Belegart.

Lösung
Customizing richtigstellen. Es muß eine eigene Belegart für die Umbuchung der Zuzahlung verwendet werden. SAP empfiehlt darüberhinaus, jeweils eigene Belegarten für die Abbildung der Zuzahlungsvorgänge (getrennt nach Forderungsverfahren und Inkassoverfahren) zu benutzen.
Bei der Umstellung im Customizing ist allerdings zu beachten, daß das Zuzahlungsprogramm nach Änderung der Belegarten, alte Zuzahlungen in der Zuzahlungstransaktion nicht mehr findet und das Rechnungsdruckprogramm diese ebenfalls nicht absetzen kann.
Es handelt sich hierbei aber nur um ein Anzeigeproblem, in der Finanzbuchhaltung sind die Posten selbstverständlich noch vorhanden.
Bitte beachten Sie auch den Einführungsleitfaden.

SAP Note 20207 - Operation quantity wrong w/alternative UoM .

Symptom

When the system converts to an alternative unit of measure in the operation, the numerators and denominators are switched.
The error does not occur until after an upgrade from 2.2A-2.2C or 2.1A-2.1I to a higher release level, or in an upgrade from 2.2S-2.2C or 2.1A-2.1I after 3.0, if you maintained your routings up to 2.2C/2.1I such that the result was correct, even though the documentation on the conversion factors states that the conversion factors should have been maintained exactly the other way around.

Cause and prerequisites

Program error corrected in 2.2D/2.1J.

Solution

Change the master data (routing) and order data. To do this, write a report that you execute once and that swaps the conversion factors in the operations. The report does NOT block the data to be changed and must not be performed while routings and/or orders are being changed in the system.

The report changes only the current client data. When there are
several clients active, begin the report either in each client
respectively or extend the DB instructions with CLIENT SPECIFIED,
so that all clients are included in a run.

Attachment: Program coding
TABLES: PLPO, AFVV.
DATA: L_UMREZ LIKE PLPO-UMREZ.


SELECT * FROM PLPO
WHERE ( UMREZ <> 1 OR UMREN <> 1 )
AND ( UMREZ <> 0 OR UMREN <> 0 ).

CHECK PLPO-UMREZ <> PLPO-UMREN .

WRITE: / PLPO-PLNTY, PLPO-PLNNR, PLPO-PLNKN,
PLPO-UMREZ, PLPO-UMREN.

IF PLPO-UMREZ = 0.
PLPO-UMREZ = PLPO-UMREN.
PLPO-UMREN = 1.
ELSE.
L_UMREZ = PLPO-UMREZ.
PLPO-UMREZ = PLPO-UMREN.
PLPO-UMREN = L_UMREZ.
ENDIF.

UPDATE PLPO.

ENDSELECT.

SELECT * FROM AFVV
WHERE ( UMREZ <> 1 OR UMREN <> 1 )
AND ( UMREZ <> 0 OR UMREN <> 0 ).

CHECK AFVV-UMREZ <> AFVV-UMREN .

WRITE: / AFVV-AUFPL, AFVV-APLZL,
AFVV-UMREZ, AFVV-UMREN.

IF AFVV-UMREZ = 0.
AFVV-UMREZ = AFVV-UMREN.
AFVV-UMREN = 1.
ELSE.
L_UMREZ = AFVV-UMREZ.
AFVV-UMREZ = AFVV-UMREN.
AFVV-UMREN = L_UMREZ.
ENDIF.

UPDATE AFVV.

ENDSELECT.

Key word: Scheduling

SAP Note 20202 - Short text is not copied to purchase req.

Symptom

If a short text is maintained on the detail screen in a network for an externally procured material, this short text is not copied to the purchase requisition. Instead, the short text from the material master always appears.

This problem always occurs when a purchase requisition is created via function module ME_REQUISITION_EXT. That is also when a purchase requisition is created from a customer or maintenance order or using BAPI_REQUISITION_CREATE.

Other terms

BAPI_REQUISITION_CREATE, BAPI, ME_REQUISITION_EXT, customer order, VA01, maintenance order, IW31, order, network, ME53, EBAN-TXZ01, TXZ01, MT06E-MAKTX, MAKTX

Reason and Prerequisites

A change of the material short text had not been planned.

Solution
See the correction instructions.

SAP Note 20201 - VA05 ABAP 4/runtime error BCD_ZERODIVIDE. .

Symptom

Transaction: VA05
Program: SAPMSSVO

Menu Path: Sales Document/Sales Order/List

An ABAP runtime error occurs in the sum up function:
BCD_ZERODIVIDE division by zero in the SUMMEN_FUELLEN routine in Member MV75AFS0.

Cause and prerequisites

Program error

Solution
Change member MV75AFS0:

FORM SUMMEN_FUELLEN USING S04-MODUS S04-TBNAM.
:
IF VBCOM-ZUART IS INITIAL.
IF SUMMEN-KWMENG <> 0. <- INSERT
SUMMEN-NETWR = SUMMEN-NETWR * SUMMEN-BMENG / SUMMEN-KWMENG.
ELSE. <- INSERT
CLEAR SUMMEN-NETWR. <- INSERT
ENDIF. <- INSERT
SUMMEN-KWMENG = POSTAB-WMENG.
ENDIF.
COLLECT SUMMEN.
ENDLOOP.
ENDIF.
ENDFORM

SAP Note 20186 - Online redo log member of a group "INVALID".

Symptom

The status of an online redo log member of a group is "INVALID"
--> DB continues running as long as at least one member of the
group is being accessed --> Status "blank".
This information is contained in table V$LOGFILE

Cause and prerequisites

Access to a member temporarily not available (e.g. hardware problem).

Solution
Once the member can be accessed again, the status will be reset from "Blank" to "File in use" during the next write operation.

SAP Note 20179 - CR21, CR22, CR23: Msg CG014, Work center hierarchy.

Symptom

Message CG041: 'Discrepancy between format description and field definition.

Cause and prerequisites

Table TCRH0 (Transaction OP39) is not filled completely.

Solution
To use the hierarchy graphics for work centers (CR21, CR22, CR23), the references to the graphics profile must be maintained correctly in Customizing with Transaction OP39. Table TCRH0 should appear as follows:
CR21 PPS CR_HIER____1 1 CR22 PPS CR_HIER____1 1
CR23 PPS CR_HIER____1 2 CR24 PPS CR_HIER____1 1
CR25 PPS CR_HIER____1 1 CR26 PPS CR_HIER____1 2


The graphics profile CR_HIER____1 must be maintained as follows in general Customizing for graphics profiles (CNG4):
Group PPS
Name CR_HIER____1
Index 1 (or 2)
Node group CR_KNOT____1
Link group CR_KANT____1
Frame group
Options profile CR_OPT_____1 (or CR_OPT_____2)

SAP Note 20176 - Where is the spool request saved?

Symptom

How should profile parameter "rspo/store_location" be used?

Reason and Prerequisites

The documentation is unclear.

Solution

For all releases:

Profile parameter "rspo/store_location" controls where TemSe stores the spooler data.

Possible values:

db
(lower case):
TemSe saves the spooler data in the database. Table TST03 is used for this.
Advantages:
Data will be backed up.

G
(upper case):
TemSe saves the data in global files. To do this, TemSe creates subdirectories in the "global" directory. Details of the path name are controlled by profile parameter "rsts/files/root/G". Do NOT change these details.
Advantages:
It is generally much faster.
Disadvantages:
Data is not regularly backed up.

L
T
(upper case):
TemSe saves the data in local files. Because these files can then only be accessed from the same application server, this setting is a special case, and should not be used. (For more information, see: profile parameters "rsts/files/root/L" and "rsts/files/root/T".)
Advantages:
It is much faster.
Disadvantages:
Data is not backed up.
Generating, processing, and spool work process (among others) must all run on the same application server.


As of Release 4.0A:
As of Release 4.0A, you can individually override the value of the profile parameter mentioned above for each output device.
Menu path:
SPAD -> Change output device -> Edit -> Data storage.
If you choose the option file system (local), the system issues a message stating that the data is saved in the local file system (see above) only when possible. The conditions are:

1. Flag "Immediate output" is set.

2. Flag "Delete after output" is set.

3. The function that generates the spool request (the dialog work process) is located on the same server as the output formatter (the spool work process).

Other terms

rspo/store_location, data storage, spool request

SAP Note 20158 - EC93/INTRASTAT - VAT ID no. not printed .

Symptom

In the INTRASTAT declaration, transaction MEIP, the VAT registration number is not printed correctly.

Additional key words
Cause and prerequisites

The affected field - T001Z-PAVAL - was not maintained correctly.

Solution
Field T001Z-PAVAL is maintained with transaction OBY6.

Menu: Tools -> Customizing -> Configuration menu -> Accounting -> Financial account -> Bookkeeping -> Environment -> Company code -> Global parameters -> Detail -> Additional specs: Number for INTRASTAT declaration.

Comment: The contents of this field are used for the INTRASTAT declaration, not the VAT registration number (field V_001_B-STCEG) that is maintained in the view "Company Code: Global Data".

SAP Note 20149 - Valuation not carried out for the costing object .

Symptom

When you enter a completion confirmation, the system issues the message CK060 'Valuation not carried out for the costing object' in the costing log. When the confirmation is saved, the order is not debited with actual costs.

Cause and prerequisites

Insufficient data maintained

Solution

Please check that,

• a work center is defined for the confirmation / operation

• the costing indicator is set in the control key of the confirmed operation

• the external processing indicator is set in the control key of the confirmed operation

• a cost center with activity types has been defined for the work center specified in the confirmation, and that the activity types are valid on the posting date of the confirmation (Transaction: CR03, Goto -> Assignments -> Cost center assign.)

• activity types are also assigned to the operation in the routing (these have been copied from the work center and may have been changed)

• activity values are entered for the activity types maintained in the operation in the routing

• activity prices have been defined for the specified activity dates and are valid on the posting date (Transaction KP23)

SAP Note 20148 - No "Back" or "Cancel" on print parameter screen .

Symptom

When the statement NEW-PAGE PRINT ON DESTINATION ... is called, a screen appears in which only the functions "Print" and "Exit" are possible, but not "Back" or "Cancel".

Cause and prerequisites

This is not an error. These buttons have to be deactivated because no return code is (or can be) set by the NEW-PAGE PRINT ON statement for compatibility reasons. Pressing the "Back" or "Cancel" key would have to be reported to the application program by setting a return code, however. The "Exit" function causes the program to terminate, and can therefore be handled by the NEW-PAGE PRINT ON statement itself, without requiring the assistance of the application program.

Solution
Instead of the old variant NEW-PAGE PRINT ON DESTINATION ..., use the new variant NEW-PAGE PAGE PRINT ON PARAMETERS ... (see the online documentation for NEW-PAGE).

SAP Note 20137 - IS-H Treatment deletion flag .

Symptom

In spite of set deletion flag - also called deletion indicator - an object (e.g. a guarantor) can still be used with concrete entry of a key. No warning appears that such a deletion flag exists.
On the other hand, the object is not displayed in the possible entries (F4).

Cause and prerequisites

Not an error! Deletion flag conceptual design.

Solution

If an object may no longer be used, is must be blocked (in the case of the guarantor, the entire business partner). The deletion flag should have no effect on any subsequent functionality whatsoever, for reasons of data integrity.

Here is the conceptual design of the deletion flag in detail, also from a point of view of cancelling and blocking:

Cancelling

Cancelling is understood as 'logical deletion': the deletion can be duplicated, since the object (at first) remains physically in the system. However, the object is at the same time no longer usable in application functions, that is, it is no longer logically available.

Deletion indicator/deletion flag

With the deletion indicator, the user shows that an object is to be deleted. Example: They enter a guarantor by mistake and want to delete it again. However, since not all dependent objects can be checked online (generally for performance reasons) (e.g. insurance data, insurance verifications, forms, billings etc.), the object is initially kept in the system for reasons of consistency, and this is without restrictions on the subsequent functions.

In the transaction in which the object is directly edited (in the above example: Change guarantor) a note appears that the objects has a deletion flag. This can also be reset again here.
In subsequent functions, the deletion indicator is not taken into account at all.
Example: A guarantor for which the deletion indicator is set can nevertheless be used in the insurance relationship or for billing a case. No W or I messages are output however.

However, on F4 lists of dependent functions, an object with a deletion indicator is no longer used, as standard (example: F4 in the insurance screen on the Guarantor field does not show any guarantors flagged for deletion, as standard). But you can also list the objects flagged for deletion via an additional checkbox "Deletion indicator" in the selection screen (in the example: "Guarantor list: Initial screen").

Blocking
With blocking, the user temporarily prevents an object being reused in dependent functions. Example: A station is blocked for a specific period, so that no movements which are created or changed for the affected period can refer to it. However, dependent objects created earlier which are no longer changed are not affected by the blocking. The blocking is thus a creation block. The blocking is always supported by a blocking interval (start date/end date).

SAP Note 20128 - User name - ? - in tran. ST03, top 40 hit lists .

Symptom

In transactions ST03, ST03N, ST03G, STAD, or STATTRACE, no user names are displayed. Instead, the system displays "- ? -" or a hash key (as of SAP_BASIS 7.00).
This also affects the BI-based IT performance reporting in Solution Manager.

Reason and Prerequisites

The user is not authorized to display user data.

Solution
The user requires the value S_TOOLS_EX_A in the field AUTH of authorization object S_TOOLS_EX. This exists, for example, in the profile S_TOOLS_EX.
For the BI-based IT performance reporting, the user that you use for the data extraction must have the relevant authorization.

Other terms

CCMSBISUITE

SAP Note 20120 - Cash mment position / liquid. forecast: No output .anage

Symptom

In cash management position, liquidity forecast or cash concentration, there is no output or not enough output.

Cause and prerequisites

The grouping is probably not maintained correctly (view V_T038).

Solution
You must take into account the field length when defining the grouping in view V_T038. This view has two types of entries: one for levels (type = 'E') and one for groups (type = 'G').
For the level entries, you must always make a two-character entry in the field "Selection", for example, F0 or F+ or ++.
For the group entries, you must always make a ten-character entry, for example, 0000113100 or ++++++++++, providing it is the cash management position (since only G/L accounts are involved there and they are always made up of ten characters).
For group entries for customers or vendors, you have to take into account the length of the groups as it is defined in the master record and also in view V_T035. If, for example, all of your groups have two characters, you also have to define the group entries with two characters in view V_T038. If, for example for major customers and major suppliers, you have defined the account number (with leading zeros) as a group in the master record and in V_T035, you need an additional entry with length 10 in V_T038. If you have chosen different lengths for the group definition, you may need as much as 10 entries, namely '+', '++', '+++', '++++' to '++++++++++'.
If you still do not get an output although V_T038 is maintained correctly, it may be due to missing authorizations. The following authorization objects are relevant for cash management and forecast: F_FDSB_BUK
F_FDSB_GSB
F_FDSR_BUK
F_FDSR_GSB
F_FDES_BUK
F_FDES_GSB

Additional key words

RQ033

SAP Note 20111 Double interest calc. of res. items (days overdu -e) .

Symptom

During the calculation of interest in arrears, interest is possibly paid twice on residual items. Interest is paid on the source document from which the residual item originates until the document date of the clearing document (= residual item). If the residual item has a due date which is before this document date (usually the date of the source document), interest is paid so far as of this due date.

Cause and prerequisites

Program error.

Solution
Please insert the lines marked with "<--insert" into program RFDUZI01 in subroutine 'FORM BESTIMME_BP_FAEDT':

SAP Note 20105 - Error BCD_ZERODIVIDE when processing the dlv. due list .

Symptom

If an order item that is relevant for delivery has requested quantity 0 (VBAP-KWMENG) and confirmed quantity > 0 (VBAP-KBMENG), a dump occurs in transaction VL04 (delivery due list) with error message 'BCD_ZERODIVIDE'.

Cause and prerequisites

This situation was not trapped in error handling.

Solution
Add the source code specified under "Advance corrections" to program LV05IFRE.

Additional key words

Dump

SAP Note 20097 - SE30: Runtime measurement error (Multi-processor machine), O.

Symptom

The analysis of a measurement
- shows a "runtime measurement error",
- ends with an OVERFLOW runtime error.

Reason and Prerequisites

This message may have the following causes:

1. The application server is a multi-processor machine on which the clocks of the individual processors are not sufficiently synchronized. With high time resolution of the measuring clock, this leads to time leaps in case of a processor change so that negative time readings may occur.

2. The kernel release is lower than 4.0A, the application server is either a single-processor machine or a multi-processor machine where the individual processor clocks are not fully synchronized (see the platform list in the 'Solution' section).

Solution

1.

-> For shorter transactions, it is often sufficient to repeat the
measurement (no processor swap).

-> Large transactions should be measured

- on a single processor machine
- on the following platforms:
- AS/400 with OS/400
- IBM with AIX
- SNI with SINIX
- SUN with SUN-OS
- Windows NT

If such a platform does not exist, measure again using a low
measuring accuracy. The measuring accuracy can be set using
the following menu function:
Runtime analysis -> Settings -> Measuring accuracy...

-> As of Release 4.5A, the user can set the measuring accuracy from
high to low. For this, refer to the ABAP online
documentation on the statement SET RUN TIME CLOCK RESOLUTION.

2. Ignore the message. The data displayed are correct.

Other terms

ABAP, SE30, ATRA, time measurement error, multi-processor machine,
BCD_FIELD_OVERFLOW

SAP Note 20094 - Deliveries do not appear in VL16.

Symptom

If individual days are selected, the message "No data for these selection conditions" is issued; but if 2 subsequent dates are selected, deliveries for picking are displayed.

Example:
Selection date: 15MAR95 --> "No data for these selection..."
Selection date: 16MAR95 --> "No data for these selection..."
Selection date: 15MAR95 - 16MAR95 --> Deliveries are displayed

Cause and prerequisites

Transaction VL16 displays all the deliveries in which the material availability date and the picking date lie within the selected period.

Solution
If you do not want this, you must change program MV50LF01, FORM "KODAT_SELECTION", as follows:
Change all lines where "MBDAT in ITAB_DATUM" appears to comment lines (enter an asterisk as the first character).
The program will then only select by picking date.

SAP Note 20089 - Logistics order: message E139(IW).

Symptom

Message E(IW)139 or E139 is issued when entries from the SAP name range are missing from table TC060 or TC062.

Cause and prerequisites

The table may have been damaged during an upgrade, or was not delivered properly.

Solution
Maintain the table: transaction SM31 Table TC060 (for Release 2.2):


Order type Sequence key
10 FCHECK
10 OC0001
10 OC0002
10 OC0003
20 FCHECK
20 OC0001
20 OC0002
20 OC0003
20 OC0004
20 OC0005
20 OC00E1
30 FCHECK
30 OC0001
30 OC0002

Maintain the table: transaction SM30, view V_TC062 (for Release 2.2)


Order Sequen Check Program Scrn Panel

10 FCHECK 0001 SAPLCOFD ED 0100
10 FCHECK 0002 SAPLCOFD ED 0120
10 FCHECK 0003 SAPLCOFD ED 0140
10 OC0001 0001 SAPLCOVF V1 0110
10 OC0001 0002 SAPLCOVF V2 0130
10 OC0001 0003 SAPLCOVF V4 0160
10 OC0001 0004 SAPLCOVF V5 0170
10 OC0001 0005 SAPLCOVF V6 0150
10 OC0002 0001 SAPLCOVF V3 0140
20 FCHECK 0001 SAPLCOFD ED 0100
20 FCHECK 0002 SAPLCOFD ED 0120
20 FCHECK 0003 SAPLCOFD ED 0140
20 OC0001 0001 SAPLCONW V1 2310
20 OC0001 0002 SAPLCONW VA 2370
20 OC0002 0001 SAPLCONW KD 2550
20 OC0003 0001 SAPLCONW VU 2311
20 OC0004 0001 SAPLCONW V2 2312
20 OC0005 0001 SAPLCONW FD 2510
20 OC00E1 0001 SAPLCONW VA 2380
30 FCHECK 0001 SAPLCOFD ED 0100
30 FCHECK 0002 SAPLCOFD ED 0120
30 FCHECK 0003 SAPLCOFD ED 0140
30 OC0001 0001 SAPLCOIH VD 3100
30 OC0002 0001 SAPLCOIH VD 3110

SAP Note 20086 - INF SQL error -861: Cannot create new PDQ thread .

Symptom

INF SQL error -861: Cannot create new PDQ thread
in the online log file contains the error message:
09:16:28 User thread table overflow - user id xxxx

Cause and prerequisites

OnLine 7.10 supports Parallel Data Query (PDQ). In this case, several threads work in parallel during an SQL statement to provide the required data. SQL error 861 means that an SQL statement cannot allocate any further threads.
Onconfig parameter is not set for PDQ.

Solution
Raise the parameter USERTHREADS and the parameter TRANSACTIONS, for example:
USERTHREADS 600 # Maximum number of concurrent threads
as user informix in file $INFORMIXDIR/etc/onconfig..

You can also change the degree of parallel processing . To do this, you must change the PDQPRIORITY parameter (standard value: 50, possible value is 5, for example).

It is possible to completely switch off parallel processing of one query by setting the parameter MAX_PDQPRIORITY in the onconfig-file to 0.

Keyword: INF ONCONFIG

SAP Note 20085 - MD04..: Pop-up for displaying MRP element .

Symptom

You can call up detail displays in the form of a pop-up for the individual elements in the MRP list displays (MD04, MD05, MD02, MD03, MD43).

Problems can occur with
1) scheduling agreements (SD)

2) production orders
A termination occurs if, for example, via a final confirmation which lies above the original order quantity in terms of quantity, technically a negative actual scrap quantity occurs.

Additional key words

Scheduling agreement, pop-up, additional data, display element,
production order

Cause and prerequisites

1) Minor program error
Corrected in the standard system of Releases 2.2G or 2.1M.
2) Error in the pop-up screen.
Corrected as of Release 3.0F.

Solution
corrections.

SAP Note 20079 - PC entry: Conversion of CoID from 6->4 chars .

Symptom

Limitation of FI-LC PC entry: only four-digit companies can be processed.
Message GC053 is issued: "Only 4 digit CoID allowed for data entry via PC! XXXXXX is too long".

Cause and prerequisites

*

Solution
If there is a way to uniquely convert the 6-digit company numbers into 4-digit numbers, you can modify programs RGCDOW10 and RGCPCU10 as follows.
In the example, companies HB0001-HB0003 and HB01-HB03 were used. The 4-digit company IDs that are only used for PC entry purposes should not be defined in the R/3 System. These company numbers are used in the PC entry program.


************************************************************************
REPORT RGCDOW10 MESSAGE-ID GC LINE-SIZE 132.
:
* Korrekturen:
* MODI 120495 Modifikation Umschlüsselung Gesellschaften
:
* Gesellschaftsname prüfen und konvertieren
* perform r2_comp_check using gesnr. "wdu35907 "MODI
MOVE GESNR TO GD_RCOMP. "wdu35907
:
:
FORM LES-TAB880.
:
* perform r2_comp_check using t852g-rcomp. "wdu35907 "MODI
:
:
FORM R3_R2_COMP USING P_COMP06 P_COMP04.

DATA: LD_COMP(6).

MOVE P_COMP06 TO LD_COMP.

* if ld_comp co '0123456789'. "MODI
* p_comp04 = ld_comp+2(4). "MODI
* else. "MODI
* p_comp04 = ld_comp(4). "MODI
* endif. "MODI

* Bitte ordnen Sie in der CASE-Leiste allen 6-stelligen "MODI
* Gesellschaften eindeutig eine 4-stellige GesNr. zu. "MODI

CASE LD_COMP. "MODI
WHEN 'HB0001'. "MODI
P_COMP04 = 'HB01'. "MODI
WHEN 'HB0002'. "MODI
P_COMP04 = 'HB02'. "MODI
WHEN 'HB0003'. "MODI
P_COMP04 = 'HB03'. "MODI
WHEN ..... "MODI
P_COMP04 = ..... "MODI
: "MODI
WHEN '999999'. "muß angegeben werden "MODI
P_COMP04 = '9999'. "muß angegeben werden "MODI
WHEN OTHERS. "MODI
IF LD_COMP CO '0123456789'. "MODI
IF LD_COMP+0(2) NE '00'. "MODI
MESSAGE A004 WITH LD_COMP. "MODI
ELSE. "MODI
P_COMP04 = LD_COMP+2(4). "MODI
ENDIF. "MODI
ELSE. "MODI
IF LD_COMP+4(2) NE SPACE. "MODI
MESSAGE A004 WITH LD_COMP. "MODI
ELSE. "MODI
P_COMP04 = LD_COMP(4). "MODI
ENDIF. "MODI
ENDIF. "MODI
ENDCASE. "MODI

ENDFORM.


************************************************************************
REPORT RGCPCU10 MESSAGE-ID GC.
:
* Korrekturen:
* MODI 120495 Modifikation Umschlüsselung Gesellschaften
:
:
*-Gesellschaftsname prüfen und konvertieren---------------------------
*PERFORM R2_COMP_CHECK USING GESNR. "wdu35907 "MODI
:
:
FORM R3_R2_COMP USING P_COMP06 P_COMP04.

DATA: LD_COMP(6).

MOVE P_COMP06 TO LD_COMP.

* if ld_comp co '0123456789'. "MODI
* p_comp04 = ld_comp+2(4). "MODI
* else. "MODI
* p_comp04 = ld_comp(4). "MODI
* endif. "MODI

* Bitte ordnen Sie in der CASE-Leiste allen 6-stelligen "MODI
* Gesellschaften eindeutig eine 4-stellige GesNr. zu. "MODI

CASE LD_COMP. "MODI
WHEN 'HB0001'. "MODI
P_COMP04 = 'HB01'. "MODI
WHEN 'HB0002'. "MODI
P_COMP04 = 'HB02'. "MODI
WHEN 'HB0003'. "MODI
P_COMP04 = 'HB03'. "MODI
WHEN '999999'. "MODI
P_COMP06 = '9999'. "muß angegeben werden "MODI
WHEN OTHERS. "muß angegeben werden "MODI
IF LD_COMP CO '0123456789'. "MODI
IF LD_COMP+0(2) NE '00'. "MODI
MESSAGE A004 WITH LD_COMP. "MODI
ELSE. "MODI
P_COMP04 = LD_COMP+2(4). "MODI
ENDIF. "MODI
ELSE. "MODI
IF LD_COMP+4(2) NE SPACE. "MODI
MESSAGE A004 WITH LD_COMP. "MODI
ELSE. "MODI
P_COMP04 = LD_COMP(4). "MODI
ENDIF. "MODI
ENDIF. "MODI
ENDCASE. "MODI

ENDFORM.
:
:
:
FORM R2_R3_COMP USING P_COMP04 P_COMP06.

DATA: LD_COMP(6).

* Bitte ordnen Sie in der CASE-Leiste allen 4-stelligen,
* für die PC-Erfassung neu angegebenen Gesellschaften, "MODI
* eindeutig die im System bestehende 6-stellige GesNr. zu. "MODI
CASE P_COMP04. "MODI
WHEN 'HB01'. "MODI
P_COMP06 = 'HB0001'. "MODI
WHEN 'HB02'. "MODI
P_COMP06 = 'HB0002'. "MODI
WHEN 'HB03'. "MODI
P_COMP06 = 'HB0003'. "MODI
WHEN '9999'. "muß angegeben werden "MODI
P_COMP06 = '999999'. "muß angegeben werden "MODI
WHEN SPACE. "MODI
WHEN OTHERS. "MODI
IF P_COMP04 CO '0123456789'.
LD_COMP+0(2) = '00'.
LD_COMP+2(4) = P_COMP04.
P_COMP06 = LD_COMP.
ELSE.
P_COMP06 = P_COMP04.
ENDIF.
PERFORM COMPANY(SAPFF10C) USING P_COMP06. "MODI
ENDCASE. "MODI
ENDFORM.

SAP Note 20076 - Unnecessary accesses to table T800X .

Symptom

The database analysis shows many accesses to table T800X.

Cause and prerequisites

The table is not buffered correctly.

Solution
You can change the buffering in your system.

Use transaction SE13 to change the technical attributes of the table:
Recommendation:
Buffering type 'G' (generic)
Number of key fields 3

SAP Note 20071 - Permanent lock after connection termination.

Symptom

R/3 work processes serialize when accessing a particular table.

In V$SESSION_WAIT, the same wait event is displayed for all sessions concerned. The wait event refers to an enqueue, lock or latch, for example:

• enqueue

• library cache lock

• latch free

• row cache lock
  

DDL statements like CREATE INDEX or VALIDATE STRUCTURE (without ONLINE option) fails with ORA-00054.

The situation is static - even after a long time nothing has changed.

Reason and Prerequisites

When an Oracle session holds an enqueue, lock or latch, the associated client process (SAP work process, for example) loses the connection to this session. The cause may be a network problem, for example. The Oracle session may not realize this under certain conditions. Instead, it is still waiting for the next Net8 packages from the (no longer existent) client process. Due to this, other sessions requiring the same lock cannot continue working either. As a consequence, the sessions and client processes serialize for this lock.

Solution

To solve the problem, the hanging Oracle session needs to be cleaned up. This can be done as follows:

1. Restart the Oracle database

The simplest, but often not acceptable solution to this problem is to restart the Oracle database. This stops the hanging Oracle session. If you cannot restart the database for business reasons, you can do one of the following.

2. Set SQLNET.EXPIRE_TIME in sqlnet.ora.

A preventive measure for avoiding the problem is the setting of SQLNET.EXPIRE_TIME in sqlnet.ora, and this parameter is set to 0 (deactivated) by default in the SAP environment. If it is set to a value greater than 0, interrupted connections are cleaned up automatically after minutes. This also corrects the enqueue, lock or latch so that the subsequent sessions can continue working properly. If you set too low, an unnecessary network overhead may occur. If you set too high, an unnecessarily long time passes until the session is cleaned up. A useful compromise may be SQLNET.EXPIRE_TIME = 5, which ensures cleaning up after five minutes.

Note that in the past, with Oracle 8. x or lower, this mechanism also cancelled long-running SQL statements in some cases. Therefore check during the days after activating SQLNET.EXPIRE_TIME whether there are inexplicable terminations with ORA-01013 (see Note 618861).

SQLNET. EXPIRE_TIME only affects connections whose Oracle session is INACTIVE. If the Oracle session has the status ACTIVE, the status is not changed if the connection is broken.

If the problem has already occurred, SQLNET. EXPIRE_TIME can no longer solve it.. This parameter can only prevent similar problems in the future.

3. WINDOWS: TCP/IP configuration:

In some cases, a dead connection from SQLNET.EXPIRE_TIME is not cleaned up (for example, when the session is still active on the Oracle side). In this case, the configuration of a TCP/IP timeout helps on WINDOWS. To do this, define the parameter KeepAliveTime in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, and set this to a value such as 300,000 (->5 minutes). By doing this, the system cleans up dead connections after five minutes.

4. Manual termination of the hanging session

In a first step, determine the session ID (SID) and serial number (SERIAL#) of the session holding the particular enqueue, latch or lock.

As of Oracle 10g, sessions that are currently blocking can in most cases be determined as follows:

SELECT
S2.SID BLOCKING_SESSION,
S2.SERIAL# BLOCKING_SERIAL#,
DECODE(S2.WAIT_TIME, 0, S2.EVENT, 'CPU') BLOCKING_SESSION_EVENT,
S1.SID WAITING_SESSION,
DECODE(S1.WAIT_TIME, 0, S1.EVENT, 'CPU') WAITING_SESSION_EVENT
FROM
V$SESSION S1, V$SESSION S2
WHERE
S2.SID = S1.BLOCKING_SESSION;

Until Oracle 9i, the required steps depend on the wait event:

• enqueue

• Determine the session IDs , , ..., of the sessions that are accessing the affected table :
  
  SELECT SID FROM V$ACCESS WHERE OBJECT = "";
  • Determine the session ID of the session actually holding the enqueue:
    
    SELECT SID FROM V$LOCK
    WHERE SID IN (, , ..., ) AND LMODE = 6;
  • Determine the serial number of session :
    
    SELECT SERIAL# FROM V$SESSION WHERE SID = ;
  • library cache lock

  Note 607944 describes how to determine and <> of the locking session.

  • latch free
  • Determine the name of the latch that (most of) the sessions are waiting for:
    
    SELECT N.NAME FROM V$LATCHNAME N, V$SESSION_WAIT W
    WHERE W.EVENT = 'latch free' AND W.P2 = N.LATCH#;
  • Determine the SID of the session that is holding the latch:
    
    SELECT H.SID FROM V$LATCHHOLDER H, V$SESSION_WAIT W
    WHERE W.P1RAW = H.LADDR AND H.NAME = "";
  • Determine the serial number of session :
    
    SELECT SERIAL# FROM V$SESSION WHERE SID = ;
  • row cache lock
  • Determine the sessions that currently have row cache locks as described in Note 619188. Perform this step several times in a row, and determine the SID of each session that has a permanent lock.

  Make sure that the session holding the lock is no longer connected to any client process. Use the following command to determine the OS-PID and the host of the client process:
  
  SELECT PROCESS, MACHINE FROM V$SESSION WHERE SID = ;

  Make sure that no process with the specified OS-PID is running on the returned host.

  If the client process actually no longer exists, you can terminate the hanging Oracle session as follows:
  
  ALTER SYSTEM KILL SESSION ',';

  If this command returns after some time with the message
  
  ORA-00031: session marked for kill

  , this means that the session cannot yet be terminated. In this case, you can try to hard terminate the corresponding shadow process (UNIX: "kill -9 ", WINDOWS: "orakill ").

  SAP Note 20067 - RPCEFZA0 Fehler beim Zugriff auf Erstattungsanträge .

  Symptom
  

  Der Zugriff auf die Datenbank PCL2, Cluster EF, Erstattungsanträge, schlägt fehl, falls bereits erstellte Erstattungsanträge (aus der Vergangenheit) im Rahmen der Rückrechnung bearbeitet werden sollen.
  

  Weitere Begriffe
  Ursache und Voraussetzungen
  

  Der Zugriff auf die Datenbank PCLx mit Major-/Minor-ID ist im Rahmen der PCLx-Pufferung nicht unterstützt.
  

  Lösung
  Verwendung von IMPORT ohne Nutzung der PCLx-Pufferung.
  
  
  Bitte passen Sie den RMAC-Baustein "RP-IMP-C2-EF-MAJ" an die neuen Gegebenheiten an (Pflege der Tabelle TRMAC) und generieren Sie danach den Report RPCEFZA0.
  
  RP-IMP-C2-EF-MAJ 001 ****************************************
  RP-IMP-C2-EF-MAJ 002 * CLUSTER EF: ERSTATTUNGSANTRAEGE (A) *
  ...
  ...
  RP-IMP-C2-EF-MAJ 011 ****************************************
  RP-IMP-C2-EF-MAJ 012 IMPORT EF-VERSION TO OEF-VERSION *
  RP-IMP-C2-EF-MAJ 013 FORML TO OFORML *
  RP-IMP-C2-EF-MAJ 014 FROM DATABASE PCL2(EF) *
  RP-IMP-C2-EF-MAJ 015 MAJOR-ID OEF-KEY(14) *
  RP-IMP-C2-EF-MAJ 016 MINOR-ID OEF-KEY+14(6)
  RP-IMP-C2-EF-MAJ 017 RP-IMP-EF-SUBRC = SY-SUBRC
  RP-IMP-C2-EF-MAJ 018 EF-VERSION-NUMBER = '00'
  RP-IMP-C2-EF-MAJ 019 IF RP-IMP-EF-SUBRC <> 0
  RP-IMP-C2-EF-MAJ 020 CLEAR: OEF-VERSION, *
  RP-IMP-C2-EF-MAJ 021 OFORML
  RP-IMP-C2-EF-MAJ 022 REFRESH: OFORML
  RP-IMP-C2-EF-MAJ 023 ENDIF

  SAP Note 20060 - MM01: Field "Critical part".

  Symptom
  

  The use of field MARC-KZKRI, "Critical part", is unclear.

  Cause and prerequisites
  

  This is an information field.

  Solution
  The "Critical part" field does not trigger any special function. It is intended for information purposes only.
  Exception: During inventory sampling procedure, critical parts are generally transferred to the complete-count area, see Note 82739 .

  SAP Note 20054 - Clearing of foreign currency documents in local currency .

  Symptom
  

  • Clearing of invoices in foreign currency with payments in local currency does not function properly, as evidenced by unexpected differences in amounts posted. This situation started to appear in Release 2.2, whereas the clearing of such items in Release 2.1 did function properly.

  • In clearing/payment documents booked in local currency, different amounts are shown in the line items if the display is switched between local and document currency. This occurs even though the two currencies are identical.

  Cause and prerequisites
  

  As of Release 2.2, clearing in a third currency is generally possible. The clearing technique was converted for this purpose.
  Up to Release 2.1, foreign currency items could only be cleared in that foreign currency or in the local currency. When clearing in local currency, items were sometimes posted partially incorrectly. This was fixed in Release 2.2.

  Solution
  ************************************************************************
  CAUTION: This note was updated on 4/20/95. As of Release 2.2E, you
  can define how foreign currency document clearings in local currency
  should be carried out. You can select settings in such a way that the
  procedures used in Release 2.1 can be implemented once again.
  You carry out these configurations from the 'Global company code data'
  screen.
  The following explanation of the clearing logic is appropriate for
  Releases 2.2A-2.2D as well as further releases, as long as the company
  code settings remain unchanged.
  ************************************************************************
  Following is a description of the logic for clearing invoices in a third currency. Local currecy is the Deutsche Mark and the invoice currency is the US dollar. Two payment scenarios are given, one is a payment in a third currency (French Franc), and the other a payment in local currency (DM).
  
  Invoice on 4/1/95 of 1000 USD = 1500 DM ( USD/DM rate = 1,50 )
  
  Payment on 5/1/95 of 4900 FF ( USD/DM rate = 1,40
  FF/DM rate = 0,28 )
  
  Since the clearing is carried out in a currency other than that of the
  invoice, it must then be determined how many FF are needed on 5/1/95 to
  settle an invoice of 1000 USD. Following is the result of the conversion:
  
  
  1000,00 USD = 1400,00 DM ( Rate 1,40000 )
  1400,00 DM = 5000,00 FF ( Rate 0,28000 )
  
  In this case, there is an underpayment of 100 FF. You must decide here
  if the difference will be successfully posted or carried over, for
  example, as a residual item. The result is the following posting
  document:
  Document currency FF Local currency DM Update in
  General Ledger
  Incoming payment 4900,00 1372,00 ( 4900,00 FF )
  Customer clearing 5000,00 1500,00 ( 1000,00 USD)
  Underpayment expense 100,00 28,00 ( 100,00 FF )
  Loss from rate fluct. 0,00 100,00 ( 0,00 USD)
  
  If DM 1372 had been paid instead of 4900 FF, there would have been
  no difference between the two postings, because both amounts had
  the same value as of 5/1/95. You would not have calculated how many
  FF would be required to clear 1000 USD here, but rather how many DM.
  On 5/1/95, that would have been DM 1400.
  
  
  Document currency DM Local curr. DM Update in General
  Ledger
  Incoming payment 1372,00 1372,00 ( 1372,00 DM )
  Customer clearing 1400,00 1500,00 ( 1000,00 USD )
  Underpayment expense 28,00 28,00 ( 28,00 DM )
  Loss from rate fluct. 0,00 100,00 ( 0,00 USD )
  
  In contrast to Release 2.1, not the historic DM value (1500), but the current value (DM 1400) is considered as the amount to be cleared. This is the correct way to view the amount because you are dealing with a foreign currency receivable, and any exchange rate losses or gains which may occur need to be eliminated.
  The gain/loss amount is only dependent upon changes which may have occurred in the ratio of the invoice and local currencies at the time the payment is made. Changes in the ratio to the payment currency do not have an effect on this gain/loss amount.
  You will notice that, in the customer clearing line in the example above, the item includes two different DM amounts. The first amount (DM 1400) is not used for updating G/L transactgion figures, but rather the USD 1000 amount is used for this purpose. As of Release 3.0, this amount will also be displayed in the line item on the additional information screen.
  The differences between Release 2.1 and 2.2 then, are particularly evident if you assume a payment not of DM 1372, but of DM 1500. In Release 2.1, this payment could be cleared with the invoice with an amount of USD 1000 (DM 1500 at the time of invoicing). No difference postings were generated.
  This procedure was, however, incorrect. At the time of payment, 1071,43 USD would correspond to DM 1500, and a payment of 1071,43 would result in an overpayment of USD 71,43 (=DM 100). Whether you post this overpayment to the profit and loss, or to the customer account as a residual item, is irrelevant.
  In Release 2.2 an overpayment of DM 100 is correctly recognized, which you must post somewhere (i.e., in the profit and loss or as a residual item to the customer account). The overpayment is represented in the resulting posting document:
  
  Document currency DM Local currency DM Update in
  General Ledger
  Incoming payment 1500,00 1500,00 ( 1500,00 DM )
  Customer clearing 1400,00 1500,00 ( 1000,00 USD )
  Gain from overpayment 100,00 100,00 ( 100,00 DM )
  Loss from rate fluct. 0,00 100,00 ( 0,00 USD )
  
  You then manually post the 'gain from overpayment' item.
  
  The clearing technique described above is used for G/L as well as customer and vendor accounts. This can cause problems if clearing accounts are involved for which a foreign currency posting is typically cleared by a posting in local currency.
  Example: 1000 USD (1500DM) is posted to the debit side of a clearing account and DM 1500 to the credit side. After some time, these items are supposed to be cleared. The clearing should be carried out in USD.
  Since the USD/DM rate has changed in the meantime, the program determines the current value of USD 1000 as DM 1400. The two items cannot be cleared then, because the countervalue to the DM 1500 posting is now DM 1400.
  As of Release 3.0, it is possible to set up the master records for such clearing accounts so that transaction figures will only be updated in local currency. Consequentially, the conversion of the USD amount described above, which is undesirable in this case, is omitted.
  This feature of Release 3.0 cannot be implemented in advance for 2.2 because an enhancement to the G/L master record was involved. It is, however, possible to implement a programming change which allows all G/L accounts to be cleared without undergoing a renewed conversion of the items previously posted in a foreign currency. This programming change is described in R/3 note number 16132.

  SAP Note 20053 - Upgrade from 2.2x to 3.0x .

  Symptom
  

  What is the fastest way for the customer to upgrade from 2.2x to 3.0x?
  

  Cause and prerequisites
  

  None

  Solution
  
  
  *********************************************************
  * Source release: Target release: *
  * 2.2a,b,c,d,e,f,g,h,i 3.0x *
  * ----------------------------------------------------- *
  * *
  * Steps to be taken: *
  * *
  * 2.2a,b,c,d -> 2.2d+ -> 3.0x *
  * *
  * 2.2d+,e,f -> 3.0x *
  * *
  * 2.2g -> 3.0x (x >= C) *
  * *
  * 2.2h -> 3.0x (x >= D) *
  * *
  * 2.2i -> 3.0F *
  * *
  * In DB2 for AIX : *
  * 2.2g -> 3.0C *
  * *
  * 2.2h -> 3.0x (x >= D) *
  * *
  * 2.2i -> 3.0F *
  * *
  * For Microsoft SQL Server: *
  * 2.2e -> 2.2f -> 3.0x *
  * *
  * 2.2g -> 3.0x *
  * *
  * 2.2i -> 3.0F *
  * *
  *********************************************************
  
  
  Please note:
  ************
  
  Operating system upgrade:
  ************************
  * all for upgrade to 2.2d+ (also refer to notes 11764, 11765, 11767)
  
  Database upgrade:
  *****************
  * Oracle (see note 11767)
  * Informix (see note 11765)
  * Adabas (see note 11764)
  * Microsoft SQL Server (see note 39400)

  SAP Note 20048 - Upgrade from 2.1x to 3.0x .

  Symptom
  

  What is the fastest way for the customer to upgrade from 2.1x to 3.0x ?

  Cause and prerequisites
  

  none

  Solution
  
  
  ***********************************************************
  * Source release: Target release: *
  * 2.1a,b,c,d,e,f,g,i,j,j+,l 3.0x *
  * ------------------------------------------------------- *
  * *
  * Single steps enclosed: *
  * *
  * 2.1a -> 2.1d -> 2.2e -> 3.0x *
  * *
  * 2.1b -> 2.1c -> 2.1d -> 2.2e -> 3.0x *
  * *
  * 2.1c -> 2.1d -> 2.2e -> 3.0x *
  * *
  * 2.1d,e,f,g,i,j,j+ -> 2.2e -> 3.0x *
  * *
  * 2.1d,e,f,g,i -> 2.1j+ -> 3.0D *
  * *
  * 2.1j+,l -> 3.0D and 3.0F *
  ***********************************************************
  
  
  Operating System Upgrade:
  *************************
  * OSF/1 during upgrade to 2.1f from OSF/1 1.3 to OSF/1 2.0
  during upgrade to 2.2 from OSF/1 2.0 to OSF/1 2.1
  * AIX during upgrade to 2.1x on AIX 3.2.5
  * all during upgrade to 2.2d+ (see notes 11764, 11765, 11767)
  
  Database Upgrade:
  *****************
  * Oracle during upgrade to 2.1 from Oracle 6.0.36 to Oracle 7.0.16
  during upgrade to 2.2d+ from Oracle 7.0.16 to Oracle 7.1.4
  during upgrade to 3.0x from Oracle 7.1.4 to Oracle 7.1.6
  * Informix during upgrade to 2.2d+ (see note 11765)
  * Adabas during upgrade to 2.2d+ (see note 11764)
  
  
  Please note:
  ************
  
  It is possible to carry out a direct upgrade from R/3 2.1J+ (new database, new operating system) and 2.1L to R/3 3.0D and 3.0F. This makes the upgrade path via R/3 2.2x no longer necessary.
  It is not possible to carry out this direct upgrade from 2.1J+ or 2.1L to R/3 3.0E.

  SAP Note 20046 - Subcontr. order/sched. agreements: reservations not deleted.

  Symptom
  

  "Maintain delivery schedule for subcontractor scheduling agreement" (ME38) or "Create/change subcontract order" (ME21, ME22):
  If several schedule lines were deleted at the same time, only the reservations (for the components, table RESB) of the last deleted schedule line were deleted. If a schedule line was changed and others deleted, no reservations were deleted at all.

  Cause and prerequisites
  

  Program error.
  

  Solution
  The program fix is described below.
  
  You can use report ZZHELP01 (described below) to display/delete the old reservations that should have been deleted. This report selects 1) reservations that refer to no-longer-existing schedule lines and 2) reservations that point to existing schedule lines which, however, point to other reservations. Such a situation can arise when the number of deleted schedule line is re-used for a new schedule line. (Incidentally, this is prevented by the correction in Note 35428). In the list display, you can recognized these reservations by the fact that the reservation number from the schedule line is still shown after the schedule line number.
  REPORT ZZHELP01.
  
  TABLES: RESB, EKET.
  
  WRITE: / 'The following reservations point to a schedule line'.
  WRITE: / 'that has been deleted:'.
  SKIP.
  WRITE: / 'Number Pos. L E Material Date required',
  ' Qty. required Qty. consumed',
  88 'Purch. doc. Item Sched. line'.
  SELECT * FROM RESB
  WHERE BDART = 'BB'.
  CHECK NOT RESB-EBELN IS INITIAL.
  CHECK NOT RESB-EBELE IS INITIAL.
  SELECT SINGLE * FROM EKET
  WHERE EBELN = RESB-EBELN
  AND EBELP = RESB-EBELP
  AND ETENR = RESB-EBELE .
  IF SY-SUBRC NE 0.
  WRITE: / RESB-RSNUM, RESB-RSPOS,
  RESB-XLOEK, RESB-KZEAR,
  RESB-MATNR, RESB-BDTER, RESB-BDMNG, RESB-ENMNG,
  90 RESB-EBELN, 100 RESB-EBELP, 106 RESB-EBELE.
  * DELETE RESB.
  ELSE.
  IF EKET-RSNUM NE RESB-RSNUM.
  WRITE: / RESB-RSNUM, RESB-RSPOS,
  RESB-XLOEK, RESB-KZEAR,
  RESB-MATNR, RESB-BDTER, RESB-BDMNG, RESB-ENMNG,
  90 RESB-EBELN, 100 RESB-EBELP, 106 RESB-EBELE,
  EKET-RSNUM.
  * DELETE RESB.
  ENDIF.
  ENDIF.
  ENDSELECT.
  
  To delete the reservations, please activate the comment line 'DELETE RESB.'.

  SAP Note 20043 - Exchange rate in document header wrong?

  Symptom
  

  The exchange rate displayed in the document header does not correspond to the relationship foreign currency amount/local currency amount in a document item.

  Cause and prerequisites
  

  The exchange rate in the document header is not intended to represent the exchange rate of the document lines.
  The exchange rate in the document header is only intended to show the exchange rate that was used for automatic translations when only one of the two amounts (foreign currency amount or local currency amount) was entered during document entry.
  The task that many users intuitively assume is performed by this field - representing the relation foreign currency amount/local currency amount - cannot in fact be performed by this field.
  The reason for this is that the exchange rate relation can differ from one document item to the next. This is the case, for example, when both amounts were manually entered and different exchange rate relations were used. Another typical example is the clearing of foreign currency documents in which the bank posting, clearing posting, and any residual items or partial payment items were performed at different exchange rates.
  It therefore makes more sense to display the required information at document item level, and not in the document header.

  Solution
  The exchange rate of the item can be displayed in the line item display. This is back-calculated from the foreign currency amount and the local currency amount. Function module CALCULATE_EXCHANGE_RATE is used to do this .
  To display this exchange rate, define a line layout that contains the field 'Effective exchange rate' (field name: RFPOS-KURSE).

  SAP Note 20040 - SAPscript: Wrong symbol values in form windows .

  Symptom
  

  Variable symbols are used in SAPscript layout sets in windows of type VAR or CONST. During the printout or test display on the screen, incorrect values are sometimes displayed for these symbols.

  Cause and prerequisites
  

  The windows of type VAR and CONST only processed at the end of the page, unlike window type MAIN, that is, the text elements of the VAR or CONST type windows are only processed when a page break is reached when filling the main window. Typ VAR oder CONST prozessiert. Especially the variables symbols are only expanded at this time and replaced by their actual value from the print program.
  However, if the print program expects that the variables are replaced immediately when calling a text elements and internally sets its variable differently, this other value is displayed, for example:
  Assume the form text element for window HEADER is:
  /E ELEM1
  * Item indicator: &REGUP-POKEN&
  ..........
  
  and the print program is:
  
  TABLES REGUP.
  
  REGUP-POKEN = 'XYZ'.
  CALL FUNCTION 'WRITE_FORM'
  EXPORTING ELEMENT = 'ELEM1'
  WINDOW = 'HEADER'.
  REGUP-POKEN = 'ABC'.
  ..........
  
  The printout would then be:
  Item indicator: ABC
  
  That is, the value set after WRITE_FORM is displayed.

  Solution
  Three solution are principally possible:
  
  1. Try to move the corresponding text elements into the MAIN window because the display or porcessing in windows of type MAIN is done immediately, that is, with the corresponding function module call.
  
  2. You have to create another variable symbol for each text element. In the above example, you could enhance the Dictionary structure REGUP by field REGUP-POKEN1 which is addressed after WRITE_FORM. Thus:
  
  REGUP-POKEN1 = 'ABC'.
  
  3. For repeatedly used variables, you have to replace the variables in the print program itself to get the desired current value. You can do this with the following function modules for the above example:
  Layout set text element for window HEADER is:
  /E ELEM1
  * Item indicator: &REGUP-POKEN&
  ..........
  
  The print program is:
  
  TABLES REGUP.
  
  DATA BEGIN OF TEXT_HEADER.
  INCLUDE STRUCTURE THEAD.
  DATA END OF TEXT_HEADER.
  
  DATA BEGIN OF FORM_LINES OCCURS 0.
  INCLUDE STRUCTURE TLINE.
  DATA END OF FORM_LINES.
  
  
  REGUP-POKEN = 'XYZ'.
  CALL FUNCTION 'READ_FORM_LINES'
  EXPORTING ELEMENT = 'ELEM1'
  WINDOW = 'HEADER'
  TABLES LINES = FORM_LINES.
  
  "Formatierbreite für Variablenersetzung setzen
  TEXT_HEADER-TDLINESIZE = 132.
  CALL FUNCTION 'TEXT_SYMBOL_REPLACE'
  EXPOPTING HEADER = TEXT_HEADER
  TABLES LINES = FORM_LINES.
  
  CALL FUNCTION 'WRITE_FORM_LINES'
  EXPORTRING HEADER = TEXT_HEADER
  WINDOW = 'HEADER'
  TABLES LINES = FORM_LINES.
  
  REGUP-POKEN = 'ABC'.
  ..........
  
  The printout would then be:
  Item indicator: XYZ
  
  Additional key words
  

  SAPscript, Form, se71

  SAP Note 20031 - ME22, ME32: EM 06007 after order acknowledgment entry .

  Symptom
  

  "Change purchase order" (ME22) or "Change outline agreement" (ME32). If you change an item on the overview screen, then immediately choose the menu option "Header -> Order acknowledgment", enter a number and choose "Copy" (adopt), the error message 06007 ("This function not allowed here") appears.

  Cause and prerequisites
  

  The order acknowledgment dialog box is called up in FCODE_CALL. Then module FCODE is processed. There OK-CODE = SELFCODE is set. The latter is set to AUFB because it was set during LOOP in module CALL_BSTPOS (only if an item was changed). However, the entry with AUFB and control indicator 2 = ' ' does not exist in table T168.

  Solution
  Cf. correction numbers in this note.
  Prior to this the error can be rectified as follows:
  Program MM06EI0R, MODULE RM06E-LABNR:
  
  CLEAR OK-CODE.
  IF SELFCODE = 'AUFB'. "<--- einfügen / insert
  CLEAR SELFCODE. "<--- einfügen / insert
  ENDIF. "<--- einfügen / insert
  CLEAR RM06E-LABNR.

  SAP Note 20029 - Dep. below zero...; Dep. in acquis. year incorrect. .

  Symptom
  

  • The system calculates depreciation below zero, although this is not allowed according to the depreciation key nor by the global specifications at company code level.

  • The depreciation in the year of acquisition becomes incorrect when there are several acquisitions with different asset value dates. In general, the depreciation is too low. In the depreciation trace in the asset value display, you see that depreciation is not calculated on transactions, but on the total base value.
    

  Cause and prerequisites
  

  When the asset class was created, the option for allowing negative APC was selected. This indicator is duplicated in the asset, and is responsible for the calculation of depreciation below zero.
  Changing the asset class does not affect the assets that have already been created.

  Solution
  Using ABAP, set the field ANLB-XNEGA for the affected areas back to its initial value. In addition, you have to switch off the indicator in the asset class for allowing negative APC.
  
  Key words: negative net book value.

  SAP Note 20028 - Line items: Search for amounts in local currency .

  Symptom
  

  In the search for local currency amounts, items may not be found when the number of decimal places is different in the local currency and the document currency.
  

  Cause and prerequisites
  

  Program error

  Solution
  Corrected in Release: 21K, 22E, 30A.
  Advance correction:
  /NSE38, RFPOSFD0, FIND DEZIMALENTABELLE_AUFBAUEN
  FORM DEZIMALENTABELLE_AUFBAUEN.
  ...
  LOOP AT SLBTAB. <-- insert
  READ TABLE DEZTAB WITH KEY SLBTAB-WAERS. <-- insert
  CHECK SY-SUBRC NE 0. <-- insert
  POSTAB-WAERS = SLBTAB-WAERS. <-- insert
  PERFORM DEZTAB_FUELLEN. <-- insert
  ENDLOOP. <-- insert
  LOOP AT CURTAB. <-- insert only 2.2
  READ TABLE DEZTAB WITH KEY CURTAB-HWAE2. <-- insert only 2.2
  IF SY-SUBRC NE 0. <-- insert only 2.2
  POSTAB-WAERS = CURTAB-HWAE2. <-- insert only 2.2
  PERFORM DEZTAB_FUELLEN. <-- insert only 2.2
  ENDIF. <-- insert only 2.2
  READ TABLE DEZTAB WITH KEY CURTAB-HWAE3. <-- insert only 2.2
  IF SY-SUBRC NE 0. <-- insert only 2.2
  POSTAB-WAERS = CURTAB-HWAE3. <-- insert only 2.2
  PERFORM DEZTAB_FUELLEN. <-- insert only 2.2
  ENDIF. <-- insert only 2.2
  ENDLOOP.
  ENDFORM.
  
  /NSE38, RFPOSFS0, FIND VERGLEICHEN
  
  IF SELTAB-KTEXT = 'DMSHB' <-- insert
  OR SELTAB-KTEXT = 'BWWRT' <-- insert
  OR SELTAB-KTEXT = 'SKNTO'. <-- insert
  READ TABLE SLBTAB WITH KEY POSTAB-BUKRS. <-- insert
  READ TABLE DEZTAB WITH KEY SLBTAB-WAERS. <-- insert
  ENDIF. <-- insert
  IF SELTAB-KTEXT = 'BWWR2' <-- insert only 2.2
  OR SELTAB-KTEXT = 'DMBE2'. <-- insert only 2.2
  READ TABLE CURTAB WITH KEY POSTAB-BUKRS. <-- insert only 2.2
  READ TABLE DEZTAB WITH KEY CURTAB-HWAE2. <-- insert only 2.2
  ENDIF. <-- insert only 2.2
  IF SELTAB-KTEXT = 'BWWR3' <-- insert only 2.2
  OR SELTAB-KTEXT = 'DMBE3'. <-- insert only 2.2
  READ TABLE CURTAB WITH KEY POSTAB-BUKRS. <-- insert only 2.2
  READ TABLE DEZTAB WITH KEY CURTAB-HWAE3. <-- insert only 2.2
  ENDIF. <-- insert only 2.2
  CASE N.
  WHEN EINS.
  ...
  /NSE38, RFPOSFP0, FIND POSTAB_ANPASSEN_SUCHE_GROSS
  
  IF SELTAB-KTEXT = 'DMSHB' <-- insert
  OR SELTAB-KTEXT = 'BWWRT' <-- insert
  OR SELTAB-KTEXT = 'SKNTO'. <-- insert
  READ TABLE SLBTAB WITH KEY POSTAB-BUKRS. <-- insert
  READ TABLE DEZTAB WITH KEY SLBTAB-WAERS. <-- insert
  ENDIF. <-- insert
  IF SELTAB-KTEXT = 'BWWR2' <-- insert only 2.2
  OR SELTAB-KTEXT = 'DMBE2'. <-- insert only 2.2
  READ TABLE CURTAB WITH KEY POSTAB-BUKRS. <-- insert only 2.2
  READ TABLE DEZTAB WITH KEY CURTAB-HWAE2. <-- insert only 2.2
  ENDIF. <-- insert only 2.2
  IF SELTAB-KTEXT = 'BWWR3' <-- insert only 2.2
  OR SELTAB-KTEXT = 'DMBE3'. <-- insert only 2.2
  READ TABLE CURTAB WITH KEY POSTAB-BUKRS. <-- insert only 2.2
  READ TABLE DEZTAB WITH KEY CURTAB-HWAE3. <-- insert only 2.2
  ENDIF. <-- insert only 2.2
  CASE N.
  WHEN EINS.
  ...
  
  Key words: RFEPOS00 FBL1 FBL2 FBL3 FBL4 FBL5 FBL6

  SAP Note 20024 - Profit margin display in header condition screen .

  Symptom
  

  Situation:
  You are using several alternative cost conditions in the pricing procedure. All these conditions are defined as statistical prices and use the subtotal = 'B', that is, the last condition not equal to zero determines stock value KOMP-WAVWR.
  Problem:
  When you use formula 018 to display the profit margin as subtotal (profit margin in percent), the display on the header condition screen of the document is incorrect.
  

  Cause and prerequisites
  

  Standard behavior.
  

  Solution
  Solution by using new condition value formulas, for example, 900 or 901 as follows:
  
  * Verrechnungswert
  FORM FRM_KONDI_WERT_900.
  XKWERT = KOMP-WAVWR.
  ENDFORM.
  
  
  * Deckungsbeitrag in %
  FORM FRM_KONDI_WERT_901.
  XKWERT = KOMP-NETWR - KOMP-KZWI5.
  XKOMV-KRECH = 'A'.
  CHECK: KOMP-NETWR NE 0.
  XKOMV-KBETR = XKWERT * 100000 / KOMP-NETWR.
  ENDFORM.
  
  
  Create a new condition type ZZVP (analog to NETW) and include it after the cost conditions with calculation formula 900 and subtotal = '5' (providing it is not already used somewhere else).
  
  All cost conditions coming before that receive subtotal = 'B'.
  
  The next subtotal for the profit margin receives calculation formula 901.
  
  Example in the pricing procedure:
  
  Condition type Frm To Manu Obl Stat Print SbTot Cond Form
  VPRS Cost 1 X B 4
  ZVPR Cost 2 X B
  ZZVP Stock value X 5 900
  Profit margin 901
  
  Please refer also to Note 381348.

  SAP Note 20021 - Inconsistencies in central address administration .

  Symptom
  

  When you print purchasing or sales documents, incorrect addresses are copied from the address administration for plants or sales organizations.
  

  Cause and prerequisites
  

  Inconsistencies in table T001W or TVKO.
  

  Solution
  The address number in table T001W or TVKO may only be used in one plant or sales organization. These address numbers point onto the address in table SADR. An address in table SADR must be unambiguously assigned to one plant or sales organization. You should maintain tables T001W and TVKO via the corresponding Customizing transactions OX10 or OVX5 and not via transaction SM31. You can maintain all addresses in SADR with transaction SAD0.
  Also consider related Note 25182.

  SAP Note 20017 - EAA613: No period determination possible .

  Symptom
  

  When you create a fixed asset, the system displays error message AA613.
  This also applies to posting transactions.

  Reason and Prerequisites
  

  1. Contrary to the fiscal year variant, the assignment rules for period control of the valuation keys are defined as fiscal year-independent.

  2. Contrary to the fiscal year variant, the assignment rules for period control are defined as year-dependent.

  Solution
  

  1. The fiscal year variant of financial accounting is already defined as year-dependent. The assignment rules in assets accounting, however, are not. You must either maintain these assignment rules for each fiscal year manually or call up the function "Generate period rules" in the IMG for Asset Accounting under ->Depreciation -> Period control, that is Transaction OA84.
  
  Note:

  • Up to (incl.) Release 4.6B: Transaction OA84 only displays the values. Only after you save the function are the period rules written in the data base.

  • As of Release 4.6C: The table entries are created if you do not select the 'Test run' switch on the selction screen of transaction OA84.

  2. The fiscal year variant of Financial Accounting is defined as year-independent.
  The assignment rules in
  assets accounting, however, are not.
  Note that you must enter 12/31 for every year of the assignment rules.

  
  In addition, 12/31 of the year before the year when generation is to start must be maintained. Furthermore, you must maintain the 31.12 of the year before the 'Year' as of which you want generation to occur.
  
  Other terms
  

  OA84; construct period control rule; AA613; AA 613;

  Key words: AS01, AS91

  SAP Note 20013 - Assert Failed: "dbinfo()" without parameters .

  Symptom
  

  
  Executing an user-defined or modified ABAP/4 report causes the informix database to crash.
  In the database log file ("online.log file"), the following information can be found for the time of the system crash:
  hh:mm:ss Assert Failed: Internal Error - Segmentation Violation
  hh:mm:ss Who: Session(...) Thread(...)
  hh:mm:ss Results: OnLine must abort
  hh:mm:ss Action : Reinitialize shared memory
  hh:mm:ss See Also: ...
  hh:mm:ss mt.c, line ..., thread ..., proc id ...,
  Unexpected virtual processor,
  termination, pid = , exit = ...
  

  The report responsible contains a call without parameters of the informix function 'dbinfo'(), for example,
  select dbinfo () from

  
  Cause and prerequisites
  

  
  The database crash is caused by the faulty call without parameters of the 'dbinfo ()' function.
  
  There is an error in the informix database software which is managed under 'PTS BUG 28533'.
  

  Solution
  

  
  Characteristics
  The error does not appear in the standard delivery since the 'dbinfo()' function is not called up anywhere without parameters.
  

  Avoiding error:
  Call the 'dbinfo ()' function with the corresponding parameters. To set the 'dbinfo ()' parameters, read the corresponding informix documentation.
  

  Correcting errors:
  Informix version: 7.10 UC2 (DEC)
  7.20.EU3P3 (HP, SUN)
  7.20.EU3P6 (SNI, IBM)

  SAP Version R/3: 2.2D (DEC)
  3.OC (HP, SUN)
  3.OD (SNI, IBM)
  
  Additional key words
  

  
  ASSERT FAILED SEGMENTATION VIOLATION DBINFO
  PTS PTS_BUG PTS_BUG_28533

  
  
  Subscribe to: Posts (Atom)
  Search

  

  Top 10 SAP OSS Notes

  • SAP OSS Notes

    Get the SAP OSS Notes widget and many other great free widgets at Widgetbox ! Not seeing a widget? ( More info )
  • SAP Note 22640 - ABAP/4 query: Add. structures in logical databases

    Symptom: Question: How can structures which are connected to logical databases as an extension be used by ABAP/4 query? Some logical databa...
  • SAP Note 16083 - Standard jobs, reorganization jobs

    Symptom: There are a number of jobs that must periodically run in a live R/3 installation, for example, to delete outdated jobs or spool o...
  • SAP Note 24832 - Pricing rules / TVCPF

    Symptom: Depending on the situation, the system should redetermine conditions or not. For this, a differentiated control is required, for ex...
  • SAP Note 18023 - Jobs EU_INIT, EU_REORG, EU_PUT

    Symptom: What are the jobs EU_INIT (program SAPRSEUC), EU_REORG (program SAPRSLOG), and EU_PUT (program SAPRSEUT), which are automatically...
  • SAP Note 11162 - Invoice split criteria in billing document .

    Symptom From a number of deliveries or sales orders more than one billing document is created. Cause and prerequisites The invoice split ma...
  • SAP Note 25528 - Parameter rdisp/max_wprun_time

    Symptom: The meaning of parameter rdisp/max_wprun_time is not clear. Other terms TIME_OUT, timeout, SY 098, Time limit exceeded, instance p...
  • SAP Note 22559 - BTCI material - Add. costing functions are impossible

    Symptom: Basic data transfer for the material master with standard batch input program RMMMBIM0. The field contents for the additional cos...
  • SAP Note 11104 - PPPR: General note on printing production orders.

    Symptom Lack of knowledge about the general printing procedure in PPSFC. Other terms Print, production order, CO04, CO04N, shop paper printi...
  • SAP Note 28869 - Printout of changes although field not print-relevant

    Symptom: When a field (item or header) is changed in a purchasing document, a change message is generated although the field is non-print-...

  Labels

  \ abap account assignment Allocation authorization book books certification CO controlling areas CPIC download free GA715 help view Help view prior index series javascript:void(0) LIST_ILLEGAL_PAGE Master data ME51 Number Ranges pdf rapidshare release strategy RKCORR01 SAP SAPcomm SAPFAX.DLL SAPLPD.EXE Service submit T800 table unknown

  • ABAP
  • SAP
  • Help View
  • Certification
  • Books

  Latest Posts

  • SAP Note 28869 - Printout of changes although field not print-relevant
  • SAP Note 28866 - Error in logical database VFV
  • SAP Note 28865 - SAPF070: Output diffs for multiple currency accts
  • SAP Note 28862 - Cycle Output: too many spool files/ blank pages
  • SAP Note 28860 - Work center hierarchy, graphic, no organization
  • SAP Note 28858 - Message V1384 when creating cust.ind.requirements
  • SAP Note 28857 - Message V1139 during withdrawal for sales order
  • SAP Note 28854 - Deactivate update program in curr.transl.
  • SAP Note 28857 - Message V1139 during withdrawal for sales order

  Subscribe Enter your email address: Delivered to your inbox instantly

  Articles

  • Home
  • Where to find SAP OSS NOTES?
  • How to implement SAP OSS NOTES?
  • What is SAP OSS NOTES?
  • How to create new SAP OSS Note?
  • Top SAP Downloads