I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn’t work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
We could simplify this requirement by adding a table called “Warehouse User” in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.
We could simplify this requirement by adding a table called "Warehouse User" in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
We could simplify this requirement by adding a table called "Warehouse User" in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.
We could simplify this requirement by adding a table called "Warehouse User" in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.
Hi Anand, any news on this feature? (and coming from Rushabh's email announcement, will this be part of the features for the more daring "beta" customers?)
We could simplify this requirement by adding a table called "Warehouse User" in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
Due to the internationalisation release and the recent performance issues, we have had our hands full. Also, I have been on leave and as such, we are also a developer short.
We sincerely want to get this done. This is a good problem to solve. We will discuss about this and inform you on how soon can this be done.
Thanks,
Anand.
Sent from my iPhone
On 31-Jan-2013, at 6:39 AM, Laurence Cua <la...@union.ph> wrote:
Hi Anand, any news on this feature? (and coming from Rushabh's email announcement, will this be part of the features for the more daring "beta" customers?)
We could simplify this requirement by adding a table called "Warehouse User" in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups “ERPNext Developer Forum” group.
Due to the internationalisation release and the recent performance issues, we have had our hands full. Also, I have been on leave and as such, we are also a developer short.
We sincerely want to get this done. This is a good problem to solve. We will discuss about this and inform you on how soon can this be done.
Thanks,
Anand.
Sent from my iPhone
On 31-Jan-2013, at 6:39 AM, Laurence Cua <la...@union.ph> wrote:
Hi Anand, any news on this feature? (and coming from Rushabh's email announcement, will this be part of the features for the more daring "beta" customers?)
We could simplify this requirement by adding a table called "Warehouse User" in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.
Due to the internationalisation release and the recent performance issues, we have had our hands full. Also, I have been on leave and as such, we are also a developer short.
We sincerely want to get this done. This is a good problem to solve. We will discuss about this and inform you on how soon can this be done.
Thanks,
Anand.
Sent from my iPhone
On 31-Jan-2013, at 6:39 AM, Laurence Cua <la...@union.ph> wrote:
Hi Anand, any news on this feature? (and coming from Rushabh's email announcement, will this be part of the features for the more daring "beta" customers?)
We could simplify this requirement by adding a table called "Warehouse User" in the warehouse form. Once populated, it will check when submitting a stock entry, if the user is allowed to make any entry against that warehouse, be it entered in source warehouse or target warehouse. However, if the user is not mentioned in the Warehouse User table, he will not be stopped from making a stock entry for that warehouse (if he has write permission on Stock Entry).
This should solve your issue. We will try to do this soon.
Thanks,
Anand.
On Tue, Dec 25, 2012 at 6:47 AM, lxnow <la…@union.ph> wrote:
Hi everyone,
I have multiple locations that we need to track inventory for and multiple users that have access to these locations. We are using Stock Entry (STE) forms to move stock in and out of these locations. However, we need to have these locations restricted to each users to avoid encoding mistakes. For example, we do not want the warehouse supervisor to mistakenly deduct or add stocks to the production location as this would render inventory data inaccurate and lead to more time spent on auditing.
The restriction rules need to be on a per user basis (rather than role) as we would have, for example, two warehouse supervisors who are in charge of different physical warehouses. The restriction rules must also be definable to both source (stock deductions) and target (stock additions).
After a few email exchanges with the erpnext support team, Rushabh suggested to post my problem here along with his original intended solution via custom script. While I am not a developer myself, I tried hacking the script to our need but have hit a wall: because we have more than 40 locations and more than 10 users at the moment (with the expectation to expand as we we go forward) the script doesn't work after 5 users and Rushabh tells me that this approach will render erpnext to run very slowly. I have attached a sample of our script.
I was hoping someone would be gracious enough to take a look into my script and offer some advice, or if someone else has already encountered and resolved a similar problem.
Thanks!
–
You received this message because you are subscribed to the Google Groups "ERPNext Developer Forum" group.