Saving Incorrect Request Data 

Use

If you want to prevent event processing being terminated when formatting errors occur with incorrectly filled out ABAP Dictionary objects, you can define this using parameter UWS_NO_DDIC_EXIT.

Features

The parameter UWS_NO_DDIC_EXIT is generated in all pages of a BSP application by default. The presetting for this is that formatting errors in ABAP Dictionary objects cause the cause the event processing to be terminated.

<input name="uws_no_ddic_exit" type="hidden" value=" "/>

However, you can define that the event processing should not be terminated when formatting errors occur in the layout of each BSP page using the indicator VALUE="X". By defining this, you also indirectly ensure that BadI method FORM_ON_EVENT is run with the customer-specific error messages in each case.

Note the following if you have set indicator VALUE="X":

To prevent assignment errors or to stop having to carry out supplementary programming for the category check of ABAP Dictionary fields in the customer-specific BAdI methods, you must check whether a formatting error exists in table IT_MESSAGE (import parameter of BAdI method FORM_ON_EVENT). You can also check this using method CL_UXX_MESSAGE=>MESSAGE_EXISTING.

Example

The following example shows how you can read a message for field VALID_FROM using method CL_UXX_MESSAGE=>MESSAGE_EXISTING. If this is the case, the value ”X“ is returned.

 

IF cl_uxx_message=>message_existing(

                                 ir_node  = ir_form_data_envelope

                                 id_xpath = '/request/valid_from' ) IS INITIAL.