Managing Periods in Oracle NetSuite

When loading periods from Oracle NetSuite, you have two options:

• Default Period Mappings—Use this option to load a single period from the POV from the data load rule. In this case, you do not map the period column in the import format or define a source period mapping in period mappings. You can set a source filter in the data rule such as the Current Period or Last period. For example, if you want to load the Feb 2018 period, you set it as the last period. When you run the data rule, periods are not checked and all the data you extract from Oracle NetSuite is imported into the selected POV.

• Explicit Period Mappings—Explicit period mappings enable the loading of General Ledger data when Oracle NetSuite and Planning periods match. Use this option to load multiple periods, or when you do not want users to select the period from the POV.

  To use explicit period mappings, you map the period column in the import format and define source period mappings. The General Ledger period column must match exactly the Oracle NetSuite period. Next in the data rule, you select the calendar from the period mapping. When you run the data rule, you specify the start – end periods that you want to load. You can set a filter condition in the data rule to extract specific period data, for example, the Fiscal Year Current to Fiscal Quarter Current period. Data Management matches the period column from the search result with the period in the period mapping and loads the data to the appropriate period.