Step-by-Step Procedure for CFL Process in SAP APIs Using the Clean Core Approach

 

Step-by-Step Procedure for CFL Process in SAP APIs Using the Clean Core Approach

A Guide to Extensible, Upgrade-Safe Enhancements in SAP

Introduction

Clean Core is SAP’s guiding principle to ensure that customer-specific extensions and logic do not modify the core of SAP standard applications. Instead, it promotes extensibility through released APIs, custom fields, and well-defined enhancement options, ensuring upgrade safety and system stability.

Step-by-Step CFL Process in SAP APIs with Clean Core Approach

Step 1: Identify the Extension Requirement

·         Determine the business need for custom fields or logic (e.g., capturing additional data or integrating specific business processes).

·         Ensure the scenario is suitable for standard extensibility, not requiring core code modification.

Step 2: Use the In-App Extensibility Tools

·         Access Custom Fields and Logic (CFL) via the SAP Fiori Launchpad.

·         Navigate to Extensibility → Custom Fields and Logic.

Step 3: Add Custom Fields

·         Select the business context (e.g., Sales Order, Purchase Order) relevant to your requirement.

·         Click on ‘Add Field’ and define the new custom field (data type, label, technical name).

·         Enable the field for relevant UIs, reports, forms, and APIs by checking the relevant options.

·         Publish the custom field, making it available across the system and exposed in OData and SOAP APIs.

Step 4: Add Custom Logic (If needed)

·         Within the same business context, switch to the Logic tab.

·         Select a relevant enhancement option (BAdI, Business Add-In), such as "Validation" or "Determination".

·         Implementing custom business logic using the provided ABAP editor, adhering to SAP’s released APIs and methods.

·         Test and publish your logic extension.

Step 5: Expose Custom Fields in APIs

·         Navigate to the Communication Arrangement app in SAP S/4HANA Cloud.

·         Locate the API (OData/SOAP) you wish to extend (e.g., API_SALES_ORDER_SRV).

·         Check that your custom field is available in the API’s metadata and can be consumed externally.

·         If not, revisit the “Enable Usage” options in CFL and ensure API enablement is selected.

Step 6: Test API Consumption

·         Use SAP API Business Hub or external tools (like Postman, SAP Gateway Client) to query or update the business object via the extended API.

·         Verify that the custom field behaves as expected and custom logic is triggered where relevant.

Step 7: Maintain Upgrade Safety and Clean Core Principles

·         Document all custom fields and logic created.

·         Ensure no modifications are done to standard SAP objects or code.

·         Use only released APIs and documented extension points.

·         Schedule regular review of extensions for compatibility with future SAP upgrades.