cancel
Showing results for 
Search instead for 
Did you mean: 

error at the time of saving sales order

Former Member
0 Kudos

Hi Sapfans,

at the time of saving the order i am getting the following error

please help me how to solve it

please help me fast

thanks and regards

srinivas

Runtime Errors MESSAGE_TYPE_X

Date and Time 19.11.2007 15:19:18

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

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

Trigger Location of Runtime Error

Program SAPMV45A

Include MV45AF0B_BAPIDATEN_ERMITTELN

Row 338

Module type (FORM)

Module Name BAPIDATEN_ERMITTELN

Source Code Extract

Line SourceCde

308 else.

309 *-----Nicht unterstützt, Abbruch

310 message a301(v3).

311 endif.

312 endif.

313

314 *-Szenario A prüfen

315 if lv_scenario_a = 'A'.

316 vbak-vbkla+2(1) = lv_scenario_a.

317 endif.

318

319 *-ermitteln CRM-Release

320 call function func_name

321 exporting

322 i_paraname = 'CRM_RELEASE'

323 importing

324 e_parval1 = lv_parval1.

325 lv_release_crm = lv_parval1+0(3).

326

327 * If lv_release_crm empty => X-message (correct download not possible)

328 if da_download_active = charx.

329 CALL FUNCTION 'CRM_CONNECTED'

330 IMPORTING

331 CRM_CONNECTED = lv_crm_connected

332 EXCEPTIONS

333 NO_CRMRFCPAR = 1

334 OTHERS = 2

335 .

336 IF sy-subrc = 0 and lv_release_crm = space and

337 lv_crm_connected = charx.

>>>>> message x302(v3).

339 ENDIF.

340 endif.

341

342 *-Füllen der View für das Ermitteln der Auftragstabellen

343 da_sales_view-partner = charx.

344 da_sales_view-sdcond = charx.

345 da_sales_view-sdcond_add = charx.

346 da_sales_view-contract = charx.

347 da_sales_view-text = charx.

348 *-bei mehr als 1000 Belegflusssätzen werden Daten nicht ermittelt

349 if lv_tabix_vbfa < 1000.

350 da_sales_view-flow = charx.

351 endif.

352 da_sales_view-billplan = charx.

353 da_sales_view-configure = charx.

354 da_sales_view-credcard = charx.

355

356 *-Im Standardszenario soll eine manuelle Änderung eines CRM Belegs

357 * (ab CRM Release 30A) nicht zurück ins CRM gesendet werden. Das

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi,

This is the problem of Basis people, still if you have the access of SAP notes, just update the current error programme with the updated note.

The access to these notes is in SAP service marketplace.

Just contact your Basis guy and tell him to implement the notes related to the dump.

Regards,

Siddharth.

Former Member
0 Kudos

HI,

This error is because of crm release patch.

You can update this patch.

Use Transaction code se16.

Type the table name-CRMPAROLTP

Go in New Entries

Type 'CRM_RELEASE' In First Field(PARNAME)

Type '40A' In Value 1 i.e. 5th Field

Save.

This will solve your problem.

If this is useful please give reward points.

Regards,

Ashok

Former Member
0 Kudos

the issue is while transferrring somedata from the CRM system into R/3 thre is a table updation error. Please check with your abaper in debug mode to find out the issue.

regards