infor.com
concierge
infor u
developer portal
Home
Groups
Lawson - Supply Chain Management Customer Community [READ ONLY]
Patient Charge Number on Pick Tickets
Stace Webley
I was recently asked by the warehouse manager if we could print the patient charge number (PC10.1) for an item on our WH130 pick tickets. I guess they are hoping the pick ticket will lead the distribution techs to knowing which items are billable and to print off a patient charge label for the item.
Does anyone know if this is possible (I know it isn't from a WH130 job parameters approach)? How difficult would it be to add this? We also use Item Attributes (IC56.1) that would be nice to add to the pick list if possible...Perhaps, there is a better practice that others are using? Any input is appreciated!
Find more posts tagged with
Comments
Legacy Contributor
This doesn't really help with your specific question, but two points...
- If you use Infor Lawson Point of Use, you would not need to print patient charge labels. POU will know what is chargeable or not and no stickers required.
- On our roadmap, we plan on adding to version 10 later this year a patient chargeable flag on IC11. it is currently on IC12.
Keith
Stace Webley
Thanks, Keith. Does the IC12.1 Patient Chargeable flag show up on the WH130 Pick Ticket at all? What effect does this flag have when the item is issued out? Thanks!
dechevar
We use IC12 Patient Charge Flag and a User Field populated with the Charge Code. We have created a custom print job the prints labels for the items that the staff leave in the bin to label with on put away.
In addition, all bin labels for chargeable items are printed in yellow as a visual queue that the items should be labeled.
[Updated on 5/5/2014 3:31 PM]
Stace Webley
Thanks, djechevarr!
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