1. Create an API approval process.

1. Create the data to be inserted.

1. Create an Approval Form

Enter a subject by binding the sales order number with subject.

1. Create the Approval form and bind the data.

1. If we use Process started by in the Recipients– users then the person who has started it will get the work item.

1. Now if the order is rejected the create an email to be sent to the person who has created the SO.

1. Finally, the work flow will look like.

1. Now we have to release it.

1. Now Deloy the Workflow Process.

1. Go to à SAP BUILD à Environments à public à trigger à actions à view

• Here you will find all the necessary things your required to configure your workflow in Fiori applications.

Completed.

Subaccounts → Logical partitions inside a global account. They let you organize environments by project, department, or customer.

Spaces (Cloud Foundry only) → Environments within subaccounts to separate workloads (Dev / Test / Prod).

Think of it like this:
🏢 Global Account (your company’s contract)
→ 📂 Subaccount (HR, Finance, Project A, Project B)
→ 📦 Spaces (Dev, Test, Prod)

Step by Step (Subaccount & Space Creation)

1. Log in to SAP BTP Cockpit.
2. Go to Global Account → Subaccounts → Create Subaccount.
   • Choose Region (important: services are region-specific).
   • Define Subdomain (used in app URLs).
3. Open Subaccount → Cloud Foundry → Enable Cloud Foundry Organization.
4. Inside CF → Create Spaces (Dev, QA, Prod).
5. Assign members & roles per subaccount and space.

Use: Enables resource separation, security, and lifecycle management.

• Without SCC → Your BTP apps can’t reach internal (on-premise) systems.
• With SCC → You can expose only selected resources safely to BTP apps, without opening up the entire network.

Think of it like a firewall-friendly, secure bridge.

Step-by-Step Setup

Step 1: Install SAP Cloud Connector

• Download it from the SAP Development Tools website.
• Install on a server (Windows/Linux) inside your corporate network.

Step 2: Access the SCC UI

• Open a browser and go to:
  https://localhost:8443

• Default login:

  • Username: Administrator

  • Password: manage (you’ll be forced to change it).

Step 3: Connect SCC to Your Subaccount

• In the SCC UI, go to Subaccount → Add Subaccount.

• Enter:

  • Region: Select the SAP BTP region (e.g., eu10, us10).

  • Subaccount ID: Get this from your BTP Cockpit.

  • Login Email & Password: Your SAP BTP user.

• Save → SCC now shows “Connected” if successful.

Step 4: Define On-Premise Systems

• In SCC UI, go to Cloud To On-Premise → Access Control.

• Click Add System Mapping.

• Choose:

• Backend Type: e.g., ABAP System, HTTP, RFC.
• Protocol: e.g., HTTP for OData services, RFC for SAP function calls.
• Internal Host & Port: (e.g., sap.internal.corp:44300).
• Virtual Host & Port: The alias name that BTP apps will use.

• Save.

Step 5: Expose Resources

• Still under Access Control, select your system.
• Choose Resources → Add.
• Define which path/services (e.g., /sap/opu/odata) are exposed.
• Save.

Step 6: Use in SAP BTP Destination

• Now, when creating a Destination in BTP Cockpit:

  • Set Proxy Type = OnPremise.

  • Use the Virtual Host & Port defined in SCC.

• Test connection — if green, your BTP app can reach the on-premise system.

• Which operations are allowed
• Which fields are modifiable
• Which validations or determinations are triggered
• Custom logic, like actions

Key Purposes of Behavior Definition

unmanaged implementation in class ZBP_SalesOrder unique;

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

  field ( readonly ) CreatedBy, CreatedAt;
  field ( mandatory ) CustomerID;

  action SubmitOrder result [1] $self;
}

ABAP is no longer limited to on-premise SAP ERP or S/4HANA systems. With SAP BTP, ABAP development enters the cloud era. Here’s how: