I Quoted text is from <FAC83571327A4C74BBF59442228A3040@desktop1>, by Michael Mattias/LS <[email protected]>
>1. Acknowledgement Reconciliation. >================================ > I think this is desirable, and our DMX Gateway software does this. For any incoming our outgoing document which has acknowledgement associated with it [1] the good/bad acknowledgement status is used to modify the status of the document which generated it in the traffic database. This is visible on traffic views, and the report generator (which can be scheduled and customised with SQL queries) can create any sort of summary required. Because the analysis and data storage infrastructure of the EDI system could be used for this it was not a very onerous capability to incorporate. If you are planning an external program rather than an extension to an existing one it could be quite a lot of work to implement. >2. Consolidated EDI/ERP History. >======================================= Potentially this could be a real can of worms unless it is being created for a specific ERP. Regarding acknowledgements then for outgoing some systems (from memory SAP - although it is many, many years since we had a SAP project) will allow status to be passed back from EDI and communication software. For incoming what are you supposed to do about flagging a conversion error to the ERP? Without data the warning is meaningless, and if you do pass through data from a faulted conversion then the ERP should be capable of dealing with it on its own terms; an EDI error does not necessarily mean that the essential data for a transaction has been compromised. I am not sure how much integration between ERP and EDI system you need. In my experience the proportion of transactions which are faulted is small and, providing the EDI system records a document identity which is meaningful for those using the ERP, and generates prompt error notifications which quote this identity, then it will in most cases be acceptable. I have always felt that the EDI system should act as a black box and that the business should be handled by the ERP; although there have been several cases where we have built customised extensions to the EDI system to handle ERP deficiencies :-( Regards Chris [1] Unfortunately acknowledgements are little used in Europe -- Chris Johnson mobile:+44 (0)7785 302122 Fax: +44 (0)870 0519 818 EDI website http://www.edimatrix.co.uk EDIMatrix Ltd work: 0844 414 6386 or +44 20 8778 1402 Registered in UK no. 2777624 Reg.Office: 34 Sydenham Rd, London SE26 5QF ------------------------------------ ... 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: [email protected] [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/
