SAP ABAP Data Element O2PAGTYP (Type of BSP Page)

Hierarchy

☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-TOO-WAB (Application Component) Web Application Builder
     ⤷ SO2_DBLAYER (Package) mySAP Application Server Pages: Database Layer

Basic Data

Data Element	O2PAGTYP
Short Description	Type of BSP Page

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	O2PAGTYP
Data Type	CHAR	Character String
Length	1
Decimal Places	0
Output Length	1
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Page Type
Medium	15	Page Type
Long	20	Page Type
Heading	15	Page Type

Documentation

Definition

The system supports the following page types:

• View
  A view contains a layout description within the Model View Controller (MVC) design pattern.
  The program flow is controlled by a controller, which calls a view to generate the on-screen display. Views do not, however, require event handlers. Nor do they have their own URLs, since only the assigned controller can receive the request.
• Page with flow logic
  This page type can be executed on its own - that is, it can be called using a URL.
  Data retrieval, input processing, and flow control are performed using the event handlers defined in the page.
  This type of page is suitable for small, simple applications. For larger applications, we recommend the MVC concept since it supports a strict separation of presentation from the flow and application logic.
• Page fragment
• A page fragment cannot be executed, that is, it cannot be addressed using a URL nor can it be used as a link in another page.
  However, it can be included in another page using the include directive, for example: <%@include file='./fragment.htm'%>.
  A page fragment has no page attributes, type definitions, or event handlers of its own. However, it can access the page attributes and type definitions (in the case of a "page with flow logic") of the surrounding page.
  A page fragment can itself include other page fragments.
  
  Page fragments are included during generation of the including page in such a way as if the respective page text took the place of the include directives. The are therefore used primarily to avoid multiple writing tasks and the are used to define uniform static areas in different pages of a BSP application (for example, uniform header area for all pages). They are not used for mudularization of tasks and functions, and particularly <ZHnot for modularization of script code. For these purposes, you should use function modules or methods (for example, from the application class), which - in contrast to page fragments - have a defined interface for data transfer and local data.

History

Last changed by/on	SAP	20030114
SAP Release Created in	50A