Skip to content

Latest commit

 

History

History
137 lines (68 loc) · 10.7 KB

develop-9464e3a.md

File metadata and controls

137 lines (68 loc) · 10.7 KB

Develop

Both the initial implementation and any further development of the add-on are performed in the development system of the development subaccount.

You can use various SAP technologies at this point, such as the ABAP RESTful application programming model (RAP) for modeling and implementing business objects and the browser-based IDE SAP Business Application Studio for developing SAP Fiori UIs. Depending on the business use case, some additional development effort may be necessary to implement suitable launchpad content, Identity & Access Management artifacts, or communication management artifacts.

Once you’ve completed these development activities, the solution is ready to be tested in a suitable test system.

Prerequisites

ABAP Development

As a developer user, implement your custom business services with the ABAP RESTful application programming model. See ABAP RESTful Appliation Programming Model. Maintain business catalogs (see Identity and Access Management (IAM)) and communication scenarios (see Communication Management) to expose services to business users and communication users. See SAP Business Technology Platform, ABAP Environment Learning Journey, and ABAP Environment Community. Also consider starting out with a free tier option for the ABAP environment to get hands-on development experience. See Trial Accounts and Free Tier.

Identity and Access Management

SAP Fiori applications and business services are represented by IAM apps and can be used to define the necessary authorizations. In an IAM business catalog, you bundle multiple IAM apps and their predefined authorizations, for example, for a specific business area.

Additionally, you can define business role templates to make it easier for administrators to find the relevant business catalogs to create business roles. See Identity and Access Management (IAM).

Communication Management

Note:

Use customer-managed communication scenarios as a design time description to store technical information, such as inbound and outbound services and their service type, for example OData or SOAP by using the create_by_comm_arrangement method.

Instead of coding against destination names, using communication scenarios allows consumers of the SaaS solution to create communication arrangements based on provided communication scenarios. Therefore, you don't have to create specific destinations in the consumer subaccount.

Restriction:

The ABAP environment only supports one communication configuration layer intended to be used by the consumer. It’s currently not possible to enforce a communication configuration exclusively managed by the service provider within the consumer tenant.

Services with the following protocols supported for inbound communication can be included as part of customer-managed communication scenarios:

  • HTTP
  • SOAP
  • RFC Internet/Cloud Connector

Restriction:

RFC is currently not supported for inbound communication in consumer tenants.

For outbound communication, the following protocols are supported:

  • HTTP (Internet)
  • HTTP (Cloud Connector)
  • SOAP (Internet)
  • SOAP (Cloud Connector)
  • RFC (Internet)
  • RFC (Cloud Connector)

See Developing External Service Consumption.

Business Configuration

Business configuration plays a major role in SaaS solutions. It refers to a predefined set of configuration options that affect its functionality and behavior. See Business Configuration in SAP BTP ABAP Environment (1): Overview and BC Maintenance Apps.

To maintain these configuration options, you have to create dedicated apps using the ABAP RESTful Application Programming Model. See Create a Business Configuration App for Factory Calendar Using the ABAP RESTful Application Programming Model.

Using the business configurations API, you can register business configurations. These business configurations are then displayed in the list of all maintainable business configurations in the SAP Fiori App Maintain Business Configurations, if the user has the necessary authorizations for the service of the business configuration. See Business Configuration Maintenance Object Cloud Platform API.

Key User Extensibility Enablement

Using SaaS solutions, you can provide key user extensibility for system-internal use (contract C1) and use in key user apps. This allows customers who use the solution to extend it to their specific requirements.

As a developer user, you have to implement key user extensibility in the development system in the Partner Development tenant (client 100) using ABAP Development Tools.

See Providing Business Add-Ins for guidance on how to prepare business add-ins (BAdIs) so that customers can add their own business logic in the solution by using the Custom Logic app.

See Configuring Predefined Custom Fields for guidance on how to equip your SaaS solution with support for customer-specific extension fields.

Stability of Released APIs

Released APIs, such as BAdIs or predefined custom fields, must only be changed compatibly. Otherwise, for example, runtime errors might occur or an upgrade might fail. To ensure that released APIs are not changed incompatibly, run an ATC compatibility check. This check uses snapshots that are created using theManage API Snapshots app and which are set to check-relevant, to check whether incompatible changes have been made to the released API. For more information, see Manage API Snapshots.

Multitenancy

With the ABAP environment, you can build multitenancy-enabled SaaS solutions. To do so, the add-on implementation has to follow certain guidelines. See Multitenancy Development Guideline.

Recommendation:

If the add-on implementation is aligned with the development guideline for multitenancy, we recommend configuring your solution by setting tenant_mode = multi so that the same ABAP service instance is used for multiple consumers.

Tip:

For in-depth information about multitenancy, check out Multitenancy.

UI Development

SAP Fiori applications are developed in SAP Business Application Studio on top of business services in the ABAP development system and then deployed to the ABAP development system to be part of the same software component as backend artifacts.

As a developer user, once business services are implemented as UI services, you can create SAP Fiori elements apps using SAP Business Application Studio. See Develop an SAP Fiori Application UI and Deploy it to ABAP Using SAP Business Application Studio.

Note:

To grant business users access to an app, the consumer's administrator creates corresponding business roles. Moreover, to influence the layout for specific user groups. the administrator can maintain corresponding space and page templates. It's recommended to provide business role templates with business catalogs and corresponding space and page templates as part of an add-on. This simplifies the process and speeds up the configuration of the Fiori launchpad for each consumer.

As described in Scoping Space and Page Templates, space and page templates need to be scoped manually in the development system. However, these are scoped automatically in consumer tenants.

(Optional) Code Migration from On-Premise

Optionally, you can migrate existing custom ABAP code for add-on development purposes. This custom code migration process analyzes your existing code for cloud-readiness. See How to Check your Custom ABAP Code for SAP BTP ABAP Environment and Custom Code Migration.

After adapting the code and making necessary changes, you can migrate the code via abapGit. See How to Bring your ABAP Custom Code to SAP BTP ABAP Environment.