on 06-21-2010 7:42 PM
Hello,
I have to configure the field "activity type" on PM order (tcode IW31).
I want to make this field obrigatory and It can't come with default values. It must comes empty.
In SPRO, when a take off the link between the Order type and the default value for activity type (table T350), occurs the error bellow, on tcode IW31:
"No maintenance activity type could be determined"
After that, occurs a runtime error, and I can't enter in the IW31 to create the PM order.
Somebody knows how can I do what I need?
Tks, Camila.
Camila,
I am guessing you have removed all the MAT assignments to order type.Please double check to make sure that in transaction OIO5 there are entries available for the order type. Make sure there is no default value assigned to order type in transaction OIO4. Check Using transaction OIAN, for the influencing order type PM02 the MAT field has been set as mandatory.
This should all that's needed to accomplish your requirement.
If you are still receiving runtime error there might be some other problem.Check transaction st22 for system dumps and if you are not able to resolve the same paste the entire information here.
Regards
Narasimhan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Narasamhan,
Thank you for your reply!
I did exately what you said.
In transaction OIO5, the order type is linked with the MAT.
In transaction OIO4, there isn't default value to order type.
And in transaction OIAN, the MAT field is mandatory.
But the error persists!
Look a piece of the runtime error:
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).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
No maintenance activity type could be determined
Camila,
This shouldn't cause a short dump.what are the steps that you are following which is causing the short dump? I am guessing that you are just creating the order using the standard transaction IW31 and the MAT is available as a visible field on the screen with a question mark? If so, Please check the OSS notes for resolution and if you aren't able to find one, raise a OSS message.
Regards
Narasimhan
Hi Pete,
I'm going to post 2 messages with the error:
Message 1:
Runtime Errors MESSAGE_TYPE_X
Date and Time 22.06.2010 09:08:15
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:
No maintenance activity type could be determined
Long text of error message:
Diagnosis
The system could not determine a default maintenance activity type
for the order type.
System Response
Procedure
o Maintain the maintenance activity type in the screen.
o In future, to have a maintenance activity type proposed as a
default for an order type, you must maintain the authorized
maintenance activity types per order type using the Customizing
function.
If you are not allowed to perform the function, contact your system
administrator.
Technical information about the message:
Message class....... "I0"
Number.............. 226
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program SAPLINST
Include LINSTU12
Row 28
Module type (FUNCTION)
Module Name T350_READ
Message 2 (second part):
Source Code Extract
Line SourceCde
1 FUNCTION t350_read.
2 *"----
-
3 ""Lokale Schnittstelle:
4 *" IMPORTING
5 *" VALUE(AUART) LIKE T350-AUART
6 *" VALUE(LANGUAGE) LIKE SY-LANGU DEFAULT SY-LANGU
7 *" VALUE(MTYPE) LIKE SY-MSGTY DEFAULT ' '
8 *" EXPORTING
9 *" VALUE(ILART_TEXT) LIKE T353I_T-ILATX
10 *" VALUE(T350_WA) LIKE T350 STRUCTURE T350
11 *" EXCEPTIONS
12 *" NO_T350_ENTRY
13 *"----
-
14
15
16 *--- Pufferung übergeben -
17 t350_wa = t350.
18 ilart_text = t353i_t-ilatx.
19 *--- nur weiter wenn noch nicht gelesen -
20 CHECK t350-auart <> auart.
21
22 *--- Lesen Vorschlag ILA zur Auftragsart -
23 SELECT SINGLE * FROM t350
24 WHERE auart = auart.
25
26 IF sy-subrc <> 0.
27 if mtype <> space.
MESSAGE ID 'I0' TYPE mtype NUMBER '226'
29 RAISING no_t350_entry.
30 endif.
31 ELSE.
32 *--- Übergeben T350 Workarea -
33 t350_wa = t350.
34 *-> nur wenn nicht im Puffer und Sprache spezifiziert
35 IF t353i_t-ilart <> t350-ilart and
36 not language is initial.
37 *--- lesen Text zur ILART -
38 SELECT SINGLE * FROM t353i_t
39 WHERE spras = language
40 AND ilart = t350-ilart.
41 *--- Übergeben Text zur ILART -
42 ilart_text = t353i_t-ilatx.
43 ENDIF.
44 ENDIF.
45
46 ENDFUNCTION.
Edited by: Camila Peralta on Jun 22, 2010 2:17 PM
Camila,
Is this a new order type? The error is looking for a entry in table T350 ,which not only contains default MAT but also other parameters for the order type. It looks like you may be missing other configuration like priority type for order type or reference time for order completion or object info for order type etc
Please go through and complete all the relevant configuration for the order type.
Regards
Narasimhan
Hello,
it isn't a new order type... we always use it and we never had problems.
The only difference is, the field "MAT" always comes with default values (table T350).
Now, I need to take off this default value, because the end user have to put this information, not the system.
So, I erase the information on the table T350, using OIO4 transacion.
I think, If there isn't this link between the Order type and the default value for MAT (on table T3250), occurs this runtime error.
If I put the information there, the transaction works...
Camila,
The error is not specifically related to MAT.All its looking for is an entry in table T350. This is the default order type config table.
Just curious, when you you say you removed the default entry of MAT for the order type,I had been presuming that you just removed the default MAT value for the order type. You did not "Delete" the entire line item for the order type right? If you had deleted the line entry, this could also be the cause of the problem. Insert a line entry for the order type once again, but leave the default MAT value to be initial.
Regards
Narasimhan
Hi Narasimhan,
the description for transaction OIO4 is "maintain Activity type defualt for order types". In this transaction, I just link the order type with the field MAT. I just do that, nothing more.
But, When I put or when I take off the values in this transaction, it reflects directly on table T350.
Looking this table, there are more informations, not only the order type and the MAT.
But if I wanna take off the default value on PM order, I have to take off the information form transaction OIO4.
Automatically, the informaton on table T350 desappears...
I really don't know what to do...
In that case you need to first give default value for MAT. Then go to table T350 and note down all out put fields value.
Remove the default MAT in OIO4.
Then go to order type configuration and all the other out put value respective config area and re-enter all those values to have an out put in table T350.
User | Count |
---|---|
95 | |
11 | |
11 | |
6 | |
6 | |
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.