1. Administering Data Management for Oracle Enterprise Performance Management Cloud
  2. Integrating Data
  3. Integrating Oracle NetSuite
  4. Process Description for Integrating Oracle NetSuite

Process Description for Integrating Oracle NetSuite

When Oracle NetSuite is used as a data source in the Oracle Enterprise Performance Management Cloud, Data Management uses the NSPB Sync SuiteApp Saved Search framework to query data from Oracle NetSuite.

A NSPB Sync SuiteApp Saved Search is a reusable search definition based on criteria and filters. For example, an NSPB Sync SuiteApp Saved Search might include all posting transactions to the General Ledger since the last period. Any kind of record in the NSPB Sync SuiteApp Saved Search can be included in or considered as the basis of a NSPB Sync SuiteApp Saved Search. A search can either be pre-packaged or user-defined. All balances are generated using transaction details that have been summarized.

When you create a new NSPB Sync SuiteApp Saved Search in Oracle NetSuite, you must include the prefix customsearch_nspbcs in the saved search id.

Note:

Data generated from the NSPB Sync SuiteApp Saved Search is used for importing data only, and not for write-back.

At a high level, these are the steps for loading data from an Oracle NetSuite data source:

  1. An administrator installs NSPB Sync SuiteApp Saved Searches, which is a shared bundle. Before you can install the bundle, it must be shared with your account.

  2. Perform the following tasks. (See the topics in the Oracle NetSuite Planning and Budgeting Cloud Service Sync guide for information on performing these tasks. Access to the guide requires a NetSuite login.)

    • You are required to have an Oracle NetSuite login to access NSPB Sync SuiteApp.

      For information on setting up the login, see the Oracle NetSuite Planning and Budgeting Cloud Service Sync guide.

    • Enable the required features in your Oracle NetSuite account. See "Required Features for Installing the NSPB Sync SuiteApp."
    • Install the SuiteApp. See "Installing the NSPB Sync SuiteApp."
    • Set the file encryption password. See "Setting Up a Password for File Encryption."
    • Create user records for EPM Cloud users. These user records must have an EPM Cloud Integration role. See "Creating a EPM Cloud User Record."
    • Set up token-based authentication for EPM Cloud users. See "Setting Up Token-Based Authentication."

    • Set up single sign-on (SSO). NSPB Sync SuiteApp Saved Searches supports single sign-on (SSO) through any SSO service that offers SAML 2.0. With an SSO account, users can navigate between NetSuite and Planning without entering their credentials each time. This enables users to navigate to the Create user records for EPM Cloud users. See "Setting Up Menu Navigation to Planning."

  3. In Data Management, register the source system with integration user credentials.

    This step includes specifying the connection details and the drill URL.

    See Configuring a Source Connection to Oracle NetSuite.

  4. Run the initialize process to import the definition of all saved search owned by the user.

    When you initialize the source system, Data Management imports all saved search definitions owned by the user. If you don't want to import all saved search definitions, you can go to target application and select individual saved search definitions one by one. If you have initialized the source system the first time, add incremental saved search definitions also in the target application.

    For more information, see Creating an Oracle NetSuite Data Source.

  5. Define the import format to map columns from the saved search to dimensions in the EPM Cloud application.

    For more information, see Adding Import Formats for Oracle NetSuite Data Sources.

  6. Once the initialization process is complete, you can pick a NSPB Sync SuiteApp Saved Search when adding a target application. When you select Oracle NetSuite as a data source, then you are presented with a list of the saved searches from the selected Oracle NetSuite source.

    You can also provide source filter criteria on the application filters tab. These source filters are the same as Oracle NetSuite "Criteria", which filter the data from the NSPB Sync SuiteApp Saved Searches.

  7. Define source mapping entries in the calendar mapping section to map the Oracle NetSuite periods to the EPM Cloud periods.

    Define any period mapping. Available options are explicit or default period mappings:

    For more information on periods mappings available for an Oracle NetSuite integration, see Managing Periods in Oracle NetSuite.

  8. In the Import Format, specify the NSPB Sync SuiteApp data source as the source application and your Planning application as the target application.

    For more information, see Adding Import Formats for Oracle NetSuite Data Sources.

  9. Define a location to indicate where to load the data.

    Each location includes an import format, data load rules, and data load mappings.

    For more information, see Defining Locations.

  10. Create data load mappings.

    For more information, see Data Load Mapping.

  11. Create a data load rule, apply any source filers, and execute the data load rule.

    This pulls the data from the Oracle NetSuite instance into Data Management, maps the data and then shows the results in the workbench. If the mapping succeeds without errors, the data is loaded to the target application.

    For more information, see Adding Data Load Rules for an Oracle NetSuite Data Source.

    For more information about applying filter criteria, see Applying Oracle NetSuite Application Filters.

    For more information about executing a rule, see Running Data Load Rules.