cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow run time dump

Former Member
0 Kudos

Hi all,

I am facing one strange problem . I have CRM workflow in production. Its working Perfectly except one problem. Out of 20-30 times workflow triggers perfectly, one time it is giving dump in background.

In SWEL , where I can see the log, I can see log of all workitems but for that  one out of thirty workitem, I am not able to see the log, I am not getting Display workitem button there...however it is showing Receiver Started correctly.

I traced it in ST22 using time. Same time this errored workitem triggered, same time one runtime dump is coming CONV_EXIT_FIELD_TOO_SHORT

in program SAPLALFA.

Frequency of this dump is one out of 20-30. Rest of the workflow instances are working perfectly.

Its is showing following message

Error in the SAP kernel.

The current ABAP "SAPLALFA" program had to be terminated because the
ABAP processor detected an internal system error.

Please suggest some solution. Is there any SAP note for this. Below is the screenshot for this...this problem is occuring rarely...rest of the time i m not getting this problem.

Accepted Solutions (0)

Answers (2)

Answers (2)

bpawanchand
Active Contributor
0 Kudos

Hi Abhishek,

Are you trying to create any CRM service order by using the business object BUS2000116, then may be you should check 1541070 note.

It might help you.

Regards

Pavan

Former Member
0 Kudos

Hi Pavan,

No I am not trying to create service order. My workflow gets triggered, whenever there is service order status change. Its pure custom BO and event, which is triggereing the workflow.

However i am using BUS2000116 and POSTPROCESSINGSTATUSSET event as terminating event of Workitem step in my workflow.

But it should matter only if it go till this step. Right now problem is coming at the time of Workflow itself.

bpawanchand
Active Contributor
0 Kudos

Hi Abhishek,

Your issue is very weird,  can you please download the dump and attach it, so that we would be in a position to understand and help you.

Regards

Pavan 

Former Member
0 Kudos

I think ..I got the issue...there was one ALPHA conversion routine call to convert Business partner number in custom program. It is fetching the value in CHAR32 type variable , may be that can be the reason. I replaced it with standard data element BU_PARTNER.

Now it will be moved to production in evening... Lets see..if problem persists or not.

thanks for help....

Former Member
0 Kudos

I think ..I got the issue...there was one ALPHA conversion routine call to convert Business partner number in custom program. It is fetching the value in CHAR32 type variable , may be that can be the reason. I replaced it with standard data element BU_PARTNER.

Now it will be moved to production in evening... Lets see..if problem persists or not.

thanks for help....

anjan_paul
Active Contributor
0 Kudos

Hi,

Its due to some binding element which is refer to some data element which have some conversion routine in its domain. Check some value length you are binding is not correct. You have to increase the length.

Former Member
0 Kudos

Hi anjan,

If it is binding error, it should occur each and every time workflow is getting triggered. but this is occuring only once in 50 times....

And in the name of binding I am only passing _EVT_OBJECT to my custom object, which I am using to trigger the workflow.

anjan_paul
Active Contributor
0 Kudos

Hi,

  Compare the element value when it is got dump, when is not. You will find something is different value in the element, for that reason it got dump.

former_member185167
Active Contributor
0 Kudos

Hello,

In the ST22 dump it should show the exact ABAP statement it has an error on.

Did you look for any OSS notes?

regards

Rick Bakker

hanabi technology