How robust is your EDI mapping utility? I've had to bypass application system stupidity in the past by trying this kind of logic in line item objects (made generic as I don't know what you're using on the EDI or APP side):
Whenever you are on an 850 PO1: PO102 -> Quantity PO104 -> Price PO107 -> Item ID Whenever you are on an 850 SAC nested inside a PO1 loop: "1" -> Quantity -SAC05 -> Price PO107++"|"++SAC02 -> Item ID So the data inside the application and thisly the extract out in the invoice *might* look like (Format of Quantity,Price,ItemID) : 100,10,ItemXYZ 1,-1,ItemXYZ|F970 1,-0.5,ItemXYZ|C300 100,10,ItemABC 1,-1,ItemABC|F970 1,-0.5,ItemABC|C300 So it'd be the mapper's dirty job to assemble things like: If the ItemID has no pipe character, make a PO1 If the itemID has a pipe character, make a SAC. SAC02 is from the substring on the ItemID after the pipe. > > Item XYZ 100 @ 10.00 > SAC rebate 100 @ -1.00 > SAC discount 100 @ -0.50 > > Item ABC 100 @ 10.00 > SAC rebate 100 @ -1.00 > SAC discount 100 @ -0.50 > > > Accounting system lists all ***FOUR*** > Item XYZ 100 @ 10.00 > Item ABC 100 @ 10.00 > Item SAC-rebate 200 @ -1.00 <--unless these codes are unique > Item SAC-discount 200 @ -0.50 <--they get munged togther! > > INV > > IT1 Item XYZ data > IT1 Item ABC data > SAC SAC-rebate data joined > SAC SAC-discount data joined > > > If the system would support completely ad-hoc items, you could dynamically > generate item discount codes so they would be unique, like "Item XYZ > Discount A" but it doesn't that I am aware of. The codes must be configured. > > Thanks, > Travis- > > > > > -----Original Message----- > From: Dale Marthaller [mailto:[EMAIL PROTECTED] > Sent: Friday, April 20, 2007 11:57 AM > To: Travis Truax; [email protected] > Subject: RE: [EDI-L] Complex SAC segment handling in 850 & 810 > > > Is is possible with your accounting system to emulate SAC's with fake item > codes. Lets say that you had a PO with one item and two SAC's. > > PO > > Item XYZ 100 @ 10.00 > SAC rebate 100 @ -1.00 > SAC discount 100 @ -0.50 > > > Accounting system list all three > Item XYZ > Item SAC-rebate > Item SAC-discount > > INV > > IT1 Item XYZ data > SAC SAC-rebate data > SAC SAC-discount data > > > > > > _____ > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of > Travis Truax > Sent: Friday, April 20, 2007 7:41 AM > To: '[email protected]' > Subject: [EDI-L] Complex SAC segment handling in 850 & 810 > > > > Please excuse the length of this post & the number of questions. I > appreciate your time reading it. :) > > We have a [crappy] accounting system that has 2 serious issues with > discounts. > 1. It can't handle anything except a discount percentage. No detail of what > the discount is for, no sac codes, no rates, amounts, etc. > 2. I can only enter *one* discount per header or line. > > As you can imagine, it's a major challenge to get 3 discrete discounts on > one line item of a po into the customer's invoice when I have to aggregate > the discount percentages of all 3 discounts into one extended discount. > > Currently, I write the sac info out to an extension table to be referenced > later by the invoice. > > Here's were the serious failure occurs: > This [crappy] accounting system also does not handle multiple ship to > locations on the same po (sdq/spreadsheet type order) - so I have to build > multiple orders from one spreadsheet order. How can I associate ONE set of > discounts with potentially MANY orders? > *Slice up the total discount among all the orders? > *Apply all the discounts to one of the orders? > *Give up and throw out the discounts as punishment for using sdq > segments? > *Other options... > > Tangent Questions: > Do most customers require their sacs sent back just as they sent > them? > How would one handle discounts on POs that are not "directly > associated" with the PO? To elaborate - if the discounts are not requested > to be subtracted from the invoice, they would not be entered into the sales > order (at least in our [crappy] accounting system). > > Thanks, > Travis- > > > > > > > [Non-text portions of this message have been removed] > ... 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/
