My Stuff
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
Explore NetSuite Next with Free Training!
Build your skills with the LCS Explorer Pass.
Visit the NetSuite Next community page
to learn more, ask questions, and share your experience.
Build your skills with the LCS Explorer Pass.
Visit the NetSuite Next community page
to learn more, ask questions, and share your experience.
Comments
-
It answered my question, but I was still not able to find the article 102501. Perhaps this article number is not valid or no longer available. I did not have any other article numbers to test the process given.
-
Here is the solution I came up with: Overview Create a checkbox field on Account to indicate which account are to be included. Create a new dropdown field on the Inventory Adjustment form which will have the selected options. Create a workflow to populate the original Adjustment account field with the Account selected from…
-
This is the function that I was able to create to solve the problem. The requestBody contains the values for subsidiary, location, transfer location, memo, item, adjustment quantity, from bin, and to bin. async function transferItem(requestBody){ try{ // Create new inventorytransfer record let transferRecord =…
-
What search tool did you use with the statement select * from oa_columns where column_name = 'built'; When I run this in my query tool, I get : Error Invalid search type: oa_columns
-
Thank you that works. And I appreciate your detailed answer and showing the steps you used to get to the answer. Greatly appreciated
-
thank you That solved the problem. It had been working with "altshippingcost" up untill a few days ago and then it just quit working.
-
No I don't think I need further checking. I assume there is something wrong in the way the custbody_atlas_assy_desc was set up. I have a working solution so it is not an issue now. I may look at this field sometime in the future. Anyway you pointed me in the right direction. Thanks
-
Here is the complete query I am using: Select T.id as WOId, BUILTIN.DF(T.TranID) as order, BUILTIN.DF(T.custbody_tw_proj_copied) as Project, TL.item AS ItemId, Item.description, BUILTIN.DF(TL.item ) AS Item, ABS(TL.Quantity) as Quantity, TL.itemSource, MT.Date, Item.averageCost, T.custbody_atlas_assy_desc as assy,…
-
This does return the Assembly Item, but it also returns 3828 other items. Not sure how all the other items are related. I am not familiar with this syntax: From Transaction as T, bomAssembly as B, item as I
-
I think you have given me the right answer, but I can't query T.assemblyitem. Search error occurred: Field 'assemblyitem' for record 'transaction' was not found
-
Here you go.
-
Have not found the answer as to why the T.custbody_atlas_assy_desc as assy does not return the correct information in the query, but I was able to do a work around by querying on field BUILTIN.DF(t.billofmaterials) instead which so far has given me the correct assembly item number. I would still like to know why the…