ABAP DUMPS:

TIME_OUT

The program has exceeded the maximum permitted runtime and has therefore been
terminated.
Error analysis
After a certain time, the program terminates to free the work process for other users who are
waiting.
The maximum runtime of a program is set by the profile parameter
“rdisp/max_wprun_time".

The current setting is 1800 seconds. After this, the system gives the program a second
chance. During the first half (>= 1800 seconds), a call that is blocking the work process
(such as a long-running SQL statement) can occur. While the statement is being
processed, the database layer will not allow it to be interrupted. However, to stop the
program terminating immediately after the statement has been successfully processed, the
system gives it another 1800 seconds. Hence the maximum runtime of a program is at
least twice the value of the system profile parameter "rdisp/max_wprun_time".

How to correct the error

Long-running programs should be started as background jobs. If this is not possible, you
can increase the value of the system profile parameter "rdisp/max_wprun_time".
------------------

RAISE_EXCEPTION

A RAISE statement in the program "---------” raised the exception condition "-----".Since
the exception was not intercepted by a superior program in the hierarchy, processing was
terminated.

CONVT_NO_NUMBER

The current ABAP/4 program "--------” had to be terminated because one of the
statements could not be executed.

The program attempted to interpret the value "415#” as a number, but since the value
contravenes the rules for correct number formats, this was not possible.

MESSAGE_TYPE_X

The current application program detected a situation which really should not occur.
Therefore, a termination with a short dump was triggered on purpose by the key word
MESSAGE (type X).

Diagnosis
An error occurred during a comparison of the Control Framework data between the
SAP Front-end and the application server. This error is very probably due to an error in
the front-end software installation or an obsolete version.
Procedure
Reinstall your front-end software or inform your system administrator. If the error
continues to occur even if the front-end is correctly installed, you should inform SAP,
including details of how to reproduce the error.

SYSTEM_NO_ROLL

Each transaction requires some main memory space to process application data. If the
operating system cannot provide any more space, the transaction is terminated.

Try to find out (e.g. by targetted data selection) whether the transaction will run with less
main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the following profile
parameters:

o ztta/roll_area (1.000.000 - 15.000.000) Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000) Amount of memory per user in
extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000) Amount of memory (malloc) for
all users of an application server. If several background processes are running on one
server, temporary bottlenecks may occur.

CALL_FUNCTION_WAIT_ERROR

"Connection closed" An error occurred when executing a Remote Function Call.

There is an error in the communication system. To clarify and resolve the error, contact
your system administrator.

DBIF_RSQL_SQL_ERROR

SQL error 1555 occurred when accessing table

Database error text........: "ORA-01555: snapshot too old: rollback segment.

If the error occurred in a non-modified SAP program, you may be able to find a solution
in the SAP note system. If you have access to the note system yourself, use the following
search criteria:

"DBIF_RSQL_SQL_ERROR"
"AQA0ZCS=========ZCS_LEG_ENTITY"or
"AQA0ZCS=========ZCS_LEG_ENTITY”
"START-OF-SELECTION"
DATASET_TOO_MANY_FILES

Maximum number of open files exceeded. This is probably due to an error in the ABAP/4
program.

DBIF_DSQL2_SQL_ERROR

An SQL error occurred when executing Native SQL. Error 235 occurred in the current
database connection.
Database error text........: "ORA-00235: control file fixed table inconsistent due to
concurrent update"

CONNE_IMPORT_WRONG_COMP_TYPE

Error when attempting to IMPORT object. Error in ABAP application program.

When attempting to import data, it was discovered that the data type of the stored data
was not the same as that specified in the program.

IMPORT_ALIGNMENT_MISMATCH

Error when importing object. This is probably due to an error in the ABAP/4 program.
When importing object, the structure did not match the structure of the target object. The
error occurred in component

This may be due to one of the following reasons:

- The structure is actually different (the next field has, for example, a different data type)
or
- The same sequence of components were exported and imported, but the fields were
from other include units.

There is a probably a new version of the program which does not match the dataset. The
data may not have been converted. It is also possible that the field type of the imported
field has been changed in the ABAP/4 Dictionary.

SAPSQL_ARRAY_INSERT_DUPREC

The ABAP/4 Open SQL array insert results in duplicate database records. This is
probably due to an error in the ABAP/4 program.

If you use an ABAP/4 Open SQL array insert to insert a record in the database and that
record already exist with the same key, this results in a termination.

Use an ABAP/4 Open SQL array insert only if you are sure that none of the records
passed already exists in the database.
SUM_OVERFLOW

Field too small when calculating totals in internal table; this is probably due to an error in
the ABAP/4 program

The current program uses an internal table to calculate totals, but the totals field intended
for this purpose is not large enough.

As a temporary remedy, you could perhaps divide the process into smaller units, so that
the totals are smaller.

TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

No roll storage space of length 2310416 available for internal storage.

Each transaction requires some main memory space to process application data. If the
operating system cannot provide any more space, the transaction is terminated.

Try to find out (e.g. by targetted data selection) whether the transaction will run with less
main memory.
If there is a temporary bottleneck, execute the transaction again.
If the error persists, ask your system administrator to check the following profile
parameters:

o ztta/roll_area (1.000.000 - 15.000.000) Classic roll area per user and internal mode
usual amount of roll area per user and internal mode
o ztta/roll_extension (10.000.000 - 500.000.000) Amount of memory per user in
extended memory (EM)
o abap/heap_area_total (100.000.000 - 1.500.000.000) Amount of memory (malloc) for
all users of an application server. If several background processes are running on one
server, temporary bottlenecks may occur.

RFCGUI_UNEXPECTED_DATA
CALL_FUNCTION_RETURN_ERROR

ABAP DUMP ERRORS

1."RFC_NO_AUTHORITY"

If there is ERRORS starts with AUTHORITY PERMISSIONS u need to intimate to

SECURITY TEAM

This is “RFC_NO_AUTHORITY” short dump for user "DURDENCM", please drop a

mail to security team.

2. TSV_TNEW_PAGE_ALLOC_FAILED

I looked at the OSS notes and nothing seems to have reasonable solution for my problem.
All the OSS talk about is the memory parameters. I have the following key parameters
defined in the system
abap/heap_area_nondia 800000000
abap/heap_area_dia 800000000
abap/heap_area_total 1500000000
ztta/roll_area 6500000
ztta/roll_extension 2000000000
em/initial_size_MB 1000

3.DATASET_NOT_OPEN

This group contains runtime errors that may occur during file access. Typical examples
are if the system cannot find the file, if no more space is available to write or create the
file, or if the authorization to access the file is missing.
When we check in SM37, We are seeing a background job that is getting terminated. In
the job log it says DATASET_NOT_OPEN, Job cancelled. It is trying to run
"RDDVERSI" program.
It is creating a Dump in ST22 and when we check the Dump in ST22, it says "The file
"/usr/sap/trans/tmp/D01V985854.P01" has not been opened".
I checked the log in the trans directory and it gives me following error)

4.ITAB_ILLEGAL_COMPONENT

5.OBJECTS_OBJREF_NOT_ASSIGNED_NO

This might be a temporary error which might occur because of "controls not being
refreshed" on UI.You can reload the page and it should start working.)

6.UNCAUGHT_EXCEPTION (Have you referred the following note

NOTE: if you cannot activate RSD_IOBJNM_PARSE (error message of the type

"Typ Name_Error not found"), you try to delete the lines with the
exception NAME_ERROR under the "Exceptions" section in SE37 for
RSD_IOBJNM_PARSE, you try to insert them again (text irrelevant) and you
try to activate the function module again.)

7.MEMORY_NO_MORE_PAGING

Related to Memory

8.SYSTEM_CANCELED

The issue seems to be table space issue.

9.DYNPRO_SEND_IN_BACKGROUND

We are almost through, actually

NOBINPT='X' seems to be solved the problem
we are creating more testing data to confirm this Is NOBINPT a parameter ID
yes, NOBINPT or something equivalent described as "activate batch mode" or "enable
dark processing" is an IMPORT parameter of the BAPI/RFC.
ust read the doc on call trans and found out by default that NOBINPT = 'X'. The main
reason this dump occurs, I think, is that the mode was set to 'E' instead of 'N'. Setting it to
'E' would result in an error screen popping up if the message control was set that way.
Right now, the dump has not occured after making this change

10.SAPSQL_ARRAY_INSERT_DUPREC
I am getting SAPSQL_ARRAY_INSERT_DUPREC update termination dump while
updating invoice (vf01) , purchase order(MIGO), movement type into the database.
I am unable to understand this sudden raised problem with MM, PP,SD modules at the
same time.
Hereunder i am pasting some part of the dump.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
in procedure "INSERT_TABLES" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.

11.CONV_EXIT_FIELD_TOO_SHORT

I am getting a dump "Runtime error: CONV_EXIT_FIELD_TOO_SHORT"

Output field too short for converted value.
in the function module CONVERSION_EXIT_ALPHA_INPUT.
This function module is used in the program like as follows:
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
INPUT = <fs>
IMPORTING
OUTPUT = lv_partner

and lv_partner is declared like this:

data: lv_partner type bu_partner.
bu_partner is of character 10.

Its due to the insufficient length of output field.So increase the length of output field.
The problem is that the fields in the FM CONVERSION_EXIT_ALPHA_INPUT
doesnot have data type.

12.SYSTEM_CORE_DUMPED

it is common error.it is kernel error.i think if u upgrade the kernel,oracle it will slove.this
is not dangerous error

13..MESSAGE_TYPE_X

This MESSAGE_TYPE_X short dump is mostly caused by unstable processing in

Frontend / SAPGUI or in its installation. The common solution for this problem is to use
another stable SAPGUI version with uninstalling the existing and installing another
version. The stable version doesn't mean the latest version but certain patches level. Most
of the time the certain patches level is also the latest one. So try first to use the latest GUI
version such as SAPGUI 7.10 patches level 2.
Sometimes applying the only patches doesn't work, we need to uninstall the SAP GUI
completely then install another.)

14.TIME_OUT

After a certain time, the program is terminated in order to clear the work area for another
waiting user. This ensures that no work area is blocked for too long. The maximum
runtime of a program is defined by the system profile parameter
"rdisp/max_wprun_time". The current setting is 900 seconds. Once this has elapsed

15.ITAB_DUPLICATE_KEY

After consulting a few SAP guru's I found the solution which I have outlined below. The
cause of the issue is that even after an old system connection has been removed some
unused objects can still remain, failing to be cleaned up properly, this causes duplicates
and hence the ABAP dump. In short you have to identify and delete the duplicate objects
yourself and then you will be able to load data again.)

16.OBJECTS_OBJREF_NOT_ASSIGNED

OBJECTS_OBJREF_NOT_ASSIGNED is related to ABAP Objects. Somewhere the

program refers to an object instance which is not created yet)
17.RAISE_EXCEPTION

This kind of error occur because there bugs cause by the earlier version of the SAPGUI
To solve it, go to OSS and apply the SAP GUI's latest front end patch to your
PC/Laptop.)

18. ASSERTION_FAILED

I solved exactly the same issue using a note involved in SP 18(Support Pack) last week.
But as you're running on SP20, it can't help you.
In your case, have a look at SAP Note 1165168. Maybe it can help you.

19. ASSIGN_LENGTH_0

When i try to delete batch input jobs thru sm35 , i get an abap dump
"ASSIGN_LENGTH_0" .
SAP has given to me solution:-
1) Delete all null entries in object field of table usr12 and ust12.
2)Reorganize APQD and APQI tables .
Since RSBDCREO only deletes processed jobs so normal housekeepping cannot
be done for the sessions which r in processing state. If somebody has faced
this problem before or somebody has any suggestions kindly revert.

20. DBIF_RSQL_INVALID_RSQL

I guess ur production server has a lot of data,Also the dump says that max size of Sql
stmt is reached which means the select dumps due to data over load.
what u can do is split the data and run thr program the required no of time u want or see
whetehr u can pass some more fields to the select where clasue.

I have one problem. Our background job of a customized program failed with shortdump
DBIF_RSQL_INVALID_RSQL. When I check at wp trace file,I found statment below.
Tue Dec 12 10:39:04 2006
*** ERROR => max. statement length (65536) exceeded
token_cnt_156, input_cnt`60, marker_cnt`60, stmt_lengthY690
***LOG BYK=> current SQL statement exceeds a database limit [dbtran#6 @ 7261]
[dbtran 7261 ]
dbtran ERROR LOG (hdl_dbsl_error): DbSl 'PRE'
Are you able to advise which parameter I should adjust?
Fyi, I saw some parameter as below.
SHM_PRES_BUF###(addr: 0xc00000000c007000, size: 20000000)
SHM_ROLL_AREA##(addr: 0xc000000018000000, size: 134217728)
SHM_PAGING_AREA##(addr: 0xc000000020000000, size: 201326592)
SHM_ROLL_ADM###(addr: 0xc00000000d31b000, size: 2672386)
SHM_PAGING_ADM##(addr: 0xc000000008d80000, size: 656416)
Thanks in advance

21. DEBUGGING_IMPOSSIBLE

22. CONNE_IMPORT_WRONG_COMP_LENG

How to correct the error

Try and find out why the length of the object is supposed to be 75.
There are a couple of possible reasons:
Perhaps the length of the field imported has changed in the ABAP
Dictionary. Check to see that the length of the field imported is
the same as the length of the field in the ABAP Dictionary.
If the data cannot be reconstructed from another source, if must
be read and converted using the "old" structure" and then
re-exported using the new structure so that future IMPORTs
always work with the new structure.
A new version of the program is may be active and this may no longer suit the dataset.
Try to get rid of the error by regenerating
program "SAPLSHI10 ". Proceed as follows: Call transaction SE38 and enter program
name "SAPLSHI10 ". Activate the program with the Generate/Activate"function.
/shamsul

23. CONVT_OVERFLOW

RSPO1043 job is failing with CONVT_OVERFLOW error.

The dump says:
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_CONVERSION_OVERFLOW',
was neither
caught nor passed along using a RAISING clause, in the procedure "NAMETEST"
"(FORM)"
.Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
When attempting to convert the value "4294168333 ",
an overflow occurred.
Please help. I have already tried deleting TemSe KONS*

24. CONVT_NO_NUMBER

1,76 is for ABAP not a number.

It have to be 1.76.
NO \"comma\" --> \',\' ... it have to be a \"dot\" --> \'.\'.
By: http://www.saptechies.com/profile/| 10 Sep 2008
this happens often when you are importing numbers as text from, say, an excel
spreadsheet, for example.
you need to clean up the data. another issue is that imported number over 4 significant
digits will have a separator in them (. in your case, i am guessing) this will also cause a
problem.
insert some code to clean up the field before trying to move it to a numeric field

* get rid of thousands separators

* do this first to avoid issues with the second part
replace all occurrences of '.' in test with ' '.
* change the decimal indicator to "standard"
replace all occurrences of ',' in test with '.'.
* now, get rid if the extra spaces
condense test no-gaps.
now you have a text field that can be moved into a numeric field. i use this for various
import functions, and it works for me. i dont have the decimal issue, but i do have the
separator issue with text fields

25. MEM_ALLOC_FAILED

f you are running in background, look if multiple jobs are running simultaneously at the
same time.
You want to talk with basis as this is related to memory issue.
Check the Memory available in DB02 or DB20 transaction( i guess as i am not with sap
system now and try rz10 & rz11
RZ10 uses to increase sap r/3 buffer dynamically. Currently i am looking for way for
increase the buffer for a particular program.

26. MESSAGE_TYPE_X_TEXT

MESSAGE_TYPE_X is a dump related to your GUI, upgrade your (or your users) GUI
patch to the latest level and that should solve the issue.
This issue has been discussed previously in several occations, please search before
posting

27. IMPORT_ALIGNMENT_MISMATCH
(Source and target object have incompatible types.)
Same sequence of components, but with type conflict or different alignment in structured
data types

28. OBJECTS_OBJREF_NOT_ASSIGNED

Each Employee must be assigned with central person in HRP1001 to run the posting.You
may please run this report for the one of the employee and then test posting should work.

RPU46CX_central_person_online

29. GETWA_NOT_ASSIGNED

Your fieldcat is not getting generated, thats the reason you getting this error.
If you are manually building your it_fieldcatalog, it_sort, or it_filter ensure that the field
names you provide exactly match the variable names in your it_outtab. I have frequently
seen this error and it often relates to a simple misspelled field name.

30. DYNPRO_FIELD_CONVERSION

A conversion error occurred while the program was trying to

display data on the screen.
The ABAP output field and the screen field may not have the
same format.
Some field types require more characters on the screen than
in the ABAP program. For example, a date field on a screen needs
two characters more than it would in the program. Attemting to display
Screen name.............. "SAPLMR1M"
Screen number............ 6310
Screen field............. "DRSEG-BPREM"
Error text............... "FX015: Sign lost."
My ABAPer debugged the same but still clueless.
Can any one solve the problem and suggest which entry we have done wrong in the PO.
In the same PO we have used 5 Condition types.

31. STACK_STATE_NO_ROLL_MEMORY
Memory Issue

32. COLLECT_OVERFLOW

Also check this sap note: 881968.

33. CALL_FUNCTION_SINGLE_LOGIN_REJ

he dump CALL_FUNCTION_SINGLE_LOGIN_REJ is created if some authorizations

for S_RFC or S_RFCACL are missing. Therefore you should carefully check the
authorizations of the users - not only of CUAREMOTE but from all users who are using
the "Trusted-RFC with same user" destinations.

34. CALL_FUNCTION_SEND_ERROR

Thanx praveen for reverting back..

i checked ST22..i checked the following error thre
RFCUSER_CRQ CALL_FUNCTION_SEND_ERROR
+Runtime Error CALL_FUNCTION_SEND_ERROR
Occurred on 25.09.2008 at 22:01:52

What happened? "CPIC-CALL: 'ThCMSEND'#Conversation ID not found " An error

occurred when executing a Remote Function Call. + here rfcuser_crq is the background
user used in BW system to take connection to CRM system..
and in CRM we r using a diff background user i.e ALEREMOTE to take connection to
CRM..
Please tell me wat may b the source of the problem and hw shud i proceed..

Goto RSMO check the status of the request and in the details log,select the transfer idocs
node which will show "idocs ready to be transferred to the application"
select that line and below you will get OLTP idoc number copy the same and go to CRM
system and run t code BD87
enter the idoc number and execute.In the next screen selct the inbound idoc with status 64
and process.
This will release the job in the source system.

35. CALL_FUNCTION_SYSCALL_ONLY

The RFC destination uses the wrong logon data (in other words, the values entered for
client, user, and password do not constitute a valid logon).

2.Not all servers within a system have the same kernel release and patch level.

3.The server does not have enough shared memory (PXA memory). For further details,
refer to transaction ST22 (ABAP dump analysis and the ABAP runtime errors
PXA_NO_SHARD_MEMORY or PXA_NO_FREE_SPACE.
The database key is different on the different servers within the system. This can be the
case, for example, if more than one network card is installed on the database server, so
that some servers identify the database server under a different host name and IP address.
You may be able to see this data in the database data section of the system status display
for the relevant server. The RFC logon screen only appears in dialog mode. In the
background, the RFC communication terminates with a message that the logon data was
incorrect (CALL_FUNCTION_SIGNON_REJECTED or
CALL_FUNCTION_SYSCALL_ONLY in the developer trace file or the system log).

Solution
1.Check the logon data against the destination used. Ensure that the user has not been
locked.
2.Ensure that all of the servers have the same kernel release and patch level.
3.Fix the shared memory (PXA) problem.
4.Ensure that all servers access the database server using the same host name and IP
address.

36. SYNTAX_ERROR

37. OPEN_DATASET_NO_AUTHORITY

38. LOAD_PROGRAM_NOT_FOUND

I am getting this dump when i am trying to run an interface program

Runtime Error: Load_Program_not_found
except : CX_SY_Program_not_found

How am i supposed to terminate this dump

Go to sm37 and check for the function module which it is saying as 'loadprogram not
found'.

This error comes if the function module is not activated also.

first check whether the program exist ? if so, then check whether program had been
activated ?

This some times may occur because of buffer over flow.

Pleasse check the tablespace "PSAPUNDO" and "PSAPTEMP"

This is sometimes temporary also.

39. LOAD_PROGRAM_LOST

On our productive system we are getting around 500 dumps a week of the type
LOAD_PROGRAM_LOST, related to the transactions MIRO,VA01,FBL1N,MIGO and
the programs GBTABCO0 and GBTABFI0.
We only transport orders from QA to productive on Thursday Morning around 3-4 AM,
from what i've read this error might happen when replacing versions of the same program
on runtime, i believe with the transport method we use its unlikely that the dump is
generated because of that, does anyone have any kind of experience with this kind of
dump and the possible solutions.

do these dumps point to some common program ?

Yes the common programs are GBTABCO0 and GBTABFI0,

in adittion after talking with the FI Department, i found that apparently this happens
when any user changes entries on a SET that contains all the Accounts for validation
purposes, it seems like those programs regenerate everytime that happens and the dump
occurs.

Please check SAP Note : 452644 ..

5451

Hi, thanks for the reply, i checked the note and its alredy implemented on our system via
support package, i believe thats not the same problem, thanks for the quick reply tho.

OR
When a user gets to the program that is having this
problem and R/3 attempts to load the generated version
from the buffer, it sees that the version is not the
most current and tries to swap it out for the most
current, but the load was lost from the pxa buffer,
hence the dump of LOAD_PROGRAM_LOST.

To correct the error you need to run tranx SAMT &

regenerate the program(s) that are listed in the dump.
You can then do a $SYNC in the OK code field in the
affected applciation server, but the other
application servers should not be running. After the
$SYNC, the other app servers can be brought up and the
buffers should then be in sync.

I'm not sure if this is what you are looking for in

terms of a solution/explanation. Please also refer
the rel. note: 162991 - Generation tool for abap.

40. ITAB_DUPLICATE_KEY
We found the easiest way to identify the duplicates within this table was to change the
view to Grid View. Then simply locate and delete the duplicate from the disconnected
system that no longer exists. If you do not have delete permission then ask your Basis
team to delete it for you.

41. RPERF_ILLEGAL_STATEMENT

42. SAPSQL_IN_ITAB_ILLEGAL_OPTION

43. GEN_SAPSQL_TOO_MANY_ITABS

44. CALL_FUNCTION_OPEN_ERROR
I am not sure about what is causing the roblem in your system. Did try to find the error on
the forum. Most of them refer sapnote 1079446 . Kindly have a look if this can be of any
help.
Most of the time, this error is due to users using an old SAPGUI patch level. Can you
update to the latest SAPGUI patch and see if this helps?
Referer the SAPNote 1075585.
Hope It will solve your error.

45. BCD_ZERODIVIDE

the program on execution, throws an error " BCD_ZERODIVIDE ".

This is due to the fact that, a line in the program has attempted to divide by Zero.
eg:
V_PERCENT = ( A / B ) * 100.
Here,
the value of B is zero, and hence this ABAP runtime.
What are the logics could be implied, when B is zero. I have no option to throw an error
mmessage, because it is a report,, am really unaware what even the report is doing..
suggest the ways to handle this situation.

Just change code as

IF B IS NOT INITIAL.
V_PERCENT = ( A / B ) * 100.
ENDIF.

Before that statement check B should not be initial.

EX.

If not b is initial.
V_PERCENT = ( A / B ) * 100.
endif.

46. LOAD_PROGRAM_CLASS_MISMATCH

are you getting a dump?

Refer to SAP note: 387866

Symptom
Runtime error LOAD_CLASS_VERSION_MISMATCH or
LOAD_PROGRAM_CLASS_MISMATCH in releases 45A and 45B.
The short dump reports that the "private / protected" part of the class interface would
have changed. Since neither inheritance nor friends are supported in release 4.5, there is
no reason for this kind of dependence. Neither is such dependence contained in the
where-used list, which is why terminations occur with changes which only affect the
private part of the interface.

Did u try to restart the program???

I think I had clicked the "Pass value" checkbox on one of the receiving object's
parameters by mistake, and then saved it (so it was not caused by the addition of the static
method).
I just deleted the constructor, re-entered it, and it was fine.

47. DYNP_TOO_MANY_RADIOBUTTONS_ON

This is the problem will come in the Production.

SAP given the OSS note for this problem:

Refer the OSS note: 214349.

Symptom
In the display of the purchase order history, a system termination occurs in view 'Basic
list' if the user executes the function 'Subtotal' or 'Sort'. The system terminates with error
message 'DYNP_TOO_MANY_RADIOBUTTONS_ON'.

Additional key words

DYNP_TOO_MANY_RADIOBUTTONs_ON, ME21N, ME22N, ME23N, purchase
order, purchase order history, grading, subtotal, MEPO

Cause and prerequisites

This is caused by a program error.

Solution
Implement the corrections specified in the section 'source code corrections'.

In addition execute the following steps:

1. Call Transaction SE38 (ABAP editor: initial screen) and enter 'SAPLMMHIPO' as
program name.
2. Select the option 'Text elements'
3. Press the function 'Change'
4. Select the view 'Text symbols' and create the following text:

Sym Text
027 Transaction/event

5. Save and activate your changes.

Source code corrections

Header Data

Release Status: Released for Customer

Released on: 12.04.2000 22:00:00
Priority: Correction with high priority
Category: Program error
Primary Component: MM-PUR-PO-GUI Enjoy Purchase Orders
Releases
Software
Component Release From
Release To
Release And
subsequent
SAP_APPL 46 46B 46B
SAP_APPL 46C 46C 46C

Highest Implemented Support Package

Support
Packages Release Package
Name
SAP_APPL 46B SAPKH46B06
SAP_APPL 46C SAPKH46C01

Corrections Instructions
Correction
Instruction Valid
from Valid
to Software
Component Type *) Ref.
Correction Last
Modifcation
157133 46B 46B SAP_APPL C P9BK039422 13.04.2000 11:46:55
157191 46C 46C SAP_APPL C P9CK021126 13.04.2000 11:58:46

48. SAPSQL_WA_TOO_SMALL

Note 1248052 solve my problem, thank you

49. TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

Memory Issue

50. BCD_FIELD_OVERFLOW

As teh dump says a certain field is too small to accept the result of some mathematical
calculation.
The problem might be with your data.

For example the decimal point notation is not being taken into consideration probable due
to some different currency or due to user settings.
For example 100.00 is considered as 10000.
So a resulting calculation is becoming too huge and therefore this results in this dump.

Or the other reason could be that indeed a small output length field might have been used
for taht particular field.

But if it is a standard field; the first reason might be responsible.

Just debug the idoc in forefround via WE19 and check.

I have found the issue .

The issue was due to a negative value in the GR quantitiy field of an process order .

To correct the issue of negative values in this field SAP has provided with OSS note
1352231

51. DBIF_RSQL_SQL_ERROR

52. COMPUTE_BCD_OVERFLOW