infor.com
concierge
infor u
developer portal
Home
Groups
Lawson - Supply Chain Management Customer Community [READ ONLY]
Item Master IC11.1, UOM / Cov Factor
Legacy Contributor
My predecessor taught me when adding a new non-stock item in IC11.1 the Conversion Factor should always be “1”. Example: UOM (BX) Conversion Factor (1).
He said, when adding a stock item in IC11.1 the Conversion Factor should be list the correct breakdown. Example: UOM (BX) Conversion Factor (12).
Issue – Being new and not really understanding why the above was done we changed the non-stock items being added to IC11.1 to read like the stock items. I’m finding when end users go into “RQC” to place orders they are now seeing the system displaying product as “EA”, thus it records on PO as each when product should be for example a purchase of a “BX”.
I’ve tested with replacing the non-stock items back to the old breakdown. User is now seeing product in “RQC” as a “BX”, thus records on PO as BX. I guess I want confirmation this is correct and we should correct the new non-stock items to how my predecessor taught me to put them into IC11.1. Thanks for your advice… Damian
Find more posts tagged with
Comments
jon-athey
We break out almost everything by CA/BX/EA if it's patient related. If it's nonstock at all locations and we break out UOMs by EA and BX and the vendors sell UOM is BX we flag BX as the Transaction default and Buy default.
I understand the policy of only loading the vendor's sell UOM for nonstock items. It does simplify the ordering process. However, from a cost accounting view, when interfacing with OR or Cath Lab systems you really want to break (at least patient charge) items down to the EA in IC11.
taliening
The trick to it is shown in Jon A.'s example. You can build items down to the EA and have the BX unit of measure only show up by removing the EA as a Buy Unit of Measure (column to the far right). Once you set EA to (blank) the user in RQC will get BX as their unit of measure.
Fax.png-840x574[1].png
dechevar
I agree with Jon about always building to the EA for 2 main reasons: it gives you the analytics you need to know how much you are paying for an item, and it means less rework to add an item into inventory.
The key is the Default Buy UOM FL. Whatever is set as the default is what your requesters will see in RQC first. If the EA is not a Valid Buy UOM (Option 2), then clear the field as in Jon's example.
We have the issue with multiple facilities where some order LUM through O&M so the EA is valid for them, but it is not valid for the other facilities. So users who can't order in the EA, have the option. Unfortunately, this something we cannot get around.
Legacy Contributor
You should be able to get around that issue by using participants and the different UOM flags on vendor agreements.
Important Links
Community Hubs
Discussion Forums
Groups
Community News
Popular Tags
ION Connect
ION Workflow
ION API Gateway
Syteline Development
CPQ Discussion Ask a Colleague
Infor Data Fabric
Infor Document Management (IDM)
LN Development
API Usage
FAQs, How-To, and Best Practices