Defining Custom Fields

Objective

After completing this lesson, you will be able to define custom fields to address data requirements that are not met by standard fields

Field Properties

"You can specify basic field properties such as field name, field type, default value, required field, and so on."

Go through each of the following properties to learn more.

  • Label: Specifies the user-visible name of the field. Limit labels to 30 characters or less. The system removes characters that it does not allow.
  • Field Name: By default, the system uses cus_label as the internal name for custom fields. However, you can customize this internal name for both custom fields and standard fields to be the label you want to display in the user interface.
  • Type: Specifies the type of field. For example, Account, Boolean, Currency, Date, User, and so on.
  • Pick list: Displays a list of choices in a dropdown control. By default, the user can also select No choice as an option. This works correctly for string or int fields.
  • Require Selection (If Pick List is selected): Require users to select an item from the item chooser, instead of leaving the field empty. The application will not allow users to continue without setting a value for the field.
  • Help Tip: Displays an information icon and specifies the text that displays when users select the icon.
  • Available on Reports: Indicates whether the field data is available in the Reporting module for use in reports. By default, this field is available for use in reports.
  • Respect User Value: If you specify a computed value expression and the user overrides it by entering a value, the system respects the value entered by the user. This setting also prevents the system from changing computed values each time the form is displayed.
  • Default Value: The initial value for the field when the form is displayed.
  • Expression: SAP Ariba expression that determines the value of the field. This is typically used for computed fields, but can also be used to specify a default value for a normal field.
  • Show in Views: Details: Specifies the views that display the field. The choices are: Print, Details, Search, Edit, and Mobile Summary. For example, if you have an Employee Information form and users are not allowed to search for employees based on gender, you can hide the Gender field in search pages. Or, if you create a confidential field, such as Social Security Number, you might want to hide it from the Details view so that it does not appear when users display the form.
  • Behavior: Required: Specifies whether users must enter a value and displays an asterisk beside the field, which indicates that the field is mandatory. The application will not allow users to continue without setting a value for the field.

Let's understand how we can apply conditions over custom fields.

You can specify when a field is visible, editable, and valid by writing and applying conditions. The Ariba expressions language is based on Object-Graph Navigation Language (OGNL) using if/then logic.

When you define a condition, use an SAP Ariba expression. The field is visible, editable, or valid when the SAP Ariba expression is true. For example, when working with savings form templates, you can also use a validity condition to make a custom field conditionally required, depending on an SAP Ariba expression that evaluates the values of savings form values.

Visibility

An SAP Ariba expression that determines when this field is visible. When the expression evaluates to true, the field is visible.

  • Example: cus_ContainsDairy == false

This expression causes the field to disappear if a user sets the Boolean "Contains Dairy" field to No.

Editability

An SAP Ariba expression that determines when this field is editable. When the expression evaluates to true, the field is editable.

  • Example: cus_ProductNumber <= 1000

This expression causes the field to be a non-editable (read-only) field if the "Product Number" field is 1001 or greater.

Validity

An SAP Ariba expression that determines when this field is valid. When the expression evaluates to false, the field is invalid and an error message that you supply displays.

  • Example: cus_SuppliersName != 'Bruce’

This expression causes the field to issue an error if a user enters the string "Bruce."

The Conditions property displays two values for each section: Applied and Custom.

Applied Condition

This is the predefined condition for the field.

Custom Condition

This is the condition you define for the field.

Custom conditions, once published, appear in the Applied section as well.

The system uses the "AND" boolean operator to join the two conditions together, which determines the behavior of the field.

"Let's see what the advanced properties of custom field are."

You can specify field behavior in special situations with the advanced properties.

Examples of features within Advanced:

  • Optional Search Field
  • Include field in approval email notifications
  • Refresh screen on value change
  • Hide
  • Hide Label
  • Procurement Operations Desk field

For more information on Custom Fields, see the Intelligent Configuration Manager administration guide at Help.SAP.com.

Log in to track your progress & complete quizzes