While doing SO, im getting run time error - reg;

[Former Member]

Hi,

While doing sales order and whenever im doing save its getting runtime error.

Runtime Errors MESSAGE_TYPE_X

Date and Time 14.12.2011 10:55:26

Short dump has not been completely stored (too big)

Short text

The current application triggered a termination with a short dump.

What happened?

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).

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

Error analysis

Short text of error message:

Maintain the current CRM release (table CRMPAROLTP)

Long text of error message:

Diagnosis

Various transfer errors occur when transferring SAP sales orders to

CRM or there is no status update or the status update has errors

when transferring from CRM to the SAP system. This is caused by an

incorrect entry for the CRM release in the SAP table CRMPAROLTP, or

no entry is maintained at all.

System Response

To avoid data inconsistencies, this message causes a short dump.

Procedure

Maintain table CRMPAROLTP in your SAP system as is described in SAP

Note 691710 and then repeat the process again.

Procedure for System Administration

Technical information about the message:

Message class....... "V3"

Number.............. 302

Variable 1.......... " "

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

Runtime Errors MESSAGE_TYPE_X

Date and Time 14.12.2011 10:55:26

hort dump has not been completely stored (too big)

If you have access to SAP Notes, carry out a search with the following

keywords:

"MESSAGE_TYPE_X" " "

"SAPMV45A" or "MV45AF0B_BAPIDATEN_ERMITTELN"

"BAPIDATEN_ERMITTELN"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "personal"

Network address...... "192.168.2.11"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x Intel 80686"

Character length.... 16 Bits

Pointer length....... 32 Bits

Work process number.. 1

Shortdump setting.... "full"

Database server... "PERSONAL"

Database type..... "ORACLE"

Database name..... "GCU"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Aug 29 2006 00:18:21"

create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version. "OCI_10201_SHARE (10.2.0.1.0) "

Patch level. 75

Patch text.. " "

Runtime Errors MESSAGE_TYPE_X

Date and Time 14.12.2011 10:55:26

hort dump has not been completely stored (too big)

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory consumption

Roll.... 8176

EM...... 30311496

Heap.... 0

Page.... 139264

MM Used. 14538320

MM Free. 91952

User and Transaction

Client.............. 100

User................ "INFO_SD"

Language key........ "E"

Transaction......... "VA01 "

Program............. "SAPMV45A"

Screen.............. "SAPMV45A 4001"

Screen line......... 65

Information on where terminated

Termination occurred in the ABAP program "SAPMV45A" - in "BAPIDATEN_ERMITTELN".

The main program was "SAPMV45A ".

In the source code you have the termination point in line 338

of the (Include) program "MV45AF0B_BAPIDATEN_ERMITTELN".

Edited by: kiran35086 on Dec 14, 2011 6:30 AM

[Former Member · Accepted solution]

Try the following and let me know the result

T.Code: SM30.

In menu, choose System Services Table Maintenance Extended Table Maintenance .

In the Table/view field, enter the table name CRMPAROLTP.

Choose Maintain.

Choose New Entries.

In the Parameter Name field, enter CRM_RELEASE.

In the Parameter.Value field, enter 500.

Choose Save.

[Former Member · Accepted solution]

Yes its solved.

May i know why its happened.

thanks for all

[Former Member · Accepted solution]

Those are uncommon issue which we to maintain when it gets the issue.

It is based on the release which is required to process the transaction further.

[Former Member]

Hi to all,

Im not done any enhancements..i already checked with ABAP team they also not getting any solution

[Former Member]

Dear kiran,

This might be many reasons.If you have not done configuration properly system will take you to dump(Run time error).

Try read the diagnosis possibly you may understand the problem.

If not You coordinate with your technical team.

Thanks&Regards

Raghu.k

[Former Member]

As it is mentioned there. Pls check in ST22 T.code to anlyse the error with the help of ABAPers.

Can u also explain about ur enhancement done in SO.

[Former Member]

Hi,

Check whether you developed any enhancement in the include MV45AF0B_BAPIDATEN_ERMITTELN in program SAPMV45A

Consult your abaper.