Stephen Smith's Blog

All things Sage 300…

More on SData and Sage ERP Accpac 6

with 11 comments

SData is Sage’s new Web Services standard. It is documented in full at For Sage ERP Accpac 6.x, SData is the interface used by the browser based UI pages to communicate with the Server. Like in Accpac 5.X where the Accpac COM API was the interface used for all UI to Business Logic communication, this role is taken over by SData in 6.x. This means that there is a complete robust REST based Web Services interface to the Sage ERP Accpac application. Anything that can be done from an Accpac User Interface Web Page can also be done via any other program making SData Web Services calls.

REST based Web Services are very simple in how they are constructed, they are built using current Web Standards such as HTTP and Atom. For instance the screen shot below shows typing:


into the URL field for the Chrome Browser.

This URL is an SData request, it is sent to the server bcraccdemo and the application SDataServlet running there. The rest of the URL is then processed by the Accpac SData provider to return the correct data for customer 1200 (Ronald Black) in XML Atom format, which is then displayed in the Browser window. As you can see, no special infrastructure or programming libraries were required to make this Web Service call. All that was needed was the ability to send an HTTP request and receive the response.

SData is also self describing. Below is a screen shot of asking for the schema of the XML response given above.

When doing update or insert calls you need to provide an XML payload of data similar to the response above of the data to be updated or inserted.  There is also a standard interface for doing services which in Accpac includes things like reporting, day end and posting.

The example above was for customer 1200, however if the (‘1200’) part was removed, SData would have returned all the customers in A/R. In this case you can specify a filter to say return all customers greater than some point or specify which fields to sort the returned data by. SData will also page the data returned, it will return a block of records with links to the previous and next blocks.

Basically SData is a fairly simple protocol to use that should be accessible to almost any programming system. It is rich enough to support all UI operations required by Accpac. And ISV’s can be confident that it is complete enough, since all Accpac UIs rely on it. It is standards based on HTTP, Atom and other Web Standards allowing standards based tools to be used. Generally a very powerful Web Based Interface to greatly enhance Accpac’s intergratability and extensibility. Since SData is being adopted by all Sage Business Applications, learning and using SData with Accpac will teach you how to use SData for any SData equipped application, such as Sage CRM.

Written by smist08

January 18, 2010 at 11:45 pm

Posted in SData

Tagged with , , ,

11 Responses

Subscribe to comments with RSS.

  1. Your screenshots got lost.

    Django Dunn

    January 19, 2010 at 1:01 am

  2. Has (or will) Sage make any information on which products will be adopting this technology?

    Wayne Schulz

    January 24, 2010 at 1:40 pm

    • It should be showing up in most product’s roadmaps. Not sure if there is a definitive list. At this point I know Accpac, X3, CRM, SLX, Act!, Line 50, Line 200, CRE and Abra either have already added support or are in the process of doing so. I suspect I’ve forgotten a few, any ERP package adopting the GCRM contract must be doing so.


      January 25, 2010 at 11:26 pm

  3. Will the Accpac COM API still be available and supported in 6.x, or will our existing apps need to be converted to make REST calls?

    Kevin Silha

    March 19, 2010 at 2:58 pm

    • Yes the Accpac COM API will still be there. You will need to run such programs on a computer that has had workstation setup installed or run it on the server.


      March 19, 2010 at 5:10 pm

  4. […] in Sage ERP Accpac 6 More on SData and Sage ERP Accpac 6 Stateful SData On the Sage GCRM […]

  5. […] of our applications. I’ve blogged about SData a few times already: SData in Sage ERP Accpac 6, More on SData and Sage ERP Accpac 6 and Stateful SData. Calling something a RESTful Web Services API sounds pretty technical and […]

  6. […] same role that the Accpac COM API had in the VB world. I’ve blogged on SData  a few times: here, here, here and here. Basically we want to limit ourselves to at most one server call per user […]

  7. […] blogged a few times about using SData to feed data into Sage products and about the general ideas behind SData. In this blog posting I want to look at some benefits to integrating into Sage products using SData […]

  8. […] on SData, see the SData Website or some of my previous blog posts: SData in Sage ERP Accpac 6, More on SData and Sage ERP Accpac 6, Stateful SData, On the Sage GCRM Contract, Fun with SData, A Roadmap for SData Integration to Sage […]

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: