16.02- 27.

02 TAW11

04.03 – taw11

12.03- taw final

UNIT14, 15 se scot;

Abap reppsitory se80

Se11table, abap dictionary

Class buider SE24

Se24- clase

Se11, abap dictionary

Se80-repository=>> function module

Se10 transport

Transport se da release la toate o data. Altfel ar putea crapa. Sunt functiile create???

SE37 functii

Se38 – rapoarte, programae

SE91 clase de mesaje, se grupeaza mai multe mesaje in clas

MESSAGE: Tnnn

Select was successful

001 select &1 was not successful

If sy_subrc=0.
 message S/I/ W/000(ZBC400_mSG_Class_LC).

Else.

message S001(ZBC400_mSG_Class_LC) with ‘scarr’

endif.

Se93- transactie

Top Include: declaratii de date care se pot accesa din orice subrutina??

Parametru, ii poti schimba valoare din ecranul de selectie.

Activate: activeaza codul in real time, save nu activeaza;

Face si check, si salveza;

Interfata: arametrii de intarre si iesire

Structura o parte din table

Subrutina nu e folosita in fara programului, doar in cadrul functieie

Se11 se considera la nivel global, tabele, structure

Data =o singura celula

Table type =nu continue date, doar defineste un tip de date

Continue mai multe structruri

Tioul unei linii din table type se defineste pe baza unei structure

Structra unui camp continue elem , date care sunt globale

Ls

Like ia doar type of dat not the length

Default for I =0, for character=space???

Text symbols: pot fi traduse, pag254

Constanta nu se schimba niciodata

Ctrl+space sugestii de nume…, keyword\

Is not initial: 0 la numeric

Spatiu la caractere??

DO IF….Ext

END DO

LS_scarr= nr linie din tabela unde cautam/loop

Sy_inde, a cata oara e in bucla

Sy_subrc= o , select e =o

=4, nu e cu success

Sy_TABiX, loop pe tabele interne

Sy_u

TEXT_001- pentru a scrie in engleza

F5 linie c linie in debug, pt debug trebuie sa fie activate program

Tot ce e cu prameters se creaza automat un ecran de selectie:

Unit 9 Debugger

-Click dr, execute, debugging,

- Click Breack-point la inceputul liniei,

- Breack username., doar mie se opreste in executia.
- /H
- Scri Breack-point;
- Linie cu linie F5 debug
- F7 in function module executa pana la capat
- F6 considera call de dunction modele ca fiind o singura sintaxxa
- Se executa dara fara sa intri in subrutina;
- F8

WATCh Point

Urmarest schimbarea unei variabile se opreste cu o linie inainte unde se schimba var pe care s-a pus
watch point

UNIT 10

Perform apel dubrutina-

- Surutine, sunt locale;

- Form, endfrom
-

Ce e cu DATA decarat e local, dar sunt globale pt routine, globale la nivel raportului;

De citit pag299, call by value, call by reference

- Ce este cu data declarant in cadrul unei subrunteste local

Clasa similar ca function module, dar e fromata din obiecte;

Unit 11

3 ipuri globale de date

Non-modifiable objects in a program, as mentioned in the context of ABAP
programming, are elements that remain constant and unaltered during the runtime of
the program. These objects include:

1. Byte code for statements: The compiled version of the program logic, which is
executed by the runtime system. Once compiled, the byte code remains constant
during program execution.
2. Values of constants and literals: Constant values or literal values (hard-coded
values) used in the program. These values are predefined and do not change
during the execution of the program.
3. Program texts: The actual source code and comments written by the developer.
The source code, once written, is considered non-modifiable during runtime.
4. Screen definitions: The layout and structure of user interface screens defined in
the program. This includes the arrangement of fields, labels, and other UI
elements.

The primary reasons for categorizing these elements as non-modifiable are:

 Stability and Predictability: Non-modifiable objects contribute to the stability

and predictability of the program's behavior. Their values and structures do not
change during program execution, providing consistency.
 Performance Optimization: Storing non-modifiable objects in a shared memory
area (such as the Program Execution Area or PXA) and buffering them helps
optimize performance. The system can reuse these objects without repeatedly
loading them from the database, reducing runtime overhead.
 Code Integrity: Certain elements, like byte code and program texts, represent
the core logic of the program. Treating them as non-modifiable helps maintain
the integrity of the program's logic and prevents unintended changes during
execution.

In summary, non-modifiable objects are essential for program stability, performance

optimization, and maintaining the integrity of the program's logic and user interface.
The provided information describes the behavior when starting an executable program
with the SUBMIT statement in ABAP (Advanced Business Application Programming),
which is a programming language used for developing applications within the SAP
environment. Let's break down the actions mentioned:

1. Ends the Calling Program:

 The SUBMIT statement is used to submit another ABAP program for
execution from within the current program.
 When the SUBMIT statement is encountered, the current program (the
calling program) is effectively put on hold, and the control is transferred to
the program specified in the SUBMIT statement.
2. Destroys the Internal Session of the Terminating Program:
 Each ABAP program execution occurs within an internal session in the SAP
system.
 When a program is terminated (either by reaching the end or
encountering an error), its internal session is destroyed.
3. Creates a New Internal Session for the Called Program:
 The program specified in the SUBMIT statement is then executed in a new
internal session.
 The system creates a fresh context for the called program, and this new
internal session is added to the session stack.
4. Replaces the Topmost Internal Session in the Stack:
 The session stack maintains a record of the sequence of executed
programs.
 The new internal session resulting from the SUBMIT statement becomes
the topmost session in the stack, effectively replacing the previous
topmost session.
In summary, using SUBMIT allows for the execution of another ABAP program
within the same SAP environment. It involves managing internal sessions to switch
betweenategories of Data Types ● Built-In ● Local ● Global These types will be used to define variables
(data objects). Data objects are always defined with the DATA keyword. You can use an ABAP standard
type, a local type, or a global type to define a data object. programs while maintaining a record
of the execution flow. This mechanism is commonly used for background processing or
executing reports in SAP systems.

 Local data types only exist in the program in question and, therefore, can only be used there.
The declaration is made using the TYPES statement.
 A data type defined in the ABAP Dictionary is called global, as it can be used throughout the
entire SAP system concerned.
 Categories of Data Types ● Built-In ● Local ● Global
 These types will be used to define variables (data objects).
 Data objects are always defined with the DATA keyword. You can use an ABAP standard type, a
local type, or a global type to define a data object.

If the domain of a check field has a value table, you have the option to let the system automatically
propose a foreign key relationship based on that value table. A foreign key relationship establishes a
connection between two tables, typically where one table (foreign table) refers to the keys of another
table (primary table). In this case, the domain's value table is proposed as a potential check table for the
foreign key field.

However, it's important to note that merely specifying a value table for a domain doesn't automatically
enable full value help and input validation for the field. To leverage these functions, you need to define
a foreign key relationship explicitly. The foreign key definition ensures that the field's values are
validated against the entries in the associated value table, providing both input assistance and validation
checks.

In summary, the domain's value table is used by the system to propose a potential check table for a
foreign key assignment, but you need to define the foreign key explicitly to activate the complete set of
value help and validation functions for the field.

1. Example:
  In the "Employees" table, if there is a column "DepartmentID" that is a
foreign key referencing the "Departments" table's primary key (e.g.,
"DepartmentID"), it establishes a relationship between the two tables. This
ensures that employees are associated with valid department IDs from the
"Departments" table.

In summary, tables store data, and foreign keys establish relationships between tables
by linking the data in one table to the primary or unique key in another table. This
relational structure allows for efficient and organized data storage in a relational
database system
UNIT 8:

Check Table : It is nothing but table it contains all valid entries of a particular foreign key table field.
Basically the check table is used for field level validation (it restricts the field value).

Example : A foreign key links two tables T1 and T2 by assigning fields of table T1 to the primary key fields
of table T2. Table T2 is then known as the check table of the foreign key.
 The check table will carry out the check for input values for the table field being entered in any
application and value table will provide values on F4 help for that table field.

https://blogs.sap.com/2020/12/01/check-table-and-value-table/

Text table,
Text Tables (SAP Library - ABAP Dictionary)

Gateway:- translator pentru web; intrepretor a serverului pt baza de date ;

Custumnamespace: z_
-stocheaza rapoartele si tot ce tine de client;
INPUT: selection screen
OUTput:dynpro, screens.

Creating Database View:

Data from several tables can be combined in a meaningful way using a view (join). You can also hide
information that is not important (projection) and display only those data records that satisfy certain
conditions (selection).

-The tables are appended to one another.

-the set of records that can be displayed with the view can be further restricted with a selection
condition.

-The join conditions can also be derived from the existing foreign key relationships. Copying the join
conditions from the existing foreign keys is supported in the maintenance transaction

-the set of data that can be selected with a view depends on whether the view implements an inner join
or an outer join. With an inner join, you only receive the records that have an entry in all the tables
included in the view. With an outer join, the records that do not have a corresponding entry in some of
the tables included in the view are also selected

-Database views implement an inner join. You only obtain the records that have an entry in all the tables
included in the view.

-Maintenance views implement an outer join.

-A database view is defined in the ABAP Dictionary and automatically created in the database during
activation. Accesses to a database view are passed directly to the database from the database interface.

-If the definition of a database view is changed in the ABAP Dictionary, the view created in the database
must be adjusted to this change. As a view does not contain any data, this adjustment is made by
deleting the old view definition and creating the view again in the ABAP Dictionary with its new
definition.

-The maintenance status defines whether you can only read with the view or whether you can also write
with it. If a database view was defined with more than one table, you can only read with this view.

- The data read with a database view can be buffered. View data is buffered in the same way as with
tables. The technical settings of a database view control whether the view data may be buffered and
how this should be done. The same settings (buffering types) can be used here as for table buffering.
The buffered view data is invalidated when the data in one of the base tables of the view changes.

---Selection with a database view is faster than access to individual tables. When selecting with views,
yyou must also ensure that there are suitable indexes on the tables contained in the view

-if an append structure is added to a table included in a view, the fields added with the append structure
are automatically included in the view

1 definit OK_CODE in TOP include

2 pus butonul de BACK in gui status

3 pus cod in PAI case when 'BACK'