Enhanced ABAP Develoment with Core Data Services (CDS)

Articles | Case Studies | White Papers | Q&As | Webinars | Videos | Blogs | Podcasts | Events | Magazine | Books | Why Subscribe?

Search
 

 
FINANCIALS GRC HR SCM CRM BI HANA CLOUD ADMIN/DEV EMERGING TECH

Close -

 
Article  
 
Enhanced ABAP Development with Core Data Services (CDS)
 
How CDS Brings a Modern Data Modeling Approach to ABAP
by Karl Kessler | SAPinsider, Volume 16, Issue 4  
October 8, 2015
 
With the advent of SAP HANA, a new data modeling infrastructure called core data services (CDS) has been introduced by
SAP to simplify how developers define semantically rich data models. Read on to learn the concepts behind CDS and how it
works in ABAP development processes, and walk through a step-by-step guide on using CDS with SAP’s development
toolset.

  Data models are a cornerstone of application development. They provide a

standardized method for defining and formatting database contents
consistently across systems, enabling different applications to share the same
data — reducing development costs, speeding time to market, and improving
quality and performance.

Those familiar with application development in the ABAP world are no

strangers to the traditional data modeling tools included with SAP NetWeaver
Application Server (SAP NetWeaver AS) ABAP — in particular, the ABAP
data dictionary (DDIC), which stores definitions of objects, such as database
tables and views, that can be used in ABAP programs. And then along came
SAP HANA and the new paradigm of pushing down data-intensive logic to
the database layer.

To take advantage of SAP HANA for application development, SAP

introduced a new data modeling infrastructure known as core data services UP NEXT @ SAPinsider
(CDS). With CDS, data models are defined and consumed on the database
rather than on the server. CDS also offers capabilities beyond the traditional Thursday, October 25
data modeling tools, including support for conceptual modeling and
Webinar: Boost Your Business with
relationship definitions, built-in functions, and extensions. Originally, CDS was
Extensions to SAP SuccessFactors
available only in the design-time and runtime environment of SAP HANA.
Please note that we use cookies to enhance your browsing experience. By continuing to use this site, you agree to our use of cookies andSolutions
our Privacy Policy. I accept
Now, the CDS concept is also fully implemented in SAP NetWeaver AS
ABAP, enabling developers to work in the ABAP layer
Read with ABAP
more
development tools while the code execution is pushed down to the database. Tuesday, October 30
This article focuses on the ABAP implementation of CDS. 1 It looks at the Webinar: How to Integrate Non-SAP
concepts behind CDS, and then walks you through a detailed example that Source System Data into Your
demonstrates how CDS in ABAP works, and how CDS is supported during Central Finance Implementation
the ABAP development process by SAP’s ABAP development tools for
Eclipse. Tuesday, November 6
What Is CDS? Q&A: The Changing Tax Landscape:
CDS is an infrastructure layer for defining semantically rich data models, Can Your Technology Handle It?
which are represented as CDS views. In a very basic way, CDS allows
developers to define entity types (such as orders, business partners, or Wednesday, November 7
products) and the semantic relationships between them, which correspond to
foreign key relationships in traditional entity relationship (ER) models. CDS is Conferences & Seminars: HR Payroll
defined using a SQL-based data definition language (DDL) that is based on Seminar
standard SQL with some additional concepts, such as associations, which
define the relationships between CDS views, and annotations, which direct Conferences & Seminars: Central
the domain-specific use of CDS artifacts. Another example is expressions, Finance Bootcamp
which can be used in scenarios in which certain CDS attributes are
considered as measures to be aggregated. See more »

Similar to the role of the DDIC in the traditional ABAP world, data models
based on CDS serve as central definitions that can be used in many different
domains, such as transactional and analytical applications, to interact with
data in the database in a unified way (see the sidebar "CDS in SAP
Software" for more on how SAP itself is using CDS in its own applications).

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

However, CDS data models go beyond the capabilities of the DDIC, which
were typically limited to a transactional scope (think of traditional online
transaction processing functionality). For example, in CDS, you can define
views that aggregate and analyze data in a layered fashion, starting with
basic views and then adding powerful views that combine the basic views.
Another difference is the support for special operators such as UNION, which
enables the combination of multiple select statements to return only one result
set.

Originally, CDS was designed for native SAP HANA application development.
It was introduced with support package stack (SPS) 06 for SAP HANA as
part of SAP HANA extended application services (XS), an application server
for SAP HANA that includes a runtime environment for native development.
With SAP NetWeaver 7.4 SPS 05, the CDS concept was also fully
implemented in SAP NetWeaver AS ABAP. While differences have evolved
between the two variants — for example, SAP HANA-based CDS obviously
operates on SAP HANA, while ABAP-based CDS operates on most major
database platforms as well as SAP HANA, and each has a different type of
repository for development objects — both variants pursue the same goal: to
represent central data definitions as a common basis for application
development of all kinds.

CDS in SAP Software

ABAP-based CDS plays a substantial role in the foundation of SAP Business Suite 4 SAP
HANA (SAP S/4HANA). A large set of CDS artifacts — several thousand CDS views —
consisting of several hundred thousand lines of ABAP code, represent the underlying core
data model of the SAP S/4HANA solution. The main motivation for SAP S/4HANA was to
provide a semantic layer on top of the traditional physical SAP ERP tables, which often
act as physical data containers on the database and have a very complex inner structure
that, in most cases, cannot be evaluated without traditional ABAP processing. The
semantically rich data modeling provided by CDS enables this layer in SAP S/4HANA,
facilitating simplified, efficient access to the underlying data.

The CDS data model used by SAP S/4HANA can be considered a successor to the virtual
data model used by SAP HANA Live, which uses SAP HANA calculation views to provide
real-time operational reporting and analysis of content from SAP Business Suite and other
sources. While the calculation views used by SAP HANA Live are supported only on SAP
HANA, ABAP-based CDS has been engineered with complete transparency to the
underlying database, meaning that all major database vendors are supported in addition
to SAP HANA, which remains the optimal database choice.

SAP developers are also using CDS for new SAP Business Suite developments,
especially in newer software components, although it is a bit more challenging to take
advantage of the full breadth of the unifying characteristics of CDS in SAP Business
Suite, as its data model has evolved over time.

Each CDS variant is properly embedded into the particularities of the

supported technology environment. With the ABAP variant, the integration of
CDS artifacts into the ABAP stack is fairly straightforward. The artifacts are
modeled and edited using the DDL editor tool within the Eclipse-based ABAP
development tools for SAP NetWeaver (known as ABAP in Eclipse). CDS
artifacts, like any other ABAP development object, are subject to the transport
system within SAP NetWeaver AS ABAP so that they can easily be
transported from a development system to quality assurance and production
systems. CDS artifacts are stored in the DDIC and can be accessed in ABAP
programs via Open SQL in the same manner as ordinary ABAP tables or
views.

CDS in ABAP: A Step-by-Step Approach

Let’s see ABAP-based CDS in action in a real-world development scenario.
Here, I’ll show you an example that demonstrates how to use CDS with SAP’s
development toolset.

1. Start ABAP in Eclipse

First, you need to start ABAP in Eclipse, which is a plug-in tool for ABAP
development that you install in your Eclipse workspace. (If you do not yet
have a local installation of Eclipse, simply download the latest version —
currently Mars — to your desktop.) SAP’s Eclipse-based plugins, including
ABAP in Eclipse, are available from its tools update site
(https://tools.hana.ondemand.com).

To start ABAP in Eclipse, open the Eclipse project explorer and switch to the
ABAP development perspective. To begin development work, establish a
connection to the ABAP back end by creating an ABAP project (in the
example, M36_001_d002831_en). With this connection, you can create new
ABAP repository artifacts, such as ABAP programs, classes, and, as in our
example, CDS artifacts.

You can create these repository artifacts as local objects belonging to the
$TMP package, but in this example we use an existing package called
ZDEV201 to house the CDS artifact. Simply right-click on the package icon,
and from the context menu select New > Other ABAP Repository Object (see
Figure 1).

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Figure 1 — Create a new repository object

 
 

2. Create a New CDS View

In the New ABAP Repository Object pop-up, search for the DDL source
editor and select it to launch the New DDL Source wizard (see Figure 2).
First, specify the basic properties of the view. In the example — which is a
simple scenario based on SAP’s well-known Enterprise Procurement Model
(EPM) demo model — we want to count open invoices that have not yet been
paid by business partners. So we specify the technical name
(ZDDLS_E2E_INV_COUNT_201) and some short text to describe the view
(“CDS view: open invoice count”). The underlying package (ZDEV201) is
assigned automatically.

Figure 2 — Specify the basic properties of the view

Note that one of the fundamental differences between CDS in native SAP
HANA and CDS in ABAP lies in the view definition. In both the ABAP and
SAP HANA scenarios, you begin your development work by creating views on
top of existing database tables that are contained in the DDIC. With CDS in
native SAP HANA, you must create the basic entity types that correspond to
the DDIC tables as part of the CDS view definition. With CDS in ABAP, you
can simply refer to any underlying DDIC table, view, or type from within the
CDS view definition, avoiding the need to “duplicate” the DDIC table
definitions on the CDS layer. In the ABAP scenario, the CDS definitions are
considered DDIC artifacts and need to be activated like any other DDIC
artifact, and when changes are made, their impact is propagated to
dependent artifacts.

3. Assign a Transport Request

On the next screen of the New DDL Source wizard, assign a transport

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

request for the view (see Figure 3). After assigning the view’s DDL source to
an existing ABAP package, either select an open transport request or create a
new one, which you can use to keep track of the changes that make up your
development tasks. This transport request can be bundled with tasks from
other developers and later transported to a subsequent system for test and
then production.

Figure 3 — Assign a transport request

There is no need to go to the lower levels of the underlying database (such as

SAP HANA) to manage the transport of CDS artifacts. All changes and
transports are managed in the ABAP layer end to end.

4. Select a Template for the CDS View

The last screen of the New DDL Source wizard (Figure 4) offers a selection
of templates for creating a CDS view, including a display of the default syntax
provided with each. There is a template for a basic view; templates for
building views with more advanced features (such as joins, associations, and
parameters); and a template for extending a view (by adding fields, for
instance). For the example, we choose the basic view template.

Figure 4 — Select the basic view template

The templates include placeholders for code that you fill in step by step. If
you later discover the need to change or extend the nature of your CDS view,
you can always change the source code directly in the DDL editor and freely
edit all parts of it as needed. This is particularly helpful if you want to copy
portions of the source code from example code, for instance.

5. Complete the Coding for the View Definition

After selecting the template and clicking on Finish, you are ready to fill the
placeholders provided by the template to complete the definition of our view
ZDDLS_E2E_INV_COUNT_201 (see Figure 5). Open the DDL editor —
which is a source code editor that offers very rich context-sensitive code
completion capabilities — from the project perspective in the Eclipse project
explorer via the context menu.

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Figure 5 — Define the view in the DDL editor

First, specify an ABAP repository name for the view — ZV_INVCNT_201 in

the example. The text label and view name are filled in automatically based
on the information entered when specifying the basic properties of the view.
Then specify the target data source for the invoice count. The underlying
base table to be used as the target data source is named
sepm_sddl_so_invoice_header (referenced as “inv”) but with the code
completion functionality included with CDS, you don’t have to remember long
names like these — you can simply start typing a prefix, such as
sepm_sddl_so, and all matching base tables are displayed in a list, where you
can view the details of each table (such as fields and their types) and select
the table you want.

You can view the details of any of the syntactical elements that make up a
CDS view definition on the fly by pressing the F2 key. The tooltip pop-up
shows all the attributes, the corresponding data elements and types, and the
associations (relationships) between the element and other tables or views,
including their cardinality. For instance, in the example, the tooltip pop-up
shows that the invoice header table contains a number of associations,
including an association with a buyer table. With the tooltip functionality, there
is no need to navigate deeply inside the DDIC — all of the relevant
information is visible in one place.

6. Add Any Associations

For the view to count the number of open invoices, it needs to collect
information about the buyer, such as the customer ID and name. To enable
this, navigate along the association between the view’s underlying invoice
header table and the buyer table, which is syntactically facilitated by a path
expression separated by dots. To add the association to the view definition,
you type a reference to the invoice header table (“inv”) followed by a dot (see
Figure 6). A list of available attributes, including associations, appears once
you have typed the dot.

Figure 6 — Add an association to a table to collect information

Select “buyer” to add the association to sepm_sddl_businesspartner, which is

a view that encapsulates the buyer table, to the view definition, and then add
another dot to display the columns available in the “buyer” view (see Figure
7). Add the columns you need to count the open invoices:
business_partner_id, company_name, and address_key. Figure 8 shows the
completed code.

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Figure 7 — Define the association

Figure 8 — The completed view definition

7. Execute the Code and View the Results

With CDS, you can activate and test your code right away by pressing the F8
key, which immediately previews the results in the data browser (see Figure
9).

Figure 9 — The result set previewed in the data browser

 

Additional Options for Refining CDS Views

Let’s look at a few different ways you can fine-tune a CDS view to get the
result set that best meets your needs.

Using Aggregation and Grouping

In the example scenario, the result set includes all business partners, not just
the ones that have not yet paid their invoices. We can refine the results by
manually adding a counter in the source code (see Figure 10).

Figure 10 — Add a counter to the view to refine the result set

The count function requires a group by clause, however, which is missing

from our source code. Using the quick-fix capabilities of Eclipse, we can add
the missing group by clause with a single click. Click on the highlighted select

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

statement and choose Add Group by Clause, which automatically inserts the
group by clause containing the elements you defined for the count (see
Figure 11). To restrict the result set, we manually add a simple where clause
that returns results with a payment status other than “P” for paid (see Figure
12).

Figure 11 — Add a group by clause to the counter

Figure 12 — Add a simple where clause to restrict the results

Now you can rerun the CDS view by pressing the F8 key, which reveals that
the result set of the view is still raw — it contains address keys, which are
GUIDs pointing to address records, when the actual city and street names
would be more useful (see Figure 13).

Figure 13 — The result set returned by the modified view definition

 

Using View Hierarchies and Associations

To show the city and street names in the result set, instead of the GUIDs
pointing to address records, define a second CDS view that declares an
association to the addresses of the business partners.

First, create another view called Zddls_E2e_Cust_Classify_201 in the

ZDEV201 package, as described previously (see Figure 14). Specify the
basic properties of the view in the New DDL Source wizard, such as the
technical name (ZDDLS_E2E_CUST_CLASSIFY_201) and some short text to
describe the view (“CDS view: customer classification”).

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Figure 14 — Create a second view to tailor the result set display

 

On the transport request screen (Figure 15), assign the newly created view
to the open development request, and on the view template screen (Figure
16), choose Define View with Association. The syntax for this is slightly more
complicated — the association contains an “on” condition, which is similar to
a join operation.

Figure 15 — Assign a transport request for the second view

Figure 16 — Select the view with an association template

After selecting the template, open the DDL editor to complete the view
definition. As with the first view, specify an ABAP repository name for the
corresponding ABAP view (ZV_CUSTCLSFY_201 in the example). Again, the
text label and view name are filled in automatically. Then specify a data
source for the view, which is the first view created in this example

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

(Zddls_E2e_Inv_Count_201), along with a target data source for the

association created by the template. As before, pick a data source with the
aid of the code completion functionality by typing the prefix sepm_sddl and
selecting sepm_sddl_address (referenced as “_address”) from the matching
items (see Figure 17).

Figure 17 — Define the view and its association in the DDL editor
 

Next, fill out the “on” condition defining the source and target columns that
are connected by the association. For the source, specify the first view
Zddls_E2e_Inv_Count_201 and select address_key from the displayed list of
available columns (see Figure 18). For the target, specify the target data
source (referenced as “_address”) for the association and select the
corresponding address_key from the displayed list of available columns (see
Figure 19).

Figure 18 — Define the source for the association

 

Figure 19 — Define the target for the association

Using View Fields and Expressions

The next step is to define the view fields. The system tells you that the
address_key column needs to be part of the view’s signature (because it is
the link between the two views), so quickly add it by typing the prefix “ad” and
using the code completion functionality (see Figure 20). Likewise, add
customer ID and customer name. Figure 21 shows the completed definition of
the view fields for the association.

Figure 20 — Define the view fields for the association

 

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Figure 21 — The completed definition of the view fields for the association
 

Finally, to demonstrate the versatility of CDS, let’s add a calculated field that
is based on conditions that need to be met. To define this field, manually add
a case expression (see Figure 22). The completed case expression for the
example (Figure 23) delivers a category field that assigns a certain value
depending on the number of open invoices: “C” for less than 5,000; “D” for
between 5,000 and 10,000; and “S” for more than 10,000.

Figure 22 — Add a case expression to enable a calculated field

Figure 23 — The completed case expression

 

Lastly, add view fields that contain address information by specifying the
target data source — “_address” (see Figure 24) — and then selecting
country, street, city, and postal code from the list of available columns (see
Figure 25).

Figure 24 — Specify the data source for the view fields

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Figure 25 — Specify the view fields to display in the result set

Figure 26 shows the completed code.

Figure 26 — The refined view definition

 

Viewing the Refined Results

Activate and run the view, which displays the results shown in Figure 27. As
you can see, all of the refinements are reflected in the data browser.

Figure 27 — The result set returned by the refined view definition

The association details defined in the DDL editor are also integrated into the
data browser. As in the DDL editor, you can navigate along the various
associations, meaning that you can select a row and view a list of
associations, such as address (see Figure 28). Selecting an association will
display the resulting record that is referred to by the association (see Figure
29), which can be used for testing and analysis.

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Figure 28 — Navigating along an association in the data browser

Figure 29 — Displaying the record referred to by the association in the data browser

Figure 30 shows our completed CDS artifacts in the Eclipse project explorer.

Figure 30 — The completed CDS artifacts in the Eclipse project explorer

 

Summary
SAP NetWeaver 7.4 brings the CDS concept introduced for native SAP
HANA development to the ABAP development world. Powerful CDS functions
such as associations and annotations are fully integrated into ABAP in
Eclipse, and assist developers at each step of the definition process. And
since CDS is executed at runtime directly on the database layer, it facilitates
the code pushdown paradigm pioneered by SAP HANA right from the
beginning. With these features on hand — along with the CDS enhancements
included in the upcoming 7.5 release of SAP NetWeaver 2 — developers will
have the tools they need to succeed in a modern business landscape.

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

1 Learn more about the SAP HANA implementation of CDS at http://bit.ly/1jDYMss. [back]

2 Learn more about CDS enhancements in SAP NetWeaver 7.5 in my article “A Foundation for the
Future” in the July-September 2015 issue of SAPinsider (SAPinsiderOnline.com). [back]

Karl Kessler
Karl Kessler (karl.kessler@sap.com) joined SAP SE in
1992. He is the Vice President of Product Management
ABAP Platform — which includes SAP NetWeaver
Application Server, the ABAP Workbench, the Eclipse-
based ABAP development tools, and SAP Cloud Platform
ABAP environment — and is responsible for all rollout
activities.

More from SAPinsider

A Foundation for the Future SAP Fiori Application A Guide to SAP's Development
Development in the Cloud Environments for SAP HANA
and the Cloud
In this column, SAP’s Karl Kessler
reveals what to expect with the Gain a comprehensive
upcoming release of SAP understanding of the new ways in Read this in-depth column for a
NetWeaver 7.5. He highlights the which SAP Fiori applications can be comprehensive understanding of
market changes that have built using SAP Web IDE on SAP SAP’s current main tooling
necessitated a new foundation, HANA Cloud Platform, as well as environments for supporting SAP
details... how to... HANA and the cloud, including both
desktop- and browser-based
environments. You will gain...

COMMENTS
Please log in to post a comment.

Ivan Panchev

2/23/2018 11:48:31 AM

Thank you

bose

1/7/2018 8:21:18 AM

Needful Info. Thank you

WAa

10/3/2017 7:05:16 AM

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Great article.

ahns

9/26/2017 6:49:09 AM

good

ahns

9/26/2017 6:43:05 AM

works for me

ahns

9/26/2017 6:35:37 AM

works for me

ahns

9/26/2017 6:33:53 AM

this is so helpful, thank you.

ahns

9/26/2017 6:33:26 AM

this is so helpful, thank you.

ahns

9/26/2017 6:27:49 AM

this is so helpful, thank you.

ahns

9/26/2017 6:23:52 AM

this is so helpful, thank you.

ahns

9/26/2017 6:23:35 AM

this is so helpful, thank you.

ahns

9/26/2017 6:22:36 AM

this is so helpful, thank you.

ahns

9/15/2017 8:47:45 AM

Great

Jim D

3/16/2017 1:11:33 PM

This was a great and very useful article. I was able to create CDS views with JOINS on our ECC (SAP_BASIS) 740-009.

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]

Enhanced ABAP Develoment with Core Data Services (CDS)

Development system. Should we see any performance gains on ECC? If yes, are there guidelines? Multiple CPU's
required? As a test, I wrote a program to do selects from the CDS views using MARA JOINing MARC and MARC joining
MARA against ECC SELECT Joins returning the same fields. I captured actual run times and they are almost identical from
an ECC report. In ECLIPSE there appears to be a slight advantage to the CDS views. Thank you-Jim

ABOUT US CONTACT US PRESS ROOM ADVERTISE FAQ PRIVACY POLICY SITEMAP

SAPinsider is published by WIS Publishing, a

division of Wellesley Information Services. SAPinsider insiderPROFILES
20 Carematrix Drive, Dedham, MA 02026 USA SAPinsider Conferences & Seminars SAPexperts
Sales and Customer Service: 1(781)751-8799;
customer@wispubs.com SAPinsider Seminars on Demand
© 2018 Wellesley Information Services. All insiderBOOKS
rights reserved.
Online ISSN #2155-2444, Print ISSN #1537-
145X
SAP and the SAP logo are trademarks or
registered trademarks of SAP SE in Germany
and other countries.
 

https://sapinsider.wispubs.com/Assets/Articles/2015/October/SPI-enhanced-ABAP-development-with-Core-Data-Services[10/22/2018 8:55:34 PM]