Dave > 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.
Their business software is 10 or 20 years old. Written in BusinessBasic, or something else. No APIs exist. Just flat files to import orders and export shipments... PO comes in with a order quantity of 150 CA (cases). The PO4 segment has a pack qty of 12. The Order Entry system (I won't glorify it with the ERP acronym) does eaches only. The EDI system takes the 150 cases, multiplies the qty by 12 and creates a flat file (for import) with a quantity of 1800. If you have a better way, please let me know... > 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 componentswhen they arereplaced, if > indeedthe > 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. Earl Wertheimer [EMAIL PROTECTED] http://www.spe-edi.com ... 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/
