I have the similar case. My Customers send both firm and forecast in the 830. We ask them to use 862 for the firm. But most of them Use 830 only. On the firm they would send the PO Number. I map conditionally the Firm to go into Inbound PO Interface and the forecast to the forecast interface files. The Firm is used to create the sales order in my system. I don't need a blanket PO Because My Customers gives me 4 days to send the shipments and my sales order can have multiple PO's. The Industry Group I work is In AIAG and some of my customers are moving towards splitting the firm into 862. Regards Kiran Dunthuluri EDI Analyst "Hurd, Richard A (Richard)" <[EMAIL PROTECTED]> on 08/31/2001 09:30:27 AM Please respond to "Hurd, Richard A (Richard)" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: Kiran Dunthuluri/Toyota Tsusho America) Subject: Re: Application-level trading partner integration And the point I'M trying to make is that I have at least two trading partners who send forecasts in AND ADDITIONALLY expect a new purchase order to be opened with the transmission of this 830/DELFOR. So in your experience an 830 is never used as a PO but that turns out not to be the case in my experience. True, any vanilla processing system would kick it out. We, of course, have made extensive modifications to our translator environment so that this functionality can happen. And if your customer explains that they want to send a PO in with an 830, I trust that you as a supplier will be more than willing to accomodate them. -----Original Message----- From: Jim Divoky [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 9:14 PM To: [EMAIL PROTECTED] Subject: Re: Application-level trading partner integration The point I was trying to make is that an 830 is never used as a Purchase Order. It IS used as a release order. There is a significant difference. I seriously doubt that anyone has ever sent an 830 or a DELFOR as a purchase order. Any system would kick it out for manual processing as there would be no match on the PO number. Apparently, I didn't make myself clear. Jim Divoky ----- Original Message ----- From: Hurd, Richard A <mailto:[EMAIL PROTECTED]> (Richard) To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Sent: Thursday, August 30, 2001 9:42 AM Subject: Re: Application-level trading partner integration -----Original Message----- From: Jim Divoky [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 30, 2001 11:28 AM To: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Subject: Re: Application-level trading partner integration This is not correct. Forecasts are sent to feed the supplier's MRP system. Fixed forecasts could be used to generate a shipment against a blanket PO but a release order is perhaps more correctly used to initiate a shipment. LOL I'll be the first to agree that it's not correct. You go ahead and tell your customers that what they're doing with their 830s and DELFORs isn't correct business practice.
|
And
the point I'M trying to make is that I have at least two trading partners who
send forecasts in AND ADDITIONALLY expect a new purchase order to be opened with
the transmission of this 830/DELFOR. So in your experience an 830 is
never used as a PO but that turns out not to be the case in my
experience.
True,
any vanilla processing system would kick it out. We, of course, have made
extensive modifications to our translator environment so that this functionality
can happen. And if your customer explains that they want to send a
PO in with an 830, I trust that you as a supplier will be more than willing to
accomodate them.
|
