Hide/Block/Restrict Items from RQC

 8 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member

I know we've had topics on this before but we're facing this again and I'm having issues finding past threads.

 

We had a safety initiative and brought in an expensive item.  We are now building a remote ASC that will not be using them - they will be using the cheaper option. All Admins are adamant that the rest of the healthcare system not be allowed to use this item.

I know how to make it "difficult" for RQC to order an item, but I don't know anyway to stop it completely.  Please add/correct my list:

Ways to Prevent an Item from RQC Orders:

1. Issue Account - if we give the IC11 record an account that only the ASC has, everyone else will get an error.

Challenge: RQC will allow users to change the account in item details.

2. Purchasing Major/Minor - if we give the item a major/minor code, the users will receive a popup error

Challenge: they will need to tell us every person who needs rights.

3. Inactivate at Ship To - If I add the item to every IC12 and inactivate it for all except the ASC, requesters will get an error

Challenge: the ASC is currently sharing a ship to so the other departments in it will have access.

JimY
Veteran Member Send Private Message
Posts: 510
Veteran Member
For item 1 couldn't you have the account number turned on for the accounting unit for ASC only? That way only those that have the accounting unit assigned to them in RQ04 would be able to use it. Not sure if that is viable.
JonA
Veteran Member Send Private Message
Posts: 1163
Veteran Member
We've used options 2 & 3 before. These are the only options I know for preventing the end user from choosing a restricted item. Assuming you use IPA for req approvals, what about using this to route the req to a buyer for approval when this item is requested? Buyer approves it and it moves on through your normal approval process. Otherwise the req is rejected.
Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member
IPA might - but we're hoping to avoid custom tables so it might be more trouble than it's worth trying to find a way to flag them. A different GL Code seems to have been nixed for the moment.
JonA
Veteran Member Send Private Message
Posts: 1163
Veteran Member

Custom tables?  I was thinking a Branch node that would look at the item number(s).  The restricted numbers are listed in the branch.  This would have to be maintained of course.

Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member
The list is over 100 skus so far, I was told that would need to be in a table. I don't have rights to IPA Design - that's the IT side here. I might ask.
Red
Veteran Member Send Private Message
Posts: 87
Veteran Member
Kat ,
How about using an Item Attribute (IC56.1)? Something like "ASC" as a True/False (Boolean) field. Then set the IPA branch logic to follow a specific path if the attribute is "Yes" and to follow the standard path if Blank or "No". We do this on a couple different topics.

Hoping to help,
Red
Learn from the Past. Prepare for the Future. Act in the Present.
JonA
Veteran Member Send Private Message
Posts: 1163
Veteran Member
^^^I like this!
Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health
Kat V
Veteran Member Send Private Message
Posts: 1020
Veteran Member
I like it - my boss wants it to flat out refuse to add to the requisition so it isn't "Kat rejected the req" but "the system won't let me"