We have Inventory Item Location Quantity, Inventory Snapshot modules in NSAW where Analytics Currency isn't yet enabled. Before we enable it, want to understand the decision points properly rather than guess. * What conversion date options are typically available per module (transaction date vs. period-end date), and what's the practical impact of each? * We have exchange rate type options :average, current, historical, how do people typically decide which to use per module? * Is this a one-time, hard-to-change decision, or can conversion settings be adjusted later without a full rebuild? * Any lessons learned from others who set this up — what would you do differently? Environment: NetSuite multi-subsidiary, modules: Inventory

Hi @User_5NVEC , For these two modules, I would not treat Analytics Currency as simply a reporting/display option. There are a few implementation considerations to validate before enabling it. 1. Conversion date For Inventory Item Location Quantity and Inventory Snapshot, Oracle's NSAW documentation identifies the Work Order Date as the exchange-rate date basis. Therefore, I would not assume that you can independently choose between transaction date and period-end date for these subject areas. The date basis is part of the NSAW subject-area implementation. This is particularly important for Inventory Snapshot, since the snapshot date and the currency conversion date are not necessarily the same concept. 2. Exchange Rate Type NSAW supports the following Analytics Currency exchange-rate types: * Current * Average * Historical * Per Account As a general guideline: * Current – generally appropriate for balance-sheet/inventory-type balances where an ending rate is required. * Average – generally used for income-statement activity over a period. * Historical – generally used for equity/historical-value accounts. * Per Account – allows the rate type to follow the account configuration. For Inventory Item Location Quantity and Inventory Snapshot, I would have Finance confirm the required valuation methodology before selecting the rate type rather than choosing based solely on which value happens to reconcile most closely. 3. Can the configuration be changed later? I would not treat the Analytics Currency configuration as a simple workbook-level setting that can be freely changed later. It is part of the NSAW modeled metrics/configuration. Therefore, I recommend confirming the following with Finance before enabling it: * Required reporting/analytics currency * Exchange Rate Type * Expected inventory valuation methodology * Whether the resulting values need to reconcile with NetSuite consolidated reporting If the configuration needs to be changed after implementation, I would confirm the impact with Oracle Support before making the change rather than assuming it can be changed without a rebuild or data processing impact. 4. Recommendation / lessons learned Before enabling Analytics Currency, I recommend testing a few representative scenarios: * Select subsidiaries using different currencies. * Compare the existing NetSuite inventory valuation against NSAW Base Currency. * Compare the proposed NSAW Analytics Currency result. * Validate the result with Finance. * Confirm that the selected exchange-rate methodology matches the organization's financial reporting policy. Also, Oracle recommends using an Exchange Rate Type filter when working with Analytics Currency metrics so that the rate being applied is explicit. For snapshot subject areas, Oracle also recommends using the Snapshot Calendar and Exchange Rate Type filters. One important point for this specific use case: Oracle documents Work Order Date as the exchange-rate date basis for both Inventory Item Location Quantity and Inventory Snapshot. Therefore, if the requirement is specifically to calculate inventory value using a period-end exchange rate based on the inventory snapshot date, I would validate this behavior carefully before enabling Analytics Currency. Oracle documentation: * NSAW Subject Area Metric Details — includes Inventory Item Location Quantity and Inventory Snapshot. * NSAW Report Authoring Tips — Analytics Currency and Exchange Rate Type guidance. * NSAW Reference Guide — detailed subject-area and metric reference. * NetSuite Consolidated Exchange Rate Types — explanation of Current, Average, and Historical exchange rates. Bottom line: I would have Finance confirm the exchange-rate methodology first. For these Inventory subject areas, the documented conversion-date basis is Work Order Date, so that should be considered before assuming that Analytics Currency will provide a period-end inventory valuation.

Based on the current NSAW documentation, I would not assume that Analytics Currency automatically converts every monetary field in a subject area. For Inventory Item Location Quantity, the current Oracle Reference documentation lists the AC/BC/TC metrics as quantity measures such as Available Quantity, On Hand Quantity, Committed Quantity, etc. Average Cost and Available Value are not listed as Analytics Currency metrics. That distinction is important because the presence of an Analytics Currency (AC) folder does not necessarily mean that every numeric or monetary field in the subject area is automatically converted. For example: * On Hand Quantity → quantity, so currency conversion isn't applicable. * Average Cost → monetary rate/value, but it is not documented as an AC metric in Inventory Item Location Quantity. * Available Value → monetary value, but it is not listed as an AC metric for that subject area. Oracle does explicitly provide Analytics Currency versions of certain monetary metrics where they have been modeled. For example, the NSAW Reference includes Analytics Currency metrics for certain Inventory Insights measures. This suggests that the conversion is applied to specific Oracle-modeled metrics, rather than automatically to every amount column. For custom monetary fields brought in through Data Augmentation, I would take the same approach. I would not expect a custom amount field to automatically participate in NSAW Analytics Currency conversion. Unless the custom solution explicitly implements the currency conversion logic, the amount should be treated as remaining in its source/base currency. I also would not recommend manually joining custom fields to internal NSAW exchange-rate tables unless Oracle provides a documented procedure for that specific use case. For the inventory valuation requirement, I would first check whether another delivered subject area, such as Inventory Snapshot or Inventory Insights, provides an Analytics Currency value that satisfies the requirement. This would be preferable to deriving an inventory value from Average Cost × Quantity if an Oracle-delivered metric is available. One additional point: Oracle documents Work Order Date as the exchange-rate date basis for Inventory Item Location Quantity. Therefore, if the requirement is specifically to calculate inventory value using a period-end exchange rate, that behavior should be validated before relying on Analytics Currency for the calculation. Oracle documentation: * NSAW Subject Area Metric Details * NSAW Reference Guide * NSAW Report Authoring Tips In summary: I would not consider Average Cost or Available Value to be Analytics Currency-converted simply because the subject area has AC/BC/TC folders. The current documentation only identifies specific metrics as Analytics Currency metrics, and Average Cost/Available Value are not listed for Inventory Item Location Quantity. For custom Data Augmentation amount fields, the currency conversion would likewise need to be explicitly designed rather than assumed to happen automatically.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Child Item

Ask A Guru

Child Item

Enabling Analytics Currency across modules — conversion date & exchange rate type guidance?

User_5NVEC

We have Inventory Item Location Quantity, Inventory Snapshot modules in NSAW where Analytics Currency isn't yet enabled. Before we enable it, want to understand the decision points properly rather than guess.

What conversion date options are typically available per module (transaction date vs. period-end date), and what's the practical impact of each?
We have exchange rate type options :average, current, historical, how do people typically decide which to use per module?
Is this a one-time, hard-to-change decision, or can conversion settings be adjusted later without a full rebuild?
Any lessons learned from others who set this up — what would you do differently?

Environment: NetSuite multi-subsidiary, modules: Inventory

Find more posts tagged with

NetSuite Analytics Warehouse (NSAW)

Component react.asset.answerThread had an error.

You are not allowed to view comments.

Child Item

Upcoming Events

SuiteWorld | October 25–28, 2026 | Las Vegas
Big ideas. No travel required. SuiteWorld On Air brings the best of SuiteWorld directly to you. Stream keynotes live, access exclusive virtual content, and connect with the NetSuite community from wherever you are. Explore what's next for NetSuite, see AI innovation in action, and discover practical insights designed to…
Learning Lab | DC
Drive better outcomes with AI built into NetSuite Next Capital Hilton,1001 16th St NW, Washington, DC 20036 Join NetSuite experts for a free half-day event where you'll get a tour of NetSuite Next, explore AI-powered capabilities built into the platform, and learn practical ways to optimize NetSuite for your business. At…
Inside the Suite | DC
Take NetSuite Next for a hands-on test drive Capital Hilton, 1001 16th St NW, Washington, DC 20036 What to expect: Inside the Suite is designed for companies exploring modern ERP solutions. This event gives you the opportunity to experience NetSuite Next - the next evolution of NetSuite that brings AI directly into how…
What's Next for Product Companies with NetSuite
WEBINAR What's Next for Product Companies with NetSuite See how NetSuite Next uses AI to improve accuracy and protect margins Ask. Understand. Act. Use Ask Oracle to search, navigate, analyze business data, surface insights, get guidance, and take action using natural language—all through a single conversational…

More events