Title: Queries.


 
Hi,

        What I want is to have a Translator which will parse the EDI documents and give me the data in the form of Java objects for each transaction set. (Instead of a flat file).

        I am giving my design approach below. Please let me know if this is a practical design approach or it is too simplistic (non practical) . Also let us know what are the other issues which we would have to handle in our translator e.g security etc.

        Also you could suggest to me how I would be able to achieve my objective using the currently available translator's. Please note that I do not want to code for each Java class. I would prefer the Java classes to be generated and readily available. Typically most translators provide EDI to flat file conversion. And we have to write Java classes which would parse these files and populate the data mambers. Is there no translator where we can tell it to give me the data in Java objects format?

        My design approach is as follows :

        It will consist of 2 components :

1] Class Generator (will be used at design time to generate Java classes i.e. for PO, Invoice, PoAckw etc.)
2] Translator.

        I am explaining the general process in detail as follows :

Java class Development Process:
The client who has bought this product would use the class generator to parse the X12 standard files and will generate a Java class mapping to each standard (mapper) .i.e a class would be generated for PO, another class would be generated for Invoice etc.

Runtime Translator functionality :

        The translator will do the job of parsing the EDI file and reading the various functional groups and the transaction sets within the functional groups.  The translator class will instantiate Java objects corresponding to those transaction sets and after parsing the EDI document it will populate the respective objects for each transaction set. Before populating the objects it would be doing the validation of the EDI file looking at the Standard file for that transaction set. Thus we would be doing the EDI data to Java object conversion.

        Translator would be having the functionality of generating the response EDI files also. Our client would be given the Java classes generated by our Java class generator. He would be using the members in these classes to populate the data and he would send these objects to the Translator. The translator would look read these objects and generate an EDI file.

       
Thanks,
Bhushan.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Opinions expressed in this e-mail are those of the individual and not that of Mastek Limited, unless specifically indicated to that effect. Mastek Limited does not accept any responsibility or liability for it.

This e-mail and attachments (if any) transmitted with it are confidential and/or privileged and solely for the use of the intended person or entity to which it is addressed.

Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited.

This e-mail and its attachments have been scanned for the presence of computer viruses. It is the responsibility of the recipient to run the virus check on e-mails and attachments before opening them.

If you have received this e-mail in error, kindly delete this e-mail from all computers and please contact the sender on +91-22-829 0635.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Reply via email to