Entering content frame

This graphic is explained in the accompanying text SAP_DEMO01: Request for Parking Permit Locate the document in its SAP Library structure

Use

Request category SAP_DEMO01 demonstrates for example which layout functions you can implement in Web requests. The input and display fields available and the use of OTR texts are demonstrated. The assignment of default entries for requester data and the error handling of incorrect or missing entries are displayed in the demo request category.

 

The request category views S01_1 (requester view) and S01_02 (processor view) are delivered.

Prerequisites

You have maintained the business partner data including the role Internet user for the respective user   (see Web Services for Self-Registration and Master Data Changes).

Features

The following characteristics and functions are displayed:

Language-dependent texts

OTR short and long texts enable you to support the texts of the field label language-dependently.

Different input fields

The demo request contains one/several-line text fields, combo boxes, selection buttons and checkboxes.

Assigning default entries

Business Add-In (BAdI) CRM_SERVICE_WEBREQ is used to assign default entries for fields in accordance with the relevant user by method FORM_ON_CREATION. A manual entry of address data is only allowed for the e-mail address.

Entry checks/error handling/auto-correction

When using BAdI CRM_SERVICE_WEBREQ, the entries are checked by method FORM_ON_EVENT.

The following checks are implemented:

·        The e-mail address is a required entry field. In this example, the check is to see whether the special character ’@’ is entered in the field. If this special character is missing, an error message is issued.

·        The license plate number is a required entry field.

·        The validity time is a required entry field.  A check is carried out on the date format supported by the ABAP Dictionary and the year is checked to make sure it is no smaller than the current calendar year. If an older year is entered, the system makes an auto-correction that is displayed as a persistent error message.

·        If the combination of category ’motorcycle’ and length ’longer than 3m’ is entered, a warning message is issued.

·        The incorrect fields are highlighted in the processor view. It is possible to navigate from the message to the corresponding field. A success message is issued if the entries in the request form are correct.

See also:

Error Handling in the Web Request Form

BadI and method documentation of CRM_SERVICE_WEBREQ.

 

 

 

 

Leaving content frame