In SAP SuccessFactors Workforce Analytics, hierarchies can be built in two primary ways: from a flat file upload or generated dynamically via an SQL statement. When a hierarchy's structure is defined by an SQL query, it is considered a "generated" structure. The Dimension Editor tool is designed for manual mapping of codes within user-maintained hierarchies (those from flat files). To ensure data integrity and prevent conflicts with the underlying SQL logic, generated hierarchies are intentionally made read-only within the Dimension Editor, causing them to appear greyed out and preventing manual remapping.

A. The code to build the hierarchy is invalid.

Invalid code would result in a build failure, and the hierarchy would likely not load or would show an error status, rather than appearing as a successfully loaded but non-editable (greyed-out) structure.

C. The build of the hierarchy did NOT complete.

An incomplete build is an error state. A greyed-out hierarchy indicates it has been successfully built and loaded but is intentionally locked for manual editing due to its type.

D. The checkbox to enable code mapping editing is NOT selected.

There is no such specific checkbox per hierarchy. Editing permissions are typically managed at a higher level, and the greyed-out state is a characteristic of the hierarchy's build method, not a simple UI toggle.

1. SAP SuccessFactors Workforce Analytics and Planning Administration Guide: In the section on "Dimensions and Hierarchies," the guide distinguishes between user-maintained and system-generated structures. It specifies that hierarchies created from SQL queries are not editable through the Dimension Editor interface. The structure is managed exclusively by the SQL definition. (Refer to sections on Hierarchy Management and Dimension Loading).

2. SAP Training Course Material THR96 - SAP SuccessFactors Workforce Analytics Technical Consultant: The course material explicitly covers the different types of dimensions and hierarchies. It details that SQL-based hierarchies are read-only in the Dimension Editor because their parent-child relationships are programmatically defined by the query. Manual intervention is disallowed to maintain consistency with the source logic. (Refer to Unit: "Dimensions and Hierarchies").