It is possible to implement an OBN that executes an application in a different target system. Thus, if the OBN target that is to be launched resides in another system, you have to use the same mechanism as described in chapter 5.10 Remote Systems. An example of this cross-system navigation scenario with static system definitions is an SRM or SCM solution wishing to navigate to an ERP system to display a specific business document. In this case, for the ERP-based application that is to be executed in a differed system, change the Target System field to have a reference to the remote host. Also see 5.10 Remote Systems for handling transactions that are not locally known.

Another example is as follows: Let APO be the leading system for planning. There could be multiple ERP systems providing different documents, such as sales order, production order, etc. Each document in APO stores the information of the logical system the original document belongs to. In case of cross-system navigation from APO to ERP in order to see all the details of the original document (e.g. VA03 for sales order), the logical system in the APO document is used to determine the correct ERP system for navigation. While setting up the PFCG role the target system needs to be defined already statically and cannot be set dynamically from the calling screen. Therefore, one possible solution could be that for every target system, the application needs to be added multiple times to the role, each time for every single ERP system that could be targeted with an OBN call. See also 5.11.7 Dynamic System Target for OBN for the possibility of dynamically determining the target system.