Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Electronic Data Interchange (EDI)

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Electronic Data Interchange (EDI)

    Hi,

    I was wondering if anyone has integrated Alpha with an EDI server?

    If so, how do you get started and were there any challenges?

    My app is an electronic medical record system, and based on HiTECH it is not a real EMR without this component. There are 8 modules that must be included. EDI is also the standard for B2B communication. Very important stuff.
    Tags: None
    #2
    Re: Electronic Data Interchange (EDI)

    Chris,
    ??? Maybe explain what you mean by
    if anyone has integrated Alpha with an EDI server
    ....Doesn't an EDI server take in EDI files, parse them into individual pieces of data, and then (mainly I believe) process this data into reports/dashboards/charts, etc ?

    Does integrate mean to be able to take the information OUT of the server once the EDI files have been processed?

    In addition to this....even if someone had integrated Alpha as you want, there is no set EDI standard even for a single industry, much less than for all industries that use this form of data transfer....so what integration that works for one most likely would have to be overhauled/rebuilt for another.
    Mike
    __________________________________________
    It is only when we forget all our learning that we begin to know.
    It's not what you look at that matters, it's what you see.
    Henry David Thoreau
    __________________________________________



    Comment

      #3
      Re: Electronic Data Interchange (EDI)

      Years ago I wrote an application to take EDI schedules (files) from the car assemblers and to send them Shipping Notices (as a file) when goods were dispatched. So the data can go both ways.

      Nowadays data transfer via files is a bit antiquated - live exchange using http with data in XML format is way better. Is this an option in your case?

      Either way, a solution can be built in Alpha.

      EDIT: Oops - I jumped in before realizing that this is a web question, which I have not done, but again I am confident that Alpha can be used for a solution.

      Comment

        #4
        Re: Electronic Data Interchange (EDI)

        Thank you for the positive responses. It is good to know someone else has done this.

        From what I can tell, the EDI servers are maintained by "Clearing Houses" which ensures XML data is properly mapped to different applications. This is great because XML data can be generated by SQL Server and I imagine XBasic as well.

        The Health Care industry (CMS/DHHS) now has several standardized protocols (maps). The protocols are maintained by non-profit organizations and cost $600!

        Let the journey begin.

        Comment

          #5
          Re: Electronic Data Interchange (EDI)

          Chris,

          As Mike mentioned, each EDI implementation has its own set of requirements. The format of the message is one variable. The mode of transmission is another.

          I have done an EDI invoicing routine for the transportation industry. It used a transport industry message format(from the ASCx12 standard). Even so, within that standard the particular invoice clearing house did not use all of the elements. The method of transmission used was ftp. This solution was an addon for an existing application so xbasic was used to translate existing table data into a suitable EDI message.(not all existing fields and terminology corresponded to the EDI elements and codes).

          The project was lots of fun to do but frustrating at times due to the lack of open source(that I could find) info on the actual standards. As you have found some standards are quite expensive to buy.

          In the end I got there by working with the people that actually were receiving the message. Taking what they were expecting to receive and working backwards from there. Also when ever you get bits of info like acronyms for standards etc, let google be your friend. You will find that all kinds of companies, government departments and educational bodies have implementation documents on the interweb. Using those pieces you should be able to solve the puzzle.

          Good luck and have fun.

          Tim
          Tim Kiebert
          Eagle Creek Citrus
          A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

          Comment

            #6
            Re: Electronic Data Interchange (EDI)

            Having spent several years integrating EDI between companies in the automotive and office furniture industries (on Progress not Alpha) - and having purchased the ANSI-X12 manuals (which are expensive) - and having spent two years on the team that developed the Office Furniture Industry standards ..

            You have to work hand in hand with the people you are exchanging data with - sending and receiving test files until you've got it down pat and there are no errors. Every x12 document has a corresponding acknowledgment document.

            The good news is that they have an industry standard and once you've gotten it together for one client, the same code generally works for future clients with minimal revision.

            All you are doing here is importing and validating data and acknowledging that the data has been received. X12 docs generally are wrapped in a package with a begin and end and you'll use those to verify that you've received the entire document - although you will not use all of the data in the standard for that document.

            Comment

              #7
              Re: Electronic Data Interchange (EDI)

              Thank you

              This seems to require XQuery. How do this integrate with Xbasic, and does anyone have an example of Xbasic calling an Xquery...uh..query to send data...did I ask this correctly?

              Comment

                #8
                Re: Electronic Data Interchange (EDI)

                DECLARE @x xml
                SET @x = '<ROOT><a>111</a></ROOT>'
                SELECT @x.query('/ROOT/a')

                ---------------------------------
                SELECT Instructions.query('declare namespace AWMI="http://schemas.microsoft.com/sqlserver/2008/07/adventure-works/ProductModelManuInstructions";
                /AWMI:root/AWMI:Location[@LocationID=10]
                ') as Result
                FROM Production.ProductModel
                WHERE ProductModelID=7

                ---------------------------------
                more stuff
                http://msdn.microsoft.com/en-us/library/ms189919.aspx

                Comment

                Previous template Next
                Working...
                X