Import Forecast, Planned Cost Totals (Operation) - EcoSys - Help - Hexagon PPM

EcoSys SAP Adapter Help

Search by Category
EcoSys Version


Import planned costs totals from SAP to EcoSys as transactions. These totals are pulled from the following SAP tables: COSS (secondary costs, internal costs) and COSP (primary costs, external costs)

Main inputs

  • Forecast type: Use PLANNED COST TOTALS for planned costs.

  • Version in EcoSys where forecasts are saved.

  • One or both of:

    • List of cost objects to import (external IDs).

    • List of cost object category values to import (matching root cost objects are included),

  • Include additional structures: Flag that indicates WBS elements only (False) or WBS, networks, network activities, activity elements, and work orders (True).

Optional inputs

  • SAP version: Specifies the VERSION value in SAP on which to filter. The default setting is to include all.

  • SAP ledger number, usually 00. Providing this value affords a performance gain as this field is part of database index.

  • Value multiplier (set to -1 if incoming revenue values are negative)

  • Commit batch size: Indicates the number of cost line items to commit in one API request when importing large projects from SAP to EcoSys. If nothing is specified, the default value 500.

  • Refer to Project/WBS Key Mappings section for details on how these elements correspond to each other.

  • If the fiscal year does not map exactly to the calendar year, the transactions imported to EcoSys may fall in the wrong financial periods. You can resolve this by shifting the costs by the correct offset to match the fiscal year start.



<parameter name="version">Current Forecast</parameter>

<parameter name="forecastType">PLANNED COST TOTALS</parameter>

<!-- <parameter name="sapVersion">000</parameter> -->

<parameter name="startDate">2000-01-01 00:00:00.000</parameter>

<parameter name="endDate">2060-12-31 23:59:59.999</parameter>


<parameter name="startCostElementRange">0000000000</parameter>

<parameter name="endCostElementRange">9999999999</parameter>


<parameter name="sapLedgerNumber">00</parameter>

<parameter name="commitBatchSize">500</parameter>

<parameter name="includeAdditionalStructures">true</parameter>

<parameter name="costObjectExternalIds">