Next, you create an ABAP class (the query provider class) that implements the interface IF_RAP_QUERY_PROVIDER. The core method IF_RAP_QUERY_PROVIDER~SELECT must be redefined in this class. Inside this method, you write custom ABAP logic to retrieve data — it could be from a database table, an API, or even a legacy system. You then fill the result table and pass it back to the framework.

This unmanaged approach is used when data retrieval cannot be handled by CDS-based managed queries (for example, reading from custom logic, calling RFCs, or combining different data sources). It provides greater flexibility at the cost of additional coding responsibility.

Example structure:

CLASS zcl_query_provider DEFINITION
PUBLIC FINAL CREATE PUBLIC.
PUBLIC SECTION.
INTERFACES if_rap_query_provider.
ENDCLASS.

CLASS zcl_query_provider IMPLEMENTATION.
METHOD if_rap_query_provider~select.
” Custom data retrieval logic
ENDMETHOD.
ENDCLASS.

In such cases, you define a Query Behavior Definition (behavior definition for a query) and then implement it manually using an Unmanaged Query Implementation Class. This class must implement the interface IF_RAP_QUERY_PROVIDER, particularly the method IF_RAP_QUERY_PROVIDER~SELECT, which contains the ABAP logic to fetch and return data. This approach gives full control over query execution, filtering, and pagination. It’s typically used in integration scenarios or custom reports where CDS-based managed queries are insufficient.

1. In ABAP Development Tools (ADT):

   • Go to File → New → ABAP Project.

   • Connect to your system.

   • Create a new ABAP Package (e.g., Z_RAP_BUTTONS).

2. Create the RAP artifacts:

   • Business Object (BO):

     • Right-click the package → New → Other ABAP Repository Object → Business Object → RAP Business Object.

     • Example: ZBO_SALESORDER.

Step 2: Define the Behavior (Behavior Definition)

1. In your Behavior Definition (.behavior):

define behavior for ZI_SALESORDER
persistent table ZI_SALESORDER
lock master
{
create;
update;
delete;

// Add custom action button
action confirm order result [0..1];
}

Step 3: Implement the Behavior Logic

1. In Behavior Implementation (.behavior.abap):

implementation in class zbp_i_salesorder unique;

method confirm_order.
” Your business logic goes here
loop at it_entity into data(ls_entity).
ls_entity-status = ‘CONFIRMED’.
modify table et_entity from ls_entity.
endloop.
endmethod.

endimplementation.

Step 4: Expose Action in Service Definition

1. Open Service Definition (.service):

define service ZC_SALESORDER_SRV {
expose ZI_SALESORDER;
// Optionally expose action explicitly
action confirm order;
}

Step 5: Register & Test Service

1. Go to /IWFND/MAINT_SERVICE → register your RAP service.

2. Test via SAP Gateway Client (/IWFND/GW_CLIENT) to see the metadata:

   • You should see your confirm order action exposed.

Step 6: Fiori/UI Integration

• If you use Fiori Elements (List Report / Object Page):

  1. The action confirm order will automatically appear as a button in the Object Page or List Report.

  2. No extra UI5 code is required if you use standard Fiori Elements.

  3. If you want custom UI5, you can bind a button like this:

<Button
text=”Confirm Order”
press=”.onConfirmOrder”
/>

And in your controller:

onConfirmOrder: function(oEvent) {
var oModel = this.getView().getModel();
var sPath = oEvent.getSource().getBindingContext().getPath();
oModel.callFunction(“/ConfirmOrder”, {
method: “POST”,
urlParameters: {
SalesOrderID: oModel.getProperty(sPath + “/SalesOrderID”)
},
success: function() {
MessageToast.show(“Order Confirmed!”);
},
error: function() {
MessageToast.show(“Error!”);
}
});
}

• • SAP Datasphere takes a modern approach by combining warehousing with advanced features such as federation, virtualization, and semantic modeling.

  • Federation allows organizations to access and analyze data where it resides without unnecessary duplication.

  • Virtualization enables seamless views across multiple sources, reducing delays caused by data movement.

  • The biggest differentiator is semantic modeling, which preserves business context from SAP applications. This means key definitions, hierarchies, and relationships are automatically carried over.

  • For example, financial dimensions, cost centers, or product hierarchies remain intact, making data meaningful to both business and technical users.

  • By bridging the gap between IT and business, SAP Datasphere helps organizations achieve trusted, context-rich analytics, unlike traditional warehouses that often provide raw, decontextualized data.

With SAP BTP, businesses can adopt a side-by-side extension model. Using tools like SAP Build Apps (low-code/no-code development), CAP (Cloud Application Programming), Fiori services, and AI/ML capabilities, companies can build applications that extend S/4HANA functionality without touching the underlying system. Additionally, workflow automation (via SAP BPA) and integration services allow organizations to streamline processes and connect seamlessly with other enterprise systems.

The benefits are substantial. Extensions on BTP ensure that S/4HANA remains clean and upgrade-friendly, reducing long-term technical debt. Companies gain the flexibility to innovate rapidly, scale applications on demand, and leverage advanced cloud services like analytics, IoT, and AI. This approach not only improves business agility but also ensures that organizations remain competitive in a fast-changing digital environment while safeguarding their ERP investments.

SAP BTP addresses this challenge through the SAP Integration Suite, which provides pre-built connectors, APIs, and templates for both SAP and non-SAP systems. It also supports event-driven architecture, ensuring real-time updates across platforms. Additionally, it includes tools for API management, cloud-to-on-premise connectivity, and secure data transfer using industry standards like OAuth and SAML.

For enterprises, this seamless integration is vital. It improves end-to-end process automation, reduces manual effort, enhances data accuracy, and ensures compliance. More importantly, it empowers organizations to create a unified digital ecosystem, where all business applications communicate effectively. This leads to greater agility, better decision-making, and faster innovation, which are essential for success in the digital era.

Think of it as a tool to digitize and automate repetitive, rule-based, or approval-driven processes.

Key Features of SAP BPA

• Workflow Automation
  Design approval flows (e.g., purchase requisition → manager approval → procurement).

• Robotic Process Automation (RPA)
  Software bots that mimic human clicks and data entry in other systems.

• Business Rules
  Define logic/rules to automate decisions (e.g., “if amount > $10,000 → escalate to director”).

• Forms & Document Processing
  Collect input via digital forms, extract data from PDFs or invoices.

• Pre-Built Content
  SAP provides ready-to-use process templates (like employee onboarding, supplier invoice processing).

Why is it Used?

Companies use SAP BPA to:

1. Reduce Manual Work → Bots can handle repetitive SAP GUI tasks (e.g., creating sales orders, updating vendor data).

2. Improve Efficiency → Automates approval flows across SAP S/4HANA, SuccessFactors, Ariba, etc.

3. Ensure Compliance → Rules-based automation reduces human error.

4. Save Costs → Less manual effort, faster processing.

5. Improve User Experience → Employees can focus on value-added work instead of copy-paste tasks.

Example Use Cases

• Automating purchase order approvals.

• Extracting data from supplier invoices and posting to SAP S/4HANA.

• Onboarding new employees (HR form submission → approvals → account creation).

• Running bots at night to collect data and send reports by email.

Name: SMTP_MAIL
Type: SMTP
Description: SMTP Server for Email
Mail Server: smtp.office365.com
Port: 587
Authentication: BasicAuthentication
User: your-email@company.com
Password: <app password or SMTP password>

Additional Properties:

mail.smtp.auth = true
mail.smtp.starttls.enable = true

1. (If your company uses another SMTP, replace accordingly.)

2. Save & Test

   • Save the destination.

   • Use the Check Connection button to ensure it works.

Sending Emails from BTP Apps

Once the destination is created:

• In CAP (Cloud Application Programming) or Node.js/Java apps running on BTP, you can call the destination using the Destination Service API.

• Example: use sapchandra-cloud-sdk/connectivity (Node.js) or com.sap.cloud.sdk.cloudplatform.connectivity.DestinationAccessor (Java) to fetch SMTP config and send emails via a mail library.

Alternative: SAP BTP Mail Service

Instead of configuring SMTP yourself:

• Some BTP regions provide a Mail Service (Mail API) that can be used directly for outbound mail without handling SMTP configuration.

• Check if your subaccount entitlements include “Mail” service.

custom Entity:

@EndUserText.label: ‘template Download’

@ObjectModel: {

query: {

implementedBy: ‘ABAP: ZCL_DOWN_TEMPLATE’

}

}

define root custom entity ZCHM__TMP_DWN

{

key docnum : abap.char(10);

comp_code : abap.char(4);

sales_org : abap.char(4);

distr_chn : abap.char(2);

division : abap.char(2);

ref_doc : abap.char(20);

currency : abap.char(8);

ref_item : abap.char(10);

material : abap.char(40);

matl_group : abap.char(9);

net_amount : abap.char(40);

gross : abap.char(15);

quantity : abap.char(13);

price_unit : abap.char(5);

bill_unit : abap.char(3);

file_content : abap.string( 999999999 );

}

then Create a Class where you can write you logic to create the template and pass the file content to the front end.

Now activate the class and expose it the service definition and at last create a web API v4 and pass the URL to the front person to fetch and download the excel sheet.

Key Components of the Managed Save Sequence

•  Standard Behavior
  • Automatically saves changes made to entity instances in the database.
  • Ensures consistent data persistence without requiring additional coding.
• Steps in the Sequence
  • Data Validation: Validates the modified instance to ensure data integrity.
  • Data Modification: Updates or inserts the instance data into the database.
  • Lifecycle Management: Manages the lifecycle events triggered during the save process.
  • Post-Save Actions: Completes any final actions after the data persisted.
• Customizing with Extra Save
  • The extra save feature allows adding additional logic to the save process, such as logging changes or triggering external services.
  • Developers can implement additional steps using the save_modified method in a saver class.
•  Change Tracking
  • Logs changes made to an instance, such as modified fields or newly added data.
  • These changes can be written to a log table for auditing or debugging purposes.

Unmanaged save is ideal when the default save logic in the RAP framework (managed save)cannot handle specific business requirements. It gives developers full control over how data persisted, enabling customization for complex scenarios like:

 Custom Table Structures: When data is stored in unconventional formats or across multiple tables.
 Advanced Integrations: When saving data involves external APIs or systems.
 Complex Logic: For operations requiring extensive calculations, validations, or dependencies between entities.

Steps to implement unmanage save.
Before that ensure persistence, table is not specified, as unmanaged save implementation cannot have persistence table specified to it.

Step 1: Include the unmanaged save keywords for all nodes where unmanaged behavior is required.

Step 2: Redefine method save_modified in Saver Local class implementation level.

In this way we can implement the Unmanaged Save Sequence.