Try a "Job Receipt to Job" with the subassembly. It seemed to work for me when I tested it on two freshly released jobs with no other transactions (i.e. no-on hand inventory). I'm on Vantage 8.00 so YMMV.
The transaction will not show on the PDR for unit B job but will show on the PDR for unit A job. That is just one of the idiosyncrasies with PDR that it doesn't show subassemblies issued out of the job. The financial results do show in the WIP report though. Depending on how you have it costed, it could create a mess of the WIP report since it will come out of unit B job in the cost elements established by the costing method but goes into unit A job as material only plus material burden (no matter what the cost elements). In other words, labor and burden get bundled in the material cost despite the costs established in the system. But honestly, Vantage doesn't play well with subassembly costing so I'm sure you are used to that.
Regards,
Chris Clunn
The transaction will not show on the PDR for unit B job but will show on the PDR for unit A job. That is just one of the idiosyncrasies with PDR that it doesn't show subassemblies issued out of the job. The financial results do show in the WIP report though. Depending on how you have it costed, it could create a mess of the WIP report since it will come out of unit B job in the cost elements established by the costing method but goes into unit A job as material only plus material burden (no matter what the cost elements). In other words, labor and burden get bundled in the material cost despite the costs established in the system. But honestly, Vantage doesn't play well with subassembly costing so I'm sure you are used to that.
Regards,
Chris Clunn
--- In vantage@yahoogroups.com, "Chris Henzel" <chrish@...> wrote:
>
>
> We sometimes have the following situation and I'd like to know if there are any solutions or suggestions.
>
> We are building two units, unit A and unit B. These units are being manufactured as seperate, multi level jobs. The units share many components in common however the units are for different projects and due dates, hence different job numbers.
>
> During the assembly stage of unit A a problem is found with a part manufactured as a sub assembly. The common component from unit B is taken and used to complete unit A.
>
> Is there any way to replicate this action in Vantage 6 or Epicor 9?
> I have looked at returning the sub assembly to stock and issuing to the other job but I recieve an error as the assembly issued quantity is zero. I have tried using a BPM to increase the issued quantity within the JobAsmbl table which then allows the sub assembly to be received to stock but the assembly 'disappears' when issued to the other job. It doesn't appear anywhere within the job but it does show a transaction in part history.
>
> Any better suggestions?
>
> Thanks
>