SM30: Selection Conditions ended with error
[check] [condition] [ended] [ended up] [Error] [Filter] [limit] [lower] [Message] [open ended] [pre-defined] [restriction] [Selection] [single ended] [SM30] [upper]
- SM30: Selection Conditions – Group correctionsSymptom You have a maintenance view with some Selection Conditions pre-defined. These selection conditions are defined in ranges (using GT, GE, LE and LT options). The conditions are for non-CHAR fields. When...
- SM30: Short dump in view maintenanceSymptom You are trying to display/maintain a Maintenance view using SM30 transaction. You get a short dump with error message – ASSIGN_LENGTH_0 in the program SAPLSVIX. NOTE: This error occurs only if...
- Error Popup while storing/retrieving documentsSymptom You get an error message when storing/retrieving documents with the error text “Error Determining document properties…” Other terms Error determing document properties, error message Reason and Prerequisites This is due to...
- No proper error messages returned when using case via BAPIsSymptom Meaningless error message returned from BAPIs for wrong input values, For eg : user creates case using BAPI & passes wrong input values get the message: “Internal error: class CL_SCMG_CASE_API; method...
Symptom
You have a maintenance view with some Selection Conditions pre-defined. These selection conditions are defined in ranges (using GT, GE, LE and LT options). The conditions are for non-CHAR fields.
When you goto SM30 to display/maintain the view data, you enter new values for the above selection conditions. You observe some of the following behavior -
1) You enter new lower and upper limit values to reduce the range
(new value lower limit > pre-defined value lower limit,
new value upper limit < pre-defined value upper limit)
Still, the selection happens only for the pre-defined values.
2) Your pre-defined condition contains a lower limit. Even if you enter
a higher value for the lower limit in the screen, you get an error
message.
3) You have maintained an upper limit using the GE operator. On screen, you enter a value lower than this. The selection still happens for the pre-defined value. The on-screen value is not read.
4) On-screen selection values are not taken into consideration, when you create new data or change existing data values.
Other terms
SM30, Selection condition, upper limit, lower limit, pre-defined selection condition, error message, check, filter, restriction
Reason and Prerequisites
The above inconsistencies occur due to programming errors.
You are currently using SP20 or above for WebAS 6.40
Or
You are currently using SPS01 or above for WebAS 7.01.
Or
You are currently using SPS01 or above for WebAS 7.02.
Or
You are currently using SPS01 or above for WebAS 7.10.
Or
You are currently using SPS01 or above for WebAS 7.11.
Solution
Please apply the changes attached to the note or import the corresponding SP.
For WebAS 6.40:
- Apply Support Package 25
or
- Apply this note via Note Assistant(SNOTE) if you are on SP20 to SP24.
For WebAS 7.01:
- Apply Support Package 05
or
- Apply this note via Note Assistant(SNOTE) if you are on SP01 to SP04.
For WebAS 7.02:
- Apply Support Package 02
or
- Apply this note via Note Assistant(SNOTE) if you are on SP01.
For WebAS 7.10:
- Apply Support Package 09
or
- Apply this note via Note Assistant(SNOTE) if you are on SP01 to SP08.
For WebAS 7.11:
- Apply Support Package 04
or
- Apply this note via Note Assistant(SNOTE) if you are on SP01 to SP03.