Business Client and OBN
The portal
Object-Based
Navigation (OBN) is used for indirect navigation in the Business Client.
Object-based navigation is a role-based navigation technology that is
controlled through processes and
Business Objects
from the Business Object Repository (
BOR). The object
model of the BOR provides a description of all business objects, their
methods, and their parameters. The BOR with all its relevant transactions
(especially SWO1) is used exclusively as a data store. Note that BOR objects
are never started or triggered by the Business Client.
The semantic business objects of the BOR are mapped to the available transactions, which are configured using Role Maintenance. This is done using a table integrated in the PFCG, through which the mapping data together with the roles can be transported.
Depending on which role different users are assigned to, they can be routed to different applications in the same navigation call.
The procedure is as follows:
...
If required, you have to Redefine the methods Display and ExistenceCheck.
2. Define OBN
Example
You want to define a navigation with enables the user to press a button and go from a vendor selected in a list to the analysis data for this vendor's account.
Starting Point
Finishing Point
1. Business Object
You are using business object /KYK/VEND, which is available in the system, and its methods and parameters.
Business Object /KYK/VEND in SWO1
Methods of /KYK/VEND
For OBN use method KYK_MM_VENDOR.Analyze_Account.
Parameters of Method KYK_MM_VENDOR.Analyze_Account
2. PFCG Role
3. You assign the Web Dynpro ABAP application /KYK/A_FK10_01 (analyze vendor account) to the role SAP_KYK_AP_CLERK-S in the menu.
4. You assign the business object to the menu entry, assign the priority, and specify parameter values.
3. NWBC OBN
If you now go to the vendor list in the Business Client, and want to go to the account analysis data for vendor 100015 with company code BP01, the method IF_WD_PORTAL_INTEGRATION~NAVIGATE_TO_OBJECT is called. This method has the following import parameters:
Parameters of NAVIGATE_TO_OBJECT
Parameter |
Typing |
Reference Type |
Default Value |
Description |
SYSTEM |
Type |
STRING |
|
System that defines the business object |
OBJECT_TYPE |
Type |
STRING |
|
Type of the triggering object. |
OBJECT_VALUE_NAME |
Type |
STRING |
'objectValue' |
Name of the object value |
OBJECT_VALUE |
Type |
STRING |
|
Value of the object |
OPERATION |
Type |
STRING |
|
Business object operation to be performed |
BUSINESS_PARAMETERS |
Type |
WDY_KEY_VALUE_LISTGEN |
|
Parameter list, for example, customerID=4711 for target application |
FORWARD_OBN_METADATA |
Type |
ABAP_BOOL |
ABAP_FALSE |
TRUE if the metadata for the OBN is forwarded |
USE_FORWARDPARAMETERS_OF_AL |
Type |
ABAP_BOOL |
ABAP_FALSE |
|
RESOLVING_MODE |
Type |
STRING |
CO_RESOLVING_MODE-SOURCE_ROLE |
Mode for resolving the roles |
The following assignment is made in parameter BUSINSS_PARAMETERS:
Key |
Value |
Company_Code |
BP01 |
POWL_QUERY |
… |
vendor |
0000100015 |
As shown above in the screen shot for the finishing point, the user is taken to the creditor analysis with the defined values.
This accords to calling the associated Web Dynpro application /kyk/a_fk10_01 with the parameters COMPANY_CODE=BP01&VENDOR=0000100015:
More information: