Best Of

Hi @Paul Reading

1. Edit your Custom Entry Form.
2. Find the Maximum Quantity field (the row directly above) and check the SHOW box to temporarily make it visible.
3. This should "un-lock" the row for Enforce Minimum Quantity Internally.
4. On the Enforce Minimum Quantity Internally row, uncheck the SAME ROW AS PREVIOUS box.
5. You should now be able to freely check or uncheck the SHOW box for the Enforce Minimum Quantity Internally field.
6. Once you have it set to your liking, you can uncheck the SHOW box for Maximum Quantity again to hide it.
7. Save the form.

Hi @Angel mariya T. P.

NetSuite User Event (UE) scripts can trigger on matrix item records, but there are specific behaviors and potential pitfalls when creating or updating matrix parents and children. Matrix child creation often occurs as a background process during parent saves, which may not always reliably trigger UE scripts on the children.

Script Deployment Check

Deploy your UE script on the Inventory Item record type (internal ID: inventoryitem), as matrix items use this type for both parents (matrixtype: PARENT) and children (matrixtype: CHILD). Ensure the script is set to trigger on relevant events like beforeSubmit or afterSubmit for creates and updates—beforeLoad won't fire on new record creation.

Hi @User_56FCN,

The behavior you are seeing is standard NetSuite behavior for Work Orders (WOs) using Average Costing and Work In Process (WIP). It is caused by how NetSuite reallocates costs across partial completions to ensure the total WIP is cleared correctly by the time the Work Order is closed.

1. Why the 1st Completion Changed
   1. NetSuite uses a dynamic costing engine. When you created the 2nd Issue, the total cost pool for the Work Order changed. To maintain the "Average Cost" across the entire order, the system recalculated and updated the GL impact of the 1st Completion to reflect the new weighted average of all issued components.
2. Why the 2nd Completion has no GL impact
   1. This happens when the 1st Completion already cleared the WIP balance  available at that moment. If your Manufacturing Preferences are set to "Use Open WIP Amount," the system pulls all available WIP into the first completion it can. The GL impact for the 2nd unit often remains $0 until the Costing Engine finishes its background run or until the Work Order is Closed, which triggers the final "true-up."
3. Allocation Logic
   1. In a WIP-enabled environment, NetSuite treats the Work Order as a single "bucket" for costs. When you issue components, their value is moved from Inventory to the WIP Asset account. When a completion is saved, NetSuite attempts to relieve that WIP bucket to value the finished assembly. Because you are using Average Costing the system doesn't "lock" the cost of the first unit; instead, it constantly re-averages the total cost of all issued components across all completed units. If you complete a unit before issuing all components, the system may pull the entire current WIP balance into that first unit. Once the remaining components are issued, the costing engine redistributes that total pool across both units, which updates the GL impact of the first completion and often leaves the second completion with a $0 impact until the final Work Order Close clears the remaining balance to a variance account.

Hope this helps!

Hi @Didik_Rohadi

In NetSuite, you are completely correct: there is no native, header-level "Close" button for Requisitions like there is for Purchase Orders. The standard native behavior is exactly what you described—you must edit the record, check the "Closed" box on the item lines, and save.

The reason your custom workflow "Close" button didn't work is due to a conflict with your validation workflow. If your validation workflow uses an action like Return User Error on Before Submit to prevent users from saving changes to an "Approved" requisition, it will also block your custom workflow from saving the record when it tries to automatically check those line-level boxes. Workflows trigger other workflows!

Here are the two best ways to solve this problem so you get a working "Close" button while keeping the record safe from manual edits.

Solution 1: Use a Hidden "Bypass" Checkbox

To make your Close workflow work, you need to tell your Validation workflow to "step aside" just for this specific action. You can do this by using a hidden checkbox.

Step 1: Create a custom checkbox

1. Go to Customization > Lists, Records, & Fields > Transaction Body Fields > New.
2. Label it something like "Is Closing Requisition" (custbody_is_closing_req).
3. Type: Check Box.
4. Applies To: Requisition.
5. Display Type: Hidden. Save it.

Step 2: Update your existing Validation Workflow

1. Open your workflow that prevents edits on Approved requisitions.
2. Find the Action that stops the edit (usually a Return User Error action).
3. Edit that action and go to the Condition builder.
4. Add a condition: Is Closing Requisition = False.
   (This tells NetSuite: Prevent edits ONLY if the user isn't using our special Close button).

Step 3: Build your "Close Requisition" Workflow

1. Create a new workflow for Requisitions.
2. State 1: Add a New Action > Add Button. Label it "Close Requisition".
3. Create a Transition from State 1 to State 2 that executes On Button Click (select your "Close Requisition" button).
4. State 2: Add the following actions (Trigger On: Before Submit):
   • Action 1 (Set Field Value): Set the hidden Is Closing Requisition field to Checked (True). (This bypasses your validation workflow).
   • Action 2 (Sublist Action Group): Select the Item sublist.
   • Inside the Sublist Action Group: Add a Set Field Value action. Choose the Closed field and set it to Checked (True).
   • Action 3 (Go To Page): (Optional but recommended) Redirect the user back to the Requisition record so they see it is closed.

Thanks

Ramu

Hi Shelton, the Workforce Framework has not been yet being added to the Framework you are installing (last time I asked I was informed that maybe in Q1).

As we were having the same need as you, we got from NetSuite approval to download the Premium Suite Success Bundle, and we are working to integrate the Workforce rules and forms into our NSPB Financials so we can have the Workforce functionality adapted to our needs while it is officially added, but we are still in the process of making this work, as we are talking about integrating two different applications (the NSPB Suite Success and NSPB Financials).

This approach is not advisable if the Workforce "Framework" is soon to be launched, so better check with your NetSuite Account Manager.

If interested in knowing more about our approach, send me a DM.

Good luck.

Not sure which Chevron you mean or which page you're looking at, sorry. Can you share a picture?

Otherwise, the way I would try to solve this is by editing the audience of the Center Tab.
Customization > Centers & Tabs > Center Tabs
Just make sure you're looking at the correct Center Tab as sometimes there are multiple named the same but for the different Center Types used by the Roles.