on 04-27-2011 11:33 AM
hi,
i am trying to fill the QM setup tables
but i got run time error like
-
-
Runtime Errors MESSAGE_TYPE_X
Date and Time 27.04.2011 18:28:17
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).
Error analysis
Short text of error message:
General object number: incorrect object type not QL transferred
Long text of error message:
Diagnosis
It is most likely that a function module from the general object
number management was called (e.g. OBJECT_KEY_GET_QL). As part of
this the object number with object type was transfered. The
function module may, however, only be called with object numbers
that have the object type QL.
Procedure
As a rule this indicates a system error. If necessary notify your
system administrator.
Procedure for System Administration
o If this error occurred in one of the standard SAP functions,
notify the SAP hotline.
o If this error occurred in your own programs or in any modified
by you, check the calls of the function modules for the general
object number management. Check in particular the function
modules OBJECT_KEY_GET_QL and OBJECT_NUMBER_DELETE_QL. For
generic calls (i.e. ones that do not depend on onject type),
use the function modules from function group BO01 (e.g.
OBJECT_KEY_GET or OBJECT_NUMBER_DELETE.
Technical information about the message:
Message class....... "BO"
Number.............. 003
Variable 1.......... " "
Variable 2.......... "QL"
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program SAPLBOQL
Include RBONRF01
Row 42
Module type (FORM)
Module Name OBART_CHECK
Source Code Extract
Line SourceCde
12 FORM CHECK_OBJNR USING OBJNR.
13 * SELECT SINGLE * FROM ONR00 WHERE OBJNR = OBJNR. "Aus Performance-
14 * IF SY-SUBRC = 0. "Gründen nicht mehr
15 * MESSAGE E001 WITH OBJNR "auf der Datenbank
16 * RAISING NUMBER_ALREADY_EXISTS. "lesen!
17 * ENDIF. "
18 * prüfen, ob Objektnummer bereits in interner Tabelle
19 ONR_INS = SPACE.
20 ONR_INS-OBJNR = OBJNR.
21 READ TABLE ONR_INS.
22 IF SY-SUBRC = 0.
23 MESSAGE E001 WITH OBJNR
24 RAISING NUMBER_ALREADY_EXISTS.
25 ENDIF.
26 * merken, daß Objektnummer für Objektart vergeben wurde
27 CALL FUNCTION 'OBJECT_TYPE_STORE'
28 EXPORTING
29 OBART = OBJEKTART.
30 ENDFORM.
31
32
33 *----
-
34 * Form OBART_CHECK
35 *----
-
36 * Prüft, ob beim Aufruf eines objektartabhängigen FBausteins
37 * (z.B. OBJECT_KEY_GET_xx) eine Objektnummer der richtigen
38 * Objektart übergeben wurde
39 *----
-
40 form obart_check using value(v_objnr) like ionra-objnr.
41 if v_objnr(2) ne objektart.
>>>>> MESSAGE x003(BO) WITH v_objnr(2) objektart
43 raising wrong_obart.
44 * Allgemeine Objektnummer: falsche Objektart &1 statt &2 übergeben
45 endif.
46 endform. "OBART_CHECK
Can any one help me regarding the same
Regards,
Raj
Edited by: Raj on Apr 27, 2011 7:07 PM
Edited by: Raj on Apr 27, 2011 7:07 PM
Hi Rajesh,
Which transaction code you were trying when you encountered with this problem?
Regards
Anand Rao
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
108 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.