cancel
Showing results for 
Search instead for 
Did you mean: 

Error ' SYSFAIL ' in SMQ1

Former Member
0 Kudos

Hi ,

When i m maintaining a relationship to BP . system is throwing the below error :

In SMQ1 , I m getting error " SYSFAIL " .When i double click on that it is giving description as ' Incorrect parameter with CALL FUNCTION "

In SMW01 , it is showing BDOC error as SEE_TABLE_SMW3_BDOCQ .

I have checked the short dump error in target system and it is showing error description as CALL_FUNCTION_PARM_MISSING .

Could any one suggest me what could be the cause of error .

Thanks & Regards,

SAPCRM

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Please check note 648311 BAPIs: BAPI_DOCUMENT_GETDETAIL2 enhancement , it worked for us

Former Member
0 Kudos

Hi,

Try to check the middleware tables. CRMRFCPAR and CRMSUBTAB, whethere business partner is activated for initial and delta changes or not.

//Bhanu

Former Member
0 Kudos

Hi,

Please check OSS Note: 641816 for this error.

I hope this helps.

Regards,

Gaurav Gera

Former Member
0 Kudos
Former Member
0 Kudos

Srinu and Gaurav ,

Thank u so much for ur quick reply .

Srinu : I have checked the EDPP1 and no data is maintained in that . Plz suggest me what data should be maintained in that table .

Gaurav : Thanks for giving that note .But is there any way other than changing code to the standard program which is suggested in given note . .

Thanks & Regards,

SAPCRM

Former Member
0 Kudos

Hi ,

Any more suggestions please.

Thanks & Regards,

SAPCRM

Former Member
0 Kudos

Hi Sapcrm,

Try to execute the queue in debug mode and see where it is failing. This should give you an idea on which function module it is falling over.

This would also help you to check if any of the data segments has got invalid character which is not being interpreted. Sometimes the function falls over if any of the data segment has got a field value which could not be converted (and back) from char to XML. I have seen similar problems on one of CRM 5.0 project.

From the description of your message it seems that an OSS note is most likely going to be a solution.

Is this problem happening only for a particular bdoc or for all bdoc's of one particular bdoc type or for all type sof bdoc?

Have you extended the bdoc type which is giving problems?

Regards,

Surendar