2010 May 19 5:53 AM
Hi Gurus,
Have a concern wrt an editable ALV.
I have an editable ALV in which a field's(Chain ID is the name of the field) domain has
fixed intervals. The fixed interval is defined as:
T000000000 TZZZZZZZZZ
S000000000 SZZZZZZZZZ
Which means that the values for this field can start only with T or S. In the ALV, for this
field I may have blank values getting displayed. If I enter a valid value in the ALV then
its ok but when I delete the same value the ALV protocol shows an error 'Enter a valid
value'. The system is interpreting the value to be 'entered' in the ALV as 'space' as its
not valid as per the fixed intervals. BUt this actually should not happen because I am just
undoing my change. Can anyone suggest a way so that this validation is skipped and the ALV thus can accept initial value?
Thanks and Regards,
Sravan.
Edited by: sravan sriram on May 19, 2010 6:54 AM
Hi Gurus,
Have a concern wrt an editable ALV.
I have an editable ALV in which a field's(Chain ID is the name of the field) domain has
fixed intervals. The fixed interval is defined as:
T000000000 TZZZZZZZZZ
S000000000 SZZZZZZZZZ
Which means that the values for this field can start only with T or S. In the ALV, for this
field I may have blank values getting displayed. If I enter a valid value in the ALV then
its ok but when I delete the same value the ALV protocol shows an error 'Enter a valid
value'. The system is interpreting the value to be 'entered' in the ALV as 'space' as its
not valid as per the fixed intervals. BUt this actually should not happen because I am just
undoing my change. Can anyone suggest a way so that this validation is skipped and the ALV thus can accept initial value?
Thanks and Regards,
Sravan.
Edited by: sravan sriram on May 19, 2010 6:54 AM
2010 May 19 9:03 AM
At check_changed_data , you can check if the the value for this cell was initial and at the time of save/enter also its initial then do not process chain block.
2010 May 21 5:15 AM
Skipping processing of the chain block will not stop the message from coming as the message is raised from the domain level. If you mean that among other things I need to delete that message from the protocol then in that case the changed value strangely does not get deleted. It comes back to the value which has been put before deleting it...