19.3.11

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

SAP Note 25285 - SLIN: TABLES parameter not used for FORM/FUNCTION

Symptom:

Key word SLIN
During the enhanced program check (transaction SLIN), a warning that a TABLES parameter of a FORM or function module is not used occurs. However, the TABLES parameter is called in the central part of the program.

Cause and prerequisites

For the TABLES parameters of FORMs and function modules, 2 parameters are actually transferred; the header of the table and the table itself.
The warning then occurs if only the table or the header is called in a subroutine.
Example:
'DESCRIBE TABLE itab OCCURS N' accesses only the table.
'UPDATE DDICTAB FROM itab' accesses only the header.

Solution

Program correction.

    1. The table or header should not be transferred via the TABLES interface.
    2. If, for compatibility reasons, the Form/Function module interface cannot be changed, the table or header can be set to used via the fields instruction. Doing so will not increase the size of the program load.
Note:
Using the square brackets [] you can reference the table section with header from an internal table.
If one wants to transfer unstructured tables, you can specify this with the non-TABLES parameters using the predefined category TABLE.

SAP Note 25281 - Usage decision, checking usage decision code

Symptom:

When making the usage decision, the entered usage decision code is not allowed. Error message QV 121.
(usage decision code .. and the code group .. must be inserted)
Affected transactions: QA11, QA12 and QA14

Cause and prerequisites

The check of the usage decision code exclusively referred to the plant of the inspection lot. In the view for inspection type maintenance (V_TQ30), however, you can set that selected sets which are not defined in the plant of the inspection lot may also be used.

Solution
Program correction

Additional key words

Usage decision, selected set

SAP Note 25279 - Suppress error message KA168, KA176

Symptom:

Error message: KA168 Transaction & not allowed for order
KA176 Transaction & not allowed for project
Transactions: KGI2, KGI3, KGP2, KGP3, CJ44, CJ45, CJ46, CJ47, CO43
Program name: SAPMKAZB, SAPMKPZB
Description : You may not want this error message to occur, if the
system statuses 'open' or 'closed', or the deletion flag
or deletion indicator are set in the order or in the
project.

Cause and prerequisites

This function not available.

Solution
The following program change ensures that the above error message is no longer displayed.

Additional key words

Error log, log

SAP Note 25276 - SAP enhancement concept CMOD: Activation

Symptom:

The statement CALL CUSTOMER-FUNCTION is not executed.

Cause and prerequisites
    1. The respective function module must be allocated to a customer enhancement project, the project must be activated (transaction CMOD).
    2. In rare cases, the function group which contains the module is not generated; or the calling program is not generated.
    3. Missing table entries (transport error)
Solution
    1. Check (transaction CMOD), whether the project in question is active.

If the project is inactive: activate it,

If the project is already active: deactivate and then reactivate it.

    2. Regenerate the function group/calling program (the name should be taken from the name of the function exit).
    3. Check whether the corresponding entries exist:

In CMOD, display the components of the project, including respective SAP enhancements as well as their components (function exits, menu options, screen areas).

      a) If only SAP enhancements are displayed, but no components, entries are missing in the table MODSAP (components of the SAP enhancements).

Restore the entries in MODSAP with a further transport, deactivate the project and reactivate it.

      b) If nothing is displayed, entries are missing in MODACT (components of the customer projects).

Delete the project, recreate and reactivate it. (By deletion of the project, any source code already entered is NOT lost.)
Note 12831 contains a check report which lists all inactive function modules in active projects or all active function modules in inactive projects.

Additional key words

CMOD, SMOD, user exits, function exits

SAP Note 25263 - 3.0 FCS - Abend in Settle Consignment Liabilities

Symptom:

Transaction MRKO - Settle Consignment/Pipeline Liabilities.
Enter a chart of accounts on initial screen & F8 to execute. On detail
screen select one line and hit Save icon. Get message "Cancel M8008 -
System Error : Error in routine BLOCK_BUCHEN#4"

************************************************************************
For More information Contact Conor Dowling At (201) 631-9053 or 9054
Our ref SIR 21
************************************************************************
8/9
Is there a fix you can send us so that we can at least test this new
functionality (e.g. we want to test if there is any branch/head office
functionality in this enhancement that is standard in normal invoice
verification. i.e.
Can you direct the payment of SMI liabilities to another
vendor account number that in turn has another vendor number defined
as its head office ? Can you then track/ report in A/P by either
vendor number ?
We require this information before 3.0.a .

Solution
OUR ANSWER 29.08.1995 20:19 Wayne Kaufhold
Connor, Per our discussion I am closing this memo and if there are any further questions we will have a consultant review then foward to W

SAP Note 25261 - No capacity category for scheduling at the work center

Symptom:

Dispatching operation to planning table is not carried out. Protocol message: Capacity category not maintained in the work center for scheduling.

Cause and prerequisites
Solution
Program modification

SAP Note 25258 - Posted ordinary depreciation is not ready for input

Symptom:

During old assets data takeover, the posted ordinary depreciation was not ready for input if the net book value entry was required.

Cause and prerequisites

Program error

Solution
Advance correction in module LALTDO02. The syntax check can only be carried out in the main program SAPLALTD.

Additional key words

SAPMA02S SAPLALTD RAALTD01 AS91 AS92 net book value

SAP Note 25255 - AC301 for consistency check of General Ledger

Symptom:

In spite of a correct definition in the general ledger, various accounts are identified as incorrect during the plausibility check. The message AC301 'Account is not a balance sheet account' occurs.

Cause and prerequisites

The field SKA1-XBILK was stored with a small 'x'. The query, however, was designed for a capital 'X'.

Solution
If the account is defined correctly, you can ignore the message from this check.
Advance correction in program RACKONTO.

Additional key words

General Ledger reconciliation account RACKONTO RACKONT2 OAK4

SAP Note 25251 - FCS: Termination CU65 Perform_confict_generic_type

Symptom:

The program SAPLCUD6 terminates with a runtime error perform_conflict_generic_type during the transaction CU65.

Cause and prerequisites
Solution
see below

SAP Note 25246 - Workflow data flow: multi-line elements now C 255

Symptom:

Symptom

Via the data flow, multi-line container elements in any format in the target container are converted into the format CHAR 255.

Cause and prerequisites

ABAP or the macros of the Business Object Repository (BOR) still do not offer a way to dynamically assign a format to internal tables.

Solution
Solved with the function 'SWA_CONT_ELEMENT_EXTEND' via the BOR macros SWC_SET_FIRST and SWC_SET_NEXT.

SAP Note 25239 - "PARAMETERS_NOT_VALID" if error in conversion

Symptom:

The exception "PARAMETERS_NOT_VALID" is initiated in "SAPLCXOT" if a unit was maintained for a standard value or user field, which has a dimension not equal to time.

Cause and prerequisites

Program error

Solution
Corrected in LCXTKF00.

Additional key words

Scheduling

SAP Note 25237 - Non-storage loc.spec.reservation of batches

Symptom:

If a batch of a material is reserved without specifying a storage location, this reservation is not taken into account in the dynamic availability check for the batch.
This has the following consequence:
If a reservation is only entered with a batch, the reservation is checked for ATP on batch level and on plant level.
If a further reservation is now created on storage location level with batch and storage location level, the ATP is then checked on batch/storage location level and on plant level. The problem consists of the fact that an ATP violation can also occur on batch level, but this is not recognized.

Cause and prerequisites
Solution
If you use the dynamic availability check for batches, please also enter the storage location in addition to the batch in reservations.

Additional key words

non-storage location specific reservation of batches

SAP Note 25236 - MD02,MD03,MD04 Consumption Planning Customer requirements

Symptom:

a) Missing or incorrect consumption of sales order or customer
requirements with planning.
b) The long text for the allocation indicator is not displayed with the
additional data for the MRP element in the MRP display (popup).

Cause and prerequisites

a)
In certain cases offsetting is incorrect if the customer requirements exist as totals records (daily requirements), that is, if "Availability check" is set to 01 ("daily requirements") in the material master (screen MRP 2).
Cause: error in program MM61XVER

b)
Program error in LM61RU01.
The long text was read with a domain that does not exist.

Solution
the problem is corrected in 2.2g.
An advance correction is possible.

SAP Note 25231 - ORA4043 during ORACLE upgrade to 7.1.4

Symptom:

Activities after importing:
When executing the scripts postinst_7016 and/or postinst_7013, the error ORA4043 occurs.

Cause and prerequisites

Error in the guide !
During processing, a 'DROP' is executed on the database objects before these are created. If this did not exist beforehand, the ORACLE error appears:
ORA4043 object does not exist

Solution
These errors can be ignored !

18.3.11

SAP Note 25227 - MD01,MD40: NO-ROLL_MEMORY in planning run

Symptom:

Termination of planning run with NO-ROLL_MEMORY.

Cause and prerequisites

Error in roll area management when starting the Function module DB_COMMIT.

Solution
The problem is corrected in 3.0a.
An advance correction is possible.
A temporary solution involves replacing the call to the function module DB_COMMIT by the ABAP key word COMMIT WORK in materials planning.

SAP Note 25223 - BrBackup:SqlDba not started after Oracle update

Symptom:

If Oracle is updated to 7.1.4 prior to the update from 2.1I to 2.2E, BrBackup 2.0C can no longer be started.

Cause and prerequisites

For 2.1I and 2.2E, there are two slightly different versions of BRBACKUP 2.0C. The older cannot read the changed version string of SQLDBA which now contains "Oracle" in mixed case.

Solution
The customer should download the newer versions of BRBACKUP and the related programs (br*, sapdba) from the CD, or from sapserv3 via X.25. Described in note 12741.

Additional key words

Update with Oracle update to 7.1.4; SQLDBA

SAP Note 25220 - No stock in transit with cross-company purchase orders

Symptom:

When goods issue is posted for a cross-company purchase order (for a delivery with movement type 643), stock in transit is not updated in the receiving plant.

Cause and prerequisites

This procedure was chosen because usually the issuing and receiving companies have to be managed on different computers. In addition, goods receipt in the receiving plant can be posted before goods issue in the issuing plant with this kind of stock transfer, i.e., the corresponding stock in transit would temporarily be negative.

Solution
You can use the reporting function in Purchasing to display the stock quantities in transit.
Starting with release 3.0D, the stock found with cross-company orders in transit is displayed in the stock overview (transaction MMBE) as well as displayed dynamically determined in the plant availability (MB53).

Additional key words

Cross-company stock transport order

SAP Note 25219 - RSBDCREO and parametrization

Symptom:

RSBDCREO and parametrization

Cause and prerequisites
Solution To start RSBDCREO and delete all processed sessions and /or logs use
the following example:
Selection screen of RSBDCREO
Session name * 1.)
Queue ID 0 2.)
Period from (date) 3.)
(time)
to (date)
(time)


or older than (days) 03 4.)
Processed sessions X 5.)
Logs X 6.)
1.)Session name: * is wildcard (all sessions)
HUGO means all sessions with name HUGO
HUG* means all sessions name starting with HUG

2.)Queue ID : don't use !!!!!!
3.)Period : from --> Space means no period defined
from 15.08.1995 09:00
to 29.08.1995 18:00 means period between the two
dates
4.)older than
(days) : 03 means alternativ to 3.)
all sessions older than 3 days (from current date)

PLEASE USE ITEM 3.) OR ITEM 4.) NOT TOGETHER.

5.)Processed sessions : 'X' means delete processed sessions if exist
and corresponding logs .
' ' means no selection of processed sessions

6.)Logs : 'X' means delete logs with no
corresponding session .

FINAL INFORMATION:

...
Caution: for release <= 30C
This report must constantly run alone.
Batch input sessions must not be processed parallel
...

SAP Note 25209 - Inconsistencies of document categories

Symptom:

The document flow, for example, is not displayed completely due to inconsistencies of the document category in the sales and distribution document.

Cause and prerequisites

The document category is stored in tables VBAK and VBUK.
The document category can be incorrect in one of the two tables.

Solution
    1. The cause of the error can be corrected with the following repair.
    2. Incorrect documents can be repaired with the following report.

The report contains 2 functions:

    1. All sales documents can be checked for the consistency of the document category by clicking the function 'LISTONLY'. You do not need to enter a sales document number in this case.
    2. Enter a sales document number to correct a document. The function 'LISTONLY' must not be selected in this case. The correction of a sales document can also be made by selecting the function 'TESTRUN' in test mode.


SAP Note 25207 - Delete company code: Incorrect EM AC048

Symptom:

When deleting the company code in the Customizing of Asset Accounting, the acknowledgement message AC048 occurs 'Company code xyz will be deleted when saving'. In this case, xyz is not the company code to be deleted.

Cause and prerequisites

Program error

Solution
Advance correction: The incorrect error message can be ignored. The company code that is queried in the saving popup is always deleted.
Advance correction in module MA07CF01. The syntax check can only be carried out in the main program SAPMA07C.

Additional key words

OAB1 SAPMA07C

SAP Note 25201 - Cred.Man: incorrect status after updating backorders

Symptom:

After updating backorders, the documents have an incorrect status with respect to credit management.

Cause and prerequisites

Program error

Solution
Corrected in 3.0B and 2.2G with P22K009863 and P22K008834.

Additional key words

Credit management, updating backorders, V_V2, VKM1, VKM2, VKM3, VKM4

SAP Note 25200 - Allocate payment amount when clearing

Symptom:

When you make a clearing for several customer or vendor accounts, a dialog box is displayed requesting you to allocate the payment amount. Here, the entire payment amount does not correspond to the total of the line items to be cleared.

Cause and prerequisites

To be able to send payment notices to business partners, the payment amount occurring for a partner must be determined in every payment transaction. Providing there is only one partner (customer or vendor) involved in the transaction, this is no problem.

If several partners are involved, first the payment amount must be determined and then this amount must be distributed to the business partners.
The payment amount is the total of all the G/L account line items on the accounts that are indicated as 'cash flow-relevant' in the master record.

This amount is compared with the clearing amounts for the business partners. If the totals agree, every partner has paid exactly the clearing amount. If the totals do not agree, the partner has only paid a part of the clearing amount and the payment amounts must be entered in a dialog box.

Example:


Incoming payment bank 990.--
Manual posting to expense account (accepted deduction) 10.--

Only the first account is cash flow-relevant -> Payment amount 990.--

Thus, 500 DEM are cleared for customers 4711 and 4712, i.e. 1000.--
The user must now decide which customer has paid how much (490/500 or 495/495 or 500/490 or ...).


What has been described above often occurs because bank charges are involved and the expenses account has not been characterized as 'cash flow-relevant'. If the customer pays, for example, 1000 DEM and the bank credits 990 DEM of this while withholding 10 DEM as bank charges, then the payment amount is 1000 DEM, but only 990 DEM are determined by the program because the bank account has been characterized as 'cash flow-relevant'.

Solution
If bank charges are the cause of the unwanted dialog box, indicate the bank charges account as 'cash flow-relevant' in the master record.

Additional key words

FBZ1, FBZ2, FBZ3, payment amount, cash flow relevant = SKB1-XGKON
POPUP = Assign payment amount, SAPMF05A, F-26, F-28, OI clearing,
screen 0614

SAP Note 25198 - Group conditions with exclusion groups

SSymptom:

When using group conditions and exclusion groups, the best price is not determined correctly.

Cause and prerequisites

program error

Solution

Correction to program code.

Additional key words

group conditions
exclusion groups

SAP Note 25187 - Fast entry, supplementing required fields

Symptom:

You have added new fields to fast entry variants according to Note 2596. However, you have not entered the external modification groups (group 1) in the reference screen as you did in the standard screen (for example 026 for WERKS). For this reason, you are asked to supplement line items in the document overview although all the required entry fields for the line items were entered on the fast entry screen.

Cause and prerequisites

Modification according to Note 2596.

Solution
Include the modification groups in the template screen (for example, ZZZVF05A 1001) using Transaction SE51. As an example for the usage of the modification groups, you can use the respective standard screen from program SAPVFxxx (for template screen ZZZVFxxx).
For user-defined field from the coding block, transfer modification group 1 from table TCOBF (display table contents using Transaction SE16).
In the template screens ZZZVF05A 1001 and 1002, enter value '001' for modification group 4 (as is done in the standard screen).
After you have saved and generated the template screen, use Transaction FAKP to delete the new field from the fast entry screen, save and activate the screen. Then re-enter the new field in the screen, which causes the fast entry screens to be regenerated.

Additional key words

FAKP, fast entry, SAKOP, F5413, RGUCBFIP

SAP Note 25186 - Customer: "Select all" function for CALL TRANS

Symptom:

If the function for changing or displaying customer master data per 'CALL TRANSACTION' is called, then the program does not react correctly when you choose the "Select all" function.
Although both company code and sales area were entered, only the general data screens and not the company code data screen or the sales area data screen are selected.

Cause and prerequisites

Program error

Solution
Error was corrected for 2.2G. Interim correction possible.

Additional key words

FD02, FD03, XD02, XD03, SAPMF02D

SAP Note 25182 - Inconsistencies due to address transport

Symptom:

Inconsistencies can occur in the target system when you transport addresses between different systems or clients.

A) These inconsistencies can be avoided by taking organizational measures.
B) Inconsistencies already existing can be corrected with a combination of organization actions and clean-uo reports.
This note refers to the transport of Customizing data like plants/branches, sales organizations, company codes etc. with the corresponding address data.

This note only applies up to Release 4.5B inclusive.

Other terms

Address, number range, client copy, client transport, transport, storage location address, customer address, address data
BAS_CUSTOMIZING

Reason and Prerequisites

The address table key is an internal sequential number per system and client. Problems can arise when the same number is assigned to two different addresses in the source and target systems.
The transport does not add the address from the source system to the target system address file, the existing address in the target system (with the same internal number) is "changed", that is, in this case it is overwritten with the data of the transported address and is no longer available.

Example 1:
System A System B
Plant US01 has address number 4711 Plant US01 has address number 4584
Plant US02 has address number 4712 Plant US02 has address number 4711
Plant US01 is changed and transported.
Afterwards both plants in system B point to address number 4711. The address of plant US02 in system B has been overwritten.

Example 2:
System A System B
Plant US01 has address number 4711 Plant US01 has address number 4584
Plant US02 has address number 4712 Plant US02 has address number 4622
Number status: 4850 Number status: 4639
Plant US01 is changed and transported.
Afterwards address number 4711 appears in system B with the address of plant US01 although the number status in system B is lower.
If further addresses are created in system B a short dump with a duplicate record might occur when using number 4711. This does not happen automatically: due to the buffer of the number range it is possible to omit numbers; also, the numbers are used as keys for several different tables.

Normally, addresses of Customizing objects (plant, company code, sales organization and so on) are transported by copying the Customizing data in the maintenance transaction into a transport request. This way, the address data belonging to it can also be copied into the transport request.
In the Customizing maintenance transactions of the extended table maintenance (SM30) a warning message appears referring to the conflicts described in this note containing a checklist for avoiding the problem. This warning message appears for all objects with an address, as long as the client must be recorded or the transport mode is used.
Up to and including Release 4.5 the table keys from the source system, that is the internal numbers used there, are used to transport the address data.

As of Release 4.6 the address data is transported via shadow tables. This avoids conflicts with the transport of internal numbers.
If you have problems in Release 4.6 B/C, refer to Note 385440.

Solution

A) Avoiding by means of organizational actions
B) Error correction

If numbers from the same number range have been used in the source and target clients, the complete error correction needs to be performed as described under B). Otherwise, the measures for avoiding future inconsistencies described under A) are sufficient.

A) Avoiding by means of organizational actions
The easiest way to avoid the problem is to execute the following organizational measure:
When maintaining addresses in various systems and clients, make sure that no two number range intervals for the number range object "ADRNR" overlap.
Address maintenance numbers are generally issued internally via the number range 01, for addresses from customizing objects as well as for most addresses from master and transaction data. The number range 01 must thus be maintained in each client in each system before addresses can be entered.
The number range 10 is only used for transaction data that is not transported (for example addresses in SD documents, which deviates from maintenance data or CpD addresses) and should remain unchanged in the context described here.
To avoid these difficulties, you should change the number range interval in each client in each system, so that no two of these intervals for number range 01 (in various systems/clients) overlap.

Proceed as follows:

    1. Call Transaction SNRO.
    2. Enter the object name "ADRNR".
    3. Choose "Number ranges".
    4. Choose "Change intervals" on the next screen.
    5. Change the number range interval of the number range 01 on the next maintenance screen so that no two intervals in any of the systems and clients overlap.
    6. Save the change. (These changes require a particular authorization).

Example:

System A, Client 001: 0.000.000.001 - 0.049.999.999
System A, Client 100: 0.100.000.001 - 0.149.999.999
and so on.
System B, Client 001: 1.000.000.001 - 1.049.999.999
System B, Client 100: 1.100.000.001 - 1.149.999.999
and so on.
To avoid future interval changes, enough space should be left for future systems and clients.
The number ranges in clients 000 (SAP default values) and 066 (Early Watch) are irrelevant and do not have to be changed.
To all addresses which are created in this client in the current SAP system after the interval change a sequential number is assigned from the new interval as a key.
All address numbers assigned before the change remain unchanged.

Please note: The changes of the upper and lower interval limits described are only possible if the number status is initial, that is, 0.
If the number status is not 0, you can, if you have the required authorization, change the number status as follows:

    1. Call Transaction SNRO.
    2. Enter the object name "ADRNR".
    3. Choose "Number ranges".
    4. Choose "Change status" on the next screen.
    5. Overwrite the status with 0 in the "Number status" field on the next screen.
    6. Save the change.
    7. You must then make the interval limit changes as described. When the number status has been reset to 0, the new interval must not contain the numbers already assigned. The already assigned numbers are the numbers which lie between the lower limit and the number status of the old interval.

Before reseting the number status in the production system make sure that no data can be entered during this time.

Do not change the number status directly before an upgrade; otherwise, the error described in Note 305365 can occur. If the change is nevertheless made before an upgrade, it suffices if you pick a number the normal way; the error described in Note 305365 does not occur then. Problematic case:

If the following two conditions are fullfilled at the same time, you must first clean-up the data before being able to transport data:

    1. Address numbers whose addresses you want to protect from being overwritten were already assigned in this target system client.
    2. Address numbers from the same number range were used in source system clients.

Do not carry out number range changes during the time when conversion RSXADR21 is running prior to the upgrade (if that report is executed; see Note 97032).
Before starting Report RSXADR21, all number range changes have to be finished.

B) Error correction


To correct existing errors please proceed as follows:

    1. As described under A), make sure that the number range intervals of the address numbers do not overlap in any of the systems involved.
    2. In Release 4.0B: Correct the following error:
  • Error in function module ADDR_MAINTAIN_COMPLETE: See Note 113242 (corrected by 4.0B Hot Package 03);
  • Error in function module ADDR_DELETE: See Note 116008 (corrected by 4.0B Hot Package 05).
    3. Make sure that you have the current version of Report RSADRNNR installed in your system. Please note the following:
  • Caution: This report is part of the standard programs but this is often an old version which does not take into account a series of special cases which may lead to follow-up problems Therefore, make sure at first that you have the current version installed in your system.

In any case, as of Release 4.0, compare the version number (is given as source code comment at the beginning of the report) of the correction instructions to the version number in your coding. If your coding does not contain any version number, it is obsolete in any case and must be replaced by the correction instructions.

The Support Package specifications in this note do not apply to Report RSADRNNR!

  • Report RSADRNNR can be implemented via SNOTE. Please note, however, that the old version of the report is not deleted but the new version is just inserted at the beginning of the source code. Therefore, after implementing via SNOTE, manually delete the old program source code using Transaction SE38.

For manually changing Program RSADRNNR using SE38, you need to enter a modification key. In the program source code, search for key word REPORT. You will find two postitions, the first one in line 1 (beginning of new coding) and the second one in line 795, for example, (beginning of old coding). Delete the coding from line 795 until the end. [The second line number depends on the number of lines in the new coding and may therefore vary]. Afterwards, save and activate the changes.

  • If you have user-defined tables that need to be transported containing table fields that refer to addresses in Table SADR (up to Release 3.1I) or ADRC (as of Release 4.0B), you must extend the source code accordingly.
    4. Run Report RSADRNNR in the source system.

Report RSADRNNR converts the customizing addresses already maintained (including the reference in the customizing tables) to a new number interval.

If necessary, you can start the program repeatedly.

The parameter 'Address Number from New Range' has the following meaning:

    • The parameter is set (default):
      For each address number it is checked whether during runtime it is contained in the then valid number range interval.
      The only address numbers that will be converted are the ones that are not contained in the current interval.
      Reason: If the interval was not redefined or not defined as 'without overlap', conflicts with numbers already in the database might occur again. If the interval was defined correctly, an address number can only be contained in the interval when the program has already been run once so that this number does not have to be converted a second time.
      It is noted in the output log of the report how many address numbers were not converted because they are contained in the current interval.
    • The parameter 'Address Number from New Range' is not set:
      It is not checked whether address numbers are contained within the valid range.
      In any case new numbers are drawn from the number range interval which is current during runtime.

The report must run in the source system to have the initial data of all transports cleaned up.

If required, the report may also run in the target system to solve any conflicts existing there - starting it in the target system is not sufficient, however, you also always need to clean up the data that may be imported in other transports from the source system.

    5. Check the customizing addresses and maintain them, if required.
    6. Only after that, new transports with the data to be transported may be created and transported. Report RSADRNNR must run already before the transports are created. For this reason, delete any transports containing customizing addresses already created since they still contain the old address numbers.


In Release 3.0/3.1 the following errors are known and should be corrected before executing report RSADRNNR:

    • If the same address number occurs in SADR and SADRP, the SADR record is not read correctly and thus not converted. This constallation is a data inconsistency. Refer to Note 27846. You can find the corrections in Notes 84893 and 84894.
      Both corrections are implemented as of the following maintenance level:
      3.0D HP 52
      3.0F HP 38
      3.1H correction instruction 84894 as of HP 24, correction instruction 84893 as of delivery 3.1H
      3.1I
    • If the SAPoffice default company address (SOPR-USRADR) is also referenced to in a customizing table that is to be converted, the assigned SAPoffice user addresses are deleted.
      You can find the correction in Note 84895. It is implemented as of the following maintenance levels:
      3.0D HP 52
      3.0F HP 38
      3.1H HP 24,
      3.1I
      If the program RSADRNNR was executed without this correction, the following error message is issued when maintaining the SAPoffice user address: 'User is not entered in the address management'.
      In this case proceed as follows:
    • Start report RSSOUADD (Transaction SO52) to dissolve the link of the SAPoffice users to the old address numbers.
    • Start report RSSOUADR (Transaction SO51) to enter missing addresses in the SAPoffice users from the address management.

SAP Note 25181 - Client copy: Addresses are not copied

Symptom:

When clients are copied without application tables, the addresses for the following customizing objects are missing in the target client:

    • Company codes (Table T001) transaction OX02
    • Address data specific to company codes (T001E) FSAP
    • Plants/Branches (T001W) OX10
    • Org. unit: Sales offices (TVBUR) OVX1
    • Routes: Transport nodes (TVKN) VORD
    • Org. unit: Sales organizations (TVKO) OVX5
    • Org. unit: Shipping points (TVST) OVXD
      Additionally in 2.2 and 3.0:
    • Sales tax group Address OBCM
      Address tax office (T007F) OBCF
      Additionally in 3.0
    • Personnel areas (T500P)
    • Org. unit: Transport scheduling points (TTDS)
Cause and prerequisites

Addresses are stored in the central address file. This file is not copied since it is an application table.

Solution
Please also refer to note 25180.
You can transport the addresses (except for transport nodes) to the target client using the correction and transport system.
To do this, enter the customizing objects concerned in a transport request using the transport function within Customizing in the source client.
Export the transport request.
Log on to the (new) target client and import the transport request with transaction SCC1 (prior to 3.0: execute the report RSCLCCOP).
The copied customizing objects are overwritten by the same versions from the source client. In addition, the associated addresses are copied to the target client.
You have to ensure that the status of the address number range (Transaction SNRO, Object ADRNR, Interval 01) in the target client is not reset to 0 (otherwise the numbers of the copied addresses would be used again later, which would lead to DUPLICATE RECORD run-time errors when inserting in the DB table).
Also refer to note 25182 "Address number range: Several systems or clients".

Additional key words

Address, number range
BAS_OLD

SAP Note 25176 - FCS 3.0 Transaction VCH1 terminates with msg V0102

Symptom:

When calling up transaction VCH1, the program terminates with the following error message :
Flow control: Entry SAPMV13H, A0, is missing in T185V
Message no. 102

Another problem is that the number range for object KONHH does not exist

Cause and prerequisites

Was obviously not delivered

Solution
T185V:
SAPMV13H A0 100 A0 A0
Request screen Batch Allocation Strategy

Transaction SNRO
Object: KONHH
Goto => Number ranges
Add number range =>
01 0000000001 0000999999
Save

SAP Note 25160 - FI-SL allocation: error message GA735

Symptom:

When executing an FI-SL assessment or distribution, the system generates error message GA735 'System error: during currency translation'.

Cause and prerequisites

In Customizing of allocation, the field LCURR (local currency) was not indicated as a dependent field of field BUKRS or RBUKRS (company code).
As a result, this field is not filled during allocation which causes the error in currency translation.

Solution
Call Transaction SM30 and enter View V_T811I.
Choose the corresponding entry for field LCURR and then choose the menu option Extras -> Dependencies.
If the menu option is not available, enter '=ABHA' in OK code.

Make the following entries in the dialog box:

Field Superior to Dependent on
BUKRS 2
LCURR 2

Consequently, field LCURR is indicated as a dependent field of BUKRS.

Additional key words

Assessment, distribution, allocation

SAP Note 25159 - Performance RVV05IVC

Symptom:

Program RVV05IVC take too long to run

Cause and prerequisites

This program repair database inconsistencies and should only be used in exceptional cases. Database indexes are missing for the SELECTs that are made.

Solution
Create database indexes via the fields MANDT and VBELN for the following tables:

VAKGU, VAKPA, VAPMA, VKDFS, VEPVG
VLKPA, VLPMA
VRKPA, VRPMA.

SAP Note 25158 - No decimal places wanted in partial retirement

Symptom:

During partial retirement, the retirement amount and the proportionate values should be determined without decimal places.

Cause and prerequisites

Customer request. This is a modification. It will not be adopted into the standard system!

Solution
Install the following correction in member LAFARU07.
In this case, Releases 2.1 and 2.2/3.0/3.1 must be distinguished.
For Releases 4.0 up to and including 4.5, the modification is effective only for asset retirement postings and transfer postings within the same company code. No modification is available for cross-company code transfer postings.
Separate correction instructions are available for Release 4.6.

Additional key words

Accumulated depreciation, depreciation, roundoff

SAP Note 25152 - New scheduling calendar in CCMS (DB13) ORACLE

Symptom:

As of Release 22F and 3.0A, a new scheduling calendar is delivered in CCMS (Transaction DB13). This Note describes its operation and the most essential new features.

Cause and prerequisites

The previous version of the CCMS scheduling calendar could be used for scheduling database backups.
The redo log backups had to be scheduled on operating system level.

Solution

The CCMS scheduling calendar (db13) has been extended by additional actions.

Basis functions
  • Scheduling new actions
    By double-clicking on an empty line of the current or a future day, you reach the planning dialog. Here, you can enter the start time, if necessary a period in weeks (no specification or 0 weeks means one-time execution), and the action to be scheduled using selection. In addition, an immediate start (additional pushbutton) is possible for the current day - the start time and period are then unimportant. No two actions can be scheduled for exactly the same time. The scheduling dialog can also be accessed via the planning list (see below). Scheduling is immediately effective without any further confirmation.
  • Display of scheduled actions
    Every scheduled action is displayed on one line in the calendar with the time (without seconds) and a short text. The background color shows the status of the action: Calendar background means either action successfully completed, action in the future, or no specification possible (for table analysis and the Next-Extent calculation); red means unsuccessful or not yet completed. More detailed information can be displayed via the planning list (see below). If there are more planning items than calendar lines for a day, you can scroll by double-clicking the '+' or '-' that then appears.
  • Detail display for scheduled actions
    By double-clicking on the header line of a day, you access the planning list. This contains the precise time, the period, a detailed description, the current status (SCHED = planned, OK = successfully completed, ERROR = terminated or still being processed, N.A. = no specification possible), and the specification of whether an action log exists for each scheduling. The following actions can be carried out from this planning list:
    • Change/Edit
      Changing a scheduled action (change of planning time, period, action, parameters) - (only for planning items with the status SCHED).
    • Insert/Add
      Creating a new scheduling (only for current or future days).
    • Delete
      Removing a scheduled action (only in status SCHED). The deletion is immediately effective without any further confirmation.
    • Parameters/Params
      Displaying the parameters used for scheduling. The parameters can be changed via "Edit".
    • Action logs/Protocols
      Displaying the action logs, if these exist.
    • Job logs
      displaying the background job log, if one exists. This log also contains the approximate output of the started external program.
    • Volumes needed/Vols needed
      Displays the required media for actions that require a backup medium.
  • Daily functions
    The pushbuttons in the calendar main screen, "Action logs", "Job logs", "Volumes needed" always refer to all the actions of the selected day. The log information is imported again with "Refresh", for example, this would update an action in the calendar that had just been completed.
List of actions that can be scheduled
  • Database online full backup + archive logs
    Online database backup of all data files with subsequent redo log backup.
  • Database online full backup
    Online database backup of all data files
  • Archive redo log files
    Backup of all archived redo log files with subsequent deletion from the archive directory.
  • Partial online database backup
    Online backup of the data files for a list of tablespaces.
  • Analyze tables in tablespace(s)
    Table analysis for all the tables in a list of tablespaces.
  • Compute and adapt next table extents
    Calculation and correction of the next extent size of all the tables in a list of tablespaces.
  • Check database structure (as of 3.0D)
Logical commands

So-called logical commands are used for scheduling actions. Logical commands are an interface for calling external programs. The external programs brbackup, brarchive and sapdba are called by the scheduling calendar via the logical commands BRBACKUP, BRARCHIVE and SAPDBA. The logical commands can be manipulated via the test mode of function module SXPG_COMMAND_LIST_MAINTAIN. CAUTION: during the first call, you get a security warning with the option to delete all commands (after saving). After deletion, the logical commands must be set up again manually!

Authorizations
The authorization S_LOGCOM_ALL in the authorization object S_LOG_COM is required to execute logical commands. This authorization is contained in the authorization object S_RZL_ADMIN. This profile therefore has to be entered for the user who is to do scheduling in the CCMS calendar (the profile SAP_ALL is not sufficient!).

Dedicated tape unit for redo log backup

For a database backup with a subsequent redo log backup, all tapes must be inserted beforehand. This is possible by using either a tape changer or a dedicated tape unit for the redo log backup. The profile file init.sap unfortunately does not allow any distinction between tape units for data backups and redo log backups. For this reason, the redo log backup gives you the option of entering a special profile file - where a different tape unit can then be entered.

Old scheduling (from <22f)

The previous scheduling should still run. However, the naming convention for background jobs has changed. That means that the old background jobs cannot be deleted with the new calendar (you get the message "No jobs found to delete"). The old background job can then be removed via sm37 (job name: BACKUP*). It is therefore recommended that you delete all scheduling items with the old calendar (see below.) and then create them again with the new calendar.

Old calendar

The old calendar can still be called - but only directly as an ABAP program (via se38 or sa38). The name of the ABAP program is RSDBA000. Background job names between the old and new calendars are incompatible as described above. When changing over, all planning items should therefore first be removed with the old calendar.

Error!
If an existing planning item is changed by editing the parameters, the respective background job is then deleted. This planning item should then be completely deleted and created again. To prevent this, when you make a change you should also change the time by at least one minute. This error is corrected as of release 22G.

Additional key words

CCMS-DBA, DB13, database backup, redo log backup, backup, archive, logical commands, authorization, no_permission


SAP Note 25151 - WM over-picking during complete stock removal

Symptom:

When picking with MM-WM transfer orders from storage types with complete stock removal without transfer back, a picking quantity which is larger than the delivery quantity is confirmed in the delivery item. A change of the picking quantity is not possible.

Cause and prerequisites
Solution
Customizing in WM should be set so that the over-picked quantity is automatically transported back. If this does not work, you can make the following program correction which will not be transferred to the standard system. The following correction allows a change to the picking quantity. Please observe that after you have changed the picking quantity, a transfer order has to be created with the remaining quantity from the shipping interface to the warehouse.

SAP Note 25150 - ME21 CO objects disappear after entry

Symptom:

The account assignment objects entered on the account assignment screen disappear when creating an assigned order item (transactions ME21, ME22).

Cause and prerequisites

Several CO function modules are processed on the account assignment screen, including function module FMCO_WRITE_CASH_FLOW_MM_EKOPI. This function module does not contain any program code. However, the structure COBL is transferred to the import structure I_COBL with the account assignment objects and the export structure E_COBL is allocated to COBL again without the the statement E_COBL = I_COBL being executed. As a result, all the data in COBL is lost.

Solution
Maintain table TRWPR with transaction SM31. Delete the entry that starts with the two key fields BEST and CHECKALL and has function module FMCO_WRITE_CASH_FLOW_MM_EKOPI as the last field. After deleting this entry, the error should no longer occur.

SAP Note 25149 - ME52 Field selection evaluation price

Symptom:

The following errors occur in relation to the evaluation price for a PReq item with non-valuated material:

1. (Release 3.0A to 3.0D only!)
The evaluation price is no longer available for entry when changing the PReq using ME52.

2. (Release 2.2 only!)
If the Preq is included in a release strategy and if a field selection key, which makes the evaluation price into a display field, is connected to the release indicator, then the field is ready for entry when changing the Preq using ME52 in spite of this.

Cause and prerequisites

Program error

Solution
Correction can be made as follows.

SAP Note 25148 - IS-H: Account determination: Entry does not exist

Symptom:

A generated account determination table cannot be maintained because the following message appears: Entry xx does not exist. The entry does, however, exist in the listed check table.

Cause and prerequisites

Incorrect foreign key generation when creating the table.

Solution
Solution consists of taking the foreign key directly: With transaction SE11 (table: Cxxx, where xxx is the number of the account determination table, then press 'change') and the key 'Fields', you access the overview screen of the table fields. Position the cursor on the field for which the entry could not be found and press the key 'For.key'. Now delete the foreign key on the foreign key maintenance screen via the key 'Delete' and then save. Press the key 'For.key' again on the field in question on the overview screen of the table fields and then save again on the foreign key maintenance screen. Now go back (F3) until you can press the key 'Activate'. Do this and leave the transaction.

Additional key words

Account determination table, revenue account determination, check table, generation, 00058

SAP Note 25147 - VF04 : Selection by payer

Symptom:

In the "Maintain Billing Due List" program, it is not possible to select by payer.

Other terms

SAPMV60S, VF04

Reason and Prerequisites

Up to now, the required functions have not been provided by SAP.
The modifications can be used as of Release 2.2C.
Take the following restrictions into account for the following modification proposals:

    • A selection according to sold-to party is no longer possible.
    • No more descriptions for the sold-to party are displayed.
    • If several sales orders with different payers are combined in one delivery, the delivery header contains the payer of the first sales order as payer. A billing index is not created for the different payers of the combined sales orders.
Solution
Only a modification solves this problem. Contact
Consulting for this purpose. See also the attached Note 170183.

The source code corrections described below provide a possible solution.

1.) Change V05IEXIT
2.) Enhance the partner schema for deliveries in Customizing
3.) Change LV05IF0V
4.) Change LV05IFLV
5.) Change screen SAPMV60S 2100
6.) Rebuild the billing index

1.) Change V05IEXIT
Implement the attached corrections.

2.) Enhance the partner schema for deliveries in Customizing
To ensure that delivery-related documents can also be selected when selecting the billing due list according to payer, you must add the partner RG to the corresponding partner role in Customizing for the delivery type to be used and this partner must be flagged as a partner that cannot be changed.
You can do this by following the menu path
Tools->
Customizing ->
IMG ->
Logistics ->
Sales and Distribution ->
Functions ->
Partner Determination.


3.) Change LV05IF0V
Implement the attached corrections.

4.) Change LV05IFLV
Implement the attached corrections.

5.) Change screen SAPMV60S: (transaction SE51, element list )
For the field VBCO7-KUNNR, change the description "Sold-to party" to "Payer".

6.) Rebuild the billing index
To rebuild the billing index for existing documents, you must start the program RVV05IVB.

SAP Note 25144 - Freight conditions for milestone billing

Symptom:

During the partial delivery or milestone billing, condition values are generally distributed by quantity among the different billing documents. For freight conditions, you may not require this standard system behavior. For delivery-related billing (in this case, for freight condition HB00), this note results in the system not distributing the condition values to different billing documents; instead, the system transfers the total value of the header condition to the first item of the first billing document. However, the transfer to the first item is also performed if no milestone billing occurs.

Other terms

Freight conditions, HB00, milestone billing, partial delivery

Reason and Prerequisites

This is the standard system response. This is not an error.

Note that the solution described below is a modification that is not included in the standard system. Therefore, this note is not subject to maintenance and further development (see also Note 381348). Inquiries and problem messages concerning this subject are not covered by Support but are processed by Consulting, which is subject to a separate fee. The solution described here does not claim to be complete and may be unsuitable for some constellations and business processes that may occur. Known restrictions:

    1. This solution works only for condition types with the "Fixed Amount" calculation type. Furthermore, the relevant condition type must be set as a header condition and as a group condition to ensure that the total order value of the condition is correctly added to a billing item.
    2. The first item that is transferred to a billing document should not be free of charge because otherwise, no freight is calculated.
    3. Overdelivery and underdelivery are not covered by the solution described.
    4. The solution described in this note refers only to one specific freight condition.
    5. This solution cannot be used in the case of billing plans, since the determination of the proportional net item value for the billing document would be incorrect.
Solution

Use transaction SE37 to add the import parameter ORDER_NUMBER to the import/export parameters interface of the function module PRICING_COPY in the function pool SAPLV61A.

function pricing_copy.
*"---------------------------------------------------------------------
*"*"Globale Schnittstelle:
*" IMPORTING
*" CURRENCY_NEW LIKE KOMK-WAERK DEFAULT ' '
*" CURRENCY_NEW_DATE LIKE KOMK-PRSDT DEFAULT 0
*" CURRENCY_NEW_LOCAL LIKE KOMK-HWAER DEFAULT ' '
*" CURRENCY_NEW_RATE LIKE KOMK-KURRF DEFAULT 0
*" CURRENCY_NEW_TYPE LIKE KOMK-KURST DEFAULT 'M'
*" CURRENCY_OLD LIKE VBRK-WAERK DEFAULT ' '
*" DOCUMENT_NUMBER_FROM LIKE KONV-KNUMV
*" DOCUMENT_NUMBER_TO LIKE KONV-KNUMV
*" ITEM_NUMBER_FROM LIKE KONV-KPOSN
*" ITEM_NUMBER_TO LIKE KONV-KPOSN
*" MODE LIKE TVCPF-KNPRS
*" QUANTITY_NEW LIKE VBRP-FKLMG DEFAULT 0
*" QUANTITY_OLD LIKE VBRP-LMENG DEFAULT 0
*" VBTYP_NEW LIKE VBRK-VBTYP DEFAULT ' '
-----> ORDER_NUMBER LIKE VBRP-AUBEL DEFAULT ' '
*" TABLES
*" TKOMV STRUCTURE KOMV
*"---------------------------------------------------------------------

    1. Supply this parameter with "vbak-vbeln" in the program LV60AF0F:


013820 *---------------------------------------------------------------
013830 * FORM FAKTURAPOSI_LIEFERBEZOGEN
013840 *---------------------------------------------------------------
013850 * Erzeugen Fakturakopf und -position aus Lieferposition
013860 *---------------------------------------------------------------
013870 * --> LIKP Lieferscheinkopf
013880 * --> LIPS Lieferscheinposition
013890 * <-- XVBRK,XVBRP,....
013900 *---------------------------------------------------------------
013910
....
15820 * Copy conditions and call pricing
15830 if xvbrp-posar ne 'B'.
15840 call function 'PRICING_COPY'
15850 exporting
15860 currency_new = vbrk-waerk
15870 currency_new_date = vbrk-fkdat
15880 currency_new_local = t001-waers
15890 currency_new_rate = vbrk-kurrf
15900 currency_new_type = vbrk-kurst
15910 currency_old = vbak-waerk
15920 vbtyp_new = vbrk-vbtyp
15930 document_number_from = vbak-knumv
15940 document_number_to = beleg
15950 item_number_from = vbap-posnr
15960 item_number_to = xposnr
15970 mode = tvcpf-knprs
15980 quantity_new = vbrp-fklmg
15990 quantity_old = vbrp-lmeng
16000 order_number = vbak-vbeln <--------
16010 tables
16020 tkomv = xkomv.
16030 perform preisfindung using tvcpf-knprs.
16040 endif.

    2. To use the user exit 'userexit_pricing_copy', edit the program RV61AFZA.


<<<<<<<<<<<<<<<< <<<<<<<<<<<<<<<< start of insertion < < << <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
tables: vbfa, vbak
vbrk.

data: begin of zitab1 occurs 20,
aubel like vbak-vbeln,
fkbel like vbak-vbeln,
storno_vorh,
kond_vorh,
end of zitab1.

data: begin of zitab2 occurs 5,
aubel like vbak-vbeln,
end of zitab2.

<<<<<<<<<<<<<<<< end of insertion <<< < <<<<<<<<<<<<<<<<<< < <<<<<<<<<< <<<
*---------------------------------------------------------------------*
* FORM USEREXIT_PRICING_COPY *
*---------------------------------------------------------------------*
* ........ *
*---------------------------------------------------------------------*
form userexit_pricing_copy.

<<<<<<<<<<<<<<<< start of insertion < < <<<<< <<<<<<<<<<<<<<<<<<<<<<<<<<<
data: tabix like sy-tabix,
kond_vorh, rc.

data: begin of zitabkey_a,
aubel like vbak-vbeln,
end of zitabkey_a.

data: begin of zitabkey_b,
aubel like vbak-vbeln,
fkbel like vbak-vbeln,
end of zitabkey_b.

if quantity_old < 0.
quantity_old = - quantity_old.
endif.

* For condition HB00: change distribution to billing
if vbtyp_new = 'M' and
konv-kschl = 'HB00' and
not order_number is initial.

clear kond_vorh.
*konv = konv.

clear zitabkey_a.
zitabkey_a-aubel = order_number.
read table zitab2 with key zitabkey_a
binary search.

if sy-subrc ne 0. " HB00 not yet handled (copied)

read table zitab1 with key zitabkey_a
binary search.

if sy-subrc ne 0. " Flow not yet read

select * from vbfa where vbelv = order_number
and vbtyp_n = 'M'
and stufe = '01'.

clear zitabkey_b.
zitabkey_b-aubel = order_number.
zitabkey_b-fkbel = vbfa-vbeln.
read table zitab1 with key zitabkey_b
binary search.

if sy-subrc ne 0.
* setup table zitab1
clear zitab1.
zitab1-aubel = order_number.
zitab1-fkbel = vbfa-vbeln.
insert zitab1 index sy-tabix.
endif.
endselect.
* are there any cancellation documents?
select * from vbfa where vbelv = order_number
and vbtyp_n = 'N'
and stufe = '01'.
if vbrk-vbeln ne vbfa-vbeln.
select single * from vbrk where vbeln = vbfa-vbeln.
endif.
clear zitabkey_b.
zitabkey_b-aubel = order_number.
zitabkey_b-fkbel = vbrk-sfakn.
read table zitab1 with key zitabkey_b
binary search.
if sy-subrc = 0.
zitab1-storno_vorh = 'X'.
modify zitab1 index sy-tabix.
endif.
endselect.
loop at zitab1.
* does condition HB00 exist?
if zitab1-storno_vorh ne 'X'.

select single * from vbrk where vbeln = zitab1-fkbel.

select * from konv up to 1 rows
where knumv = vbrk-knumv
and kschl = 'HB00'.
endselect.
if sy-subrc = 0.
zitab1-kond_vorh = 'X'.
modify zitab1.
endif.
endif.
endloop.
endif.
* end of setup of table zitab1
else.
kond_vorh = 'J'.
endif.


if kond_vorh ne 'J'.
clear zitabkey_a.
zitabkey_a-aubel = order_number.
read table zitab1 with key zitabkey_a
binary search.
tabix = sy-tabix.
while sy-subrc = 0 and zitab1-aubel = order_number.
if zitab1-kond_vorh = 'X' and zitab1-storno_vorh = ' '.
kond_vorh = 'J'. exit.
endif.

tabix = tabix + 1.
read table zitab1 index tabix.
endwhile.
endif.

if kond_vorh ne 'J'.

read table zitab2 with key order_number
binary search.
if sy-subrc ne 0.
zitab2-aubel = order_number.
insert zitab2 index sy-tabix.
endif.
*konv-kwert = *konv-kbetr.
*********************************************************************
* currency conversion 24.01.1997
*********************************************************************
xkomv = *konv.
if ( currency_new ne *konv-waers and currency_new ne space ).
perform xkomv_kkurs_ermitteln.
*konv = xkomv.
if currency_new ne *konv-waers and
xkomv-kwert ne 0.
xkwert = xkomv-kwert.
if *konv-waers ne currency_new_local.
call function 'CONVERT_TO_LOCAL_CURRENCY'
exporting
date = currency_new_date
foreign_amount = xkwert
foreign_currency = *konv-waers
local_currency = currency_new_local
rate = *konv-kkurs
type_of_rate = kurstyp
importing
local_amount = xkwert
exceptions
no_rate_found = 4.
if sy-subrc ne 0.
*konv-kinak = 'X'.
endif.
endif.
if currency_new ne currency_new_local.
call function 'CONVERT_TO_FOREIGN_CURRENCY'
exporting
date = currency_new_date
local_amount = xkwert
foreign_currency = currency_new
local_currency = currency_new_local
rate = currency_new_rate
type_of_rate = kurstyp
importing
foreign_amount = xkwert
exceptions
no_rate_found = 4.
if sy-subrc ne 0.
*konv-kinak = 'X'.
endif.
endif.
*konv-kwert = xkwert.
endif.
endif.
**********************************************************************
* currency conversion
***********************************************************************
else.
clear: *konv-kbetr, *konv-kawrt, *konv-kwert.
endif.

quantity_old = - quantity_old. " protect against overwrite
konv = *konv.
konv-ksteu = 'E'.
endif.
<<<<<<<<<<<<<<<< end of insertion <<< < < << < < <<<<<<<<<<<<<<<<<<<<<<<<<<<

endform.

3. Generate the program SAPLV61A.

SAP Note 25141 - Class. system: Obj. search SAPSQL_NO_DBTAB_OR_VIEW

Symptom:

Object search (transaction CL30) terminates with the message "SAPSQL_NO_DBTAB_OR_VIEW".
"KKRAMERK" is not in the ABAP/4 Dictionary as database table or view.

Cause and prerequisites

The 'Redundancy' indicator for key KKRAMERK is not set in table TCLT.

Solution
Please compare table TCLT in clients 000 and 051.
'Tools -> Customizing -> Tools -> Table analyses -> Table/view TCLT -> Compare'.

The following entry must exist for table KKRAMERK.

Table Screen no. C Redund. .. ObjID Screen no. C Redund. .. <<
IRLOT 0412 0412
KKRAMERK 0405 X 0405 X
KNA1 0417 0417
LFA1 0415 0415

Additional key words

SAPSQL_NO_DBTAB_OR_VIEW, KKRAMERK, termination

SAP Note 25128 - FI SL: Error message GI722 when installing

Symptom:

Error message GI722 'An error occurred when activating the table GLU1' is displayed when installing a table group in FI-SL.

Cause and prerequisites

When activating the table, you find that the table is used in too many programs and that it therefore cannot be activated.

Solution
Due to the different customer configurations in comparison with the SAP System, the error cannot occur for customers.
If the error occurs in the SAP System, you should try to activate the table directly in the ABAP/4 Repository (also see the long text for the error message).

Additional key words

FI-SL table installation, RGICGLU1

17.3.11

SAP Note 25127 - Parallel server : ORA-600 [1193][6]

Symptom:

Transactions terminate when operating the ORACLE Parallel Server in parallel mode. The ORACLE Alert file contains the following entries:
ORA-00600: internal error code, arguments: [1193], [6]
ORA-09952: scgcmn: lk_open_convert unexpected return: open failed
Additional information: 22

Cause and prerequisites

The parameter setting of the resource parameter of the distributed lock manager is too small and causes the error.

Solution
Stop all instances of the database, stop the lock manager (lkshut) and start it with a higher -r parameter (lkstart).
Notes on lock manager configuration can be found in the file readmedlm.doc in the directory $ORACLE_HOME/pso/doc. You should not make the lock manager parameters unnecessarily high, to keep the memory consumption and startup time within sensible limits.
If the problem occurs during the ORACLE import (imp), you can leave the lock manager parameters unchanged and perform the import in exclusive mode: Stop all instances of the database and restart the database instance via which the import is to run with "STARTUP EXCLUSIVE". After the import, stop the instance and restart the database in parallel mode (STARTUP PARALLEL).

Additional key words

ORA-600, ORA-9952, DLM, Distributed Lock Manager, lkstart
ORACLE 7.1.6

SAP Note 25120 - AS91, unplanned deprec., takeover in fiscal year

Symptom:

During an old data transfer during the fiscal year, unplanned depreciation (or manual depreciation) posted for a calendar period during the year in the previous system is to be transferred for specific areas.
Using AS91, the unplanned depreciation (or manual depreciation) POSTED during the fiscal year can be entered for the area in question without any problems.
The transfer of the also necessary PLANNED unplanned depreciation amount via AS91 - transfer values - movements Transactions 64x, asset value date in the calendar period during the fiscal year is, however, not possible since either error message AA207 (Mty only for special areas ... ) occurs or the area to be posted to is not ready for input.
If the PLANNED unplanned depreciation amount is missing, then the posted transferred unplanned depreciation is cancelled by the depreciation posting program during the next posting run (reversal).

Other terms

Old data transfer AS92,
manual depreciation

Solution
Post the planned value for the posted unplanned depreciation in the calendar period during the fiscal year via Posting - Other with the corresponding Transactions 64x and an asset value date during the fiscal year (or Transactions 60x, 61x, 62x, 63x for manual depreciation).

SAP Note 25119 - Part.funct.contract address as contract req.func.

Symptom:

The partner function 'contract address' is entered as a mandatory function in the Customizing for contracts. When creating a contract (ME31), default values are entered for plant or vendor sub-range in the initial screen. If the system does not find a contract address on this level in the vendor master, then the higher levels (thus without plant/vendor sub-range) are not scanned for possible contract addresses.

Cause and prerequisites

Program error

Solution
Corrected in 3.0A. An advance correction can be made as follows:

SAP Note 25114 - Plan.data interface: INSERT/UPDATE COKS terminates

Symptom:

When using the planning data interface for transactions RKP3, RKP7, RKPW or RKPX, a termination occurs when inserting in or updating table COKS. (Activity-dependent or activity-independent activity input/secondary order cost planning).
In the standard system, the interface is used for copying cost center planning data.

Cause and prerequisites

The error only occurs if a large number of planning records are edited for a transaction so that several documents are created.
Cause: Initialization error in program

Solution
1. Divide the dataset into portions. For example, work with individual
groups instead of all cost centers (KP97).
2. Corrected in 3.0A
An advance correction can be made as follows:

Additional key words

Program name: SAPLKIPL
Transaction: KP97

SAP Note 25110 - Cash sale: Mode of operation

Symptom:

Cash sale does not work INTERNALLY as expected !!!!!

Additional key words

Cash sale

Solution
The following describes how cash sale works.
By cash sale, we mean a business transaction where the customer deals directly with the salesperson, receives an invoice as documentation for the transaction and pays it directly if necessary.
Posting the sales order initiates a delivery. If the customer has already received the goods, this delivery should not be relevant for picking. If the customer goes to a warehouse to pick up the goods, the delivery should be relevant for picking. Even the sending of the goods can be supported via normal delivery processing.
In cases where the transaction goes as expected by the salesperson and the buyer, that is, where the customer receives the goods and is satisfied with them, the transaction can be seen as completed. The goods issue of the delivery should now be carried out in batch (an example of this is contained in note 30672), and billing and transfer to FI is carried out by the billing collective processing.
If the transaction does not run quite so smoothly, then a manual intervention is necessary. If the goods, for example cannot be found in the full amount in the warehouse, the delivery quantity should be changed. If the customer is later dissatisfied with the price because for example, the goods are scratched but the customer still wants them, then the price can be changed in the sales order. In extreme cases, the entire transaction starting with the delivery can be deleted. It is also possible to initiate a subsequent delivery if a part of the delivery is damaged during pickup and replacement stock is not available, but the customer has already paid for the total quantity. If changes are made, a new invoice can be created by repeated printout from the sales order.
The complete transaction, consisting of the sales order and one or more deliveries, can be adapted to the current requirements either by changing the sales order or the deliveries. Only with complete goods issue of the deliveries - which reflects the goods movement really carried out - can the sales order be billed if the order quantity corresponds to the goods issue quantity. Otherwise, the sales order must be adapted so that the delivered and the billed quantities agree.

SAP Note 25106 - FCS - Update program generated twice

Symptom:

When generating the same update definition repeatedly, new update programs are always generated. Usually it is only the program that is created with the first generation that is changed.
If more than one update program is generated for the same update, the key figures can be repeatedly updated.

Cause and prerequisites

The problem only occurs if update definitions are also used in other clients.
The error can be traced to a faulty check on the same update definitions in other clients.

Solution
Correction P30K000776.

Preliminary correction is possible by altering the program.

After including the correction, carry out the following steps to delete the update programs that were generated too many times.

. Created and perform the following correction program (delete the
incorrect program reference):

REPORT .....
TABLES: TMC2Q, TMC2P, TMC2F.

DELETE FROM TMC2Q CLIENT SPECIFIED
WHERE FPROG BETWEEN 'RMCX0000' AND 'RMCX9999'.

DELETE FROM TMC2P
WHERE FPROG BETWEEN 'RMCX0000' AND 'RMCX9999'.

DELETE FROM TMC2F CLIENT SPECIFIED
WHERE FPROG BETWEEN 'RMCX0000' AND 'RMCX9999'.

. In addition, the customer's own update definitions must be manually
regenerated in all of the (!) clients.

Additional key words

Update, update program, generation, doubled, multiple

SAP Note 25099 - Activate SQL trace

Symptom:

An SQL trace is needed for a precise problem analysis.

Solution

Activate SQL trace:

    1. System --> Utilities --> Trace SQL
    2. Click on the button ´Trace on´ and enter the user ID

(It is also possible to enter * as the user ID)
The trace can be analyzed directly via R/3 and the button ´List Trace´.

On UNIX level, the file TRACE000 is created in the directory. /usr/sap//DVEBMGS00/log This file may only be as large as the parameter rstr/max_diskspace allows it to be (default value: 16384000). If the file is filled, recording of the following data records starts again at the beginning of the file (circular record entry). It is therefore occasionally possible that the sections necessary for problem analysis have been overwritten. To avoid this, the trace should be deactivated (with ´Trace off´) immediately after completion or termination of the problematic run (for example, the payment run).

If very large datasets are generated by the trace, increase the size of the profile parameter rstr/max_diskspace. Below, nn specifies the instance number (sometimes also called system number).

On a UNIX system or Windows NT proceed as follows:

    1. Log on as user adm.
    2. Shut down the R/3 System.
    3. Enter the following command to delete the SCSA:
    sapmscsa pf=/usr/sap//SYS/profile/_DVEBMGSnn -r
    alternatively, you can execute the command
    cleanipc nn remove ausführen. Auf NT Systemen muß kein sapmscsa/cleanipc ausgeführt werden.
    4. Increase the value of rstr/max_diskspace in the instance profile
    /usr/sap//SYS/profile/_DVEBMGSnn
    rstr/max_diskspace =32768000 (sample value, should be within the
    framework of the free disk space available)
    5. Restart R/3 and activate the SQL trace as described above.

If problems occur when you delete the SCSA refer to the collective Note 12715.
On AS/400, proceed as follows:

    1. Log on as OFR.
    2. Shut down R/3.
    3. Enter the following command:
    call sapmscsa 'pf = /usr/sap//SYS/profile/_DVEBMGSnn -r'
    4. Increase the value of rstr/max_diskspace in the instance profile
    /usr/sap//SYS/profile/_DVEBMGSnn
    rstr/max_diskspace =32768000 (sample value, should be within
    the framework of the free disk space available)
    5. Then enter the following command:
    call sapmscsa 'pf = /usr/sap//SYS/profile/_DVEBMGSnn-n'
6. Restart the R/3 System and start the SQL trace as described above

Additional key words

ST05

SAP Note 25097 - Inc. characteristic values in control recipes

Symptom:

Process instruction characteristics can sometimes have incorrect values in process instructions and process messages. For the characteristic PPPI_PHASE_STATUS, for example, the value '00001' should be processd in the control recipe, but instead the language-specific description 'Gestarted' (logon language German) or 'Started' (logon language English) is processed. This incorrect characteristic value causes errors when processing the control recipe in the process control system or for process messages.

Cause and prerequisites

The error is caused when valuating in the master recipe. The language-independent internal characteristic value is not internally processed.

Solution
In a temporary solution for Release 3.00 (FCS), the internal values are processed in the master recipe. This does not apply to the process order which displays the language-specific description in the user interface but processes the correct internal value internally. This solution will also be available for the master recipe as of Release 3.0A.
The correction can be picked up from sapserv3 (internal transfer order P30K000750). It can be found in the directory /dist/permanent/Note.0025097. Note 13719 describes how to import a correction from sapserv3 into the customer system.
Caution: This correction can only be used by FCS customers and may no longer be used as of Release 3.0A! !! !

Additional key words

Process instruction characteristics

SAP Note 25092 - Material component sorting in production order

Symptom:

The material component sorting in the bill of material, the production order and the list for the goods issue for the production order is not the same.

Cause and prerequisites

Different sort criteria.

Solution
    1. The sorting of the components in the bill of material is carried out according to item number and material number.
    2. The sorting of the components in the production order is carried out according to the following operation. Within the sequence and operation, the components are displayed in a single-level BOM display (not a structure display !!!). The following example makes this clear.

Structure display of the bill of material:
O. Finished product F1
1. 10 Component R1
1. 20 Phantom assembly D1
2. 10 Component R11
2. 20 Phantom assembly D2
3. 10 Component R21
2. 30 Component R12
1. 30 Component R2
1. 40 Phantom assembly D3
2. 10 Component R31
Structure display as single-level BOM in production order:

*... all componenten on level 1, which are not phantom assemblies
10 Component R1
30 Component R3
*... all phantoms on level 1 with components which are not phantoms
20 Phantom assembly D1
10 Component R11
30 Component R12
40 Phantom assembly D3
10 Component R31
*... all phantoms on level 2 with components which are not phantoms
20 Phantom assembly D2
10 Component R21
*.... all phantoms on level 3 ..... etc.



The components in the production order all receive the same reservation number and a consecutive counter. This counter is assigned regardless of the displayed sequence of the components.
It is not possible to consider the sorting during the counter allocating because all counters would possibly have to be reassigned for certain order modifications, and therefore a DELETE and an INSERT would have to be carried out for each reservation in the database.

    3. The material provision list and the goods issue slips are sorted in the standard by sequence, operation, storage location, and reservation item. The printed reports can, however, be modified easily in order to obtain another sorting.
    4. During the goods issue for the production order, the components in transaction MB1A are listed according to the sequence of the reservation; that is, without considering the sorting in the production order. Theoretically, it would be possible to sort the list in this transaction exactly the same way as in the production order. This sorting, which also means an additional system load, is not yet implemented in the standard R/3 system.
    5. In transaction COGI 'Rework backflushed items', the materials to be withdrawn are also displayed in unsorted order.

    In Release 3.0, it is possible to restrict the withdrawals list according to plant, material, order category, order number, error document, movement type or sales order number.

SAP Note 25091 - Performance improvement for creating process order

Symptom:

Bad performance for texts with a lot of process characteristic texts.

Cause and prerequisites

Performance improvement for creating process order
Texts for process characteristics are no longer copied during
creation, but only in the update program. This reduces dialog.
(For a large number of texts, particularly when working with process
instruction sheets: decisive improvement!)

Solution
CORRECTION IN P30: P30K000773
This applies only to the First Customer Shipment. In 3.0a this is
already corrected!

The data file and cofile of transport P30K000773 are now in the list
/dist/permanent/Note.0025091 on sapserv3.

To implement, please refer to note 13719.

SAP Note 25090 - Update term.coll.conversion plan.order->process order

Symptom:

Update termination occurs when converting planned orders into process orders for all except the first order.
Duplicate Records in CO_BR_AFFX_POST

Cause and prerequisites
Solution
Correction in P30: P30K000773
This applies only to the First Customer Shipment (FCS). In 3.0a this
is already corrected!

Data file and cofile from transport P30K000773 are now in the list
/dist/permanent/Note.0025091 on sapserv3.

To implement this, refer to note 13719.

Additional key words

COR8, process order

SAP Note 25089 - CAD function library for MS Windows

Symptom:

Customer has missing SAP CAD function library under MS Windows. Customer cannot find software on CD.

Cause and prerequisites

not yet delivered on CD.

Solution
The SAP CAD function library for MS Windows and Windows NT will only be delivered on the SAP-GUI CD as of Release 3.0B. Until then, if you have any queries contact: Ernst Berger or Andreas Hauser at SAP Walldorf.

SAP Note 25088 - KS01: Intervals not joined, CoCde missing

Symptom:

    1. When you create another cost center interval which directly borders on an existing one, the intervals are not grouped even if the existing interval was used as a reference and no manual changes were made before saving. A check for the table CSKS with SE16 shows that the field company code is empty in the new interval.
    2. Cost centers without company code assignment. The creation is as described above.

Because of this problem it is possible that the following termination occurs in systems with Release 3.0 and later:
ERROR_IN_COIOB in program LKALPF20, FORM routine GET_ORGUNITS_FROM_COIOB.
In this case, execute only the attached report ZKCORR04.

Additional key words

Key words:
master data, cost center, interval, analysis period, company code, controlling area

Program: SAPMKMA1
Transaction: KS01

Cause and prerequisites
    • There is a 1:1 allocation of controlling area and company code, or cross-company cost accounting is used. However, only one company code is currently allocated to the controlling area.
    • The newly created cost center interval does not correspond to a posting period according to the fiscal year variant.
Solution

Correction for Release 3.0A
The error does not occur anymore as of Release 2.2I since another FORM routine is used there.

You can also use correction report ZKCORR04 for Release 4.0.

For Release 2.2A to 2.2H, you can implement the correction in advance as follows.
Procedure:

    1. Implement the correction.
    2. Execute below report ZKCORR04 to correct the wrong cost center master data.

You need not implement the note if you have already implemented Note 48183 or 30977.
**********************************************************************
REPORT ZKCORR04 .

TABLES: TKA01, TKA02, CSKS.


PARAMETER TESTRUN LIKE KREO-TESTLAUF DEFAULT 'X'.

DATA: BEGIN OF KOKSTAB OCCURS 20,
KOKRS LIKE TKA02-KOKRS,
BUKRS LIKE TKA02-BUKRS,
END OF KOKSTAB.

DATA: BEGIN OF BUKRS_TAB OCCURS 20,
BUKRS LIKE TKA02-BUKRS,
END OF BUKRS_TAB.

* Read all controlling areas
SELECT * FROM TKA01.

MOVE-CORRESPONDING TKA01 TO KOKSTAB.
APPEND KOKSTAB.

ENDSELECT.

* Read company codes for controlling areas
LOOP AT KOKSTAB.

CLEAR BUKRS_TAB.
REFRESH BUKRS_TAB.

SELECT * FROM TKA02 WHERE KOKRS = KOKSTAB-KOKRS.
BUKRS_TAB-BUKRS = TKA02-BUKRS.
APPEND BUKRS_TAB.
ENDSELECT.

DESCRIBE TABLE BUKRS_TAB LINES SY-TFILL.

IF SY-TFILL = 0 OR
SY-TFILL > 1.
DELETE KOKSTAB.
ELSE.
READ TABLE BUKRS_TAB INDEX 1.
KOKSTAB-BUKRS = BUKRS_TAB-BUKRS.
MODIFY KOKSTAB.
ENDIF.

ENDLOOP.

* find missing lines in DB-table CSKS
LOOP AT KOKSTAB.
WRITE: / 'Scanning controlling area ', KOKSTAB-KOKRS, ' ...'.

SELECT * FROM CSKS WHERE KOKRS = KOKSTAB-KOKRS
AND BUKRS NE KOKSTAB-BUKRS.

WRITE: / ' cost-center', CSKS-KOSTL.

IF TESTRUN = 'X'.
WRITE 'not modified (test run)'.
ELSE.
CSKS-BUKRS = KOKSTAB-BUKRS.
UPDATE CSKS.
WRITE: 'modified with company-code ', KOKSTAB-BUKRS.
ENDIF.

ENDSELECT.
IF SY-SUBRC <> 0.
WRITE: / ' no inconsistencies found.'.
ENDIF.

ENDLOOP.

SAP Note 25082 - Bill/exch.due date for calc.of interest on arrears

Symptom:

If the "Bill of exchange payment possible" flag is set for the calculation of interest on arrears, interest should be calculated up until the bill of exchange due date. The system, however, calculates interest up until the clearing date of the invoice.

Cause and prerequisites

Program error

Solution
Coding

SAP Note 25080 - Key for investment measure cannot be deleted

Symptom:

Once a key has been stored in the asset master record for a capital investment measure, it can no longer be deleted even if no postings have been made for capital investment measures.
The error can occur only if you do not use a separate subsidy area for the capital investment support.

Cause and prerequisites

Program error.

Solution
Bypass correction:
Manage the capital investment measure in a separate investment support area.
If you do not want to do this, you can install the following correction in program MA02SF01:
Error corrected as of Release 2.2G/3.0A.

Additional key words

AS02 AS92 Master record Investment key

SAP Note 25079 - Only last page and/or comments in export

Symptom:

A report is exported to the presentation server. The exported file is empty or only contains the last page and/or the comments.

Cause and prerequisites
    1. The report does not contain a title page but has a last page or a comment.
    2. It is exported to the presentation server (output medium '2') in table format (output format '1').
Solution
Insert the line marked with "H25079 in program include FGRWFE10. Generate all affected report groups again afterwards.

Additional key words

Report Writer, download, Excel, exporting

SAP Note 25073 - Address for ISO codes

Symptom:

We are looking for a contact address for ISO codes.

Cause and prerequisites

The SAP references ISO codes, for example, countries and currencies, in many places

Solution
Information on ISO codes can be acquired from the following address in Belgium:

BE/EB Secretariat
CEC-DG 111-Unit B5
200 Rue de la Loi
B-1049 Brussels
Telephone: +32 2299 0250

You can then request the most current information on ISO standardization.

Additional key words

ISO codes, country codes, currency keys

SAP Note 25072 - Rough-cut planning profile: Capacity requirements

Symptom:

When scheduling the orders via a rough-cut planning profile, no capacity requirements are written.

Cause and prerequisites

Program error

Solution
Correction in LCXTKTOP, LCXTKU04

SAP Note 25071 - Parallel update programs block each other

Symptom:

Description:
When making or canceling an allocation, all parallel update programs are filled but they all block each other in their execution sequence.


Result:
Update program 2 waits for update program 1; update program 3 waits for update program 2, and so on


Transactions:
KSV5, KSU5, KSVB, KSUB, KSW5, KEU5, GA15, GA35, GA2B, GA4B


Program name:
SAPMKGAL; ALxxyyyR

Cause and prerequisites

The lock situation is a result of updating table T811C, where the last person changing and the change date of the cycle is updated.

Solution
The following program corrections can be installed in your system as an immediate correction. It stops table T811C from being updated. Since the information stored there is not used operatively, this change is not critical.

Additional key words

Allocation

SAP Note 25065 - Reporting points: Wrong controlling area for plant

Symptom:

In repetitive manufacturing when reporting points are used, the controlling area for a plant cannot be correctly found. The company code is used as the controlling area.

Cause and prerequisites

Function module CO_RM_COMPANYCODE_FIND is used to determine the controlling area for the plant. However, it supplies the company code, so the value of the company code is used for the controlling area. Occurs in function group RMRT in the following function modules:
RM_REPORTINGPOINT_POST
RM_REPORTINGPOINT_REDUCE
RM_REPORTINGPOINT_ADJUST
RM_REPPOINT_STRUCT_CHANGE
RM_REPPOINT_STRUCT_DELETE

Solution
Function module RM_KOKRS_TO_PLANT_FIND is used.
Repair in S11 on 8/24/95 for version 30A : Number S11K154398.
In version 300 (FCS) the error still occurs.

SAP Note 25064 - Date posted depreciation cannot be maintained

Symptom:

During the migration from R2 to R3, the date for depreciation already posted during the fiscal year is not set in table T093D. or cannot be maintained. The depreciation of period 01 is therefore posted during depreciation posting.

Cause and prerequisites

The date of the fiscal year-end is set as the old assets data takeover date in fixed asset customizing. Therefore, this cannot be maintained.

Solution
Please specify an old assets data takeover date during the fiscal year. The system then displays the field for the date of the posted depreciation for every depreciation area to be posted.
Example
If you have a normal fiscal year-end on 12/31/1994, the field for takeover during the fiscal year is not displayed. Therefore, specify a date during the fiscal year, for example, 07/31/1995 --> The field for the posted depreciation can then be maintained.

Additional key words

Depreciation posting RABUCH00 old assets data takeover

SAP Note 25059 - Update term.for LEINUU05 SAPSQL_ARRAY_INSERT_DUPREC

Symptom:

ME42 occurs in SAPLEINU, LEINUU05
"SAPSQL_ARRAY_INSERT_DUPREC" in ME_UPDATE_DOCUMENT
INSERT SADR FROM TABLE DB_SADR.

Cause and prerequisites

Missing number range after clientcopy or release upgrade
The number range counter of address administration does not have the latest status.

Solution
Determine the status of number range counter in the old system with transaction SAD0. Correspondingly raise the number range counter via Customizing or transaction SNUM.

Additional key words

SAPMM06E, error message 00671, ME_CREATE_DOCUMENT

SAP Note 25044 - Problem with table MCNV in Rel. 3.0 (FCS)

Symptom:

1. A135(CZ): Error reading table TMCNV, RC = 04
The entry for editing the material number is missing in the
corresponding client.
2. Runtime error if you call up view V_TMCNV.
3. Calling up transaction OMSL results in the message that the table is
client-independent.

Cause and prerequisites

In Rel. 3.0, table TMCNV is client-dependent; however, it is delivered only in one client (SAP Customizing client) with the result that a corresponding table entry is missing in the other clients; in addition, the client is not contained in the relevant view V_TMCNV.

Solution
1. Modify view V_TMCNV
Transaction SE11:
Object name: V_TMCNV
Dictonary objekt: View
-> Specify and press the pushbutton.
-> On the "Change view (attributes)" screen, press the
pushbutton.
-> On the "Change view (fields)" screen, please insert a new
field:

TMCNV MANDT MANDT <<< Insert
TMCNV CONVID CONVID
TMCNV LMATNR LMATNR
TMCNV MASKE MASKE
...

Then save and activate the view.

2. Supply table TMCNV with entries in the individual clients.
Transfer program ZMATCONV to your system and run this program to
create an entry in table TMCNV in each client:

report zmatconv.

tables: t000, tmcnv, *tmcnv.

select * from tmcnv client specified
where mandt = '000' "client where a table entry TMCNV exists
and convid = 'MATCONV'.
select * from t000.
clear *tmcnv.
move-corresponding tmcnv to *tmcnv.
move: t000-mandt to *tmcnv-mandt.
insert *tmcnv.
if sy-subrc is initial.
write: / 'table entry insert - client', t000-mandt.
else.
update *tmcnv.
if sy-subrc is initial.
write: / 'table entry update - client', t000-mandt.
else.
write: / 'update error - client', t000-mandt.
endif.
endif.
endselect.
endselect.

Additional key words

SE11, OMSL, conversion exit MATN1