Generic Object Services Configuration

With a minor amount of configuration, it is possible to allow user’s access to BDEx from any exception case or master data object via the standard SAP generic objects services (GOS). This means that when a user is within an exception case or displaying a master data object (e.g. a business partner) related transaction; they are then able to launch BDEx from the GOS menu available in the title-bar.

Once selected from the menu path, the user will be taken into the BDEx transaction passing through the context of the case, or master data object they were in.

To make this function available, add the following entry to standard SAP table SGOSATTR:

Once this is done, a reference to the new service must be added in the “Next service” field of the last item in the existing generic object services menu. This will be an entry with a blank “Next service” field currently, usually ESJI_GW_SUB in an unmodified system.

The generic object services linkage code is largely based on the BOR object bindings to master data and work requests (see the relevant chapters in this guide). If selecting the GOS menu item causes a “Linkage not found” error, this is likely due to missing configuration in these tables.