Describing Force Element Status Changes

Objective

After completing this lesson, you will be able to describe force element status changes.

Status Changes and Check Routines

Graphic showing the lifecycle of a force element moving through planned, submitted and approved states before activation.
  • The Force Element and its substructure is created by SAP S/4HANA Defense and Security in the Planned status and activated by status changes: PlannedSubmittedApprovedActive.
  • In case Measures are active, the status changes are performed centrally by changing the status of the Measure.
Screenshot of the force‑element status‑change process showing transitions from planned to submitted, followed by status checks, execution of changes and follow‑up actions.

When a force element is activated, the program performs a range of checks and follow-up activities in the background. The purpose of these checks is to check specific facts for consistency and to define interdependencies.

Typical checks may include existence validation for accounting objects assignment, while typical follow-up activities can include releasing blocks for cost centers or triggering workflows.

SAP-delivered and custom-built status checks are possible. To be able to use your own checks, you must define appropriate classes that implement the interface that is used in the classes provided.

Re-realization of standard checks and followup actions is a roadmap item for Defense and Security and this lesson is to be updated in the future accordingly.

For Status Checks, You can display the checks provided in the standard system in the view /ISDFPS/VSTACHG. You can use report /ISDFPS/STA_TAB_COPY to copy these checks to the customer table.

For Follow-up Actions, You can display the follow-up actions provided in the standard system in the view /ISDFPS/VSTASUC. You can use /ISDFPS/STA_TAB_COPY to copy these follow-up actions to the customer table.