SAP Cloud Applications Studio

July, 2015

SAP Cloud Applications Studio 1508 Delta features highlights

© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2 Internal

SAP Cloud Applications Studio

1508 Delta Highlights

Legend: available X not available

1505 1508 Type Area Description Details

X New Studio Node Extensions

X New Studio Annotation [ChangeHistory]

X New Studio Production Bug Fix

X New Studio Extension fields on Custom Forms

X New Studio Performance Improvement

X New Studio Other Enhancements


Node Extensions (1/4)

Feature: Studio 1508 provides the support to add new nodes (custom nodes) to the

Standard Business objects.

Following are the scope and characteristics of node extensions for the current release 1508

Enhance SAP Standard BOs (XBO) with custom nodes.

The custom nodes can be nested (multi level) and have cardinalities of 0..1, 0..N, 1..N.

Actions & associations can be added to the custom nodes.

ABSL script files can be generated for the custom nodes.

Association of custom node to Standard BO nodes or different custom node of the same

extension BO or different Custom BO nodes.

Model the custom nodes in to the existing UIs using Embedded component.

Messages can be defined and raised on custom nodes.

No restrictions in annotations and data types for defining the elements within the custom

nodes.

Enabling the custom nodes for Data Sources, Web services, Forms is not supported with

1508 release.

Note: Not all Standard BOs support the node extensions. A list of the supported BOs will be published

soon in the https://help.sap.com/studio_cloud .

https://help.sap.com/studio_cloud


Node Extension (2/4)

Task 1: Node extension definition



Task 2: Create and configure Embedded Component

Add the EC to the Std screen via

Extensibility Explorer



Task 3: Runtime view of the custom node


Demo


Enabling Change History for Business Objects and

Extension (1/5)

Feature: With release 1508, Studio developers can enable Change History at a fine granular

level for all changes made to the elements, nodes, associations of custom business object as

well as standard business object extensions with the support of the new annotation

[ChangeHistory].

Business Value: With this feature, the business user can view at runtime all the changes

that has been carried out on the specific elements, nodes or associations of the custom

business object or extensions business objects.

Tasks: Annotate the specific nodes, elements or association with the keyword [ChangeHistory]

Add the Embedded Component

(“/SAP_BYD_APPLICATION_UI/Reuse/ChangeHistory/ChangeDocuments_EC.EC.uicomponent”) to the ‘Changes’ tab of

the OIF/TI.

Create binding between the OIF/TI and EC

Note: The Change Log feature at the BO level was available (only in ByD) in the previous releases via the

BCO.



Extension (2/5)

Task 1: Annotate the specific nodes, elements or association with the keyword [ChangeHistory]



Extension (3/5)

Task 2: Add the Embedded Component

(“/SAP_BYD_APPLICATION_UI/Reuse/ChangeHistory/ChangeDocuments_EC.EC.uicomponent”)

to the ‘Changes’ tab of the OIF/TI

Clicking on “Publish” will generate the web service for the custom business object



Extension (4/5)

Task 3: Create binding between the OIF/TI and EC



Extension (5/5)

Task 4: View the Change History. OIF/TI view -> Changes tab


Demo


Production Bug Fix (1/3)

Feature: In release 1508, Studio provides the support to do ABSL code changes directly in

the Customer’s production tenant.

Business Value: In general, if a partner/customer wants to do any code change to a

productive add-on, the recommended way is to create a patch in the test/development

tenant where the add-on was originally developed. The patch shall then be uploaded to the

production tenant only after thorough testing in the source tenant.

As there are associated risks of doing code changes directly on a production tenant, the

usage of Production Bug Fix feature is recommended only in cases where the source

tenant is already upgraded to a higher release than the production tenant and the customer

requires an urgent fix that needs to be carried out in the production tenant and cannot wait

until the production upgrade. Also the Partners/Customers has to make sure that such

code changes are double maintained in the current patch.

With this new feature the code changes can be directly done on the production tenant.

Tasks: Prerequisites.

Create correction.

Perform code changes, Save and Activate.

Close correction.



Task 0: Prerequisites

Assign the work center view 'Production Fix Authorization' to the Studio developer.

The Solution on which the code changes are to be carried out should be scoped and with Deployed status

Task 1: Create Correction

In the Solution Explorer, click on the highlighted icon to Create a Correction.

Read the Disclaimer pop-up and agree to proceed with the code changes.



Task 2: Perform code changes

In the Solution Explorer, Check-out the specific absl file for which the code change needs to be carried out.

Perform the absl code changes as required using the Studio absl editor.

Save and Activate the modified absl file.

Check-In the activated absl file.

Task 3: Close Correction

In the Solution Explorer, click on the highlighted icon to Close the Correction.

Once the correction is closed, the status of the Solution will be changed from

“Deployed-In Correction” to “Deployed”

On successful activation, the code changes will be active for the Business users.

Revert changes

In the Solution Explorer, right click on the specific file and click on ‘Revert’.

This will roll back all the changes done to the specific file to the state before

the correction was started (i.e., the previous successfully Deployed state).


Demo


Extension fields on Custom Forms

Feature: In release 1508, Studio provides the support to include the standard extension fields to the

Custom Forms built on the Custom Business objects.

Business Value: Until 1508 release, it was possible to include only the standard BO fields to the

Custom Forms via the association between the Custom BO and the Standard BO. However it was not

possible to include the extension fields to the Custom forms.

Now with 1508, Studio developers can include the extension fields of the standard BOs to the Custom

form via the association between the Custom BO and the Std BO.

< 1508 1508

element ce1:<data_type> element ce2:<data_type>

association to std BO

element se1:<data_type>


Custom BO

Standard BO

Custom Form

ce1

ce2

se1

se2

element ext1:<data_type>

element ext2:<data_type> Extension fields

element ce1:<data_type> element ce2:<data_type>

association to std BO



Custom BO

Standard BO

Custom Form

ce1

ce2

se1

se2

ext1

ext2

element ext1:<data_type>

element ext2:<data_type> Extension fields


Performance Improvements

With release 1508, the following performance improvements has been implemented.

BO and XBO delta activation – Solution level activation will now ensure that only those BOs and XBOs

are considered which are in ‘inactive’ state, all the active BOs and XBOs are not activated again. This is

same for activation during Assembly and Download process. This on a case to case basis improves the

performance of the activation significantly.

For example, in a large scale add-on solution when there are minor changes that are carried out in a BO

or XBO, the time required for the activation shall be significantly reduced.

PSM Check – Calls to PSM(Public Solution Model) checks and updates during Assembly are optimized.

During activation, if the PSM checks are executed once and further there are no changes, the

checks are not executed again. This improves the runtime performance.


Other Enhancements

Query function ExecuteFromDB : A new query function which enables to read

the data of a BO node directly from the database. Unlike the Execute() function

which returns the recent changes from the buffer, this new function returns only

the last saved image of the data.

query.ExecuteFromDB()

Function GetWeekday for Reuse library “Date”:

Returns the calendar week day of a date.

Example:

this.date = Date.ParseFromString("20150607");

this.result = this.date.GetWeekday();

Result: Numeric value 1

Annotation [SeparatelyLockable]:

This annotation on a node shall mark it as separately Lockable. It enables

Mass Data Runs to lock only those node on which they perform updates.

This resolves locking issue and the update can happen in parallel which

improves performance.

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Thank you

Contact information:

Kumar Raj Moorthy ( [email protected] )

Product Expert

SAP Cloud Applications Studio

mailto:[email protected]


© 2015 SAP SE or an SAP affiliate company.

All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an

SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE

(or an SAP affiliate company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional

trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind,

and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or

SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and

services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related

presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated

companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be

changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment,

promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties

that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking

statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

http://global12.sap.com/corporate-en/legal/copyright/index.epx



