Please note in this scenario I have shown from the POWL example. This OBN configuration is applicable to all OBN configuration in Portal.
We have copied the standard iViews into our custom folder and created a role to launch a Maintenance Tasks iview.
We are able to display it fine. however, when we select any notification and click on the buttons such as change notification/display notification, it doesn’t display the respective iView’s in new window, as it generally does in the standard role/iview.
It displays an error message saying “There is no iView available for system “SAP_ERP_Manufacturing”: object “notification”. For more information, contact your administrator.”
In the below example on POWL screen select notification created by User link (Called Query).
Select any notification(in table row) and click on say, Display Notification button, below error messages pops up.
scenario may vary based on our requirements. Another exmample navigating from one webdynpro application to another webdynpro application.
Even though we copied the standard iview to our custom folder, the iview doesn’t have the OBN properties copied and configured. We have to manually add the business operation to the OBN Business object.
Step by step procedure
Process Flow of Business Object and Business Operation in OBN
- User Logins in to Portal with User ID and access the assigned Role
- Access the assigned Application(In this case POWL application).
- Click on the appropriate action Button on Application (POWL)
- iView/ Page linked to BO Operation is triggered
Procedure to add the iView as Source and Targets in OBN:
- Adding Application as OBN Source:
Add business object operations that this iView activates at runtime. You can add operations automatically, if you check the iView runtime by choosing Check Source iView; or you can add operations manually from the Portal Catalog.
Here, we have the iview/application(POWL), which is the OBN source. From this iview, we would launch other iViews upon Action/Button.
- Adding Application as OBN Target
Current iView/page opens upon activation of the following business object operations
Here we create the Business Operation, by selecting the Business Object, Operation it would perform and System Alias defined.
Above fields selected are from standard Operations that we have under ERP Common Parts folder, in manufacturing folder
PCD path: Business Objects – ERP Common Parts – Maintenance Management – Maintenance Notification – select the operation that you want to activate.
We use standard business object that’s in the ERP Common parts folder as per the iview we want to launch, as the Business Object of Target iview.
This business object and operations we need to read from feeder classes or from ECC where ever you required.
Code Snippet of reading BO from ECC:
ls_powl_follow_up–bo_system = <system alias>.
ls_powl_follow_up–bo_name = ‘maintenance_order’.
ls_powl_follow_up–bo_op_name = ‘change’.
ls_powl_follow_up–parameters = <Passing Parameters to target iview>.
Please comment if any further clarifications.