Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Question of the Week! You only have until tomorrow, November 6, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Advanced Revenue Management: Fair Value Allocation Configuration
Hi all,
I am in the process of configuring the Fair Value allocation's side of Advanced Revenue Management for a customer whose FV allocations are different from the usual process in NetSuite.
In essence, the calculation would go something like this:
Step 1. Calculate the lower bound of the FV for the item
Step 2. Calculate what the Standalone selling price is for the item.
Step 3: Decision
If the price is above the lower bound then take the price as the FV amount.
If the price is below the lower bound, then take the Standalone selling price as the FV amount.
My understanding is that the module would be unable to handle the decision process in step 3. Has anyone come across an issue similar to this before?
0