Scribd
Upload
31 views7 pages

Bopf (Document)

Uploaded by

srsatapathy087
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
31 views7 pages

Bopf (Document)

Uploaded by

srsatapathy087
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

BOPF - Business Object Processing Framework

BOPF is a framework for working with the BO (Business Objects). This


framework provides tools and services for entire BO life cycle. BO is a
representation of a type of uniquely identifiable business entities described by a
structural model, an internal process model, and one or more service interfaces.

Important transaction codes:


BOBF -> Business Object Building Framework, it’s not Bopf.
BOB -> Business Object Builder
BOBT-> Bo Test
BOBX -> Business Object Enhancement Workbench

Architecture:
TCode -> BOBF
How to create business object in bopf:
Tcode -> bob
Goto se11->create structure(based on any table . like(vbap) ->
activated -> goto bob -> click custom business object ->pop up
will appear-> click continue-> give name in prefix value and
give name for name and short des->continue->constant interface
name automatically will appear->give persistent structure name
(already u created one ) or ( here also click on persistesnt name
it will navigate structure name) ->continue-> root node and data
base type name will appear->continue->completed.

Extensible :
An indicator to define whether a node can be extended.
Transient :
An indicator to define if a node is transient.
Use:
This indicator can be used to define if a node is stored in the
database or some other persistency.
Types of nodes :
1) Standard node
2) Delegated Node
3) Businees object representation nodes
Types of Node elements :
1) Actions
2) Determinations
3) Validations -------a) Action validation , b) Consistency
validation
4) Association
5) Queries
6) Alternative keys
Actions :
Explicitly we have to call the actions.
Determinations:
Whenever we made changes in node instance ,it will trigger
automatically in determination.(Implicitly it will trigger based
on node changes.)
Types :
a) Transient determination
b) Prescient determination
Difference between determination and validation
Determination -> We can do curd operation(create , modify
, delete and read) and validation also.
Validation --- We cant do curd operation but we can
validate the fields based on 2 ways.
a) Action Validation -- It will trigger based on action
name.
b) Consistency validation -- After determination it will
trigger (this validation).
Association:
It is relationship between two nodes.
Uni-directional ------- Root to item
By-directional--------- root to item and item to root.
Note : We can insert the data two data base table using of
association
Queries :
It is used to retrieve the data based on custom queries or
standard queries.
a) Node attribute query
b) Custom Query
Difference between retrieve and query:
Retrieve -- Fetching data from buffer.
Query-----Fetching data from data base table

Query Category:
a) Modeled Query -- Node Attribute Queries
Node attribute queries are modeled queries whose logic is defined within the
BOPF runtime. These simple queries can be used whenever you simply need to
search for BO nodes by their attributes (e.g. ID = ‘12345’).

b) Implemented Query
Writing custom logic only implemented query.

Query import/export parameter:


IS_CTX -- Provides the context information of a query (BO key, key of
root node, key of assigned node, …)

IT_FILTER_KEY --(Optional parameter) Table with keys for a


limited set of node instances that are to be affected by the query execution. When
this optional parameter is used, the service consumer is able to specify a type of
filtering.

If this parameter is empty, all node instances (that are assigned to the query) are
affected by the query.

IT_SELECTION_PARAMETERS---- Represents a range table of


attributes of the query filter structure.Using this parameter, you can specify (limit)
a value range for dynamic query selections.

IO_QUERY---Represents the query object that allows execution of the


query.

IO_READ-----Provides read access to the data of business object instances

IO_MODIFY ---Provides write access to the data of business object instances

IV_FILL_DATA---
Indicates that the node data is to be read. If true, ET_DATA holds the read node data -
including all attributes. If false, only the attribute key is returned in table ET_DATA .

You might also like