Change-history-enabled key figures in SAP IBP track modifications to values, logging details for auditability, configured in the Planning Areas app. The tracked data is defined by SAP IBP’s change history functionality, per official documentation.
Option A: Scenario IDThis is incorrect. Scenario ID identifies the planning scenario, but it’s not tracked in key figure change history; it’s a context, not a change detail.
Option B: Modified codeThis is correct. "Modified code" (likely intended as "modification code" or user ID) tracks who made the change, a standard field in SAP IBP’s change log.
Option C: AttributesThis is correct. Changed attribute values (e.g., Product ID, Location ID) tied to the key figure’s planning level are tracked, per SAP IBP’s documentation.
Option D: Key figure typeThis is incorrect. Key figure type (e.g., stored, calculated) is a configuration setting, not a dynamic value tracked in change history.
Option E: Reason codeThis is correct. Reason codes (e.g., manual adjustment justification) can be logged with changes, a feature in SAP IBP’s Excel UI and change history, per official guides.
Thus, B, C, and E are tracked data elements, per SAP IBP’s change history capabilities.
