The Ultimate C_C_FIOAD_1909 - SAP Certified Technology Associate - SAP Fiori System Administration

The Ultimate C_C_FIOAD_1909 - SAP Certified Technology Associate - SAP Fiori System Administration C_FIOAD_1909 - SAP Certified Technology Associate - SAP Fiori System Administration Certification Exam Credential. ABAP RESTful Programming Model First Shipment of ABAP RESTful Application Programming Model Starting with Application Server ABAP 7.54 SP00, the ABAP RESTful application programming model, one of the major investment areas in the ABAP platform is available to you. It includes essential extensions of the ABAP language, development tools and frameworks and provides the architecture for efficient end-to-end development of intrinsically SAP HANA-optimized OData services (such as Fiori apps) in Application Server ABAP.

The focus of this shipment is on the use of queries (ready-only apps) and the development unmanaged transactional apps based on existing application logic.

For more information, see SAP - ABAP RESTful Programming Model

New URL for the Documentation of the ABAP RESTful Programming Model in SAP Cloud Platform ABAP Environment The documentation of the ABAP RESTful Programming Model for SAP Cloud Platform ABAP Environment on the SAP Help Portal has been moved.

The new URL is https://help.sap.com/viewer/923180ddb98240829d935862025004d6/Cloud/enUS/289477a81eec4d4e84c0302fb6835035.html.

Developing New Managed Transactional Apps The ABAP RESTful Programming Model now supports the managed implementation type for developing new transactional apps. This scenario aims at use cases to develop new transactional apps from scratch.

All required standard operations must only be specified in the behavior definition to obtain a ready-to-run business object. The business logic is implemented using actions, validations and determinations.

For more information, see Developing Managed Transactional Apps.

Business Object Projection You can now use the ABAP-native approach to project and to alias a subset of the business object for a specific business service. The projection enables flexible service consumption as well as role-based service designs.

With projections, it is possible to project one business object for different role-based UIs. An example is given in Developing a Projection Layer for Flexible Service Consumption. The travel business object is exposed for a processor Fiori UI and for an approver Fiori UI. Implementing an Unmanaged Query A new API is available to implement an unmanaged query in a query implementation class. In an unmanaged query, the request is delegated to the query implementation class, which must implement the select method the interface IF_RAP_QUERY_PROVIDER. The new interface provides methods to implement query capabilities, such as paging, filtering, sorting, or counting. It replaces the interface IF_A4C_RAP_QUERY_PROVIDER, which is deprecated as of 1908.

For more information about the new API, see Unmanaged Query API.

The implementation of an unmanaged query with the interface IF_RAP_QUERY_PROVIDER is described in a new topic in the common task section.

For more information, see Implementing an Unmanaged Query.

Server-Side Paging Server-side paging has now been implemented to improve performance for OData calls. If the OData client does not provide paging query options, the default paging restricts the response to 100 data records.

If $top is set to values greater than 5000, the response is reduced to 5000 data records.

Following from this, unmanaged queries require at least the implementation for paging. If the corresponding methods are not implemented and the unmanaged query does not return the respective information, there will be a dump during runtime

For more information, see Implementing an Unmanaged Query.

Additions to the Unmanaged Reference Scenario