Hi there,
can anyone help me on the error log during posting sales order via va01? the checking of sales order is correct.
Runtime Errors MESSAGE_TYPE_X Date and Time 2009.02.17 10:11:37 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. | | 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. | | | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |User and Transaction| | Client.............. 200 | | User................ "SAMSON"| | 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". | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Source Code Extract | ---------------------------------------------------------------------------------------------------- |Line |SourceCde | ---------------------------------------------------------------------------------------------------- | 308| else. | | 309|*-----Nicht unterstu9EF7zt, Abbruch | | 310| message a301(v3). | | 311| endif. | | 312| endif. | | 313| | | 314|*-Szenario A pru9EE4en | | 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|*-Fu9EEElen der View fu9EF5 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 Belegflusssu92DEzen 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 u818Ederung eines CRM Belegs| | 357|* (ab CRM Release 30A) nicht zuru9EDEk ins CRM gesendet werden. Das | ----------------------------------------------------------------------------------------------------
any responses will be awarded,
regards,
samson