OBN Errors 

Object-based navigation (OBN) is a technology in which the calling application has no knowledge of the target application to be triggered. For example, assume that a pushbutton is named Buy Widgets. A different application may have to be called depending on the branch or country. The calling application calls the logical target widgets.buy. (The object is defined first and then the calling method.) The developer or solution manager who defined the specific role and placed the current application in the role in question is responsible for ensuring that at least one other application is available for the same role or for another role assigned to the user and is indicated as a target for the pseudo-call. The system only scans roles assigned to the user and starts the application indicated as the target for widgets.buy at runtime.

If this target is not found, this can be due to the following problems:

●      Configuration error

Not all relevant roles are assigned to the user and the OBN target being addressed is not visible in one of the roles assigned to the user. During runtime, the system is unable to find out which other roles should be assigned to the user, since this is always dependent on the application in question. The NWBC_LIST_OBN_TARGETS report can help here - it returns a list of all roles that contain a specific OBN target. You can then make the message available for the relevant application component for further processing.

●      Development error

The developer calls an OBN target that has never been defined. If this is the case, only the developer can solve the problem. The message must then be passed to the relevant application component.

You cannot solve this kind of OBN error on Business-Client side. The Business Client simply receives the request to trigger OBN. If there is no OBN target, the Business Client has no other way of knowing which additional roles are required or whether a development error exists.