channingm - I'm guessing you would have to have all the legal entities set up as subsidiaries under one root subsidiary (call it a 'consolidation subsidiary') - and the root subsidiary would initially hold all the stock. Then as each legal entity processes orders, stock would transferred (using inter company transfer…

Well we've looked into it further and it seems that it can be done, but it wouldn't be ideal. Certainly the chart of accounts could not be taken at face value any more - all figures would have to come from customised reports and searches taking location into account. So we're going to look at OneWorld more closely now.

We use our own saved searches to help identify item demand when placing stock orders, so no worries there. I think our company names are going to be identical as well so it won't really matter where it pulls the name from. I'm comfortable with scripting so I'm assuming with small annoyances that are just how OneWorld…

It looks like we'll get NetSuite to guide us on the implementation, but I want to do as much as I can - they can basically tell me in what order I should be doing things, and check my work if they want. I'm talking to a support rep from NetSuite today who's done these implementations before, so will get a better idea after…

Oh and just been reading about the new Intercompany Inventory Management in release 2012.2...says it enables you to coordinate inventory transfer between subsidiaries, but I thought this was already handled with Intercompany Transfer Orders?

From what I've read, these seem to be the important things to take into consideration: - existing data in a NetSuite account is moved to the root subsidiary in OneWorld - setting the country for each subsidiary defines the NetSuite edition and tax Nexus that is used - each transaction pots to a single subsidiary, with the…

Actually you're right the documentation does say it's a 1-1 relationship. I think I may have gotten confused because some relationships to subsidiaries are not 1-1, such as items and accounts...whereas entities and locations are 1-1...correct?

That worked! So NetSuite's online help regarding fonts is incorrect, at least for producing PDFs. I think from now on I'll use NetSuite's resources for NetSuite-specific stuff only (field Ids and record joins and the like) and use the official Freemarker and BFO reference for everything else :)

michoel, you are a font of knowledge! I was thinking about PM-ing you a couple of questions but I suppose discussing them out int he open leaves a trail for others to follow, hopefully someone else will benefit as well. It worked perfectly, and the form doesn't seem to take noticeably longer to render.

Oh and I know about having the Shipping Item display at the end of the other line items on a transaction, I am attempting to break the shipping info out to make it more prominent on the printed form. If it's not possible I have figured out how to identify the shipping item in the list ( <#list record.item as item> ), so I…

Well that would explain it...though NetSuite specifically states you can use any of the selectable fonts in WYSIWYG mode! Off I go to test...

Huh good point. That seems like the long way around to get it though, I was hoping it could be referenced directly. FYI you can identify the shipping item like this (inside the #list declaration): <#if item.itemtype="Description"> Not sure if it's better to have == instead of one = ? In all cases where I'm evaluating a…

That did it! Genius :) So what I gather from this is that although we can source fields from related records linked in BODY fields, in a SUBLIST you can only refer to fields on the form? Also wondering why in this instance not storing the value in the field is important? I did know about the trick to hide a field by…

I couldn't get this working either. To get data from another field on the item's record, I had to use custom Transaction Column Fields. Set the field to source from the item's record, don't store the value, and when adding it to your form make sure the Label is completely blank which will hide it but leave it open to…