Welcome!

Course Objectives

Upon completing this course, you should be able to:

Explain Basic functional processes in SAP TM
Understand technical aspects of SAP TM
Know about BOPF Framework
Know about FPM and FBI
Able to handle developments in SAP TM
Course Content Duration

Module 1: SAP TM Overview 2 hours

Module 2: BOPF Architecture Overview 8 hours
Module 3: BOPF Consumer Implementation 8 hours.
Module 4: TM UI FPM and FBI 8 hours
Module 5: Output Management PPF Framework 4 hours.
Module 6: POWL 2 hours
Course Title: TM Technical

Module 1: SAP TM Overview

Module 1: Objectives

At the completion of this chapter you

should be able to:
Demonstrate benefits and features of
SAP TM
Demonstrate various scenarios in
SAP TM
Demonstrate various processes in
SAP TM
Demonstrate Master data
requirement in SAP TM
Demonstrate various elements of
Transportation network.
Demonstrate Master data required
for charge management.
Module 1: TM Overview =>
User Involvement in SAP TM
 Module 1: TM Overview> User
Involvement in SAP TM
Shipper Someone who sends goods for shipment, by packaging, labeling, and arranging for
transit, or who coordinates the transport of goods

Freight Forwarder A freight forwarder, forwarder, or forwarding agent, is a person or company

that organizes shipments for individuals or corporations to get goods from the manufacturer or
producer to a market, customer or final point of distribution

Consignee the consignee is the person to whom the shipment is to be delivered to whether by
land, sea or air.

Carrier - Person or company that transports goods and is responsible physical movement of
goods and any possible loss of the goods during transport.
Module 1: TM Overview >
Transportation Scenarios
SAP TM supports following five scenarios:
Domestic Outbound Transportation.
International Outbound Transportation.
Domestic Inbound Transportation.
International Inbound Transportation.
Outsourcing Transportation

Domestic outbound is simplest of all the scenarios. It is further broken down into
following sub scenarios.
Truckload Shipments (FTL or LTL).
Intermodal (IM).
Direct Shipment.
Multi-Stop Shipments.
Pool Shipments.
Module 1: TM Overview > SAP TM
Solution
Module 1: TM Overview > Scenario
and Process Details
 Module 1: TM Overview >
Transportation Process
SAP TM divides transportation process into four main categories:

Order Management: The initial event triggering transportation management

is Order management. It involves request for transportation of goods. This is
mainly a front office job to accept orders from different types of customers

Managing Transportation Requirement Both Inbound and Outbound.

Managing Forwarding Orders Internal Status Management within TM

Transportation Planning: Once a request is placed, next step is to begin

planning of movement of goods. It involves determination of mode and means
of transportation depending on source and destination location in cost
efficient way.
Planning and Optimization.
Managing Freight and Bookings.
Planning Freight and Selecting Carriers.
Tendering Freight Contracting with Freight Carriers.
 Module 1: TM Overview >
Transportation Process
Transportation Execution: After planning is done, its time now to execute the plan. It includes
selection of carriers based on factors like cost or reliability. The process includes
initiating the goods issue, creating the transport order, and triggering the decrement
of inventory.
Executing and Monitoring Freight

Financial Settlement: Once freight orders have been executed, the next step
requires the completion of financial settlement. Integration with SAP ECC is used
for financial settlement.
Settling Freight Orders.
Settling Forwarding Orders.
Compliance Adherence to international trade and compliance in logistics.
Integration of settlement documents in ECC.
Integration of customer billing.
Module 1: TM Overview > Master
Data
To setup SAP TM we need to set up master data for various transactions. Master data
plays significant role in proper transportation planning and execution. As SAP TM is
integrated with SAP ECC, so ECC master data needs to be synchronized in and used
in TM system. Following are the basic master data maintained in TM.
Locations Production Plant, Distribution Center, Shipping Point, Stock
Transfer Point, Storage location, MRP area, Customer, Vendor, Transportation
Service Provider, Terminal, Store.
Transportation Zones and Hierarchies.
Transportation Lanes ( Routes).
Schedules.
Business Partners.
Carrier Profile.
Product (Materials transferred from ECC).
Dangerous Goods Master.
 Module 1: TM Overview >
Transportation Network
Locations
Are geo-coded (longitude and latitude).
Can be assigned to transportation zones.
Can act as trans-shipment locations.
Are the nodes of the transportation network.
Trans-shipment Location It is the intermediate location used for loading and unloading of goods.
Transportation Zones It can group several locations (customers, vendors) as well as other zones. Zones can
be of several types Direct, Postal Code, Region, Mixed. We can also organize zones into hierarchies for
better planning.
Means of Transport It represents class of vehicles. It is used in connection with transportation lane.
Transportation Lanes It represents direct route between two locations for transport of freight. It can be a
direct route between two locations or a location and a transportation zone or two transportation zones.
Transportation Lanes are uni-directional, for reverse route we need to create another Lane. Further it can have
validity period.
Resources A vehicle resource represents a specific vehicle with specific dimension.
Mode of Transport - > Means of Transport -> Resource
A resource specifies the available capacity and the hours in which they can be operated.
Module 1: TM Overview > Charge
Management Master Data

Charge Management uses master data to calculate transportation charges for a

forwarding order or freight order, and for transportation planning.
Scales Product, Package Type, Weight, Volume, Means of Transport, Location,
Distance, Business Partner.
Rate Tables Rate tables contain the freight rates for transportation services and
allows to maintain rates for certain validity periods. A Rate Table can contain up to 9
dimensions for rate maintenance.
Calculation Sheets Transportation charge calculation sheet includes transportation
charge elements, subtotals and totals.
Charge Calculation Rules.
Freight and Forwarding Agreements.
 Module 1: SAP TM Overview - Takeaway

All the participants now, should be able to:

Demonstrate benefits and features of SAP TM
Demonstrate various scenarios in SAP TM
Demonstrate various processes in SAP TM
Demonstrate Master data requirement in SAP
TM
Demonstrate various elements of
Transportation network.
Demonstrate Master data required for charge
management.
Course Title: SAP TM Technical

Module 2 : BOPF Architecture Overview

 Module 2: Objectives

At the completion of this chapter you

should be able to:
Understand SAP TM BOPF
architecture.
Understand BOPF business object.
Understand and implement various
elements of BOPF business object
Actions, determination, validation,
query, alternative Keys in BOPF
object.
 Module 2: BOPF Architecture >
Overview
SAP TM uses BOPF (Business Processing framework) to access and store business
data in SAP database.
BOPF framework is highly encapsulated framework for business data processing.
BOPF framework is based on object oriented programming.
Avoids use of direct select and update on database, thereby maintaining database
integrity.
Business processes are represented as Business objects as single entity instead of
distributed database tables.
Different business processes communicate with each other through cross BO
relationship.
Provides associations among different nodes of the business objects and to access
cross BO
 Module 2: BOPF Architecture >
Business Object
Implemented business processes operate on business objects.
A business object is a representation of a type of uniquely identifiable business
entities described by a structural model and an internal process model.
A business object can inherit its characteristics and configuration settings from
another business object and enhance the characteristics and settings.
A business object and its characteristics and configuration settings can be enhanced
by an enhancement.
A BOBF business object can be used to implement a business object or an
application from the scratch.
BOBF Business object comprises of multiple nodes with Root node as mandatory
one. There can be 1:1, 1:n, relationship between nodes.
 Module 2: BOPF Architecture >
Structure

BOBF Model consists of Business object representing business processes. Below are
the main Business objects:
Business Process Object (TOR/TRQ/etc).
Dependent Objects (Attachment Folder/Test Collections).
Master Data Objects (BUPA/Location/FreightAgreement/TCCS)
Meta Data Objects Not in the scope of this session.
Technical Objects Not in the scope of this session
 Module 2: BOPF Architecture >
Transaction Codes
Three must know Transaction Codes for TM Developer:

/BOBF/CONF_UI Check configuration/structure of BO / Create new BO(Used till

8.0 to create new BO. As of 9.0 new BO can be implemented using CUST_UI)
/BOBF/TEST_UI Test BO operations.
/BOBF/CUST_UI Enhance existing BO / Create new BO(Recommended to create
New BO)

Types of Nodes in BO
Standard Node
Delegated Node
Business Object Representation Node (Cross BO)
 Module 2: BOPF Architecture > Object
Elements
BOBF Object model has
following main elements.
1. Associations.
2. Determinations.
3. Validations
Consistency/Action
4. Actions
5. Queries
6. Alternative Keys
7. Status Variables
8. Status Derivators
9. Status Schema
10. Attribute Value Set
 Module 2: BOPF Architecture >
Associations
An association is a direct, uni-directional, binary relationship between two business
object nodes.

Associations can be used to relate two nodes in a well-defined direction. The

association can be used to navigate from one node (source node) to the related node
(target node). The associated nodes can be nodes within one business object or in
different business objects (cross business object association).

Associations can have parameters to filter the result of the related nodes.

Associations can only be defined between two nodes and in one defined direction.

Associations have a defined cardinality which gives information about the existence
of an association and the number of associated nodes.
 Module 2: BOPF Architecture >
Determinations
A determination is an element of a Business Object node that describes internal
changing business logic on the Business Object.
A determination can be used to trigger business logic based on internal change in
state of Business Object.
A determination is only triggered if trigger nodes are assigned and instances of these
trigger nodes are changed.

Example
Read attributes from master data (for example, the product master) if the product ID
changes.
Calculate the header weight if the item weights change.
Determine status changes based on the quantity changes (see also state guard).
Module 2: BOPF Architecture >
Determinations (Creation)
Module 2: BOPF Architecture >
Determinations (Creation)
 Module 2: BOPF Architecture >
Validations
A validation is an element of a business object node that describes some internal
checking business logic on the business object .
Action Validation: a validation can be used to check if an action is allowed.
Consistency Validation: a validation can be used to check the consistency of a
business object.
An action validation is carried out when an action is called before it is performed. If
some validations fail, the action is not performed for the instances where the
validation failed. Depending on the action settings, the action is not performed.
A consistency validation is only triggered if some of the trigger nodes are assigned
and instances of these trigger nodes are changed.

Example
Check if an order can be released depending on a defined time interval for release.
Check if the master data exists and is valid.
Module 2: BOPF Architecture >
Validations
Consistency Validation can be
used to provide warning / error
message and / or prevent save.
Need to populate failed key &
message class

Action Validations can be created

by right-clicking on the selected
action
 Module 2: BOPF Architecture >
Actions
An action is an element of a business object node that describes an operation
performed on that node.
An action can be used to allow the external triggering of business logic (in contrast
to a determination)
When the action is performed, you must specify the key for the instances on which it
is to be performed (if it is not a static action) and any input parameters that the action
requires
An action can only be performed with the number of instances that is configured in
the cardinality of the action.
The action is performed for all instances if an error in the action validation has not
occurred. If errors occur, then the behavior depends on the action settings.
Example
The following are examples of an action:
Release Order
Post Goods Movement
Copy Sheet
Module 2: BOPF Architecture >
Custom Action

Action can be called by method

do_action from Service Manager or
linked to a UI Button
Module 2: BOPF Architecture > Queries
A query is a defined set of attributes, such as search parameters, that return the queried IDs
of the business object node instances
A query allows you to perform searches on a business object.
Queries provide the initial point of access to business objects. Each query has an associated
parameter structure. The result of the query is a set of all the record IDs in a business object that
match the query criteria.

Example
The QUERY_BY_COMPLETION_STATUS queries the outbound deliveries that have a
specific completion status. The completion status is defined as a search parameter. The query
returns the keys of all outbound deliveries that fit the given search criteria. For example, all
outbound deliveries which are not complete.
 Module 2: BOPF Architecture > Alternate Key
1. An alternative key is a defined set of attributes of a business object node that is unique for each
node instance.
2. An alternative key can be used to identify a business object node. Multiple alternative keys can be
defined for a business object node.

Example
The key of the root node of the business object outbound delivery is a (non-readable) GUID. One
alternative key is the readable internal number that is also unique and identifies this node instance,
which is defined on the root node (the business object instance).
Module 2: BOPF Architecture >
Node Structure
Module 2: BOPF Architecture > Node Combined
Structure
Module 2: BOPF Architecture - Takeaway

All the participants now, should be able to:

Understand SAP TM BOPF architecture.
Understand BOPF business object.
Understand and implement various elements of
BOPF business object Actions, determination,
validation, query, alternative Keys in BOPF
object.
Course Title: SAP TM Technical

Module 3 : BOPF Consumer Implementation

 Module 3: Objectives

At the completion of this chapter you should be able to: Service Manager
Method Description
QUERY Search, execute a BO query.
RETRIEVE Read data for a given set of node
instance keys.
RETRIEVE_BY_ASSOCIATION Read data via association.
DO_ACTION Execute a given action of a BO
node.
CONVERT_ALTERN_KEY Convert an alternative key to the
technical key.
MODIFY Create, change and delete BO
node instances
Module 3: BOPF Implementation >
Transaction Layer
Transaction Manager
Provides methods to save & exit, save & continue or cleanup the current transaction
Collects all changes, which are done within the current transaction(thus the
architectural layering must be strictly obeyed)
Checks, if the cross business object calls are valid at all (e.g. calling an action of
BO2 out of a check implementation of BO1 is forbidden)
Is only used by the consumer and never out of a BOPF entity implementation

Service Manager
Provides methods to access a business objects service layer methods
Can be used both by the consumer and out of a BOPF entity implementation (to
access a foreign BO)
 Module 3: BOPF Implementation >
Service Manager
Service Manager Factory
Service Manager provides an object oriented interface to query BOPF business
Object.
Provides get_service_manager( iv_bo_key ) to receive a service manager instance
for a certain business object
Ensures, that there is always only one service manager instance for each business
object
Can be used both by the consumer and out of a BOPF entity implementation (to
access a foreign BO)
Module 3: BOPF Implementation >
BOPF Architecture
Module 3: BOPF Implementation >
TSM and BOPF
Module 3: BOPF Implementation >
Consumer, TSM and BOPF
Module 3: BOPF Implementation >
Query Definition

A query is a business object entity and is always assigned to a certain node, whose
instances shall be returned
The consumer is able to query either only the keys or the whole data of the resulting
node instances
Queries never modify any node instance data*
There are three types of queries:
Node Attribute Query
Custom Query
Generic Result Query
 Module 3: BOPF Implementation >
How to Use Query
A business object can be accessed via a so called Service Manager. The following
coding shows how to get an instance of the service manager for e.g. the business
object TOR
Module 3: BOPF Implementation >
How to Call Query
 Module 3: BOPF Implementation >
Retrieve
Retrieve is used to fetch the data for a specific node single or multiple
Below coding example shows how to retrieve the data for the Root node keys that
were found by the query. Method RETRIEVE of the service manager instance is
used.
Module 3: BOPF Implementation >
Retrieve By Association
Retrieve by Association is used to retrieve the data of another node using the
association
Below coding example shows how to retrieve the data for the Item node keys that
were found by the earlier query. Method RETRIEVE_BY_ASSOCIATION of the
service manager instance is used with the composition association from Root to Item
 Module 3: BOPF Implementation >
Retrieve By Association
Retrieve By Association (XBO)
The coding example shows how to retrieve the data for the Locations stored in the
items whose Item node keys were retrieved in above code`. Again, method
RETRIEVE_BY_ASSOCIATION of the service manager instance is used with the
Cross BO association (XBO) from Item to Source Location Root that is defined on
the item node of BO TRQ: Retrieve By Association (XBO)
 Module 3: BOPF Implementation >
Convert Alternate Key
Below coding example shows how to convert a list of TRQ IDs into the
corresponding Root node keys. Method CONVERT_ALTERN_KEY of the service
manager instance is used.
 Module 3: BOPF Implementation > Do
Action (Standard)
Coding example shows how to start an action for a given set of TRQ instances
represented by the corresponding Root node keys. The action CONFIRM of the TRQ
Root node is called:
Module 3: BOPF Implementation > Modify

While the coding examples of the previous sub sections demonstrated how to access
BOPF business objects, we now take a look at how to create, update and delete BO
(node) instances. For these purposes, method MODIFY of the service manager is
used. To demonstrate different possibilities of the method,
Module 3: BOPF Implementation > Modify
Module 3: BOPF Implementation - Takeaway

All the participants now, should be able to:

Understand Service Manager and Transaction
Manager
Use Service Manager and Transaction manager
to retrieve, query data, perform action, convert
alternative Keys.
Module 4: TM UI FPM & FBI

Course Title: TM Technical

 Module Objectives

At the completion of this chapter you

should be able to:
Understand SAP TM UI
What is FPM and FBI
Create new UI using FPM
Enhance standard UI
 TM UI Overview : Agenda

Topic 1: UI Overview FPM and FBI

Topic 2: UI Components - UIBB
Topic 3: FBI View and View-Exit
Topic 4: Building a TM UI (Case Study)
Topic 5: Enhance existing UIBB
Topic 6: View-Exit Functionalities
 Module 4: TM UI Overview > FPM

FPM Floor Plan Manager (FPM) is a Web Dynpro ABAP application that provides a framework for developing new
Web Dynpro ABAP application interfaces consistent with SAP UI guidelines.
In SAP TM, FPM is used to design all the UI screens for the various business functionalities
 Module 4: TM UI Overview > FPM and FBI
FBI FPM BOPF Integration
Module 4: TM UI Overview > Why FBI and FPM

BOPF and FPM-FBI perfectly fits

Common way of implementing UI across systems
Avoidance of duplicate coding
Framework supports fast implementation of UIs
Enhancements concerning UI functionality are centrally implemented
Deep knowledge of Web-Dynpro skills not needed
Module 4: TM UI Overview > UIBB

UIBB User Interface Building Blocks

UIBBs are the interface views (Web Dynpro ABAP windows) that are provided by
the external application and not by FPM itself.
UIBB are also Web Dynpro components by themselves.
An UI view would have multiple UIBB windows associated with it
Any UIBB will have multiple implemented Web Dynpro component interfaces like
IF_FPM_UI_BUILDING_BLOCK
FORM, LIST, TREE & TABBED are some of the most used UIBBs.
 Module 4: TM UI Overview > UIBB
FORM UIBB

LIST UIBB
 Module 4: TM UI Overview > UIBB

TREE UIBB
 Module 4: TM UI Overview > UIBB

TABBED UIBB
Module 4: TM UI Overview > BO Layer, FPM and FBI
Module 4: TM UI Overview > Identify UI Component

Open any UI Screen (Example : Forwarding Order or Forwarding Agreement)

Identify UI Component Right-Click and select Technical Help on any UI screen

LIST UIBB Component FPM_FORM_UIBB_GL2

Component Configuration /SCMTMS/WDCC_TCM_TBO_GENDATA
 Module 4: TM UI Overview > Component
Configuration (WDCC)
The component details are shown on clicking component configuration
 Module 4: TM UI Overview > Field Groups
Fields in the FORM UIBB are divided into groups
Module 4: TM UI Overview > UIBB Feeder Class

Each UIBB Component Configuration needs to have a feeder class

 Module 4: TM UI Overview > UIBB Feeder Class
Parameters
The feeder class parameters would provide the BO name &node or the FBI view
 Module 4: TM UI Overview > Important Feeder
Classes

FBI Feeder Classes for Main Screen UIBBs

Forms : /BOFU/CL_FBI_GUIBB_FORM

Lists : /BOFU/CL_FBI_GUIBB_LIST

Trees : /BOFU/CL_FBI_GUIBB
 Module 4: TM UI Overview > Initial Screen

Feeder Classes for initial screen

Alternative Key: /BOFU/CL_FBI_GUIBB_ALTKEY_FDR
Bootstrap: /BOFU/CL_FBI_GUIBB_BOOTSTRAP
 Module 4: TM UI Overview > Wiring
Wire Connectors are used to pass the instance key from the preselection screen to the bootstrap and from the bootstrap
to the FBI Controller / Main Screen
 Module 4: TM UI Overview > FBI View

FBI View is the most important parameter of a generic FBI feeder

Specifies with which node the data exchange should occur
Specifies UI Structure
Specifies how the data is to be converted between BO and UI
View Mapper class (Conversion class) - /SCMTMS/CL_UI_CONVERSION
Specifies how the data is to be adjusted during roundtrips
Exit Interface class (View Exit class) - /SCMTMS/CL_UI_VIEWEXIT_CMN
Specifies Field Descriptions and Field Groups
Specifies Actions (UI and BOPF Action)
Related Views can be used to include data of related Nodes
Component
/BOFU/FBI_VIEW
Module 4: TM UI Overview > FBI View
 Module 4: TM UI Overview > UI Structure
To define the fields that will be available to be displayed on the screen for a given BO Node Example : UI Structure
for FREIGHTAGREEMENTROOT

UI Structure needs a Key of type /BOBF/CONF_KEY (for internal processing) along with the necessary fields
UI Structure can have display-only fields. Such fields can be populated using mapper or view-exit classes
 Module 4: TM UI Overview > View Exit Class &
Mapper Class
View Exit: Provides various functionalities for handling the UI fields hiding fields or making them read-only
Example - /SCMTMS/CL_UI_VIEWEXIT_TBO

Mapper Class Helps in field conversion and mapping values.

Example - /SCMTMS/CL_UI_CONVERSION_TRQ
Module 4: TM UI Overview > UI Architecture
 Module 4: TM UI Overview > UI Structure

Application Configuration a contained for Component Configuration

Component Configuration : FPM_OVP_COMPONENT
Pages Overview Pages
Toolbar
Section
UIBBS
Wires
 Module 4: TM UI Overview > UI Structure

UIBB are components in itself

Form UIBB : FPM_FORM_UIBB; FORM_WINDOW
List UIBB : FPM_LIST_UIBB; LIST_WINDOW
Tree UIBB : FPM_TREE_UIBB; TREE_WINDOW

Each UIBB needs to be configured which is Component Configuration in itself

 Module 4: TM UI Overview > Overview Page

Contains
Identification Region
Main Toolbar
Content Blocks
Wiring of Content Blocks
Other Content Areas like Initial Screen, Edit Pages etc

Special FBI View Handles Main Toolbar

Special TM Class sets IDR
Module 4: TM UI Overview > UI Customization /
Personalization

In most cases we would need to make changes to standard UI screens. The

requirement can be for example
Add a new custom field
Add a new custom tab.
Remove a standard field
Make a standard field read-only

Before changing an existing UI configuration, we need to customize the component.

There are multiple ways to actually customize a component.
Module 4: TM UI Overview > UI Customization /
Personalization

Method 1 :
- Launch Web Dynpro Application CUSTOMIZE_COMPONENT (Add as a short cut to your user menu)
- Provide the Component Name and Configuration ID
- Click on New and proceed

Method 2 :
- Configuration editor or customizing editor can be found via UI screen. Go to the Technical Help menu - --
context by right click in the UI.
- Click on Customizing Link
Module 4: TM UI Overview > UI Customization /
Personalization

Identify the UI Component to be Customized

UIBB Component Configuration - /SCMTMS/WDCC_TCM_TBO_GENDATA
UIBB Component -FPM_FORM_UIBB_GL2
Module 4: TM UI Overview > UI Customization /
Personalization
Existing Fields can be removed or new fields can be added in this list view
Property of existing fields can be changed example : text-view to input field
Also we can add new groups of fields
 Module 4: TM UI Overview > Adding New Fields

Ensure that the field is already present in the UI Structure

Adding the field to the persistent or transient includes for the corresponding BOPF
node does not necessarily add the field to the UI structure
 Module 4: TM UI Overview > Field Property

Field Property help in assigning the display attributes of a field

Module 4: TM UI Overview > Adding Buttons

Buttons can be added to Toolbars by adding a new Toolbar Element

Buttons need to be linked to Actions BOPF or UI Action
Module 4: TM UI Overview > View Exit Functionality

View-Exits provides enhancement options like :

Make a standard or custom field read-only / editable / hidden
Make a toolbar button read-only / editable / hidden
Populate values for a drop-down field
Provide confirmation popup for any actions
Handle logic for any UI action or event example navigating to new transactions

The necessary methods are enhanced by pre-exit or post-exit methods (enhancement

framework)
Module 4: TM UI Overview > View-Exit : Make
Field Read-Only
Method /BOFU/IF_FBI_VIEW_EXITINTF_RUN~ADAPT_DATA can be used to achieve this
functionality

The logic should be restricted for the specific BO and node and if necessary further transaction level value
filters
 Module 4: TM UI Overview > View-Exit : Make
Field Invisible
Method /BOFU/IF_FBI_VIEW_EXITINTF_RUN~ADAPT_FIELD_PROPERTIES can be used to achieve this
functionality

The logic should be restricted for the specific BO and node and if necessary further transaction level value filters
Module 4: TM UI Overview > Retrieve Node Data
For most scenarios, we may need to read the single or multiple node data inside the
view-exit methods

Sample Code to retrieve node data

Root Key retrieval inside a Item Node

Logic
Module 4: TM UI Overview > Button enable / disable

The button (action) can be enabled / disabled / hidden using method

/BOFU/IF_FBI_VIEW_EXITINTF_RUN~ADAPT_ACTION_PROPERTIES

Generic codes to hide or disable a

toolbar button (action)
 Module 4: TM UI Overview > Dynamically
Change Button Text

The text for a button (action) can also be changed inside the method
/BOFU/IF_FBI_VIEW_EXITINTF_RUN~ADAPT_ACTION_PROPERTIES
 Module 4: TM UI Overview > View-Exit : Event
Handling
Method /BOFU/IF_FBI_VIEW_EXITINTF_RUN~ADAPT_EVENT can be used to handle action
specific validations or making calls to new transactions
The current event is checked via parameter iv_eventid

Handling Create FWO

Action for FAG Item
Module 4: TM UI Overview > View Exit : Additional

Method
/BOFU/IF_FBI_VIEW_EXITINTF_RUN~ADAPT_NEEDS_CONFIRMATION can
be used to provide confirmation popup on clicking any action.

Method /BOFU/IF_FBI_VIEW_EXITINTF_DEF~ADAPT_FIELDS can be used to

dynamically change the display text for a field in a form view.