Our practice with our customers is to perform necessary calculations and data transformations in the APIs that integrate the EDI translator with the business software.
This way you can change the EDI translator and/or backend software by modifying only the API interface and still retain the business logic built into the API and it's interface with whatever doesn't get changed. This additional level of modularity saves big time and big money for the end-user in the long run compared with simply transferring flat files and re-building that business logic into components when they are replaced, if indeed the replacement software is sufficiently flexible to be modified at all. The only changes to data that we perform in the map are format changes (eg. 2 decimals to 4 decimals, etc.) which do not change the value of the data. Dave Taylor President Sysmark Information Systems, Inc. 49 Aspen Way Rolling Hills Estates, CA 90274 800-SYSMARK (800-797-6275) (O) 310-544-1974 (C) 310-561-5200 (P) 800-339-1497 (F) 310-377-3550 Your Source for Integrated EDI Translation and DataSync Integration www.sysmarkinfo.com ----- Original Message ----- From: Earl Wertheimer To: [email protected] Sent: Monday, July 31, 2006 9:32 AM Subject: [SPAM] Re: [EDI-L] Re: [edi_gns] How to price an invoice using a map Adding my 0.02 , Some of our clients have large, expensive (compared to their EDI system) ERP systems, that don't even come close to replicating the variability of the EDI documents being sent out... (or received) One example of this is SAC charges for taxes, freight, handling, discounts, allowances, ad nauseum. Most of these can be mapped, but some are not. Another big problem is the differences of units of measure. The incoming orders have case quantities, but the ERP system is all in units. The shipping quantities have to be changed back to cases (in the EDI system) before the invoices can be created. (Don't ask what happens if the shipper only packs part of a standard case...) I agree that having all this information in their ERP systems would be nice, but the cost of adding these fields is huge, so it's not done.... yet. To: "EDI-L" <[email protected]> From: "Michael Mattias" <[EMAIL PROTECTED]> Date sent: Tue, 25 Jul 2006 10:41:27 -0500 Subject: Re: [EDI-L] Re: [edi_gns] How to price an invoice using a map Send reply to: "Michael Mattias" <[EMAIL PROTECTED]> > > You NEVER calculate totals in an invoice. That is the job of the > > applications program. How do you know > > that your calculated total matches the value posted to A/R? If your > > applications folks don't understand this, > > i'd be happy to come over (on their dime, plus expenses) and explain it > > to them. > > Don't diss calculating the invoice amounts on the '810' out of hand. I have two > examples... > > 1. Application System (a well-known major brand whose name I won't give you but > its initials are either "Point.Man" or "MAPICS") has a bug and does not include > in its EDI invoice extract certain things... which causes the EDI invoice total > to not foot/agree with either A/R or itself. > > Ok, so that's a bug in a 'user-unfixable' system, which is pretty rare...but > this next one ....... > > 2. This happened to me about six-seven years ago.... the invoice receiver's > EDI system did not round line item fractional penny prices the same way the > application (correctly!) did it, so I had to calculate the TDS01 invoice amount > using "customer math." > > True, the ERP system and the check did not match, but my client (the seller) > didn't care as much about the fourteen-cent 'short pay' as he did about the > $73,000.00 invoice which was totally 'unpaid' for the sake of that fourteen > cent difference. > > That is, "never say never...." > > MCM > > > > > > > ... > 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 > > > > > > > > > > __________ NOD32 1.1684 (20060729) Information __________ > > This message was checked by NOD32 antivirus system. > http://www.eset.com > > Earl Wertheimer [EMAIL PROTECTED] http://www.spe-edi.com [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/ <*> 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/
