2008 Apr 02 1:33 PM
Hi GURUS,
While creating sales order (VA01), we gave all required data like customer no, material no, quantity etc. even we check incompletion log ..system give message Document is completed
But when we to the save the order, following ABAP runtime error comes ..
Runtime Errors MESSAGE_TYPE_X
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation
should not occur. Therefore, a termination with a sho
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
REGARDS
RAMKUMAR WARIYAR
2008 Apr 02 6:21 PM
Hi, as the OSS note 691710 is a short one here it goes:
Symptom
Errors occur when you transfer purchasing documents.
For example, the following errors may occur:
The document flow may be incomplete.
After a change in the R/3 system, the quantity disappears in the CRM system.
Others.
Other terms
Release, CRMPAROLTP, CRM_RELEASE, quantity, zero, settings, document flow, response missing, distribution status missing, document cannot be changed, transferring
Reason and Prerequisites
In the CRMPAROLTP table, the current CRM release was not maintained in the OLTP R/3 system.
Solution
You can maintain the CRMPAROLTP table in Transaction SM30 in the R/3 OLTP Backend System:
Parameter Name (PARNAME) "CRM_RELEASE"
Param. Value (PARVAL1) "30A" for a 3.0A Release
Maintain the corresponding value for other releases, that is, '400' for Release 4.00, '310' for Release 3.10 and so on.
Leave the user field empty.
Best regards.
2008 Apr 02 6:21 PM
Hi, as the OSS note 691710 is a short one here it goes:
Symptom
Errors occur when you transfer purchasing documents.
For example, the following errors may occur:
The document flow may be incomplete.
After a change in the R/3 system, the quantity disappears in the CRM system.
Others.
Other terms
Release, CRMPAROLTP, CRM_RELEASE, quantity, zero, settings, document flow, response missing, distribution status missing, document cannot be changed, transferring
Reason and Prerequisites
In the CRMPAROLTP table, the current CRM release was not maintained in the OLTP R/3 system.
Solution
You can maintain the CRMPAROLTP table in Transaction SM30 in the R/3 OLTP Backend System:
Parameter Name (PARNAME) "CRM_RELEASE"
Param. Value (PARVAL1) "30A" for a 3.0A Release
Maintain the corresponding value for other releases, that is, '400' for Release 4.00, '310' for Release 3.10 and so on.
Leave the user field empty.
Best regards.
2008 Apr 03 9:16 AM
Dear Sir,
Thank you for your solution,it has solved my problem.and i have reward points also
Regards
Ramkumar Wariyar