Disable Inventory Transactions during Phy Inventory

Kinetic ERP
1

We will be completing Physical Inventory activities at multiple sites over the next two weeks, but not all at the same time. I need to lock down Inventory transactions to just a couple of people at each site (on different days), while allowing others to continue with activities that do not affect inventory.
Example:

  • Group A would be locked down Monday/Tuesday/Wednesday and then have access restored on Thursday.
  • Group B would have access locked down on Thursday/Friday/Saturday and have access restored on Sunday.

I’ve been poking around trying to understand securities and how we are using them. We use Security Groups and assign those groups to the user. So I’m thinking the only option I have is to remove the Security Group with inventory transaction tasks from each individual on the days it needs to be locked down and then adding those security groups back when they are done.

Am I going about this the right way or is there a better option?

In our test/pilot system I tried adding my user to the disallow list for customer shipments for example but it didn’t seem to have any affect, I was still able to process a customer shipment.

2

Hi Valorie,

Security groups limit menu access. Best to just use groups and remove add/users to the group. I have not used the do not allow.

Staff do need to close & re-open Epicor for changes to take effect. Also although you can limit access to menus there are many items that impact inventory e.g. shipping, receiving, MES work Q etc

3

I have a couple BPMs I use each year. It’s an “In-Transaction” Data Directive on PartTran.

You can literally make it this simple:

image
image960Ă—872 49.8 KB

I made mine only just slightly more complicated, with a group for people allowed to bypass the rule:

image
image1200Ă—728 55.7 KB

(We have 2 sites hence 2 BPMs. If you had many sites I’m sure you’d do the BPMs more efficiently…)

4

Thanks Matt - with the number of employees and possible inventory transactions I was hoping to avoid removing and re-adding groups to each employee - since I have to repeat the process I thought this was just a setup for failure on my part. :frowning:
I had a feeling that was going to be the best option.

5

I Like this possibility! So the PartTran type is any that affects inventory obviously and you could condition for people and plants?

6

Right, PartTran is the table that all inventory parts must pass through in order to make quantities go up or down. (Also all non-inventory parts hit the table as well.)

So blocking people from writing to this table is an unflinching hard stop against inventory changes.

Even if you are terrified at the idea of BPMs, I think this one is bar none the easiest you could imagine.

About giving people access. You can go person by person in the BPM. That’s fine. I just get lost in all the ANDs and ORs myself.

What I did is make a security group (see pic above) and assign the users to it that I want to allow, and add that to the BPM logic.

So, you’ll find that you still need to let your AP clerk be in the “allow” group, for example. He or she may not do receiving of parts, of course, but it turns out that things like purchase adjustments hit PartTran also.

7

Perfect! I have stumbled through a couple of BPM’s and this one seems like something I can handle! LOL

thank you for the idea!

1 Like
8

It would be better to just carve out certain transactions (PUR-UKN,PUR-INS,INS-SUB,DMR-REJ,MFG-CUS, etc.) that don’t hit inventory rather than carve out people. Maybe give 1 or 2 people full exceptions because sometimes hot jobs hit during inventory.

9

Thanks John I did think of going that route too. I’m testing both paths in pilot now and will settle on one to go with today since I need to implement/enable the BPM on Sunday so transactions are locked down for first group on Monday AM. Either one is much better than what I thought I was going to be facing a couple of day ago!