Dump IW31 after assigning several people to the work order

Question

I get the following dump when trying to add several people to a WO with IW31:
Runtime Errors         RAISE_EXCEPTION
Date and Time          24.04.2008 09:46:51
Short text
Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
Error analysis
A RAISE statement in the program "CL_EXITHANDLER================CP" raised the
exception
condition "DATA_INCONS_IN_EXIT_MANAGEM".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
Trigger Location of Runtime Error
Program                                 CL_EXITHANDLER================CP
Include                                 CL_EXITHANDLER================CM001
Row                                     155
Module type                             (METHOD)
Module Name                             GET_INSTANCE
Source Code Extract
Line
SourceCde
125
IF is_impl = 'X'.
126
      ok at least one implementation found
127
act_imp_existing = 'X'.
128
ENDIF.
129
130
ENDIF.
131
ENDIF.
132
ELSE.
133
134
check how many implementations exist for an exit
135
CALL METHOD cl_badi_flt_data_trans_and_db=>act_imps_per_flt_val
136
EXPORTING
137
runtime_call                  = seex_true
138
exit_name                     = exit_name
139
EXCEPTIONS
140
singular_exit_multiply_active = 1
141
no_active_implementation      = 2
142
only_default_implementation   = 3
143
OTHERS                        = 4.
144
CASE sy-subrc.
145
WHEN 0.
146
act_imp_existing = seex_true.
147
WHEN 1.
148
RAISE single_exit_multiply_active.
149
WHEN 2.
150
act_imp_existing = seex_false.
151
WHEN 3.
152
act_imp_existing = seex_false.
153
def_impl = seex_true.
154
WHEN 4.
>>>>>
RAISE data_incons_in_exit_managem.
156
ENDCASE.
157
158
new parameter considered for performance purposes
159
IF act_imp_existing = seex_true OR
160
def_impl = seex_true OR
161
null_instance_accepted = seex_false.
162
163
ok, then do your job
164
CREATE OBJECT exit TYPE (abs_type_classname).
165
CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
166
instance ?= exit.
167
ENDCATCH.
168
IF sy-subrc = 1.
169
RAISE cast_error.
170
ENDIF.
171
172
ENDIF.
173
ENDIF.
174
ENDMETHOD.                    "
Does anyone have the solution for this?
Thanks!

Answer 1

I am using SAP ECC 6.0.
SAP Basis Component and Cross-Application Component: release 700, level 013
Is there any other information you need?
Could I still use this OSS note with this version?
Also, the issue is not about the response time like mentioned in the OSS note.