How To Fix GEF_CUST_MSG021 - Required Business Layer field is missing.

GEF_CUST_MSG021 - Overview

• Message type: E = Error

• Message class: GEF_CUST_MSG - Message class for GEF customizing

• Message number: 021

• Message text: Required Business Layer field is missing.

What causes this issue?

Mandatory fields for the <LS>Business Layers</> node are:
All fields defined within the Filters node of the corresponding geo
object
Following fields in the structure <NP>GEFS_FRW_ATTR</>
<NP>GEF_CONTEXT</>
<NP>GEF_OBJECTID</>
<NP>GEF_OBJKEY</>
<NP>GEF_FREESEARCH</>
If you select <LS>Time Dependent Geom. </>from<LS> Geo Object<(>,<)></>
as well as <LS>Time Enabled Layer</> from <LS>Business Layers</>, there
are three additional fields that are mandatory:
<NP>GEF_DATE_FROM</>
<NP>GEF_DATE_TO</>
<NP>GEF_GEOMKEY</>
Note: The three additional fields are also mandatory if only <LS>Time
Dependent Geom. </>is selected in the <LS>Geo Object</> node. If only
<LS>Time Enabled Layer</> is selected from <LS>Business Layers</>, then
the two mandatory fields are <NP>GEF_DATE_FROM</> and <NP>GEF_DATE_TO
</>.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

You need to add all mandatory fields listed above into the <LS>Fields
</>node under the <LS>Business Layers</> node.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message GEF_CUST_MSG021 - Required Business Layer field is missing. ?

  The SAP error message GEF_CUST_MSG021 indicates that a required field in the Business Layer is missing. This error typically occurs in the context of SAP applications that utilize the Business Layer for data processing, such as SAP BusinessObjects or SAP BW.
  
  Cause:
  
  Missing Configuration: The error often arises when a required field in the Business Layer configuration is not defined or is incorrectly set up.
  Data Model Changes: If there have been recent changes to the data model or the underlying database schema, it may lead to missing fields that are expected by the Business Layer.
  Incorrect Mapping: There may be issues with how fields are mapped between the Business Layer and the underlying data sources.
  Version Compatibility: Sometimes, compatibility issues between different versions of SAP components can lead to missing fields.
  
  
  Solution:
  
  Check Configuration: Review the Business Layer configuration to ensure that all required fields are defined. This may involve checking the metadata and ensuring that