infor.com
concierge
infor u
developer portal
Home
Groups
VISUAL - Enterprise Customer Community
Buying a part that comes in and becomes two parts
Legacy Contributor
We buy rolled pipe from an outside vendor. When we bring the rolled pipe into our facility we process the rolled pipe and create 3 new components. We will often stock the rolled pipe as a full section.
We have been discussing how we can handle this in visual. We don't seem to have the ability to purchase a part and process it to make 3 new parts.
We do this for a number of bends and in some cases the purchased bend can create 2 of one component and 3 or another.
Any help would be greatly appreciated.
Thanks
Stephen
Find more posts tagged with
Comments
ztrue
What about receiving it in as a purchased part ID and processing it against 3 work orders?
Issue 1/3 of the total pipe (I would guess your UM is a length measure) to each and received the finished product as a fabricated part ID.
Legacy Contributor
I am presuming that you have masters in place for the three components and that the masters call for the rolled pipe as a material. Thus you are able to purchase enough rolled pipe to produce the number of components you need to make. First determine the number of each of the components you need to make and the number of rolled pipe sections you need to use. Then, make a work order for one of the components and over ride the material card [pipe sections] quantity to be the pipe sections you determined you needed. Then, in the header card, select co-products. Enter in the quantity of the other components you will get by running the job. You can assign cost on a % basis to each of the components.
You should be able to maintain visibility of your pipe sections and your components using this method.
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