Mi contenido
Review our AI Community Guidelines before posting AI-generated or AI-assisted content. Verify accuracy and include the appropriate AI disclaimer.
Action Required: Review and submit pending reconciliation matches before the NetSuite upgrade to avoid rework. After 26.2, unsubmitted matches will be unmatched. For more details, see SuiteAnswers 1047397
Comentarios
-
Hi @User_APXUW I would not call any single formula universally correct. Two common interpretations: Sellable from stock you physically have now: ATS = On Hand − Committed (open SO) Here open POs are not included, since that stock has not arrived yet. This matches NetSuite's native Available field. Promisable including…
-
Hi @Keat Yee, Both are achievable, but neither is fully native, both need a User Event script on the Item Receipt. 1. Duplicate DO Number Use a beforeSubmit script that queries existing Item Receipts for the same DO number and throws an error if a match is found, blocking the save. A saved search alone cannot stop the…
-
Hi @Elina Kourouzidou, Sourcing will not work for this, because the Requisition to PO link is not stored in a sourceable field on the PO. When you create a PO from a Requisition, the relationship is kept in NetSuite's internal transaction link table (nexttransactionlink), which is what drives the Related Records subtab. To…
-
Thanks for sharing @Jeanne Padilla-Oracle.
-
Thanks for sharing @Francesca Nicole Mendoza-Oracle.
-
Yes, you can handle that in the script. Instead of reading one fulfillment, search all Item Fulfillments linked to the originating Sales Order, then loop through them and collect serial numbers from each one's inventory detail, skipping any that have none. The logic: from the invoice line get the source Sales Order, search…
-
Hi @TheCrawford, The reason your template edits are not working is that the serial numbers do not actually exist on the invoice line. When the invoice is transformed from the Sales Order, the inventory detail (where serial numbers live) does not carry onto the invoice line, so ${item.inventorydetail} has nothing to render.…
-
Hi @Kevenale, The account depth (4000 > 4001 > 4004) is driven by the actual account parent-child structure, and the Financial Report Builder always renders every level in that chain. The layout editor controls sections and summary rows, but it cannot flatten the GL hierarchy, so there is no native way to show CEN >…
-
Great feature, @Niña Camille G. Paule-Oracle. Having the full transaction lifecycle (fulfillments, invoices, payments, returns) surfaced in one AI summary should save a lot of time when checking where an order stands. Thanks for the clear walkthrough.
-
Thanks for sharing this @Ivy Lopez-Oracle
-
Thanks for sharing this @Ivy Lopez-Oracle
-
Hi @User_8LGY2, This is by design. The Match Bill to Receipt checkbox is an item-level field that only appears on item types received through an item receipt, like inventory items. You can see it on the Inventory Item record under Item/Cost Detail (next to Drop Ship and Special Order), but it does not exist on the Service…
-
Hi @Dext3r, Solid setup, Sam. The queue pattern where the UE just drops a lightweight record and the MR/SS does the real work is a good way to keep load off the UE and client side. Reusing the same model for the ecommerce integration makes sense to me. One thing if you have SuiteAnalytics Connect you could push some of the…
-
Hi @kees.netsuiteadmin As far as I know, there is no out-of-the-box way to achieve this. For what you need, a custom solution is the way to go. The approach would be a Suitelet based item search page that reads the current user's department from their employee record and filters the item results to only those relevant to…
-
Hi @User_APXUW, The native quantity fields (On Hand, Committed, Available, On Order) will not give you a true ATS, since Available is only On Hand minus Committed and does not factor in incoming POs or transaction dates. For future-dated supply and demand, NetSuite's Available to Promise (ATP) feature is the native route.…
-
Hi @User_IM2YY, This error comes from the Transaction Line Distribution SuiteApp (com.netsuite.vendorinvoicedistribution). On save, the fetchSubsidiaryDetails method runs a SuiteQL query that joins the Subsidiary, Customer, and Vendor tables to build intercompany details. This path triggers when the Intercompany feature is…
-
Very useful write-up @Jeanne Padilla-Oracle. The callout on period locking being driven by subsidiary time zone is an easy one to overlook, especially for distributed teams. Thanks for sharing.
-
Great breakdown @Richard James Uri-Oracle. Having Switch Company and All My Roles and Companies directly accessible from the role switcher is a nice improvement, especially for those of us working across multiple subsidiaries and roles. Looking forward to the rest of the series.
-
Hi @Elina Kourouzidou, To add some technical detail: this can be handled with a User Event afterSubmit script on the Vendor Bill, firing on create only. The logic: Read the createdfrom field to identify the source PO Use a transaction search with a File Fields join to get the file IDs attached to the PO Loop those and use…
-
Hi @Elina Kourouzidou, As other community member mention that native Purchases portlet does not allow reordering the PO and Requisition subtabs, as the tab order is hardcoded. To change the order, you would need a custom HTML Portlet Script that renders the tabs in your preferred order and add it to the Employee Center…
-
Hi @User_MZTGL, If you have administrator access, a good starting point before filing a support case is to check the following: Go to Customization > Scripting > Script Execution Logs and filter by time of the error. Also go to Customization > Scripting > Scripted Records and find the Sales Order record. You will see all…
-
Great roundup @Clarisa De Torres-Oracle. The Finance Analyst Skill for the AI Connector Service is a welcome addition for finance teams. Looking forward to SuiteWorld 2026!
-
Hi @Vishnu M Good solution from @Francesca Nicole Mendoza-Oracle. One thing worth noting though, even with this workflow in place, if users have access to the Saved Search feature, they can still create a search against the Vendor Bill record type and view bill data including amounts, vendors, and statuses directly from…
-
TRUE
-
Great write up @Richard James Uri-Oracle. The Get Started panel is a thoughtful addition, especially as NetSuite Next is shaping up to be the most significant platform overhaul in NetSuite's history. The interactive Show Me guidance directly addresses one of the biggest adoption challenges: helping users navigate a…
-
Hi @User_ZA0IY If you need this functionality now without waiting for the enhancement, a custom solution is possible but involves work across multiple layers: Frontend: custom SuiteCommerce extension for pickup location selection at checkout Backend: SuiteScript to handle location availability and inventory checks per…
-
Hi @Vishnu M, I think Inventory Items is the right approach for your scenario. It supports FIFO costing, quantity tracking, and value tracking out of the box. On the other item types: Gift Certificates track outstanding liability not physical quantity or cost, and each line is limited to a quantity of 1 so bulk tracking is…
-
Hi @ACVP Yes, this is doable with a Client Script. Use fieldChanged on the taxdetails sublist: On taxcode change: load the salestaxitem record, grab custrecord_ste_taxcode_taxrate, strip the %, and set taxrate with ignoreFieldChange: true. On taxbasis change: calculate taxamount = taxbasis * (taxrate / 100) and set it with…
-
Hi @Kevin Hosea, It looks like a budget record already exists in NetSuite for the same dimension combination (Subsidiary + Year + Account + Department/Class/Location), not that your CSV has internal duplicates. Have you checked in NetSuite is you already have one of the budget you are trying to import?
-
Thanks for tagging me here @Francesca Nicole Mendoza-Oracle Hi @User_APXUW For requirements 1-3 (creation permissions, Submit for Approval button, Approve button), a standard Workflow handles these cleanly using role based permissions, Set Field Display Type to lock the Approval Status dropdown, and workflow driven buttons…