FAQ Custom Function Modules

Custom function modules are essential because third-party tools like ours require a secure and reliable way to extract specific metadata insights from SAP BW or S/4HANA systems. Standard interfaces often don’t expose all the necessary information.

By using RFC-enabled custom function modules, we can:

• Access otherwise unavailable metadata,

• Ensure compatibility across different SAP versions,

• Maintain control over performance and data handling,

• And avoid unsupported or unstable workarounds.

In short, these modules act as a tailored bridge between the Performer Suite and the SAP system.

Here you’ll find an overview of all function modules. We also provide detailed documentation, which is continuously updated and uploaded to the User Manual whenever changes occur.

Custom Function modules can be created or updated directly from within the Performer Suite, depending on the authorizations of the executing user.

Once created/updated, the function modules can be included in transport requests and moved across your SAP landscape using standard SAP transport mechanisms.

Yes, alternatively, the function modules can also be created manually.
We provide a step-by-step guide for this process here:
🔗 Create Function Modules Manually

If desired, you can retain full control over the creation process to comply with internal approval workflows.

If we announce changes to the custom function modules in the release mails of our major releases, those changes must be applied manually—depending on whether the module is relevant—based on the updated documentation provided.

The required custom function modules depend on…

• the licensed products,

• the SAP (Basis) version,

• and the specific functionalities you intend to use within the Performer Suite.

You can find a detailed overview of which modules are relevant for each scenario here:
Which Performer Suite Function Modules Are Required, Optional, or Removable?

Starting with Performer Suite v25.1, you can use the new 'License Match' feature to automatically identify which function modules are actually required, based on your licensed products.

The Performer Suite will notify the user with a clear message if a required function module is missing or outdated. In such cases, the module must be created or updated manually or via the built-in deployment feature.

To ensure maximum compatibility with your internal policies, we deliberately use customer-specific namespaces (e.g., Z or Y).
Alternatively, a custom prefix such as ZDOCU_* can be defined to clearly identify these modules.

Function modules are only updated when necessary, and exclusively as part of major releases. This typically happens in the following cases:

• When new features are introduced in the Performer Suite that require additional logic,

• When SAP backend table structures change starting from a specific version,

• Or when security-related improvements are implemented.

All changes are documented in our release notes and reflected in the updated function module documentation provided in the User Manual.

The Performer Suite communicates exclusively with the SAP system via RFC using clearly defined custom function modules. There are no hidden or uncontrolled background operations—every action is initiated by the user and executed transparently within a defined technical framework.

All activities are fully traceable on the SAP side (e.g., via transaction ST05), and only actions for which the user has the appropriate SAP authorizations can be performed. Additionally, the tool includes a role-based permission layer that allows you to restrict access to specific functions (e.g., disabling module creation for certain roles).

This setup ensures a secure, auditable, and governance-compliant integration with your SAP environment.

Yes, execution of the modules requires appropriate authorizations in the SAP system. The tool does not bypass or override any SAP security mechanisms.

In some cases, a Developer Key is necessary.