A3K Frame Work:

Gui Layer:
For the graphical design, WindowBuilder is available for the developer
Connection of data windows and interface elements with the dialog layer
Legacy concept

PowerBuilder emulation (mapping and binding)

relevant PowerBuilder emulation class.

connection is via the

Gets used by older Core windows; to be used by customers only for the
adjustment of such old Core windows

New concept

Data Binding (short: Binding)

GUI component is connected directly.

To be used, if applied for the Core window with the new concept or an
independent new window is created.

DiaLogLayer: 1:1 abstraction through Gui Layer

Context:The context is generally the current business object (e.g. person, contract,
claim), which is transferred to the dialog layer.
Persistent:A persistent corresponds to a table (e.g. TPERSON, TVERTRAG,
TSCHADEN) and is a data object. The contexts mostly relate to one of the business
object persistents person, contract, claim from which the associated business logic
object can be fetched.
RemoteClassMapper: Connects the interface (GUI) with the appropriate dialog
object
DoClasses:
Dialog equivalents for the GUI structures and components, e.g.

File

DoAkte

Window

DataWindow

Button

Text

DoPage
DoGroup or DoList

DoCommand
DoField

Business Logic Layer:

Contains ABS Business logic and validations.
Independent of the representation, can therefore be used from client and portals
Unit Of Work(UOW):
Transaction block via a business process
Manages all changes which are related to database tables and knows which
persistents must be saved
Corresponds to a GUI file
Persistence Layer:
Contain as a cache
Contain the database access component ORBIT
Also called as DATALAYER
The persistence layer is used as a tool kit by the business layer.
The developer uses only the access classes and not directly the ORBIT.
Views and persistence interfaces use ORBIT for DB accesses, where

Views access the DB (read-only)

Persistence interfaces work on ORBIT data (cache) as soon as these are

loaded from the DB (reading/writing)

Accesses to DD and OP data

ORBIT ensures that DD data are not changed persistently

Persistent changes are only possible on OP data

Everything in ORBIT cache is directly written to the database.

Persistance Manager:
Manages the access channels to the data sources (DD reading, OP writing/reading)
Thus abstracts the data access, see ORBIT
Is a component of ORBIT

Domains:
Are components of the data model and are loaded in the ORBIT cache

With A3k+ extensions are possible on all layers

Most important A3k+ extension mechanisms are:

Parameterization in order to set the configuration switches for the application
Inheritance in order to extend the Core GUI
Business adapters in order to extend the Core business logic objects
Extension points in order to support any number of customer specifications
Extension Points:
At an extension point any number of extensions which extend the existing
functionality can be registered.
This is a 1:N relation.
Extension Adapter:
Using an extension adapter, an existing function can be extended by precisely one
component.
This is a 1:1 relation.
Inheritance:
With inheritance, an existing functionality can be reused and extended without reimplementing it.
Adapter:
Similar to inheritance, an existing functionality can be reused and extended with the
help of the adapter concept without re-implementing it. This does not lead to an
extension explosion.
When compared with inheritance, the adapter concept is the better
solution for extension.

Extension Mechanisam:

GUI
Dialog

Business

Persistence

Inherit
ance

DialogContribu
tors
NavigationNod
Extension
adapter
Extension
point
Business
Generation
via
Core

ABS Batch:
Batch is responsible for automation and post-processing of processes in ABS
- Not online without batch - The operationally leading inventory is managed on the Host
Frequently Used Terms in ABS Batch:
Program:

Batch Job: A job starts a program in a single instance and processes record by record.
No parallelism
For programs with less input or e.g. need-based carrier.
Batch Services:
A service has advantages over a simple batch job:
Supports parallel activities
Can be defined as a permanent carrier
Can be controlled externally
Process:
Prescribed succession of programs
FlashCopy:
Flash on operational database, complete copy on another computer for month-end, printing and
delivery of data warehouse. Condition for 24x7 operation in case of a higher load
ABS Operatinoal Day Featuers:
Start,SpecialDays,Process,End.
The logical ABS operating day is not necessarily a calendar day.
Examples of critical jobs:
Provision of environment variables (e.g. logical working day)
System / infrastructure consistency checks (DB2-system, web server, etc. are accessible?)
Mandatory processing of impulses of TBATCH_PROT or TDRUCKOUTDATEN (depends on logical
working day)

Cash flow is carried out externally as well as internally

General ledger transition

The most important batch processes in the time

sequence Overview
Preparation for the online operation
Batch processes parallel to online operation
Post-processing
Examples of worklists filled by the host:
Claim work list :Claim assigned to a clerk or team.
Application work list:New and to be changed Applications.
Assignment work list: Assignments in claim processing
Reminder evidence work list: Status of contracts in
reminder
Document work list: Incoming documents, which are to be
assigned to a contract or claim and are not functionally
distinct
Processes of policy processing during batch
processing.
Continuous checking and correction of inputs
Processing an application or contract amendment
Completion
Batch processes in claim post-processing

Continuous acceptance of claims and events from online

processing
Processing a claim
Completion
Monthly subsequent invoice creation (FRE)
Selection
Processing a contract due in the subsequent month
Completion