SAP Note 25339 - W501 Creating orders with reference to a contract

Symptom:

Message V1501 is issued incorrectly when creating an order with reference to a contract. The target quantity in the warning does not correspond to the target quantity in the contract.

Cause and prerequisites

Variance in units of measure from the sales unit of measure on order creation.

Solution
Program correction as of 2.1d

Additional key words

Release order

SAP Note 25337 - During settlement to assets FS217

Symptom:

When settling an order or WBS element to an asset, you receive the unjustified error message FS217 "No taxes on sales/purchase are allowed for account & &, & is not allowed."
The error can also occur during settlement of EP managed assets under construction.

Cause and prerequisites

An incorrect tax indicator was determined.

Solution
Please install the following correction.
You have to delete 2 lines of coding, and then generate the program SAPLAMDC.

Additional key words

Transaction KO88, CJ88, MWSKZ, AIBU, AIST

SAP Note 25335 - Abend: Program RK2Rxxxx not found

Symptom:

An abend occurs because Program RK2Rxxxx (where xxxx = the name of your operating concern) cannot be found. (Dump: ABAP/4 runtime error LOAD_PROGRAM_NOT_FOUND).
The abend occurs in the CO document flow display in various transactions, such as VA03 and MB02.

Cause and prerequisites

Controlling area 0001 is already assigned to operating concern S001 when delivered, or you assigned a controlling area to operating concern xxxx which had not yet been generated. The abend occurs due to a program error in the function group KEII.

Solution

If you are not using Profitability Analysis (CO-PA) with operating concern xxxx:

• Delete the assignment of the controlling area to operating concern xxxx (Transaction KEKK).
  

If you are using Profitability Analysis (CO-PA) with operating concern xxxx:

• Generate operating concern xxxx:
  Transaction KEA0, "Change data structures -> Activate structure".

• Then execute the function "Generate environment".

Additional key words

Document display, line item display, accounting

SAP Note 25332 - Net book val.after end.useful life (APC depr.)

Symptom:

When using a depreciation key which depreciates exclusively from the acquisition value (for example, level key GD35, GD70 in the German chart of depreciation 0DE), the book value is not depreciated to zero or to the memo value.

Cause and prerequisites

The past depreciation copied by the SAP System was too small. The respective calculation keys do not have a control for a conversion after the end of useful life.

Solution
Change the calculation key allocated to the depreciation key.
Use transaction AX01 for this if it is a standard key.
Enter changeover method '5' and changeover key '0010' in the calculation key.
For the fixed assets, which are already past the end of useful life, you need to recalculate the depreciation.

Additional key words

AW01 SAPMA03W net book value, depreciation on buildings, building depreciation

SAP Note 25330 - Formula provides incorrect value instead of zero

Symptom:

In a report, a value different to zero is calculated for a formula although the result should have been zero.

Cause and prerequisites

The values of the operands are converted into floating point display for the evaluation of formulas.Small rounding errors can occur here which basically cannot be avoided.In this way, it can happen that figures do not add up to zero after the conversion, although they do in the more exact display.
This can cause the following symptoms:

• If two such values are divided in a formula, the result can assume values different from zero depending on the rounding.

• During addition of very large numbers (more than 15 characters) there may be inaccuracies at the last characters which can be traced back to rounding errors.
  

Solution

• The problem can be avoided by rounding in the formula.
  Example: Instead of (#-#)*100/#

the formula should be defined as follows:
(INT((#-#)*10000))/10000 *100/#
or equally
(INT((#-#)*10000))/(100*#)

• Use a set for the addition instead of a formula line. The total of a set is not calculated as a formula line. There is no conversion in floating point numbers. That is why there can be no rounding errors when using sets.

Additional key words

Report Writer, formula line
----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_FORMULA, SGRW_AMOUNT, SGRW_DATA, SGRW_DOCU_CONS_NOTE
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS

SAP Note 25328 - Translation of standard/application texts

Symptom:

The customer searches for an option to translate standard texts of applications (SAPScript). However, no tool is available for this.

Cause and prerequisites

In the standard translation system, only objects that are relevant for delivery (for example forms) are supported, but not SAPscript texts that are created in the application (for example, material texts).

Solution
The functions you require do not exist in the system. Standard texts can only be translated when you log in in the target language, choose maintainace of the texts again and create the foreign texts there. Pay attention to the code page compatability of the target language with that of your application server.
A translation connection for SAPScript texts is currently (as of May 2000) not planned.

SAP Note 25323 - Imputed costs term.: Locked by same user

Symptom:

The calculation of imputed costs terminates when updating. The message KA133 says that the same user is blocking processing. However, this is not the case.

Cause and prerequisites

More than one cost center is being processed, the update is therefore broken down internally into several steps.
When setting the lock again after the corresponding COMMIT statement, another owner is obviously set (in the new LUW).

Solution
Only call the calculation of imputed costs for smaller cost center groups or install the following correction.

Additional key words

Transactions KSA3, KSA8. Error message KA133

SAP Note 25320 - FCS: Missing transactions OICW; OIEM; OILG; ....

Symptom:

The following Customizing transctions are not found in the FCS:
OICW; OIEM; OILG; OIMC; OIPL; OIPM; OIZ7; OQ41; OQ49; OQÄ2; OS52; OVS0; OVS1; OVS2; OVS3; OVS4; OVS5

Cause and prerequisites

The transaction AD20 was deleted incorrectly in the system.
These transactions are therefore not generated cleanly.
The program SAPMSD20 exists.

Solution

With the transaction SE93, you can create the transaction codes.

Choose the transaction SE93,
Enter the transaction name AD20,
Choose the function Create and the transaction type 'Dialog transaction'.

Enter now the following attributes:
Transaction text matchcode maintenance (for IMG)
Program SAPMSD20
Screen number 99
Check object S_DEVELOP

Choose the pushbutton 'Check object' to maintain the check object. Enter value '03' on the next screen in the field 'ACTVT'. The remaining attributes remain initial. Press the ENTER key to copy the values and save the transaction attributes.

On the next popup, you must enter the development class. You can allocate the transaction to your local, private objects with the pushbutton 'local object'. The transaction will be overwritten with the next update to 3.0A with the original SAP version.

SAP Note 25302 - AS91 Update termination Create old asset

Symptom:

An update termination occurs during old assets data takeover if

1. the asset class does not propose all the depreciation terms that are mandatory for the fixed asset (for example depreciation key)

2. the depreciation areas cannot be displayed on a single overview screen (because of the number of areas or window that is too small)

3. if the last depreciation area of the asset class receives all the necessary parameters

4. if you exit the first overview screen with by pressing ENTER (and not for example with 'Scroll' or 'Cumulative values')

Cause and prerequisites

Program error

Solution
Advance correction: Do not exit the overview screen by pressing ENTER, but with a program function (for example, Scroll)
Advance correction in module MA02SF00, syntax check in program SAPMA02S

Additional key words

SAPMA02S SAPLALTD RAALTD01 AS91

SAP Note 25296 - Final invoice indicator

Symptom:

Despite setting the final invoice indicator (EKPO-EREKZ) during invoice entry (MR01 / MRHR) or in the order item (ME21) in the case of a quantity variance between goods receipt and the invoice, the purchase order is displayed as still to be billed in the various list displays.

Cause and prerequisites

Insufficient documentation and missing functions.

Solution
Setting the final invoice indicator has only caused up to now that the purchase order commitments are reduced. Further information on this can be found in the Controlling documentation in the chapter "Open Items Management".

To display the order item as completely invoiced, you must maintain the GR/IR clearing account via transaction MR11.
Please, in addition, see Note 61227 for purchase orders for which a non-valuated goods receipt is provided.

The program design was changed in Release 3.0F: You can now control via Customizing in Purchasing, if the final invoice indicator should be taken into consideration for the list displays. Please see also the release notes in 3.0F for this.

Additional key words

ME2L, ME2M, ME2N