10.9.11

SAP Note 27222 - Goods receipt not possible with status 'created'

Symptom:

It is possible to create a purchase order for an order if this order has the status 'created'..
It is not possible to post a goods receipt for a created order.

Cause and prerequisites

No error.
This system setting allows you to order purchases with a longer purchase order period without you being able to post these purchase orders to the order.

Solution
The order must be set to status 'free' before goods receipt since it is now debited with actual costs.
If it is not required to create a purchase order for a created order, this can be determined by means of a user status in the system.

Additional key words

Status control BS007 007(BS) ME21

SAP Note 27216 - Availability: Issue quantity not taken into account

Symptom:

The quantity already issued in the reservation is not taken into account for the availability check in the production order.

Cause and prerequisites

The field "Confirmed quantity for the availability check" (RESB-VMENG) in the reservation was not updated at goods movement.

Solution

If you are using backflushing of components, note 35645 has to be implemented as well.

Expand the following structures in the ABAP/4 Dictionary:

  • Structure RBEFU: Field name Data element
    VFMNG VMENGMaintain reference table RESB and reference field MEINS by double-clicking on VFMNG
    Save and activate the structure.
  • Structures DM07M and SMRES: Field name Data element
    VFMNG VMENGMaintain reference table MSEG and reference field MEINS by double-clicking on VFMNG.
    Save and activate the structures.
Use transaction se37 to maintain a new import parameter in function module MB_FILL_MRES_ENQUEUE_TABLE:
Parameter Struct./Field
VFMNG DM07M-VFMNG
Save function module.

Attention: If you use release 2.2A - 2.2D, please now make the
corrections described in Note 21459
because the fields newly defined there are also required
for the following correction.

Then make the following source code corrections:
(Please note: This Note has been created on the basis of 2.2G. If the
following coding contains lines which do not exist in
Release 2.2 and are not marked as 'new', you can ignore
them.

Additional key words

CO06, backorder processing

SAP Note 27214 - Compatibility of reports in reporting

Symptom:

When including a new, possibly user-defined Report Writer report into the user's list, it is indeed included in the list but the indicator "not compatible" appears after the report group.
The indicator states that the entered report cannot be executed with the standard interface of the report selection.
This occurs, for example, if the report does not contain a variable for the report object. In Profit Center Accounting, for instance, the indicator is set if the corresponding report does not contain a variable for profit center but the profit centers are linked in the report.
Nevertheless, the report can still be executed with the help of the report selection in the respective application; it is then processed with the standard request screen of the Report Writer. In this case, no report functionality is lost as compared to the common user interface.

Cause and prerequisites
Solution

If you are willing to do without the functionality of the standard interface, you can copy your report without any changes into the report list.
However, should you want the new functionality of the standard interface for your report, you should check whether you can adapt the report definition to the requirements stated below.

Criteria for the compatibility of Report Writer reports for the standard interface for the report selection:

  • The report was created for table GLPCT.
  • A maximum of 2 value variables are used for the dimension Planned or Fixed price version (RVERS).
  • A maximum of 4 value variables may be used for the dimension period (RPMAX) in the report.
  • A maximum of 4 variables may be used for the dimension Fiscal year (RYEAR).
  • Either 1 value variable must exist for the dimension Controlling area (KOKRS) or one variable for the company code (RBUKRS).
  • The dimension Profit center (RPRCTR) must be used in the report. However, there may only be a maximum of two set variables for this.
  • The same applies for the dimension Revenue/cost element for which also only a maximum of two set variables (RACCT) may exist.
Additional key words

- Standard interface for accessing reports SAPLPC10 / 1000
- Maintenance report list, transaction 0KEH

SAP Note 27212 - No output found despite condition record

Symptom:

Although appropriate condition records were created in output control, the message determination is still unsuccessful.

Additional key words
Cause and prerequisites

In the details of the output type, the flag 'condition access' must be selected in the general data, otherwise, the message determination will not become active via condition technique.
In SD, output is otherwise determined using the customer master.

Solution
Set the checkbox 'condition access' in the Customizing of the output type.

SAP Note 27202 - Eval.amnt in line item display is 0 for G/L accts

Symptom:

The value 0 is constantly displayed in the 'Evaluated amount' field (BWWRT) of the line item display for G/L accounts managed on an open item basis, even if the items were evaluated with updating in the document.

Cause and prerequisites

This case was not allowed for in the program.

Solution
Corrected as of 2.2G and 3.0B

Additional key words

RFEPOS00 FBL3 FBL4 Line item display SAPF100

SAP Note 27200 - BOM item text in the production order

Symptom:

If two lines of text were maintained in a BOM item, only one line was displayed in the production order.

Cause and prerequisites
Solution
Correction

Additional key words

Item text

SAP Note 27198 - Inspection lot display from production order

Symptom:

If you created an inspection lot for a production order, you could not display this inspection lot from the order via the environment menu.

Cause and prerequisites

Missing entries in tables T354S and T354T

Solution
The following entries are necessary: T354T: SAPLCO10 CAUFVD-PRUEFLOS QA03
T354S: CAUFVD-PRUEFLOS 1 QLS CAUFVD-PRUEFLOS

SAP Note 27197 - Missing storage location in billing item

Symptom:

A storage location only entered in the delivery is not transferred to the billing item

Cause and prerequisites
Solution
Corrected in 2.2G/3.0B

Additional key words

VBRP-LGORT

SAP Note 27196 - Cost VBRP-WAVWR not filled

Symptom:

The field cost (VBRP-WAVWR) in the billing item is not filled.

Cause and prerequisites

A group condition is not contained under the item conditions.

Solution
This is corrected in Releases 2.2G/3.0B.
Create the correction program ZZDAMR10 as in the following source code in the system and start it afterwards.
This program determines the incorrect billing documents and corrects them.
The program can be started in test mode.
If you use a condition type other than VPRS for the cost in your system, you nned to adjust the corresponding program positions.

Additional key words

VF01, CO-PA, statistics, cost

SAP Note 27194 - BRBACKUP FM: BR074W BRCONNECT call failed.

Symptom:

The following warnings are displayed at the end of a backup:
BR252W Function kill failed for 'nnnn:mm' at location BrKill-3
BR253W errno 3: No such process
BR074W BRCONNECT call failed.
In the directory where BRBACKUP was started, there is often a core file that belongs to the BRCONNECT program.

Caution:
This error causes a programmed termination of the backup with BACKINT (mostly due to a timeout), if BRBACKUP was called with the parameter/option
backup_dev_type = util_file_online / -d util_file_online

Cause and prerequisites

Non-SAP problem - termination in Oracle code.

Solution
A new version of BRCONNECT can be downloaded from sapserv*. Refer to Notes 12741 and 19466 for information on downloading patches.

SAP Note 27193 - Partner: TABLE_ILLEGAL_STATEMENT IVBPA2

Symptom:

When selecting the transaction 'Partner of a function' (function Proceed), the dump: TABLE_ILLEGAL_STATEMENT occurs for table IVBPA2.

Cause and prerequisites

Program error

Solution
Program correction

SAP Note 27191 - Credit control area data - payer

Symptom:

When creating sales orders without reselecting a transaction, the credit control area data of the payer is not refilled. Thus, an unwanted invoice split can occur in billing.

Cause and prerequisites

Program error.

Solution
Program correction. Change or insert the lines indicated by <------.

Additional key words

VA01, credit control area

SAP Note 27190 - Term. when calling object overview from comp. list

Symptom:

If you call the object overview from the general component overview, an abnormal termination occurs. This only occurs if the object overview was not already called before from another screen and if the operation overview was not yet called as well.

Cause and prerequisites

Program error

Solution
Insert a new FORM routine in Include LCOMKFL1 (see "Source code corrections") and change one entry in table TC02. Entry TC02:
Old: SAPLCOMK * * UVLI LST_OVERVIEW_OBJ_CREATE SAPLCOVG
New: SAPLCOMK * * UVLI LST_LVARI_CREATE SAPLCOMK
Caution: Table TC02 is client-specific !!!

Additional key words

Production order, overview version

SAP Note 27187 - MR01: Changing the account assignment

Symptom:

Key words: MR01, purchase order assigned to an account, screen 202.
Changing the account assignment.

Error when changing account assignment.
The purchase order contains several items assigned to an account and a goods receipt is only expected for some of the items.
Depending on whether you expect a goods receipt for the last item, you may or may not change the account assignment of the item from the overview screen (screen 202).
For example: Purchase order with two items. Overview screen, correction ON, Extras --> Account assignment
Item 1 with GR posting, item 2 without GR posting
----> You can change the account assignment of both items
Item 1 without GR posting, item 2 with GR posting
----> You cannot change the account assignment of any of the items.
Further symptom:
For positions with goods-receipt-based invoice verification, the reference to the GR document in the purchase order history might get confused. This may cause problems in the following invoices or credit memos: in the case of invoices, the full quantities are proposed again, for credit memos, no default value is set.

Cause and prerequisites

Error in the source code.

Solution
Corrected in Release 3.0B. You can make the following advance corrections.
You can correct the purchase order history using program RM06HL20 (on SAPSERV3 in directory /general/R3server/abap/note.0027187). The report selects not all possible cases but only the most frequent one, in which exactly one goods receipt and one invoice receipt do exist.

SAP Note 27185 - Collective order with by-product

Symptom:

You could not create an order for a material with by-product production and collective order. On the screen for maintaining the distribution rules, the following message is displayed: 'Object type & not permitted'.

Cause and prerequisites
Solution
Correction

Additional key words

CO01, direct production

SAP Note 27184 - Exception condition "INVALID_PA_TYPE" raised

Symptom:

When you execute a report from Release 2.1 or 2.2, you get a dump with the message "INVALID_PA_TYPE".
When you execute form reports which have already been converted, you get an abend with the message KH125.

Cause and prerequisites

1.) Program error, PA_TYPE is not set.
2.) You still cannot execute form reports after correction 1.) because all the forms (row/column structures) from Releases 2.1 and 2.2 are empty in 3.0 (FCS) (due to a transport error).

Solution
1.) Insert the correction below.
2.) (i) Insert note 25284
(ii) Transport the forms from Release 2.2 again (see part I of note 24342).
(iii) Call up XPRAS COXMKE53.
(iv) Regenerate the reports in Release 3.0: Transadtion KEMO, start the report by using the function "Regenerate".
The problem no longer occurs in Release 3.0A.

Additional key words

KE30, conversion,

SAP Note 27183 - EDI incoming order: Screen determination

Symptom:

In EDI incoming orders, the double-line entry overview (screen SAPMV45A number 400) is fixed in the program and is not determined using table 185V.

Cause and prerequisites
Solution
Corrrection P30K017411 in function module IDOC_INPUT_ORDERS

SAP Note 27181 - Deadlock when updating, despite note 68476

Symptom:

Despite the existence of the database indices according to note 68476, the INFORMIX ISAM error:
INF143 "deadlock detected"
occurs in connection with the Informix SQL errors
INF240 "Could not delete a row"
INF244 "Could not do a physical-order read to fetch next row"
INF246 "Could not do an indexed read to get the next row"
INF271 "Could not insert new row into the table"
during updates on one of the tables VBLOG, GLT0, RFBLG and REGUV.

Cause and prerequisites

There are an unusually large number of entries (more than 500) in the table VBLOG (release < 3.0A) or in the transparent tables VBHDR, VBMOD and VBDATA.

Solution

The remedy is to update or delete the records, having first checked with the users (SM13).

The most sensible procedure is as follows:

    1. Update Statistics on the affected table(s)

    In order to make the best use of the access path when processing, the information for the optimizer should be updated. Use the tool 'sapdba' to do this,
    For example
    sapdba -updstat -threshold 0 -t vbmod .
    (See note 42574).

    Ensure that the correct index is used:
      a) If the SAP Release is prior to 3.0A and the tables VBHDR, VBMOD and VBDATA are not transparent, execute the following statements with 'dbaccess'

      set explain on;
      select * from vblog where vbkey = 'abc12345';
      b) If the SAP Release is greater than or equal to 3.0A or the tables VBHDR, VBMOD and VBDATA are transparent, execute the following statements with 'dbaccess'

      set explain on;
      select * from vbmod where vbkey = 'abc12345';
      select * from vbdata where vbkey = 'abc12345';

The query plan for all of these queries (file sqexplain.out) must always contain the field 'vbkey' as the index used:

QUERY:
------
........

1) sapr3.vb...: INDEX PATH
(1) Index Keys: vbkey

........

    2. Reduce the number of update programs for this action

    It has proved to be advantageous to avoid starting this action when the system load is high. For the purpose of this action, you are recommended to reduce the number of update processes to 1 or 2.
    3. After the number of entries in the tables has returned to a 'normal' level again (< 100), another Update Statistics should be executed.
4. The number of update processes should be reduced as far as possible to a suitable number.

SAP Note 27179 - IN-Clause versus OR

Symptom:

Performance problems, observations

Cause and prerequisites

Optimizers and indices

Solution
Change from IN statements to OR

Additional key words

IN-Clause, OR

SAP Note 27178 - oncheck -cc: "Unknown error message 0"

Symptom:

The database utility 'oncheck' returns the following error message when executing 'oncheck -cc' on an SAP database:
"Unknown error message 0."

Cause and prerequisites

'oncheck -cc' checks the consistency of the INFORMIX system catalog tables.
If one of these system tables is found to be in "Update" access mode during this consistency check, due to an application transaction, the 'oncheck -cc' utility terminates with the above error message. This message is WRONG. It should state "Lock has been denied" instead. This improper message is scheduled to be fixed in an upcoming release of Informix.

Solution
'oncheck -cc' can only be executed, if no system catalog tables are blocked by application transactions.
To ensure that the consistency check using 'oncheck -cc' does not terminate with the above error message, the R/3 work processes must be stopped (stopsap r3) so that no further change transactions can occur on the system catalog tables.
OR an alternative solution to this problem is to try running oncheck -cc repeatdely until no error is returned. This can be accomplished by running oncheck -cc thru a shell script and trapping for this error. However, pleae be aware that the probability of an errror being returned increases along with R3 activity. One should use this approach during slack time periods only. It should be noted that a few R3 sites are using this approach with success during slack periods.

SAP Note 27176 - No record in payroll cluster if split in last day

Symptom:

No split of the payroll results will be performed if an event, which has been defined as to produce a split of the payroll results in the table T530 (field PERSP), takes place the last day of the payroll period.

Cause and prerequisites

The conditions to loop at the internal table SDATES are GT APER-BEGDA and LT APER-ENDDA.

Solution
The conditions to loop at the internal table SDATES should be GT APER-BEGDA and LE APER-ENDDA.

Additional key words

RPCHRT00 RPCHRT09 Split Payroll Result RPCALC*0
RPCALCA0 RPCALCB0 RPCALCC0 RPCALCD0 RPCALCE0 RPCALCF0 RPCALCG0 RPCALCJ0 RPCALCK0 RPCALCM0 RPCALCN0 RPCALCU0

SAP Note 27175 - Error during goods movements from backflushing

Symptom:

Various errors during automatic goods movements:
- backflushed items are not taken into account
- automatic goods receipt is not executed

Cause and prerequisites

Program error in different programs and function modules

Solution
No preliminary solution possible before release 3.0B

Additional key words

CO11, CO12, material overview

SAP Note 27169 - Subcontract order: Rounding error in component qty

Symptom:

A bill of material contains a component with a non-integral number of pieces for each unit of measure. (example: 1 pc of material B is needed for 10 KG of material A). When you create a subcontract order, the required component quantity is rounded correctly. However, if you change the quantity ordered, the component quantity is adjusted on the basis of this rounded quantity. As a result, the rounding becomes more and more inaccurate, that is, if you repeatedly change the quantity it significantly differs from the quantity defined in the bill of material.

Cause and prerequisites

The effect cannot be avoided in the current implementation. The conversion routine cannot always access the initial BOM because the component quantities can be changed manually in the purchase order. Since the unrounded quantity is not stored internally (it would also have to be written to the database), rounding errors cannot be avoided. For reasons of performance, you also cannot always execute a new BOM explosion in the purchase order. A satisfactory solution would be extremely complicated.

Solution
However, the user can start the BOM explosion manually and correct the resulting rounding errors when changing the purchase order quantity. For this, the function Item -> Components -> New BOM explosion is available (please also see note 16029).

Additional key words

Subcontracting component
Subcontract requisition, subcontractor scheduling agreement
ME21, ME22, ME51, ME52, ME38

SAP Note 27167 - Missing index on TGORA after upgrade

Symptom:

Primary index on TGORA is missing

Cause and prerequisites

Possible upgrade from 2.2.x to 3.0

Solution
Use SE80 or SE11 in R/3 to create the missing index.

SAP Note 27165 - CO summarization: no summarization of a group

Symptom:

During the summarization of a cost center group which contains only an individual value or only an interval, nothing is summarized. This cost center group is also not displayed in the results list.

Cause and prerequisites

Program error.

Solution
The error is corrected in Release 3.0B.
In the meantime, you can manage by making additional dummy entries in the group or by splitting up the interval.

Additional key words

Cost center summarization KR05

SAP Note 27163 - BOM explosion number from sales order, planning

Symptom:

Materials planning (MD01, MD02, MD03, ...):
The lot size determination groups requirements together (through sales orders or planning) with different BOM explosion numbers. The planned order, the purchase requisition or the delivery schedule for the entire quantity gets the BOM explosion number of the first respective requirements.

Cause and prerequisites

Preconditions:
Different BOM explosion numbers are specified during the planning (planned independent requirements) or in the sales orders for a material.
The time intervals of the quantities are specified in a way that the quantities are grouped together by the lot size determination (This happens, for example, for lot size 'Exact', if there are requirements at the same date.).
Cause:
For BOM explosion numbers, there is no separate materials planning and no inventory management as for the make-to-order production.

Solution
For sales orders, separate planning and inventory management can be achieved by make-to-order production.

If BOM explosion numbers should be used for orders of the make-to-order production only (make-to-order production, project make-to-order or collective order), a modification for Releases 3.0*, 3.1* is possible (see below). The modification (test, maintenance, responsibility at customer's side) leads to BOM explosion numbers being transferred in planned make-to-order productions only.

As of Release 4.0A, the function from the modification is available in the standard system. Here, you can control by means of a flag in plant Customizing (Transaction OPPQ -> BOM explosion) whether the BOM explosion numbers should be used for make-to-order production only.

Additional key words

Grouping

SAP Note 27162 - Line items: Sort criteria incorrect for amounts

Symptom:

Message: The amounts are not displayed correctly.
a) The decimal points in the user master are not taken into account.
b) Amounts without 2 post-decimal places are not displayed correctly.

Example for b)
Sorting is to be done by amounts, and subtotals are to be set up:


Cost center Amount Currency key
-----------------------------------------------------
100.00 "<< --incorrect
-----------------------------------------------------
4711 10000 Lira
4711 10000 Lira
-----------------------------------------------------
20000 Lira

Cause and prerequisites

Program error

Preconditions:
Sorting was done by an amount field and subtotals are displayed.

Solution
As of 2.2H, 2.1M, and 3.0B, the following repair will be in the standard system. Until then, only the following repair helps.

Additional key words

Transactions: KSB1, KSB2, KOB1, KOB2, CJ74, CJ76
Programs: SAPMK21A, SAPMK21O, SAPMK21V, SAPMK21T

SAP Note 27157 - FCS: Copying qualification data from task list

Symptom:

When you include maintenance routings in a maintenance order, the qualification data from the order is not copied into the task list.

Cause and prerequisites

Program error

Solution
Correct program LCOSDFR1
FORM ROUTING_AFVG_BT_INSERT

9.9.11

SAP Note 27154 - Non-stock material in maintenance task lists

Symptom:

You cannot maintain purchasing information for materials of material type NLAG (non-stock material). The item category for material allocations without bill of material (free material allocation) is predefined with L (stock item) in the system and cannot be changed in the present configuration level. In the maintenance order the message occurs that the item type for the material and/or component is not allowed.

Cause and prerequisites

Free material allocation of non-stock material is not provided in the present configuration level.

Solution
The allocation of material of material type NLAG is not possible within the framework of the free material allocation. An allocation of non- stock material can be performed via the usage of maintenance bills of material in maintenance task lists. Therefore, you must maintain items of type N including the required external processing data in your bills of material structure. Then you can allocate them via the structure list within the framework of the material allocation of the maintenace task lists.
In order to remove the resulting error in the maintenance order, please make the following correction in the source code for Releases 3.0 FCS and 3.0A only.

Additional key words

General maintenance task list, equipment routing, maintenance order, free material allocation

SAP Note 27153 - Planning file entries from Inventory Management

Symptom:

In the net change mode, the only materials that are included in the planning run at plant level (MD01), are those which have been given the appropriate entry in the planning file MDVM. This technique aims to reduce the runtime of the planning run. The system only flags those materials that have undergone a change relevant to the planning run and that are active for the planning run.

These flags can also be created in inventory management. However, in the standard system, not every stock change triggers a flag.
This logic differentiates materials that are planned using reorder point procedures from the rest.

For materials that are not planned using reorder point procedures, a flag is always created if no reference to a reservation (purchase order, and so on) exists. If a reference does exist, then a flag is only created for this material if

      a) more than the remaining open 'rest' quantity is received or issued
      b) less than the remaining open 'rest' quantity is received or issued and the final delivery indicator is set.
      c) the requirements date of the reservation lies in the future (not valid for purchase orders)


From Release 3.0C, you can pre-define tolerance values (as a percentage) for points a) and b). Then the system will only flag the material if a quantity deviation exceeds this tolerance value. You make the necessary Customizing settings in Table 440C and you can make the settings plant-specific.

A reorder point material is only flagged if, for a goods receipt, the reorder point was fallen short of before the receipt and if the goods receipt occurs without reference (e.g. to the purchase order).
On the other hand, the system only creates a flag during goods issue, if the reorder point was fallen short of after the issue.

However, some customers want the system to create an entry in the planning file after every stock change. That is, they want the system to create more flags.
You can also make this setting in Customizing in Table T440C in the standard system from Release 3.0C (Transaction OMIY).

Here, note that the following errors still exist when creating planning file entries from inventory management:

    1. Goods movements for make-to-stock and project stocks do not lead to planning file entries.
    2. For goods movements with reference to reservations, a planning file entry is always created. The system reacts as if NO reference to the reservation exists.
Other terms

Planning file entry, planning file, MRP record, inventory management, documentation, special stock, make-to-order

Reason and Prerequisites
    1. This is not programmed.
    2. This is caused by an incorrect naming.
Solution

For Release 2.2, by implementing a modification, you can instruct the system to create a planning file entry for every goods movement.
In Release 3.0, (from Release 3.0C) you will be able to activate the version mentioned above via Customizing (Transaction OMIY).

    1. Correction, see below. Standard from 2.2G and in another form from 3.0C.
    2. Correction, see below. Standard from 2.2G and in another form from 3.0B.

For this correction, note that errors in the central function pool for the creation of planning file entries (SAPLDISP) can cripple the entire SAP logistics system! Therefore, the correction should ideally be implemented outside of the main hours of business.

SAP Note 27152 - Automatic GR: BS027 "'&' is not permitted (&)"

Symptom:

When you confirm a production order, termination message BS027 is displayed: "& is not permitted (&)".

Cause and prerequisites

An automatic goods receipt should be carried out during the confirmation of a production order. In addition, the production order must be assigned to a sales order.

Solution
Correction in program MM07MFK0

Additional key words

Automatic goods receipt, CO11, CO12, CO15, COGI

SAP Note 27151 - MR01: Exch. rate diff. despite 'Fixed exch. rate'

Symptom:

You want to post an invoice for a purchase order with fixed exchange rate. For certain values, an exchange rate difference line is created due to rounding differences. Exchange rate differences, however, may not be posted if the exchange rate is fixed.

Cause and prerequisites

The error is caused by rounding problems.

Solution

This error is corrected in Release 3.1H. Advance corrections:

    1. Only for Release 2.2: Add field KUFIX (data element KUFIX) to the following two structures.

DM08R
EK08R.

    2. Correct the source code according to section headed 'Corrections'.

Additional key words

MR01, MRHG, MRHR, KDF, KUFIX


SAP Note 27148 - 'Incorrect' results of the selection profile

Symptom:

The evaluations of the Production Information System or of the Missing Parts Information System deliver inplausible results when you are using a selection profile which contains 'Or' operations.

Cause and prerequisites

The 'Or' operation of the selection profile uses two statuses negatively (exclusively) that exclude themselves. Ex.: SSTAT: 'FREI - Inclusive- Active'
SSTAT: 'RÜCK - Exclusive- Active' or 'TRÜC - Exclusive - Active'

Expectation: Listing of all released orders which do not have status RÜCK or TRÜC.

System behavior: Listing of all released orders, even those with status RÜCK or TRÜC.

Reason: The negative (exclusive) OR operation of statuses which exclude themselves gives the total quantity.

Solution
AND operation: Ex.: SSTAT: 'FREI - Inclusive - Active'
SSTAT: 'RÜCK - Exclusive - Active'
SSTAT: 'TRÜC - Exclusive - Active'

Additional key words

Shop Floor Information System, Missing Parts Information System
Selection profile
CO20, CO21, CO22, CO23, CO24, CO44 CF11, CF12, CF13

SAP Note 27147 - MRHR: Mult. select., deliv. note w. several vendors

Symptom:

Symptom
Key word: MRHR, multiple selection, delivery note, meherere vendors

When you add invoices with multiple selection, you enter delivery notes which point to different vendors. However, when you select the vendor, none of the purchase order items is proposed and copied.

Cause and prerequisites

Program error.

Solution
Corrected in Release 3.0B. You can make the following advance corrections in Release 2.2.

SAP Note 27144 - Exception NO_OPS when creating a collective order

Symptom:

The production order creation for a collective order terminates if no routing can be determined for underlying orders. Message RAISE EXCEPTION NO_OPS.

Cause and prerequisites

Program error

Solution
P30K015128

Additional key words

Collective order, NO_OPS, BOM explosion

SAP Note 27136 - Purchase requisitions from planning: Text not copied

Symptom:

For purchase requisitions which are created from materials planning (conversion planned order or MRP run), text is not copied from the material master, even if this is in fact specified in Purchasing Customizing (Transaction OMFU, table T165P).

Other terms

ME52, ME53, MD03, MD04, purchase requisition, material text

Reason and Prerequisites

This is not an error. Due to reasons of performance, the system cannot check in the material master whether a text exists each time a purchase requisition is created.

Solution
The text from the material master is displayed in the purchase requisition if the adoption indicator is selected in Customizing (see above). If it is actually to be copied, it must be copied explicitly using Transaction ME52.

SAP Note 27132 - Terminat. during mass activat. of QM insp. data

Symptom:

The mass activation of QM inspection data (transaction QA08) causes a runtime error: "*" cannot be interpreted as a number.

Cause and prerequisites

Cause: Program error
Preconditions: More than 10 materials are being processed

Solution
Carry out the program change given below

Additional key words

RQMQMM00


SAP Note 27131 - ME81 No access to the multiple selection screen

Symptom:

Transaction ME81 (analysis of order values): Whenever you click on one of the arrows on the selection screen (RM06ENHI, screen 1000) to branch into the multiple selection screen, a second selection screen (screen 100) is always displayed instead.

Cause and prerequisites

Program error

Solution
Corrected in 3.0B. You can make the following advance correction by inserting the lines indicated below in the specified program.

SAP Note 27130 - A grouping cannot be defined in the layout

Symptom:

A new grouping can be created when maintaining the layout for a partial screen. It is in fact possible to specify a name and a text. However if you are on "Grouping definition" level and try to create entries using "New entries", the error message "Select one entry only as a heading" is issued.

Cause and prerequisites

At least one of the entries must be selected as a heading. The check continues to be made even if no entries exist.

Solution
Repair in SAPL0C29 (see below)

SAP Note 27127 - Delete splits of an operation

Symptom:

A split operation is scheduled or rescheduled in another work center or the splits are deleted. If the order is scheduled afterwards, the splits remain unchanged.

Cause and prerequisites
Solution
Source code corrections

Additional key words

Planning table
Scheduling

SAP Note 27124 - Cycle lengths <> Multiple of one day or < 1 day

Symptom:

You can define cycle lengths or offset lengths that are not the multiple of one day (for example, cycle length = 36 hours) or that are less than one day. This causes incorrect results during the scheduling because the scheduling is only carried out on a daily basis.

Cause and prerequisites

The query whether the cycle length or offset length is an exact multiple of one day was not programmed so far.

Solution
I. 3.0 System: Please implement correction P30K015379.
II. 2.2/2.1 Systems: Please implement correction P22K009678.
If you are using a 2.1 System, please replace correction P22K009678 by P21K005932.

SAP Note 27122 - Converting customer matchcode IDs to transparent IDs

Symptom:

Customer-defined matchcode IDs are to be converted into transparent IDs.

Cause and prerequisites

see Symptom

Solution
1. Customer wants to convert all matchcode IDs of a matchcode object
into transparent matchcode IDs.
1.1.Use Transaction se14 to delete the physical matchcode pool.
se14->Object name (select matchcodes) -> Edit ->
Select processing type (recommended: "Direct") -> Delete
1.2.Use Transaction SE11 to set the update type of the matchcode ID
to 'I' (= transparent matchcode ID)
1.3.Activate the matchcode ID
1.4 Create a view on the DB: Utilities -> DB utilties -> Create DB
view (online).
1.5.If required, create an index to improve performance of the
matchcode display (see note 17617).

2.Customer wants to convert some but not all matchcode IDs of a
matchcode object into transparent matchcode IDs.
2.1.Use sapmaco to delete the matchcode records for the IDs to be
converted.
se38->sapmaco->Parameter
Matchcode object: Name of the matchcode object, e.g., KOST
Client : * (the matchcode records must be deleted
for all clients !)
Function : DEL
You can choose the remaining parameters as required.
2.2.Proceed as described under 1.2 ff.

Additional key words

Matchcodes

SAP Note 27121 - ME21 ME22 Error messages concerning delivery date

Symptom:

The following errors occured in connection with the warning or error messages relating to the delivery date which the user may receive on the purchase order item detail screen:
1. An error message can be overridden by pressing ENTER twice. This can result in it being possible to save a PO, for example, even though the delivery date is outside the factory calendar (e.g. 1195 instead of 1995, due to a typo).
2. The system does not issue an appropriate warning message when a user converts a requisition whose delivery date lies in the past into a purchase order.

Cause and prerequisites

Program error.

Solution
Corrected as of 3.0B. Advance correction possible by inserting or changing the lines marked below in the specified programs. Please also refer to Note 38795.

Additional key words

ME21, ME22, ME57, ME58, Error message ME039, Error message ME078.

SAP Note 27118 - CO02/IW32 : Display reservation list

Symptom:

In Release 3.0B, the reservation number is carried over onto the component individual screen, making it possible to display the reservation list via 'Environment -> Objects' as in Release 2.2.

Cause and prerequisites

Screen was changed for reasons of space in 3.0

Solution
Correction P30K017022 (re-include RSNUM in screen SAPLCOMD 100)

SAP Note 27117 - E286 manual insurable year < closed fiscal year

Symptom:

For old assets data takeover, a manual insurable value which is translated into a base insurable value and then updated by the system should be entered with a manual maintenance year earlier than the closed fiscal year.
The manual values then determined by the insurance should (must) remain.
The system does not allow a manual maintenance year earlier than the last closed fiscal year and it outputs the error message E286.
Particularly Releases 3.0B and 3.0C.
The entry was allowed but a base value was not determined.

Cause and prerequisites

Function was not taken into account

Solution
This correction makes it possible to enter a manual insurable value together with the original insurance year at the date of old assets data takeover. This is only allowed for old assets data takeover transactions. This function is not supported in the master data maintenance transactions (create,change fixed asset) and is still exited with the error E276.
Please note:
The advance correction is integrated in the standard system as of Release 3.0B. Please note the correction for 3.0B and 3.0C since the base value was not calculated.
Another advance correction is required in Release 2.1 and 2.2. because of the program conversion.

Additional key words

AA286 insurance data old data old assets data takeover AS91 AS92 AS02 SAPMA02S SAPLAIST

SAP Note 27115 - No date in purchase requisition for the component

Symptom:

A requirements date is not transferred to the purchase requisition for the newly created component of a production order. This causes an error message.

Cause and prerequisites

Program error

Solution
Correction P30K015078

Additional key words

Purchase requisition, production order, requirements date

SAP Note 27108 - sql error -4020 performing INS on table DDLOG

Symptom:

The following error message is displayed in the syslog:
sql error -4020 performing INS on table DDLOG
> unknown sequence name

Reason and Prerequisites

A MaxDB system or SAP DB system was not installed using R3Inst, R3Setup, or SAPInst.
Therefore, an object of the sequence type is missing in the database.

Solution

After the installation, you must subsequently create the sequence.

    1. Start the SQLStudio (user SAPR3).
    2. Execute the following select statement:
    select * from DOMAIN.SEQUENCES
    3. If the entry DDLOG_SEQ is not displayed, execute the following create statement:
    CREATE SEQUENCE DDLOG_SEQ MINVALUE -2147483646
    MAXVALUE 2147483646 INCREMENT BY 1 START WITH
    -2147483646 NOCACHE NOORDER NOCYCLE

SAP Note 27102 - Chunk table overflow

Symptom:

For dbspace enhancement using onmonitor, the following error message appears:
Cannot add a new chunk to the dbspace
ISAM error INF-137: chunk table overflow

Cause and prerequisites

The maximum number of chunks in the ONCONFIG file was reached. The value is set with the parameter CHUNKS, and is set to 32 as default.

Solution
Increase parameter CHUNKS in the ONCONFIG file (for example, to 64).
The maximum allowed depends on the number of files which a process can keep open at the same time. The number of open files for each process can be configured for each operating system level.
The value of the parameter must lie in the following range:
Minimum : Number of dbspaces
Maximum : (number of open files for each process - 6), to a maximum of 2047

Additional key words

onmonitor ONCONFIG

SAP Note 27101 - ORA-1405 "Fetched column value is NULL"

Symptom:

When reorganizing tablespace with sapdba, the following error message appears
ORA-1405 error "Fetched column value is NULL".
sapdba terminates with the message:
SAPDBA: Error selecting next table!

Cause and prerequisites

Error in sapdba.

Solution
The problem is corrected in the subsequent version of the sapdba.
A corrected version of the sapdba can be found on sapserv3/4 under dist/permanent/sapdba/hp/sapdba.30A.716.Z.

Additional key words

sapdba

SAP Note 27100 - ME21, ME22: Release order: Texts not copied

Symptom:

Contract texts are not adopted in the release order when an existing purchase order is extended.

Cause and prerequisites

Error.

Solution
Corrected as of Releases 2.2F/3.0C.

Additional key words

ME21 ME22 Release order

SAP Note 27099 - Update statistics in transaction DB02

Symptom:

In TA DB02 (database performance: tables and indexes), it is possible
to schedule an Update Statistics. No separate background job is defined;
only a new 'partial job' is defined for the performance collector.

Cause and prerequisites

An Update Statistics can be scheduled via the TA DB02 -> Goto -> Check -> Table Statistics -> Sizes/Statistics. This Update Statistics is started by the performance collector (background job SAP_COLLECTOR_FOR_PERFMONITOR with Report RSCOLL00), which should run in the system hourly (see Note 16083).
The time of the last Update Statistics is displayed in Last success. execution.
You can display the log of the collector with the TA ST03 -> Environment -> Data Collector -> Display protocol.
This log contains report RSEFA350, which started the Update Statistics (at the time also specified in the DB02).

Solution
This is not an error, but within the framework of CCMS it is possible
to define a separate background job for the Update Statistics under
Informix. Using TA DB13 (DB administration in the SAP environment),
you can schedule an Update Statistics for a certain table or for all
tables. This job can be found in the job overview (TA SM37).
(NAme for example DBA:UPDATE_STA0______014:00/1000)

Additional key words

DB02, infupdstat, update statistics, rscoll00, rsefa390, rsefa350
SAP_COLLECTOR_FOR_PERFMONITOR

SAP Note 27096 - FCS: Costing maintenance routings IA16

Symptom:

In program "SAPLKKCK", the exception "NON_ZERO_DATE_EXPECTED" was triggered by a RAISE statement.
The processing was terminated because the exception is not trapped by a higher-level program in the call hierarchy.

The termination occurred in ABAP/4 program "SAPLKKCK" in "CK_F_CO_OBJECT_PLAN_DELETE".
The main program was "RMIAPL20".

Cause and prerequisites

The interface parameter CKCOUEB_IMP-DATUM is not set due to a missing value in transfer structure CAUFVD-GSTRS

Solution
Enhance the source code for report RMIAPL20 (two lines)

SAP Note 27093 - MB01 PK13: Currency translation missing

Symptom:

1) If two or more Kanban containers for a material are replenished
simultaneously, an error occurs in the currrency translation at the
time of the goods receipt posting.
2) The same problem can also occur in the case of normal goods receipt
postings.

Cause and prerequisites

Error.

Solution
Corrected as of Release 3.0B.

Additional key words

Kanban LEINRU04 LEINRF03 Goods receipt

SAP Note 27088 - last minute info for language import 3.0A

Symptom:

Last minute information for language import 3.0A

Cause and prerequisites

This note contains actual information about known problems for language
import 3.0A.
Please run language import as described below.

Solution
1. Import additional transport orders

!!! Please import the transport order BEFORE starting the
language import !!!

Import an additional transport order with necessary table entries
for the language import tools.
(the WindowsNT examples are assuming you are using drive d)

a) Login as user adm in Unix.

b) You should enter the following commands in order to import
the transport order:
Change directory and start the script using

UNIX:
cd /sapcd
./TOOLS.IMP /usr/sap/trans/data/lang

WindowsNT
d:
TOOLS.BAT e:\usr\sap\trans\data\lang

SAP Note 27087 - Vendor evaluation - price history

Symptom:

During the calculation of the score for the automatic criterion "price history", the effective price from the last PO of the preceding year was incorrectly determined. The price of the current year was taken as the effective price.

Cause and prerequisites

Program error.

Solution
See below.

SAP Note 27082 - Various errors during copying (adoption) of item texts from

Symptom:

Despite table T165P having been set up appropriately, the attempted adoption of reference document item texts in a new purchasing document failed in the following cases:

    1. Adoption of an RFQ text in a purchase order with status '*'.
    2. Adoption of an outline agreement text in an RFQ.
    3. Adoption of a text from a reference document with status '*'.
Cause and prerequisites

Program error.

Solution
Corrected as of 2.2G/3.0C.
The implementation of the advance correction as described below.
When you display or reference the reference document text (status N or *), note that this text is not displayed anymore during the changing or display of the newly-created document because the link to the reference document is not stored in the database (exception: release order). This cpnverns only an entry aid in the process of document creation.

SAP Note 27080 - More than 999 char. values for a characteristic

Symptom:

Within characteristic maintenance, the standard SAP system only allows you to define up to 999 values.
If you try to enter more than 999 values, message C1034 (Value $ entered more than one) is displayed when you exit the value screen.

Cause and prerequisites

Guarantee of good performance in the standard SAP System.

Solution
If more than 999 values are necessary, the system must be modified. The following changes are to be made in this case:
1. Data element PAGAC: Change domain 'NUM3' to 'NUM4' in the data element and activate the data element.
2. Data element PAGSU: Change domain 'NUM3' to 'NUM4' in the data element and activate the data element.
3. Change the output length of fields RCTMV-PAGAC and RCTMV-PAGSU on screen 0200 of program SAPLCTMV from three to four characters and generate the screen.
This modification now allows you to define up to 9999 values for each characteristic.

SAP Note 27078 - SAPF103: Data missing when making a transfer posting

Symptom:

When transferring the receivables to a special G/L account, some data is not transferred: business area and dunning data. Also the due date is not correct.
The correction was enhanced on 04/23/96; if the dunning date is blank, it is not transferred.

Cause and prerequisites

was not defined

Solution
Maintain correction.

SAP Note 27076 - HR: Fast entry balance revisions incorrect

Symptom:

Records of infotype 2012 (balance revisions) for several personnel numbers are entered with default values using transaction PA71. For the same validity period and the same personnel numbers, other balance revisions are then entered and saved again. In this case, the records of the last personnel number are not saved on the database even though a corresponding message appears. An abnormal end can also occur in Release 2.* since an attempt is made to write two records with the same key to the PREL.

Cause and prerequisites

Program error

Solution

The error is corrected in Release 3.0B. You can implement the following temporary workaround:

    1. Edit Include MP2000FS.
      a) Find module READ_TABLE_001P and make the changes described in the section "Source code corrections".
    2. Then run a syntax check on program MP200000.

Additional key words

MP200000 screen 2550, SAPUP505


SAP Note 27075 - Accnt determination Provisions: Error msg. F4078

Symptom:

During account determination for the transaction ACC (provisions), the error message F4078 occurs although the account determination should be carried out regardless of the provision method.

Cause and prerequisites

Error.

Solution
Corrected in 30B.

Additional key words

FBKP SAPDFKB1 ACC T030 OBXD

SAP Note 27072 - Credit management: Error when checking OI struct.

Symptom:

The check 'Wenn > x % of open items are overdue more than n days', which can be set in SD Customizing, also takes those open items with special G/L indicators into account which are not relevant for credit management.

Cause and prerequisites

Error

Solution
Corrected in 22G/30B.

Additional key words

T691F VA01 SAPLF035 CUSTOMER_OPEN_ITEMS_STRUCTURE T074U

8.9.11

SAP Note 27071 - Production version: "To location" entry

Symptom:

You maintain production versions when maintaining material master records and choose "New: Details" in the "Production Version Overview" dialog box. You then enter a value in the "To location" field in the following "Production Version Details" dialog box. The system thereupon issues error message 00 058, "Entry xxxx does not exist (please check your entry)", although the specified storage location does exist.

Cause and prerequisites

The foreign key check was not made correctly by the system.

Solution
Problem corrected in Releases 2.2G and 3.0B.

Additional key words

Transactions: MM01, MM02; program: SAPLMDIA; field: MKAL-ALORT

SAP Note 27070 - Term. in plan when characteristic type changed

Symptom:

If an inspection characteristic in a plan is changed from quantitative to qualitative, an abnormal termination occurs during the initialization of quantitative fields.

Cause and prerequisites
Solution

Either delete the inspection characteristic and then create it again as a qualitative characteristic, or implement the following correction (see below).

Header Data


Additional key words

Inspection plan, routing, recipe, inspection characteristic

SAP Note 27069 - No Capacity load appears in Capacity Leveling

Symptom:

In Capacity leveling or Capacity evaluation no load is appearing.

Cause and prerequisites

See Advice note 15274. Some customizing from SAP needs to be copied into your working client.

Solution


Other reasons are due to customizing.

    1. Control key does not have capacity swithced on.
    2. Your operation does not have any work.
    3. You need to have a duration aswell if you wish to see the operation on the graphical planning table.
    4. The workcenter does not have a valid formular in the capacity header. The "OTHER" formular should have SAP008 (Standard entry).
    5. The scheduling is also not going to work properly if you do not have a formular in the scheduling screen. (Standard SAP004).
    6. As an extra tip costs should be calculated using SAP008. See assignments.
    7. If you have defined your capacity category to be machine rather than labour, then you will not see these objects on the Planning table when start the planning table from PM or SM menus. You will only see them when you start the planning table from PP See Tran. CM00 for all options.

Additional key words

PPCRP CM01 CM24 cm34 cm22 cm32


SAP Note 27068 - CC information: Insert into read-only-view not allowed

Symptom:

A client copy with tp terminates with the message:
Insert not allowed into read-only-view.

Cause and prerequisites

During a transport between two systems, all relevant data is selected in the source system. A view that was selected is marked as Read-only-view in the target system.

Solution
Start the report RSCCEXPT and add the view which caused the error to the list of exceptions using "Add table".

Additional key words

SCC2, SCC8, SCC7, tp

SAP Note 27067 - Transfer of LZBKZ and LANDL from SD to FI

Symptom:

It is not possible to transfer the fields
- State Central Bank Indicator (LZBKZ)
- Supplying country (LANDL)
to financial accounting.
The system rejects the release of a billing document with message F5 808:
"Field XXXX is a required field for G/L account YYYYYY ZZZZ"

Other terms

BSEG, LANDL, LZBKZ, T015L, required entry, customer line item

Reason and Prerequisites

Prerequisite:
The fields
- State Central Bank Indicator (LZBKZ) and/or
- Supplying Country (LANDL)
are defined as required entry in the field selection of the G/L account YYYYYY in the company code ZZZZ.

Cause:
The transfer of the "SCB Indicator" and "Supplying Country" fields from
the sales module (SD) to financial accounting is not provided in the standard.

Solution
A change in the standard is not planned.

This problem can only be corrected by a modification. Contact
Consulting for this purpose. See also the attached Note 170183.

Solution:
Use the user exit 002 (function module EXIT_SAPLV60B_002) to fill the fields
- XACCIT-LZBKZ
- XACCIT-LANDL
according to your requirements.

SAP Note 27066 - Intercompany billing: Incorrect address printed

Symptom:

The address of the intercompany billing sales organization is generally printed during intercompany billing. In certain constellations, however, this can be incorrect because different company codes are affected.

Cause and prerequisites

The allocation of intercompany billing sales organization and company code does not have to be correct. (see note 2271)

Solution
Solution: The company code address is printed in intercompany billing

Additional key words

Billing document printout
Cross company
Intercompany sales

SAP Note 27065 - Error: No status object available for operation xxx

Symptom:

If you look up master data (routing, bill of material), you cannot save the order because of the above error message.

Cause and prerequisites
Solution
Program correction in module LCOSDFO1 (contained in 3.0A)

SAP Note 27064 - RAISE_EXCEPTION in production order: WRONG_VBKZ

Symptom:

Raise exception WRONG_VBKZ is triggered in the production order.

Cause and prerequisites

Program error

Solution
See correction P30K017067

SAP Note 27063 - PD: Integration: Several positions for transfer

Symptom:

- One person occupies (for PD - PA integration) several positions in PD. One of these positions (generally the one with the highest staffing percentage) is also stored in PA infotype 0001 ("organizational assignment").
-a transfer event is carried out for this person.

--> Only the relationship to the position displayed in PA infotype 0001 is delimited by PB on the transfer date. The other positions not displayed in PA are not taken into account, and the relationships of the person to these positions are kept.

Cause and prerequisites

Program design

Solution
The other position relationships of the person must be delimited after completion of the transfer event by PD transaction.
A note on the existence of several position relationships appears as an information message when you display PA infotype 0001.

Additional key words

Transfer, changes of work center, occupancy of position, multiple occupancy

SAP Note 27062 - VPRS: deliv-related billing document for returns

Symptom:

Both delivery items and returns items are entered in a sales order.
The respective billing document is created delivery-related (even for the returns item).
The cost VPRS is correctly determined as negative for the returns item in the sales order, but it is positive in the billing document. If the billing document is created before the goods issue posting, the VPRS is correctly determined as negative.

Cause and prerequisites

Program error

Solution
Corrected in 2.2G/3.0B

Additional key words

VF01

SAP Note 27061 - VF04 term. routine SELEKTIONSEINTRAG_IN_STATAB

Symptom:

After deleting "further selection criteria", a termination occurs with the following error message:
Termination: error in the routine
SELEKTIONSEINTRAG_IN_STATAB

Cause and prerequisites

Work areas are not deleted.

Solution
See source code corrections

Additional key words

SAPMV60S, billing due list

SAP Note 27060 - OKKP Runtime error SPOOL_INTERNAL_ERROR

Symptom:

The transaction OKKP ends with a runtime error SPOOL_INTERNAL_ERROR. when saving the controlling area

Cause and prerequisites

The SUBMIT statement for the spool has been changed in the ABAP.

Solution
Please correct the selected lines in the program code of the program SAPMKC00.

Additional key words

OKKP , SPOOL_INTERNAL_ERROR

SAP Note 27059 - SAPDBA: no scripts dro.sql, tab.sql

Symptom:

When reorganizing a table with sapdba, the scripts dro. sql and tab.sql are not created. Reorganization cannot be carried out.

Cause and prerequisites

Storage error in sapdba, only occurs in version 3.0A up to now and only with OSF/1.
The error has not ocurred in earlier versions and on other operating systems.

Solution
Corrected in 3.0B.
A corrected version of 3.0A is also available on sapserv3 and sapserv4.

Additional key words

sapdba, reorganize, reorganization, single table

SAP Note 27058 - Archived redo logs do not have same size as online

Symptom:

Archived redo log files of the database do not have the same size as the online redo logs.

Cause and prerequisites

Cause is a generic behaviour of Oracle7.
In Oracle online redo log files are used in a circular fashion. The default for a R/3 installation is to have four online redo log files (log file groups, to be more precise; here it's sufficient to just think of each group to consist of one file only, i. e. no mirroring of online redo logs) with a size of 20MB each.
The database will write to one file, once that has been filled up, it will switch to the 2nd., 3rd., 4th. and then reuse the 1st. and so on.

The database ARCHive process will save the online redo logs to an archive directory (usually ORACLE_HOME/saparch) before they are reused (if the database runs in archive mode).

If the online redo log was fully written, the archived redo log will have the same size as the online redo log.

It is possible to force the database to switch from one online redo log to the next, before the online redo log file was completely filled with redo data, e. g. the database may have written 8MB of redo data to an online redo log file with a size of 20MB, and then an online redo log file switch may have been forced.

In this case the archived redo log file will have a size of 8MB only, i. e. the size of the archived redo log file is less than the size of the online redo log file. The archived file will always have the size of the amount of redo data kept in the online redo log file.

An online redo log switch is forced, for example, at the end of an online database backup using SAPDBA - brbackup.

Solution
No solution, generic behaviour, not an error

SAP Note 27057 - Planning: Raise exception in LKPP0F12

Symptom:

Key words : Manual planning, pre-parameterization
Description: After initial planning screen confirmation, runtime error RAISE_EXCEPTION PROGRAM_ERROR occurs in Include LKPP0F12, FORM routine VORPARAMETRISIERUNG_EINSTELLEN.

Cause and prerequisites

Program error
Preconditions: (When does the error occur?)
The error only occurs in Release 3.00 (FCS). The planner profile used contains one or more planning layouts for which parameters were predefined.

Solution
Program correction

Additional key words

Program : SAPLKAPP, SAPLKPP0
Transactions: KP06, KP07, KP26, KP27, KP46, KP47

SAP Note 27056 - Authorization to change scheduled quantity in ME38

Symptom:

Despite authorization 'M_LPET_ALL' it is impossible to change the scheduled quantity in transaction 'ME38'.

Cause and prerequisites

The list of authorizations specified in the authorization profile is in complete. 'M_RAHM_EKO' is allocated as check object to transaction ME38.

Solution
- Two solution options:
The authorization profile 'M_LPET_ALL', which is not used in the standard system, must be extended by authorization 'M_RAHM_EKOAL'. This is the only possibility for a user to maintain the scheduled quantity if he/she is only allocated authorization profile 'M_LPET_ALL'.
- Alternatively, it is possible to replace the authorization object
M_RAHM_EKO by M_LPET_EKO using transaction SM31 table TSTC for
transaction ME38 (was performed as default for Release 3.0).

SAP Note 27055 - FD32/FB02/FS02: Unsaved text changes

Symptom:

FD32 - Change credit master data - Texts - Enter text - Back - Texts - No change - Back: If you now exit the transaction with 'Back', no confirmation prompt appears and the changes are not made.
That is, if you look at the texts again without changing them after you have made the text changes, the program behaves as if no changes have been made.
The same applies for the long texts in the document (FB02) and for the texts for the G/L account data (FS02).

Cause and prerequisites

Error.

Solution
Corrected in 2.2G/3.0B.

Additional key words

SAPMF02C, credit management, SAPLFTXT SAPMF05A SAPMF02E

SAP Note 27053 - PS structure reports: Increase text length to 40

Symptom:

Up to now, master data texts were only displayed in length 30.

Cause and prerequisites

So far, only 30 columns were defined.

Solution
1. After you have increased the width of the row text, you have to regenerate the report.
2. The row text width must be larger than 65.
3. Implement the specified correction (P22K009642)

Additional key words

Project structure reports
CJ50: RCNCO010, CJ52: RCNCO011, CJ54: RCNCO012

SAP Note 27052 - RFDKAG00, RFKKAG00: no list output when run in background

Symptom:

No list is displayed for the RFDKAG00 and RFKKAG00 programs when they
are run in the background.

Cause and prerequisites

At the AT SELECTION-SCRREN point in the program, the system asks for
confirmation of the SY-UCOMM system variable (function entry in OK-CODE). The variable is, however, not set when the program runs in the background.

Solution
Turn the query of the SY-UCOMM system variable into a comment line, or delete it from the coding. Corrected for Release 3.0B. An advance correction is also possible.

Additional key words

Master data comparison, BT175

SAP Note 27051 - Subseq. deb./cred. reversal for PO assigned to acct

Symptom:

You want to reverse a subsequent debit/credit for a purchase order assigned to an account. Message 00347 is displayed: 'Field && is not an input field'.

Cause and prerequisites

Program error

Solution
Corrected in Release 3.0B. Advance correction: Please make the following correction.

Additional key words

MR08, TBTKZ, SAKNR, KOSTL

SAP Note 27046 - CO0: Problem in simple discontinuations in SFC

Symptom:

After the availability check of a simple discontinuation, the component list is edited incorrectly or a termination occurs.

Cause and prerequisites

Implementation of a performance improvement.

Solution
Correction P30K017021 in module LCOZAF01

SAP Note 27037 - AWE based on contract elements for SSP

Symptom:

When the average weekly rearnings are calculated for an employee who has no prior payroll results then the basic pay infotype P0008 is used as contractual elements.
If the employee is paid an hourly rate then the multiplication of the hourly rate by the contracted number of hours per week is wrongly divided by 100.

Cause and prerequisites

Error in coding.

Solution
Please change the FORM FIND_CONTRACT_AWE within report RPUSPFG0 with the lines marked 'MO'Djan96.

SAP Note 27036 - Business area in company code clearing item

Symptom:

When posting cross company-code documents, the items generated automatically in the company code clearing accounts are not assigned to the business area.
Requested solution 1:
If the business area is clear, you want the company code clearing accounts to be posted automatically with this business area.
Requested solution 2:
You want to make a subsequent account assignment using the "Post Balance Sheet Readjustment" function, by making a transfer posting from business area SPACE to business areas other than SPACE.
However, transfer postings are not carried out by the "Post Balance Sheet Readjustment".

Cause and prerequisites

For 1:
From a business perspective there is no definite answer as to whether or not it is right that the business area is inherited to the company code clearing item. A corresponding statement can also depend on the accounting transaction in question. This is the reason why in principle no business area is inherited to these items in the SAP standard system.
For 2:
The "Post Balance Sheet Readjustment" function is only carried out for customer and vendor reconciliation accounts as well as tax accounts and the cash discount clearing account. Other G/L accounts are not processed.

Solution

For 1:
For postings which were directly entered in FI (for example FI invoices), the business area can be supplemented manually in the company code clearing items. To do this simulate the document, select the company code clearing items and insert the required value into each business area.
For postings that are not entered in FI (for example SD billing documents), you can control as of Release 4.6 whether the business area if unique (in the respective company code document), should be copied to the company code clearing items. In earlier releases this can be implemented as a program modification (see below).

For 2:

      a) Releases >= 3.0F:

An enhancement is available. With the help of this enhancement, it is possible by means of customer-specific source code to ensure that also G/L accounts are allocated through the "Post Balance Sheet Readjustment". To do this, call up transaction CMOD. A description of the enhancement method is available under Utilities -> Online manual. The enhancement is called F180A001. Please read the documentation on both the enhancement and the individual enhancement components.

      b) Releases >= 3.0A:
You can manage your company code clearing accounts as customer and/or vendor reconciliation accounts. These accounts are then taken into consideration by the "Post Balance Sheet Readjustment".
In addition, managing accounts on an open item basis ensures that all postings made to the company code clearing accounts are taken out with the same business area, with which they were also posted.
To do this, create a customer (vendor) for each company code clearing account who manages this account as a reconciliation account. Enter a customer posting key (vendor posting key) as well as the corresponding customer account (vendor account) in the account determination for the company code clearing accounts.

Additional key words

SAPF180, SAPLF048, SAPLF049, RFGAUF00, business area allocation

SAP Note 27035 - Termination ASSIGN_LENGTH_0 during import

Symptom:

When importing the standard reports for cost center accounting with the help of the transaction OKD3, the runtime error ASSIGN_LENGTH_0 occurs in the program SAPFGUTR.

Cause and prerequisites

The attempt is made to import an invalid report group.
The invalid report group is presumably 1CA1.

Solution
Please carry out the import online and only mark the report groups with a valid library on the list of the report groups to be imported.

Additional key words

Report Writer

SAP Note 27031 - Conversion_exit_konpr_output: Incorr. WBS elem. no.

Symptom:

If the conversion_exit_konpr_output does not find an (internal) WBS element number, it currently always displays the number found last (during a previous call). As a result, data error cannot be recognized and subsequent error may occur (for example during the settlement).

Cause and prerequisites

Incorrect source code in LCJPNU21.

Solution
see below

Additional key words

LCJPNu21, conversion exit, project number

SAP Note 27026 - Incorrect correlation of order items

Symptom:

Preconditions: Sales document with 2 items where the second item was manually allocated as a subitem to the first one. If you now change the quantity of the higher-level item, then the quantity of the subitems is correlated incorrectly.

Cause and prerequisites

Program error

Solution
You can make the following advance correction:

Additional key words

credit memo, debit memo, contract, target quantity

SAP Note 27025 - AuCs for CIM were not deleted

Symptom:

If AuCs are created for a WBS element before release and then the WBS element is deleted from the structure, then the AuC is not deleted and remains in the system without a managing object (WBS).

Cause and prerequisites

Function was not supported.

Solution
The function was implemented in Release 3.0B. A delivery as an advance correction is not intended.

Additional key words

AuC CJ02 capital investment measure

SAP Note 27024 - MM-SRV: Setting up components (services)

Symptom:

In Release 3.0, the new services management functionality is available.
To use this functionality, you have to make various settings in the system.
This note describes the required Customizing settings.

Cause and prerequisites

In order to understand the settings, you must be familiar with the function "Compare with client 0" in the "Utilities" menu when maintaining the Customizing.
You have to decide whether the copied Customizing entries from client 0 meet your requirements. SAP nevertheless recommends to first copy the settings from client 0 and to adapt them, if required.

Solution
    1. Setting up the intervals for the number ranges:

    Path in SAP Reference IMG: -> Materials management
    -> Purchasing
    -> Environment data
    -> Maintain number ranges
    In function "Number ranges for services management", you define a number range for the service package and for the entry sheet.
    Then you have to insert an interval in each case for the previously specified number ranges in functions "Intervals: package" and "Intervals: entry sheet".
    2. Maintaining the authorizations for the acceptance of services performed.

    Please refer to the release notes for 3.0A for more information. You can find the release notes in the "Help" menu.
    Path in Release notes for 3.0A:
    -> Materials Management
    -> Purchasing
    -> External services management
    3. Setting up service conditions:
      a) Setting up exclusion indicator:
      Transaction: SM30
      View : V_T686A
      Application: MS
      Copy the settings from client 0.
      b) Copying condition types:
      Path in SAP Reference IMG:
      -> Materials management
      -> Purchasing
      -> Functions
      -> Maintain conditions for services
      Select transaction: Condition types
      Copy the condition types from client 0.
      c) Copying condition schema:
      Path in SAP Reference IMG: see condition types under b)
      Select transaction: Schema for services
      Copy procedures MS0000 and MS0001 from client 0.
      Then select the two procedures and perform the "Control" function.
      On the following overview screen you copy all levels from client 0.
      You do this for procedure MS0000 and procedure MS0001.
    4. Copying messages:
      a) Message types:

      Path in SAP Reference IMG:
      -> Materials management
      -> Purchasing
      -> Functions
      -> Messages
      -> Output control
      -> Message types
      Define message types for service entry sheets.
      Copy the data from client 0.
b) Message schema:

Path in SAP Reference IMG: see output types under a)
Define message schemas for service entry sheets.
Copy the data from client 0.
Copy as well the control data of the schema from client 0.

Additional key words

SE316

SAP Note 27021 - Customizing for cond type/table: agreements

Symptom:

When using transaction VB(4 to customize condition types/tables for agreements, the following error message occurs when using the "help" function (PF4) for condition tables:

"E: Entry E 029 does not exist (check your entry)".

Cause and prerequisites

Program error.

Solution
Program corrections.

SAP Note 27020 - Plan Data Interface: Message GP 405

Symptom:

When using the plan data interface for transfering/generating cost center plan data, error message GP 405 appears (Planning parameter xxx not available).

Additional key words

The error message can occur in the following standard functions where the interface is used:

  • KP97: Copy Version (Cost Centers)
    • Error removed in Release 3.0D.
  • KP96: Generate Opening Balance
    • Error removed in Release 3.0D.
  • AR13 (RAKOPL01): Data Transfer Depreciation/Interest
    • Error removed in Release 3.0C.
  • KPHR (RKHRPLAN): Data Transfer from HR Personnel Cost Planning
    • Error removed in Release 3.0D.
  • KO14: Copy Version (Order Planning)
    • Error removed in Release 3.0E.
  • KSPP: Transfer Plan Activity Requirements for Production
    • Error removed in Release 3.0D.
Cause and prerequisites

The plan data interface uses the planning parameter to determine the manually planned field groups (given through the interface).
Planning parameters were also required in manual planning up to and including Release 2.2. For Release 3.0, the manual planning functions were changed so that planning parameters are no longer used there. The planning interface and all standard functions using this interface, however, continue to work with the parameters. A default parameter in the interface is planning parameter "CO-01", which most of the functions named above use. If this is not available, or if the function called up uses another unavailable planning parameter, the above error message appears.

Solution
Please install the correction described in note 50360 for copying the version for internal orders (transaction KO14). You do not need to create a planning parameter to copy the version for internal orders. Otherwise the missing planning parameter must be created.
As of Release 3.0, this can only be done directly using transaction KPG1.
For the interface, only the planning-area-dependent definition of the manually plannable field groups is relevant.

SAP Note 27017 - Customer CATT objects become SAP originals

Symptom:

If a CATT object is created, for example, with transaction SCAT in a customer system under Release 3.0A-FCS, this object is characterized as an SAP original object in the object catalog table TADIR.

Cause and prerequisites

The reason for the error response is an incorrect allocation of CATT objects to the SAP name range. This error is corrected with update level 3.0A.

Solution
The original system of CATT object can be changed in the update level 3.0A-FCS.
To do this, log on to the system with full autthorization for the Workbench Organizer (for example, as user 'DDIC') and proceed as follows:
System -> Services -> Table maintenance
Maintain table TADIR
Program ID : R3TR
Object type : SCAT
Object name : Z*
Search
By double-clicking on the individual entries, the maintenance popup for catalog attributes appears. You can then overwrite the original system 'SAP' with the current system name. Once you have done this, save the changes.

Additional key words

The object text of CATT objects in table TADIR is called:
R3TR SCAT

SAP Note 27015 - Error when converting the unit of a service

Symptom:

The values are updated incorrectly in the fields of the cumulated actual activities of an operation.

Cause and prerequisites

The cumulated actual activities are updated in the unit of the allocated activity providing an activity is defined. If the unit of the standard value is different to the unit of an activity tpye and if the backflushing is made in the unit of the standard value, the backflushed service is added to services already backflushed without prior conversion.

Solution
Change the source code in program LCORFFU1.

Additional key words

CO11, quantity/service

SAP Note 27013 - "SAPLCYBT" "PROGRAM_ERROR"

Symptom:

Raise exception "PROGRAM_ERROR" was triggered in ABAP/4 program "SAPLCYBT" in "CY_BT_KBED_OPR_UPDATE". The main program is "SAPMM61P".

Cause and prerequisites

Order creation

Solution
Program correction

SAP Note 27010 - Capacity requirements for rough-cut planning profiles

Symptom:

Capacity requirements for rough-cut planning profiles cannot be displayed on the planning table.
Messages stating that no work center was maintained for the operation are written to the scheduling log.

Cause and prerequisites

The remaining requirements are not written to the KBED record.

Solution
Program correction