Topic
  • 3 replies
  • Latest Post - ‏2019-03-26T12:22:58Z by pratikd1987
pratikd1987
pratikd1987
24 Posts

Pinned topic X12 835 Db Structure

‏2019-03-19T17:06:44Z | @paulbrettibm

Hi @paulbrettibm ,

We are currently trying to map X12 835 transaction to our DB (SQL Server 2016).

However, we are having issues with creating the DB Design for a 835 transaction.

We have tried resorting to tools such as XMLSpy to convert XML to DB but to no avail (apparently the xsd created from design studio doesnt work).

We are trying to manually create tables for the 835 transaction for this scenario.

Could you let us know if there is a way to automatically generate a relational DB Design from the 835 .mtt file or .xsd file?

Looking forward to hearing from you.

 

Thanks

  • pratikd1987
    pratikd1987
    24 Posts

    Re: X12 835 Db Structure

    ‏2019-03-21T11:32:17Z  

    @PaulBrett

     

    Updated on 2019-03-21T17:39:08Z at 2019-03-21T17:39:08Z by pratikd1987
  • PaulBrett
    PaulBrett
    367 Posts

    Re: X12 835 Db Structure

    ‏2019-03-26T11:37:52Z  

    I am not overly familiar with the X12 standard, but if it is a simple file with a specific number of fields, then creating a data row is a simple matter.

    If the file is complicated (with having optional and possibly repeating segments) as I suspect it is, then a DB row is not going to hold all of that data effectively, and a relational DB consisting of many linked tables will be required.

    I think this is a design topic, too complex for the developerWorks forum, but if anybody else on here fancies giving it a stab (hours and hours of unpaid consultation time) then I say - have at it!

    Thank you.

    Paul

    Follow me on Twitter

  • pratikd1987
    pratikd1987
    24 Posts

    Re: X12 835 Db Structure

    ‏2019-03-26T12:22:58Z  
    • PaulBrett
    • ‏2019-03-26T11:37:52Z

    I am not overly familiar with the X12 standard, but if it is a simple file with a specific number of fields, then creating a data row is a simple matter.

    If the file is complicated (with having optional and possibly repeating segments) as I suspect it is, then a DB row is not going to hold all of that data effectively, and a relational DB consisting of many linked tables will be required.

    I think this is a design topic, too complex for the developerWorks forum, but if anybody else on here fancies giving it a stab (hours and hours of unpaid consultation time) then I say - have at it!

    Thank you.

    Paul

    Follow me on Twitter

    Thank you @paulbrett ,

    I will try posting this in the Sterling Forum