Here on the Azdan blog, we’ve written some posts that cover some of the core components of NetSuite and Planning Budgeting Cloud Service. We’ve covered in our previous posts, the best practices for integrating Oracle ERP fusion with Oracle Hyperion planning and budgeting, and the best dynamic method to load data in PBCS.

This Article by Azdan Business Analytics is a simplified quick guide that explains how to configure and execute the integration between NetSuite and Oracle Planning and Budgeting Cloud Service (PBCS). If you are seeking a complete integration detail, Azdan’s consultants recommend taking a look on Oracle Data Management guide available from the Oracle documentation library.

If you are not familiar with the knowledge of NetSuite as well as PBCS. No worries! Feel free to contact us anytime, Our consultants will give you a hand in your integration process.

By the end of this post, you will be able to perform the following:

    • Categorize a Saved Search in NetSuite that may be selected for use in PBCS.
    • Import saved search definitions into PBCS.
    • Configure Data Management to use a NetSuite saved search as an integration source for PBCS.
  • Run the integration that extracts data from NetSuite and loads the target model in PBCS

1. NetSuite Saved Search Definition

First of all, you must apply the NetSuite bundle that enables the integration with PBCS.

This integration bundle comes with two predefined saved searches: “PBCS – Trial Balance” and “PBCS – Transaction Detail”, but users may create additional saved searches for any data in NetSuite they want to load into PBCS. When initializing the NetSuite source, Data Management in PBCS will surface any saved search created in NetSuite with customsearch_nspbcs as the prefix of the saved search ID. For example, the image below is the “PBCS – Trial Balance” saved search.

The ID must include the customsearch_nspbcs prefix, as well as additional criteria for the saved search. Each criteria defined for the saved search is available in PBCS. The user can set then set it as a runtime parameter when executing the saved search.

2. Source System Setup in Data Management

The first step to configure NetSuite to Data Management integration in PBCS is to create a source system entry in PBCS for NetSuite. Create a source system type of NetSuite in Data Management, and then provide the authentication details for the NetSuite source.

You can choose the authentication type to be user based, enter the integration account email, password, your NetSuite account ID, then test your connection.

After the source system connection is successfully tested, save the details and then initialize the source system. The initialization process will extract the saved search details from NetSuite, and create a target application entry in Data Management for each saved search.

When initializing the source system, users can specify an optional prefix to allow for duplicates or categorization. The application filters defined for a saved search are included in Data Management and users can edit these filters as needed.

Once the saved searches are pulled over from NetSuite, the remaining setup in Data Management is the same as any other source and target definition and is not specific to a particular source.

3. Import Format Definition in data management

The Import Format allows the user to map the columns from the NetSuite saved search to the dimensions in the target PBCS application. The user specifies the source, which is the desired saved search; the target, which is the PBCS application; and then maps the source columns to the target dimensions. If a source column is not available for a target dimension, the user can enter a default in the expression field in Data Management. Below is a sample Import Format:

4. Location Definition and member mapping

After the user creates an Import Format, they will create a location that includes an import format. The Location is the container for mapping rules and data load rules and drives the point of view for all integrations. The user may also specify the functional currency for the data that is being loaded. This is a very simple setup, and looks like the following.

Member mapping

Member Mapping is used to transform the source members to the target dimension members. In some cases, this is a 1-to-1 mapping where the source member is the same as the target, or the target is different, but there is still only a single target member. Mapping also allows the user to combine multiple source members to a single target member to summarize data across selected dimensions and members. For example, the source NetSuite system may have four cash accounts, but in PBCS, there may be only a single cash account defined. The mapping process allows the user to specify that the four cash accounts map to one cash account in PBCS. Another feature of mapping is to set a default for source dimensions that are not supplied by the NetSuite saved search. In PBCS, there is a version dimension, but this may not exist in the source. In this case, the user can define a mapping rule to set a default for the “Version” member. The following are examples of mapping rules defined in Data Management.

5. Data Load Rule

The Data Load Rule defines the processing details and is used to execute the integration process. The rule can be run manually from the UI, scheduled to run at a specific time, or called from EPMAutomate or the REST API. The user can also specify the saved search parameters in the data load rule to extract the desired data. The most important save search parameter is the period or date parameter, and there are a number of ways that the period selection is handled via the data load rule.

The easiest approach to loading data from NetSuite is to specify the date parameter in the data load rule, and then load the entire returned data set to the period defined in the Data Management point of view (POV). For example, the user may specify “Last Fiscal Year” as the date parameter for the saved search, and then “Dec-17” as the target period in Data Management. When the process runs, an entire year of data will be loaded into Dec-17. The setup in the Data Load Rule looks like the following:

For this type of rule, the “Period Mapping Type” of “Default” was selected which uses the predefined periods in Data Management. The results from the integration are as follows and show multiple source period IDs that will all be loaded to the Jan-17 period:

6. Conclusion

Data is easily extracted from NetSuite and loaded to a model in PBCS with Data Management and the various methods in regards to posting period specification. The two most important steps of the integration are the processing period selection and definition of the mapping rules that transform the source data to be successfully loaded to the target PBCS application.

Feel free to contact our consultants directly if you have any inquiry