SAP Note 27640 - Batch determ. for individual stock for sales order

Symptom:

You want to carry out a batch determination for batches of an individual stock for sales order in the delivery.
This batch determination gives no result although the batches are classified.

Cause and prerequisites

The batch determination in Release 3.0 does not consider special stocks. Only the normal warehouse stocks are considered.

Solution
When you call the batch determination in the delivery, a check is made now whether a special stock indicator is set.

Additional key words

Batch determination for batches of an individual stock for sales order in the sales order.

SAP Note 27637 - FF716, tax group, missing tax statements

Symptom:

- Missing tax statement lines (BSET),
- incomplete check of the control information,
- Termination FF716 'Error in allocating the tax group',
if:
the tax calculation is performed using the jurisdiction codes and the entered document contains more than 16 different combinations of tax code/jurisdiction code.

Cause and prerequisites

The check of the taxes and the transfer to the tax statement table (BSET) is carried out by processing the control data screen in the background and checking the relationship tax base - tax amount line by line (for each combination MWSKZ/TXJCD). This screen only contains 16 loop lines and scrolling was not supported up to now.
If the taxes should be calculated, the error does not occur because the entire table of the entered initial amounts is then looped.
Due to the fact that scrolling was not possible on the entry screen for tax amounts, no entered information is lost. In the worst case, tax statement lines for a 0% tax amount were not generated.

Solution
Organization: Make sure that there are no more than 16 different combinations of 'tax code/jurisdiction code' in one document (split the document if necessary).
Scrolling can be performed on all tax screens as of 2.2G
Advance correction: please insert all the lines indicated by correction P22K009905. Also make the following change to the user interface for program SAPLTAX1:
in statuses 0300, 0600 and 0650, include the functions 'P+ Next page' and 'P- Previous page' in the menu option 'Goto' in each case. In the function key assignment, please set P- to 22 and P+ to 23. P+ and P- already exist in the function list, but they must not have the category 'E' (please set to 'blank'). Generate the user interface afterwards.

Additional key words

FB01, SAPLTAX1, TTXJ, TXJCD,TTXD

SAP Note 27636 - Message: Condition exists (removed manually)

Symptom:

A condition is unexpectedly not found in pricing.
Pricing analysis issues the message:
"Condition record exists (removed manually)"
or
"Condition record exists, however, was not stored"
although the condition was not removed manually.

Cause and prerequisites

The pricing analysis works as follows:

• First, a complete new pricing is carried out,

• the outcome of which is then compared with the conditions defined until then in the document.

If this new pricing now finds a condition, but this condition was not previously set in the document, then the above message appears.
This can have the following causes:

1. The condition was deleted manually on the item condition screen

2. The condition record was only created afterwards. Note, in this case, that order processing and pricing have buffer techniques. This has the effect that a newly inserted condition record can, in certain cases, only be found after completely leaving order processing and then accessing it again.

3. During the insertion of an item, different key fields are used to access the condition record than at the time of the change.
The conditional check can also give different results at the time of the insertion and at the time of the change. Until now this has happened in connection with the use of USEREXIT_PRICING_PREPARE_TKOMK (TKOMP) in MV45AFZZ or RV60AFZZ.

4. In billing (or when copying sales orders): certain condition types were not determined in the source document (this is normally controlled by pricing conditions). When creating the document, a pricing type is used via the document flow (TVCPF,TVCPA) which does not determine these condition types anew, although they should be read via the requirements.

Example: Invoice list conditions are not used in the sales order.
If the billing document is now created with pricing type
D or A then these are missing in the billing document,
even though they should be there.

5. The condition is specified as an interval scale (scale type D), but
it does not come up to the scale quantities.

6. If a sales order is created externally that is, for example, via EDI in an R/3 system, make sure that at the time of pricing all required fields are filled for the access of condition records. Example: The above error message is displayed for VAT and freight conditions. Cause: The flow logic of the IDoc was defined in such a way that fields VBAP-WERKS and VBAP-LGORT are only supplied after the execution of item pricing. However, in general, both fields are required for the determination of tax and freight conditions.

7. For displaying special constellation during bonus determination in connection with legal VAT increases, Note 96352 has been installed in the system. This influences, via USEREXIT_PRICING_RULE, the work method of the pricing type 'G' as listed below:

FORM USEREXIT_PRICING_RULE.
...
IF ( KOMK-VBTYP CA VBTYP_ANFO OR KOMK-VBTYP CA 'H' ) AND
KOMK-KNUMA IS INITIAL AND
NOT KOMP-VGBEL IS INITIAL.
STEU-KNPRS = 'G'.
STEU-KOAID = 'C.........'.
APPEND STEU.
ENDIF.

The note in question has been withdrawn by SAP because it had negative side effects on copied/referenced documents during the determination of tax conditions (condition class = 'D'). As of Release 4.0A, the pricing type 'I' is available in the standard system for displaying the required system behavior.

Additional key words

VE008, VE108, Condition screen

SAP Note 27635 - Endless loop during generation of sets

Symptom:

When you generate a set, runtime error STACK_VALUE_TOO_LARGE occurs in FORM pool SAPLGSGE, Include LGSGEF20, FORM routine UPDATE_HIGHER_OBJECTS. This runtime error can also originate from routines READ-T800S or MODIFY-T800S in FORM pool SAPFGSB3 (Include FGSB0E01).

Cause and prerequisites

An incorrectly created usage list for a set leads to a recursive call of UPDATE_HIGHER_OBJECTS in an endless loop.

Solution
Please make the following correction in LGSGEF20 (insert the statements indicated with '<-- insert --'). As of Release 3.0B, another solution will be available in the standard system.

Additional key words

Function modules G_SET_GENERATE, G_GENERATE_BASIC_SET, G_GENERATE_SINGLE_SET, G_GENERATE_DATA_SET, G_GENERATE_MULTI_SET

SAP Note 27633 - CO01: Missing check whether comp. handled in batches

Symptom:

If you select a component which is not handled in batches and choose Insert -> Batch split, the system responds as when you choose Insert -> General; that is, there is no check whether the material is actually handled in batches.

Cause and prerequisites
Solution
Correction in module LCOMKFM1 : MAT_INSERT_PAI :

SAP Note 27629 - Header texts when cancelling Note 27629 - Header texts when cancelling

Symptom:

Header texts were maintained in the billing document.
When creating the respective cancellation document, these header texts are not transferred from the billing document into the cancellation, but from the basic sales document.

Cause and prerequisites

Program error

Solution
Corrected in 2.2G/3.0B

Additional key words

VF01 Cancellation text

SAP Note 27628 - DDIC texts for SELECT-OPTIONS / PARAMETERS

Symptom:

Frequently asked question:
Are the texts for SELECT-OPTIONS / PARAMETERS which result originally from the Dictionary updated if the Dictionary texts are changed ?
Response: No!

Cause and prerequisites

In text maintenance, it is possible to take certain texts (defined in the program with ... FOR Dict-Struct.) from a dictionary structure.

Solution
These texts are stored in the text pool in exactly the same way.
Thus, later dictionary text changes have no effect on the originally created text pool. If dictionary texts are changed or corrected, the texts of the affected programs must be updated with the help of Text maintenance Selection Text => Utilities => Refresh!
Also note that the transfer of a DICT text only affects the text pool of the current language. The text pool of another language is in no way affected by this.

SAP Note 27625 - Finite scheduling: Multiple reserv. after insertion

Symptom:

Planning board: The planning strategy with parameter 'Insert operation' is activated. The insertion of an operation into an available occupancy situation leads to a multiple reservation.

Cause and prerequisites
Solution
Source code corrections

Additional key words

Finite scheduling

SAP Note 27624 - CO01: Incorrect avail. check for discontinued parts

Symptom:

When you check the availability of a part to be discontinued, the quantity was not redirected correctly to the successor.

Cause and prerequisites
Solution
Correction P30K018001

SAP Note 27623 - Termin. "TABLE_INVALID_INDEX" in ABAP/4 "SAPMIPM0"

Symptom:

The following error occurs:
Line number 0 of internal table "MMPT_TAB" is to be changed, deleted or created. In this case, an index less than or equal to zero was specified in the corresponding ABAP/4 statement with the detail "...INDEX...". This is not permitted.
The termination occurred in ABAP/4 "SAPMIPM0" in "ABR_PLAN_ZHL_DAT_F00" (line 2966 of the ABAP/4 source "MIPM0F00").

Cause and prerequisites

The problem occurs if you try to exit the transaction with 'Cancel' or if you try to call a new transaction (for example, Maintenance planning -> Display preventive maintenance plan within the transactions (IP01, IP02, IP03, IP04, IP05, IP06, IP10).

Solution
The error is corrected in Release 3.0A. Please avoid performing the above-mentioned functions in the 3.00 System. Exit the respective transactions first and then call a new one.

Additional key words

Scheduling, preventive maintenance plan, maintenance item.

SAP Note 27621 - Different currencies in FI and CO as of Release 3.0

Symptom:

In Release 3.0 (and for pilot customers from Release 2.2), it is possible to use different currencies for a controlling area and the assigned company codes.
Question: Can company codes and controlling areas that were set up before this be changed correspondingly?

Cause and prerequisites
Solution
Changing the existing company codes and controlling areas always requires a data conversion.
Existing master data must be checked and, if necessary, changed, because the object currency of the CO account assignment objects must correspond to the company code currency of the CO account assignment object when dealing with company codes and controlling areas using different currencies. For example, the cost center currency must be identical to the currency of the cost center's company code.
Documents already posted must also be converted, so that the updated values in controlling area currency and object currency correspond to the new currency keys for these currencies.
A standard tool does not exist for this conversion. It must be carried out for individual customers with the help of SAP's European Support Group (consultants service).
If a customer wants to set up his system in release 2.2, it is recommended implementing the desired functionality as a pilot version in 2.2. In this case, a conversion is not necessary when upgrading to 3.0.

Additional key words

CO interface

SAP Note 27619 - RFFOCH_U : Bank country of receiver for TR 830

Symptom:

The specification of the country of the bank of the receiver is missing for data medium exchange (foreign payment transactions Switzerland) for transfers which are processed without a SWIFT code.

Cause and prerequisites

Inaccurate description in the data carrier specification

Solution
Correction is made in 2.2G or 3.0B.
You can make the following advance correction:

SAP Note 27617 - Syslog Q0G, scratch area too small

Symptom:

Syslog message Q0G / request (type NOWP) cannot be processed

In the dispatcher trace dev_disp you can find:
*** ERROR =>AdExecBlk:scratch area too small (10436) [adxx.c 0435]
*** ERROR =>DpAdmHandle:AdExecBlk [dpxxdisp 5782]
*** ERROR =>DpRqNoWpHandle:DpAdmHandle [dpxxdisp 1587]
***LOG Q0G=>DpRqBadHandle, bad_req (NOWP) [dpxxdisp 2160]
or also something like
*** ERROR +> MsISnd2: len/2 200/9924 [msxxi.c 0625]

This problem particularly occurs if many work processes are defined. When you go to Alert Details in Transaction RZ03, the syslog is displayed. In Transaction AL01 it is displayed regularly without the user's intervention.
The syslog message may also be generated by external monitoring tools. Test whether the messages disappear when the monitoring tools are switched off.

Cause and prerequisites

When alert information is received, more information is generated than there is space in the message buffer if more than approximately 25 work processses are configured. The number also depends on the kernel release.

Solution
If a lot of work processes are required, it can be more favorable for performance to create two instances on the same host to avoid bottleneck situations at critical points.
A second option is to decrease the amount of transferred information for the alert details (only up to Release 3.0C).
In program RSALINC1 deactivate the following lines:

clear req_tbl.
req_tbl-opcode = ad_profile. "Instance_Name
req_tbl-buffer = 'INSTANCE_NAME'.
append req_tbl.

clear req_tbl. <-deactivate
req_tbl-opcode = ad_wpstat. "Workprozess-Status <-deactivate
append req_tbl. <-deactivate

clear req_tbl.
req_tbl-opcode = ad_queue. "Queue-Status
append req_tbl.

Up to and including Release 3.0F, the following line should be deactivated in the programs rsrzalm1, rsrzadm1:
perform get_slog.


Additional key words

CCMS, Alert, Alerts, ADM Work processes, ADM buffer AD_SCRATCHLEN

SAP Note 27612 - Trans.groups: Field movement checked inadequately

Symptom:

If the new function for 3.0 'Transaction groups' is used in the ledger maintenance of FI-SL Customizing (to allocate activities to a ledger), then suitable field movement rules must be entered. The check for whether an entered field movement rule may be used is incomplete.

Cause and prerequisites

Missing validation in the program

Solution
Do not use the function 'Transaction groups' in Releases 3.0A and 3.0A FCS or you can make the following program correction.
If the function 'Transaction groups' has been used, the correctness of the entered field movement rules can be checked by entering (overtyping) a data element transfer rule again that is assigned in each case to one activity. A check is then started automatically.

Additional key words

Transaction groups, SAPMGCU0, GCL1, GCL2, GCB3, GCG1, GCG2

SAP Note 27605 - Electronic accnt statement GB - Incorr. bal. calc.

Symptom:

When importing the electronic account statement in Great Britain, the balances are not calculated correctly. In bank transactions with processing type 07 or 08, the new account balance is too large by factor 100.

Cause and prerequisites

Program error

Solution
This is corrected in Releases 2.2G and 3.0B.

Additional key words

BACS, UK

SAP Note 27603 - KP95: Background termin. LIST_TOPOFPAGE_OVERFLOW

Symptom:

When copying a plan version with transaction KP95, abnormal termination LIST_TOPOFPAGE_OVERFLOW occurs.

Cause and prerequisites

Preconditions:
1. List printout was chosen and
2. Background processing was used for copying.

Solution
1. Copying without the output of a detail list or
2. Copying without background processing (online) or

Additional key words

Program: SAPMGPLV
Background processing

3. Copying with transaction KP97 or
4. Correction P22K009908 in 2.2G, advance correction as follows:

SAP Note 27600 - Missing actual costs of orders/networks for project

Symptom:

Reporting for capital investment programs did not include the orders/networks for the project when calculating the (summarized) actual values from projects.

Cause and prerequisites

Program error.

Solution
Please make the following advance correction in the source code of function module AIPA_COST_COLLECTOR. The correction has been added to over time, so parts of it may already exist!
Caution: When installing the advance correction, you have to distinguish between releases 3.0B and 3.00, 3.0A!
The final correction will be available in Release 3.0C.

SAP Note 27597 - Processing of several splits causes disappearance

Symptom:

If you select several scheduled splits on the planning table for individual capacities and perform the function "Deallocate", not all splits are displayed on the partial screen of the unscheduled splits. This also applies to other functions concerning splits.

Cause and prerequisites

This is caused by an error in the control of those tables that supply the planning board.

Solution
The necessary changes to correct the error are very extensive. It is therefore not very useful to repeat them in the following section.
The only feasible solution is to process the splits individually.

SAP Note 27596 - Sample drawing instruc.: Missing sample drawing txt

Symptom:

The sample drawing text for a master inspection characteristic copied into the task list is not printed in the sample drawing instruction.

Cause and prerequisites
Solution
See the source code corrections.

Additional key words

Sampling text

SAP Note 27595 - Vendor evaluation - Score for complaints level

Symptom:

The score for in-production complaints was not displayed in the overall log.

Cause and prerequisites
Solution
see below

SAP Note 27592 - Transferring data from the billing plan

Symptom:

An alternative term of payment in the billing plan or billing type is not transferred to the billing document.

Cause and prerequisites

Program error

Solution
corrected in 3.0B

Additional key words

VF01 FPLT-FKARV FPLT-ZTERM

SAP Note 27589 - RFFOD__U - Change note to payee debit memo

Symptom:

The note to payee in field C16 of the German data medium exchange (format DTAUS0) has been changed for debit memos in Release 2.2:

up to Release 2.1 : Account number of the orderer
as of Release 2.2 : Payment document number and invoice number

Cause and prerequisites

The change consists of the following description of field C16 in DTAUS0 format (you can get the record description from the house bank).
Quote:

"...
C16 Note to payee: Please make entries as short as possible.*)
...
*) Such entries are to be made left-justified at the start of this field which may be intended to identify the beneficiary for transfers (for example savings account number, insurance policy number, invoice number) or which the payee may require as a debit memo in case the payment is unpaid or returned."

Conclusion:
For bank transfers, the account number (of the sender for the receiver or - if this is not maintained in the master record - of the receiver at the sender) is entered.
For debit memos, the payment document number is entered as of Release 2.2 since this clearly identifies a returned memo .

The information on the original ship-to party is set in the first note to payee of the variable part (fields C19/C20) for alternative persons liable for payment, so that this information must suffice to identify the initiator of the entry.

Solution
The standard program strictly follows the data record description specified by the banks and quoted above. A change is therefore not supported.

As of Release 3.0, a user exit will be available for field C16. Until then, it is of course left up to you to recreate the 2.1 status of the program using modifications.
Bear in mind that you must release the modification as a repair and that it might have to be maintained again after updates. If the repair should not be released, inconsistencies can occur in the program after an update and lead to errors in data medium exchange for which SAP is not accountable.

Additional key words

DME, F110, RFFOD__U, RFFORI04

SAP Note 27588 - Report RMCSISGN does not generate recordings

Symptom:

The report RMCSISGN does not generate update rules

Cause and prerequisites

Error in the program RMCSISGN

Solution
The error is corrected in Release 3.0B. An advance correction can be made by a program correction.

SAP Note 27586 - Transfer of material master data: units of measure

Symptom:

When transferring material master data (for example, batch input or decentralized shipping), an error occurs accompanied by the message "Data for screen 110 does not exist" or "Conversion factors for unit on main screen can be changed only via BMMH6".

Cause and prerequisites

You maintain an alternative unit of measure that is simultaneously a standard unit of measure (for example, a sales unit). The problem is particularly likely to arise if two standard units of measure have the same value on one screen (for example, delivery unit and sales unit on the Sales 1 screen) or if a delivery unit is assigned to the material.

Solution
Problem corrected in Release 2.2J and Release 3.0B.

Additional key words

BTCI, SAPMM03E, RVMATDEZ

SAP Note 27583 - SE54: Error in automatic screen number assignment

Symptom:

In the transaction SE54, for the function Search for screen numbers -> Popup Propose screen numbers, overview screen = 1 and single screen = 2 are always proposed as a maintenance screen. This occurs even if the maintenance screens for the function group entered are already assigned.

Cause and prerequisites

This is an error in the program code

Solution
Correction of the program code

Additional key words

Generate the table maintenance dialog
Generate the enhanced table maintenance
Generate SM30

SAP Note 27579 - Pmnts on acct not considered for interest calc.

Symptom

When calculating interest on arrears (program RFDUZI00), it can happen that payments on account (partial payments) are not taken into consideration.
If the "Only int.on debit items" (T056U-FLAG5) switch is selected, then interest is nevertheless calculated on payments on account (partial payments); this should not happen.

Cause and prerequisites

Payments are recognized by the NEBTR field, and it can happen that interest is not calculated.

Solution
Error corrected in Release 2.2I and 3.0D. It is also possible for customers to implement a fix for this problem themselves.
Insert the lines marked with "<----insert" in the RFDUZI00 and RFKUZI00 programs.

Additional key words

RFDUZI00, RFKUZI00, partial payments, payments on account

SAP Note 27578 - Long runtimes during order reorganization

Symptom:

The runtimes during the production order reorganization increased disproportionately with the orders on hand to be processed.

Cause and prerequisites
Solution
Correction

Additional key words

PPREOSEL, CO78

SAP Note 27574 - Procurement type X in order profile -> EM 61018

Symptom:

When you try to create a planned order profile or purchase requisition profile (Transaction OMDD) with procurement type X (internal and external processing), error message 61018 is displayed: 'Invalid procurement type'.

Cause and prerequisites

When you press the possible entries pushbutton (F4), all procurement types which are stored in the system are displayed. Procurement type X is only defined for maintenance in the material master. In Customizing, you have to determine unambiguously whether the order profile is defined for internal or external processing. This is necessary for scheduling, for example (internal production or replenishment lead time, material master or routing).

If procurement type 'X' is entered in the material master, the planned order can only be procured internally or externally regardless of the planned order profile definition.

Solution
Select procurement type 'E' (internal processing) or 'F' (external processing) in Transaction OMDD.
As of Release 4.X, if you press the possible entries pushbutton (F4) on the procurement type in Transaction OMDD only those values that can actually be entered are listed (in this case 'E' or 'F'.)

Additional key words

Purchase requisition, PReq

SAP Note 27573 - Routing selection via user exit

Symptom:

The existing routing selection by means of a selection ID did not consider user exits, if the selection was neither made via the task list application nor the task list type.

Cause and prerequisites
Solution
The task list type is unique for each selection ID and selection priority, TCA43. Via table TCA01, you can determine the task list application for a specific task list type. You can now determine the user exit via table TCA44 by means of the task list application, task list type and selection ID.

If you select the routings via the selection ID, all routings with selectable operations can be assigned to this ID and to a priority. All routings with the lowest priority are selected. The user exit is determined as described above and carried out, if available.

Additional key words

routing_selection

SAP Note 27572 - Incorrect obj. type during settlement rule determ.

Symptom:

An incorrect object type is read during the settlement rule determination for a network activity.

Cause and prerequisites
Solution
Source code changes in Include LCOSFU11:

SAP Note 27569 - Vendor evaluation: ME63 - Smoothing factors

Symptom:

If you change the smoothing factors, they at first do not affect the scores for the subcriteria (for example, on-time delivery performance).

Cause and prerequisites

Certain points scores are determined during the goods receipt, for example, when the statistical delivery date deviates from the actual goods receipt date.
The determined points score is smoothed and stored in information structure S013. Transaction ME63 only reads these values and calculates your result. This means that transaction ME63 does not read the smoothing factors at all. The changed smoothing factors only take an effect, if you post new goods receipts.

Solution
See the cause.

Additional key words

ME61, V_T147, (T147-LFABW, T147-MGABW)

SAP Note 27567 - Planned allocation: Reversing several periods

Symptom:

1) When you reverse a planned assessment or planned distribution, only one period is reversed although several periods should be reversed at the same time.
2) When you reverse a planned assessment or planned distribution, only the first period block (for example, 16 periods) is reversed although more periods should be reversed.
Caution: These errors can only occur in POOL tables.

Cause and prerequisites

re: 1) No plan line item table is implemented although plan line items are written. The plan line items are then correctly written to the actual line item table, but index table GLIDXB is not (the period is not contained in GLIDXB).
re: 2) A plan line item table is implemented, but only the first period block can be written because of a design error in table GLIDXB.

Solution
re: 1) Either define and implement a plan line item table or perform the allocation individually for each period and then reverse it.
re: 2) Always perform the allocation for an entire period (for example,
1 - 16) and then reverse it.

Additional key words

Assessment, distribution, allocation, segment, cycle, GA15, GA2B, GA35, GA4B

SAP Note 27564 - Set SAPREORG directory to another hard disk

Symptom:

The SAPREORG directory is too small. The customer wants to set it to another hard disk. How do you do this?

Solution
Unix: Create a new file system on a hard disk which is large enough, and then create a link.

Example: System P11, new file system /bigdisk:
su - root
mount /bigdisk
su - orap11
rmdir /oracle/P11/sapreorg
mkdir /bigdisk/sapreorg
cd /oracle/P11
ln -s /bigdisk/sapreorg sapreorg

Note: If you do not want to use a soft link, further changes are necessary, namely entries in /oracle/P11/dbs/initP11.dbs and /oracle/P11/dbs/initP11.sap. The above-mentioned method is therefore preferable.
Windows NT: Create a new directory which is large enough. Change the parameter SAPREORG with "Control Panel -> System -> User environment variables".

Note: It is not necessary to modify the 'init' files, as the environment variable is entered there instead of the path.

SAP Note 27559 - Exploding bill of material in network (3.0)

Symptom:

If you explode a bill of material in the network:
- a dummy assembly is not exploded in several steps.
- the BOM line item number is copied even if an item with same number exists already in the network.
- and if you further explode a component of the existing list, it is created as text item in which case the material number is written into the description and not easy to find.
- the characteristic value assignment is not considered when you explode a configurable component.
- the dependent requirements indicators maintained in the material master of the BOM items (individual/collective requirements) are not checked.

Cause and prerequisites
Solution
Various source code changes:

SAP Note 27557 - MF50: Incorrect scrap distribution in planned orders

Symptom:

Planning table in repetitive manufacturing: In planned orders with distribution function, the scrap is distributed incorrectly. The entire scrap is added to the first period.

Cause and prerequisites

Program error in the distribution function.

Solution
Source code corrections

SAP Note 27555 - Error in quota deduction

Symptom:

Caution: On 22 May 1997, the line marked "XLCK147924 was inserted in this note in module FILL_ICLPC of Include MPZPCALE.
Inconsistencies arise between absences or attendance on the one hand (infotypes 2001 or 2002) and absence or attendance quotas on the other hand (infotypes 2006 or 2007).

Cause and prerequisites

Some situations where this error is known to occur:
Enter an absence, make a save, collision in the time constraint or warning message: Make a change in the accounting past, cancel without saving the absence: the quota was reduced anyway.
An absence exists which reduces a quota, another absence is entered which automatically delimits a part of the existing absence with regard to its time constraint: the quota is not updated correctly.

Solution
The correction specified below will change the whole procedure for quota deduction entirely. This affects the entering and tracing of quotas by deleting or changing data.
This note contains Note 26350's correction for leave deduction. However, you must use the modules specified HERE.
Change the modules in Note 26350 correspondingly!
Insert the modules
REFRESH_QUOTA
CHECK_DEDUCTION
REFRESH_QUOTA_FAST
CANCEL_QUOTA_DELETED on screens 2001, 2050, 4000, 4050, 4051, 7150, 7151 of program MP200000 as specified and then regenerate the screens.
(the changed lines are marked XDEP30K012776.)
Then enter the modules in the specified Includes, and the corresponding respective data declarations and subroutines as specified.
After this, change the existing subroutines and modules as specified.
If you want, you can delete any subroutines you no longer need (UPDATE_P2006/7, EXEC_P2006/7, READ_P2006/7, HOLIDAY and CHARGE_HOLIDAY) in Include MP200140.
Finally, carry out a syntax check for program MP200000.

Additional key words

Absence quota, attendance quota, approval of attendance, I2006, P2006, I2007, P2007, I2002, P2002, I2001, P2001, attendances, absences.

SAP Note 27551 - MF50: Shift sched.:Planned orders classed wrongly

Symptom:

In the repetitive manufacturing planning table (MF50), Rate view and explosion: 'shift', the scheduled planned orders are in the wrong columns.

Cause and prerequisites

Program error

Solution
Repair in program code:

SAP Note 27550 - No shares after release upgrade to 2.1/2.2 -> 3.0

Symptom:

The release upgrade from 2.1 or 2.2 to 3.0A was performed and program RGCON30A ("Conversion to 3.0A") was started as well during the update. However, the subgroup does not show the correct group shares (transactions GC17, GC18) but only "0,00000000".

Cause and prerequisites

Program error RGCON30A

Solution
Implement correction vsk014885 in RGCON30A and restart the conversion.

SAP Note 27547 - Winhelp: R/3 Multimedia Disp. window remains

Symptom:

When you call Windows Help from R/3, the popup 'R/3 Multimedia Dispatcher' appears as soon as the Windows Help is displayed, and does not close. In the task list, you can see that a new task 'help_04' is created whenever the Help is called, and does not close by itself.

Cause and prerequisites

Program Help_04.EXE, delivered with the 2.2F SAP-GUI, causes this phenomenon to occur under certain circumstances.

Solution
If you want to be able to go back to an older SAP-GUI (Release 2.2..), copy the program Help_04.EXE from the directory of this SAP-GUI into the directory of the 2.2F SAP-GUI you are using.
Note that it is not possible to copy the program from an older 32-bit SAP-GUI into the current 16-bit SAP-GUI.
Save the program Help_04.EXE under another name before you overwrite it.
You can also copy the current version of program HELP_04.EXE from the SAPSERV3 or SAPSERV4 server.

Usable in R/3 Release 2.2.. and 3.0..
The current version of the program HELP_04.EXE is on SAPSERV3 and SAPSERV4.
The 16-bit version can be found in the directory 'dist/help_04/16bit/help_04.exe'
The 32-bit version can be found in the directory 'dist/help_04/32bit/help_04.exe'
Requirement: You have access to SAPSERV3 or SAPSERV4 via FTP.
Enter the following commands and confirm every line with
open sapserv3 (or sapserv4 or sapserv4.sfo)
ftp (user ID = FTP)
ftp (password = FTP)
cd dist
cd help_04
cd 16bit (or cd 32bit)
bin (switch to binary mode)
get help_04.exe c:\temp\help_04.exe
close (end FTP session)
Open the SAP-GUI directory with the File Manager. Localize the program HELP_04.EXE in the SAP-GUI directory and copy it under the name HELP_04.SAV. Copy the program HELP_04.EXE from the directory C:\TEMP\... to the SAP-GUI directory.
If directory C:\TEMP\ does not exist, either create it or use another directory.

Additional key words

Winhelp Documentation Docu-CD R/3 Multimedia Dispatcher HELP_04.EXE

SAP Note 27546 - Edit formats, underscores in table view control

Symptom:

When displaying a table control, the field contents are not displayed, only the edit formats of the fields.
No error message appears

Cause and prerequisites

Error in the data exchange between the server and the frontend

Solution
By resizing the window, the error can generally be avoided.
Corrected in 3.0B

SAP Note 27544 - Syntax error SE16 / incorrect table / Type conflict

Symptom:

Syntax error in Transaction SE16 - general table display -
Display the contents of the incorrect table in Transaction SE16.
Type conflict when calling form routine "RSEUMOD_SELECT"
Problems in the individual display

Solution
Force a regeneration of the display report in the initial screen of SE16 by means of TABLE -> Program generation. If the error occurs for several tables, the entire CONTENTS of the table TBPROGREF can be deleted. If required, this causes a regeneration of all display reports.

Additional key words

eunote, eudatabrowse, PERFORM_PARAMETER_TOO_SHORT, LSETBF01, SAPLSETB

SAP Note 27543 - Error message in usage decision because inv.posting

Symptom:

Message KI235: 'Account & requires an assignment to a CO object'
Message M7093: 'Fld select.for mvmt type 553 / account & differs for cost center (010)'
Message M7093: 'Fld select.for mvmt type 331 / account & differs for cost center (010)'
Transactions: QA11, QA12, QA14

Cause and prerequisites

This is caused by an error.

Solution
Carry out the program correction.

Additional key words

Usage decision, quantity release, stock postings, production lots

SAP Note 27542 - Parameter ZCOM0 with sapmaco

Symptom:

Performance problem when building matchcode records - sapmaco is running.

Cause and prerequisites

The suggested change can be used in every case, even when no performance problems for sapmaco have been detected.

Solution
Code change in the function module MC_CREATE_UTILITY_MCO

Additional key words

sapmaco matchcode records

SAP Note 27537 - FI-SL:termination due to missing exit programs

Symptom:

An abnormal termination occurs because a user exit program was not found in FI-SL (for example RGIVUxxx, RGIFUxxx) when you post a document.
Typically, this problem occurs after a release upgrade, an upgrade, a client copy (local or remote) or a system copy.

Cause and prerequisites

In the FI-SL Customizing, field movements with user exits were created or exits for validation or substitution were entered, which cause problems with the above-specified actions.

Solution
For releases < 3.0:
If program RGIFU000 was not found, you have entered user exits for the fixed field movements but have not programmed any exits. Therefore, check your fixed field movements and create an exit, if necessary.
If program RGIVUxxx (xxx = current client) has not been found, copy RGIVUxxx to your new clients.
As an alternative, you can also use the program RGIVU000 for all clients.
Then start program RGIMOVV0. The program RGIMOVV0 ensures that the respective FI-SL programs are regenerated and the right user exit programs are used.

For releases 3.0A through 3.0B
Please read the release note 'User Exit Programs in the Field Movement' for Release 3.0A first.
You can find the exit programs for the respective application areas in the table T80U (client-independent). These tables you can find in the FI-SL Customizing under Basic Settings -> User Exits.
If a program terminates because a user exit program could not be found (for example, after a client copy), create this exit program by copying an already existing one, include it in this table and then start program RGIMOVV0 to regenerate the FI-SL programs.

As of Release 3.0C
Please read the release note 'Specifying the User Exit Programs in Tables T80I and/or T80D' for Release 3.0C first.
You can find the exit programs for the respective application areas in the tables T80I (client-independent) and T80D (client-specific). These tables you can find in the FI-SL Customizing under Basic Settings -> User Exits.
There shold not be any problems with the client copy.
In the case of a system copy, the user exit programs up to and including Release 3.0F are not also transported automatically.
After the client transport, you have to transport the user exit programs into the target system or maintain them there manually.
In case of an upgrade from a release < 3.0C to a release > 3.0C, the current client is always specified as the last 3 characters of the program name when table T80U is converted to T80D (if the Client-dependent ID was active in T80U), regardless of whether the program exists, or not. This can cause problems with the upgrade. In this case, please make sure to maintain table T80D.

Up to and including Release 3.0E, you have to start program RGIMOVV0 or program RGUGBR00 with the parameters Validation, Substitution, Rules for regenerating the FI-SL programs after each change to table T80D.


General note:
Please ensure that you only use program names that lie in the customer name range (for example, Zxxxxxxx) in the table T80U (up to and including Release 3.0B) or in the tables T80D and T80I (as of Release 3.0C), in which user exit programs are entered.
Please assign a valid customer development class to these programs so that the programs can be transported correctly.

Additional key words

RGICOPY0, T80U, T80D, T80I, RGIVU000, RGIFU000

SAP Note 27536 - Dynamic shift creation: breaks outside of planned working ti

Symptom:

In the case of part-time workers with dynamic shift creation, breaks which fall outside of the planned working times / normal working times are not taken into account in the following cases:
1. Breaks which are stored in table T550P with break type = 'O' and which fall outside of the employee's planned working times should be proposed as default values when infotype 2005 ( overtime ) is being created. For dynamic shift creation, this is not the case.
2. As of Release 3.0A, time evaluation should, as a default, import and evaluate all breaks which are stored in the work break schedule. In the case of dynamic shift creation, not all breaks are imported.

Cause and prerequisites

Program error.

Solution
This error has been corrected in Release 3.0B (correction number P30K013021). You can carry out this correction in advance.
To do this, change the lines marked "XEDP30K013021 below in Include LRPTMF02 in FORM routine CHECK_DYSCH, and then check that program SAPLRPTM contains no errors.

Additional key words

Part-time work, dynamic shift creation, employment percentage, breaks, unapproved overtime, planned working time, cycle TD00, T550P.

SAP Note 27534 - Vendor evaluation: author and date of creation

Symptom:

ME61/ME63(RM06LBEW)/RM06LBAT:
-----------------------------
In some cases (e.g. in the case of a new evaluation), the author and the date of creation of a vendor evaluation was only partially set. Now this information is updated with each new evaluation.

Cause and prerequisites
Solution
See above.

SAP Note 27530 - SAPDBVLV: PUT_VBFA gives incorrect data

Symptom:

The logical database VLV gives incorrect data at the event GET VBFA.

Cause and prerequisites

Program error

Solution
Correct FORM routine PUT_VBFA in program SAPDBVLV as follows:

SAP Note 27527 - RM07IDIF: Error in several special stocks

Symptom:

If you create a physical inventory document for a special stock in which the individual items belong to different sales orders, customers or vendors, the following error occurs when you print the list of inventory differences for this physical inventory document:
only one heading is issued for all items, that is, it seems as if all items belong to the very same sales order, customer or vendor. Instead, a heading must be displayed every time you change the special stock.

Cause and prerequisites

Program error

Solution
Corrected in 2.1M, 2.2G and 3.0B.

SAP Note 27522 - Online planning: Termination

Symptom:

Release 2.2:
Runtime error in the sales and profit planning during screen change from the entry screen of the characteristics to the entry screen of the planned figures. The error occurs in program MKEPPF05 in FORM routine PRCTR_STERN_VERPROBEN.
Release 3.0:
The ABAP/4 runtime error RAISE_EXCEPTION occurs in FORM routine CREATE_DIMENSION_TREE in Include LKPP0f02 during online planning (KE11) or the pre-parameterization of a layout in profile maintenance (KP34).

Cause and prerequisites

The profit center was excluded from being used during planning in the characteristic usage (table TKEOE).
Up to and including Release 3.0B it is not valuated during the table maintenance. As of Release 3.0C, a validation is made so that the profit center should not be excluded. The termination can nevertheless also occur in a release > 3.0B, if the table has been maintained in an earlier release.

Solution
Release 2.2:
Activate the profit center for the planning in the characteristic usage. Call transaction KE02, Details, Segment level crit. Specify the additional entry for the profit center: PRCTR X
Then start transaction KE02 and choose 'Details -> Process conversion'.
Release 3.0:
Delete the entry in the Segment level crit. (KEQ3) for field PRCTR.

SAP Note 27521 - Planned delivery costs for unvaluated material

Symptom:

Invoice Verification: If you want to copy over planned delivery costs for an unvaluated material, the system checks whether valuation data has been maintained for the material. An error message appears indicating that no valuation data exists (message number M3354). This check is superfluous. The planned delivery costs are copied over to the document.

Cause and prerequisites

Program error.

Solution
Corrected in 3.0A.

Additional key words

Transaction: MR01 / MRHR

SAP Note 27517 - Installing RFCSDK

Symptom:

The Remote Function Call Software Development Kit (RFCSDK) is not available in the customer's system.

Other terms

RFC, SDK

Reason and Prerequisites

You require RFC SDK or the test programs it contains for development. However, RFC SDK is not installed in your system. To make sure that RFC SDK has not yet been installed in the system, search the system for the directory "rfcsdk" (standard installation directory).

In the following subdirectories, RFCSDK contains:

• bin - the MS Window DLL and the executable test programs

• include - the C-header files

• lib - librfc32.lib for MS Windows or the shared libraries

• text - documentation for RFCSDK; C-source files for the sample programs
  

Note that the executable test programs in the directory bin can be used to execute RFC-enabled functions in the SAP system (provided the user has the required authorization). We therefore recommend that you remove the programs again after the test.

The programs startrfc and rfcexec have been classified as potential
security holes (see Note 1140031) and are therefore no longer delivered with the classic RFC SDK 7.20.

As of SAP release 7.10, NetWeaver RFC SDK is delivered, which has a modified API that is incompatible with the classic or the Unicode RFC SDK. For new developments, we recommend that you use the NW RFC SDK. The installation of NW RFC SDK is described in Note 1025361.

Solution

The classic and the Unicode RFC SDK are available via SAP Software Distribution Center:

Classic RFC SDK

• 6.40: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200314690200003978&V=MAINT

• 7.00: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200314690200005775&V=MAINT

• 7.10: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200314690200005795&V=MAINT

• 7.20: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200615320200018068&V=MAINT
  

Unicode RFC SDK

• 6.40: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200314690200003979&V=MAINT

• 7.00: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200314690200005778&V=MAINT

• 7.10: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200314690200006291&V=MAINT

• 7.20: https://service.sap.com/~form/handler?_APP=00200682500000001943& _EVENT=DISPHIER&HEADER=N&FUNCTIONBAR=N&EVENT=TREE&TMPL=01200615320200018069&V=MAINT
  

You can unpack the SAR files using the program sapcar. To do this, switch to the directory in which you want to install RFCSDK. The subdirectory "rfcsdk" is created automatically when you unpack the files.
For example: sapcar -xvf RFC.SAR

If you install RFCSDK from the presentation CD, the RFC library may be obsolete. Refer to the following notes:

• 413708 RFC library that is current at this time

• 336693 Replacing the librfc32.dll on a Win 32 Platform

The documentation for the RFC library can be downloaded from:
http://service.sap.com/connectors
SAP NetWeaver
SAP NetWeaver in Detail
Application Platform
Connectivity
Connectors
RFC Library
Media Library
RFC Library Guide (PDF)

SAP Note 27515 - VF01/VF02: SD/FI transfer - Error F5844

Symptom:

Error message F5844 is displayed during the SD/FI transfer:
'System error: FI data from RW interface are inconsistent'.

Cause and prerequisites

One of the fields
blart Document type
bldat Document date
budat Posting date
xblnr Reference document number
is set via user exit 'userexit_fill_xkomk1'.

Solution
Corrected in 3.0B.

Additional key words

VF01, VF04, VF02

SAP Note 27514 - Planning log: Undefined date in factory calendar

Symptom:

Planning board: In scheduling an operation the message C7008 occurs in the planning log.
Instead of this, the message C7056 'Capacity not available' has to appear.

Cause and prerequisites

The work center formulas are maintained so that they lead to an overload.

Solution
Instead of this, the message C7056 'Capacity not available' has to appear.
Source code corrections.

Additional key words

Finite scheduling

SAP Note 27506 - Which objects are modified in customer systems?

Symptom:

An analysis of how many and which objects in the SAP Standard System are modified in a customer system is required.

Cause and prerequisites

For example, preparation of a release upgrade ...

Solution

• In Release 2.2G, a modification monitor is delivered.
  Call it via Correction and Transport System -> Tools -> Transport tools -> Modification monitor, or directly by starting the ABAP program MODIMON1.

• This monitor determines all modified objects, and groups them together according to their development classes.
  By selecting a development class, a list of modified objects in this development class is displayed.
  By selecting an object, a list of the versions of this object is displayed.

• The modification monitor is also available for all 2.1 and 2.2 releases as the preliminary transport B11K017585.
  This preliminary transport can be acquired according to note 13719 from sapserv3 or sapserv4 in the directory dist/permanent/Note.0027506 .
  Important note: If this preliminary transport is imported into a system with update level < 2.2E, the texts for development classes are only displayed in German.

Additional key words

Repair exits SPAU SPDD modification, modification adjustment

SAP Note 27505 - ME90: Delivery costs not printed

Symptom:

Delivery costs and other conditions involving provisions for specific future liabilities are not printed in the purchase order although they are marked as "to be printed" in the price calculation schema (pricing procedure).

Cause and prerequisites

Error.

Solution
Corrected as of Releases 3.0B and 2.2G.

Additional key words

PO printout, freight

SAP Note 27503 - Update assembly scrap for material

Symptom:

Assembly scrap is calculated incorrectly.

Cause and prerequisites
Solution
Program correction

Additional key words

Scheduling

SAP Note 27502 - No text for the message SI 033

Symptom:

No text is displayed for the message SI 033.

Cause and prerequisites

The message SI 033 appears after downloading a customizing project.
No text exists for this message.

Solution
The message SI 033 means that the project download was completed successfully.
To create a text for this message, call the transaction SE91. As the message class, enter 'SI'. When you then press the pushbutton 'Change', list of all messages of this class appears.
Scroll to line 033, position the cursor on this line and press the pushbutton 'Individual maint.'. You can now enter the missing message text, for example, 'Data successfully transferred'. This text is available as soon as you save it.
The error no longer occurs from Release 3.0A onwards.

SAP Note 27501 - PPIS: Totals instead of Mean Values in Analyses

Symptom:

Many key figures in the standard analyses and flexible analyses of the Shop Floor Information System are displayed as mean values. In spite of this, you may want to have the totals displayed in some applications.
As of Release 2.2I and 3.0E, quantities are displayed in terms of totals and no longer as mean values. If you require mean values, you need to use the opposite method to the solution given below.

Cause and prerequisites
Solution

In Release 3.0, the totals display is always used for self-defined information structures.
If it is absolutely necessary for you to make such a modification, do so for the standard analyses in routine KENNZAHLEN_BERECHNEN in the corresponding program RMCF0xF0 (x = 1, 2, 3, 4 - this stands for the information structures S021 to S024).
For the flexible analyses proceed in several steps:

1. Expand the program FMCFxF01 (x = 1, 2, 3, 4) by the routine F02 (see below).

2. Change an entry in table T804B in order to display a key figure as a total. An example for the actual execution time is shown below in the ABAP ZCDT804B.

3. Generate the corresponding evaluation structure.

SAP Note 27500 - Maintain configurat. profile: Organizational areas

Symptom:

If configuration profiles were maintained with several organizational areas, errors can occur when determining the parametrization valid for the class within a given time.

Cause and prerequisites

Program error

Solution
Correction in FORM routine 'Dynamic_date_to' in Include LCUCOF01.

Additional key words

CU41, CU42, CU43, SAPLCUCO

SAP Note 27499 - Confirm delivery: credit check -> error

Symptom:

When confirming a delivery by a WM transfer order, an error occurs due to a credit check. As a result, the transfer order cannot confirm which causes an unresolvable situation.

Cause and prerequisites

Program error

Solution
Corrected in 3.0B and 2.2G with P22K009863
An error is no longer triggered when the credit situation is violated in the above case. Therefore, it is important that you also activate the lock indicator in the Customizing of the 'automatic credit check' in addition to response 'B' (error) to ensure that the document appears in the work list of the credit representative and is blocked for follow-up actions (goods issue).

Additional key words

Credit limit, VL02

SAP Note 27497 - Rebate settlement payment: Displaying cancel. doc.

Symptom:

Cancellations for rebate credit memos are not displayed under the menu option Payment - Rebate document.

Cause and prerequisites
Solution
Enhance LV14AF01 in form: DISPLAY_CN_ITEMS and
Enhance LV14AI01 in module: LIST_PRO
Enhance LV14ATOP

Additional key words

Transaction VBO1, VBO2, VBO3
SAPLV14A, rebate settlement

SAP Note 27496 - Maintain configuration profile: Inserting classes

Symptom:

If you insert a class when maintaining the configuration profile if other classes are already allocated, errors can occurs for example, when deleting this class.

Cause and prerequisites

Program error

Solution
Correction in module 'D0200_LOOP_CR' in Include LCUCOI01 and in function 'CUCO_INSERT_CONFIG_PARAMETERS' in Include LCUCOU01.

Additional key words

CU41, CU42, SAPLCUCO

SAP Note 27493 - CO-PA cycle maintenance: Inc. scrolling in segment

Symptom:

Description: When entering selection criteria for a field and simultaneously changing the line number (scrolling to the exact line), the entries are assigned to an incorrect field.
Example: If an available group is entered as a selection criterion for a field and the line number is changed at the same time, then the unwarranted error message GA080 appears: "Group & belongs to a different field".
Transaction: KEU1, KEU2, KSU1, KSU2, KSV2, KSV2, KSU7, KSU8, KSV7,
KSV8, KSC1, KSC2, KSC7, KSC8, KSW1, KSW2, KSW7, KSW8,
GA11, GA12, GA31, GA32, GA27, GA28, GA48, GA49, CPC1,
CPC2, CPC7, CPC8
Program name: SAPMKAL1

Cause and prerequisites

Program error in the screen logic - the line feed is carried out too early.

Solution
1. Workaround: You can avoid the error by pressing ENTER between the
two actions of "change selection criteria" and "change line number."

2. To correct the error finally, you must install the following
correction.

Additional key words

Allocation

SAP Note 27488 - Variant configuration: Table maintenance CU60

Symptom:

If the window for entering values for the characteristic is displayed during the table maintenance, the values are partially overwritten by the value texts. As a result, those values cannot be selected.

Cause and prerequisites

Program error

Solution
Correction in FORM routine 'output_w100' in Include LCUD2F10.

Additional key words

CU60 SAPLCUD2

SAP Note 27485 - Goods issue for deliveries w/o inventory management

Symptom:

Deliveries which only consist of non-inventoried items are not taken into account in the collective transactions for posting the goods issue:

• up to Release 4.0B
  Transaction VL19: Deliveries currently being processed - Deliverieis for Goods Issue

• as of Release 4.5A:
  Transaction VL06G: Outbound delivery monitor - Outbound Deliveries for Goods Issue
  

This affects, for example, deliveries which consist only of items with materials of material type 'DIEN' (service products, service management, MM external services management) or which consist only of text or value items. These deliveries are also not displayed in the search help for outbound deliveries.

Cause and prerequisites

This function is not planned in the R/3 standard system. For non-inventoried deliveries, a goods issue posting is not required. Nevertheless, in individual cases you might want to be able to trigger follow-up actions, as for example, billing via the posting of goods issue.

Solution

Change the selection conditions of matchcode object VMVL as described below.

1. Call up Transaction SE11 (ABAP Dictionary) and branch to the display of matchcode object VMVL. Carry out this step according to the release of your system:

• Releases 3.0 and 3.1: On the initial screen of Transaction SE11, enter object name VMVL and select the dictionary object 'Matchcode objects'. Then, choose 'Display'.

• Release 4.0: On the initial screen of Transaction SE11, enter object name VMVL and choose function 'Utilities--> Matchcode objects --> Display' via the menu.

• Releases 4.5 and 4.6: On the initial screen of Transaction SE11, choose function 'Utilities -> Other Dictionary objects'. On the dialog box which is then displayed, select object type 'Matchcode object' and enter object name VMVL. Choose 'Display'.

2. On the initial screen of the matchcode maintenance, press 'Matchcode IDs'.

3. Select matchcode ID A on the selection dialog box and branch to the selection conditions of the matchcode ID.

4. There, delete the following line of the selection condition

MC field Lngth Offs Op. Comp. value AND/OR

VBOBJ 1 0 EQ 'L' AND
WBSTK 1 0 NE ' ' AND <<<<<< DELETE
WBSTK 1 0 NE 'C'

5. Activate the matchcode ID. These steps are sufficient in order to allow the selection of the non-inventoried deliveries via Collective Transactions VL19 or VL06G. If you want that these deliveries can also be selected via search help C 'Not posted for goods issue: shipping point/trans.s', carry out steps 1 to 5 for matchcode ID C of object VMVL.

6. Reconstruct matchcode ID A (and C, if necessary) with report SAPMACO (see Note 15760).

Additional key words

Matchcode, VMVL, M_VMVLA, M_VMVLC, WABU, selection, delivery monitor, WBSTK, goods movement status, VL23

SAP Note 27484 - Variant configuration: Table maintenance CU60

Symptom:

No intervalso for numeric characteristics are stored during the table maintenance that are not already listed under the standard values for the characteristic.

Cause and prerequisites

Program error

Solution
Correction in FORM routine 'value_check_num' in Include LCUD2F04.

Additional key words

CU60, SAPLCUD2

SAP Note 27471 - Late payment to leavers in the same leaving period

Symptom:

When there is a need to have a payment made to a leaving employee and then make a second payment after they have left, but in the same period, then there are differing tax and NI rules required to be used in the calculation.
In addition it was felt that rather than using special wage types to calculate late NI in terms of it being regular or irregular (model company wage types A090 and A095), the normal payment wage types should be able to be used and the payroll automatically detect when we are in the 'Late payment to Leavers' situation.

Cause and prerequisites

There is an assumptions made to realise this solution. In actual fact it is the issue of the P45 that should determine when any future payments to the employee need to be calculated in the 'Late payment to leavers' way. Therefore an employee could have left but if not having yet recieved their P45 the any payments are normal. The development of an automatic 'P45 issued' indicator is in process but in the meantime we have to assume that the leaving event (rendering the employee inactive) means that the 'Late payment to leavers' method of calculation will be used.

Solution
The key to solving the problem is to have two sets of payroll results in the same period. There is a way to achieve this at the event level.
To enable this creation of two payroll results in one payroll period please either maintain the leaving event or create a leaving event with a specific reason in T530. The table entry either way should have the split field marked.
In addition, all payment wage types must have either cumulation class 32 or 33 marked. The reason being that we can then determine on these normal wage types in which way (regular or irregular) NI should be calculated on detection after leaving. All these payment wage types should still retain the cumulation class 31 mark also.
An example of this would be on model company wage types A090, A095:
-----------------------------------------

Additional key words

An example of where this may occur, is when the user wishes to make one payment to cover the part period renumeration and then before the end of the current payroll period, make a supplementary run to pick up redundancy payments for the current period that have to be taxed at basic rate on basis week 1 month 1.

SAP Note 27469 - Starters NI deductions in second period

Symptom:

If a new starter has not been paid in their first period but then in the second (or third...) then the NI calculation should in fact retroactively calculate the NI to be taken for both employees and employers but bring it forward into the current period and take it there. In other words for 'normal' NI periods retroaction should be active for NI.
For periods where NI was taken before then we should not recalulate it but bring forward any changes to the NIable pay which may have happened in the past.

Cause and prerequisites

Payroll missing an employee for a period in which they are to be paid and subsequently are liable for NI contributions. A typical example is a starter whom started last period too late to be administered by that payroll run. They should of course have that 'normal' NIable period administered in this period and thus have the NI contributions taken this period.

Solution
Please amend the existent reports / cycles /tables as directed. Apologies for the number of changes required, but this is a fundamental change to the way in which retroaction for NIC's was designed.

SAP Note 27468 - SAPMA01B runtime error / paging ZANLC

Symptom:

Runtime error TSV_TNEW_PG_CREATE_FAILED occurs during the generic retirement.

Cause and prerequisites

Program error

Solution
Advance correction in program LAINTI20.

Additional key words

Retirement, SAPMA01B, AB01, subnumber

SAP Note 27464 - 3.0A System error: Control table TCR00 is not set

Symptom:

Create/Change/display Work center:
Running a workcenter transaction CR01, CR02 or CR03, we get a system error message number CR001:
Control table TCR00 is not set up. Looking at the table TCR00 has one Our system was upgraded from 3.0 FCS to 3.0A.

Cause and prerequisites

In the control data in Customizing of the work center, the integration with the human resource system is not set up.
The transaction does not handle this is in the right way.

Solution
Set up the control data of the work center in Customizing, if you want to use the integration with the human resource system (TA OP09).
You can do this as a workaround, even if you do not want to use the integration.
The bug is corrected with P30K018514 in Version 3.0b.
You can implement this correction by changing the following form in include FC68AE00:

Additional key words

CRC1, CRC2, CRC3, CNR1, CNR2, CNR3, SAPLCRA0

SAP Note 27462 - ERS for external service management

Symptom:

When the user calls up ERS for a purchase order involving services, message 00055 'Required entry not made" appears.

Cause and prerequisites

Program error

Solution
Corrected in release 3.0A. Prior correction:
Copy EXPORT parameter E_PSTYP (reference field EKPO-PSTYP) to function module ME_READ_DOCUMENT_ERS.
Assemble the following corrections:

Additional key words

ERS MRRS RMMR01RS

SAP Note 27461 - CO01 / CO02 : Changing the order quantity

Symptom:

This only applies to components with batch handling.
When you change the order quantity, the gross quantity of the leading batch split record is not adapted.

Cause and prerequisites
Solution
Correction in CO_MK_RESB_AMOUNT :

SAP Note 27460 - CO01: Term. during simple discont. with long text

Symptom:

A termination occurs if the simple discontinuation in the bill of material has a long text.

Cause and prerequisites
Solution
Correction P30K018001 in module LCOSDFB1:

Additional key words

Simple discontinuation

SAP Note 27458 - Changing the time fence is not copied

Symptom:

On the project planning board (transaction CJ27), you can set the time fence via Settings -> Temporal settings -> Time fence for a subsequent call of the capacity planning board. If you enter a time fence in this dialog box and immediately choose "Copy", the data is not copied.

Cause and prerequisites

This is caused by a module in PAI of the screen which is called at the incorrect position.

Solution
Change the flow control of the screen.

SAP Note 27457 - SAPDBA: SAPDBA is already running on this computer

Symptom:

SAPDBA brings the following message when starting ("sapdba ... " ):

SAPDBA is already running on this computer with the same operating system user ID (this usually implies with the same database). This is not recommended because the two processes might use resources concurrently. SAPDBA does not check this.
If you choose to continue you will be responsible for all consequences.

Do you want to continue? (y/n) [n] ==>

Cause and prerequisites

As SAPDBA can interrupt itself if it called several times simultaneously, SAPDBA initially checks the process list to see if it is already running, that is, id the string "sapdba" is contained in the name. If this is the case, it outputs a corresponding warning message.

The warning also appears if SAPDBA is called from a script, whose name contains this string, although SAPDBA itself is only running once.

Solution
The user should decide what to do, depending on the actions planned:
If he is sure that SAPDBA processes will not interfere with each other (for example, if he only wants to start the check functions in the second SAPDBA in the reorganization menu), he can then continue to work with the second SAPDBA (response "... continue ==> y").
However, it is obviously not possible to reorganize the same objects in parallel, or to shut down the database during a reorganization run, and so on. If such actions are planned, you should cancel the second SAPDBA and await termination of the current action in the first SAPDBA (response "... continue ==> n").

Shell scripts that started SAPDBA should not contain the string "sapdba" in their name, to avoid an unnecessary warning message.

You should never rename sapdba so that the string "sapdba" no longer appears in the program name, as the described protective mechanism would then no longer be effective.

Additional key words

sapdba, process list

SAP Note 27453 - Termination program RFDOPR00, transaction FD11

Symptom:

Program for the customer assessment with OI sorted list terminates.
Program RFDOPR00, line 29420 - 29460.
Field overflow for ZVMALVZ field.

Cause and prerequisites
Solution
Corrected in Release 3.0B

Additional key words

RFDOPR00, RFD0PR10

SAP Note 27452 - SAP Asia sapserv7 R3 Remote Connection Information

Symptom:

Customer has a X25 connection, and would like to establish remote
connection to SAP Asia to access R/3 services (eg. OSS, EarlyWatch,
Remote Trobule-shooting and etc..). Customer need the relevant SAP Asia
network parameters for configuration.

Cause and prerequisites

Customer does not know the SAP Asia remote connection router X121 and IP address, and the sapserv7 IP address.

Solution
The typical connection between a customer and SAP network via X25 is as
follows:

customer network <-> x25 <-> SAP router <-> sapserv7 <-> SAP network

As illustrated above, several important parameters are needed by
customer to configure their network (eg. router) to reach SAP network:

- SAP Asia router X121 address : 05252211103
- SAP Asia router IP address : 202.242.2.1 255.255.255.0
- SAP Asia sapserv7 IP address : 194.39.134.35 255.255.255.224

Please configure your router accordingly to connect to sapserv7. Please
also remember to send the Remote Connection Data Sheet to SAP Asia
OSS/Remote Connection HOTLINE Fax: (65)-2491718 before connecting.
This will allow us to configure our router accordingly to reach
your network. If you have questions, feel free to call (65)-2491700

Additional key words

sapserv7, OSS, remote connection, X25.

SAP Note 27450 - Duplicate activity numbers in networks

Symptom:

In a network, all activities must have a unique number. When inserting an activity, you can assign an activity number which already exists.

Cause and prerequisites

The system does not check whether an activity number already exists.

Solution
Include check.

SAP Note 27449 - Procedure for Migration Coding Block 2.1/2.2 ->3.0

Symptom:

When migrating from Release 2.1 or 2.2 to Release 3.0, what do you need to pay attention to if you added customer specific additional account assignments to SAP tables according to Note 22204?

In this note a detailed description of the procedures involved as agreed with the Basis department will be described and updated continuously.

Additions
02/20/96: Include customer append with 2.1/2.2 fields in ACCIT (1)
03/15/96: If required, include entry in TMODU per 2.1/2.2 customer field (2)
03/19/96: Include customer append with 2.1/2.2 fields in COBL_08 (3)
07/19/96: Addtnl customer append structures for 3.0 functionality (4)
08/23/96: Upgrade to 3.0D/3.0E does not activate append structures (5)

Beginning with Release 3.0D the manual additions (1)-(3) are no longer applicable.
The program RGUCBL01 is started in the FI-SL XPRAs and transfers the above described additions (1)-(3).

Beginning with Release 3.0E, the program RGUCBL00 exists. This program selectively stores and activates append structures with the migrated account assignment dimensions for the selected areas in the Repository.

The program RGUCBL00 is available on sapserv3 for Release 3.0D. Please see note 43077.

The note 39278 is only relevant for Releases 3.0A/B/C.

Additional key words

Coding block, ZA includes, CI includes, CI_COBL, CI_COBL_BI,
Additional account assignments, migration

Cause and prerequisites
Solution
With regards to the migration, you should always accept the suggestions from SAP and -as suggested- create your own append structure per table for the customer-specific fields during a SPDD comparison.

The names of the append structures should always be in the customer name range. As a suggestion for an append to table , ZA is generated (truncated after 10 characters). Therefore, most names of appends begin with ZA.

I M P O R T A N T! ------------------------------- Addition 02/20/96
You MUST manually include the customer-specific fields defined in 2.1/2.2 as an append structure (suggestion: ZAACCIT) in the structure ACCIT (= RW interface, item information), so that the information for the update is made generally available.

The log of the XPRA RGUXI30A also tells you if ACCIT fields are missing; the XPRA RGUXI30A, amongst other things, converts the field movements from BSEG to ACCIT.

If the fields are not included in ACCIT, the FI-SL update cannot take into account all the dimensions you require; that is, the level of detail does not meet your requirements.
I M P O R T A N T! --------------------------------- Addition 02/20/96

---------------------------------------------------- Addition 03/15/96
If necessary include an entry in table TMODU per 2.1/2.2 customer field.
TMODU is the table for the where-used list of field names - MODIF1.
The table TMODU is used in the FI interface to interpret the field selection. If entries are missing there, the required entries are not checked. If you depend on this validation of the data, subsequently maintain the entries with the following content:
TMODU-FAUNA = 'SKB1-FAUS1',
TMODU-MODIF =
TMODU-TABNM = 'BSEG',
TMODU-FELDN = ,
TMODU-KOART = 'S',
TMODU-UMSKS = ' ',
TMODU-XRELE = 'X'.
--------------------------------------------------- Addition 03/15/1996

--------------------------------------------------- Addition 03/19/1996
You should also manually include the customer fields defined in 2.1/2.2 as an append structure in the structure COBL_O8 (suggestion ZACOBL_08), so that the information based on the invoice verification can be taken automatically from the purchase order.

You will be made aware of the effect during the migration when you compare the old and new status of program MM08RFK0. Select the SAP standard in the program MM08RFK0 and limit the structure COBL_08 with a new customer append structure.

If you do not include the fields in a COBL_08 append structure, an automatic transfer of the customer-defined account assignment fields from the purchase order to the invoice verification does not take place.
--------------------------------------------------- Addition 03/19/1996

--------------------------------------------------- Addition 07/19/1996
Detailed analysis has shown that in Release 3.0 there is approximately twenty structures which contain the customer include CI_COBL, but not the migrated customer defined account assignment dimensions from 2.1/2.2.
To ensure that the entire 3.0 functionality also exists for the (after the migration to 3.0) additional account assignments defined in Release 2.1/2.2 according to note 22204, you must store append structures in the dictionary for the required areas:

- Accounting interface : ACCIT, ACCTIT
- Batch input FI-Accounting : ZBSEG (BBSEG), see note 44920
- FI: SAPF181-Profit. seg. adj. : COBL_CUST
- FI Fast entry : SAPOS
- Parking documents (FI/MM) : VBSEG, VBSEGS
- Purchasing (MM-PUR) : ESKN, VSEBKN_CN
- Ivntry Mgmt (MM-IM) : ACCIT_MB, IMSEG
- Invoic verification (MM-IV) : COBL_08,EK08BN,EK08RN,DRSEG,RBSEG
- FI Document changes for CO : BSEGCO, BSEGCO_CHG
- CO-Archiving : COEP_ONLY
- CO-Line item reporting : RKPOS, see note 33846
- ALE: User fields for distrbtn : SAP_COBL.

Beginning with Release 3.0E, the program RGUCBL00 offers the possibility of automatically creating the customer append structures for the selected areas during execution.
Additional documentation can be found in:
- Note 43077 (=migrated customer-defined account assignment dimensions missing in 3.0
- 3.0e Release Note FI_GLX_30E_RGUCBL00
- Documentation on report RGUCBL00
--------------------------------------------------- Addition 19.07.1996

--------------------------------------------------- Addition 19.07.1996
During the upgrade to 3.0D/3.0E, the append structures written from "XPRA" RGUXI30A/RGUCBL01 are unfortunately not activated. Therefore, you must manually maintain the FI-SL field movements in order to permit the data to be updated at the required level of detail.

You must carry out the following steps:
1.) Transaction SE11: Maintain an active append structure for ACCIT
2.) Transaction GCF2: Maintain FI-SL field movements

Additional details -> see note 47482 (Upgrade: Upgrade...)
--------------------------------------------------- Addition 23.08.1996

The user can continue to work as usual after the migration.

Short-term strategy:
In order to use the complete 3.0 range of functionality for migrated fields, all required append structures (see Note 43077) must have been created.

Long-term strategy:
In Release 3.0, a procedure is offered which allows the user to transfer coding block enhancements (quality: modification) made in Release 2.1/ 2.2 to the 3.0 SAP standard.

More information pertaining to this will be found in this note - as soon as it is available.

SAP Note 27441 - Unnecessary accessing of KNVL

Symptom:

Unnecessary accesses are made to the file KNVL
1) Accesses without a customer number
2) Accesses for taxes JR1, JR2..... although the license check is
only to be performed for the carrier condition UTXJ
3) Accesses, although no licenses at all are needed in the system

Cause and prerequisites
Solution
Re 1) and 2):

Corrected in 2.2G/3.0B

Re 3):

Change the condition category of the affected tax condition types as described in note 19195 to blank or '$' depending on whether you use the Jurisdiction Code or not.

Make the program change described below.

Additional key words

VF01 VA01 tax condition UTX1 UTXJ MWST XJR1 JR1

SAP Note 27439 - AS02 - Termination AA698 Error with investment support

Symptom:

1. You receive termination AA698 when changing an asset, when the investment key is entered and the asset is already posted, and you save without going to the screen for the depreciation areas.

• 2. When deleting an investment key, the investment support depreciation area (ANLB) remains, but ANLC is missing. This results in error AA698 - ANLB is not the same as ANLC - when depreciation is recalculated.
  This can occur if the depreciation has takeover of parameters that is identical to another area.

• 3. Deleting by positioning the cursor on the investment key and using the function 'Delete inv. key' does not work. This function was possible before Release 3.0. Now you have to click on the button before the investment key, in order to carry out the delete function.

Cause and prerequisites

Program error

Solution
Corrected in Release 3.0B
1. Enter the investment key, go to the depreciation area screen and then save.
2. Check the assets to see if ANLCs for the investment support area are deleted, but the ANLB record still exists. When you localize the error, you have to delete the ANLB record with a correction program. --> See Source code corrections.
3. The function is active again in 3.0B. Until then, you can delete the investment key by selecting the 'delete button' before the investment key, and using the function 'delete inv. key'.
All of these problems are corrected in 3.0B.

Additional key words

AS92, AS91, Investment support, INVSL, AS01, AS02, Master data

SAP Note 27436 - Missing LIS transactions: access from the IMG

Symptom:

When you access some setup transactions in the Logistics Information System (LIS), program terminations can occur.

Cause and prerequisites
Solution
The report names of reports belonging to missing transactions can be found in the respective IMG texts. Determine the report name and start the program in each case via SYSTEM -> SERVICES -> REPORTING.
Examples

Action Abending Transaction Belonging Report

Setup Sales Documents OLI7 RMCVNEUA
Setup Deliveries OLI8 RMCVNEUL
Setup Invoices OLI9 RMCVNEUF
Setup Purchasing OLI3 RMCENEUA
Setup PCO/Warehouse OLI2 RMCBNEUB
Setup Production OLI4 RMCFNEUA
Setup PMCO OLI5 RIPMCO00
Setup PM-IS OLI6 RIPMS000

You can also maintain the respective transactions.
Tools -> ABAP/4 Workbench -> Development -> Other tools -> Transactions -> Transaction code. Enter the transaction name and select 'Reprt transaction'. Enter MCS as development class after you have maintained the data.

Additional key words

Setup of statistical data, setup, VIS,PMIS OLI2, OLI3, OLI4, OLI5, OLI6, OLI7, OLI8, OLI9, NPRT

SAP Note 27435 - 300: Layout set QC02 and standard texts QCERT* are missing

Symptom:

Layout set QC02 and standard texts QCERT* are missing in FCS Release 300.
Layout sets QM_* and standard texts QM_* are missing in FCS Release 300.

Cause and prerequisites

This is probably a delivery problem in Release 300.

Solution

1. Please check whether the layout sets and the standard texts exist in client 000. If yes, you can copy them with "Utilities -> Copy from client" in transactions SE71 or SO10 into your productive client (all languages).

2. If the layout sets and the standard texts are also missing in client 000, you have to pick up these objects via ftp from SAP and import them into your system. Please see note 13719 on how to do this. The corresponding files are on sapserv3 and sapserv4 at SAP AG in the directory /dist/permanent/QM_layout_sets.

3. These are the versions from Release 3.0A. Because of the naming convention (note 25804), some objects were renamed in 3.0A. Therefore copy layout set QM_QCERT_01 and the standard texts QM_QCERT* into your productive client (all languages). You do not require layout set QC02 and standard texts QCERT* (Release level 3.00); for this reason they are not stored in the above directory.

4. If necessary, replace the entry for layout set QC02 with layout set QM_QCERT_01 in your certificate profiles.

Additional key words

Certificates
Quality certificates
Certificate profile
Transactions QC01, QC02
Quality notifications
Print
Transactions QM01 QM02 QM03

SAP Note 27433 - KP97: Corrections in Release 2.2G / 3.0B

Symptom:

When copying planning of a cost center to several cost centers, incorrect values might be written.

Cause and prerequisites

Preconditions: The error only occurs when the data of a reference cost center is copied to several cost centers (cost center group) (1:N reference) and 'Reset and overwrite' was chosen.

Solution
Program correction in 3.0B, advance correction as of Release 2.2 as follows:

Additional key words

Key words : Copy planning
Programs : SAPMGPLV
Transactions: KP97

SAP Note 27431 - Plan. data interface CO-CCA termination GI167

Symptom:

The termination GI167 occurs when using the planning data interface
( Document items contained error. No update allowed ).
The error occurs when activity inputs are copied.

Cause and prerequisites

The transfer is carried out into a non-integrated plan version
The error only occurs under 3.0 FCS and 3.0A

Solution
Corrected in 3.0B, advance correction can be installed as follows

Additional key words

The interface is used in the following standard functions, in
which the errors can occur:
- KP97: Copy version (cost centers)
- CJ9B: Copy plan (projects)
- KP96: Create beginning inventory
- AR13 (RAKOPL01): Transfer depreciation/interest
- KPHR (RKHRPLAN): Transfer personnel costs
- KO14: Copy version (order planning)
- KSPP: Transfer disposition SOP

SAP Note 27430 - Leading zeros on the payment accompanying list

Symptom:

In the payment accompanying list, the open item account number of the business partner (vendor/customer number) is printed without leading zeros, those of an alternative payee/payer is printed with leading zeros.

Cause and prerequisites

The alpha conversion is not defined for the output field.

Solution
Error is corrected in Release 3.0B. Advance correction is possible.

Additional key words

RFFOD__U, RFFOD__S, RFFOD__L, RFFOUS_C and so on

SAP Note 27429 - Liquidity forecast - Cust. information system

Symptom:

With the liquidity forecast for a vendor group, the vendor information system is to be called up but the customer information system is accessed instead.

Cause and prerequisites

Customer incorrectly maintained

Solution
Since it is not determined anywhere with the planning groups, whether the group belongs to the customers or to the vendors, the report searches for a customer who in the master record has the planning group you chose for the liquidity forecast. If the report finds a customer in any company code, it assumes that the selected planning group is a customer planning group and thus also call up the customer information system. If no customer is found, the vendor information system is called up.
Thus, the customer must be determined, in whose master record the vendor planning group is entered in order to assign a correct planning group to it. The easiest thing to do is to determine the customer(s) by means of the transaction SE16, to enter KNB1 as table name and then, with the accrual/deferral 'planning group', to enter the group you wanted to choose with the liquidity forecast.

Additional key words

Cash management position RFDRRANZ RFKRRANZ RFTS7000 FF70

SAP Note 27428 - SAPDBA: SAP R/3 naming conventions for DB data files

Symptom:

When generating, enhancing or reorganizing tablespaces with data files, SAP database administration tools (for example, br* tools and sapdba) report the non-adherence to SAP conventions for names, directories or symbolic links to database files.

Other terms

File name, directory, symbolic link, SAP convention, convention

Reason and Prerequisites

You entered a directory name or file name that does not correspond to the SAP conventions, or you failed to adhere to the SAP conventions when you manually enhanced or reorganized tablespaces.

Solution
The following rules describe the naming conventions for R/3 database files, that is, the file names and path names in the database (V$DATAFILE, DBA_DATA_FILES) must be defined in accordance with these rules.


SAP conventions for ORACLE database files:
===========================================

For UNIX:
---------

Main directory:

For FSys: $SAPDATA_HOME/sapdata[n]
For RawD: $SAPDATA_HOME/sapraw

Data file:

For FSys: $SAPDATA_HOME/sapdata[n]/[tsp]_[m]/[tsp].data[m]
For RawD: $SAPDATA_HOME/sapraw/[tsp]_[m]

Symbolic link:

[tsp]_[m] may (for FSys) or must (for RawB) be a symbolic link:

For FSys: $SAPDATA_HOME/sapdata[n]/[tsp]_[m] -> target_directory
For RawD: $SAPDATA_HOME/sapraw/[tsp]_[m] -> /dev/rdsk/[db][tsp_m]


For Windows NT:
---------------

[D]:%SAPDATA_HOME%\sapdata[n]\[tsp]_[m]\[tsp].data[m]


Notes:
--------------

In UNIX, pay attention to upper and lower case (the SID in the path is generally in upper case and everything else is in lower case).
FSys = Database files in the file system
RawD = Database files on raw device (only possible in UNIX)

In Windows, no distinction is made between upper case and lower case in file names and path names. You can enter the names in either upper or lower case.

[D]:
Disk drive ID (for Windows only):
Exactly 1 letter (A ... Z), followed by a colon ':'.

$SAPDATA_HOME:
Directory for all sapdata[n] or rawdev.
$ORACLE_HOME is the default value for $SAPDATA_HOME.
For information about the environment variables, see Note 96858 (UNIX) or 94801 (Windows NT).

sapdata{n]:
Main directory in FSys.
The name must contain the string "sapdata" and any natural number n>=1 without preceding zeros. Other characters are not allowed.
For example: "sapdata12"

In Windows, sapdata[n] must be a directory (not a link)!
In UNIX, sapdata[n] can be a symbolic link to any other directory (but not a link to another link to a directory, that is, no chained links), but sapdata[n] are usually mount points, not symbolic links.

sapraw:
Main directory in RawD.
When you use raw devices (UNIX only), you must use the "sapraw" directory instead of sapdata[n]. No other name is permitted. "sapraw" cannot be a link itself. It only contains the symbolic links [tsp]_[m] to the raw devices.

[tsp]_[m]:
Subdirectory of sapdata[n] for the data file or the link to the data file directory or link in sapraw to the raw device.
Chained links (multiple links) are not permitted.
[tsp] is actually any name. However, it should always be a unique, shortened form of the tablespace name.
m is the consecutive number within the tablespace. This is any natural number, m>=1, without preceding zeros.
[tsp] and [m] must (except in the case of RawD) be identical to the corresponding values in the subsequent file name [tsp].data[m].
Example for tablespace "PSAPBTABD": "btabd_10"

[tsp].data[m]:
File name (only in the case of file systems). Links are not permitted.
[tsp] and [m] are identical to the corresponding values in the name [tsp]_[m].
Example for tablespace "PSAPBTABD": "btabd.data10"

target_directory:
Any target directory of a symbolic link (only UNIX with FSys). It cannot be a link itself and it contains one or more data files for a database.
The name of the target_directory cannot contain the string "sapraw" and it cannot start with "/dev/".
For example: "/data"

"/dev/rdsk/[db][tsp]_[m]":
Example for a raw device name (entire path, UNIX only). (depending on the UNIX-BS, '/dev/rdsk' might have a different name)
The raw device is always the target of a symbolic link "$SAPDATA_HOME/sapraw/[tsp]_[m]".
[db] is the name of the database.
[tsp]_[m] in the raw device name (link target) and the link name are identical.
The link target must not contain the string "sapraw".
For example: "/oracle/C11/sapraw/btabd_10" -> "/dev/rdsk/c11btabd_10"

Caution:
--------
You are allowed to page out temporary tablespaces in separate file systems that are mounted under the directories saptemp[n] (n = 1...99), for example $SAPDATA_HOME/saptemp1/temp_1/temp.data1.
This allows you to manage and monitor sparse files, which are used by temporary tablespaces.
These configurations are supported by BR*Tools 7.00 as of Patch 20.

SAP Note 27427 - Proc. assess. cycle maint.: Flds. do not appear

Symptom:

Description: The PROZESS, KOSTEN-TRÄGER fields relevant for the process assessment do not appear in the cycle maintenance of the process assessment.
Transactions: CPP7, CPP8, CPP9, CPPA

Additional key words

Allocation CO-ABC

Cause and prerequisites

Program error - error when validating the version

Solution
Please install the following correction.

Description: The PROZESS, KOSTEN-TRÄGER fields relevant for the process assessment do not appear in the cycle maintenance of the process assessment.
Transactions: CPP7, CPP8, CPP9, CPPA

Additional key words

Allocation CO-ABC

Cause and prerequisites

Program error - error when validating the version

Solution
Please install the following correction.

Description: The PROZESS, KOSTEN-TRÄGER fields relevant for the process assessment do not appear in the cycle maintenance of the process assessment.
Transactions: CPP7, CPP8, CPP9, CPPA

Cause and prerequisites

Program error - error when validating the version

Solution
Please install the following correction.

Additional key words

Allocation CO-ABC

SAP Note 27426 - Deprec. recalc. does not consider all fixed assets

Symptom:

The depreciation recalculation does not consider all fixed assets.

Cause and prerequisites

Program error.
Preconditions: Shortened fiscal year with depreciation reduction.

Solution
Corrected in 2.2H and 3.0B.
Advance correction in LAFARF20 (syntax check only in SAPLAFAR!!).

Additional key words

RAAFAR00, shortened fiscal year, reduction

SAP Note 27421 - RIMPLA00: Create select. para. 'Blocked for calls'

Symptom:

Symptom

The selection parameter 'Preventive maintenance plan blocked for calls' is missing when editing the list.

Cause and prerequisites

Selection parameter was not considered in the program.

Solution
Please implement correction P30K018273 in your system.

SAP Note 27419 - PM order: Automatic distribution rule only GES

Symptom:

The automatic distribution rule for periodic settlement was not created.

Cause and prerequisites

Table delivery problem

Solution
P30K018258

SAP Note 27416 - Standard Hierarchy Repair

Symptom:

Error message: None
Description:
The standard hierarchy (cost centers, profit centers, business processes) is inconsistent:

• Nodes are missing in the hierarchy or nodes are included which do not belong to the hierarchy.

• Individual values (cost centers, profit centers, business processes) are missing or too many individual values are included or they are assigned to an incorrect node.

Transactions: KSH1 KCH1 CPH1 KSH1 KCH1 CPH1
KSH2 KCH2 CPH2
KSH3 KCH3 CPH3
Program name: SAPLGRZZ

Cause and prerequisites

In general, inconsistent data imports from other clients or systems (client copy; up to and including Release 2.2: transports of Report Writer objects linked to standard hierarchies; object imports from different clients/systems).
With client copy, "empty" standard hierarchies are created in a client which does not contain master data.
Important note: The assignment between master data and standard hierarchy is carried out exclusively when creating/changing master data. Therefore, always transport master data and standard hierarchy only from the system in which this data was created.

Solution

There are different options for repairing hierarchies.
If the structure of the standard hierarchy is correct but does not contain individual values (cost centers, profit centers, or business processes) or includes them at an incorrect location, use the appropriate master data transactions ("Change") for the repair. If an incorrect node is entered in the master record (field hierarchy area), you must enter and save the correct node in the master record. If, however, the correct node is specified in the master record but this hierarchy node does not contain the value, you must make the master record change twice. The first time, you enter any other hierarchy node and save the change. You then enter the original node again and save this change as well.
Remark:
Values contained in the hierarchy for which no master record exists cannot be removed from the hierarchy this way.
If, however, your standard hierarchy has greater discrepancies both concerning the hierarchy structure and with respect to the contained individual values, you must choose another procedure:

1. Check whether there is another client in which the respective standard hierarchy exists correctly. On the condition that the quantity of the master records, including their assignments to the hierarchy nodes, is identical, you can import the respective standard hierarchy from the other client.

To do this, use the Report Writer transport tools (transaction GS02 -> "Environment -> Transport ..."). The "Copy from client" function is available within the same system. For all systems, you must first write the standard hierarchy to a sequential file in the source system using the "Export" function. Then use the "Import" function in the import system to create the standard hierarchy there again. With the import, existing nodes are overwritten. Missing nodes are created. Unnecessary nodes are not deleted but removed from the standard hierarchy.
The input values for the Report Writer transport tools can be found in note 17940.
Note for Release 2.2: In order to use the Report Writer transport tools successfully, the protection of the standard hierarchy must be cancelled temporarily with a small program in the target system (!) and must be restored again after the import (!!!).
The procedure is described in detail in note 17940.

2. If a correct standard hierarchy does not exist anymore in any system, correction program RKCORRH1 can help repair the standard hierarchy.

You can find the program on SAPSERV3 under the directory
dist/permanent/Note.0027416 .
The file names are
R922685.Q30 und K922685.Q30 "<<< 3.0-Version
R900074.Z2A und K900074.Z2A "<<< 2.2-Version
Have your system administrator import the program into the required system (the procedure is described in note 13719). You must adapt the program code for a 2.1 release (see below). In 2.2 and 3.0, the programs can be run immediately.
The program has the following input parameters:
Controlling area (controlling area in question)
HierTyp (KOSTL-PRZNR-PRCTR) KOSTL (for cost centers)
PRZNR (for business processes, as of 2.2)
PRCTR (for profit center, Release <= 2.2)
RPRCTR (for profit center, Release >= 3.0)
Test run X (yes) / ' ' (no = production run)
(As of Rel. 3.0, the report can be accessed directly via group maintenance).
The program compares the hierarchy areas stored in master data with the standard hierarchy and adapts the hierarchy to master data (NOT vice- versa). The following actions are carried out:

• All incorrect items of individual values in the hierarchy are corrected by INSERT/DELETE, unnecessary values are removed (DELETE), and missing ones are entered in the corresponding node (INSERT).

• If a node is missing in the hierarchy which nevertheless exists in the system, it is inserted again (INSERT); if it does not exist, it is created again (GENERATE). A dummy node (SAP-...) is created at the 2nd location in the hierarchy and all inserted nodes are subordinated to this dummy node.

All actions are written to the log.
An inconsistent hierarchy structure CANNOT be reconstructed by the program. Only the assignment master record/hierarchy area is cleared. You may have to restore the old structure manually with the use of group maintenance. If in this case a group is inserted that still exists in the system, you may have to disconnect (not delete) the end nodes from the group to be inserted prior to inserting. Once the old structure is restored, the nodes under the dummy node can be connected to the correct position and then the dummy node can be deleted.
Start the program in test run first. If you agree with the changes according to the log, execute the program in production run.