Hardware recommendations and software prerequisites - HxGN SDx - v10 - Installation & Upgrade - Hexagon

HxGN SDx Connector for Plant Maintenance Installation and Configuration

Language
English
Product
HxGN SDx
Subproduct
HxGN SDx Connectors
Search by Category
Installation & Upgrade
SmartPlant Foundation / SDx Version
10
  • The interface must be installed and configured in SAP. For more information about the Jump interface for SAP, refer to the Asset Information Link for SAP guide delivered with the installation package.

  • The custom tables for interface configuration are delivered with SAP installation packages. These tables must be configured in SAP according to the input from the HxGN SDx or SPO/E Core team:

    • /INGR/PLNTMAPP_V or /INGR/SCOPEMAP_V

    • /INGR/API_PARM_V

  • An administrator must provide an Excel file with API calls to the SAP basis team, which is the same as the custom tables in SAP:

    • The Excel file is delivered within the product installation folder. It is located at:

      • For HxGN SDx: [Installation drive]:\Program Files (x86)\SDx Connectors\HxGN SDx Connector for Plant Maintenance\SDx Connector for Plant Maintenance_SDx\Installation Materials_SDx\Example Objects\Exemplary Excel file for SAP Tables Configuration

      • For SPO/E Core: [Installation drive]:\Program Files (x86)\SDx Connectors\HxGN SDx Connector for Plant Maintenance\SDx Connector for Plant Maintenance_SPO\Installation Materials_SPO\Example Objects\Exemplary Excel file for SAP Tables Configuration

    SHARED Tip The Excel file is also available on Smart Community. You can download it from the website.

    • The API calls that are listed in the Excel file are only for reference. The administrator must identify and test them on Postman before sending them to the SAP team.

    • The tabs in the Excel file provide information corresponding to different tables in SAP.

  • The HxGN SDx or SPO/E Core Services must provide the list of API calls in the required format to the SAP basis team.

  • Bi-directional communication on port 443 (it requires IT support to set up the connection).

  • Token Request supports Resource Owner and Client Credentials Authentication flows.