Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

FI Validation rule error message problem at line item level

Former Member
0 Likes
1,786

Hello all.

I have created a step within an FI Validation rule (OB28) at the document line item level. I have set the message to "E" for an error. I have generated the validations. When I test my step, the error is triggered, but triggered as an Information popup - warning and does not give me a hard stop. Does anyone have an idea why this may happen? I need this to be a hard stop but not a cancellation of the document entry. I am using FV60 to enter my document.

Thanks for help.

mvp0821

Hello all.

I have created a step within an FI Validation rule (OB28) at the document line item level. I have set the message to "E" for an error. I have generated the validations. When I test my step, the error is triggered, but triggered as an Information popup - warning and does not give me a hard stop. Does anyone have an idea why this may happen? I need this to be a hard stop but not a cancellation of the document entry. I am using FV60 to enter my document.

Thanks for help.

mvp0821

4 REPLIES 4
Read only

Former Member
0 Likes
968

Did you make the message type "E" in OB28?

Rob

Read only

Former Member
0 Likes
968

Hi.

Yes... i have marked it as "E". The message is part of a custom message class "Z..". Does this have an effect? I read another posting on a different forum and user had same problem and their message was contained in a custom message class.

Read only

0 Likes
968

I have a validation with an error message and a custom message class. It works fine.

Rob

Read only

Former Member
0 Likes
967

OSS note # 863267 explains answer. Cannot create "error" message on ENJOY transactions - FV60 is included in this list. "E" works on classic transactions.

Thanks for thinking about this.