SAP Knowledge Base Article - Public

2945112 - Mandatory fields in the child object is not recognized

Symptom

Customer has a child object where some or all fields are mandatory / required. Customer can still save the object even if he / she hasn't filled out any of the required / mandatory fields in the child object.

Environment

  • SAP SuccessFactors HCM Suite
  • Metadata Framework (MDF)

Reproducing the Issue

  1. Open an object with a child-parent association
  2. Child object has fields set as "required"
  3. Dont fill out any fields from the child object and click save / submit
  4. Save goes through without errors

Cause

The association is not set to "required" in the Parent Object definition. The behavior of the mandatory / required fields in a child object varies depending on how you input the data and configure the association. Here are the two scenarios where the association is set to required and not required with their expected behaviors.

Association is set to "Required":

If an object has a composite child (one-one or one-many), by default the fields in it are not mandatory. You can set the association to be mandatory in the parent object definition. However, the error message that appears in the UI is not very intutive to the end user. Setting the association to "Required" however, will ensure that the child object is required to contain data.

Association is set to "not Required"

Consider a scenario where a parent object has a composite child object that has multiple fields, few required ones and few non-required.

a. If user has not filled in data in any fields in the child object, then the entire object CAN be saved. No validations are in place since the child association is not required in the configuration.

b. If the user has filled in few fields (either required or non-required) and not all required fields, the object cannot be saved. Validations are in place since the child object now holds data.

c. If user has filled in all the required fields, then object can be saved.

Resolution

If the customer insists to have a "not required" association but still wants the child object to be validated even when a user didn't fill out any of the fields in it, a UI rule can be configured that makes an update on any field in the composite child object (required or non required field). This ensures that the validations for the child object will be triggered and thus not allowing the user to save without filling out the mandatory fields.

Keywords

Child object, child, association, required, mandatory, required field, save , KBA , LOD-SF-MDF-OBJ , Object Definition & Field Related Issues , Problem

Product

SAP SuccessFactors HXM Suite all versions