Tag Archives

Archive of posts published in the category: Model

ABAP Programming Model for SAP Fiori – Part – 12

BOPF with Draft

In this tutorial, lets analyse how to work on Draft class to retrieve data from other entities and push all the data model’s data into respective tables. For our Airline scenario, we don’t have any specific business logic, so direct INSERT or UPDATE or DELETE operations to DB will work.

Our objective inside the Draft class is to collect the data from all the entities and then do DB operations accordingly.

In the Draft generated class, we redefine method /bobf/if_frw_draft~copy_draft_to_active_entity to apply our business logic for the Save sequence.

To retrieve the own data model entity and its child data model entities retrieve() and retrieve_by_association() methods can be used respectively. Follow the below code for retrieving the data from all the entities.

Once the retrieval is complete, data has to be organised in order to find whether the data has to be inserted or updated. Table type of each

Read More

Interact Model One computer

Interact Electronics was started in 1976 by Ken Lochner, a programmer who in the 1960’s
worked on the
Dartmouth Time-Sharing System.

The Interact computer was originally envisioned as a simple 4K game machine without a keyboard, but
further development showed that it could be much more – a full-fledged user-programmable computer.

By 1978, two years of redesign and $1 million in development costs resulted in the completed
Interact Model One computer system. The Interact Model One was shown by NCE/CompuMart at the
Personal Computing ’78
Personal Computer Show, which was held in Philadelphia, PA over the weekend of August 24th thru 27th, 1978.

The Model One system has no built-in programs – all programs and data must be loaded from the built-in cassette tape.

Although the programming language Edu-BASIC is included with the purchase of the Model One, it is very limited, and works with
integers only. An improved Level

Read More

Programming Model

This section under major construction.

Our study of algorithms is based upon implementing them as programs written in the Java
programming language. We do so for several reasons:

  • Our programs are concise, elegant, and complete descriptions of algorithms.
  • You can run the programs to study properties of the algorithms.
  • You can put the algorithms immediately to good use in applications.

Primitive data types and expressions.

A data type is a set of values and a set of operations on those values.
The following four primitive data types are the basis of the Java language:

  • Integers, with arithmetic operations (int)
  • Real numbers, again with arithmetic operations (double)
  • Booleans, the set of values { true, false }
    with logical operations (boolean)
  • Characters, the alphanumeric characters and symbols that you type (char)

A Java program manipulates variables that are named

Read More

ABAP Programming Model for SAP Fiori – Part – 8

CRUD Operation in SAP BOPF

From our data model of Airline which we have created, there are three Composite Interface views. It is always good practice to add semantic business object annotations to the composite interface views. Because Basic Interface views has to be reused in other applications as well, so we apply business object annotations on Composite interface views. To generate a BOPF business object based on the three composite CDS views, we must add several @ObjectModel annotations to the views.

In the Airline root view (ZAPF_I_AIRLINE), we must add the annotations on the header level.

Read More

ABAP Programming Model for SAP Fiori – Part – 10

Action in BOPF

Action has the literal meaning in BOPF. Do something. We can create an Action to an existing business object node by carrying out the following steps,

  • Open the business object (ZAPF_I_AIRLINE).
  • In the business object editor, click on Go to the Root Node link.
  • Select Actions tab, and choose New.

A dialog appears, where we must specify the details of the action:

  • Name: Enter the name of the action; in our case, we enter “Set URL”.
  • Description: Enter description that describes the purpose of the action, for instance, “Set the URL”.
  • Implementation Class: We can simply accept the suggestion that will lead to the generation of a global ABAP class or enter an already existing class that implements the interface /bobf/if_frw_action~execute. We will call the class ZCL_A_LOCK_APF_I_AIRLINE.
  • Instance Multiplicity: Select multiple node instances here, as we want the action to operate on several
Read More