Sub Contract error

Yahoo Archive
1
Donna we have the same problem here and I asked the group the same question.
I'm also on version 5.0. so there may be a patch. Can anyone tell me where I
can find all the patches for each version and what they were supposed to
have fixed?


Fredy Venczel


-----Original Message-----
From: Donna Larrick [SMTP:dlarrick@...]
Sent: Wednesday, November 19, 2003 11:15 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Sub Contract error

I have a problem that has been on going for some time now. I have a
part master routing with one sub assembly. The top level (ex: P/N 54G01) has
10 operations and the sub assembly (ex. P/N 54P01) has 15 operations.
The problem is after the job is created, in the top level routing we
have a sub contract operation and when we print the PO or RFQ for this, it
prints out the sub asm. P/N instead of the top level P/N.
I checked the part master routing and the P/N (54G01) is correct on
the Sub contract operation. This becomes a major problem because some of
jobs have 175 -200 sub asm. and it happens on all of them and then we have
to go in and manually change each one prior to releasing the job.
We are on Vantage 5.0.
Any suggestions would be greatly appreciated.

Thanks,
Donna
2
I have a problem that has been on going for some time now. I have a part master routing with one sub assembly. The top level (ex: P/N 54G01) has 10 operations and the sub assembly (ex. P/N 54P01) has 15 operations.
The problem is after the job is created, in the top level routing we have a sub contract operation and when we print the PO or RFQ for this, it prints out the sub asm. P/N instead of the top level P/N.
I checked the part master routing and the P/N (54G01) is correct on the Sub contract operation. This becomes a major problem because some of jobs have 175 -200 sub asm. and it happens on all of them and then we have to go in and manually change each one prior to releasing the job.
We are on Vantage 5.0.
Any suggestions would be greatly appreciated.

Thanks,
Donna



[Non-text portions of this message have been removed]