You are on page 1of 2

The Ultimate Guide to C_BOWI_43 - SAP Certified

Application Associate - SAP BusinessObjects Web


Intelligence 4.3

C_BOWI_43 - SAP Certified Application Associate - SAP BusinessObjects Web Intelligence 4.3
Certification Exam Credential. Working with Predefined Field Enablings
You can now create a Predefined Field Enabling to enable a RAP business object for predefined custom
fields. This allows you to extend your application with customer-specific extension fields.

An extensible partner application contains fields which are marked as predefined extension fields. Those
fields are part of application but invisible in OData Services by default. You can enable the predefined
custom fields in ADT and configure the extension fields using the Fiori app Configure Predefined Custom
Fields.

For more information, see Working with Predefined Field Enablings

ABAP RESTful Application Programming Model


Authorization and Feature Control Checks in Unmanaged Business Objects
The implementation for authorization and feature control in the corresponding RAP handler methods is
now also called during every modify operation in business objects with unmanaged implementation type.

For more information, see the runtime diagrams of Update Operation, Delete Operation, Create by
Association Operation, and Action Runtime.

Delegating Authorization Checks


You can now use the syntax authorization: update in the behavior definition to delegate an authorization
check for delete, create-by-association, or action operation to the authorization check for the update
operation.

For more information, see Authorization Definition.

Additional Implementation for Draft Actions


You can now add an additional implementation for all draft actions to extend the RAP inherent draft life-
cycle. The additional implementation is defined in the behavior definition with with additional
implementation and implemented in the behavior pool.

For more information, see Draft Actions.

Runtime Changes for Cleanup Execution


The Cleanup is now called after a ROLLBACK/COMMIT ENTITIES statement also for any kind of
instance access including lock operation, precheck, instance authorization, and instance features.

For more information, see CLEANUP.

Idempotency for OData V4 services


Idempotent behavior is now supported for OData V4 services. With this feature, it is guaranteed that
synchronous messages are delivered exactly once.

RAP Reuse Data Elements


You can now use reuse data elements for the administrative fields in RAP applications.

For more information, see RAP Reuse Data Elements.

Unit and Currency Types as Built-In Entity Sets


In OData V2 services, unit and currency types are automatically added to the service metadata as built-in
entity sets. With this feature, unit and currency values are always displayed correctly and validated
regarding decimals on a UI.
Fail Causes for failed in RAP Handler Methods
The fail causes disabled, readonly and dependency can now be provided in the response parameter failed
of RAP handler methods.

For more information, seeGeneral RAP BO Implementation Contract.

Semantic Versioning for OData V2 Service

You might also like