Yes, you can do that. Click on the Checklist Icon for the period you are trying to open Click on the Arrow icon on the last row of the "Go To Task" column Enter "Justification" and click the "Reopen Period" button Click "Ok" when you get the "Reopening will mean reopening all subsequent periods (They will remain locked…

Hey @User_LVLRS, Yes - you can do that via custom workflow. At a high level: Create a workflow to trigger the Edit Create a "Set Field Value" action for the "Date" field and set a formula to {today} Enter a condition in the action for the required Assembly Build status

Perhaps the user doesn't have access to a Saved Search that is attached to the custom field (not locked). You are probably testing this in Admin role, which has access to the Saved Search/

When you open a period, all periods coming after it must also be re-opened. Imagine a Closing Bank Balance of $10,000 in 2017, which is also the Opening Bank Balance of 2018. If you open 2017 and change the balance to $15,000, you have to have 2018 and future periods open, so the Opening Bank Balance also changes to…

I am referring to a "custom field" that is "powered by a Saved Search". Can you check if you have any custom fields on the Transfer Order record? A separate Saved Search opened in another tab won't affect this.

Hey @ONO4, You can source the Transaction ID to a custom column/line field via the formula:

Hey @MaheboobVanteli, You can trigger a Workflow action on clicking of a custom button. For standard buttons, you need a script.

Hey @Dext3r, Do you see any pattern in terms of items that are causing this? Will the same item cause the same issue for everyone? There is a chance this might be related to item configuration, default bin, quantity on hand in the specific location, etc. In my view, this is a core functionality and should be resolved…

Hey @HX_SUBHANKAR, No - there is no such practical limit in NetSuite. In theory, if we try to create 1000s of periods, we may hit some warning messages, although these won't apply to real-life scenarios.

Hey @User_TXI1Z, I need significantly more insights into the configuration and the record the Saved Search is running on to propose the exact adjustments. Based on the current screenshots, it appears the "Summary Type = Minimum" is one of the reasons for the issue. For Summary % calculations, I mainly used "Sum."

Hey @User_OGQAD, There is probably a custom field on the PO record with a linked Saved Search. The linked Saved Search is probably misconfigured, which is causing these issues.

I am 90% confident it can be done. If I knew the exact steps, I would have listed them here. It would take me some time to figure it out, and I can't spare much at this time, I have too many competing priorities. Open a ticket with NetSuite Support and mention the issue. Per the SCM Mobile guide, we should be able to add…

Agreed - the information on SuiteAnswers provides limited help. I know I tried several things before it worked. I was adding custom fields and am not sure how different it is from adding standard fields. Perhaps your issue is the incorrect "Merge" criteria. If that's helpful, I used a Saved Search for "On Load Action" and…

Hey @PatrickConrad, There is very little documentation on how to customize SCM Mobile pages. It took me a while to figure out how to add a few custom fields to the Work Order selection table. Take a look at these articles for some examples: SCM Mobile App Customization

NetSuite Consultants do everything related to NetSuite to help customers achieve their business goals. As part of NetSuite Implementation, I import multiple journals for my multi-currency and multi-subsidiary customers.

If the Supply and Demand are also empty, then the Supply Plan Definitions and/or the related MRP configuration are inaccurate. Multiple reasons can exist, such as an incorrect Supply Plan Definition, Planning Rule Groups, or mismatched Planning Item Groups. I recommend working with your NetSuite Consultant to review the…

You can only do that via Script, as Electronic Payments doesn't have the functionality to change the bank based on the transaction subsidiary.

Thanks for the answers. You can create a workflow to auto-update the Work Order location based on the Assembly default location. Would this resolve your main issue, or do you also need to impact MRP recommendations?

Hey @User_J1C00, For these use cases, the best option is to: Create the "Store Value" version of the same field Create a Scheduled Workflow to run every 30 minutes and copy the value from the "non-stored" field to the "stored" field Add the "stored" field to the Saved Search

Hey @User_V4YFI, Are you paying via the standard "Make Payment" / "Pay Bills" functionality or via Electronic Payments?

Hey @User_7VOB5, Instead of using "Name", you should use the following "join" field:

Hey @PaulRipley, This is typically done via multiple imports, impacting Parent, Child, and Elimination subsidiaries. There are multiple steps involved in the process, and it would be best to do this with your NetSuite Consultant.

Hey @User_TCN82, There are multiple ways to resolve this, some of which would be based on your specific configuration. Questions Is this required only for Work Orders generated from Sales Orders? Are you physically fulfilling Sales Orders only from the "Despatch" location? Do you have assemblies that can be built in both…

Hey @User_4BBKV, The voiding and updating of the Bank Rec is the cleanest option and shouldn't take too much extra time. Any other method will involve more work and won't be as clean. The best practice is to wait for all payments to be processed via Bank before completing the Bank Rec.

Thanks for confirming. Try SUM(NVL({task.custevent10},0)) instead of SUM({task.custevent10})

Hey @User_NG5TG, The issue might be related to Field IDs. Can you confirm you selected the correct field ID for the "Task: Cost of Job" field?

Thanks for the additional details. I confirmed that the "Before Record Load" trigger doesn't work. Can you open a support case and ask them to investigate? If you change the trigger to "Before User Edit" and edit the Customer Record, the form will change correctly. I know this won't work for you. If NS Support can't…

Thanks for sharing, @Ivy Lopez-Oracle!

Thanks for the screenshots. I assume the action is "Set Field Value". Can you set the Condition similar to my screenshot and try again?

Can you share some screenshots of the workflow so I can help? Here are a few screenshots that should work for you: