Best Of

Thanks @Tiru Chembeti!

It will help! Thanks a lot!

Hi @Bee Yook

From what I know, usually we don't have to configure for all the item location whenever new locations or new items record are created. Unless your company has a requirement to set specific reorder point or preferred stock level or any other stocktake or demand/supply related settings for each item + location pair.

Item cost are usually auto computed based on the stock in and stock out transactions posted in each location. If you are using inventory adjustment to add inventory balance then the unit cost field value should manually specify instead of taking the default value in the field.

May I know what costing method are you using ?

Regards,
Wee Ming

That's a great suggestion going forward, thanks Wee Ming!

Any suggestion/idea of what to do about all the rejected proposals still hanging out there causing a disconnect between FAMS and the General Ledger?

@Jervin Nicholas Teopengco-Oracle Thank you so much! I appreciate the detailed response and was able to get it to work on my end.

Hi User_KYOCJ

You can merge multiple asset proposals to generate one asset. The cost will be auto sum together.

So instead of rejecting the proposal for the shipping charges, edit the proposal and set the FA asset proposal id in the Parent Proposal field.

Then on the Fixed Assets > Transactions > Manager Asset Proposal page , select only the parent asset proposal to generate asset.

Once asset generated, you will see the same asset id populated in Asset field both the Parent and Child Asset Proposal record.

Regards,
Wee Ming

Hi,

I just added filter to the Generate Price Lists > Items tab.

Can you try the following?

1. On the custom record, change the field type for the Vendor to "List/Record" and select the Vendor list. Ensure the "store value" is checked.
2. On the Workflow, select the "Internal ID" instead of "Name/ID" for the "Preferred Vendor" join

Let's see if it works this time.

Ran into the same issue and this thread was the first search that comes up. I managed to make a scripting solution for it. It will update the To Location field correctly.

The issue appears to be that NetSuite has labeled the fields wrong on implementation. Ideally, you should aim to fix the labels of these fields first but for me I already had a number of workflows and scripts that treat the fields as NetSuite has labeled them (incorrectly). So this script is perhaps an easier fix for some.

Deployment:
Applies to: Item Receipt
Event Type: Create