You can implement an OBN that executes an application in a different target system. Therefore, if the OBN target that is to be launched resides in another system, use the same mechanism as described in Remote Systems . An example of this cross-system navigation scenario with static system definitions is an SAP Supplier Relationship Management (SRM) solution or an SAP Supply Chain Management (SCM) solution that wants to navigate to an SAP Enterprise Resource Planning (ERP) system to display a specific business document. In this case, for the ERP-based application that is to be executed in a different system, change the Target System field to refer to the remote host. For more information about handling transactions that are not locally known, see 5.11 Remote Systems .
Another example: Advanced Planning and Optimization (APO) is the leading system for planning. There could be multiple ERP systems providing different documents, such as sales order, production order, and so on. Each document in APO stores the information of the logical system to which the original document belongs. For cross-system navigation from APO to ERP to see all the details of the original document (for example, 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 already needs to be defined 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. For more information about dynamically determining the target system, see Dynamic System Target for OBN .