Floorplan for Object Instances (OIF) 
A design template that dictates the structure and behavior of a user interface for processing a business object instance.
You can use this floorplan to model an application interface that allows the user to create, delete, display, and change the attributes and associations of business objects (for example, an employee, or a purchase order).
Although the OIF floorplan is still in use, it has been superseded by the Overview Page Floorplan (OVP) as it no longer satisfies current UI guidelines.
Structure
OIF Floorplan in the Runtime Environment
An application configuration based on an OIF type floorplan typically shows multiple view tabs, whose content is determined by a defined business object and the related tasks a user must perform.
This floorplan has the following schematic structure:
Page Title (formerly, the Identification Region (IDR))
The system displays the title and step of the current activity in this area.
Page Toolbar
The toolbar contains action buttons and navigation options and links to more detailed information. The order and naming convention for the standard buttons are determined by the floorplan.
Information Area
This optional area, formerly known as the Extended Identification Region, displays all relevant information that more narrowly specifies the activity. It is divided into the following elements:
Ticket
Contains additional information that is displayed without a descriptor. Any available explanations can be found using the Quick Help.
Header Area
Contains additional information shown with the descriptor and value.
Message Region
This area is only visible if at least one message has been generated by the system.
Contextual Navigation Region (CNR)
This area consists of view and subview tabs. View tabs are used for switching between different OIF views and subviews. They are implemented with the HorizontalContextualPatternControl control. This is conceptually, technically, and visually different from TabStripControl and cannot be used outside of this navigation region of an OIF.
Content Area
This area provides information that can be edited by the user. The content is provided by individual UI building blocks (UIBBs).
Additional pages are available for this floorplan type, providing an initial screen and additional confirmation screens. If a business object is deleted, it is then necessary to navigate to a confirmation screen. This navigation is technically supported by the floorplan.
Note that if, during configuration, you define only one main layer with only one sub-layer, the tabs and sub-tabs are hidden at runtime.
OIF Floorplan in the Design Time Environment
Use FLUID (Flexible UI Designer) to display the floorplan component in the design time environment.
With respect to the floorplan structure at runtime (described above), note the following points:
Main Views and Subviews
Each main view or subview in the application configuration at runtime corresponds to one of the following types of views displayed in the Object Instance Schema:
Main View
Each Main View in the hierarchy represents one main view tab at runtime. Each Main View must contain at least one subview (which are only visible at runtime if there is more than one).
Subview
A Subview in the hierarchy represents a view tab that appears under a main view tab. Attributes allow you to name and identify the individual subviews. Like a main view, subviews must have at least one UIBB. You add UIBBs to a subview in the same way you add them to a main view.
Main views and subviews are available on a Main Screens type of page.
To make changes in the page title and information area, you must edit the IDR component configuration related to the application.
Settings for the message region are found in the General Settings panel.
Integration
The floorplan is implemented using the Web Dynpro component FPM_OIF_COMPONENT.
You can configure an application based on this floorplan using the FPM Configuration Editor.