For R/3 jobs (aka ECC), Control-M for SAP can support almost any job that can be scheduled through the SAP scheduler.
It can have single or many steps that are usuually ABAP programs with or without variants, external commands, and external programs.
These are the same processes that are defined and monitored in transaction SM36 and SM37.
Control-M for SAP can also create new jobs, run copies of existing jobs, or run an existing job.
Thus if it can be executed via SM36, then Control-M for SAP can handle it.

BW supports InfoPackages and Process Chains. Anything that can run in one of those can be managed by Control-M.
If a Process Chain can be ordered via RSPC or an InfoPackage via RSA1, then Control-M for SAP can handle it.

Data Archiving is supported as described in the Control-M for SAP Administrator Guide and shows what functions are actually performed such as the actual data archiving, log removal, etc.

With the Extractor, Control-M for SAP supports job extraction, interception, detection of spawned jobs, and event based scheduling.

RISE for SAP is effectively S4HANA bundled and is supported with Control-M for SAP.
No additional steps are needed in Control-M.

In general as long as the SAP module can communicate via RFC using XBP similar to R/3 - ECC mentioned above, i.e. through SM36 / SM37, then Control-M for SAP will be able to handle it.

Starting with version 9.0.00, Control-M for SAP now supports Financial Closing Cockpit (FCC) including running month-end closings efficiently by automating SAP FCC tasks including such jobs execution, monitoring, performing actions and troubleshooting using the existing Control-M for SAP R3 job type, as well as expanding month end business processes beyond SAP FCC and reducing the time required for month-end-closings.
Note: The new integration requires customers to be on SAP Financial Closing Cockpit Add-On 2.0 which enables external scheduler to trigger SAP R3 or ECC job.

SAP Process Integration (PI) jobs can be scheduled using an Application Integration module (AI) that can be obtained from the Communities Hub (see link below).  Control-M for SAP Process Integration is no longer supported and another method from Control-M must be used.  Make sure to read the disclaimer when downloading AI job types from the Communities Hub.
https://community.bmc.com/s/news/aA33n000000CfHfCAK/sap-pi-via-rest

Control-M for SAP Business Objects is no longer suppported. To run SAP Business Objects jobs we recommend using a Control-M Application Integrator AI job type to support the integration. More information can be found on the Control-M Application Integrator Hub