It seems to me that the best way to handle this is to internally identify the division with the PO. That way, the Trading Partner has nothing extra to do, there is no temptation to place two pieces of information in the PO number or part number, and you only need one GS ID.
But if the Invoice or ASN must be routed to a different platform depending on Divison, then it won't work unless you track the target system in the EDI system or some other middleware database. Art Douglas Lead Consultant Blackwater Network (877) 464-8915 -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Dunham Sent: Tuesday, July 08, 2008 9:09 AM To: [email protected] Subject: [EDI-L] Re: basic edi question No offense to Brian, but his solution may be a bit more complicated than you wish to go. Besides, what if you order the same item for two (or more) divisions...? Now you'd have to set up those additional items in your back-end system and your buyers would need to know which item they need to be ordering. The previous suggestions of using the N1 loop is probably the best. And it's something I use in our documents all the time. In our 850 spec, we have a BILL TO (BT) and a SHIP TO (ST) N1 (and the N3 and N4 segments) to reference where the item is to be shipped and where to send the bill.... We're a retailer with well over 300 store locations that get shipped product directly, as well as a single distribution center that handles the majority of our product lines and receives the bulk of our merchandise, which is then sent out to stores as needed. What this may require on your part, however, in addition to including the information in an N1 loop, is that some of your trading partners may want an address or location listing for all of the possible divisions and/or locations you will be shipping to. They need this to create a table on their own side that references the N104 element and populates that data into the ASN or the Invoice. Some systems may not be capable (or programmed/set up to) capture the data from the inbound PO and populate it to the outbound ASN or Invoice. That's My 2 bits... Craig Dunham EDI Coordinator Big 5 Sporting Goods --- In [email protected], Brian Lehrhoff <[EMAIL PROTECTED]> wrote: > > I vote to hide it as a REF DP. No one knows what DV is and probably > will ignore it. DP (department) > is commonly accepted, persisted and returned. Your partners need to > save the field for each order and > be able to parrot it back. Hiding it in a N1 may or may not work - if > the N1 is built from the customer > file your field will be ignored. > > You can also try hiding it in the PO1. For example, prefix your item > numbers with the division > (01-XXXXXX). This method lets the customer order multiple items from > multiple divisions. If you > don't let them mix the orders (i.e. the warehouses are 30 miles apart), > then you can set up some > business rules ... for example, the order prefix has to match the > department. That's fairly easy to > test in any translator (even ours). > > Art Douglas wrote: > > PER is short for Person. (At list I think it is.) Put the buyer, the EDI > > person, the guy who washes the windows, but not the division there. > > > > Use the N1 or REF, as suggested by Mr. Nolen. I would use N101 = DV for > > Division, then give them a division code in N104, with an N103 qualifier of > > 56 for division. Make sure you specify that you want to see the code > > returned in the 856 and 810. > > > > Some companies revise the group sender id, keeping the same ISA sender id. > > I don't recommend it, because that creates too much admin overhead. > > > > Art Douglas > > Lead Consultant > > Blackwater Network > > (877) 464-8915 > > -----Original Message----- > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of > > improvadam > > Sent: Monday, July 07, 2008 12:03 PM > > To: [email protected] > > Subject: [EDI-L] basic edi question > > > > I'm trying to figure out which segment I can put the my company's > > divisions into an 850 so that I can get them returned in the 856 and > > 810's. > > > > >From my research so far I am leaning toward PER. Would that be > > possible? doesn't seem 100% though, and I don't know if it would be > > returned in the 856 and 810 for parsing. > > > > The other option I'm seem to have found is that I create a unique EDI > > account for each division. With our current setup, I'm not looking > > forward to that option. ;) > > > > we have divisions like: plumbing, lighting, HVAC, etc. each make > > their own sets of PO's but are all integrated together in our system. > > > > any suggestions? > > > > Thanks > > -adam > > > > > > ------------------------------------ > > > > ... > > Please use the following Message Identifiers as your subject prefix: > > <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > > > > Job postings are welcome, but for job postings or requests for work: <JOBS> > > IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links > > > > > > > > > > > > > > ------------------------------------ > > > > ... > > Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > > > > Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links > > > > > > > > > > > > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%% > Brian Lehrhoff, EA ([EMAIL PROTECTED]) > Messaging Consultant 201-913-4506 > > Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com > Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% %%%%%%%%%% > ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
