We are very pleased that you are considering writing an article for the ISUG-TECH Journal. Sharing your expertise makes us all more aware of the important issues facing our organizations, and helps us to become more effective users of SAP  technologies. To assist our authors and ease the production process, we have established a few basic guidelines which can be downloaded here.

    Contact us at if you are interested in writing for us. We'd like to discuss your topic with you to see that it's relevant, that it hasn't been already covered elsewhere in the Journal, and to talk about deadlines. We may ask you to send an abstract for review. If you have a good topic but don't feel that you can write anything very long, don't let that stop you–we may run it as a technical tip.


    • We rarely accept articles that have already been run in other publications.
    • We do not accept marketing pieces.
    • We do accept articles that discuss management topics, or technical concepts in a very general or theoretical fashion, provided that the content is strategic in nature and is designed to open the readers' minds to technologies and methodologies that they might not be currently considering.
    • All articles published become the property of ISUG-TECH. They can be used freely by the author after initial publication, with inclusion of the language: "First published in the ISUG-TECH Journal, International Sybase User Group". ISUG-TECH does require notification prior to publication. (Note: this reprint courtesy only applies to the author, and not any third party, including the author's employer, unless prior arrangements have been made.)

    After Your Abstract or Article Has Been Accepted

    1. As you begin writing your article, please send a brief summary or abstract of your article. Also, please let us know if you anticipate including graphic images, pictures, etc.
    2. Content-wise, we look for solid technical content, giving details of architectures and interesting functions; commands and results– information useful and interesting to a sophisticated client/server audience. Please include code fragments used to deal with specific problems.
    3. Please try to meet the word count as established in your conversation with the Managing Editor or ISUG-TECH representative. This helps us fit the article into the rest of the Journal's material, and means we won't have to come back to you asking for copy cuts. However, if you find that there is a problem staying within or meeting foobar word count, please let us know as soon as possible, and we will do our best to accommodate you.
      NOTE: Please do NOT change the topic or substitute another article at the last minute! If you are concerned about meeting the deadline as the time draws near, let us know immediately and we'll discuss it from there.
    4. Obviously, please do your best to meet the scheduled deadline. Again, the earlier we get your copy, the more flexibility we have to run it without cuts or changes.
    5. Your article will be reviewed by our Technical Editorial board. These highly qualified industry experts will respond with suggestions and comments on your article, which will be passed on to you by the Managing Editor.
    6. After your final edits, take the time to proofread the copy carefully before you send it to us. You'll have one more chance to see it before it's printed, but accuracy up-front will help prevent typesetting errors. Naturally, we're especially concerned that any included code or commands be exactly right. The column width of the ISUG -TECH Journal is 2 1/2", so break up lines of code to be shorter whenever possible.
    7. Graphics (screenshots, etc.) should be included inside the document so we know their correct positions, but must also be sent outside of the document, and in uncompressed format. All graphics ideally should be in 300 dpi resolution.
    8. We'd also need a photograph – ideally, a professional 5"x7" black-and-white glossy head shot, but a passport-type photo is also fine – and a brief biographical sketch highlighting your professional background and experience with SAP products and the topic being covered.
    9. Please send your final article by e-mail (Microsoft Word or Open Document Format are best, but we can translate most files), with photos and hi-rez graphics, to the Managing Editor.

    Please note that adherence to these guidelines is a requirement to qualify for remuneration.

    Although all of our authors gain recognition for both themselves and their company through being published in the ISUG-TECH Journal, as well as a great portfolio piece and resume item, ISUG-TECH also rewards each author of featured articles based upon their on-going contributions*.

    • First article: 6 month subscription to ISUG-TECH website
    • Second article: Upgrade to a 12 month Core membership
    • Third article: Upgrade to a 12 month Gold membership

    These rewards are based upon a 12 month rolling calendar beginning with the author's first published article. Regular columnists (minimum of 6 columns per year) also receive a stipend of $100 for each published column.

    If an article is also included in our print edition, the author will receive four complimentary copies of the printed issue of the Journal in which their article is published. Additional copies are available through ISUG-TECH.

    * This reward system begins with Issue 7, 2013. To be considered for any form of remuneration, authors must adhere to the Author Guidelines for a featured article.

    In the event that a single article is split across multiple issues due to length, ISUG-TECH will generally only pay for the first portion unless a waiver agreement is in place prior to submission.

    If an article is attributed to multiple authors, one author must be identified as the primary author and will be the qualifying author for any remuneration. Also, only 1 article per author(s), per issue, will be considered for any remuneration.

    Please note that authors will not receive monetary payment for their article if they have received payment for their work from another source. A detailed explanation of this restriction is available from ISUG-TECH upon request.


    Copyright © 2014 ISUG-TECH. All Rights Reserved
    All material, files, logos and trademarks within this site are copyright their respective organizations

    Terms of Service - Privacy Policy - Contact the Help Desk