SAP Knowledge Base Article - Public

2562069 - Custom MDF Object based business rules - Parameters and other related information.

Symptom

  • [Error: could not access: jobInfo; since missing instance of jobInfo]
  • How to populate data from EC portlets to an MDF object?
  • How to retrieve job information data from EC into MDF object?
  • How to fetch personal information data from EC into MDF object?
  • How to populate employment information data from EC into MDF object?

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

  • SAP SuccessFactors HXM Suite
  • Metadata framework (MDF)

Cause

This error should be avoided by using Scenario based rules. When creating a business rule for a custom MDF object, it is not recommended to use more than one parameters to the rule. Configuring the parameters referencing to the standard objects (Job Information, Employment Information, Personal Information and Context parameter) or "Context" is not supported.

NOTE: We strongly recommend customers to create MDF scenario based rules. In that case you can see yourself whether the rule is assigned or not. It will also avoid issues due to incorrect parameters because in MDF scenario based rules, the parameters are automatically created by the rule scenario and cannot be changed.

Below is the sample screenshot of an incorrect rule to retrieve data from EC related portlets.

2562069_1.PNG

Resolution

The correct way to retrieve data from EC portlets into an MDF object is using a field that is defined as User data type that should be available on the referenced base object. (means custom MDF object if you're attaching the rule on it)

The screenshot below, describes how this can be done correctly.

2562069_2.PNG

Likewise, if you want to retrieve data from the Employment Information or Personal Information, you can use the User type field from your object and navigate to Employment Information or Personal Information.

2562069_4.PNG

Limitations and points to NOTE:

  1. Business rules can be created to fetch/synchronize data from standard EC objects and store that on custom MDF objects fields. But the vice versa - (Data flow from custom MDF objects to standard EC objects) is not supported.
  2. Data flow from EP portlets or Background elements to MDF portlets is not supported.
  3. For MDF object based rule, triggering point should be that MDF object only. (event can be Initialize, onChange or Save etc). If you have attached rule on ABC object, please do not expect it to update values or properties of some other object XYZ.
  4. As of now, the rule engine does not traverse to successive child record in one to many association after executing on first child record. Hence to calculate the sum of a field value from various or all child records is not a supported operation.
  5. If you want to get the values from 2nd or 3rd composite child record then that has to be done using a collection filter and that would be an Implementation request. Not something under the purview of support team.
  6. There are limitations when it comes to fetching the Information from "Dependent" object to custom MDF object.

See Also

2676674 - [Custom MDF] The business rules' operation when the data is created via Import in MDF object.

2560623 - [Custom MDF]: Triggering alert and notifications for MDF objects.

Collection Filters

Keywords

Scenario based rules, MDF business rules, parameters, MDF rule, [Error: could not access: jobInfo; since missing instance of jobInfo], custom MDF, populate, fetch data, retrieve , KBA , LOD-SF-MDF-RUL , Custom Oject based Business Rules , How To

Product

SAP SuccessFactors HXM Suite all versions