Location Flowfilter on Item

SmokeScreen · 2006-09-01

Nav 3.70A

Multiple Locations

Issue is that employees at other locations do not realize that Quantity On Hand is not location specific.

What I would like to do is utilize the flow filter on location code, however I would like to know if there is a way to "default" the filter value whenever a user logs in.

Is there a way to set a different value per user? (Example my CA employees always filter for CALI location code, my NY emp always filter for NYC location upon login)

I have tried explaining Item Avail by Location, however this is not the option mgmt. wants.

Any help would be great

kine · 2006-09-01

You can add some settings into User setup (for example "Location Filter") and aply this filter to "Location Filter" on Item Card and Item List...

nunomaia · 2006-09-01

In the Form Card

In the

Form - OnAfterGetRecord()

After the SETRANGE("No.")

Filter the location based in the new filed in the user setup

Savatage · 2006-09-01

Another Way is to add two new fields to the item table.
Cali-Qty
NYC-Qty
It basically mimics the regular qty field but the filter is set permenantly.

This way the filter is never lost when updating a form or the user simply forgets.

it will be type Flowfield same calcformula as the regular qty on hand field except for

Sum("Item Ledger Entry".Quantity WHERE (Item No.=FIELD(No.),Global Dimension 1 Code=FIELD(Global Dimension 1 Filter),Global Dimension 2 Code=FIELD(Global Dimension 2 Filter),Drop Shipment=FIELD(Drop Shipment Filter),Variant Code=FIELD(Variant Filter),Bin Code=FIELD(Bin Filter),Location Code=FILTER(NYC)))

And (CALI) would be the formula on the other one.

These fields then can be added to the item list, etc etc

We have two locations and this is pretty easy to set-up - but if you have more locations than that - the filter on logon as mentioned above would be the best solution.

themave · 2006-09-01

Savatage wrote:

Another Way is to add two new fields to the item table.
Cali-Qty
NYC-Qty
It basically mimics the regular qty field but the filter is set permenantly.

This way the filter is never lost when updating a form or the user simply forgets.

it will be type Flowfield same calcformula as the regular qty on hand field except for

Sum("Item Ledger Entry".Quantity WHERE (Item No.=FIELD(No.),Global Dimension 1 Code=FIELD(Global Dimension 1 Filter),Global Dimension 2 Code=FIELD(Global Dimension 2 Filter),Drop Shipment=FIELD(Drop Shipment Filter),Variant Code=FIELD(Variant Filter),Bin Code=FIELD(Bin Filter),Location Code=FILTER(NYC)))

And (CALI) would be the formula on the other one.

These fields then can be added to the item list, etc etc

I like this approach also, it involves the least changes to Navision, and works really well.

nunomaia · 2006-09-01

The only problem that I see with this solution with the flowfield is that you need a field for every new location.

themave · 2006-09-01

nunomaia wrote:

The only problem that I see with this solution with the flowfield is that you need a field for every new location.

I agree, but as long as it is just a few locations it is a good solution.

If I were to go with the filter by user id, I would still do that on a new field in the item table, and leave the existing qty field unchanged.

that way you could have a total qty (existing field) and a "my location" qty the new field. and any upgrade or service pack in the future would not affect your field.

Savatage · 2006-09-01

We've been using it for years - helps with reports too. Instead of running two reports, one for each location, we can run one with the report show the qty's in both, & 100 other useful goodies.
We only have two locations..I can see how 10, 20, etc can be a bit much.

But by this quote it seems that they want a solution that doesn't require any reminders.

SmokeScreen wrote:

I have tried explaining Item Avail by Location, however this is not the option mgmt. wants.
Any help would be great

& when the form opens they will immediately know how much they got altogether & how much in each location.

Qty On Hand = 100
Qty in NYC = 70
Qty in CALI = 30

Also, it doesn't require a Developer license. You can do it in 2 minutes

SmokeScreen · 2006-09-01

Wow... thank you for the ideas... My hesitation to adding additional flow fields to the Item table would be any potential system slowdown that could occur from the constant calcs...

I like the user setup Idea with the single new field... I am going to layout the plan and see what it will involve to have coded.

Thanks again everyone, and please if you have more ideas, let me know.

Savatage · 2006-09-01

the calc is instantaneous just like the reg qty field

oh, I see we posted the previous posts at the same time

SmokeScreen · 2006-09-01

No potential for system wide slow down if I were to have say 5 additional fields added for each location? The NSC balked at the idea pretty hard.

Savatage · 2006-09-01

Maybe cause you can do it yourself without paying him :-#

You can always simply try it and if you don't like it, delete the field.
Won't cost you anything.
My Item Ledger Entry table has 2,973,712 records - no slow down.

(Ok someone will chime in with "It's not the Navision Way")
but it works

themave · 2006-09-01

Savatage wrote:

Maybe cause you can do it yourself without paying him :-#

You can always simply try it and if you don't like it, delete the field.
Won't cost you anything.
My Item Ledger Entry table has 2,973,712 records - no slow down.

(Ok someone will chime in with "It's not the Navision Way")
but it works

I like your thinking, that is how we try most things, see if we can do it ourself before we pay to have someone else do.

SmokeScreen
If you are worried about system slow downs with flow field the only danger is will list, not really a problem on a form
On a list it can slow down, because it has to cal the flowfields for all the items on the list. but on a single form it is not a problem at all.

Location Flowfilter on Item

Comments

Categories