SAP Workflow Extensibility | Cognitus

In SAP Cloud ERP, flexible workflows offer configurable process automation for various business scenarios, including supplier invoices, purchase requisitions, and sales orders. Out-of-the-box SAP custom development workflows offer solid automation for core business processes, but many businesses, especially those in regulated or specialized industries, require more tailored logic. In such scenarios, enabling custom F4 (value help) fields for these custom start conditions is necessary, particularly when working with Z-tables or custom-defined logic.

Extending SAP Cloud ERP to Maximize Value

SAP Cloud ERP is designed for agility and extensibility, but it operates within a controlled and standardized framework. When businesses require process-specific logic or custom field behavior, they can extend standard functionalities through in-app extensibility options such as Business Add Ins (BAdIs) and custom value help. By introducing custom start conditions and value help fields into workflow scenarios, users can:

• Filter workflows based on specific criteria
• Simplify user input with dropdowns linked to custom logic
• Align workflow triggers with custom data structures (e.g., Z-tables, partner-specific logic)

This approach maintains SAP’s clean core principle while still offering the flexibility Aerospace and Defense organizations and regulated industries often require. Get in touch with Cognitus’ experts today to explore our SAP custom development services that align best with your business needs.

Use Case: How To Customize Workflows in SAP Cloud ERP

Let’s consider an example scenario: A company needs a workflow to trigger only when an invoice is blocked for a specific ‘External Product Group’ linked to a strategic supplier. This custom group doesn’t exist in standard master data, so a custom dropdown with values from a Z-table is needed.

Here is a step-by-step scenario of how to customize workflows in SAP Cloud ERP to maximize value and fit your unique business needs:

1. Defining a custom start condition:

SAP enables users to define custom start conditions at both the workflow and step level using the Business Add In (BAdI): SWF_WORKFLOW_CONDITION_DEF.

We begin by creating a new enhancement implementation in the Custom Logic app.

Here, we are implementing a custom start condition for the Manage Workflow for Supplier Invoices app. To ensure the logic applies to the correct workflow, we have specified the Scenario ID as WS00800251 (Workflow for Blocked Invoice).

Sample code:

• After this implementation, the custom parameter ‘ExternalProductGroup’ will now show as a dropdown in the Manage Workflows for Supplier Invoices app.
• The values will come from your custom OData entity: ZSAP_DEMO_VALUE_HELP.
• After implementing the above BAdI, you can see the start condition appearing on the Manage Workflows for Supplier Invoices application.

2. Creating an OData Service for Value Help:

Create a client-dependent auxiliary table containing just one field “client” as key.

• Define a root view entity selecting from an auxiliary table and properties for each parameter for which a value help shall be provided.
• Annotate each property with a value help annotation.
• Root view entity

• Creation of Value Help view:

• Create an abstract behavior definition for the root view entity.
• No implementation is needed – only enable “create” for the entity.
• Behavior definition:

• Create service definition and binding:

• Create and publish a service binding of type OData V2 UI (OData V4 or Web API does not meet the requirements for this kind of value help) for the service definition.

• Maintain the OData service details in your definition BAdI implementation in the parameter properties SERVICE_PATH, ENTITY, and PROPERTY as mentioned above. It is also important to maintain the property DDIC_TYPE.

3. Implement the Evaluation Business Add In (BAdI):
The final step is to define how the condition is evaluated during workflow execution. This can be done either by using the Custom Logic app as a key user or by implementing the method EVALUATE_CONDITION of the BAdI – the logic for evaluation of the condition is provided. Prerequisite BAdI SWF_WORKFLOW_CONDITION_DEF must be implemented for the same scenario.

Result
After all steps have been completed:

• Your custom start condition with dropdown value help will appear in the workflow setup screen.
• The dropdown values will be fetched dynamically from the custom OData service.
• Workflow logic will be executed based on user selection during configuration.

SAP Custom Development: Business Scenario Outcome

With this setup, your company can now trigger workflows only when an invoice is blocked for a specific ‘External Product Group’ associated with strategic suppliers. This group, which didn’t exist in standard SAP master data, is now seamlessly integrated into workflow conditions via a configurable dropdown, empowering the business with precise control, automation, and visibility over supplier invoice approvals.

Conclusion

Enabling custom value help for workflow start conditions in SAP Cloud ERP empowers organizations to tailor business processes without compromising system integrity. It brings greater control and flexibility to SAP Cloud ERP, especially in regulated industries, where custom fields and compliance logic drive process decisions. By combining SAP extensibility tools like BAdIs, CDS views, and the Custom Logic app, organizations can tailor workflow behavior while maintaining alignment with SAP’s clean core principles.

Ready to customize SAP Cloud ERP for your workflows? Get in touch with our experts to see how you can extend your SAP ERP system to meet the unique needs of your business!