One approach, supported by the PFCG integration, could be to use business objects from the Business Object Repository (BOR) for the definition of the OBN interfaces. The object model of the BOR provides a description of all business objects, their methods, and their parameters. Use transaction SWO1 to look up the relevant information required. For more information, see the relevant links listed at 5 Role Maintenance in PFCG. In the context of NWBC, the calling application needs to know the interface and the names and possible values of the parameters. This is achieved by directly referencing BOR objects. Note: the BOR objects are only a design time construct to define the symbolic interfaces. At runtime there is no BOR involvement. Here the BOR business objects are purely used as a help in aligning onto standardized interfaces.

The use of BOR objects is optional; it is just a convenient repository of predefined interfaces that also includes parameter mapping. Alternatively, it is possible within PFCG just to configure a predefined set of values that have no relationship to an actual BOR object. The agreement on the specific symbolic interface to use is then handled within the development team and must only be documented. In this case, the following data must be known: the object name, the method name and the list of parameters with their value ranges. This information is then used to define the mapping onto the target application that must be called.