SAP Note 28272 - BCD_FIELD_OVERFLOW in program RLLI0400

Symptom:

BCD_FIELD_OVERFLOW in program RLLI0400
The field CNT_POS (defined with format P(2)) overflows.
The overflow occurs in routine INV_ZAEHLEN

Reason and Prerequisites

The field is defined too small.

Solution
Inventory documents in Warehouse Management should not be too large because the documents are imported and processed completely in all processing steps. Therefore, runtime problems or or terminations may occur if very large documents exist. The critical value depends in this case on the different system parameters and on the number of discovered inventory differences since one transfer order (or one item as of 3.0) is created for each difference. During everyday work, we generally recommend the splitting into several smaller documents that can be grouped together under one reference number. You can then print and make postings using this reference number. In addition, you can enter counting results in parallel which is not possible for a large physical inventory document.
'Large' storage bins are an exception to this organizational rule. Since locations must always be contained as a whole in a physical inventory document, there is nothing you can do organizationally in the case of locations with more than 1000 quants. You then have to extend the length for the definition of field CNT_POS to 3.

SAP Note 28271 - Availability check - sales order creation

Symptom:

Make-to-order production, transaction VA01
If the desired delivery date equals the possible delivery date, the system still displays a screen for the availability check in which you have to confirm the delivery date again (check date = date of replenishment lead time).

Cause and prerequisites
Solution
Corrected in member LM61VF50

SAP Note 28268 - Number of read priorities during CPSE selection

Symptom:

The routing selection via CP_SE_ALT_SELECT_AUTO was expanded by export parameter TCA43_COUNT. This parameter specifies the number of found priorities for the predefined routing selection.

Cause and prerequisites
Solution
Correction P30K021641 contains the solution for Release 3.0B.
Correction P22K009368 contains the solution for Release 2.2G.

Additional key words

routing_selection

SAP Note 28265 - Update termination when changing equipment

Symptom:

If the PRT screen is activated for existing equipment via Customizing and PRT data is maintained, an update termination occurs

Cause and prerequisites

Program

Solution
Correction

Additional key words

IE02 PRT update termination

SAP Note 28263 - Unreas. values on certificate for upper tolerance

Symptom:

In certain cases, the unreasonable value -99999999999999 is output for the upper tolerance.

Cause and prerequisites

The data origin of the inspection specifications is defined in the certificate profile for this characteristic that they are to be read from batch classification (Origin 02 in the standard system).
The setting for the general characteristic in the classification system provides an upper tolerance. The value of the upper tolerance is no longer defined in the value range (that is: allowed value < upper tolerance).

Solution
Program correction in Include LQC02U08, function module QC02_BATCH_CHAR_SPECS.

Additional key words

Certificate, transaction QC01, QC02, QC03
Quality certificate
Specifications
Batch specification
Limit

SAP Note 28258 - Cash discount base 0 in preliminary posting

Symptom:

Although you can enter cash discount base 0 during preliminary posting, the cash discount base amount is still calculated when posting instead of writing cash discount base 0 into the accounting document.

Cause and prerequisites

This was not programmed.

Solution
Advance correction, corrected in 2.2G.

Additional key words

FBV1, FBV2, FBV0, preliminary posting

SAP Note 28257 - Abnormal termination during transaction QGA2

Symptom:

After running transaction QGA2 (Display inspection results), the program terminates abnormally (ABAP/4 runtime error RAISE_EXCEPTION "CHARACTERIST_SELECT_NOT_UNIQUE") if you choose the 'Select' function for a characteristic.

Cause and prerequisites

Missing entry in table TQ78.
As of Release 3.0B, the entry is no longer necessary.

Solution
In Customizing table TQ78 (processing modes results recording) copy the following entry: Transaction code = SE38, Processing mode = 1 into the entry Transaction code = QGA2, Processing mode = 1.
1. Transaction SM30
2. Table/view : V_TQ78
3. Function 'Maintain'
4. Function 'Position'
5. Transaction code SE38, processing mode 1, function 'Continue'
6. Select upper line
7. Function 'Copy as'
8. Transaction code QGA2, processing mode 1
9. Function 'Save'

Additional key words

Analyses, inspection results

SAP Note 28256 - Prod.order relevant to planning despite status TECO

Symptom:

A production order is displayed in the current stock/requirements list in Transaction MD04 although it has status TECO (technically completed).

Cause and prerequisites

Flag AFPO-DNREL was not set. So far, the error could not be reproduced, however, there is an index error which could possibly be the cause.

Solution

• You can generally correct the incorrect production order if you cancel and reset the status with Transaction CO02:
  Menu 'Order -> Functions -> Restrict processing'.

• In addition, make the following source code corrections.

Additional key words

CO01, CO02

SAP Note 28252 - Cap.sch.:Schedule pl.order with subops.or phases

Symptom:

Planning board: If an operation of a planned order is scheduled, the allocated suboperations and phases remain in the lower partial screen.

Cause and prerequisites
Solution
Source code corrections

Additional key words

Capacity scheduling

SAP Note 28250 - KP97: Activity-rel. stat. key figures not posted

Symptom:

When the planning data of stat. key figures is copied, activity-related planned key figures are not copied although they are identified in the log as processed.

Cause and prerequisites

Program error

Solution
Corrected in 3.0B; can be implemented as advance correction as follows

Additional key words

KP97, RKP4, SAPLKIPL

SAP Note 28248 - Creating an equipment with reference

Symptom:

When you create equipment with reference, only a very small number of fields are copied from the reference equipment. In particular, the fields from the location and account assignment data is missing.
Furthermore, the system does not behave uniformly with respect to the copied fields depending on whether the equipment is generated via the single entry or the multiple entry.

Cause and prerequisites
Solution

As of Release 4.0A, all useful fields are copied.
In addition, multiple entry has its technical origin in single entry which in particular leads to a standardization of the behavior concerning the copied fields.

In this note, a solution is described how to modify the selection of the fields to be copied.

For the adjustment of single entry, enhance the interface of function module EQUI_BY_REFERENZ in addition to the implementation of the attached modification (for example by means of Transaction SE37). Include the parameter ILOA as an additional export parameter which is defined as follows:

• Reference structure ILOA

• Reference type stays empty

• Reference stays empty

Additional key words

IE01, IE08, IE25, IE10, SAPMIEQ0, SAPLIE01, LIE01U06, SAPMIEQ5, MIEQ5I10
Equipment, reference equipment, reference

SAP Note 28241 - Routing selection via alt. task list application

Symptom:

During the routing selection via the modules of function groups CPSE or CPSL, the selections via the task list applications were not made.

Cause and prerequisites
Solution
Correction P30K0116502 considers the predefined task list applications during the selection.

Additional key words

routing_selection

SAP Note 28240 - 'Online versus batch' - cumulation error

Symptom:

In the 'online verus batch' correction it is possible that the system
will not correctly cumulate requirements - in particular in cumulation
mode 2 and 3 and if sales order lines are present.

Cause and prerequisites

This error may occur in early pre-release installations (following
installation UPDATE 3). THIS NOTE SHOULD BE IMPLEMENTED ONLY INTO
SYSTEMS WHICH ALREADY HAVE INSTALLED THE 'ONLINE VERSUS BATCH'-
CORRECTION.

Solution
Error in member LM61VF60 FORM ATP_BERECHNEN

SAP Note 28237 - Double entry in list control

Symptom:

When you call the list control in transactions CO01, CO02, CO03, CO04 (call: (Order -> Print -> Print settings -> List control...), you must press F3 or ENTER two times to take over values. F15 terminates the action.

Cause and prerequisites

Inconvenient design

Solution

Program change:

• The first ENTER provides an information message and with the second ENTER you return and the data is taken over.

• With F3 and F15 you return directly and take over the data in this case.

SAP Note 28233 - NULL values in field FIELDSLG of table DDNTF

Symptom:

The use of a structure (database table or internal table), whose generated field catalog in system table DDNTF reaches or exceeds the length of 32768, either causes an endless loop in R/3 on informix or the R/3 process terminates with a 'core'.
Typical terminations which occurred up to now affected either the very 'wide' table CE8xxxx or the R/3 upgrade from 2.2E to 2.2F (in the 'build_ftab' function).
Cause and prerequisites

There is a program error in the database interface.

The use of 2-byte integers to present and transfer the length of the field catalog generated to the database causes in cases where the length 32768 (0x8000) is either reached or exceeded a NULL value to be mistakenly stored in the informix database during the generation of a large structure. Since field catalogs exceeding this length are blocked, this error appears with all structures that are generated in which the length of the field catalog reaches or exceeds this value.

Solution

This error can only be rectified by using a corrected R/3 kernel. The error is corrected as of

• 2.1L/2.2F, patch level 6 (see Note 19466)

• 2.2G

• 3.0B
  

After the R/3 upgrade has been completed or after the corresponding R/3 kernel has been applied, the nametab of the affected structure must be reactivated. First delete the data records belonging to the structure in system tables DDNTT and DDNTF by means of dbaccess using:
DELETE FROM DDNTT WHERE TABNAME = ''
DELETE FROM DDNTF WHERE TABNAME = ''

The structure can now be activated using Transaction SE11.

Additional key words

KEU5; CE8xxxx, CE8COB1, CE8E001, CE8Z001, NAMETAB, DDNTF, NULL, DB_PGNTAB, BUILD_FTAB, SEGMENTATION FAULT, CORE

SAP Note 28232 - IW31: Long text not copied from task list operat.

Symptom:

When you copy task lists into the order, the operation long texts were not copied from the task list. However, the long text indicator was set for the order operations.

Cause and prerequisites

Program error

Solution
Error recovery

Additional key words

IW31, IW32, RIPLKO10

SAP Note 28230 - Data of the capacity splits disappears

Symptom:

When you maintain a production order, you execute capacity splits for an operation. If you exit the corresponding detail screen with "Back" and call it again later, the data entered has disappeared.

Cause and prerequisites

When you create a production order, one of the key fields of the capacity requirements records is not yet filled. As a result, the splits are no longer found during a second call.

Solution
Make the following program correction

SAP Note 28229 - Report terminates with Oracle error ora-01555

Symptom:

Report terminates with Oracle error "ora-01555 snapshot too old" after a long runtime. The report uses logical database BRF.

Cause and prerequisites

Extensive evaluations of the document database and database updates occur at the same time. The documents are read sequentially (a SELECT database access) in logical database BRF. Because of the parallel updates (different programs) the data to be read is rolled out to a rollback segment.
Due to the long runtime, this data in the rollback segment is out of date before the data is completely imported by the ABAP/4.

Solution
Change the sequential access to "document by document".
Both access modes are realized in logical database BRF.
You only have to set parameter "BR_SEQ" of the logical database to SPACE (when you start the report).
Special case: RFGAUF00
This report sets parameter BR_SEQ in the program directly to 'X'.
Here you have to implement the correction specified below.

Additional key words

SAPDBBRF, RFGAUF00

SAP Note 28228 - External transfers combination prior to Net

Symptom:

Wage types input via P0011 are not processerd correctly by GB net payroll if they are non-taxable.
Additional key words

Model company entry D040: Charitable donations, is an example.
Cause and prerequisites

Incorrect positioning of X045 in model company schemas.
Solution

The movement of the cycle X045 from GNN0 to GNT0 will solve the problem together with amendment of the processing classes for wage type D040. What this means is that all the user definable pre-tax deductions (regardless of from which Infotype they are input) are added together into cumulation class /124: Pre-tax deductions and it is this, rather than the individual user wagetypes, that are deducted from the taxable pay value.
Note that due to the repositioning of X045 that any user defined cumulation wage types /1xx should have processing class 25 set to 0.